Você está na página 1de 879

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

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

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

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

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

14.5.2 Data Configuration on the UMG8900 ...........................................................................................14-9 14.5.3 Data Configuration Examples .......................................................................................................14-9 14.6 Service Management .............................................................................................................................14-15 14.7 Charging and CDR ................................................................................................................................14-15 14.8 Service Interaction.................................................................................................................................14-16 14.9 Reference...............................................................................................................................................14-16 14.9.1 Protocols and Specifications .......................................................................................................14-16 14.9.2 Acronyms and Abbreviations ......................................................................................................14-16

15 IP Fax Feature..........................................................................................................................15-1
15.1 Service Description .................................................................................................................................15-2 15.2 Working Principle....................................................................................................................................15-2 15.3 Benefits....................................................................................................................................................15-2 15.3.1 To Carriers.....................................................................................................................................15-2 15.3.2 To Mobile Subscribers...................................................................................................................15-2 15.4 Availability ..............................................................................................................................................15-2 15.4.1 Application ....................................................................................................................................15-2 15.4.2 Requirements for Software............................................................................................................15-3 15.4.3 Requirements for Hardware ..........................................................................................................15-3 15.5 Service Flow............................................................................................................................................15-3 15.5.1 Classification of Call Model..........................................................................................................15-3 15.5.2 Processing Flow ............................................................................................................................15-3 15.6 Data Configuration ..................................................................................................................................15-7 15.6.1 Configuring Data at the MSOFTX3000 Side ................................................................................15-7 15.6.2 Data Configuration Example.........................................................................................................15-9 15.7 Service Management .............................................................................................................................15-10 15.8 Charging and CDR ................................................................................................................................15-10 15.9 Service Interaction.................................................................................................................................15-10

16 License Feature .......................................................................................................................16-1


16.1 Service Description .................................................................................................................................16-2 16.1.1 Function Code ...............................................................................................................................16-2 16.1.2 Application Scope .........................................................................................................................16-2 16.2 Working Principle....................................................................................................................................16-2 16.2.1 Working Principle of License ........................................................................................................16-2 16.2.2 Running Status of License.............................................................................................................16-2 16.2.3 Invalidation of License..................................................................................................................16-3 16.2.4 Alerting Mechanism of License.....................................................................................................16-3 16.3 Operation and Maintenance of License ...................................................................................................16-4 16.3.1 LOD LICENSE (Loading a License) ............................................................................................16-4 16.3.2 ROL LICENSE (Rolling Back a License).....................................................................................16-5 16.3.3 LST LICENSE (Listing a License) ...............................................................................................16-6 16.3.4 DSP ESN (Displaying the System ESN) .......................................................................................16-7

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xi

Contents

HUAWEI MSOFTX3000 Feature Description 16.3.5 STR LICCRC (Starting CRC Check of License) ..........................................................................16-9 16.3.6 DSP LICENSE (Display Running License File Status) ................................................................16-9 16.3.7 DMP LICENSE (Dumping License File)....................................................................................16-10 16.3.8 ULD LICENSE (Uploading License File to FTP Server) ........................................................... 16-11 16.3.9 DLD LICENSE (Downloading License File from FTP Server)..................................................16-12

16.4 License Control Items............................................................................................................................16-12 16.4.1 Control Items...............................................................................................................................16-12 16.4.2 Resource Control Items ...............................................................................................................16-15 16.5 Other Precautions ..................................................................................................................................16-17 16.5.1 License Checks............................................................................................................................16-17 16.5.2 License Invalidation and Prevention ...........................................................................................16-17 16.5.3 License Alarms............................................................................................................................16-19 16.5.4 License Upgrading ......................................................................................................................16-20 16.5.5 Effects of BAM Operations on License ......................................................................................16-20 16.6 Reference...............................................................................................................................................16-21 16.6.1 Protocols and Specifications .......................................................................................................16-21 16.6.2 Acornyms and Abbreviations ......................................................................................................16-21

17 NE User Dynamic Monitoring Feature ..............................................................................17-1


17.1 Function Description ...............................................................................................................................17-2 17.1.1 Function Code ...............................................................................................................................17-2 17.1.2 Definition ......................................................................................................................................17-2 17.1.3 Standard Compliance ....................................................................................................................17-3 17.1.4 System Specifications....................................................................................................................17-3 17.1.5 Benefits .........................................................................................................................................17-4 17.1.6 Application Scenario .....................................................................................................................17-4 17.1.7 Application Limitations.................................................................................................................17-4 17.2 Availability ..............................................................................................................................................17-4 17.2.1 Requirements for NEs ...................................................................................................................17-4 17.2.2 Requirements for License..............................................................................................................17-5 17.2.3 Applicable Versions.......................................................................................................................17-5 17.2.4 Others ............................................................................................................................................17-5 17.3 Working Principle....................................................................................................................................17-5 17.3.1 Functions of NEs...........................................................................................................................17-5 17.3.2 Internal Processing of the System .................................................................................................17-6 17.3.3 External Interfaces.........................................................................................................................17-6 17.4 Service Flow............................................................................................................................................17-6 17.4.1 Monitoring Flow of Online User...................................................................................................17-6 17.4.2 Reporting Flow of User Operation ................................................................................................17-6 17.4.3 Disconnection Flow of User Operation .........................................................................................17-7 17.5 Function Maintenance .............................................................................................................................17-7 17.5.1 Overview .......................................................................................................................................17-7

xii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

17.5.2 Maintenance Operations................................................................................................................17-7 17.6 Service Management ............................................................................................................................. 17-11 17.7 Charging and CDR ................................................................................................................................ 17-11 17.8 Performance Measurement .................................................................................................................... 17-11 17.9 Service Interaction................................................................................................................................. 17-11 17.10 References ...........................................................................................................................................17-12 17.10.1 Standards and Specifications.....................................................................................................17-12 17.10.2 Glossary, Acronyms, and Abbreviations....................................................................................17-12 17.11 FAQ .....................................................................................................................................................17-12

18 SMS Notification for Call Failure Feature ........................................................................18-1


18.1 Service Description .................................................................................................................................18-2 18.1.1 Function Code ...............................................................................................................................18-2 18.1.2 Definition ......................................................................................................................................18-2 18.1.3 Benefits .........................................................................................................................................18-2 18.2 Availability ..............................................................................................................................................18-3 18.2.1 Requirements for NEs ...................................................................................................................18-3 18.2.2 Requirements for License..............................................................................................................18-3 18.2.3 Applicable Versions.......................................................................................................................18-3 18.3 Working Principle....................................................................................................................................18-3 18.3.1 Functions of Each NE....................................................................................................................18-3 18.3.2 Internal Processing ........................................................................................................................18-4 18.4 Service Flow............................................................................................................................................18-6 18.4.1 Prerequisites for Service Triggering..............................................................................................18-6 18.4.2 Service Triggering Point................................................................................................................18-7 18.4.3 Processing Flow After Service Triggering.....................................................................................18-8 18.5 Data Configuration ................................................................................................................................18-10 18.5.1 Data Configuration on the MSOFTX3000 ..................................................................................18-10 18.5.2 Data Configuration Sample .........................................................................................................18-10 18.6 Service Management ............................................................................................................................. 18-11 18.6.1 Operations by Carriers.................................................................................................................18-12 18.6.2 Operations by Subscribers...........................................................................................................18-13 18.7 Charging and Charging Data Record (CDR) .........................................................................................18-13 18.7.1 CDR of the SMMO .....................................................................................................................18-13 18.7.2 CDR of the SMMT......................................................................................................................18-13 18.7.3 Charging ......................................................................................................................................18-13 18.8 Service Interaction.................................................................................................................................18-13 18.8.1 Call Service .................................................................................................................................18-13 18.8.2 SM Service ..................................................................................................................................18-13 18.8.3 Call Forwarding Service..............................................................................................................18-13 18.8.4 Voice Mailbox Service ................................................................................................................18-14 18.9 Reference...............................................................................................................................................18-14

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xiii

Contents

HUAWEI MSOFTX3000 Feature Description 18.9.1 Protocols and Specifications .......................................................................................................18-14 18.9.2 Aronyms and Abbreviations ........................................................................................................18-14

19 Summer Time Feature of Wireless Time Zone ................................................................19-1


19.1 Feature Description .................................................................................................................................19-2 19.1.1 Function Code ...............................................................................................................................19-2 19.1.2 Definition ......................................................................................................................................19-2 19.1.3 Benefits .........................................................................................................................................19-3 19.2 Availability ..............................................................................................................................................19-3 19.2.1 Requirement for NEs.....................................................................................................................19-3 19.2.2 Requirement for License ...............................................................................................................19-3 19.2.3 Applicable Versions.......................................................................................................................19-3 19.3 Working Principle....................................................................................................................................19-4 19.4 Data Configuration ..................................................................................................................................19-5 19.4.1 Data Configuration for the MSOFTX3000 ...................................................................................19-5 19.4.2 Example.........................................................................................................................................19-6 19.5 Charging and CDR ..................................................................................................................................19-7 19.6 Service Interaction...................................................................................................................................19-8 19.7 Reference.................................................................................................................................................19-8 19.7.1 Protocols and Specifications .........................................................................................................19-8 19.7.2 Acronyms and Abbreviations ........................................................................................................19-8

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

21 Configuration Rollback Feature..........................................................................................21-1


Huawei Technologies Proprietary

xiv

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

21.1 Service Description .................................................................................................................................21-2 21.1.1 Function Code ...............................................................................................................................21-2 21.1.2 Definition ......................................................................................................................................21-2 21.1.3 Benefits .........................................................................................................................................21-3 21.2 Availability ..............................................................................................................................................21-3 21.2.1 Requirements for NEs ...................................................................................................................21-3 21.2.2 Requirements for License..............................................................................................................21-3 21.2.3 Applicable Versions.......................................................................................................................21-3 21.3 Working Principle....................................................................................................................................21-3 21.3.1 Basic Principle...............................................................................................................................21-3 21.3.2 State Transition..............................................................................................................................21-4 21.3.3 Validity Check ...............................................................................................................................21-6 21.4 Service Flow............................................................................................................................................21-7 21.5 Data Configuration ..................................................................................................................................21-9 21.5.1 Data Configuration on the MSOFTX3000 Side ............................................................................21-9 21.5.2 Configuration Preparations.......................................................................................................... 21-11 21.5.3 Configuration Steps.....................................................................................................................21-12 21.5.4 Data Configuration on the UMG8900 Side.................................................................................21-13 21.6 Service Management .............................................................................................................................21-13 21.6.1 Rollback Commands ...................................................................................................................21-13 21.6.2 Synchronization and Forcible Synchronization Commands........................................................21-14 21.6.3 Activation and Forcible Activation Commands...........................................................................21-17 21.6.4 Rollback and Forcible Rollback Commands ...............................................................................21-19 21.6.5 Cancellation and Confirmation Commands ................................................................................21-21 21.6.6 Query Commands........................................................................................................................21-23 21.7 Charging and CDR ................................................................................................................................21-27 21.8 Service Interaction.................................................................................................................................21-27 21.9 Reference...............................................................................................................................................21-27

22 CAMEL4 Service ....................................................................................................................22-1


22.1 Service Description .................................................................................................................................22-2 22.1.1 Function Code ...............................................................................................................................22-2 22.1.2 Definition ......................................................................................................................................22-2 22.1.3 System Specifications....................................................................................................................22-4 22.1.4 Benefits .........................................................................................................................................22-4 22.1.5 Application Scenario .....................................................................................................................22-4 22.1.6 Application Limitations.................................................................................................................22-4 22.2 Availability ..............................................................................................................................................22-4 22.2.1 Requirements for NEs ...................................................................................................................22-4 22.2.2 Requirement for License ...............................................................................................................22-5 22.2.3 Applicable Versions.......................................................................................................................22-5 22.2.4 Others ............................................................................................................................................22-5

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xv

Contents

HUAWEI MSOFTX3000 Feature Description

22.3 Working Principle....................................................................................................................................22-6 22.3.1 Functions of NEs...........................................................................................................................22-6 22.3.2 Internal Processing of the System .................................................................................................22-6 22.3.3 External Interfaces.........................................................................................................................22-6 22.4 Service Flow............................................................................................................................................22-6 22.4.1 Conference Call.............................................................................................................................22-7 22.4.2 CAMEL4 IN RBT Service ............................................................................................................22-9 22.4.3 CAMEL4 Simultaneous Ringing ................................................................................................22-10 22.5 Data Configuration ................................................................................................................................22-13 22.5.1 Overview .....................................................................................................................................22-13 22.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................22-13 22.5.3 Data Configuration at the UMG8900 Side ..................................................................................22-13 22.5.4 Data Configuration Examples .....................................................................................................22-14 22.6 Service Management .............................................................................................................................22-17 22.7 Charging and CDR ................................................................................................................................22-18 22.8 Performance Measurement ....................................................................................................................22-18 22.8.1 Specifications ..............................................................................................................................22-18 22.8.2 Implementation Principle ............................................................................................................22-19 22.9 Service Interaction.................................................................................................................................22-19 22.9.1 Restriction Between the Supplementary Services .......................................................................22-19 22.9.2 Restriction Between Multiple CPH Operations in the CAMEL4 Service ...................................22-20 22.10 Reference.............................................................................................................................................22-21 22.10.1 Specifications ............................................................................................................................22-21 22.10.2 Glossary, Acronyms and Abbreviation ......................................................................................22-21 22.11 FAQ .....................................................................................................................................................22-23

23 IMSI-Based Announcement.................................................................................................23-1
23.1 Service Description .................................................................................................................................23-3 23.1.1 Function Code ...............................................................................................................................23-3 23.1.2 Definition ......................................................................................................................................23-3 23.1.3 System Specifications....................................................................................................................23-3 23.1.4 Benefits .........................................................................................................................................23-3 23.1.5 Application Scenario .....................................................................................................................23-4 23.1.6 Application Limitations.................................................................................................................23-4 23.2 Availability ..............................................................................................................................................23-4 23.2.1 Requirements for NEs ...................................................................................................................23-4 23.2.2 Requirements for License..............................................................................................................23-4 23.2.3 Applicable Versions.......................................................................................................................23-4 23.2.4 Others ............................................................................................................................................23-5 23.3 Working Principle....................................................................................................................................23-5 23.3.1 Functions of the NEs .....................................................................................................................23-5 23.3.2 Internal Processing of the System .................................................................................................23-5

xvi

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

23.3.3 External Interfaces.........................................................................................................................23-7 23.4 Service Flow............................................................................................................................................23-7 23.5 Data Configuration ..................................................................................................................................23-8 23.5.1 Overview .......................................................................................................................................23-8 23.5.2 Data Configuration at the MSOFTX3000 Side .............................................................................23-8 23.5.3 Data Configuration at the UMG8900 Side ....................................................................................23-9 23.5.4 Data Configuration Examples .......................................................................................................23-9 23.5.5 Querying Tables of the IMSI-Based Announcement Service ......................................................23-10 23.6 Service Management .............................................................................................................................23-13 23.7 Charging and CDR ................................................................................................................................23-13 23.8 Performance Measurement ....................................................................................................................23-13 23.9 Interactions with Other Services............................................................................................................23-13 23.10 Reference.............................................................................................................................................23-13 23.10.1 Specifications ............................................................................................................................23-13 23.10.2 Acronyms and Abbreviations ....................................................................................................23-13 23.11 FAQ .....................................................................................................................................................23-13 23.11.1 Question 1..................................................................................................................................23-13 23.11.2 Question 2..................................................................................................................................23-14 23.11.3 Question 3..................................................................................................................................23-14

24 IP over E1 .................................................................................................................................24-1
24.1 Service Description .................................................................................................................................24-2 24.1.1 Function Code ...............................................................................................................................24-2 24.1.2 Definition ......................................................................................................................................24-2 24.1.3 System Specifications....................................................................................................................24-2 24.1.4 Benefits .........................................................................................................................................24-2 24.1.5 Application Scenario .....................................................................................................................24-3 24.1.6 Application Limitations.................................................................................................................24-3 24.2 Availability ..............................................................................................................................................24-4 24.2.1 Requirements for NEs ...................................................................................................................24-4 24.2.2 Requirements for License..............................................................................................................24-4 24.2.3 Applicable Versions.......................................................................................................................24-4 24.2.4 Others ............................................................................................................................................24-4 24.3 Working Principle....................................................................................................................................24-4 24.3.1 Functions Provided by NEs...........................................................................................................24-4 24.3.2 Internal Processing Flow of the System ........................................................................................24-5 24.3.3 External Interfaces.........................................................................................................................24-7 24.4 Service Flow............................................................................................................................................24-8 24.4.1 Inter-Office Call Flow Based on IP over E1..................................................................................24-8 24.4.2 Cross-MGW Call Flow Based on IP over E1 ..............................................................................24-10 24.5 Data Configuration ................................................................................................................................ 24-11 24.5.1 Overview of Data Configuration ................................................................................................. 24-11

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xvii

Contents

HUAWEI MSOFTX3000 Feature Description 24.5.2 Data Configuration at the MSOFTX3000 Side ........................................................................... 24-11 24.5.3 Data Configuration at the UMG8900 Side ..................................................................................24-13 24.5.4 Data Configuration Example.......................................................................................................24-17

24.6 Service Management .............................................................................................................................24-19 24.7 Charging and CDR ................................................................................................................................24-19 24.8 Performance Measurement ....................................................................................................................24-20 24.9 Service Interaction.................................................................................................................................24-20 24.10 Reference.............................................................................................................................................24-20 24.10.1 Specifications ............................................................................................................................24-20 24.10.2 Glossary, Acronyms, and Abbreviations....................................................................................24-20

25 IP QoS Flow Control .............................................................................................................25-1


25.1 Feature Description .................................................................................................................................25-2 25.1.1 Function Code ...............................................................................................................................25-2 25.1.2 Definition ......................................................................................................................................25-2 25.1.3 System Specifications....................................................................................................................25-2 25.1.4 Benefits .........................................................................................................................................25-3 25.1.5 Application Scenario .....................................................................................................................25-3 25.1.6 Application Limitations.................................................................................................................25-3 25.2 Availability ..............................................................................................................................................25-3 25.2.1 Requirements for NEs ...................................................................................................................25-3 25.2.2 Requirements for License..............................................................................................................25-4 25.2.3 Applicable Versions.......................................................................................................................25-4 25.2.4 Others ............................................................................................................................................25-4 25.3 Working Principle....................................................................................................................................25-4 25.3.1 Functions of NEs...........................................................................................................................25-4 25.3.2 Internal Processing of the System .................................................................................................25-5 25.3.3 External Interfaces.........................................................................................................................25-8 25.4 Service Flow............................................................................................................................................25-8 25.4.1 IP QoS Flow Control in Inter-Office Office Direction Mode for Outgoing Calls .........................25-9 25.4.2 IP QoS Flow Control in Inter-Office Gateway Pair Mode for Outgoing Calls..............................25-9 25.4.3 IP QoS Flow Control in Gateway Pair Mode for Intra-Office Calls............................................25-10 25.5 Data Configuration ................................................................................................................................ 25-11 25.5.1 Overview ..................................................................................................................................... 25-11 25.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................25-12 25.5.3 Data Configuration at the UMG8900 Side ..................................................................................25-15 25.5.4 Data Configuration Examples .....................................................................................................25-16 25.5.5 Operations by Carriers.................................................................................................................25-18 25.5.6 Operations by Mobile Subscribers ..............................................................................................25-18 25.6 Charging and CDR ................................................................................................................................25-18 25.7 Performance Measurement ....................................................................................................................25-18 25.7.1 Index Description ........................................................................................................................25-19

xviii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

25.7.2 Implementation Principle ............................................................................................................25-19 25.8 Service Interaction.................................................................................................................................25-19 25.9 References .............................................................................................................................................25-19 25.9.1 Standards and Specifications.......................................................................................................25-19 25.9.2 Acronyms and Abbreviations ......................................................................................................25-19 25.10 FAQ .....................................................................................................................................................25-20

26 O-CSI SMS ..............................................................................................................................26-1


26.1 Service Description .................................................................................................................................26-2 26.1.1 Function Code ...............................................................................................................................26-2 26.1.2 Definition ......................................................................................................................................26-2 26.1.3 Standard Compliance ....................................................................................................................26-2 26.1.4 System Specifications....................................................................................................................26-2 26.1.5 Benefits .........................................................................................................................................26-2 26.1.6 Application Scenario .....................................................................................................................26-2 26.1.7 Application Limitations.................................................................................................................26-3 26.2 Availability ..............................................................................................................................................26-3 26.2.1 Requirements for NEs ...................................................................................................................26-3 26.2.2 Requirements for License..............................................................................................................26-3 26.2.3 Applicable Versions.......................................................................................................................26-3 26.2.4 Others ............................................................................................................................................26-4 26.3 Working Principle....................................................................................................................................26-4 26.3.1 Functions of the NEs .....................................................................................................................26-4 26.3.2 Intenal System Processing.............................................................................................................26-4 26.3.3 External Interfaces.........................................................................................................................26-7 26.4 Service Flow............................................................................................................................................26-8 26.5 Data Configuration ................................................................................................................................26-10 26.5.1 Overview .....................................................................................................................................26-10 26.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................26-10 26.5.3 Data Configuration at the HLR Side ...........................................................................................26-13 26.5.4 Data Configuration Example.......................................................................................................26-13 26.5.5 Table Query Procedure of the O-CSI SMS..................................................................................26-14 26.6 Service Management .............................................................................................................................26-16 26.6.1 Operations by Carriers.................................................................................................................26-17 26.6.2 Operations by Subscribers...........................................................................................................26-18 26.7 Charging and CDR ................................................................................................................................26-18 26.7.1 Charging Principle.......................................................................................................................26-18 26.7.2 CDR.............................................................................................................................................26-18 26.8 Performance Measurement ....................................................................................................................26-18 26.9 Service Interaction.................................................................................................................................26-18 26.10 Reference.............................................................................................................................................26-18 26.10.1 Specifications ............................................................................................................................26-18

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xix

Contents

HUAWEI MSOFTX3000 Feature Description 26.10.2 Glossary, Acronyms, and Abbreviations....................................................................................26-19

26.11 FAQ .....................................................................................................................................................26-19

27 UP Header Redundancy Data Service................................................................................27-1


27.1 Service Description .................................................................................................................................27-2 27.1.1 Function Code ...............................................................................................................................27-2 27.1.2 Definition ......................................................................................................................................27-2 27.1.3 Benefits .........................................................................................................................................27-2 27.1.4 Application Scenario .....................................................................................................................27-2 27.1.5 Application Limitations.................................................................................................................27-2 27.2 Availability ..............................................................................................................................................27-3 27.2.1 Requirements for NEs ...................................................................................................................27-3 27.2.2 Requirements for License..............................................................................................................27-3 27.2.3 Applicable Versions.......................................................................................................................27-3 27.2.4 Others ............................................................................................................................................27-3 27.3 Working Principle....................................................................................................................................27-3 27.3.1 Functions of the NEs .....................................................................................................................27-3 27.3.2 Internal Processing of the System .................................................................................................27-4 27.3.3 External Interfaces.........................................................................................................................27-8 27.4 Service Flow............................................................................................................................................27-9 27.5 Data Configuration ................................................................................................................................27-15 27.5.1 Data Configuration at the MSOFTX3000 Side ...........................................................................27-15 27.5.2 Data Configuration at the UMG8900 Side ..................................................................................27-17 27.5.3 Data Configuration at the HLR Side ...........................................................................................27-17 27.5.4 Data Configuration Example.......................................................................................................27-17 27.6 Performance Measurement ....................................................................................................................27-19 27.7 Service Interaction.................................................................................................................................27-19 27.8 Reference...............................................................................................................................................27-20 27.8.1 Specifications ..............................................................................................................................27-20 27.8.2 Glossary, Acronyms, and Abbreviations......................................................................................27-20 27.9 FAQ .......................................................................................................................................................27-20

28 VDB Dynamic Data Backup ................................................................................................28-1


28.1 Feature Description .................................................................................................................................28-2 28.1.1 Function Code ...............................................................................................................................28-2 28.1.2 Function Definition .......................................................................................................................28-2 28.1.3 System Specification .....................................................................................................................28-3 28.1.4 Service Benefits.............................................................................................................................28-3 28.1.5 Application Scenario .....................................................................................................................28-3 28.1.6 Use Restriction ..............................................................................................................................28-3 28.2 Availability ..............................................................................................................................................28-4 28.2.1 Requirements for NEs ...................................................................................................................28-4 28.2.2 Requirements for License..............................................................................................................28-4

xx

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

28.2.3 Applicable Versions.......................................................................................................................28-4 28.3 Working Principle....................................................................................................................................28-4 28.3.1 Functions Provided by NEs...........................................................................................................28-4 28.3.2 Internal System Processing ...........................................................................................................28-5 28.3.3 External Interfaces.........................................................................................................................28-8 28.4 Service Flow............................................................................................................................................28-8 28.4.1 Subscriber Data Backup FLow......................................................................................................28-8 28.4.2 Processing of Aging upon Dual-Homing Switchover .................................................................28-14 28.4.3 MT Flow Optimization upon Dual-Homing Switchover.............................................................28-14 28.5 Data Configuration ................................................................................................................................28-14 28.5.1 Overview .....................................................................................................................................28-14 28.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................28-15 28.5.3 Data Configuration at the UMG8900 Side ..................................................................................28-16 28.5.4 Example.......................................................................................................................................28-16 28.6 Service Management .............................................................................................................................28-21 28.7 Charging and CDR ................................................................................................................................28-22 28.8 Interaction with Other Services .............................................................................................................28-22 28.9 Reference...............................................................................................................................................28-22 28.9.1 Specifications ..............................................................................................................................28-22 28.9.2 Glossary, Acronyms, and Abbreviations......................................................................................28-23

29 Multi-Area Network Role-Based and Domain-Based Management Feature.............29-1


29.1 Service Description .................................................................................................................................29-3 29.1.1 Function Code ...............................................................................................................................29-3 29.1.2 Definition ......................................................................................................................................29-3 29.1.3 Standard Compliance ....................................................................................................................29-6 29.1.4 System Specifications....................................................................................................................29-6 29.1.5 Benefits .........................................................................................................................................29-6 29.1.6 Application Scenario .....................................................................................................................29-7 29.1.7 Application Limitations.................................................................................................................29-7 29.2 Availability ..............................................................................................................................................29-7 29.2.1 Requirements for NEs ...................................................................................................................29-7 29.2.2 Requirements for License..............................................................................................................29-8 29.2.3 Applicable Versions.......................................................................................................................29-8 29.2.4 Others ............................................................................................................................................29-8 29.3 Working Principle....................................................................................................................................29-8 29.3.1 Functions of NEs...........................................................................................................................29-8 29.3.2 System Internal Processing ...........................................................................................................29-8 29.3.3 External Interfaces.........................................................................................................................29-9 29.4 Service Flow............................................................................................................................................29-9 29.5 Data Configuration ................................................................................................................................29-10 29.5.1 Overview .....................................................................................................................................29-10

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxi

Contents

HUAWEI MSOFTX3000 Feature Description 29.5.2 Data Configuration on the M2000...............................................................................................29-10 29.5.3 Data Configuration on the MSOFTX3000 ..................................................................................29-16 29.5.4 Data Configuration Example.......................................................................................................29-16

29.6 Service Management .............................................................................................................................29-19 29.7 Charging and CDR ................................................................................................................................29-19 29.8 Performance Measurement ....................................................................................................................29-20 29.9 Service Interaction.................................................................................................................................29-20 29.10 Reference.............................................................................................................................................29-20 29.10.1 Specifications ............................................................................................................................29-20 29.10.2 Acronyms and Abbreviations ....................................................................................................29-20 29.11 FAQ .....................................................................................................................................................29-20

30 Alarm for Malicious Short Messages .................................................................................30-1


30.1 Service Description .................................................................................................................................30-2 30.1.1 Function Code ...............................................................................................................................30-2 30.1.2 Definition ......................................................................................................................................30-2 30.1.3 Standard Compliance ....................................................................................................................30-2 30.1.4 System Specifications....................................................................................................................30-2 30.1.5 Benefits .........................................................................................................................................30-2 30.1.6 Application Scenario .....................................................................................................................30-2 30.1.7 Application Limitations.................................................................................................................30-3 30.2 Availability ..............................................................................................................................................30-3 30.2.1 Requirements for NEs ...................................................................................................................30-3 30.2.2 Requirements for License..............................................................................................................30-3 30.2.3 Applicable Versions.......................................................................................................................30-3 30.2.4 Others ............................................................................................................................................30-4 30.3 Working Principle....................................................................................................................................30-4 30.3.1 Functions of the NEs .....................................................................................................................30-4 30.3.2 Internal Processing of the System .................................................................................................30-4 30.3.3 External Interfaces.........................................................................................................................30-5 30.4 Service Flow............................................................................................................................................30-5 30.5 Data Configuration ..................................................................................................................................30-7 30.5.1 Overview .......................................................................................................................................30-7 30.5.2 Data Configuration at the MSOFTX3000 Side .............................................................................30-7 30.5.3 Data Configuration at the UMG8900 Side ....................................................................................30-8 30.5.4 Data Configuration Examples .......................................................................................................30-8 30.5.5 Data Table Relevant to the Alarm for Malicious Short Messages .................................................30-9 30.6 Service Management ...............................................................................................................................30-9 30.7 Service Interaction...................................................................................................................................30-9

31 Call Simulation.......................................................................................................................31-1
31.1 Service Description .................................................................................................................................31-2 31.1.1 Function Code ...............................................................................................................................31-2

xxii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

31.1.2 Definition ......................................................................................................................................31-2 31.1.3 System Specifications....................................................................................................................31-3 31.1.4 Benefits .........................................................................................................................................31-4 31.1.5 Application Scenario .....................................................................................................................31-4 31.1.6 Application Limitations.................................................................................................................31-4 31.2 Availability ..............................................................................................................................................31-5 31.2.1 Requirements for NEs ...................................................................................................................31-5 31.2.2 Requirements for License..............................................................................................................31-5 31.2.3 Applicable Versions.......................................................................................................................31-5 31.3 Working Principle....................................................................................................................................31-5 31.3.1 Functions of the NEs .....................................................................................................................31-5 31.3.2 Internal Processing of the System .................................................................................................31-8 31.4 Service Flow............................................................................................................................................31-8 31.4.1 Selection of LAI/GCI and Circuits................................................................................................31-8 31.4.2 Handling at the Trunk Side............................................................................................................31-9 31.5 Data Configuration ................................................................................................................................31-10 31.5.1 Configuration Description...........................................................................................................31-10 31.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................31-10 31.5.3 Data Configuration at the UMG8900 Side ..................................................................................31-10 31.5.4 Data Configuration Example.......................................................................................................31-10 31.6 Service Management ............................................................................................................................. 31-11 31.6.1 Creating a Call Simulation Task.................................................................................................. 31-11 31.6.2 Message Trace and Logs During the Call Simulation .................................................................31-14 31.6.3 Description of the Shortcut Menu of the Message Output Pane..................................................31-15 31.6.4 File Saving ..................................................................................................................................31-16 31.6.5 Operations by Carriers.................................................................................................................31-16 31.7 Charging and CDR ................................................................................................................................31-17 31.8 Performance Measurement ....................................................................................................................31-17 31.9 Service Interaction.................................................................................................................................31-17 31.10 Reference.............................................................................................................................................31-17 31.10.1 Specifications ............................................................................................................................31-17 31.10.2 Glossary, Acronyms, and Abbreviations....................................................................................31-17 31.11 FAQ .....................................................................................................................................................31-18

32 Load-Based Handover ...........................................................................................................32-1


32.1 Service Description .................................................................................................................................32-2 32.1.1 Function Code ...............................................................................................................................32-2 32.1.2 Definition ......................................................................................................................................32-2 32.1.3 System Specifications....................................................................................................................32-2 32.1.4 Benefits .........................................................................................................................................32-3 32.1.5 Application Scenario .....................................................................................................................32-3 32.1.6 Application Limitation ..................................................................................................................32-3

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxiii

Contents

HUAWEI MSOFTX3000 Feature Description

32.2 Availability ..............................................................................................................................................32-3 32.2.1 Requirements for NEs ...................................................................................................................32-3 32.2.2 Requirements for License..............................................................................................................32-4 32.2.3 Applicable Versions.......................................................................................................................32-4 32.2.4 Others ............................................................................................................................................32-4 32.3 Working Principle....................................................................................................................................32-4 32.3.1 Functions of the NEs .....................................................................................................................32-4 32.3.2 Internal Processing of the System .................................................................................................32-6 32.3.3 External Interface ..........................................................................................................................32-7 32.4 Service Flow............................................................................................................................................32-7 32.4.1 Intra-MSC Load-Based Handover From 3G to 2G System...........................................................32-7 32.4.2 Inter-MSC Load-Based Handover From 3G to 2G System...........................................................32-8 32.4.3 Intra-MSC Load-Based Handover From 2G to 3G System...........................................................32-9 32.4.4 Inter-MSC Load-Based Handover From 2G to 3G System...........................................................32-9 32.4.5 Intra-MSC Load-Based Handover in 2G System ........................................................................32-10 32.4.6 Inter-MSC Load-Based Handover in 2G System ........................................................................ 32-11 32.5 Data Configuration ................................................................................................................................32-12 32.5.1 Overview .....................................................................................................................................32-12 32.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................32-12 32.5.3 Data Configuration at the UMG8900 Side ..................................................................................32-13 32.5.4 Data Configuration Example.......................................................................................................32-13 32.5.5 Data Tables Related to Load-Based Handover ............................................................................32-14 32.6 Service Management .............................................................................................................................32-15 32.6.1 Operations by Carriers.................................................................................................................32-15 32.6.2 Operations by Subscribers...........................................................................................................32-16 32.7 Charging and CDR ................................................................................................................................32-16 32.8 Performance Measurement ....................................................................................................................32-16 32.9 Service Interaction.................................................................................................................................32-16 32.10 Reference.............................................................................................................................................32-16 32.10.1 Specifications ............................................................................................................................32-16 32.10.2 Acronyms and Abbreviations ....................................................................................................32-17 32.11 FAQ .....................................................................................................................................................32-17

33 Union Subscriber Trace ........................................................................................................33-1


33.1 Service Description .................................................................................................................................33-2 33.1.1 Function Code ...............................................................................................................................33-2 33.1.2 Definition ......................................................................................................................................33-2 33.1.3 Benefits .........................................................................................................................................33-3 33.1.4 Application Scenario .....................................................................................................................33-3 33.1.5 Application Limitation ..................................................................................................................33-3 33.1.6 Others ............................................................................................................................................33-3 33.2 Availability ..............................................................................................................................................33-4

xxiv

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

33.2.1 Requirements for NEs ...................................................................................................................33-4 33.2.2 Requirements for License..............................................................................................................33-4 33.2.3 Applicable Version ........................................................................................................................33-4 33.3 Working Principle....................................................................................................................................33-4 33.3.1 Functions of NEs...........................................................................................................................33-4 33.3.2 Internal Processing of the System .................................................................................................33-5 33.3.3 External Interface ..........................................................................................................................33-5 33.4 Service Flow............................................................................................................................................33-5 33.4.1 Trace Flow of Activation Message Received from the HLR During Location Update/Data Recovery ..................................................................................................................................................................33-5 33.4.2 Trace Flow of Activation Message Sent by the HLR ....................................................................33-6 33.4.3 Trace Flow of Deactivation Trace Sent by the HLR......................................................................33-7 33.4.4 Trace Flow of the Initiation Call ...................................................................................................33-8 33.4.5 Trace Flow of the Termination Call...............................................................................................33-8 33.4.6 Trace Flow of the Originated Short Message ................................................................................33-9 33.4.7 Trace Flow of the Terminated Short Message ...............................................................................33-9 33.4.8 Trace Flow of Power-On/Location Update..................................................................................33-10 33.4.9 Trace Flow of Power-Off and Trace File Generated....................................................................33-10 33.5 Data Configuration ................................................................................................................................ 33-11 33.5.1 Overview ..................................................................................................................................... 33-11 33.5.2 Data Configuration at the MSOFTX3000 Side ........................................................................... 33-11 33.5.3 Data Configuration at the HLR Side ........................................................................................... 33-11 33.5.4 Data Configuration Examples ..................................................................................................... 33-11 33.5.5 Related Tables .............................................................................................................................33-12 33.6 Service Management .............................................................................................................................33-12 33.6.1 Operation by Carriers ..................................................................................................................33-12 33.6.2 Operations by Subscribers...........................................................................................................33-13 33.7 Charging and CDR ................................................................................................................................33-13 33.8 Performance Management.....................................................................................................................33-13 33.9 Service Interaction.................................................................................................................................33-14 33.10 Reference.............................................................................................................................................33-14 33.10.1 Specification..............................................................................................................................33-14 33.10.2 Glossary, Acronyms and Abbreviations.....................................................................................33-14

34 Service Restriction by Cell ...................................................................................................34-1


34.1 Service Description .................................................................................................................................34-2 34.1.1 Function Code ...............................................................................................................................34-2 34.1.2 Definition ......................................................................................................................................34-2 34.1.3 System Specifications....................................................................................................................34-3 34.1.4 Benefits .........................................................................................................................................34-3 34.1.5 Application Scenario .....................................................................................................................34-3 34.1.6 Application Limitations.................................................................................................................34-3 34.2 Availability ..............................................................................................................................................34-4

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxv

Contents

HUAWEI MSOFTX3000 Feature Description 34.2.1 Requirement for NEs.....................................................................................................................34-4 34.2.2 Requirement for License ...............................................................................................................34-4 34.2.3 Applicable Version ........................................................................................................................34-4 34.2.4 Others ............................................................................................................................................34-4

34.3 Working Principle....................................................................................................................................34-4 34.3.1 Functions of the NEs .....................................................................................................................34-4 34.3.2 Service Implementation.................................................................................................................34-4 34.3.3 External Interfaces.........................................................................................................................34-5 34.4 Service Flow............................................................................................................................................34-5 34.4.1 Location Update Message Flow ....................................................................................................34-6 34.4.2 Originated Service Message Flow.................................................................................................34-6 34.4.3 Terminated Service Message Flow................................................................................................34-8 34.5 Data Configuration ..................................................................................................................................34-9 34.5.1 Overview .......................................................................................................................................34-9 34.5.2 Data Configuration at the MSOFTX3000 Side .............................................................................34-9 34.5.3 Data Configuration Examples .....................................................................................................34-17 34.6 Service Management .............................................................................................................................34-24 34.7 Charging and CDR ................................................................................................................................34-24 34.8 Performance Measurement ....................................................................................................................34-24 34.8.1 Index Description ........................................................................................................................34-24 34.8.2 Implementation Principle ............................................................................................................34-24 34.9 Service Interaction.................................................................................................................................34-24 34.9.1 Enhanced Roaming Restriction and ZC Roaming Restriction ....................................................34-25 34.10 Reference.............................................................................................................................................34-25 34.10.1 Specifications ............................................................................................................................34-25 34.10.2 Acronyms and Abbreviations ....................................................................................................34-25 34.11 FAQ .....................................................................................................................................................34-26

35 Dialing Test on Designated TDM Circuit.........................................................................35-1


35.1 Service Description .................................................................................................................................35-2 35.1.1 Function Code ...............................................................................................................................35-2 35.1.2 Definition ......................................................................................................................................35-2 35.1.3 Benefits .........................................................................................................................................35-3 35.1.4 Application Scenario .....................................................................................................................35-3 35.1.5 Application Limitations.................................................................................................................35-3 35.2 Availability ..............................................................................................................................................35-3 35.2.1 Requirements for NEs ...................................................................................................................35-3 35.2.2 Requirements for License..............................................................................................................35-3 35.2.3 Applicable Versions.......................................................................................................................35-3 35.3 Working Principle....................................................................................................................................35-4 35.3.1 Functions of NEs...........................................................................................................................35-4 35.3.2 Internal Processing of the System .................................................................................................35-4

xxvi

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

35.4 Service Flow............................................................................................................................................35-5 35.4.1 Dialing Test on the Designated TDM Circuit for the Trunk Outgoing Call ..................................35-5 35.4.2 Dialing Test on the Designated TDM Circuit for the Intra-Office Call .........................................35-7 35.4.3 Dialing Test on the Designated TDM Circuit for the Incoming Call.............................................35-9 35.5 Data Configuration ..................................................................................................................................35-9 35.5.1 Configuration Description.............................................................................................................35-9 35.5.2 Data Configuration at the MSOFTX3000 Side .............................................................................35-9 35.5.3 Data Configuration at the UMG8900 Side ..................................................................................35-10 35.5.4 Data Configuration Examples .....................................................................................................35-10 35.6 Charging and CDR ................................................................................................................................ 35-11 35.7 Performance Measurement ....................................................................................................................35-12 35.8 Service Interaction.................................................................................................................................35-12 35.9 Reference...............................................................................................................................................35-12 35.9.1 Specifications ..............................................................................................................................35-12 35.9.2 Acronyms and Abbreviations ......................................................................................................35-12 35.10 FAQ .....................................................................................................................................................35-12

36 IN Service Performance Measurement Enhancement ....................................................36-1


36.1 Service Description .................................................................................................................................36-3 36.1.1 Function Code ...............................................................................................................................36-3 36.1.2 Definition ......................................................................................................................................36-3 36.1.3 System Specifications....................................................................................................................36-3 36.1.4 Denefits .........................................................................................................................................36-4 36.1.5 Application Scenrio .......................................................................................................................36-4 36.1.6 Application Limitations.................................................................................................................36-4 36.2 Availability ..............................................................................................................................................36-4 36.2.1 Requirements for NEs ...................................................................................................................36-4 36.2.2 Requirement for License ...............................................................................................................36-5 36.2.3 Applicable Versions.......................................................................................................................36-5 36.2.4 Others ............................................................................................................................................36-5 36.3 Working Principle....................................................................................................................................36-5 36.3.1 Functions of NEs...........................................................................................................................36-5 36.3.2 Internal Processing of the System .................................................................................................36-5 36.3.3 External Interfaces.........................................................................................................................36-8 36.4 Service Flow............................................................................................................................................36-8 36.4.1 Traffic for WIN User Calling Fixed User......................................................................................36-8 36.4.2 Traffic for WIN User Calling Other MSC User ............................................................................36-9 36.4.3 Traffic for Fixed User Calling WIN User.................................................................................... 36-11 36.4.4 Traffic for Other MSC User Calling WIN User ..........................................................................36-12 36.5 Data Configuration ................................................................................................................................36-13 36.5.1 Description ..................................................................................................................................36-13 36.5.2 Data Configuration at the MSOFTX3000 Side ...........................................................................36-14

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxvii

Contents

HUAWEI MSOFTX3000 Feature Description 36.5.3 Data Configuration Examples .....................................................................................................36-14

36.6 Service Management .............................................................................................................................36-18 36.6.1 Operations by Carriers.................................................................................................................36-18 36.6.2 Operations by Subscribers...........................................................................................................36-18 36.7 Charging and CDR ................................................................................................................................36-18 36.8 Performance Measurement ....................................................................................................................36-19 36.8.1 Specification Descriprion ............................................................................................................36-19 36.8.2 Implementation Principle ............................................................................................................36-19 36.9 Service Interaction.................................................................................................................................36-20 36.10 Reference.............................................................................................................................................36-20 36.10.1 Specifications ............................................................................................................................36-20 36.10.2 Glossary, Acronyms, and Abbreviations....................................................................................36-20 36.11 FAQ .....................................................................................................................................................36-20

37 Automatic Device Detection ................................................................................................37-1


37.1 Service Description .................................................................................................................................37-2 37.1.1 Function Code ...............................................................................................................................37-2 37.1.2 Definition ......................................................................................................................................37-2 37.1.3 Standard Compliance ....................................................................................................................37-2 37.1.4 System Specifications....................................................................................................................37-2 37.1.5 Benefits .........................................................................................................................................37-2 37.1.6 Application Scenario .....................................................................................................................37-3 37.1.7 Application Limitations.................................................................................................................37-3 37.2 Availability ..............................................................................................................................................37-3 37.2.1 Requirements for NEs ...................................................................................................................37-3 37.2.2 Requirements for License..............................................................................................................37-3 37.2.3 Applicable Versions.......................................................................................................................37-3 37.2.4 Other..............................................................................................................................................37-3 37.3 Working Principle....................................................................................................................................37-4 37.3.1 Functions of the NEs .....................................................................................................................37-4 37.3.2 Internal Processing of the System .................................................................................................37-4 37.3.3 External Interfaces.........................................................................................................................37-5 37.4 Service Flow............................................................................................................................................37-5 37.5 Data Configuration ..................................................................................................................................37-7 37.5.1 Configuration Description.............................................................................................................37-7 37.5.2 Data Configuration at the MSOFTX3000 .....................................................................................37-7 37.5.3 Data Configuration Example.........................................................................................................37-8 37.5.4 Table Query Flow of ADD ............................................................................................................37-9 37.6 Service Management .............................................................................................................................37-10 37.6.1 Overview .....................................................................................................................................37-10 37.6.2 Operations by Carriers................................................................................................................. 37-11 37.6.3 Operations by Subscribers........................................................................................................... 37-11

xxviii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

37.7 Reference............................................................................................................................................... 37-11 37.7.1 Specifications .............................................................................................................................. 37-11 37.7.2 Acronyms and Abbreviations ...................................................................................................... 37-11 37.8 FAQ .......................................................................................................................................................37-12 37.8.1 Problem Description....................................................................................................................37-12 37.8.2 Cause of the Problem ..................................................................................................................37-12 37.8.3 Method ........................................................................................................................................37-12

38 Noise Suppression .................................................................................................................38-1


38.1 Service Description .................................................................................................................................38-2 38.1.1 Function Code ...............................................................................................................................38-2 38.1.2 Definition ......................................................................................................................................38-2 38.1.3 Standard Compliance ....................................................................................................................38-2 38.1.4 System Specifications....................................................................................................................38-3 38.1.5 Benefits .........................................................................................................................................38-3 38.1.6 Application Scenario .....................................................................................................................38-3 38.1.7 Application Limitations.................................................................................................................38-3 38.2 Availability ..............................................................................................................................................38-4 38.2.1 Requirements for NEs ...................................................................................................................38-4 38.2.2 Requirements for License..............................................................................................................38-4 38.2.3 Supporting Versions ......................................................................................................................38-4 38.2.4 Others ............................................................................................................................................38-4 38.3 Working Principle....................................................................................................................................38-4 38.3.1 Functions of NEs...........................................................................................................................38-4 38.3.2 Internal Processing ........................................................................................................................38-5 38.3.3 External Interfaces.........................................................................................................................38-5 38.4 Service Flow............................................................................................................................................38-5 38.5 Data Configuration ..................................................................................................................................38-6 38.5.1 Overview .......................................................................................................................................38-6 38.5.2 Configuration at the MSOFTX3000 Side......................................................................................38-7 38.5.3 Configuration on the UMG8900 Side ...........................................................................................38-7 38.5.4 Data Configuration Examples .......................................................................................................38-8 38.5.5 Table Query Flow of Noise Suppression Feature ..........................................................................38-9 38.5.6 Table Query Flow of Noise Suppression Feature ........................................................................38-10 38.6 Service Management ............................................................................................................................. 38-11 38.6.1 Operations by Carriers................................................................................................................. 38-11 38.6.2 Operations by Subscribers........................................................................................................... 38-11 38.7 Charging and CDR ................................................................................................................................ 38-11 38.8 Performance Measurement ....................................................................................................................38-12 38.9 Service Interaction.................................................................................................................................38-12 38.10 Reference.............................................................................................................................................38-12 38.10.1 Specifications ............................................................................................................................38-12

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxix

Contents

HUAWEI MSOFTX3000 Feature Description 38.10.2 Glossary, Acronyms and Abbreviations.....................................................................................38-12

38.11 FAQ .....................................................................................................................................................38-13

39 TDM Circuit Selection Based on Service Type................................................................39-1


39.1 Service Description .................................................................................................................................39-2 39.1.1 Function Code ...............................................................................................................................39-2 39.1.2 Definition ......................................................................................................................................39-2 39.1.3 Standard Compliance ....................................................................................................................39-2 39.1.4 System Specifications....................................................................................................................39-2 39.1.5 Benefits .........................................................................................................................................39-3 39.1.6 Application Scenario .....................................................................................................................39-3 39.2 Availability ..............................................................................................................................................39-3 39.2.1 Requirements for NEs ...................................................................................................................39-3 39.2.2 Requirements for License..............................................................................................................39-3 39.2.3 Supporting Versions ......................................................................................................................39-3 39.2.4 Others ............................................................................................................................................39-4 39.3 Working Principle....................................................................................................................................39-4 39.3.1 Functions of the NEs .....................................................................................................................39-4 39.3.2 External Interface ..........................................................................................................................39-5 39.4 Data Configuration ..................................................................................................................................39-5 39.4.1 Overview of Configuration ...........................................................................................................39-5 39.4.2 Data Configuration at the MSOFTX3000 Side .............................................................................39-5 39.4.3 Configuration Examples................................................................................................................39-6 39.4.4 Data Configuration at the UMG8900 Side ..................................................................................39-10 39.5 Service Management .............................................................................................................................39-10 39.6 Charging and CDR ................................................................................................................................39-10 39.7 Performance Measurement ....................................................................................................................39-10 39.8 Service Interaction.................................................................................................................................39-10 39.9 FAQ .......................................................................................................................................................39-10

40 BICC and ISUP Route Allowed for the Same Office Direction....................................40-1
40.1 Service Description .................................................................................................................................40-2 40.1.1 Function Code ...............................................................................................................................40-2 40.1.2 Definition ......................................................................................................................................40-2 40.1.3 Standard Compliance ....................................................................................................................40-3 40.1.4 System Specifications....................................................................................................................40-3 40.1.5 Benefits .........................................................................................................................................40-4 40.1.6 Application Scenario .....................................................................................................................40-4 40.1.7 Application Limitations.................................................................................................................40-5 40.2 Availability ..............................................................................................................................................40-6 40.2.1 Requirements for NEs ...................................................................................................................40-6 40.2.2 Requirements for License..............................................................................................................40-6 40.2.3 Supporting Versions ......................................................................................................................40-6

xxx

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

40.2.4 Others ............................................................................................................................................40-6 40.3 Working Principle....................................................................................................................................40-6 40.3.1 Functions of the NEs .....................................................................................................................40-6 40.3.2 Internal Processing of the System .................................................................................................40-6 40.3.3 External Interfaces.........................................................................................................................40-8 40.4 Service Flow............................................................................................................................................40-8 40.5 Data Configuration ..................................................................................................................................40-8 40.5.1 Overview .......................................................................................................................................40-8 40.5.2 Data Configuration at the MSOFTX3000 Side .............................................................................40-8 40.5.3 Data Configuration at the UMG8900 Side .................................................................................. 40-11 40.5.4 Data Configuration Examples .....................................................................................................40-12 40.6 Service Management .............................................................................................................................40-16 40.6.1 Operations by Carriers.................................................................................................................40-16 40.6.2 Operations by Mobile Subscribers ..............................................................................................40-16 40.7 Charging and CDR ................................................................................................................................40-16 40.8 Performance Measurement ....................................................................................................................40-16 40.9 Service Interaction.................................................................................................................................40-16 40.10 References ...........................................................................................................................................40-17 40.10.1 Standards and Specifications.....................................................................................................40-17 40.10.2 Acronyms and Abbreviations ....................................................................................................40-17 40.11 FAQ .....................................................................................................................................................40-17

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

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxxi

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

xxxii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Figures

Figure 3-4 CFU 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 .....................................................3-9 Figure 3-6 UDUB service flow for a call forwarded to a PSTN subscriber ...................................................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-12 Figure 3-9 CFNRy service flow for a call forwarded to a PSTN subscriber ..................................................3-13 Figure 3-10 CFNRy service flow for a call forwarded to a mobile subscriber. ..............................................3-14 Figure 3-11 CFNRc service flow for call forwarded to a PSTN subscriber ...................................................3-16 Figure 3-12 CFNRc service flow for the mobile forwarded-to subscriber .....................................................3-17 Figure 3-13 Charging of the call forwarding services ....................................................................................3-22 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 Figure 5-1 Service flow when a subscriber accepts a waiting call ...................................................................5-7 Figure 5-2 Service flow when a subscriber rejects a waiting call.....................................................................5-9 Figure 5-3 Service flow for holding and retrieving a call...............................................................................5-10 Figure 5-4 Service flow for alternating from the A-B call to the A-C call ..................................................... 5-11 Figure 6-1 Setting up the MPTY call................................................................................................................6-6 Figure 6-2 Create a personal communication ...................................................................................................6-7 Figure 6-3 Add a remote subscriber..................................................................................................................6-7 Figure 6-4 Disconnect the remote subscriber by main controller .....................................................................6-8 Figure 6-5 Disconnect the remote subscriber by main controller .....................................................................6-9 Figure 7-1 Check flow of the VLR for the BAOC service ...............................................................................7-5 Figure 7-2 Check flow of the VLR for the BOIC service.................................................................................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-8 Figure 7-5 Check flow of the HLR for the BIC-ROAM service ......................................................................7-9 Figure 7-6 BO service flow ............................................................................................................................7-10 Figure 7-7 BI service flow.............................................................................................................................. 7-11 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 Figure 10-1 Flow of UMTS authentication ....................................................................................................10-4

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxxiii

Figures

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

xxxiv

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Figures

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-7 Figure 18-4 Triggering point of SMS notification for call failure in the VMSC ............................................18-8 Figure 18-5 Processing flow after SMS notification for call failure is triggered............................................18-9 Figure 19-1 Synchronization relationship between the NTP server, BAM server, and the host.....................19-4 Figure 19-2 Time icon of Windows2000 operating system ............................................................................19-5 Figure 19-3 Adjusting clock for daylight saving changes...............................................................................19-6 Figure 20-1 Patch operation flow ...................................................................................................................20-5 Figure 21-1 Sketch of the active and the standby areas..................................................................................21-4 Figure 21-2 Illustration of state transition during configuration rollback.......................................................21-5 Figure 21-3 State transition of data in the standby area..................................................................................21-7 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-10 Figure 22-3 CAP message flow of the simultaneous ringing with C answering the call first....................... 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-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...............................................................................23-7 Figure 23-3 Table query flow in the IMSI-based announcement service .....................................................23-12 Figure 24-1 Internal processing of IP over E1 processing in the MSOFTX3000 ...........................................24-5 Figure 24-2 IP over E1 bearer adopted inter-office MGWs............................................................................24-6 Figure 24-3 IP over E1 bearer adopted by intra-office MGWs.......................................................................24-7 Figure 24-4 Inter-office call flow of forward fast...........................................................................................24-8 Figure 24-5 Inter-office call flow of forward delay ........................................................................................24-9 Figure 24-6 Inter-office call flow of backward delay ...................................................................................24-10 Figure 24-7 Setup of intra-office medium cluster.........................................................................................24-10 Figure 24-8 Typical networking of IP over E1 .............................................................................................24-17 Figure 25-1 Networking of the IP QoS flow control granularity....................................................................25-6 Figure 25-2 IP QoS processing flow in inter-office office direction mode.....................................................25-9 Figure 25-3 IP QoS processing flow in inter-office gateway pair mode for inter-office calls ......................25-10 Figure 25-4 IP QoS processing flow in gateway pair mode for intra-office calls......................................... 25-11 Figure 26-1 Internal processing of system when the sending of short message is allowed by the SCP .........26-5 Figure 26-2 Internal processing of system when the sending of short message is prohibited by the SCP .....26-6

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxxv

Figures

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

xxxvi

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Figures

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

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxxvii

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 .........................................................................................................................................................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 ........................................................................................................36-8 Figure 36-4 WIN user calling other MSC user without acquiring roaming number in the local office..........36-9 Figure 36-5 WIN user calling other MSC user with acquiring roaming number in the local office.............36-10 Figure 36-6 Fixed user calling WIN user ..................................................................................................... 36-11 Figure 36-7 Other MSC user calling WIN user ............................................................................................36-12 Figure 36-8 Special flow of the number regulation ......................................................................................36-13 Figure 37-1 Flow of the ADD service ............................................................................................................37-4 Figure 37-2 ADD message flow .....................................................................................................................37-5 Figure 37-3 Table query flow of the ADD service........................................................................................37-10 Figure 38-1 Networking of the system internal processing ............................................................................38-5 Figure 38-2 Service flow of the noise suppression feature.............................................................................38-6 Figure 38-3 Table query flow of noise suppression service (Support noise removing benefit local end).....38-10 Figure 38-4 Table query flow of noise suppression service (Support noise removing benefit peer end) ..... 38-11 Figure 39-1 TDM circuit selection based on the service type ........................................................................39-4 Figure 40-1 Current networking of China Mobile..........................................................................................40-3 Figure 40-2 Scenario 1 ...................................................................................................................................40-4 Figure 40-3 Scenario 2 ...................................................................................................................................40-5 Figure 40-4 Scenario 3 ...................................................................................................................................40-5

xxxviii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 1-1 Function names and function codes in the speech service ................................................................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 ..................................................................................................1-4 Table 1-5 Versions of the products that support the speech service ..................................................................1-5 Table 1-6 Differences between early assignment and late assignment ...........................................................1-20 Table 1-7 Configuration steps .........................................................................................................................1-21 Table 1-8 Interaction between the emergency call function and other services ..............................................1-26 Table 2-1 NEs required to realize the SMS.......................................................................................................2-4 Table 2-2 HUAWEI CS product versions that support the SMS.......................................................................2-4 Table 2-3 Functions of NEs in the transmission of SMs...................................................................................2-5 Table 2-4 Functions of NEs in the transmission of SMs...................................................................................2-6 Table 2-5 Interaction between the SMS and other services ............................................................................2-16 Table 3-1 Function code....................................................................................................................................3-2 Table 3-2 Definitions of the call forwarding services .......................................................................................3-2 Table 3-3 Benefits of the call forwarding services............................................................................................3-3 Table 3-4 Related NEs ......................................................................................................................................3-3 Table 3-5 Applicable versions...........................................................................................................................3-4 Table 3-6 Operation modes of the call forwarding service .............................................................................3-18 Table 3-7 CFU service operations...................................................................................................................3-19 Table 3-8 CFB service operations...................................................................................................................3-20 Table 3-9 CFNRy service operations ..............................................................................................................3-20 Table 3-10 CFNRc service operation..............................................................................................................3-20 Table 3-11 Operations applicable to all the call forwarding services..............................................................3-21 Table 3-12 All the CCF services .....................................................................................................................3-21 Table 3-13 CDR creation principles................................................................................................................3-23

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xxxix

Tables

HUAWEI MSOFTX3000 Feature Description Table 3-14 Interaction between the CFU and other services...........................................................................3-24 Table 3-15 Interaction Between CUG and Call Forwarding...........................................................................3-27 Table 3-16 Service interaction between the CFB and other services ..............................................................3-28 Table 3-17 Interaction between CFNRy and other services ............................................................................3-30 Table 3-18 Interaction between CFNRc and other services ............................................................................3-33 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 Table 5-1 Name and code of the function .........................................................................................................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 ....................................................................................5-3 Table 5-4 NEs required by the call completion supplementary services...........................................................5-3 Table 5-5 Applicable versions of Huawei wireless core network products.......................................................5-4 Table 5-6 Related software parameters ...........................................................................................................5-13 Table 5-7 Operation modes of the call completion supplementary services ...................................................5-14 Table 5-8 Operations performed by mobile subscribers .................................................................................5-15 Table 5-9 Interactions between the CW service and other services ................................................................5-18 Table 5-10 Interactions between the CH service and other services ...............................................................5-19 Table 6-1 Network elements involved in MPTY features.................................................................................6-3 Table 6-2 Applicable versions of the MPTY.....................................................................................................6-3 Table 6-3 Operation method for MPTY service.............................................................................................. 6-11 Table 6-4 MPTY service operation (For mobile subscriber)........................................................................... 6-11 Table 6-5 Interactions between the MPTY and the other services ..................................................................6-13 Table 7-1 Name and code of the function .........................................................................................................7-2 Table 7-2 NEs required by the call barring services .........................................................................................7-3 Table 7-3 Applicable versions of Huawei wireless core network products.......................................................7-4

xl

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Tables

Table 7-4 Operation modes of the call barring supplementary services .........................................................7-13 Table 7-5 Operations performed by mobile subscribers .................................................................................7-13 Table 7-6 Interactions between the BAOC service and other services ...........................................................7-15 Table 7-7 Interactions between the BOIC service and other services .............................................................7-16 Table 7-8 Interactions between the BOIC-exHC service and other services ..................................................7-17 Table 7-9 Interactions between the BAIC service and other services .............................................................7-18 Table 7-10 Interactions between the BIC-ROAM service and other services.................................................7-19 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 Table 9-1 Name and function code of the ODB services ..................................................................................9-2 Table 9-2 NEs related with the ODB services ..................................................................................................9-4 Table 9-3 Versions that support the ODB services............................................................................................9-5 Table 9-4 Service interaction between ODB and other services .......................................................................9-7 Table 10-1 Function names and functions codes in the authentication and encryption ..................................10-2 Table 10-2 Benefits for carriers and mobile subscribers.................................................................................10-2 Table 10-3 NEs involved in the authentication and encryption ......................................................................10-3 Table 10-4 Versions of the products that support the authentication and encryption......................................10-3 Table 11-1 Name and code of the function ..................................................................................................... 11-2 Table 11-2 Beneficiaries and description of the benefits ................................................................................ 11-4 Table 11-3 NEs required by the enhanced MSRN allocation service ............................................................. 11-4 Table 11-4 Applicable versions of HUAWEI wireless core network products ............................................... 11-5 Table 12-1 Requirement for NEs ....................................................................................................................12-3 Table 12-2 Applicable versions.......................................................................................................................12-3 Table 13-1 Name and function code of the IN service triggering. ..................................................................13-2 Table 13-2 Processing modes of the IN services.............................................................................................13-2 Table 13-3 NEs related to the IN service triggering........................................................................................13-3

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xli

Tables

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

xlii

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Tables

Table 19-4 Alarms related to summer time .....................................................................................................19-5 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 Table 21-1 Feature name and function code ...................................................................................................21-2 Table 21-2 Benefits of the configuration rollback feature ..............................................................................21-3 Table 21-3 Applicable versions that support the configuration rollback feature.............................................21-3 Table 21-4 Tables that support configuration rollback....................................................................................21-9 Table 21-5 List of configuration rollback commands ...................................................................................21-10 Table 21-6 Synchronization and forcible synchronization commands..........................................................21-14 Table 21-7 Activation and forcible activation commands.............................................................................21-17 Table 21-8 Rollback and forcible rollback commands..................................................................................21-19 Table 21-9 Cancellation and confirmation commands..................................................................................21-21 Table 21-10 Query commands ......................................................................................................................21-24 Table 22-1 Function name and function code in the CAMEL4 service ..........................................................22-2 Table 22-2 Added call functions in the CAMEL4 service ..............................................................................22-2 Table 22-3 Benefits for carriers and mobile subscribers.................................................................................22-4 Table 22-4 NEs required to implement the CAMEL4 feature ........................................................................22-5 Table 22-5 Versions of the Huawei UMTS products that support the CAMEL4 feature................................22-5 Table 22-6 New CSA Measurement..............................................................................................................22-18 Table 22-7 Modified WIN event measurement.............................................................................................22-18 Table 22-8 List of supplementary services supported in mode A .................................................................22-20 Table 23-1 Name and code of the function .....................................................................................................23-3 Table 23-2 System specifications....................................................................................................................23-3 Table 23-3 NEs required to implement the IMSI-based announcement service .............................................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........................................................................23-8 Table 23-6 Related tables in the IMSI-based announcement service............................................................23-10 Table 24-1 Function code about this service...................................................................................................24-2 Table 24-2 Benefits of this service to carriers and mobile subscribers ...........................................................24-2 Table 24-3 NEs related with IP over E1..........................................................................................................24-4 Table 24-4 Product versions that support IP over E1......................................................................................24-4 Table 25-1 NEs that are involved in this IP QoS flow control........................................................................25-3

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xliii

Tables

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

xliv

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Tables

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

Issue 02 (2007-02-15)

Huawei Technologies Proprietary

xlv

Tables

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

xlvi

Huawei Technologies Proprietary

Issue 02 (2007-02-15)

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
About This Document.....................................................................................................................1

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

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). This manual describes the definition, realization principle, service flow, data configuration and service interaction of each feature. The manual introduces the features of V100R005C10 of the MSOFTX3000. In this way, audiences can use the MSOFTX3000 more easily.

Related Versions
The following table lists the product versions related to this document. 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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

About This Document

HUAWEI MSOFTX3000 Feature Description

Chapter 1 Speech Service

Content This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the speech services, such as phone service, emergency call, and special service emergency call. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the short message service. This chapter describes the implementation principle, service flow, and the interception with other services of the call forwarding supplementary service. This chapter describes the implementation principle, service flow, and the interception with other services of the line identification service. This chapter describes the implementation method and principle of the call completion supplementary service. This chapter describes the implementation method of the multiparty service. This chapter describes the implementation principle, service flow, and the interception with other services of the call barring service. This chapter describes the implementation method and principle of the explicit call transfer service. This chapter describes the feature of the OBD service. This chapter describes the implementation principle, service flow, data configuration and service management of the authentication feature. This chapter describes enhanced MSRN allocation methods supported by the system. This chapter describes the implementation principle, service flow, data configuration and service management of the call forwarding early and late assignment feature. This chapter describes the implementation principle, service flow, charging and CDR, and the interception with other services of the IN service triggering feature. This chapter describes the mobile number portability feature. This chapter describes the service flow, and data configuration of the IP fax feature.

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

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

About This Document

Chapter 16 License Feature

Content This chapter describes the implementation principle of the License feature, the O&M of the License files, the control items of the License, and the cautions of using the License. This chapter describes the implementation principle and data configuration of the NE user dynamic monitoring feature. This chapter describes the implementation principle, service flow, and the interception with other services of the SMS notification for call failure feature. This chapter describes the implementation principle of the summer time feature of wireless time zone, and its impacts on the charging and CDR. This chapter describes the management feature of the network management system to the MSOFTX3000 software version. This chapter describes the method of rolling back the data configuration of the system, to ensure the correctness of the data configuration, the time of the rollback, and the stability and safety of the system operation. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the CAMEL4 service. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the IMSI-based announcement. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the IP over E1. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the IP QoS flow control. 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, service flow, data configuration service management and the interception with other services of the UP header redundancy data service. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the VDB dynamic data backup.

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

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, service flow, data configuration service management and the interception with other services of the multi-area network role-based and domain-based management feature. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the alarm for malicious short messages. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the call simulation. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the load-based handover. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the union subscriber trace. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the service restriction by cell. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the dialing test on designated TDM circuit. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the IN service performance measurement enhancement. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the automatic device detection. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the noise suppression. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the TDM circuit selection based on service type. This chapter describes the implementation principle, service flow, data configuration service management and the interception with other services of the BICC and ISUP route allowed for the same office direction.

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

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

About This Document

Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows. Symbol Description Indicates a hazard with a high level of risk that, if not avoided, will result in death or serious injury. Indicates a hazard with a medium or low level of risk which, if not avoided, could result in minor or moderate injury. Indicates a potentially hazardous situation that, if not avoided, could cause equipment damage, data loss, and performance degradation, or unexpected results. Indicates a tip that may help you solve a problem or save time. Provides additional information to emphasize or supplement important points of the main text.

General Conventions
Convention Times New Roman Boldface Italic Courier New Description Normal paragraphs are in Times New Roman. Names of files, directories, folders, and users are in boldface. For example, log in as user root. Book titles are in italics. Terminal display is in Courier New.

Command Conventions
Convention Boldface Italic [] { x | y | ... } [ x | y | ... ] Description The keywords of a command line are in boldface. Command arguments are in italics. Items (keywords or arguments) in square brackets [ ] are optional. Alternative items are grouped in braces and separated by vertical bars. One is selected. Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

About This Document

HUAWEI MSOFTX3000 Feature Description

Convention { x | y | ... } *

Description Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

GUI Conventions
Convention Boldface > Description Buttons, menus, parameters, tabs, windows, and dialog titles are in boldface. For example, click OK. Multi-level menus are in boldface and separated by the ">" signs. For example, choose File > Create > Folder.

Keyboard Operation
Format Key Key 1+Key 2 Description Press the key. For example, press Enter and press Tab. Press the keys concurrently. For example, pressing Ctrl+Alt+A means the three keys should be pressed concurrently. Press the keys in turn. For example, pressing Alt, A means the two keys should be pressed in turn.

Key 1, Key 2

Mouse Operation
Action Click Double-click Drag Description Select and release the primary mouse button without moving the pointer. Press the primary mouse button twice continuously and quickly without moving the pointer. Press and hold the primary mouse button and move the pointer to a certain position.

Update History
Updates between document versions are cumulative. Therefore, the latest document version contains all updates made to previous versions.

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

About This Document

Updates in Issue 02 (2007-6-10)


Second archive. The updated contents are as follows: The feature description of PCR is added.

Updates in Issue 01 (2007-2-15)


First release.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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 1.9.2 Acronyms and Abbreviations .............................................................................................................1-26

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

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-9 Figure 1-3 Flow of the call from a mobile subscriber to a fixed line subscriber (2) ........................................1-10 Figure 1-4 Flow of the call from a fixed line subscriber to a mobile subscriber ..............................................1-13 Figure 1-5 Networking model of a call from a mobile subscriber to another mobile subscriber .....................1-15 Figure 1-6 Flow of the call from a mobile subscriber to another mobile subscriber (1) ..................................1-16 Figure 1-7 Flow of the call from a mobile subscriber to another mobile subscriber (2) ..................................1-17 Figure 1-8 Flow of the call from a mobile subscriber to another mobile subscriber (3) ..................................1-18 Figure 1-9 Process of generating CDRs when the mobile caller and callee are under the same VMSC ..........1-23 Figure 1-10 Process of generating CDRs when the mobile caller and callee are under different VMSCs.......1-23 Figure 1-11 Process of generating CDRs when a mobile subscriber calls a fixed line subscriber ...................1-23 Figure 1-12 Process of generating CDRs when a fixed line subscriber calls a mobile subscriber ...................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)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 1-1 Function names and function codes in the speech service..................................................................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 ....................................................................................................1-4 Table 1-5 Versions of the products that support the speech service....................................................................1-5 Table 1-6 Differences between early assignment and late assignment .............................................................1-20 Table 1-7 Configuration steps...........................................................................................................................1-21 Table 1-8 Interaction between the emergency call function and other services................................................1-26

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

1 Speech Service

1
About This Chapter
The following table lists the contents of this chapter. Section 1.1 Service Description 1.2 Availability 1.3 Working Principle 1.4 Service Flow 1.5 Data Configuration 1.6 Service Management 1.7 Charging and CDR 1.8 Service Interaction 1.9 Reference Describes

Speech Service

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

1-1

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

1.1 Service Description


1.1.1 Function Code
Table 1-1 lists the mapping between function names and function codes in the speech service. 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.1.2 Definition
The speech service is the elementary feature of a telecom network. The service consists of the functions such as telephony, emergency call, and emergency call for special service. Table 1-2 lists the definitions of these functions. 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, ISDN and PLMN over telephones. When a mobile subscriber chooses the type of an emergency call on the menu of an MS/UE or dials 112, the call is connected to a record notification device. Then the device instructs the subscriber how to call the emergency center. The subscriber can make an emergency call without a SIM/USIM card. Compared with the telephony function, the processing of the emergency call does not include authentication and specific routing requirements. An emergency call is of higher priority than an ordinary call.

Emergency call

1-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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 call is connected to a corresponding special service center that is nearest to the base station. The special service center consists of the fire alarm center, bandit alarm center, first-aid center and traffic center. Such kind of call can generate alarms. Carriers can decide whether to charge the subscriber.
NOTE The difference between the emergency call for special service function and the emergency call function is that: When a CM service is required, the emergency call for a special service is considered as an ordinary call. The MSC processes the number as a special service number after analyzing the number. While for the emergency call function, there is a parameter indicating that this is an emergency call.

Note PSTN = public switched telephone network; ISDN = integrated services digital network; PLMN = public land mobile network; SIM = subscriber identity module; 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), depending on the role of a mobile subscriber in a call.

MOC
If a mobile subscriber makes a call, this call is an MOC. In an MOC, the MSC server/visitor location register (VLR) and media gateway (MGW) perform the following functions: Security control This step is optional. If you do not select it, 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, the call is an MTC. In the universal mobile telecommunications system (UMTS), all network elements (NEs) cooperate with each other to route the call to the mobile subscriber. During the setup of an MTC, the designated MSC server queries the location information of the callee in the home location register (HLR) to which the callee belongs, because only the HLR stores such information. If the caller is also a mobile subscriber, the MSC server/VLR to which the caller belongs initiates the query. If the caller is a fixed line subscriber, the gateway mobile switching center (GMSC) server initiates the query.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-3

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

1.1.3 Benefits
Table 1-3 lists the benefits for carriers and mobile subscribers. Table 1-3 Benefits for carriers and mobile subscribers Beneficiary Carriers Mobile subscribers Description The speech service increases the income of carriers. The speech service enables mobile subscribers to freely move around the PLMN, and make and receive calls in any place at any time. The service also enables mobile subscribers to make emergency calls without SIM/USIM cards.

1.2 Availability
1.2.1 Requirements for NEs
The speech service requires the cooperation of the user equipment (UE)/mobile station (MS), NodeB/base transceiver station (BTS), radio network controller (RNC)/base station controller (BSC), and core network (CN). For details, see Table 1-4. 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.2.2 Requirements for License


No License is required to obtain the speech service, because the service is the elementary feature of the HUAWEI wireless core network.

1.2.3 Applicable Versions


Table 1-5 lists the versions of the HUAWEI circuited switched (CS) products that support the speech service.

1-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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


The NEs in the PLMN cooperate with each other to implement MOCs or MTCs. MOCs and MTCs enable mobile subscribers to freely move around the global system for mobile communications (GSM)/UMTS, and make and receive calls in any place at any time.

1.3.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). Based on the Service request, 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, based on the Service request. This means that the MSC server/VLR performs authentication, encryption/decryption, and/or temporary mobile subscriber identity (TMSI) reassignment. This function, however, can also not be enabled. Authentication The authentication function defines whether a mobile subscriber is authorized to access the PLMN. The function prevents invalid subscribers from using the services that the network provides. In the GSM and UMTS, the MS/UE, VLR/serving GPRS support node (SGSN) and HLR/authentication center (AuC) cooperate with each other to implement authentication. The MS and AuC calculate authentication parameters respectively. Then the VLR/SGSN compares the two results, to verify the validity of the MS/UE. In the UMTS, the UE can also verify the validity of the network.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-5

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

Encryption/Decryption In the UMTS, cipher key (CK) guarantees the confidentiality of access data. Secret signaling information and data information are encrypted. That is, logical channels are encrypted. Integrity key (IK) guarantees the integrity of signaling data. CK and IK are stored in the USIM and VLR/SGSN, and sent from the VLR/SGSN to the RNC with the security mode command. This helps to encrypt channels. The USIM can also send the CK and IK to the UE based on the requirements of the UE. That is, the UE stores a copy of the CK and IK. The VLR/SGSN must update the CK and IK at least once a day. In the GSM, encryption/decryption guarantees the information exchange through the wireless interface. Therefore, the MS and base station subsystem (BSS) are loaded with the same CK. TMSI reassignment The MSC server/VLR assigns a TMSI to a mobile subscriber periodically. This function is to prevent intruders from monitoring the signaling on wireless channels and identifying mobile subscribers. To guarantee the confidentiality, TMSI is reassigned at the right time. When a subscriber makes an emergency call without a SIM/USIM, international mobile station equipment Identity (IMEI), instead of TMSI or IMSI, is used to identify the subscriber. This means that the MSC server/VLR does not perform authentication, encryption/decryption and TMSI reassignment. Call setup between the calling MS/UE and the visited MSC server After the service acceptance message is received or the encryption is complete, the MS sends a Setup message to the visited MSC (VMSC) server. Then the VMSC server returns a Call Proceeding message to the calling MS/UE. Setup of a user panel bearer at the caller side The MSC server sends a Prepare Bearer request to the MGW, which assigns asynchronous transfer mode (ATM) resources dynamically. The MSC server then sends a Radio Access Bearer (RAB) Assignment message to the radio network subsystem originated (RNS-O). The RNS-O creates the ATM bearer resources at the access side together with the MGW through bearer establishment.

MOC Completion
The MSC/VLR checks subscription data and service compatibility. If the check is passed, the Connection request from the mobile subscriber is accepted. Then the originating MSC/VLR assigns service channels and occupies ground circuits, to continue the call.

1.3.2 MTC
An MTC is generated when a subscriber in the PSTN/ISDN/PLMN dials the MSISDN of a mobile 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. To obtain the route information, the VMSC/GMSC initiates a query by the steps as follows:

1-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

1 Speech Service

1. 2. 3. 4.

The MSC server begins to query after receiving an MSISDN. The MSC server queries the information of the callee in the HLR to which the callee belongs. The MSC translates the MSISDN and the results include the information of the HLR. The HLR requests the mobile station roaming number (MSRN) from the VLR. The HRL stores the current VLR number of the subscriber and dynamically updates the number, depending on the location of the subscriber. The HLR finds the VLR sequentially based on the mapping between the VLR and ISDN, and then requests the MSRN from the VLR. The VLR assigns a temporary MSRN to the callee. 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. The MSRN is released when the call reaches the VMSC/VLR. During the requirement for the MSRN, the VMSC/VLR transfers the MSRN to the GMSC through the HLR. During the query, the HLR/AuC and VMSC/VLR check subscription data and service compatibility.

5. 6.

7.

MTC Initiation and Completion


After the call is routed to the VMSC/VLR, 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. The MSC/VLR must, in the location area, check the cell where the mobile subscriber locates. The MSC/VLR checks the cell by paging. If the mobile station responds to the paging, it means the mobile subscriber is detected. The MTC initiation begins. This means that the system performs authentication, encryption, TMSI reassignment and equipment control, if required. 2. The MSC/VLR assigns service channels, occupies ground circuits and plays ringing tones. If the mobile subscriber answers the phone, the MTC is complete. Now the call is connected and the MSC begins to collect the call detail records (CDRs) for charging the subscriber.

1.3.3 MMC
A mobile-to-mobile call (MMC) is between two mobile subscribers. An MMC can be considered as an MOC plus an MTC. The MOC takes place first, followed by the MTC. The originating MSC/VLR initiates and completes the MOC. The service MSC/VLR initiates and completes the MTC. The originating MSC/VLR also queries the route to the MS/UE. If the two mobile subscribers register with the same MSC/VLR and all service channels are exchanged in the same MSC/VLR, the service MSC/VLR initiates and completes the MOC and MTC. The service MSC/VLR queries the information of the callee in the HLR.

1.4 Service Flow


The flows in this section are applied to the telephony function and emergency call function. The difference between the two functions is that there is no requirement for authenticating the access of the MS in an emergency call.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-7

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

1.4.1 MOC to Fixed Line Subscriber


Figure 1-1shows the networking model of the call from a mobile subscriber to a fixed line subscriber. 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)

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 UE sends a CM Service request to the VMSC server. 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)

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. 2. The network may initiate authentication and encryption. During the process, the network may obtain authentication set from the HLR/AuC. The MSC/VLR must send a Command ID message to the RNS on not identifying the TMSI of the UE, to obtain the IMSI of the UE. Step 3 takes place immediately after step 1 if there is no security management, which consists of authentication, encryption, TMSI reassignment and identity obtaining. After the service acceptance message is received or the encryption is complete, the UE sends a Setup message to the VMSC server. After receiving the Setup message, the VMSC server returns a Call Proceeding message to the calling UE. A user panel bearer begins to be created at the caller side. The VMSC server sends a Prepare Bearer request to the MGW. The MGW assigns ATM resources dynamically and sends a Prepare Bearer response containing TerminationId (T1). The MSC server then sends an RAB Assignment message to the RNS-O. The RNS-O creates the ATM bearer resources at the access side together with the MGW through bearer establishment. The GMSC server sends an Initial Address Message with Information (IAI) message to the PSTN. The PSTN returns an Address Complete Message (ACM) message after receiving the IAI message, and sends the ringback tone for the calling MSC. After the callee hangs up, the called UE sends an ANC message to the network side. The PSTN stops sending the ringback tone. The caller and callee begin to talk on the phone. If the caller hangs up first, the calling UE sends a Disconnect message to the GMSC server.

3. 4. 5.

6. 7. 8. 9.

10. The GMSC server sends a Clear Forward Signal (CLF) message to the PSTN and instructs it to disconnect the connection. 11. The PSTN returns a Release Guard Signal (RLG) message to the GMSC server after disconnecting the connection. 12. The GMSC server releases transaction resources by sending a Release message to the calling UE. 13. The calling UE sends a Release Complete response after receiving the Release message. 14. The GMSC server releases resources on the user panel after sending two Release Termination messages to the MGW. The two messages are sent through the Iu interface and ISDN User Part (ISUP) trunk respectively.

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

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

Security control for the callee service channel assignment, 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-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

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

1. 2.

The PSTN subscriber sends an IAI message containing the MSISDN of the callee to the GMSC server. The GMSC server determines the HLR that the callee belongs to by analyzing the MSISDN. The GMSC creates a signaling connection to the HLR and sends a request for routing. After receiving the request, the HLR checks the subscription data of the callee, and finds the VLR and MSC server to which the callee currently belongs. The HLR creates a signaling connection to the VLR based on the VLR number, and requests the MSRN of the callee. The VLR sends the MSRN of the callee to the HLR after finding the number. The HLR forwards the MSRN to the GMSC server. The GMSC server sends the IAI message to the VMSC server/VLR based on the MSRN. The VMSC server/VLR initiates paging to locate the callee after identifying the MSRN. After the VMSC server receives the paging response from the called UE, step 10 takes place immediately after step 8 if there is no requirement for authentication, encryption and TMSI reassignment.

3. 4. 5. 6. 7. 8. 9.

10. The network initiates authentication, encryption and TMSI reassignment. During the process, the network may obtain authentication set from the HLR/AuC. The MSC/VLR must send a Command ID message to the RNS on not identifying the TMSI of the UE, to obtain the IMSI of the UE. 11. The VMSC server sends a Setup message to the called UE. 12. The VMSC server creates the user panel bearer after receiving the Call Confirmed message from the called UE. 13. The MSC server sends a Prepare Bearer request to the MGW. The MGW assigns ATM resources dynamically and sends a Prepare Bearer response containing TerminationId. The MSC server then sends an RAB Assignment message to the RNS. The RNS creates the ATM bearer resources at the access side together with the MGW through bearer establishment. 14. A transmission control panel and user panel must be created during assignment. The RAN sends the RAB Assignment response only after receiving an acknowledgement message of the creation of the user panel. 15. The VMSC sever creates a user panel bearer at the caller side at the same time. The callee picks up the phone. 16. The MSC server sends an ACM message to the calling UE after receiving an Alerting message, and sends a Send Tone message to the MGW, instructing it to play the ringback tone. 17. The called UE sends a Connect message to the MSC server after the callee picks up the phone. The MSC server sends an ANC message to the calling UE after receiving the Connect message from the called UE. Meanwhile, the MSC server sends a Stop Tone message to the MGW, instructing it to stop playing the ringback tone. 18. The VMSC server forwards a Connect ACK message to the called UE after receiving the message from the calling UE. The caller and callee begin to talk on the phone. 19. If the callee hangs up first, the called UE sends a Disconnect message to the VMSC server. The VMSC server then sends a CLF message to the calling UE. 20. The calling UE sends an RLG message to the VMSC server after the caller hangs up. The VMSC server releases transaction resources by sending a Release message to the called UE. 21. The VMSC server sends an IU Release Command message on initiative, and begins to release the resources on the signaling panel.

1-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

1 Speech Service

22. The VMSC server releases resources on the user panel after sending two Release Termination messages to the MGW. The two messages are sent through the Iu interface and ISUP trunk respectively.

1.4.3 MMC
Figure 1-5 shows the networking model of the call from a mobile subscriber to another mobile subscriber. The two subscribers are both in the local office. 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, Figure 1-7and Figure 1-8 show the flow of the call from a mobile subscriber to another mobile subscriber.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-15

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)

HUAWEI MSOFTX3000 Feature Description

1 Speech Service

The MSC server is combined with the VLR. Therefore the B interface is an internal interface and the messages through the B interface are internal messages.

Flow at Caller Side (Early Assignment)


1. The UE sends a CM Service request to the MSC server. 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.

The network may initiate authentication and encryption. During the process, the network may obtain authentication set from the HLR/AuC. Step 3 takes places immediately after step 1 if there is no security management, which consists of authentication, encryption, TMSI reassignment and identity obtaining. After the service acceptance message is received or the encryption is complete, the UE sends a Setup message to the MSC server. After receiving the Setup message, the MSC server returns a Call Proceeding message to the calling UE. A user panel bearer begins to be created at the caller side. The MSC server sends a Prepare Bearer request to the MGW. The MGW assigns ATM resources dynamically and sends a Prepare Bearer response containing TerminationId (T1). The MSC server then sends an RAB Assignment message to the RNS-O. The RNS-O creates the ATM bearer resources at the access side together with the MGW through bearer establishment. This step takes place together with step 5. The MSC server queries route information in the HLR. The HLR requests the MSRN from the VLR. The VLR initiates paging immediately after the MSC server requests the incoming call data from the VLR.

3.

4.

5. 6. 7.

The difference between early assignment and late assignment lies in the chance of assigning traffic channels (TCHs). For details, see Table 1-6.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-19

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. Refers to assigning TCHs after the MSC receives the Call Confirmed message. Decreases call connection delay, thus improving the call connection ratio. Late Assignment Refers to assigning TCHs after the Alerting message.

Callee Side Advantages

Refers to assigning TCHs after the callee picks up the phone. Prevents TCHs from being occupied during ringing, thus improving the usage of TCHs.

Flow at Callee Side (Early Assignment)


1. 2. The MSC server receives a Paging response from the callee. The network may initiate authentication, encryption and TMSI reassignment. During the process, the network may obtain the authentication set from the HLR/AuC. If no authentication is required, step 3 takes place immediately after step 1. The MSC server sends a Setup message to the called UE. The MSC server creates user panel bearer after receiving a Call Confirmed message from the called UE. The creation process is similar to that of the ATM bearer at the caller side. A transmission control panel and user panel must be created during assignment. That is, Q.AAL2 must be created and ISUP must be initiated. The RAN sends the RAB Assignment response only after receiving an Establish Confirm message. The MSC server forwards an Alerting message to the calling UE after receiving the Alerting message from the called UE. The MSC server also sends a Send Tone message to the MGW and instructs it to play the ringback tone. The VMSC server forwards a Connect message to the calling UE after receiving the Connect message from the called UE. After receiving the Connect message, the MSC server sends a Stop Tone message to the MGW and instructs it to stop playing the ringback tone.

3. 4.

5. 6. 7.

8. 9.

10. The calling UE also sends a Connect ACK message to the MSC sever, which then forwards the message to the called UE. The caller and callee begin to talk on the phone.

Call Disconnection
1. 2. The caller hangs up first. At this moment, the calling UE sends a Disconnect message to the MSC server/VLR, which then forwards the message to the called UE. The called UE releases transaction resources by sending a Release message to the VMSC/GMSC, which then forwards the message to the calling UE and releases the transaction resources. The calling UE sends a Release Complete response after receiving the Release message.

3.

1-20

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

1 Speech Service

4. 5.

The VMSC/GMSC sends an IU Release Command message on initiative, and begins to release the resources on the signaling panel. The VMSC/GMSC sends a Release Termination message to the MGW and releases resources on the user panel.

1.5 Data Configuration


1.5.1 Telephony
The telephony is the elementary function of the UMTS. The data to be configured involves the number analysis data. For how to configure the data, see the following manuals: HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide U-SYS UMG8900 Configuration Guide

1.5.2 Emergency Call for Special Service


At the MSOFTX3000 side, you can configure the type and number of an emergency call for special service on the local maintenance terminal. After the configuration, the system can obtain the called number based on the type of the emergency call. Table 1-7 lists the configuration steps. 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. Run ADD ESRVCAT to add a type and number of an emergency call for a special service. Repeat step 2 to add more types and numbers.

The number of emergency call for special service is configured based on the local situation, when the speech service is opened. If a number has been configured, you do not have to configure it again.

1.5.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. The values of TARIFF are as follows: Charging indication No charging No indication

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-21

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

1.6 Service Management


1.6.1 For Carriers
Carriers can provide and cancel the speech service through the HLR client. You do not have to subscribe to the emergency call service at the HLR client. The service is opened automatically when you open an account. 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, see the manuals relevant to the HLR.

1.6.2 For Mobile Subscribers


There is nothing for mobile subscribers to do to manage the speech service.

1.7 Charging and CDR


1.7.1 Generation of CDR
In each call, the MSOFTX3000 collects call data and generates CDRs. The CDRs are the basis for carriers to charge mobile subscribers. The MSOFTX3000 collects call data, generates original CDRs, and stores the CDRs in the bill pool. 1. 2. 3. 4. The MSOFTX3000 transfers the original CDRs to the iGateway Bill (iGWB) in real time. The iGWB processes the original CDRs and generates final CDRs. The iGWB transfers the final CDRs to the charging center. The PLMN carriers generate telecom CDRs based on the final CDRs.

The iGWB collects, stores, sorts and transforms the original CDRs generated by the MSOFTX3000. It also provides an access interface for the charging center. This ensures that the correct CDRs are transferred to the charging center in time. In addition, the iGWB transforms original CDRs to final CDRs based on subscriber requirements.

1.7.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. A is the caller and B is the callee. Figure 1-9 shows the process of generating CDRs under this condition.

1-22

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. One is for the MOC and the charged subscriber is A. The other is for the MTC and the charged subscriber is B.

CDR for the Call Between Two Mobile Subscribers Under Different VMSCs
A and B are mobile subscribers under two VMSCs, both of which belong to the local network. A is the caller and B is the callee. Figure 1-10 shows the process of generating CDRs under this condition. 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. VMSC B generates a CDR for the MTC and the charged subscriber is B.

CDR for the Call from Mobile Subscriber to Fixed Line Subscriber
A is a mobile subscriber and B is a fixed line subscriber. The call from A to B involves the GMSC. The process of call connection is as follows: 1. 2. 3. VMSC A routes the call from A to the tandem MSC (TMSC). The TMSC forwards the call to the GMSC. The GMSC forwards the call to a switch in the fixed network.

Figure 1-11 shows the process of generating CDRs under this condition. 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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-23

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

The TMSC generates a transit (TRANSIT) record, which is the reference for calculating the charge of occupied trunks in the local network. The GMSC generates a gateway outgoing (GWO) record, which is the reference for calculating the charge of occupied outgoing trunks between the wireless network and the fixed network. If the end office directly routes the call to the GMSC (without passing the TMSC), and then to the PSTN, no TRANSIT record is generated.

The TRANSIT record and GWO record are defined by MOD GBILLCTRL. That is, TRANSIT records can be generated not only by the TMSC, and GWO records can be generated not only by the GMSC. For example, in practice, if an end office directly connects to a switch in another network and acts as a gateway office, the end office can also generate GWO records after relevant data is configured.

CDR for the Call from Fixed Line Subscriber to Mobile Subscriber
A is a fixed line subscriber and B is a mobile subscriber. The call from A to B involves the GMSC. The process of call connection is as follows: 1. 2. 3. 4. The switch in the fixed network sends an IAI message to the GMSC. The GMSC obtains the MSRN of B. The GMSC routes the call to the TMSC after obtaining the MSRN. The TMSC routes the call to the VMSC.

Figure 1-12 shows the process of generating CDRs under this condition. 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, which is the reference for calculating the charge of occupied incoming trunks between the fixed network and the wireless network. The TMSC generates a TRANSIT record, which is the reference for calculating the charge of occupied trunks in the local network. VMSC B generates a CDR for the MTC and the charged subscriber is B. If the GMSC directly routes the call to the end office (without passing the TMSC), no TRANSIT record is generated.

The roaming record, TRANSIT record and GWO record are all defined by MOD GBILLCTRL.

1-24

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. Subscriber A belongs to the wireless network of carrier Y. The switch in the network of carrier Y generates CDRs for A. The switch in the network of carrier W generates CDRs for B. The GMSCs in the two networks generate CDRs respectively for inter-network calculation. The call from A to B involves GMSC 1 and GMSC 2. The process of call connection is as follows: 1. 2. 3. VMSC 1 routes the call to GMSC 1. GMSC 1 routes the call to GMSC 2 that is in the network of carrier W. GMSC 2 routes the call to VMSC 2 after obtaining the MSRN.

Figure 1-13 shows the process of generating CDRs under this condition. 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. VMSC 2 generates a CDR for the MTC and the charged subscriber is B. TMSC 1 generates a TRANSIT record. GMSC 1 generates a GWO record, which is the reference for calculating the charge of occupied outgoing trunks between the two wireless networks. GMSC 2 generates a GWI record, which is the reference for calculating the charge of occupied incoming trunks between the two wireless networks.

1.7.3 CDR for Emergency Call


After a mobile station successfully originates an emergency call, the MSC server at the caller side generates a CDR for the emergency call. The CDR consists of the source and destination of the call, and user identity. The CDR is stored in the iGWB and waits to be sent to the charging center. The CDR for an emergency call is of the same format as an MOC bill. Emergency call observation flag is set to True, and the service code is of an emergency call. If a subscriber makes an emergency call without a SIM/USIM, the network identifies the subscriber through IMEI.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

1-25

1 Speech Service

HUAWEI MSOFTX3000 Feature Description

1.8 Service Interaction


Table 1-8 lists the interaction between the emergency call function and other services. 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, the calling number cannot be displayed on the phone of the callee. The ODB service does not prevent a subscriber from making an emergency call. The CUG service conflicts with the emergency call service.

Note: CLIR = calling line identification restriction; ODB = operator determined barring; CUG = closed user group

1.9 Reference
1.9.1 Protocols and Specifications
The reference of the speech service is as follows: 3GPP TS 22.101 4.6.0

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

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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 2-1 Location of the SMC in a mobile network........................................................................................2-5 Figure 2-2 MAP_SEND_ROUTING_INFO_FOR_SM flow ............................................................................2-7 Figure 2-3 MAP_REPORT_SM_DELIVERY_STATUS flow...........................................................................2-7 Figure 2-4 MAP_READY_FOR_SM flow ........................................................................................................2-8 Figure 2-5 MAP_ALERT_SERVICE_CENTRE flow .......................................................................................2-8 Figure 2-6 SM MO flow.....................................................................................................................................2-9 Figure 2-7 SM MT flow ...................................................................................................................................2-10 Figure 2-8 Flow of alert SMC mobile station reachable ............................................................................... 2-11 Figure 2-9 Flow of alert SMC memory of MS ready ....................................................................................2-12 Figure 2-10 Flow of alert SMC SMS succeeds .............................................................................................2-13

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 2-1 NEs required to realize the SMS ........................................................................................................2-4 Table 2-2 HUAWEI CS product versions that support the SMS ........................................................................2-4 Table 2-3 Functions of NEs in the transmission of SMs.....................................................................................2-5 Table 2-4 Functions of NEs in the transmission of SMs.....................................................................................2-6 Table 2-5 Interaction between the SMS and other services ..............................................................................2-16

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

2
About This Chapter
Section 2.1 Service Description 2.2 Availability

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

2.3 Working Principle 2.4 Service Flows 2.5 Data Configuration 2.6 Service Management

2.7 Charging and CDR 2.8 Service Interaction 2.9 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-1

2 Short Message Service

HUAWEI MSOFTX3000 Feature Description

2.1 Service Description


2.1.1 Function Code
Name Short message MO/PP (SMS-MO) Short message MT/PP (SMS-MT) Code WMFD-010201 WMFD-010202

2.1.2 Definition
The short message service (SMS) allows subscribers to send or receive information through the short message center (SMC).The information can be texts, pictures, and voices. "Short" means that the length of information sent in the SMS is short. A point to point (PTP) short message (SM) can have up to 140 bytes in size, that is, 160 ASCII characters or 70 Chinese characters. A broadcast SM can have 82 bytes per page, that is, 92 ASCII characters or 41 Chinese characters. A macro broadcast message can have up to 15 pages that are sent continuously. 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. The SMSs fall into two categories: PTP SMSs and PTM SMSs. PTM is short for point to multipoint. The PTM SMSs mainly refers to the cell broadcast SMSs. The PTP SMSs fall into two categories: SM MT service (TS21) SM MO service (TS22) This chapter describes only the PTP SMSs. 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. The following figure shows the process.
Short message delivery SMC report MS

2-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. The following figure shows the process.
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, the SMC sends an SM status report to the HLR, containing the MSISDN of the callee and the address of the MO SMC. The HLR stores the information in the message waiting data (MWD) list and enables the Mobile Station Not Reachable Flag (MNRF).The VLR also enables the MNRF. At the same time, the SMC temporarily stores the SM that fails to be sent. When the MS makes or receives a call, or re-registers with the network through a location update, 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, the SMC sends an SM status report to the HLR, containing the MSISDN of the callee and the address of the SMC. The HLR stores the information in the MWD list and enables the Mobile Station Memory Capacity Exceeded Flag (MCEF). At the same time, the SMC temporarily stores the SM that fails to be sent. 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. Upon receipt of the message, the MSC server sends a message indicating memory of MS ready to the HLR. The HLR receives the message and checks the MCEF. The HLR sends an SM ready alert to the SMC specified in the MWD list.

2.1.3 Benefits
Beneficiary Carriers Description The SMS can help to provide value added services, information inquiry services, and services such as website SMS and pictures. It also expands service types and improves the average revenue per user (ARPU).

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-3

2 Short Message Service

HUAWEI MSOFTX3000 Feature Description

Beneficiary Mobile subscribers

Description The SMS can be used to send information. It can also be used to receive information such as stock prices, weather reports, sports news, and bank accounts. This eases information query and makes subscribers feel closer to carriers.

2.2 Availability
2.2.1 Requirements for NEs
The SMS is implemented through the interworking between the MS/UE, the radio access network (RAN), and the core network (CN). Table 2-1 lists the network elements (NEs) that are required to realize the SMS. 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; UE = User Equipment, BTS = Base Transceiver Station; BSC = Base Station Controller; RNC = Radio Network Controller; MSC = Mobile Switching Center; MGW = Media Gateway; SGSN = Serving GPRS Support Node; VLR = Visitor Location Register; HLR = Home Location Register; SMC = Short Message Center

The symbol indicates that the NE is required.

2.2.2 Requirements for License


The SMS is an optional feature of the radio access network (RAN) provided by Huawei Technologies Co., Ltd. (called Huawei in this manual). To use the SMS, both a License of the MSOFTX3000 and that of the SMC are required.

2.2.3 Applicable Versions


Table 2-2 lists the HUAWEI circuit switched (CS) domain product versions that support the SMS. 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)

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

2.3 Working Principle


2.3.1 Networking Structure
As a service processing system independent of the GSM/UMTS network, the SMS system performs the following functions: Submitting, storing, and forwarding SMs Interworking with the PSTN, ISDN, and PSPDN to transmit SMs from external short message entities (ESMEs) such as manual stations and automatic stations The SMC, as the SMS system provided by Huawei, brings together functions of the SMS-GMSC, SMS-interworking MSC (IWMSC), and service center (SC). Figure 2-1 shows the location of the SMC in a mobile network. 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, the NEs related to the SMS system are the MSC, VLR, SGSN, and HLR. Table 2-3 lists the functions of the NEs in the transmission of SMs. 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, the MSC forwards the SM to the SMC. After an SM is sent from the SMC to the MSC, the MSC obtains the routing and subscriber information from the VLR and forwards the SM to the MS through the RAN.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-5

2 Short Message Service

HUAWEI MSOFTX3000 Feature Description

NE VLR

Function It authenticates the subscriber to whom the SMC sends an SM. It provides routing for the MSC when the SMC sends an SM to the subscriber through the MSC.

SGSN

When an SM sent by the MS reaches the SGSN through the RAN, the SGSN forwards it to the SMC. After receiving an SM sent from the SMC, the SGSN forwards it to the MS through the RAN.

HLR

Before the SMC sends an SM, the HLR searches the MSC that serves the subscriber. If authentication is required when the MSC sends an SM, the MSC requests the authentication set from the VLR. If there is no authentication set in the VLR, the MSC requests it from the HLR. In all other cases, the MSC does not request basic subscriber information from the HLR when sending an SM.

2.3.2 Short Message Transfer Path


When different network access modes are used, the SM transfer paths are different. Table 2-4 lists the details. 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, the GMSC sends it to the VMSC. This is similar to the transfer means used in the GSM network. 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. domain or the CS domain. This

2.4.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. Thus, the SM can be routed to the MSC or SGSN. Figure 2-2 shows the flow.

2-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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), the HLR may return two numbers: an SGSN number and an MSC number. If the GMSC does not support the GPRS, the HLR returns one number and whether the number is an SGSN number or an MSC number is determined by MOD SMDP.

MAP_REPORT_SM_DELIVERY_STATUS
The flow is started by the GMSC to inform the HLR whether the SM sending succeeds or fails. Figure 2-3 shows the flow. If the message sending succeeds, 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. If the message sending fails, the HLR saves the address of the SMC or the cause of MS not reachable to the MWD list. 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, the HLR clears the MCEF and starts the

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-7

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. If the HLR detects that the MCEF and the MNFG/MNRG of the subscriber are not enabled, which shows that the MAP_REPORT_SM_DELIVERY message is not sent to the HLR, the HLR sets a timer. After the message is received, the HLR sets the flag bits of the MCEF and the MNFG/MNRG to 0. Figure 2-4 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, location update flow, or GPRS location update flow, 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. Figure 2-5 shows the 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, the MAP_Alert_Service_Centre message is sent from the HLR to the IWMSC logically.

2-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

2.4.2 SM MO Flow
In the SM MO flow, a subscriber uses the MS to send an SM to the SMC. Figure 2-6 shows an SM MO flow. Figure 2-6 SM MO flow

MS
1. ShortMessage (RP_Data)

VMSC/SGSN

VLR

SMC

2.SEND_INFO_FOR_MO_SMS (*)

7.ShortMessage Error (RP_ERROR)

3.SEND_INFO_FOR_MO_SMS_ACK (*) 4.MO_FORWARD_SHORT_MESSAGE (RP_DATA) 5.MO_FORWARD_SHORT_MESSAGE_ACK (RP_ACK)

6.Short Message Acknowledgement(RP_ACK)

The messages with "(*)" are applicable to the MSC only, not the SGSN.

1. 2. 3. 4.

The MS sends an SM to the VMSC server or the SGSN through the A/Iu interface. Upon receipt of the SMS request, the VMSC server sends a subscriber data check request to the VLR based on the MSISDN of the MS. The VLR checks the subscription information and whether the local office supports the SMS, and sends the result to the VMSC server. The VMSC server analyzes the result. If the local office does not support SM MO, or it registers the outgoing call barring service, the VMSC server directly sends a reject message (RP_ERROR) to the MS. Otherwise, the VMSC server obtains the address of the SMC from the SM MO and transparently transmits the SM MO to the SMC. Upon receipt of the request, the SMC checks whether the data is valid. If yes, the SMC sends a message to the VMSC server or the SGSN to acknowledge the transparent transmission of the SM MO. Upon receipt of the message, the VMSC server or the SGSN sends the result of SM MO sending to the MS.

5.

6.

2.4.3 SM MT Flow
In an SM MT flow, the SMC sends an SM to the MS. Figure 2-7 shows an SM MT flow.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-9

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).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).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, not the SGSN.

1. 2.

Upon receipt of the SM MT, the SMC obtains the called number and uses it to request the routing information from the HLR. Upon receipt of the routing information, the HLR returns a response.
When the priority of the SM MT is high, the HLR returns a normal response to the SMC even if the MNRF and the MCEF are enabled.

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. Roaming is not allowed. Carrier determined call barring barring of all incoming calls or SMs MT The SM MT service is not supported. The MNRF is enabled. The MCEF is enabled. The subscriber is deleted by the MSC server/VLR to which the subscriber roams. If none of the preceding events occurs, the HLR sends the MSC number or the SGSN number to the SMC. 3. 4. 5. By using the MSC number, the SMC sends a transparent transmission request to the VMSC server. Upon receipt of the request, the VMSC server sends a request for checking SM MT subscriber data to the VLR. The VLR checks the subscription data and mobility management status:

2-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

If the subscriber cannot be paged because the subscriber does not support SM MT, the handset is powered off, the MNRF is enabled, or the roaming is not allowed, the VMSC server sends a failure response to the SMC. If the location area of the MS is known, the VMSC server starts paging the MS in the specific location area. If the location area of the MS is unknown, the VMSC server starts paging the entire area controlled by the MSC server.

6. 7. 8.

The VMSC server pages the MS. The MS sends a response to the VMSC server. (8)(9)(10): Upon receipt of the response, the VMSC server starts the subscriber access process. After the process is complete, the VMSC server sends the SM to the MS through the Iu interface. (11)(12): After receiving the result from the MS, the VMSC server sends it to the SMC.

9.

10. If there are multiple SMs, that is, the RP-MMS exists in the transparent transmission request, the connections are maintained and (3), (10), (11), and (12) are repeated. 11. If no additional message is to be sent, all connections are released.

2.4.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. The MS alerts the SMC when its memory is ready.

Alert SMC Mobile Station Reachable


Figure 2-8 shows the flow. Figure 2-8 Flow of alert SMC mobile station reachable
MS MSC/ SGSN VLR HLR SMC

(1) CM Service Req (**), 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.

Alert SC: Alert_Service_Centre

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-11

2 Short Message Service

HUAWEI MSOFTX3000 Feature Description

1. 2.

The MS makes or receives a call or updates the location to re-connect with the network. The MSC server sends an access request to the VLR if the MS makes or receives a call. Or the MSC server checks the data of the subscriber who updates the location if the MS updates the location. The VLR checks subscriber data. If the VLR detects that the MNRF 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 VLR directly sends a location update request to the HLR in the case of a location update flow. If the HLR receives the SM ready alert, it checks the dynamic data of the subscriber. If the MNRF is enabled, the HLR clears it, sends an Alert_Service_Centre message to the SMC, and sends a message to the VLR to acknowledge the sending of the SM ready alert. If the HLR receives a location update request and the MNRF in the dynamic data of the subscriber is enabled, the HLR clears the MNRF, sends an Alert_Service_Centre message to the SMC, and continues the location update flow.
The HLR sends the Alert_Service_Centre message to all SMCs specified in the MWD list. The HLR sends the Alert_Service_Centre message only when the MCEF of the MS is set to False.

3.

4.

5.

Upon receipt of the Alert_Service_Centre message, the SMC returns a response and tries to send SMs again.

Alert SMC Memory of MS Ready


Figure 2-9 shows the flow. 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. 2.

The MS sends a memory ready message to the MSC server through the Iu interface. The MSC server sends an SM ready message with the cause as memory of MS ready to the HLR.

2-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

3.

Upon receipt of the message, the HLR checks the dynamic data of the subscriber. If the MCEF of the subscriber is enabled, the HLR clears it, sends an Alert_Service_Centre message to the MSC server, and sends an SM ready message to the VLR. Upon receipt of the message, the MSC server returns a response to the MS. Upon receipt of the Alert_Service_Centre message, the SMC returns a response and tries to resend the SM. The timing of the SM resending upon SMS failure is controlled by the SMC through the resending interval setting.

4.

Alert SMC SMS Succeeds


If the SMS succeeds, 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. 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. 2. 3. 4.

The GMSC server sends an SMS succeeds message to the HLR. Upon receipt of the message, the HLR returns a response. The HLR sends an Alert_Service_Centre message to the SMC. The SMC returns an Alert_Service_Centre_ACK message to the HLR.

2.5 Data Configuration


The SMS is implemented through the signaling system. Therefore, you must configure data only on the MSC server and the HLR, not on the MGW.

2.5.1 Data Configuration of the MSOFTX3000


To implement the SMS, you must configure the signaling and service data of the MSOFTX3000 for interworking with the SMC.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-13

2 Short Message Service

HUAWEI MSOFTX3000 Feature Description

Adding MTP Data


To add MTP data, proceed as follows: Step 1 Add an MTP destination signaling point (DSP) by using ADD N7DSP. Step 2 Add an MTP linkset by using ADD N7LKS. Step 3 Add an MTP route by using ADD N7RT. Step 4 Add an MTP link by using ADD N7LNK. ----End

For details about the configuration steps and parameter descriptions, refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Adding SCCP Data


To add SCCP data, proceed as follows: Step 1 Add an SCCP DSP by using ADD SCCPDSP. Set Network indicator to a value based on the actual requirements from the SMC to the SCCP DSP. You can set it to National network, for example. Step 2 Add an SCCP sub-system number by using ADD SCCPSSN. Add the MSC and SCCP management subsystem (SCMG) to the remote SMC. The local MSC, VLR, SCMG are already configured in the office information data. Therefore, run LST SCCPSSN to list the values and there is no need to configure the data again. Step 3 Add an SCCP GT group by using ADD SCCPGTG. Specify the GT group to which the SCCP GT group belongs during the configuration. Step 4 Add an SCCP global title by using ADD SCCPGT. Select a general global title. Select a network indicator based on the actual requirements. Set Numbering Plan to ISDN/telephony numbering Plan. Enter an SMC number such as 8613900007 as the GT address information. ----End

Setting MAP Feature Configuration


Step 1 Run LST MAPACCFG to see whether Support SMMO function and Support SMMT function are set to Yes. Step 2 If not, run SET MAPACCFG to set them to Yes. ----End

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

For details about the configuration steps and parameter descriptions, refer to related HLR manuals.

2-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

2.6 Service Management


2.6.1 For Carrier
The following operations can be performed on an HLR client: Enable or Disable the SMS. List the path of an SM. Modify the path of an SM.
For details, refer to related operation manuals of the HLR.

2.6.2 For Mobile Subscriber


The address of the SMC can be configured.

2.7 Charging and CDR


Difference Between SMS CDR and Voice Call CDR
In an SMS call detail record (CDR), ordinary subscriber. there is no difference between an IN subscriber and an

The SMS uses signaling or voice channels to send characters. An SMS CDR, different from an ordinary voice call CDR, contains the following elements: Number of bytes: It indicates the actual number of bytes of the UserPart in an SM. It is the actual length of an SM after decoding. Address of SMC: It indicates which SMC is used for communication.

SMS CDR of Caller


If an SM is successfully sent to the SMC, the VMSC server that serves the subscriber who sends an SM generates an SMS CDR for the caller. The SMS CDR contains the IMSI and MSISDN of the caller, the number of the caller, the SMC address in E.164 format, the charging flag, the additional charging flag, and the content of the SM. The CDR files are saved in the iGWB. Based on FTAM or FTP, the iGWB sends the CDR files to the billing center through the TCP/IP connection. FTAM is short for File Transfer Access and Management Protocol.

SMS CDR of Callee


When a subscriber receives an SM, the VMSC server that serves the subscriber generates an SMS CDR for the callee. The SMS CDR contains the IMSI and MSISDN of the callee, the number of the caller, the SMC address in E.164 format, the charging flag, the additional charging flag, and the content of the SM.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

2-15

2 Short Message Service

HUAWEI MSOFTX3000 Feature Description

The CDR files are saved in the iGWB. Based on FTAM or FTP, the iGWB sends the CDR files to the billing center through the TCP/IP connection.

2.8 Service Interaction


Table 2-5 shows how the SMS interacts with other services. 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. It interacts with the SM MO service. When a subscriber subscribes to the hot billing service, a hot billing flag is generated for each SM sent or received. The hot billing flag provides the charging data for all services of a subscriber. It is immediately sent to the billing center. Handover No SM can be sent during an intra-MSC or inter-MSC handover. An SM can be sent after the handover is complete. A handover request is rejected when an SM is being transmitted. The handover continues after the transmission of an SM is complete. IMSI attach/IMSI detach It interacts with the SM MT service. When the VLR sets the subscriber to IMSI detach, the subscriber is not reachable. If the SM is sent to a subscriber who is in IMSI detach state, the SM is stored in the SMC. After the IMSI is attached, the SMC tries to resend the SM.

2-16

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

2 Short Message Service

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

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)

HUAWEI MSOFTX3000 Feature Description

Contents

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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Contents

HUAWEI MSOFTX3000 Feature Description

3.9 References ...................................................................................................................................................3-35 3.9.1 Protocols and Specifications ..............................................................................................................3-35 3.9.2 Acronyms and Abbreviations .............................................................................................................3-35

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Figures

Figures
Figure 3-1 GMSC-originated call forwarding service flow................................................................................3-5 Figure 3-2 VMSC-originated call forwarding service flow................................................................................3-6 Figure 3-3 CFU service flow for a call forwarded to a PSTN subscriber...........................................................3-7 Figure 3-4 CFU 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 .......................................................3-9 Figure 3-6 UDUB service flow for a call forwarded to a PSTN subscriber .....................................................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-12 Figure 3-9 CFNRy service flow for a call forwarded to a PSTN subscriber ....................................................3-13 Figure 3-10 CFNRy service flow for a call forwarded to a mobile subscriber. ................................................3-14 Figure 3-11 CFNRc service flow for call forwarded to a PSTN subscriber .....................................................3-16 Figure 3-12 CFNRc service flow for the mobile forwarded-to subscriber .......................................................3-17 Figure 3-13 Charging of the call forwarding services ......................................................................................3-22

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

Tables

HUAWEI MSOFTX3000 Feature Description

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

iv

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Call Forwarding Supplementary Service

About This Chapter


The following table lists the contents of this chapter. Section 3.1 Service Description 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.

3.2 Availability

3.3 Working Principle 3.4 Service Flow 3.5 Data Configuration 3.6 Service Management

3.7 Charging and CDR 3.8 Service Interaction 3.9 References

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-1

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

3.1 Service Description


3.1.1 Function Code
Table 3-1 lists the function codes of the call forwarding services. 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.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, the network, or the subscriber. Call forwarding services are divided into CFU, CFB, CFNRy, and CFNRc. Here, the third party can be a subscriber in the PLMN, PSTN, ISDN networks, or a service platform such as the voice mailbox. Table 3-2 lists the definitions of the call forwarding services. 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. The calls to a mobile subscriber are forwarded to the third party if the subscriber is busy. 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.

3-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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, the calls to the mobile subscriber are forwarded to the third party. The triggering conditions of the CFNRc service includes mainly: The mobile subscriber does not respond to the paging. The wireless channel allocation fails. The mobile station is powered off. The forwarding may occur in the network where the caller resides or the network that the callee resides.

3.1.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. A subscriber can activate or deactivate the call forwarding services provided by the system through the mobile phones. In this way, the subscriber can select the terminal and the site for answering a call. The call quality is improved consequently.

Subscriber

3.2 Availability
3.2.1 Requirements for NEs
The MSC server, the VLR, and the HLR work together to implement the call forwarding services. Table 3-4 lists the related NEs. 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

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

The symbol represents that the NE is required to implement the service.

3.2.2 Requirements for License


Call forwarding is a basic service of HUAWEI wireless core network. You can use the service without acquiring a license.

3.2.3 Applicable Versions


Table 3-5 lists the applicable versions of the call forwarding service. Table 3-5 Applicable versions Product MSC Server MGW MSOFTX3000 UMG8900 Applicable Version V100R002 and later versions V200R002 and later versions

3.3 Working Principle


3.3.1 Functions of the NEs
The MSC server, the MGW, and the VLR work together to implement functions such as signaling processing, data analysis, announcement playing, and billing. The MSC server and the MGW work together to implement the announcement playing function. The MGW is mainly used to load the announcement files related to the call forwarding services. PSTN switches are used to process the calls forwarded to them and then route the calls to the destination PSTN terminal. 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. Call forwarding triggering analysis The system determines which service to be triggered in this process. For example, the system may determine whether to trigger the CFU or the CFNRc service and return the FTN to the GMSC.

3.3.2 Service Flow Inside the System


Based on the call forwarding types, the service flow inside the system can be divided into GMSC-originated forwarding and VMSC-originated forwarding.

3-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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.) Figure 3-1 shows the GMSC-originated call forwarding service flow. 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. 2. 3. 4. An incoming call to the callee is routed to the GMSC server. The GMSC server requests the routing information from the HLR of the callee. The HLR checks the authentication and subscription information of the callee. 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, 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. The GMSC server sets up the call to the forwarded-to subscriber based on the FTN.

5.

6.

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

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. 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. 2. 3. 4. 5. 6. An incoming call to the callee is routed to the GMSC server. The GMSC server requests the routing information from the HLR of the callee. The HLR checks the authentication and subscription information of the callee. The HLR obtains the MSRN of the callee from the VLR. The GMSC server requests the VMSC server of the callee to set up the call based on the MSRN. The VMSC server requests the subscription information of the callee from the VLR. The VLR returns the call forwarding service information to the VMSC server. For CFNRy, it also returns the value of the no reply timer. After receiving the subscription information of the callee, the VMSC server checks whether the conditions to trigger the call forwarding service are met. The triggering principles are as follows:

7.

The CFNRy service is triggered if the no reply timer expires. 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 MS of the callee is powered off, or the channel allocation fails.

8.

If the conditions for triggering a call forwarding service are met, the VMSC server requests the FTN from the VLR.

3-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

9.

The VMSC server sets up the call to the forwarded-to subscriber based on the FTN.

3.4 Service Flow


This chapter describes only the call forwarding which takes place before a MGW is selected. The user plane bearing is established after the call is forwarding to different target offices.

3.4.1 CFU Service Flow


In CFU service, the call is forwarded under any situation. information is stored in the HLR. 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. 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. 2. The GMSC sends the Info req message to the HLR. The HLR returns the Info ack message to the GMSC.

On detecting that the callee has subscribed to and activated the CFU, the HLR includes the FTN in the Info ack message and sends the message to the GMSC server. The GMSC server forwards the call based on the FTN. If the Info ack message contains the information element Notification to calling party, the GMSC server sends the notification to the caller. If the subscriber has not registered to the CFU service, the call is routed to MSC Server B normally.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-7

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

3.

If the call forwarding conditions are met, the GMSC server forwards the call to the PSTN subscriber based on the FTN directly.

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. 2. 3. The GMSC sends the Info request message to the HLR. The HLR returns the Info ack message to the GMSC. On detecting that the callee has subscribed to the CFU, the HLR includes the FTN in the Info ack message and sends the message to the GMSC server. The GMSC server forwards the call based on the FTN. If the Info ack message contains the information element Notification to calling party, the GMSC server sends the notification to the caller. The GMSC server sends the Info request message to HLR C where the forwarded-to subscriber resides to request the routing information. HLR C sends the Info ack message containing the routing information to the GMSC server. After receiving the routing information, the GMSC sends the Set-up message to MSC server C. MSC server C is responsible for paging the target mobile subscriber.

4. 5. 6. 7.

3.4.2 CFB Service Flow


In CFB service, the call is forwarded in network determined user busy (NDUB) or user determined user busy (UDUB) conditions. UDUB refers to the situation that the callee rejects the call after the MS of the callee rings. NDUB refers to the situation that there is no available

3-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

network resource. For the forwarded-to subscriber, the call is not affected if the CFB is activated.

Forwarding to a PSTN Subscriber in NDUB


Figure 3-5 shows the NDUB service flow for a call forwarded to a PSTN subscriber. 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. 2. 3. 4. 5. 6. 7. MS A sends the Setup message to the GMSC server. The GMSC server sends the Info req message to HLR B. HLR B sends the Info ack message containing the MSRN to the GMSC server. The GMSC server sends the Set-up message to MSC server B. After receiving the Set-up message, MSC server B sends the Info request message to VLR B to request the information about MS B. VLR B sends the Page MS message containing the FTN to MSC server B. 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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-9

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

8. 9.

If the subscriber has not registered to the CFB service, the call fails. If the subscriber has registered to the CFB service, go to step 9. 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. 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. 2. 3. 4. 5. 6. 7. MS A sends the Setup message to the GMSC server. The GMSC server sends the Info req message to HLR B. HLR B sends the Info ack message to the GMSC server. The GMSC server sends the Set-up message to MSC server B based on the routing information. After receiving the Set-up message, MSC server B sends the Info req message to VLR B to request the information about MS B. VLR B sends the Page MS message to MSC server B. After MS B responds to the paging, MSC server B sends the Set-up message to MS B. After MS B rings, the UDUB service is triggered if the callee rejects the call.

3-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

8.

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. The Page MS message sent from VLR B to MSC server B contains the information related to the forwarding, for example, the FTN and whether the caller and the callee is notified when forwarding occurs.

9.

10. If the callee has not subscribed to and activated the CFB service, the call fails. Otherwise, go to step 12. 11. 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. 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. The only difference lies in the call forwarding flow. The NDUB service flow for mobile forwarded-to subscriber is as follows:

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-11

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

After receiving the FTN, 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 sends the Set-up message to MSC server C.

Forwarding to a Mobile Subscriber in UDUB


Figure 3-8 shows the UDUB service flow for a call forwarded to a mobile subscriber. 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 only difference lies in the forwarding flow. The UDUB service flow for mobile forwarded-to subscriber is as follows: After receiving the FTN, MSC server B requests the routing information (through the Info req message) from HLR C. After HLR C sends the routing information (through Info ack) to MSC server B, MSC server B sends the Set-up message to MSC server C.

3-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

3.4.3 CFNRy Service Flow


In CFNRy service, all the calls of the basic service and certain other services are forwarded.

Forwarding to a PSTN Subscriber


Figure 3-9 shows the CFNRy service flow for call forwarded to a PSTN subscriber. 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. 2. 3. 4. 5. 6. MS A sends the Setup message to the GMSC server. The GMSC server sends the Info req message to HLR B. HLR B sends the Info ack message containing the routing information to the GMSC server. The GMSC server sends the Set-up message to MSC server B based on the routing information. MSC server B requests the information of MS B from VLR B. VLR B sends the Info ack message to MSC server B.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-13

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

7. 8. 9.

MSC server B pages MS B. After MS B responds to the paging, a no reply timer is started on MSC server B. If the callee does not answer the call after the no reply timer expires, MSC server B starts the call release process. At the same time, MSC server B notifies VLR B that the no reply timer expires through the Info req message.

10. VLR B determines whether to forward the call as follows: If there is no CFNRy service data, the call is released. If there is CFNRy service data, VLR B forwards the data to MSC server B, which routes the call to the forwarded-to subscriber.

Forwarding to a Mobile Subscriber


Figure 3-10 shows the CFNRy service flow for a call forwarded to a mobile subscriber. Figure 3-10 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. 2. The MS A sends the Setup message to the GMSC server. The GMSC server sends the Info req message to HLR B.

3-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

3. 4. 5. 6. 7. 8.

HLR B sends the Info-ack message to the GMSC server. The GMSC server sends the Set-up message to MSC server B. MSC server B requests the information of MS B from VLR B. VLR B sends the Info ack message to MSC server B. MSC server B pages MS B. After MS B responds to the paging, a no reply timer is started on MSC server B. If the callee does not answer the call after the no reply timer expires, MSC server B starts the call release process. At the same time, MSC server B notifies VLR B through the Info req message. VLR B determines whether to forward the call as follows:

9.

If there is no CFNRy service data, the call is released. If there is CFNRy service data, VLR B forwards the data to MSC server B, which routes the call to the forwarded-to subscriber.

3.4.4 CFNRy Service Flow


The CFNRc service is triggered in the following situations: The callee does not respond to the paging. The MS of the callee is powered off. The channel allocation fails. The following CFNRc service flow takes the situation when the subscriber does not respond to the paging as an example.

In the following examples, the CFNRc service flow is initiated by the VMSC. The GMSC-initiated CFNRc service flow is similar to the GMSC-initiated CFU service flow. For detailed information, refer to section 3.4.1 CFU Service Flow.

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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-15

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. 2. 3. 4. 5. 6. 7. 8. 9. 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 Information message to VLR B. VLR B provides the roaming number to HLR B. HLR B sends the Info ack message to the GMSC server. The GMSC server sends the Set-up message to MSC server B. MSC server B requests the information of MS B from VLR B. VLR B sends the Page MS message to MSC server B. MSC server B pages MS B. If MS B does not respond to the paging, MSC server B returns page response to VLR B indicating the reason for no response is Absent Subscriber.

10. VLR B determines whether to forward the call. If the forwarding conditions are not met, the call is released. If the forwarding conditions are met, the call is routed based on the CFNRc service data.

3-16

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. 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. 2. 3. 4. 5. 6. 7. 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. The GMSC server sends the Set-up message to MSC server B. MSC server B sends Info req to VLR B. VLR B sends Page MS to MSC server B. MSC server B pages MS B. If MS B does not respond to the paging, MSC server B returns page response to VLR B with the reason of the no response as Absent Subscriber. VLR B determines whether to forward the call.

If the forwarding conditions are not met, the call is released. If the forwarding conditions are met, the call is routed based on the CFNRc service data.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-17

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

3.5 Data Configuration


3.5.1 MSOFTX3000 Data Configuration
The data configuration of CF SS for the MSOFTX3000 is complex. Please refer to the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

3.5.2 HLR Configuration


Refer to the corresponding operation manuals of the HLR products for detailed operations.

3.6 Service Management


The management operations of the CF SS consists of provisioning, activation, deactivation and deregistration. The definition of each operation is as follows: Provisioning The operation is performed by the carriers. It makes a service available to the subscribers. Its reverse operation is withdrawal. Withdrawal The operation is performed by the carriers. It makes a service unavailable to the subscribers. Its reverse operation is provisioning. Registration The operation is performed by the carriers or the subscribers. The operation is mainly used to input some dedicated supplementary service information. For certain services, the registration process also activates the services. Its reverse operation is deregistration. Deregistration The operation is used to delete the information input in the HLR in the registration. Its reverse operation is registration. Activation The operation is performed by the service providers, the subscribers, or the system. The operation makes the service ready for provisioning. Its reverse operation is deactivation. Deactivation The operation is performed by the service providers, the subscribers, or the system. It is used to terminate the process started by the activation operation. Its reverse operation is activation. The call forwarding services are activated once they are registered. You need not to activate a call forwarding service separately. A call forwarding service should be first provided, and then registered before it can be used by the subscribers. The call forwarding service has two operation modes, as shown in Table 3-6. Table 3-6 Operation modes of the call forwarding service Mode Carrier Site HLR Service Provisioning, withdrawal, registration, and deregistration. withdrawal, registration,

3-18

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Mode Subscriber

Site MS

Service Registration, activation, deactivation, and deregistration.

3.6.1 Operations by the Carriers


Through operations in the HLR, the carriers can control the provisioning, withdrawal, registration, and deregistration of the call forwarding services.

3.6.2 Operations by the Subscribers


Prerequisites
The system has provided the call forwarding services to the subscribers.

Operation Steps
By dialing the service feature code through the MSs, mobile subscribers can register, activate, deactivate, or deregister a service.

When registering an international FTN through the MS, you should add a symbol + before the country code. Otherwise the registration may fail. An example of the correct number format is as follows: +8613912345678.

Table 3-7 lists the procedures of CFU service operations. 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. Here, FN represents the FTN. The subscriber dials #21# through the MS and then press the button used to send the information. The subscriber dials *21# through the MS and then press the button used to send the information. The subscriber dials ##21# through the MS and then press the button used to send the information.

Table 3-8 lists the procedures of CFB service operations.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-19

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. Here, FN represents the FTN. The subscriber dials #30.39kg through the MS and then press the button used to send the information. The subscriber dials *30.39kg through the MS and then press the button used to send the information. The subscriber dials ##30.39kg through the MS and then press the button used to send the information.

Table 3-9 lists the procedures of CFNRy service operations. 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. Here, FN represents the FTN. The subscriber dials #27.67kg through the MS and then press the button used to send the information. The subscriber dials *27.67kg through the MS and then press the button used to send the information. The subscriber dials ##27.67kg through the MS and then press the button used to send the information.

Table 3-10 lists the procedures of CFNRc service operations. 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. Here, FN represents the FTN. The subscriber dials #28.12kg through the MS and then press the button used to send the information. The subscriber dials *28.12kg through the MS and then press the button used to send the information.

3-20

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Operation Deregistration:

Procedure The subscriber dials ##28.12kg through the MS and then press the button used to send the information.

Table 3-11 lists the procedures of operations applied to all the call forwarding services. 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. Here, DN represents the FTN. T represents the value of the no reply timer. It ranges from 5 to 30 seconds. The subscriber dials ##002# through the MS and then press the button used to send the information.

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. Here, DN represents the FTN. T represents the value of the no reply timer. It ranges from 5 to 30 seconds. The subscriber dials ##004# through the MS and then press the button used to send the information.

Deregistration:

3.7 Charging and CDR


3.7.1 Charging Principle
Assume that the caller is A, the callee is B, and the forwarded-to subscriber is C. After querying the information and status of subscriber B, the originating MSC (or GMSC) routes the call to the office where the subscriber C resides, as shown in Figure 3-13.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-21

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, who has initiated the call forwarding, is charged as a caller, not as a callee. A separate CDR is created for the call forwarding service. In the CDR, B is the caller, C is the callee, and A is the third party.

3.7.2 Difference Between CFU and CCF in Judging an International Call


Call Forwarding (CF) refers to all the call forwarding services. Conditional Call Forwarding (CCF) consists of CFB, CFNRy, and CFNRc. In CFU, 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. In CCF, 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. Therefore, CFU and CCF define international numbers differently for the charging of international roaming. In the CFU service, an FTN is considered as an international number if it is not a number within the country. In the CCF service, an FTN is considered as an international number if it is not a number within the country where the callee roams to.

The CFNRc service initiated by the GMSC judges an international number in the same way as the CFU service.

3.7.3 CDR Creation Principles


Assume that the caller is A, the callee is B, and the forwarded-to subscriber is C. The CDR creation principles are shown in Table 3-13.

3-22

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

3 Call Forwarding Supplementary Service

Table 3-13 CDR creation principles Subscriber Type A, B, and C are GSM/UMTS subscribers and belong to the same MSC. CDR Creation Principle For subscriber A: The MSC creates a Mobile Originated Call (MOC) CDR with the A as the caller, B as the callee, and C as the third party. For subscriber B: The MSC creates a call forwarding CDR, with B as the caller, C as the callee, and A as the third party. The service feature indication is CALL_FORWARD_OTHER. For subscriber C: The MSC creates a Mobile Terminated Call (MTC) CDR with B as the caller, C as the callee, and A as the third party. A and B are GSM/UMTS subscribers and C is a PSTN subscriber. For subscriber A: The MSC where A resides creates a Mobile Originated Call (MOC) CDR, with A as the caller, B as the callee, and C as the third party. For subscriber B: The MSC where B resides creates a call forwarding CDR, with B as the caller, C as the callee, and A as the third party. The service feature indication is CALL_FORWARD_OTHER. The GSM or UMTS gateway creates a GWO CDR with B as the caller and C as the callee. A is a PSTN subscriber and B and C are GSM/UMTS subscribers. For subscriber C: The MSC where C resides creates a Mobile Terminated Call (MTC) CDR with B as the caller, C as the callee, and A as the third party. For subscriber B: The GSM or UMTS gateway creates a call forwarding CDR, with B as the caller, C as the callee, and A as the third party. The service feature indication is CALL_FORWARD_OTHER. A ROAM CDR with A as the caller and B as the callee is created at the GSM or UMTS gateway for trunk charging. A and C are PSTN subscribers and B is a GSM or UMTS subscriber. 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. The GSM or UMTS GWI creates a call forwarding CDR for B, with B as the caller, C as the callee, and A as the third party. The service feature indication is CALL_FORWARD_OTHER. The GSM or UMTS GWO creates a GWO CDR with B as the caller and C as the callee for trunk charging.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

3-23

3 Call Forwarding Supplementary Service

HUAWEI MSOFTX3000 Feature Description

To create gateway CDRs, 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. To create ROAM CDRs, you need to set the General Bill Control as follows: Execute the MOD GBILLCTRL command and select ROAM in Ticket Control Flag.

3.8 Service Interaction


This section describes the interaction between the call forwarding services and other services.

3.8.1 CFU
Table 3-14 lists the interaction between the CFU and other services. 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. The forwarded-to subscriber subscribes to the CLIP service. The caller does not activate CLIP service. CFU and CLIR The CFU has no interaction with the CLIR. That is, if the caller subscribes to and activates CLIR, the forwarded-to subscriber cannot display the MSISDN of the caller unless the forwarded-to subscriber has the override capability. CFU and COLP If the callee forwards a call without notifying the caller, the caller cannot receive the call forwarding notification. When the call is answered, the number of the forwarded-to subscriber is not presented to the caller unless the forwarded-to subscriber has the override capability. In other cases, CFU has no interaction with COLP. CFU and COLR The CFU 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.

3-24

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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

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)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

In the Universal Mobile Telecommunications System (UMTS), if the PI value of a caller is Restrict providing, the network may send Cause of No CLI. Cause of No CLI

Unavailable Reject by user Interaction with other services Coin line or pay phone

4.1.3 Types
Line identification services are classified into CLIP, CLIR, COLP and COLR. Name CLIP Definition CLIP is a supplementary service provided for callees. The service provides calling line identification for callees. CLIP and CLIR are mutually exclusive. That is, when a callee activates the CLIP and the caller activates the CLIR, service conflict occurs. In general, the CLIR enjoys higher priority than the CLIP. Therefore, when service conflict occurs, the system processes according to the CLIR service. But if Override Category of the CLIP is Enable, the system processes according to the CLIP when service conflict occurs. CLIR CLIR is a supplementary service provided for callers. The service restricts that calling line identification is provided for callees. Carriers can provide the CLIR service for subscribers in permanent, temporary allowed and temporary restricted modes. Permanent mode: The CLIR service is invoked for every call. Temporary allowed mode: In default status, the CLIR service is not invoked. Subscribers can invoke the CLIR service temporarily through the menus of some mobile phones. Temporary restricted mode: In default status, the CLIR service is invoked. Subscribers can suppress the CLIR service temporarily through the menus of some mobile phones. COLP COLP is a supplementary service provided for callers. The service provides connected line identification for callers. COLP and COLR are mutually exclusive. That is, when a caller activates the COLP and the callee activates the COLR, service conflict occurs. In general, the COLR enjoys higher priority than the COLP. Therefore, when service conflict occurs, the system processes according to the COLR service. But if Override Category of the COLP is Enable, the system processes according to the COLP when service conflict occurs. COLR COLR is a supplementary service provided for callers. If a subscriber is a callee, the service restricts that connected line identification is provided for callers.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-3

4 Line Identification Service

HUAWEI MSOFTX3000 Feature Description

4.1.4 Benefits
Table 4-2 lists the beneficiaries and description of the benefits. Table 4-2 Beneficiaries and description of the benefits Beneficiary Carriers Mobile subscribers Description The line identification services add values of services. After the CLIP service is provided, a subscriber can identify callers based on numbers presented by Mobile Station (MS) to determine whether to answer phones. Also, if the subscriber is unavailable to answer, the subscriber can reply later based on presented numbers. After the CLIR service is provided, a subscriber numbers is not presented on the MS of callee. Thus, the caller number can be kept secret. After the COLP service is provided, if a callee activates forwarding service and notifies the caller, forwarding number is presented on the MS of the caller. After the COLR service is provided, a called number is not presented on the MS of caller. After the COLR service is provided for a forwarding subscriber, forwarding number is not presented on the MS of caller.

4.2 Availability
4.2.1 Requirements for NEs
Table 4-3 lists the network elements (NEs) required by the line identification services. 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; MS = mobile station; BTS = base transceiver station; RNC = radio network controller; BSC = base station controller; MSC = mobile switching center; MGW = media gateway; SGSN = serving GPRS support node; VLR = visitor location register; HLR = home location register

The symbol indicates that the corresponding NE is required. The hyphen - indicates that the corresponding NE is not required.

4-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

4.2.2 Requirements for License


The line identification services are basic services of Huawei wireless core network. No license is needed.

4.2.3 Applicable Versions


Table 4-4 lists the applicable versions of Huawei wireless core network products that the line identification services support. Table 4-4 Applicable versions of Huawei wireless core network products Product MSC server MSOFTX3000 Applicable Version V100R002 and later versions

4.3 Working Principle


4.3.1 Service Data Management
The HLR performs the following functions: Completes the management operations of carriers on service data. Modifies the subscription information that it stores. Updates the subscription information in the VLR by inserting subscriber data.

4.3.2 CLIP
The following section describes the working principle of the CLIP service: The Gateway MSC (GMSC) obtains CLI, PI, SI and possible aCLI, aPI and aSI from the VLR or incoming signaling, configures them in outgoing signaling and then sends them to the MSC of callee. Based on the earlier mentioned information and callee CLIP subscription information stored in the VLR, the MSC of callee determines whether to send CLI information to the callee.

4.3.3 CLIR
The following section describes the working principle of the CLIR service: A subscriber initiates a call. (For subscribers that subscribe CLIR temporary mode, the parameter whether to invoke the CLIR may be sent at that time.) The MSC of caller determines CLI, PI and SI in outgoing signaling based on CLIR subscription information stored in the VLR and CLI, PI and SI in A interface signaling. The MSC of caller sends corresponding CLI information in the outgoing signaling.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-5

4 Line Identification Service

HUAWEI MSOFTX3000 Feature Description

4.3.4 COLP
The following section describes the working principle of the COLP service: When a callee answers the phone, the answer message sent by the MSC of callee to the MSC of caller carries COL, PI, SI and possible aCOL, aPI and aSI information. Based on COL, PI, SI and possible aCOL, aPI and aSI in incoming signaling, and caller COLP subscription information stored in the VLR, the MSC of caller sets the COL information to be sent to the caller. The MSC of caller sends answer message with COL information to the caller.

4.3.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, PI and SI. The MSC of callee sets COI, 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 in A interface signaling. The MSC of callee sends answer message with COL, PI and SI to the MSC of caller.

4.4 Service Flow


4.4.1 CLIP
Figure 4-1 shows the CLIP service flow. Figure 4-1 CLIP service flow
MS/PSTN (G)MSC server HLRb MSC server b MS

SETUP(CLIPBN) or IAM(CLIPN,GN)

SRI PRN PRN ack SRI ack IAM(CLIPN,GN,CoNC) SETUP(CLIPBN,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.

If a caller is the MS, the MS sends the SETUP message to the MSC server. The parameter Calling Party BCD Number in the message contains CLI, PI and SI. If the

4-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

caller is a fixed network subscriber, the Public Switched Telephone Network (PSTN) sends originated call message (such as the IAM message) to the GMSC server through trunk signaling. The parameter Calling Party Number in the originated call message contains CLI, PI and SI. In addition, the originated call message may contain parameters Generic number and Cause of NO CLI. The Generic number contains aCLI, aPI and aSI. 2. 3. 4. The (G)MSC server initiates the SRI operation to the HLRb. The HLRb initiates the PRN operation to the MSC server b (VLR). After obtaining the roaming number, the (G)MSC server transfers the originated call message to the MSC server b. The message contains the Calling Party Number and possible Generic number and Cause of NO CLI. The MSC server b sets Calling Party BCD Number and possible Cause of NO CLI in the SETUP message based on received CLI, PI and SI in the Calling Party Number, aCLI, aPI and aSI in the Generic number, Cause of NO CLI and CLIP subscription information. The MSC server b sends the SETUP message to the callee.

5.

6.

4.4.2 CLIR
Figure 4-2 shows the CLIR service flow. Figure 4-2 CLIR service flow
MS MSC server (G)MSC server

SETUP(CLIPBN,CLIR suppression or CLIR invocation) IAM(CLIPN,CoNC)

CLIPBN: Calling Party BCD Number CLIPN: Calling Party Number

IAM: Initial Address Message CoNC: Cause of NO CLI

1.

The MS sends the SETUP message to the GMSC server. The parameter Calling Party BCD Number in the message contains CLI, PI and SI. If CLIR service s in temporary allowed mode, when a subscriber invokes the CLIR service through the menu of mobile phone, the SETUP message contains the parameter CLIR invocation. If the CLIR service is in temporary restricted mode, when a subscriber shields the CLIR service through the menu of mobile phone, the SETUP message contains the parameter CLIR suppression. 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, CLIR invocation, CLIR suppression and CLIR subscription information. The Calling Party Number contains CLI information. The MSC server sends the originated call message to called office.
If the SETUP message contains the parameter CLIR invocation and the subscriber does not subscribe the CLIR service, the MSC server directly end the call. If the call triggers some special application in the MSC server, the originated call message may contain the Generic number.

2.

3.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-7

4 Line Identification Service

HUAWEI MSOFTX3000 Feature Description

4.4.3 COLP
Figure 4-3 shows the COLP service flow. Figure 4-3 COLP service flow
MS MSC server (G)MSC server PSTN/MS

ANM(CON number,GN) CONNECT(CON number)

CONNECT or ANM(CON number,GN)

CON: Connected GN: Generic number

ANM: Answer Message

1.

If a callee is the MS, when the MS answers, it sends the CONNECT message to the MSC server. Based on the callee COLR subscription information, 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. The value of Connected number contains COL, PI and SI. If the call triggers some special application in the MSC server, the answer message may contain Generic number that contains aCOL, aPI and aSI information. If the callee is a fixed network subscriber, the GMSC server transparently transmits the received answer message (such as the ANM message). The answer message contains Connected number and possible Generic number. The (G)MSC server sends the answer message to the MSC server of caller. The MSC server sets the parameter Connected number in the CONNECT message based on received COL, PI, SI, possible aCOL, aPI and aSI, and COLP subscription information. The Connected number contains COL, PI and SI. The MSC server of caller sends the CONNECT message to the caller.

2. 3.

4.

4.4.4 COLR
Figure 4-4 shows the COLR service flow. 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)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

1. 2.

When the MS answers, it sends the Connect message to the MSC server. The MSC server sets the value of Connected number in the answer message (such as the ANM message) to be sent to calling office. The value of Connected number contains COL, PI and SI. The MSC server sends the answer message to the calling office.

3.

4.5 Data Configuration


4.5.1 Configuring Data at the MSOFTX3000 Side
For the details of data configuration, see the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Enabling the Service


No additional data is required to enable the service.

Changing Caller Number Presentation


When the MSOFTX3000 acts as a landing office, it can change caller number presentation for different caller numbers, call sources and called numbers related to caller numbers. The change procedure is listed as follows: Step 1 If necessary, run ADD DNC to add number change format. Step 2 Run ADD CLIPRO to add a caller number and call source thus to change caller number presentation. Step 3 If necessary, run ADD CLCRPRO to add a called number related to the caller number thus to change caller number presentation. ----End The following table lists an example: Description Script For a caller number with call source name A and started with 60139, delete the prefix 60 when the caller number is presented. ADD DNC: DCN="DEL60", DCT=TYPE6, DCL=2; ADD CLIPRO: CSN="A", CLDCORNAME="DEL60"; CLIPFX=K'60139, CLIMAXLEN=13,

Changing Connected Number


When the MSOFTX3000 acts as an originating office, it can change connected numbers for different connected numbers and call sources. The change procedure is listed as follows: Step 1 If necessary, run ADD DNC to add number change format. Step 2 Run ADD AIDNUMPRO to add called number and call source thus to change connected number.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-9

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, add prefix 0 in front of it. ADD DNC: DCN="ADD0", DCT=TYPE1, ND=K'0; ADD AIDNUMPRO: CSCNAME="A", NUMTY=TY0, PFX=K'755, CDN="ADD0";

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 signaling is incoming office or converted into No.7 signaling. It indicates whether to release when a subscriber has the CLIR request if the subscriber does not subscribe the CLIR service. It indicates whether the PI value in caller number parameter is set to CLI not available. It indicates whether the PI value in connected number parameter is set to COL not available. It controls the realization of COLR and CLIR functions. Value = 0: Allow a caller number to be presented. = 1: Not allow a caller number to be presented. Default Value 1

P51 (Call internal parameter 3) Bit 3

= 0: Not release. = 1: Release.

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. = 1: Process based on protocol. = 0: The PI value in connected number parameter is set to COL not available. = 1: Process based on protocol. = 0: Provide COLR and CLIR services based on subscriber subscription information. = 1: The VLR forces COLR and CLIR supplementary services are provided whether they are subscribed.

4-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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.

Value = 0: Set CLIR for all subscribers forcibly. = 1: Set CLIP for all subscribers forcibly. = 11: Determine the realization of CLIP/CLIR function based on 3GPP protocol.

Default Value 3

4.5.2 Configuring Data at the HLR Side


No data related to the service needs to be configured at the HLR side.

4.6 Service Management


The line identification services have two operation modes, 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. Withdraw the service. In temporary allowed mode, invoke the CLIR service. In temporary restricted mode, suppress the CLIR service. as listed in Table 4-5.

For supplementary line identification services, the services are activated when they are provided, and the services are deactivated when they are withdrawn.

4.6.1 Opreations by Carriers


For details, see the corresponding operation manual of the HLR.

4.6.2 Operations by Mobile Subscribers


Prerequisite
The system has provided the CLIR service in temporary allowed or temporary restricted mode for subscribers.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-11

4 Line Identification Service

HUAWEI MSOFTX3000 Feature Description

Operations
On the MS, mobile subscribers can perform the operations listed in Table 4-6. Table 4-6 CLIR service operation performed by mobile subscribers Operation Type In temporary allowed mode, invoke the CLIR service. In temporary restricted mode, suppress the CLIR service. Step On the MS, dial "#31#DN", and then press the Send key. Of it, DN refers to a called number.

On the MS, dial "*31#DN", and then press the Send key. Of it, DN refers to a called number.

Subscribers can also perform the operations through the menus of some mobile phones. For details, see the user manuals of the mobile phones.

4.7 Service Interaction


4.7.1 CLIP
Table 4-7 lists the interactions between the CLIP service and other services. Table 4-7 Interactions between the CLIP service and other services Service CLIP and CLIR Interaction In general, the CLIR service enjoys higher priority than the CLIP service. When a callee activates the CLIP service and the caller activates the CLIR service, the system processes according to the CLIR service. But if the CLIP property of the callee is OVERRIDE, the system processes according to the CLIP service. CLIP and CFU, CFB, CFNRy and CFNRc If the system provides the CLIP to a callee and the caller does not activate the CLIR service, when forwarding occurs, the caller number is presented to the callee according to the CLIP service. For example, subscriber A calls subscriber B. The call is forwarded to subscriber C. If C activates the CLIP service and A does not activate the CLIR service, the MS of C can present the number of A. CLIP and CW The CLIP and CW services are compatible. If a subscriber activates CLIP and CW service, calls are processed according to the CW service. In addition, the MS of the subscriber can present caller numbers.

4-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

4.7.2 CLIR
Table 4-8 lists the interactions between the CLIR service and other services. Table 4-8 Interactions between the CLIR service and other services Service CLIR and CLIP Interaction In general, the CLIR service enjoys higher priority than the CLIP service. When a callee activates the CLIP service and the caller activates the CLIR service, the system processes according to the CLIR service. But if the CLIP property of the callee is OVERRIDE, the system processes according to the CLIP service. CLIR and CFU, CFB, CFNRy and CFNRc The CLIR and forwarding services are compatible. If a caller activates the CLIR service, 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. For example, subscriber A activates the CLIR service. A calls B. The call is forwarded to subscriber C. The MS of C cannot present the number of A.

4.7.3 COLP
Table 4-9 lists the interactions between the CLIP service and other services. Table 4-9 Interactions between the COLP service and other services Service COLP and COLR Interaction In general, the COLR service enjoys higher priority than the COLP service. When a caller activates the COLP service and the callee activates the COLR service, the system processes according to the COLR service. But if the COLP property of caller is OVERRIDE, the system processes according to the COLP service. COLP and MPTY If a subscriber activates both COLP and MPTY service. When the subscriber is a main controller, the COLP and MPTY services are compatible. When the subscriber is remote (participant of the MPTY service) the subscriber cannot receive COLP supplementary service information of other meeting participants.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

4-13

4 Line Identification Service

HUAWEI MSOFTX3000 Feature Description

Service COLP and CFU, CFB, CFNRy and CFNRc

Interaction The COLP and forwarding services are compatible. If a caller activates the COLP service and the forwarded subscriber does not activate the COLR service, when the callee is forwarded, the callee notifies the caller. The MS of caller presents callee numbers. If the callee activates the forwarding service and selects not to notify the caller when forwarding occurs, the MS of caller cannot present the callee number unless the property of caller is OVERRIDE.

4.7.4 COLR
Table 4-10 lists the interactions between the COLR service and other services. Table 4-10 Interactions between the COLR service and other services Service COLR and COLP Interaction In general, the COLR service enjoys higher priority than the COLP service. When a caller activates the COLP service and the callee activates the COLR service, the system processes according to the COLR service. But if the COLP property of caller is OVERRIDE, the system processes according to the COLP service. COLR and CFU, CFB, CFNRy and CFNRc If a forwarded subscriber activates the COLR service, the forwarding notification does not provide the number of forwarded subscriber. If a caller activates the COLP service and the property of caller is OVERRIDE, the forwarding notification does not provide the number of forwarded subscriber, but the COLP service can be invoked to present callee numbers.

4.8 Reference
4.8.1 Protocols and Specifications
This following specifications and manuals are referred to: 3GPP TS 22.081 V4.1.0 3GPP TS 23.081 V4.1.0 3GPP TS 24.081 V4.1.0 3GPP TS 24.008 V4.15.0 3GPP TS 29.002 V4.15.0

4-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

4 Line Identification Service

HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide HUAWEI HLR9820 Home Location Register Subscriber Management

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

HUAWEI MSOFTX3000 Feature Description

Contents

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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 5-1 Service flow when a subscriber accepts a waiting call .....................................................................5-7 Figure 5-2 Service flow when a subscriber rejects a waiting call.......................................................................5-9 Figure 5-3 Service flow for holding and retrieving a call.................................................................................5-10 Figure 5-4 Service flow for alternating from the A-B call to the A-C call ....................................................... 5-11

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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...............................................................................5-2 Table 5-3 Beneficiaries and description of the benefits ......................................................................................5-3 Table 5-4 NEs required by the call completion supplementary services ............................................................5-3 Table 5-5 Applicable versions of Huawei wireless core network products ........................................................5-4 Table 5-6 Related software parameters.............................................................................................................5-13 Table 5-7 Operation modes of the call completion supplementary services.....................................................5-14 Table 5-8 Operations performed by mobile subscribers ...................................................................................5-15 Table 5-9 Interactions between the CW service and other services ..................................................................5-18 Table 5-10 Interactions between the CH service and other services.................................................................5-19

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

5 Call Completion Supplementary Service

Call Completion Supplementary Service

About This Chapter


The following table lists the contents of this chapter. Section 5.1 Service Description 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.

5.2 Availability

5.3 Working Principle 5.4 Service Flow 5.5 Data Configuration 5.6 Service Management

5.7 Charging and CDR 5.8 Service Interaction 5.9 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-1

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

5.1 Service Description


5.1.1 Function Code
Table 5-1 lists the name and code of the function. Table 5-1 Name and code of the function Name Call completion supplementary services Code WMFD-020400

5.1.2 Definition
The call completion supplementary services provide two services: call waiting (CW) and call hold (CH). Subscribers can choose either one to process two calls at the same time. Table 5-2 lists the name and definition of the CW and CH services. 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 subscriber is in conversation, or has a call on hold. The subscriber can determine to accept, reject, or ignore the incoming call. The caller receives notifications during call waiting. For one subscriber, only one waiting call is allowed, and the system disconnects the subsequent incoming calls instantly. CH The CH service enables a mobile subscriber to interrupt the current call temporarily, and retrieve the call later if required. When the call is interrupted, the system reserves the traffic channel allocated for the call. When a call is on hold, and no active call is set up, a subscriber can: Retrieve the held call. Set up an active call. Disconnect the held call. When a call is on hold, and an active call is set up, the subscriber can: Alternate from one call to the other. Disconnect the active call. Disconnect the held call. Disconnect both the active call and the held call. For one subscriber, only one held call is allowed.

5-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

5 Call Completion Supplementary Service

5.1.3 Benefits
Table 5-3 lists the beneficiaries and description of the benefits. Table 5-3 Beneficiaries and description of the benefits Beneficiary Carriers Mobile subscribers Description The call completion supplementary services add values of services, and improve the call completion rate. Subscribers can activate and deactivate the CW service freely. This indicates that subscribers can control the CW service flexibly. After the CW service is activated, a subscriber can answer another call in conversation. Therefore, the subscriber can select the one that is more important. When the CH service is activated, a subscriber can hold the current call, and answer another call. This minimizes the possibility of missing calls, and improves the call completion rate.

5.2 Availability
5.2.1 Requirements for NEs
Table 5-4 lists the network elements (NEs) required by the call completion supplementary services. 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; MS = mobile station; BTS = base transceiver station; RNC = radio network controller; BSC = base station controller; MSC = mobile switching center; MGW = media gateway; SGSN = serving GPRS support node; VLR = visitor location register; HLR = home location register

The symbol indicates that the corresponding NE is required. The hyphen - indicates that the corresponding NE is not required.

5.2.2 Requirements for License


The call completion supplementary services are basic services of Huawei wireless core network. No license is required.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-3

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

5.2.3 Applicable Versions


Table 5-5 lists the applicable versions of Huawei wireless core network products that the call completion supplementary services support. 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.3 Working Principle


5.3.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, the MSC transparently sends the operation message to the HLR. The HLR modifies the subscription information stored in the HLR based on the message, and then updates the subscription information in the VLR by inserting subscriber data. For the CH service, there is no activation or deactivation operation.

5.3.2 Working Principle of CW


The following section describes the working principle of the CW service. When subscriber B is in conversation, the MSC receives a call from C to B (a C-B call). The MSC queries the subscription information of B. If the CW service is activated for B, the MSC processes the CW service. The MSC sends a SETUP message for setting up the C-B call to the MS. The message carries a CW indication. Currently, an A-B call is active or on hold. Therefore, the MS informs B of the incoming call based on the CW indication. At the same time, the MS sends a response to the MSC, indicating that B is busy. After receiving the response, the MSC waits for the ALERTING message from the callee.

5-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

5 Call Completion Supplementary Service

Upon receiving the ALERTING message, the MSC starts the CW timer T2 and the no-reply timer T3. The MSC then waits for the answer of B. At the same time, the MSC sends an ALERTING or ACM message to C, carrying the CW indication. Before B answers or disconnects the call, the MSC of B plays an announcement to C, instructing C to wait for the call. If B answers before T2 and T3 time out, the MS sends a CONNECT message to the MSC for connecting the C-B call. The MSC sends a response to the MS, and sends an acknowledge to C, indicating that the C-B call is set up. If B rejects the call before T2 and T3 time out, the MSC follows the normal flow to disconnect the waiting call. If T2 or T3 times out, the MSC sends a DISCONNECT message to B and C respectively, instructing them to release the C-B call.

5.3.3 Working Principle of CH


Overview
The following sections describe the working principle of the CH service, including two parts Holding a call Retrieving a call

Holding a Call
The following section describes the working principle for holding a call. 1. 2. 3. 4. A holds the call when A is in conversation with B. MS A sends a HOLD request to the MSC. The MSC queries the subscription information of A. If the CH service is activated for A, the MSC processes the CH service. The MSC determines whether to accept the request for the CH service based on the CH activation indication and other factors, for example, whether there is a held call. If the MSC rejects the request, it returns a HOLD REJECT message to MS A. The conversation between A and B continues. If the MSC accepts the request, it returns a HOLD ACKNOWLEDGE message to MS A, reserves the channel allocated for the current call, and sends a message to B or the MSC of B at the same time to notify B.

5.

Retrieving a Call
The following section describes the working principle for retrieve a call. 1. 2. 3. 4. A retrieves the A-B call. MS A sends a RETRIEVE request to the MSC. If the MSC rejects the request, it returns a RETRIEVE REJECT to MS A. The conversation between A and B continues. If the MSC accepts the requests, it returns a RETRIEVE ACKNOWLEDGE message to MS A, retrieves the connection of the original channel, and sends a message to B or the MSC of B at the same time to notify B.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-5

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

5.

If an A-C call is active, A returns a HOLD ACKNOWLEDGE message to the MS before 4, converts the active call to a held call, and sends a message to C and the MSC of C at the same time.

5.4 Service Flow


5.4.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. An A-B call is active. The fixed network subscriber C calls B. B accepts the waiting call. Figure 5-1 shows the call flow.

5-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. 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. 2. 3. 4. 5. 6. The PSTN subscriber C sends an IAM message to the gateway mobile switching center (GMSC) server. 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. MSC server B sends a SETUP message to MS B. The value of the Signal Information element in the message is 7 (call waiting tone on). MS B returns a CALL CONFIRMED message. The value of the Cause information element in the message is 17 (user busy). MSC server B allocates channels with the BSC or RNC. MS B sends an ALERTING message.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-7

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

7.

MSC server B sends an ACM message to the GMSC server, carrying a CW indication. MSC server B then follows the indication to play an announcement to C, instructing C to wait for the call. If B answers, MS B sends a CONNECT message to MSC server B. MSC server B returns a CONNECT ack message to MS B.

8. 9.

10. MSC server B sends an ANM message to the GMSC server, instructing C to answer. 11. The B-C call is set up.
The transaction identifier of the signaling messages for the B-C call is different from that for the A-B call. Thus MS B and MSC server B can identify the signaling messages.

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. An A-B call is active. The fixed network subscriber C calls B. B rejects the waiting call. Figure 5-2 shows the call flow.

5-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. 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. 2. 3. 4. 5. 6. 7. The PSTN subscriber C sends an IAM message to the GMSC server. The GMSC server forwards the IAM message to MSC server B after obtaining the MSRN of MS B by sending an SRI request. MSC server B sends a SETUP message to MS B. The value of the Signal Information element in the message is 7 (call waiting tone on). MS B returns a CALL CONFIRMED message. The value of the Cause information element in the message is 17 (user busy). MSC server B allocates channels with the BSC or RNC. MS B sends an ALERTING message. MSC server B sends an ACM message to the GMSC server, carrying a CW indication. MSC server B then follows the indication to play an announcement to C, instructing C to wait for the call. If B rejects the call, MS B sends a DISCONNECT message to MSC server B. The value of the Cause information element in the message is 17 (user busy).

8.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-9

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

9.

MSC server B returns a RELEASE message to release the B-C call.

10. MS B returns a RELEASE COMPLETE message, indicating that the release of the B-C call is complete at the MS side. 11. MSC server B sends an REL message to the GMSC server for call release. The value of the Cause information element is 17 (user busy). 12. The GMSC server returns an RLC message, indicating that the call release is complete.
The transaction identifier of the signaling messages for the B-C call is different from that for the A-B call. Thus MS B and MSC server B can identify the signaling messages.

5.4.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. B is a mobile subscriber. Figure 5-3 shows the service flow. 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. HOLD HOLD ack CPG FACILITY CALL A-B on HOLD

A wants to retrieve the A-B call. RETRIEVE RETRIEVE ack CPG FACILITY CALL A-B ACTIVE

CPG: Call Progress

ack: Acknowledge

5-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

5 Call Completion Supplementary Service

The service flow for holding and retrieving a call is as follows: 1. 2. 3. 4. When A wants to hold the current A-B call, MS A sends a HOLD message to MSC server A, requesting MSC server A to hold the call. MSC server A accepts the request, and returns a HOLD ack message to MS A. MSC server A sends a CPG message to MSC server B, carrying a notification for remote hold. MSC server B sends a FACILITY message to MS B. In the message, the invoke component is NotifySS, in which CallOnHold-indicator is callOnHold. The message is used to inform MS B that the call is on hold. When A wants to retrieve the A-B call, MS A sends a RETRIEVE message to MSC server A, requesting MSC server A to retrieve the call. MSC server A accepts the request, and returns a RETRIEVE ack message to MS A. MSC server A sends a CPG message to MSC server B, carrying a notification for remote retrieve. MSC server B sends a FACILITY message to MS B. In the message, the invoke component is NotifySS, in which CallOnHold-indicator is callRetrieved. The message is used to inform MS B that the call is retrieved.

5. 6. 7. 8.

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. An A-B call is active. An A-C call is on hold. B and C are mobile subscribers. Figure 5-4 shows the service flow for alternating from the A-B call to the A-C call. 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, call A-C on hold A wants to alternate from the A-B call to the A-C call. HOLD RETRIEVE HOLD ack CPG RETRIEVE ack CPG FACILITY Call A-B on hold, 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

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. When A wants to alternate from the A-B call to the A-C call, MS A sends a HOLD request to MSC server A for holding the A-B call, and a RETRIEVE request for retrieving the A-C call. MSC server A accepts the request, and returns a HOLD ack message to MS A. MSC server A sends a CPG message to MSC server B, carrying a notification for remote hold. MSC server B sends a FACILITY message to MS B. In the message, the invoke component is NotifySS, in which CallOnHold-indicator is callOnHold. The message is used to inform MS B that the call is on hold. MSC server A accepts the request, and returns a RETRIEVE ack message to MS A. MSC server A sends a CPG message to MSC server C, carrying a notification for remote retrieve. MSC server C sends a FACILITY message to MS C. In the message, the invoke component is NotifySS, in which CallOnHold-indicator is callRetrieved. The message is used to inform MS B that the call is retrieved.
The transaction identifier of the signaling messages for the A-C call is different from that for the A-B call. Thus MS A and MSC server A can identify the signaling messages.

2. 3. 4.

5. 6. 7.

5.5 Data Configuration


5.5.1 Configuring Data at the MSOFTX3000 Side
Overview
For the details of data configuration, see HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Enabling the Service


No additional data is required to enable the service.

Generating CDRs
The command MOD GBILLCTRL is used to generate the call detail records (CDRs) of the CW and CH services.

Related Software Parameters


Table 5-6 lists the related software parameters.

5-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. Value = 0: If the callee who has registered with the CW service is busy, the caller hears the call waiting tone. When A and B are in conversation, C calls B. If the caller A has not registered with the call forwarding service, an ALERTING message containing FACILITY-IE is sent to inform C of the CW service. If A has registered with the call forwarding service, an ALERTING message containing FACILITY-IE is sent to inform C of the CW service. When the CW service interacts with the ring back tone (RBT) service, the caller hears the call waiting tone if the callee is in the same office. The caller hears the tone from another office if the callee is in another office. = 1: If the callee who has registered with the CW service is busy, the caller hears the ringback tone. When A and B are in conversation, C calls B. If the caller A has not registered with the call forwarding service, no ALERTING message containing FACILITY-IE is sent to inform C of the CW service. If A has registered with the call forwarding service, an ALERTING message containing FACILITY-IE is sent to inform C of the CW service. When the CW service interacts with the RBT service, the caller hears the RBT. P20 (ISUP Operation Reserved Parameter 3) Bit 4 It determines whether to play the call hold tone. = 0: Play the ringback tone. = 1: Play the call hold tone. 1 Default Value 1

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-13

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. It determines whether to generate event CDRs when the subscriber, in call active state, invokes the CW service.

Value = 0: Generate intermediate CDRs. = 1: Generate event CDRs.

Default Value 1

P130 (CHG Parameter 2) Bit 10

= 0: Generate event CDRs. = 1: Not generate event CDRs.

5.5.2 Configuring Data at the HLR Side


No data related to the service needs to be configured at the HLR side.

5.6 Service Management


5.6.1 Overview
The call completion supplementary services have two operation modes, as listed in Table 5-7. Table 5-7 Operation modes of the call completion supplementary services Operation Mode Operations by carriers Operation Interface HLR Service Operations Provide the service. Withdraw the service. Activate the service (for the CW service only). Deactivate the service (for the CW service only).

5-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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). Deactivate the service (for the CW service only). Release and reject a waiting call. Hold an active call, and accept a waiting call. Set up a call, and hold the original active call. Accept a waiting call, and hold an active call. Alternate from an active call to a held call. Retrieve a held call, and release an active call. Release a held call. Release both the active call and the held call.

For the CH service, the service is activated when it is provided, and the service is deactivated when it is withdrawn.

5.6.2 Operations by Carriers


For details, see the corresponding operation manual of the HLR.

5.6.3 Operations by Mobile Subscribers


Prerequisite
The CW or CH service is provided for mobile subscribers.

Operations
On the MS, mobile subscribers can perform the operations listed in Table 5-8. Table 5-8 Operations performed by mobile subscribers Service Type CW CW Operation Type Activate the CW service. Deactivate the CW service. Step On the MS, dial "43#", and then press the Send key. On the MS, dial "#43#", and then press the Send key.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-15

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

Service Type CW

Operation Type Release and reject a waiting call. Release an active call, and answer a waiting call. Hold an active call, and accept a waiting call. Set up a call, and hold the original active call. Alternate from an active call to a held call. Retrieve a held call, and release an active call. Release a held call. Release both the active call and the held call.

Step On the MS, dial "0", and then press the Send key.

CW

On the MS, dial "1", and then press the Send key.

CW

On the MS, dial "2", and then press the Send key.

CH

On the MS, dial the called number of the new call, and then press the Send key. On the MS, dial "2", and then press the Send key.

CH

CH

On the MS, dial "1", and then press the Send key.

CH CH

On the MS, dial "0", and then press the Send key. On the MS, press the Release key.

Subscribers can also perform the operations through the menus of some mobile phones. For details, see the user manuals of the mobile phones.

5.7 Charging and CDR


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

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. 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 CW indicator and time stamp are in the last CDR. 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. Usually, independent charging is adopted. The following gives an example of independent charging for the CW service. The scenario is as follows: A in the local office calls B in another office. C in another office calls A when A is in conversation with B. The supplementary service domain in the MOC CDR generated by the local office for the A-B call records the supplementary service operation. The supplementary service indicator is CW, and the time stamp is the time when a SETUP message is sent to A.

5.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. Segment charging means that the MSOFTX3000 generates an intermediate MOC or MTC CDR at the time of the hold and retrieve operations. The billing center combines the group of CDRs and processes other charging. The CH indicator and time stamp are in the last CDR. 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. Usually, independent charging is adopted. The following gives an example of independent charging for the CH service. The scenario is as follows: A in the local office calls B in another office. A holds the call when A is in conversation with B. The supplementary service domain in the MOC CDR generated by the local office for the A-B call records the supplementary service operation. The supplementary service indicator is CH, and the time stamp is the time when A sends a HOLD message.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-17

5 Call Completion Supplementary Service

HUAWEI MSOFTX3000 Feature Description

5.8 Service Interaction


5.8.1 CW
Table 5-9 lists the interactions between the CW service and other services. 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. When a callee who has both the CW and CFU services activated is called, the incoming call is forwarded unconditionally based on the CFU service, instead of being processed based on the CW service. CW and CFB The CW and CFB services are compatible. If the callee is NDUB, the system directly processes the incoming call based on the CFB service, without notifying the subscriber. If the callee is UDUB, the system notifies the subscriber, and the subscriber determines how to process the incoming call (process it based on the CFB or CW service). CW and CFNRy If both CFNRy and CW services are activated, a subscriber can receive the CW indication when serving as the callee. If the subscriber does not send any response before the expiry of the No Reply Condition timer, the call is processed based on the CFNRy service. If both CW and CH services are activated, a subscriber can use the CH service to answer a waiting call. If the subscriber is in conversation, and has a call on hold, the subscriber can still receive a CW indication, but cannot answer the call. If the subscriber is not in conversation, but has a call on hold, the subscriber can receive a CW indication. CW and CLIP The CLIP and CW services are compatible. If both CLIP and CW services are activated, the incoming call is processed based on the CW service, and the MS of the subscriber displays the number of the caller. The CW and MPTY services are compatible. If a subscriber has an active MPTY call, the subscriber can receive a CW indication when being called. When holding the MPTY call, the subscriber can answer the waiting call. CW and BAIC CW and BIC-ROAM The BAIC service takes precedence over the CW service. When the BAIC service is activated, the CW service cannot be activated. The activation of the BAIC service does not affect any waiting call. The BIC-ROAM service takes precedence over the CW service. When roaming out of the HPLMN, a subscriber cannot activate the CW service if the BIC-ROAM service is activated. The activation of the BIC-ROAM service does not affect any waiting call.

CW and CH

CW and MPTY

5-18

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

5 Call Completion Supplementary Service

Service

Interaction

Note: CFU = call forwarding unconditional; NDUB= network determined user busy; UDUB = user determined user busy; CFNRy = call forwarding no reply; CLIP = calling line identification presentation; MPTY = multiparty service; BAIC = barring of all incoming calls; BIC-ROAM = barring of incoming calls when roaming outside home PLMN country

5.8.2 CH
Table 5-10 lists the interactions between the CH service and other services. Table 5-10 Interactions between the CH service and other services Service CH and CW Interaction If both CW and CH services are activated, a subscriber can use the CH service to answer a waiting call. If the subscriber is in conversation, and has a call on hold, the subscriber can still receive a CW indication, but cannot answer the call. If the subscriber is not in conversation, but has a call on hold, the subscriber can receive a CW indication. CH and MPTY The CH and MPTY services are compatible. If both CH and MPTY services are activated, a subscriber can hold an active MPTY call, set up another call, and retrieve the MPTY call after the new call is complete.

5.9 Reference
5.9.1 Protocols and Specifications
This following specifications and manuals are referred to: 3GPP TS 22.083 V4.1.0 3GPP TS 23.083 V4.3.0 3GPP TS 23.083 V4.0.1 3GPP TS 24.008 V4.15.0 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide HUAWEI HLR9820 Home Location Register Subscriber Management

5.9.2 Acronyms and Abbreviations


Acronym/Abbreviation CW Full Name Call Waiting

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

5-19

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)

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 6-1 Setting up the MPTY call .................................................................................................................6-6 Figure 6-2 Create a personal communication.....................................................................................................6-7 Figure 6-3 Add a remote subscriber ...................................................................................................................6-7 Figure 6-4 Disconnect the remote subscriber by main controller.......................................................................6-8 Figure 6-5 Disconnect the remote subscriber by main controller.......................................................................6-9

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 6-1 Network elements involved in MPTY features...................................................................................6-3 Table 6-2 Applicable versions of the MPTY ......................................................................................................6-3 Table 6-3 Operation method for MPTY service ............................................................................................... 6-11 Table 6-4 MPTY service operation (For mobile subscriber) ............................................................................ 6-11 Table 6-5 Interactions between the MPTY and the other services....................................................................6-13

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

6 Multiparty Service

6
About This Chapter
Section 6.1 Service Description Describes 6.2 Availability

Multiparty Service

The following table lists the contents of this chapter.

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.

6.3 Working Principle 6.4 Service Flow 6.5 Data Configuration 6.6 Service Management

6.7 Charging and CDR 6.8 Service Interaction 6.9 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

6-1

6 Multiparty Service

HUAWEI MSOFTX3000 Feature Description

6.1 Service Description


6.1.1 Function Code
Function Name Multiparty SS (MPTY) BOM WMFD-020500

6.1.2 Definition
The served mobile subscriber is the mobile subscriber who can invoke the MPTY. The served mobile subscriber, namely, the main controller, controls the MPTY when the MPTY is active. The remote party is the party except the served mobile subscriber in the MPTY calls.

The MPTY provides multiple call connections for one subscriber. That is to say, three or more than three subscribers can take part in a session at the same time. The maximum number of subscribers that the MSOFTX3000 can support through the MPTY is six. When a served mobile subscriber has an active call and an on-hold call, and when both calls are answered, the served mobile subscriber can invoke the MPTY to combine the two calls to an MPTY call. In this case, the served mobile subscriber can communicate with the remote subscriber. As for the MPTY calls, the served mobile subscriber can realize the following functions: Hold the MPTY call and resume the call in subsequent sessions. Initiate a new call and hold the MPTY call. 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. Set up personal communications with the remote subscribers, namely, session separation. Disconnect a remote subscriber. Release an MPTY call.

6.1.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. Multiple subscribers can discuss together, which make the communications more convenient.

6-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

6 Multiparty Service

6.2 Availability
6.2.1 Requirements for NEs
The MPTY features are realized by co-operations of the UE/MS, MS C Server, MGW, VLR and HLR, as listed in Table 6-1. 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.

6.2.2 Requirements for License


The MPTY feature is an optional feature of HUAWEI wireless core network. The feature service can be obtained only after the MSOFTX3000 license is obtained.

6.2.3 Applicable Versions


The applicable versions of MPTY features for HUAWEI CN are as listed in Table 6-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.3 Working Principle


6.3.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. The HLR stores and manages the subscriber data and service data. The HLR updates the subscription information stored in the VLR by inserting subscriber data.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

6-3

6 Multiparty Service

HUAWEI MSOFTX3000 Feature Description

6.3.2 Service Data Management


The HLR completes the service data management and modifies the stored subscription information of subscribers. The HLR updates the subscription information stored in the VLR by inserting subscriber data.

6.3.3 MPTY Invocation


When an on hold call (A-B) and an active call (A-C) are answered, subscriber A invokes the MPTY. To invoke the MPTY, perform the following steps: 1. 2. 3. 4. 5. 6. The MS A sends the FACILITY message to MS C, to instruct the subscriber A to invoke the MPTY. After the MS C receives the message, it queries the subscription information of A. If A subscribes to the MPTY, the MS C processes the MPTY service. The MS C applies the conference call resources that are used to connect subscriber A, B and C. The MS C responses to the MS A with a message. The MS C sends a message to subscriber B, indicating the call is resumed. The MS C sends messages to B and C, instructing them to set up the MPTY.

6.3.4 MPTY Call Management


Setting up Personal Communications with Remote Subscriber
When subscriber A has an active MPTY call (A-B-C), set up a personal communication to B. To set up personal communications with remote subscribers, perform the following steps: 1. 2. 3. 4. 5. The MS A sends the FACILITY message to the MS C, to instructing the subscriber A to set up a personal communication with B. After the MS C receives the message, it holds the MPTY call and activates the call A-B. The MS C response to MS A with a message. The MS C sends messages to other remote subscriber C subscribing the MPTY, instructing the subscriber to hold the call. A talks with B.

Adding a Remote Subscriber


When subscriber A has an active single call (A-D) and an on hold MPTY call (A-B-C), invoke the MPTY. To add a remote subscriber, perform the following steps; 1. 2. The MS A sends the FACILITY message to the MS C, to instruct the subscriber A to invoke the MPTY. After the MS C receives the message, it applies the call conference resources if the single call meets the requirements of joining the MPTY call. And then, the MS C connects A, B, C and D by using the call conference resources. The MS C responses to MS A with a message.

3.

6-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

6 Multiparty Service

4. 5.

The MS C sends messages to subscriber B and C, to instruct them that the call is resumed and they can take part in the MPTY service. The MS C sends a message to D, instructing D to take part in the MPTY service.
If the single call (A-D) is an active call, the MPTY call (A-B-C) is an on hold call, 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, and then sends message to D to instruct D to join the MPTY service.

Disconnecting a Remote Subscriber


Based on different active disconnecting parties, disconnecting a remote subscriber falls into the following two occasions: The served mobile subscriber disconnects a remote subscriber call. The remote subscriber disconnects a served mobile subscriber call. To disconnect a remote subscriber by a served subscriber, perform the following steps: 1. 2. 3. 4. The served mobile subscriber A sends disconnecting message to the MS C, to instruct MS C to disconnect the call A-D. After the MS C receives the message, it disconnects the connections related to remote subscribers and releases the idle call conference resources. The MS C sends message to A to release the call A-D between the MS C and the served mobile subscriber. The MS C sends message to the disconnected remote subscriber to release the call A-D between subscriber D and the MS C.

To disconnect the call between the remote subscriber and the served mobile subscriber, perform the following steps: 1. 2. 3. 4. The remote subscriber D sends disconnecting message to the MS C, to instruct the MS C to disconnect the call A-D. After the MS C receives the message, it disconnects the connections related to subscriber D and releases the idle call conference resources. The MS C sends message to the served mobile subscriber A to release the call A-D between the MS C and subscriber A. The MS C sends message to D to release the call A-D between subscriber D and the MS C.

6.4 Service Flow


6.4.1 Setting up the MPTY Call
The carrier provides the MPTY for subscriber A. The call A-B is on hold and the call A-C is active. The subscriber A, B and C are the MSs under the same MS C server. The procedure of setting up the MPTY call is shown as Figure 6-1.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

6-5

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

If A wants to set up a multi-party call, the MS A sends a FACILITY message containing the BuildMPTY invoke component to the MS C server. The MS C server sends the FACILITY message to the MS A, 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-B. The CallOnHold-indicator in the invoke component is callRetrieved, informing the MS-B that the call is resumed. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B. The invoke component contains the MPTYindicator. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS C. The invoke component contains the MPTYindicator.

4. 5.

6.4.2 Setting Up a Personal Communication with Remote Subscriber


The carrier provides the MPTY for subscriber A. The call A-B-C is the MPTY call. The subscriber A, B and C are the MSs under the same MS C server. The procedure of setting up the personal communication between A and B is shown as Figure 6-2.

6-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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

If A wants to set up a new call, the MS A sends a FACILITY message containing the SplitMPTY invoke component to the MS C server. The MS C server sends the FACILITY message to the MS A, indicating that the request of SplitMPTY is accepted. The MS C server activates the A-B call. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS C and MS B. The CallOnHold-indicator in the invoke component is callOnHold, informing the MS C that the call is on hold.

6.4.3 Adding a Remote Subscriber


The carrier provides the MPTY for subscriber A. The A-B-C is the MPTY call on hold and the A-D is the active single call. The subscriber A, B, C and D are the MSs under the same MS C server. The procedure of adding subscriber D to the MPTY call is as shown Figure 6-3. 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

6 Multiparty Service

HUAWEI MSOFTX3000 Feature Description

1. 2. 3.

When subscriber A wants to add a remote subscriber, the MS A sends a FACILITY message containing the BuildMPTY invoke component, to the MS C server. The MS C server sends the FACILITY message to the MS A, indicating the request of BuildMPTY is accepted. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B and MS C separately. The CallOnHold-indicator in the invoke component is callRetrieved, informing the MS-B and MS C that the call is resumed. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-B and MS C separately. The invoke component contains the MPTYindicator. The MS C server sends the FACILITY message containing the NotifySS invoke component to the MS-D. The invoke component contains the MPTYindicator.

4.

5.

6.4.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 A-B-C-D is the active MPTY call. The procedure for subscriber A to remove the subscriber D from the MPTY calls, is as shown Figure 6-4. 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.

When subscriber A wants to disconnect the A-D call, the MS A sends a DISCONNECT message to the MS C server. The Transaction identifier in the message is instructed to remove the A-D call. The MS C server A sends a RELEASE message to the MS A to disconnect the A-D call at the wireless side. 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.

2. 3.

6-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

6 Multiparty Service

4. 5.

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.

Removing Subscriber Disconnect the Call


The carrier provides the MPTY service for the subscriber A. The A-B-C-D is the active MPTY call. 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. 2. 3. 4. 5.

If subscriber D wants to disconnect the call, the PSTN D sends the REL message to the MS C server A, to instruct it to disconnect the A-D call. 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. The MS C server A sends a DISCONNECT message to the MS A. The Transaction identifier in the message instructs to remove the A-D call. 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.

6.5 Data Configuration


6.5.1 Data Configuration at MSOFTX3000 Side
For detailed operations of data configuration, see HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

6-9

6 Multiparty Service

HUAWEI MSOFTX3000 Feature Description

Enabling Service
The service availability does not require special configuration data.

Controlling MPTY Service Bill


You can control the bill generation of MPTY service by using the MOD GBILLCTRL command.

Setting Tone Playing of Conference


If it is required, set related data of playing conference tone by using the SET LOCALSRV command.

Related Software Parameter


Name P168 (CM software parameter 1) Bit 10 Definition When the main control party retrieves the MPTY, it controls whether to play tone suggesting the conference is entered. . When the tone is required to be played by the call release initiated at the network side, it controls whether to play tones to prompt the remote subscriber to enter the conference. When the times of control handover or the times of supplementary services operation is over the maximum times set by the system, it controls whether the bills generated is outgoing intermediate bill or the event bill. Value =0:play tones =1:Not play tones Default Value 1

P174 (CM software parameter 7) Bit 8

=0: Support =1: Not support

P129 (CHG parameter 1) Bit 7

=0: Generate intermediate bill =1: Generate event bill

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

6-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

6 Multiparty Service

6.6 Service Management


There are two operating methods for the MPTY service, 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. Release o- hold calls, release active calls and resume on-hold calls, release remote subscriber, set up personal communications with remote subscribers, alternate calls, invoke the MPTY and add remote subscriber, initiate a new call and hold the MPTY call, and release all calls. as listed in Table 6-3.

As for the MPTY service, the service is provided when being activated; and the service is cancelled when being deactivated.

6.6.1 Carrier Operation


As for the MPTY service, the service is provided when the service is activated; the service is cancelled when the service is deactivated. For detailed operations, see compatible operation manuals of HLR products used in the network at present.

6.6.2 Mobile Subscriber Operation


Precondition
The carrier provides the MPTY service to the subscribers.

Steps
For detailed operation steps, see Table 6-4. 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. The subscriber dials 1 on the MS and press the "Send" button. The subscriber dials 1X on the MS and press the "Send" button. X is the sequence number of remote subscriber. It starts from 1 and increases based on the sequence of setting up or answering the calls for the served mobile subscriber.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

6-11

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. X is the sequence number of remote subscriber. It starts from 1 and increases based on the sequence of setting up or answering the calls for the served mobile subscriber. The subscriber dials 2 on the MS and press the "Send" button. The subscriber dials 3 on the MS and press the "Send" button. The subscriber dials the number of new subscriber on the MS and press "Send" button. Press "Release" button on the MS.

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. For detailed operations, see the mobile phone instructions.

6.7 Charging and CDR


There are two modes to generate the bill of MPTY service for the MSOTX3000, independent charging and segmented charging. 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. Then, the final MOC/MTC is generated. 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. The charging center combines the bills or processes the other charging. The mark and time stamp of MPTY are added to the latter segment of bill. The MSOTX3000 controls the mode created by bill, and the frequency created by the event bill, or intermediate bill through the CHG parameter 1 (P129) Bit 7 and integrated control table of bill. In usual cases, the independent charging is adopted. The following is an independent charging case for MPTY call. In the following occasions, The subscribers A under the MS C server calls the subscriber B in other offices. During the communications of A-B, subscriber A holds a call and calls the subscriber C in other offices.

6-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

6 Multiparty Service

Subscriber C answers the call and sets up the MPTY call. The local office is the MOC bills created by the A-B call. There are two supplementary service operation records in the supplementary service field of the bill. One indicator of supplementary service is CH and the time stamp is the time for the subscriber A sending the HOLD message; 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. The MOC bill is created by the local A-C call. There is one supplementary service operation record in the supplementary service field of the bill. The record indicator of supplementary service operations is the MPTY. The time stamp is the time that subscriber A sends the FACILITY message containing the BuildMPTY.

6.8 Service Interaction


For the interactions between the MPTY and the other services is listed in Table 6-5. 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, the remote subscriber subscribing the CLIP and involving the MPTY service cannot receive the number of remote subscriber newly added. The MPTY and the forwarding services do not affect each other. The calling party: When the calling party tries to set up the MPTY call with the called party subscribing the call forwarding service, the forwarding subscriber hears rings and is added to the conference if the forwarding meets the trigger conditions. Forwarding subscriber: When the forwarding subscriber sets up the MPTY call, the forwarding call existed is added to the conference as a connection of the MPTY call. MPTY and CW The MPTY and CW do not affect each other. If a subscriber activates a MPTY call, the subscriber receives a call on hold notice when other subscribers call the subscriber. When the subscriber sets the MPTY call to on hold, the subscriber can answer the call on hold. MPTY and CH Subscribing CH service is the prerequisite of subscribing the MPTY service. If a subscriber activates a MPTY call, the subscriber (the served subscriber or the remote subscriber) is allowed to hold the MPTY call and resume the call. MPTY and BO If the BO service is activated after invoking the MPTY call, the outgoing call of the MPTY is not affected by the BO service. However, the outgoing call made after activation of the BO service is to be barred if the call meets the barring requirements.

MPTY and Forwarding services

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

6-13

6 Multiparty Service

HUAWEI MSOFTX3000 Feature Description

Service MPTY and BI

Interaction If the BI service is activated after invoking the MPTY call, the incoming call of the MPTY is not affected by the BI service. However, the incoming call made after activation of BI service is to be barred if the call meets the barring requirements.

6.9 Reference
6.9.1 Protocols and Specifications
The references of the feature are list as follows: 3GPP TS 22.084 V4.1.0 3GPP TS 23.084 V4.1.0 3GPP TS 24.084 V4..0.0 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide

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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
7 Call Barring Service ...................................................................................................................7-1
7.1 Service Description .......................................................................................................................................7-2 7.1.1 Function Code......................................................................................................................................7-2 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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Contents

HUAWEI MSOFTX3000 Feature Description 7.9.2 Acronyms and Abbreviations .............................................................................................................7-21

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Figures

Figures
Figure 7-1 Check flow of the VLR for the BAOC service .................................................................................7-5 Figure 7-2 Check flow of the VLR for the BOIC service...................................................................................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-8 Figure 7-5 Check flow of the HLR for the BIC-ROAM service ........................................................................7-9 Figure 7-6 BO service flow ..............................................................................................................................7-10 Figure 7-7 BI service flow................................................................................................................................ 7-11

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

Tables

HUAWEI MSOFTX3000 Feature Description

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

iv

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

7
About This Chapter
Section 7.1 Service Description 7.2 Availability 7.3 Working Principle 7.4 Service Flow 7.5 Data Configuration 7.6 Service Management 7.7 Charging and CDR 7.8 Service Interaction 7.9 Reference Describes

Call Barring Service

The following table lists the contents of this chapter.

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

7-1

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

7.1 Service Description


7.1.1 Function Code
Table 7-1 lists the name and code of the function. Table 7-1 Name and code of the function Name Call barring services Code WMFD-020400

7.1.2 Definition
Call barring supplementary services allow mobile subscribers to perform barring for incoming or outgoing calls with special properties.

7.1.3 Types
Call barring services are classified into two types: barring of outgoing calls (BO) and barring of incoming calls (BI). The BO service includes: Barring of All Outgoing Calls (BAOC is for short.) Barring of All Outgoing International Calls (BOIC is for short.) Barring of Outgoing International Calls except those directed to the Home PLMN Country (BOIC-exHC is for short.) The BI service includes: Barring of All Incoming Calls (BAIC is for short.) Barring of Incoming Calls When Roaming Outside Home PLMN Country (BIC-ROAM is for short.)

BAOC
After the service is activated, a mobile subscriber cannot initiate calls.

BOIC
After the service is activated, a mobile subscriber cannot call any subscriber (including mobile subscriber or fixed network subscriber) outside the country where the caller is.

BOIC-exHC
After the service is activated, a mobile subscriber cannot call any subscribers outside the country (homing to the PLMN) where the caller roaming. After the subscriber is roaming outside the country homing to the PLMN, the subscriber can call only subscribers (mobile subscribers or fixed network subscribers) in homing countries.

7-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

BAIC
After the service is activated, a mobile subscriber cannot receive calls.

BIC-ROAM
After the service is activated, a mobile subscriber cannot receive calls when the subscriber is roaming outside the country homing to the PLMN. Subscribers can select one or several types of call barring service. If the service controller is set to subscribers, subscribers can activate or deactivate call barring services through their handsets. In advance, password must be provided.

7.1.4 Benefits
Beneficiary Carriers Mobile subscribers Description The call barring supplementary services add values of services. After the system provides the call barring service, subscribes can bar some type of incoming/outgoing calls. Subscribes can perform activation/deactivation operation, thus to control incoming/outgoing calls flexibly.

7.2 Availability
7.2.1 Requirements for NEs
Table 7-2 lists the network elements (NEs) required by the call barring services. 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; MS = mobile station; BTS = base transceiver station; RNC = radio network controller; BSC = base station controller; MSC = mobile switching center; MGW = media gateway; SGSN = serving GPRS support node; VLR = visitor location register; HLR = home location register

The symbol indicates that the corresponding NE is required. The hyphen - indicates that the corresponding NE is not required.

7.2.2 Requirements for License


The call completion supplementary services are basic services of Huawei wireless core network. No license is needed.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-3

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

7.2.3 Applicable Versions


Table 7-3 lists the applicable versions of Huawei wireless core network products that the call barring services support. 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.3.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 that it stores. Updates the subscription information in the VLR by inserting subscriber data.

Registration
If the service controller of the call barring services is subscribers, subscribers can modify the password used for service control through registration. The MSC transparently sends the registration operation message to the HLR, and then updates the subscription information in the VLR by inserting subscriber data.

Activation and Deactivation


If the service controller of the call barring services is subscribers, when a subscriber initiates activation or deactivation operation, the MSC transparently sends the operation message to the HLR. The HLR modifies the subscription information that it stores based on the message, and then updates the subscription information in the VLR by inserting subscriber data

If the activated call barring service conflicts with other activated services, the activation may fail. For details, see section 7.8 "Service Interaction."

7.3.2 BO
The following section describes the working principle of the BO service. A subscriber initiates a call. 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)

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. Then the VLR sets the call barring indication based on the check result and sends the indication to the MSC. For service check procedures by the VLR for BAOC, BOIC and BOIC-exHC services, see Figure 7-1, Figure 7-2 and Figure 7-3. The MSC determines whether to perform call barring based on the call barring indication. If the call barring indication is Yes, the MSC releases the call; if the call barring indication is No, the MSC processes the call according to normal flow. 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

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)

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, 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, subscribers can still call special numbers when the BO service is activated.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-7

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

7.3.3 BI
The following section describes the working principle of the BI service. A subscriber initiates a call. The (G)MSC initiates the operation of fetching route information to the HLR. The HLR checks the service based on BI information of callee and call property of the incoming call. 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, see Figure 7-4 and Figure 7-5. The HLR determines whether to perform call barring based on the call barring indication. If the call barring indication is Yes, the HLR indicates to reject the call in the response to the operation of fetching route information; if the call barring indication is No, the HLR processes the call according to normal flow. 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)

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, every service check flow is executed.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-9

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

7.4 Service Flow


7.4.1 BO
Figure 7-6 shows the BO service flow. Figure 7-6 BO service flow
MS MSC server MSC server/ PSTN

SETUP RELEASE COMPLETE OR1: Yes Facility (Invoke = NotifySS (SSOR1: No Code, SS-Status)) IAM

OR1: call barred

IAM: Initial Address Message

1. 2.

The MS sends the SETUP message to the MSC server. The VLR of the MSC server checks the service based on BO service information and call property. Then the VLR sets call barring indication based on the check result. For service check procedures, see Figure 7-1, Figure 7-2 and Figure 7-3. The MSC determines whether to perform call barring based on the call barring indication. If the call barring indication is Yes, the MSC sends the RELEASE COMPLETE message or other release message to the MS to release the call. The parameter Facility contains invocation component of NotifySS operation. The SS-Code of the component refers to service code of the BO service. The SS-Status indicates that the BO service is in activated or deactivated status. If the call barring indication is No, the MSC processes the call according to normal flow.

3. 4.

5.

7-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

7.4.2 BI
Figure 7-7 shows the voice BI service flow. 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.

If a caller is an MS, the MS sends the SETUP message to the MSC server. If the caller is a fixed network subscriber, the PSTN office sends originated call message (such as the IAM message) to the GMSC server through trunk signaling. The (G)MSC server initiates the SRI operation to the HLR b that callee homes. The HLR b checks the service based on BI service information and call property. Then the HLR b sets call barring indication based on the check result. For service check procedure, see Figure 7-4 and Figure 7-5. If the call barring indication is Yes, the HLR b sends the SRI ack message to the (G)MSC server. The parameter User error in the message is Callbarred. If the caller is an MS, after receiving the SRI ack message, the MSC server b sends the RELEASE COMPLETE or other release message to the MS. Then the MSC server b releases the call according to normal flow that is omitted in the figure. If the caller is a fixed network subscriber, 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 No, the HLR processes the call according to normal flow.

2. 3.

4. 5.

6.

7.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-11

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

7.5 Data Configuration


7.5.1 Configuring Data at the MSOFTX3000 Side
For the details of data configuration, see the HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide.

Enabling the Service


No additional data is required to enable the service.

Checking the Service


The MSOFTX3000 can suppress the BO service for special prefix and special call source through service check configuration. The procedure is as follows: Step 1 Run ADD SRVCHK to define a service check configuration. Of it, the value of BO service item of the parameter SCC is 0; the value of BO service item of the parameter SCM is 1. Step 2 Run ADD CNACLD or MOD CNACLD to set a call prefix. Of it, the value of the parameter ISERVICECHECKNAME is the one of SCN that is set in step 1. ----End The following table lists an example: Description Script BAOC, BOIC, ODB_BAOC and ODB_BOIC subscribers are allowed to dial 110. ADD SRVCHK: CSCNAME="ALL", SCN="NOCHECK", IFSC=YES, SCC=ODB_BAOC-0&BAOC-0&ODB_BOIC-0&BOIC-0, SCM=ODB_BAOC-1&BAOC-1&ODB_BOIC-1&BOIC-1; ADD CNACLD: PFX=K'110, MINL=3, MAXL=3, ISERVICECHECKNAME="NOCHECK";

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. = 1: Enable forced release function of the supplementary service at once. That is, if the added supplementary service is BAOC, BOIC or BOIC_EXHC, the forced release flow will be initiated to subscribers in conversation. Default Value 0

7-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

7.5.2 Configuring Data at the HLR Side


No data related to the service needs to be configured at the HLR side.

7.6 Service Management


The call barring supplementary services have two operation modes, as listed in Table 7-4. 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. Withdraw the service. Register the service. Activate the service. Deactivate the service. Modify the service control right. Operation by mobile subscribers MS Register the service Activate the service. Deactivate the service.

7.6.1 Operations by Carriers


For details, see the corresponding operation manual of the HLR.

7.6.2 Operations by Mobile Subscribers


Prerequisite
The controller of call barring services is subscribers.

Operations
On the MS, mobile subscribers can perform the operations listed in Table 7-5. Table 7-5 Operations performed by mobile subscribers Operation Type Modify call barring service password. Step On the MS, dial "**03*330*oldPW*newPW*newPW#", and then press the Send key. Of it, oldPW refers to old password of the call barring service and newPW refers to new password of the call barring service.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-13

7 Call Barring Service

HUAWEI MSOFTX3000 Feature Description

Operation Type Activate the BAOC service. Deactivate the BAOC service. Activate the BOIC service. Deactivate the BOIC service. Activate the BOIC-ExHC service. Deactivate the BOIC-ExHC service. Activate the BAIC service. Deactivate the BAIC service. Activate the BIC-Roam service. Deactivate the BIC-Roam service. Deactivate all call barring services. Deactivate all BO services. Deactivate all BI services.

Step On the MS, dial "*33*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#33*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "*331*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#331*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "*332*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#332*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "*35*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#35*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "*351*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#351*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#330*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#333*PW#", and then press the Send key. Of it, PW refers to call barring service password. On the MS, dial "#353*PW#", and then press the Send key. Of it, PW refers to call barring service password.

Subscribers can also perform the operations through the menus of some mobile phones. For details, see the user manuals of the mobile phones. The call barring service password is 0000 by default.

7-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

7 Call Barring Service

7.7 Charging and CDR


The call barring services cause call failure. Therefore, no CDR is generated for failed call.

7.8 Service Interaction


7.8.1 BAOC
Table 7-6 lists the interactions between the BAOC service and other services. Table 7-6 Interactions between the BAOC service and other services Service BAOC and CFU, CFB, CFNRy and CFNRc Interaction The forwarding and BAOC services are incompatible. If a subscriber activates the forwarding service, it is prohibited to activate the BAOC service. If a subscriber activates the BAOC service, it is prohibited to register or activate the forwarding service. BAOC and CW The BAOC and CW services are compatible. When a caller activates the BAOC service, no waiting call that has been initiated is affected. BAOC and CH The BAOC and CH services are compatible. After initiating a call that is in call hold status, a caller activates the BAOC service. The held call still can be invoked. But all new outgoing calls are inhibited. BAOC and MPTY After invoking an MPTY call, a subscriber activates the BAOC service. All outgoing calls in the MPYT call are not affected. All new outgoing calls are inhibited. The BAOC service enjoys higher priority than the CUG service. During an outgoing call, a caller activates the BAOC service without affecting any CUG calls.

BAOC and CUG

7.8.2 BOIC
Table 7-7 lists the interactions between the BOIC service and other services.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

7-15

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, the CFU service registered and activated to an international number is rejected. If a subscriber activates the CFU service to an international number, the BOIC service cannot be activated. BOIC and CFB If a subscriber activates the BOIC service, the CFB service registered and activated to an international number is rejected. If a subscriber activates the CFB service to an international number, the BOIC service cannot be activated. If the CFB service is registered to a home country number and both CFB and BOIC services are activated, when a subscriber is roaming to another country, the CFB service is unavailable. If the BOIC service is deactivated later, or the subscriber comes back to the home country, the CFB service auto changes to available. BOIC and CFNRy If a subscriber activates the BOIC service, the CFNRy service registered and activated to an international number is rejected. If a subscriber activates the CFNRy service to an international number, the BOIC service cannot be activated. If the CFNRy service is registered to a home country number and both CFNRy and BOIC services are activated, when a subscriber is roaming to another country, the CFNRy service is unavailable. If the BOIC service is deactivated later, or the subscriber comes back to the home country, the CFNRy service auto changes to available. BOIC and CFNRc If a subscriber activates the BOIC service, the CFNRc service registered and activated to an international number is rejected. If a subscriber activates the CFNRc service to an international number, the BOIC service cannot be activated. If the CFNRc service is registered to a home country number and both CFNRc and BOIC services are activated, when a subscriber is roaming to another country, the CFNRc service is unavailable. If the BOIC service is deactivated later, or the subscriber comes back to the home country, the CFNRc service auto changes to available. BOIC and CW BOIC and MPTY BOIC and CH The BOIC and CW services are compatible. When a caller activates the BOIC service, any waiting international call that has been initiated is affected. After invoking an MPTY call, a subscriber activates the BOIC service. All outgoing calls in the MPYT call are not affected. All new outgoing international calls are inhibited. The BOIC and CH services are compatible. After initiating an international call that is in call hold status, a caller activates the BOIC service. The held call still can be invoked. But all new outgoing international calls are inhibited.

7-16

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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

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

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

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

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. Start time: B answers the call. End time: The B-C call is disconnected. The CH operation is 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. 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. There is no CDR.

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. There is no CDR.

During the A-B call, A holds the call with B and calls C. After C is in the alerting state, A invokes the ECT. The B-C call is disconnected. During the A-B call, A holds the call with B and calls C. After C is in the alerting state, A invokes the ECT. C does not answer the call.

8.7.3 Segmented 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 MSOFTX3000. Table 8-8 lists the scenarios of generating the CDR.

8-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. Start time: B answers the call. End time: A invokes the ECT. Interval CDR: The ECT operation is recorded in the supplementary service field. Start time: A invokes the ECT. End time: The B-C call is disconnected. During the A-B call, A holds the call with B and calls C. After C is in the alerting state, A invokes the ECT. The B-C call is The first CDR: The CH operation is recorded in the supplementary service field. Start time: B answers the call. End time: A invokes the ECT. 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 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 first CDR: There is no record in the supplementary service field. Start time: C answers the call. End time: The B-C call is disconnected. Interval CDR: The ECT operation is recorded in the supplementary service field. Start time: A invokes the ECT. End time: The B-C call is disconnected. The first CDR: There is no record 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. Start time: C answers the call. End time: The B-C call is disconnected. 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.

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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-11

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. Start time: C answers the call. End time: The B-C call is disconnected.

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. Start time: C answers the call. End time: The B-C call is disconnected.

CDR of Subscriber A in the A-C Call

disconnected.

During the A-B call, A holds the call with B and calls C. After C is in the alerting state, A invokes the ECT. C does not answer the call.

The CH operation is recorded in the supplementary service field. Start time: B answers the call. End time: The B-C call is disconnected.

There is no record in the supplementary service field. Start time: B answers the call. End time: The B-C call is disconnected.

There is no CDR.

There is no CDR.

8.8 Service Interaction


Table 8-9 gives the interaction between the ECT and other services. 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, the number of C (or B) must be sent to B (or C). But if C (or B) also registers with the CLIP, the number need not be sent to B (or C). 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 the A-C call is established after the ECT, the number of C must be displayed during the connection. If B (or C) is the callee and (or C) registers with the CLIP (OVERRIDE CATEGORY CLIP) service, the number of the peer end is displayed after the ECT is invoked.

8-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. The number of B must not be sent to C. If B is the caller in the A-B call and B (or C) registers with the COLP, the number of C (or B) must be sent to B (or C). But if C (or B) also registers with the COLP, the number is not required to be sent to B (or C). 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 the A-C call is established after the ECT, the number of C must be displayed during the connection. If B (or C) is the caller and B (or C) registers with the COLP (OVERRIDE CATEGORY COLP) service, the number of the peer end is displayed after the ECT is invoked.

ECT and COLR

If A is the caller in the A-B call and B registers with the COLR service, the number of B must be hidden to C. If A is the caller in the A-C call and C registers with the COLR, the number of C must be hidden to B. If C registers with the CFB, the call is forwarded to D on C busy. If C registers with the CFNRy, the call is forwarded to D when C does not answer the call. The CFNRy timer is not restarted during the call forwarding. The ECT and CFNRc services do not affect each other. If A is in idle state after invoking the ECT, there will be no CW indication. If A has a CW before the ECT, process it as an ordinary terminated call. If C registers with the CW and the A-C call is in the waiting state, B will receive the CW indication after the ECT.

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. The ECT and AoC services conflict with each other. The cheating prevention feature prevents the subscribers from owing fee by continuously invoking the ECT.

8.9 Reference
8.9.1 Protocols and Specifications
Refer to the following references: 3GPP TS 22.091 V4.0.0 3GPP TS 23.091 V4.0.0

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

8-13

8 Explicit Call Transfer Service

HUAWEI MSOFTX3000 Feature Description

3GPP TS 24.091 V4.0.1 HUAWEI MSOFTX3000 Mobile SoftSwitch Center Configuration Guide

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

HUAWEI MSOFTX3000 Feature Description

Contents

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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Tables

HUAWEI MSOFTX3000 Feature Description

Tables
Table 9-1 Name and function code of the ODB services....................................................................................9-2 Table 9-2 NEs related with the ODB services ....................................................................................................9-4 Table 9-3 Versions that support the ODB services .............................................................................................9-5 Table 9-4 Service interaction between ODB and other services.........................................................................9-7

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

9 ODB Service

9
About This Chapter
The following table lists the contents of this chapter. Section 9.1 Service Description 9.2 Availability 9.3 Working Principle 9.4 Service Flow 9.5 Data Configuration 9.6 Service Management 9.7 Charging and CDR 9.8 Service Interaction 9.9 Reference Describes

ODB Service

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

9-1

9 ODB Service

HUAWEI MSOFTX3000 Feature Description

9.1 Service Description


9.1.1 Function Code
Table 9-1 lists the name and function code of the ODB services. 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.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 ODB is similar to the call restriction supplementary service. The differences between these two services are as follows: The service state of the user subscribing to ODB is determined by the operator, and that of the latter type can be determined by both the operator and the user. The ODB service is activated once it is provided to the user, and the latter type must be activated by the user.

9-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

9 ODB Service

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

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

9.2 Availability
9.2.1 Requirement for NEs
The ODB requires the corporation of the MSC server, VLR, HLR, SGSN, and GGSN. Table 9-2 lists the NEs related with the ODB services. 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.

9.2.2 Requirement for License


The ODB is an optional feature of the Huawei wireless core network. You can obtain this service only after getting the license of MSOFTX3000.

9-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

9 ODB Service

9.2.3 Applicable Versions


Table 9-3 lists the Huawei core network product versions that support the ODB services. 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.3 Working Principle


The ODB requires the corporation of the HLR, MSC, VLR, and the SGSN. The MSC processes signaling, analyzes data, and plays announcements. The HLR stores the subscription data, determines whether to trigger the ODB, and sends subscription data of the user to the VLR. The VLR stores temporally the subscription data of the user which is to be queried by the MSC. The SGSN processes all the signaling related with packet services.

9.4 Service Flow


9.4.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. If the user subscribes to this service, 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 network of the calling party, and the calling party hears the prompt tone defined by the operator.

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. If the user subscribes to this service, 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.

9.4.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. If the outgoing call barring of the user is

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

9-5

9 ODB Service

HUAWEI MSOFTX3000 Feature Description

activated, the MSC refuses the call request of the user and returns a refusing message which contains the cause value. 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 MSC/HLR bars all the calls originated by this user and returns a refusing message which contains the cause value.

9.4.3 Barring of Roaming


If a mobile subscriber subscribes to the ODB barring of roaming, and if the subscriber launches registration to the VLR in the roaming restriction area defined by this barring of roaming service, the VLR sends a location update request to the HLR. The HLR checks the identifier of the VLR and determines that the VLR is in the roaming restriction area. Then the HLR responses a location canceling message and refuses the location update.

9.4.4 Barring of Supplementary Services


If a mobile subscriber subscribes to barring of supplementary services, and if the user launches a supplementary service operation, the HLR or MSC/VLR refuses the request and sends an error message to the mobile subscriber.

9.4.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, and if the MS subscribes to the ODB barring of packet services, the SGSN returns a refusing message which contains error message. 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, and if the routing request contains the PDP context activation information, the HLR checks the subscription data of the MS. If the MS subscription data contains the data for ODB barring of packet services, the HLR responses a refusing message which contains error message. Then the GGSN sends the error message to the network that launches the PDP context activation.

9.5 Data Configuration


9.5.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. You can perform service check through certain call prefix.

9-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

9 ODB Service

You can add service check by using the command ADD SRVCHK. You can perform service check through certain call prefix and determines whether to connect the call based on the check result.

9.5.2 Data Configuration for UMG8900


None.

9.6 Service Management


All the management operations of the ODB services are performed in the HLR. For details, see the related product manuals of the latest version.

9.7 Charging and CDR


None.

9.8 Service Interaction


Table 9-4 lists the service interaction between ODB and other services. 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. ODB has higher priority over supplementary services. If the ODB conflicts with supplementary services, the supplementary services will be barred. If the ODB barring of call forwarding is activated, the user is not allowed to register call forwarding services. 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. 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.

ODB and call barring

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

9-7

9 ODB Service

HUAWEI MSOFTX3000 Feature Description

9.9 Reference
9.9.1 Protocols and Specifications
This document takes the following protocols and manual as references: 3GPP TS 22.091 V4.0.0 3GPP TS 23.091 V4.0.0 3GPP TS 24.091 V4.0.1 HUAWEI MSOFTX3000 Mobile Softswitch Center Configuration Guide

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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 10-1 Flow of UMTS authentication ......................................................................................................10-4 Figure 10-2 Flow of GSM authentication.........................................................................................................10-6

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 10-1 Function names and functions codes in the authentication and encryption ....................................10-2 Table 10-2 Benefits for carriers and mobile subscribers...................................................................................10-2 Table 10-3 NEs involved in the authentication and encryption ........................................................................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

HUAWEI MSOFTX3000 Feature Description

10 Authentication Feature

10
About This Chapter
Section 10.1 Service Description 10.2 Availability Describes

Authentication Feature

The following table lists the contents of this chapter.

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 protocols and specifications that this feature must comply with, and the acronyms and abbreviations of this chapter.

10.3 Working Principle 10.4 Service Flow 10.5 Data Configuration 10.6 Service Management 10.7 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

10-1

10 Authentication Feature

HUAWEI MSOFTX3000 Feature Description

10.1 Service Description


10.1.1 Function Code
Table 10-1 lists the mapping between function names and function codes in the speech service. 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; UMTS = Universal Mobile Telecommunications System

Code WMFD-060301 WMFD-060302

10.1.2 Definition
Authentication is a process used for a network to verify the validity of an UE. In the UMTS, an UE can also verify the validity of a network. Authentication, as part of the security management of a wireless network, guarantees the confidentiality and integrity of the wireless network, so that illegal subscribers cannot use the services that the network provides.

10.1.3 Benefits
Table 10-2 lists the benefits for carriers and mobile subscribers. Table 10-2 Benefits for carriers and mobile subscribers Beneficiary Carriers Description Authentication is an elementary feature of a network. Authentication enables carriers to verify the validity of MSs/UEs, and prevents illegal subscribers from accessing the network and using the services that the network provides. Authentication protects mobile subscribers from illegal attack.

Mobile subscribers

Note: MS = mobile station; UE = user equipment

10-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

10 Authentication Feature

10.2 Availability
10.2.1 Requirements for NEs
The authentication and encryption requires the cooperation of the UE/MS, base station subsystem (BSS) , radio access network (RAN) and core network (CN). For details, see Table 10-3. 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.

10.2.2 Requirements for License


No License is required to obtain the authentication service, because the service is the elementary feature of the HUAWEI wireless core network.

10.2.3 Applicable Versions


Table 10-4 lists the versions of the HUAWEI circuited switched (CS) products that support the authentication and encryption. 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.3 Working Principle


In the GSM and UMTS, the MS/UE, visitor location register (VLR) and authentication center (AuC) cooperate with each other to implement authentication. The MS/UE and AuC calculate authentication parameters respectively. The VLR then compares the two results, to verify the validity of the MS/UE. In the UMTS, the MS/UE can also verify the validity of the network.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

10-3

10 Authentication Feature

HUAWEI MSOFTX3000 Feature Description

10.4 Service Flow


10.4.1 UMTS Authentication
UMTS authentication takes place when a UMTS subscriber accesses the UMTS with a UMTS subscriber identity module (USIM) card. Figure 10-1 shows the flow of UMTS authentication. Figure 10-1 Flow of UMTS authentication
Uu UE RAN 1. Send a service request (call setup/location update/ supplementary serice/SMS) 2. Send a MAP request (CKSN, IMSI/TMSI) 5. Start authentication 5 5 (RAND, AUTN) 3. Send a request for authntication parameters ( IMSI) 4. Return parameters IMSIRANDCK IKAUTNXRES RANAP Iu MSC MAP B VLR MAP D HLR/AuC

6. Refuse authentication (XMAC MAC) 6. Synchronization fails (SQNHE SQNMS) 7. Send an authentication response

AuC re-synchronization

7. Accept the request/ Refuse the request Sends an acceptance response Authentication succeeds legal UE Authentication fails illegal UE

8. Compare SRES and XRES

Explanations of the flow of UMTS authentication are as follows: 1. 2. 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. The MSC sends a MAP_PROCESS_ACCESS_REQUEST to the VLR, requesting the authentication set from the VLR.

If there are available authentication sets in the VLR, the VLR returns the RAND and AUTN contained in the authentication set to the MSC before starting authentication. The MSC then directly transfers the two parameters to the UE over the RAN, without interacting with the AuC. That is, step 5 takes place immediately after step 2. If no available authentication set is in the VLR, step 3 takes place.

3. 4. 5.

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. The VLR starts authentication.

10-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

10 Authentication Feature

6.

The UE calculates the authentication parameters XMAC and SQNMS at the UE side, based on the RAND and AUTN returned by the VLR. The UE then compares the XMAC and SQNMS with the MAC and SQNHE in AUTN.

If MAC is not equal to XMAC, the authentication of the UE to the network fails. In this case, the VLR reports the authentication failure message to the AuC. If the difference between SQNMS and SQNHE is not within the specific range, it means the authentication of the UE to the network fails. In this case, the VLR sends a re-synchronization message to the AuC. The re-synchronization flow is similar to the flow of obtaining authentication set from the AuC. The difference is that the MAP_SEND_AUTHENTICATION_INFO message carries the re-synchronization information containing AUTS and RAND. After receiving the re-synchronization message, the AuC calculates MAC based on the RAND in the message, and compares the MAC with the MAC-S in AUTS, to judge whether the re-synchronization is valid. The AuC adjusts its own SQNHE based on the SQNMS in AUTS, and calculates a new group of authentication values for the VLR. The VLR starts authentication again with the new group of authentication values, and returns AUTN and RAND to the UE. After that, steps 3 and 4 are repeated. If the validity verification succeeds, then the authentication succeeds.

7. 8.

The UE calculates XRES based on the AUTN and RAND returned from the VLR, and sends an authentication response carrying XRES to the VLR. The VLR compares the XRES returned by the UE with the XRES calculated by the AuC.

If the two values are different, the VLR sends an authentication rejection response to the UE. The UE receives the response. This means the UE is invalid and the authentication fails. If the two values are the same, the authentication of the network to the UE succeeds. In this case, the network sends a response to the UE, indicating that the service or location update is accepted.

10.4.2 GSM Authentication


GSM authentication takes place under one of the following conditions: A GSM subscriber accesses the GSM with a SIM card. A GSM subscriber accesses the UMTS. A UMTS subscriber accesses the GSM. SIM stands for subscriber identity module. In GSM authentication, the MS does not have to authenticate the network. Figure 10-2 shows the flow of GSM authentication.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

10-5

10 Authentication Feature

HUAWEI MSOFTX3000 Feature Description

Figure 10-2 Flow of GSM authentication


Um MS BSS 1. Send a service request (call setup/location update/ supplementary serice/SMS) (CKSN, IMSI/TMSI) 3. Send a request for authntication parameters (IMSI) 4. Return parameters (IMSI, KC, S, RAND) BSSAP A MSC 2. Send a MAP request MAP B VLR MAP D HLR/AuC

5. Start authentication 5 5 (CKSN, RAND)

6. Send an authentication response 6 Sends an acceptance response 7. Accept the request/ Refuse the request Authentication succeeds legal UE Authentication fails illegal UE 8. Compare SRES and XRES

Explanations of the flow of GSM authentication are as follows: 1. 2. The MS sends an authentication request to the MSC. The authentication of services is defined by the data configured on the MSC. The MSC sends a MAP_PROCESS_ACCESS_REQUEST to the VLR, requesting the authentication set from the VLR.

If there are available authentication sets in the VLR, the VLR returns the RAND and AUTN contained in the authentication set to the MSC before starting authentication. The MSC then directly transfers the two parameters to the MS, without interacting with the AuC. That is, step 5 takes place immediately after step 2. If no available authentication set is in the VLR, step 3 takes place.

3. 4. 5. 6. 7.

The VLR requests the authentication set from the AuC. The AuC returns one to five groups of triplets to the VLR based on actual conditions. The VLR starts authentication. The MS calculates SRES based on the RAND returned from the VLR, and sends an authentication response carrying SRES to the VLR. The VLR compares the SRES returned by the MS with the SRES calculated by the AuC.

If the two values are different, the VLR sends an authentication rejection response to the MS. The MS receives the response. This means the MS is invalid and the authentication fails. If the two values are the same, the authentication of the network to the MS succeeds. In this case, the network sends a response to the MS, indicating that the service or location update is accepted.

10-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

10 Authentication Feature

When a UMTS subscriber roams in the GSM, the AuC may return a quintuple to the VLR. In this case, the VLR must transform the quintuple to a triplet. After that, the VLR returns the ciphering key sequence number (CKSN) together with the RAND in the triple to the MS.

10.5 Data Configuration


10.5.1 Data Configuration on MSOFTX3000
To configure the data for the authentication feature, perform the following steps: Step 1 Run MOD AUTHCFG to modify authentication configuration. (Optional) Step 2 Run ADD CHKIMEICTRL to add IMEI check control. (Optional) Step 3 Run SET CHKIMEICFG to set IMEI check configuration. (Optional) Step 4 Run ADD VEIRUSER to add a virtual EIR subscriber. (Optional) ----End

10.5.2 Data Configuration on HLR


For the details on configuration steps and parameter description, see the manuals relevant to the HLR.

10.6 Service Management


10.6.1 Subscription of Authentication
The subscription of authentication is on the HLR. For details, see the manuals relevant to the HLR.

10.6.2 Query of Authentication


The query of authentication is on the HLR. For details, see the manuals relevant to the HLR.

10.7 Reference
10.7.1 Protocols and Specifications
3GPP TS 33.102: <3rd Generation Partnership Project; Technical Specification Group Services and System Aspects;3G Security; Security Architecture> 3GPP TS 29.002: <3rd Generation Partnership Project; Technical Specification Group Core Network; Mobile Application Part (MAP) specification;>

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

10-7

10 Authentication Feature

HUAWEI MSOFTX3000 Feature Description

10.7.2 Glossary, Acronyms and Abbreviations


Glossary
Glossary Triplet Definition A triplet is a GSM authentication vector composed of three elements: RAND, SRES and Kc. 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, XRES, CK, IK and AUTN. It is a temporary data used for the MSC/VLR or SGSN to negotiate UMTS AKA with a specific subscriber.

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)

HUAWEI MSOFTX3000 Feature Description

Contents

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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 11-1 Simple MSRN allocation procedure ............................................................................................. 11-6 Figure 11-2 General procedure of MSRN allocation........................................................................................ 11-7 Figure 11-3 Procedure for random allocation................................................................................................... 11-8 Figure 11-4 Mapping between the MSRN or HON allocation tables............................................................... 11-9

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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-3 NEs required by the enhanced MSRN allocation service ............................................................... 11-4 Table 11-4 Applicable versions of HUAWEI wireless core network products ................................................. 11-5

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

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. Section 11.1 Service Description 11.2 Availability 11.3 Working Principle 11.4 Service Flow 11.5 Data Configuration 11.6 Service Management 11.7 Charging and CDR 11.8 Service Interaction 11.9 Reference 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 acronyms and abbreviations in this chapter.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

11-1

11 Enhanced MSRN Allocation Feature

HUAWEI MSOFTX3000 Feature Description

11.1 Service Description


11.1.1 Function Code
Table 11-1 lists the name and code of the function. Table 11-1 Name and code of the function Name Enhanced MSRN allocation Code WMFD-042400

11.1.2 Definition
Overview
The mobile station roaming number (MSRN) is used by the mobile switching center (MSC) to address callees. When the mobile station (MS) receives a call, 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). An MSRN has a validity period, and the default value is 90 seconds. You can set the validity period in the VLR configuration table. There are several modes for allocating MSRNs. 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. The default value is Allocate randomly. 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. The VLR can allocate specific roaming number resources through different allocation modes to meet various requirements.

Generally, the mode of random allocation can meet the requirements of networking except for certain special cases: In the multi-area network, you are recommended to set MSRN allocation mode to Allocate according to MSC number. When the location area identification (LAI) number is used for charging, you are recommended to set MSRN allocation mode to Allocate according to LAI number.

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. That is, the VLR allocates MSRN resources for different MSC numbers.

11-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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, the local MSC or VLR allocates an idle MSRN randomly from the MSRN pool to which the MSC number of the callee corresponds.

The mapping between the MSRN and the MSC number is configured by using the command ADD MHMSCCFG.

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. That is, the VLR allocates MSRN resources for different LAI numbers. When the home HLR of a mobile subscriber requests the local MSC or VLR to allocate an MSRN for the mobile subscriber, the local MSC or VLR allocates an idle MSRN randomly from the MSRN pool to which the LAI number of the callee corresponds.

The mapping between the MSRN and the LAI number is configured by using the command ADD MHLAICFG.

Random Allocation
The VLR does not range the MSRN resources that the local VLR can use in advance. When the home HLR of a mobile subscriber requests the local MSC or VLR to allocate an MSRN for the mobile subscriber, the local MSC or VLR allocates an idle MSRN randomly from all the MSRN pools that the local MSC or VLR can use. For the mode of random allocation, the VLR adds an extended function to the enhanced MSRN allocation service. 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. Inter-province roaming numbers Inter-province roaming numbers are configured by using the command ADD IMHSUFFIX. Inter-province roaming numbers are classified into four types based on the attribute of the callee. 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 VLR allocates a roaming number from the corresponding roaming number resource pool based on the attribute of the callee. If the related inter-province roaming numbers are used up, the VLR allocates an intra-province roaming number so that the incoming call can be connected to the office.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

11-3

11 Enhanced MSRN Allocation Feature

HUAWEI MSOFTX3000 Feature Description

11.1.3 Benefits
Table 11-2 lists the beneficiaries and description of the benefits. Table 11-2 Beneficiaries and description of the benefits Beneficiary Carriers Description Carriers can choose the allocation mode based on their requirements. In this way, the subscriber types are analyzed more effectively, and the customer satisfaction rate is improved. None.

Mobile subscribers

11.2 Availability
11.2.1 Requirements for NEs
Table 11-3 lists the network elements (NEs) required by the enhanced MSRN allocation service. 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; MS = mobile station; BTS = base transceiver station; RNC = radio network controller; BSC = base station controller; MGW = media gateway; SGSN = serving GPRS support node

The symbol indicates that the corresponding NE is required. The hyphen - indicates that the corresponding NE is not required.

11.2.2 Requirements for License


The enhanced MSRN allocation service is the basic service of HUAWEI wireless core network. No license is required.

11.2.3 Applicable Versions


Table 11-4 lists the applicable versions of HUAWEI wireless core network products that the enhanced MSRN allocation service supports.

11-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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


11.3.1 Functions of NEs
The MSC server determines the MSRN allocation mode through data configuration. The VLR realizes MSRN allocation based on the configuration of the system.

11.3.2 Processing in the System


Messages are exchanged between the MSC server, VLR, and HLR through the Mobile Application Part (MAP) protocol.

The VLR and HLR exchange and transfer the requests for MSRN allocation. 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, and records the information required after the call is connected. Figure 11-1 shows the simple MSRN allocation procedure.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

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

The (G)MSC server receives a call request from the caller. The (G)MSC server requests routing information from the HLR of the callee. The HLR checks compatibility and the feasibility of subscription. 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 checks the status of the subscriber, allocates an MSRN based on the current allocation mode, and returns the MSRN to the HLR.

4.

If MSRN allocation mode is set to Allocate according to MSC number, the VLR allocates an MSRN related to the MSC number of the callee. If MSRN allocation mode is set to Allocate according to LAI number, the VLR allocates an MSRN related to the LAI number of the callee. If MSRN allocation mode is set to Allocate randomly, the VLR allocates an MSRN from all MSRN pools. If the extended MSRN allocation function is enabled for the mode of random allocation, the VLR allocates a corresponding MSRN from the MSRN pool based on the attributes of the call and the callee.

5.

The HLR returns the MSRN to the (G)MSC server at the caller side.

11-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

11 Enhanced MSRN Allocation Feature

6. 7. 8. 9.

The (G)MSC server sends a request for setting up the call to the VMSC server of the callee based on the MSRN. The VMSC sever queries the VLR for the subscription information of the callee. After receiving the subscription information of the callee, the VMSC server checks the information, and sends a paging request to the callee. The callee sends a response to the MSC of the callee.

10. The MSC of the callee analyzes access data, and sets up the call with the caller side. The UE of the callee rings.
MSRN allocation is processed at the callee side in the module. This section does not give details.

11.4 Service Flow


11.4.1 General Procedure of MSRN Allocation
Figure 11-2 shows the general procedure of MSRN allocation. 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, and updates the values of the counters. MAP_VLR_MSRNAllocate_RSP MAP_PROVIDE_ROAMING_NUMBER_RSP [msrn] [msrn]

The VLR and HLR exchange and transfer the requests for MSRN allocation. The MSC server completes the interaction between the C/D interfaces of the VLR and the HLR, checks subscriber status, and conveys flag bits to the VLR. The VLR allocates an MSRN based on the configuration in the MSC server, and records the information required after the call is connected.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

11-7

11 Enhanced MSRN Allocation Feature

HUAWEI MSOFTX3000 Feature Description

11.4.2 Procedure for Random Allocation


Figure 11-3 shows the procedure for random allocation. 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, 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, and updates the values of the counters. 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. The MSC server analyzes the attribute of an incoming call. When receiving a request for allocating a roaming number from the HLR, 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 then stores the Province Flag in the MAP table so as to transfer the flag to the VLR when allocating a roaming number. 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, and then allocates a roaming number based on the attribute of the callee. If the inter-province roaming number resources of the callee are used up, the VLR allocates an intra-province roaming number so that the incoming call can be configured with a roaming number. The HLR must carry the GMSC number of the callee; otherwise, the MSC server cannot judge whether the incoming call is an inter-province call. In this case, the MSC server regards the incoming call as an inter-province call by default.

11-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

11 Enhanced MSRN Allocation Feature

11.5 Data Configuration


11.5.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 MSRN or HON Prefix table, the MSRN or HON Suffix table, and the Inner MSRN or HON Suffix table are mandatory. 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. 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 command ADD MHLAICFG or ADD MHMSCCFG is selected to configure the data.
Both the MHSUFFIX commands and the IMHSUFFIX commands are used to configure the MSRN or HON Suffix table, but they configure different types of roaming numbers. The differences are as follows: The IMHSUFFIX commands can configure inter-province roaming numbers. The MHSUFFIX commands cannot configure the inter-province roaming numbers.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

11-9

11 Enhanced MSRN Allocation Feature

HUAWEI MSOFTX3000 Feature Description

Configuration Steps
To configure an MSRN or HON, perform the following steps: Step 1 Run ADD VLRCFG to configure the basic functions of the VLR. The default allocation mode is Allocate randomly. Step 2 Run ADD MHPREFIX to configure the prefix of the MSRN. Step 3 Run ADD MHSUFFIX to configure the suffix of the MSRN. Step 4 To allocate an MSRN or HON based on the LAI number or the MSC number, modify the allocation mode by running MOD VLRCFG. Step 5 To enable the extended MSRN allocation function for the mode of random allocation, run MOD MSFP to change the value of BIT of VLR software parameter 1 to 1 from 11. Thus the roaming number resources are re-allocated, and the function of allocation based on the attributes of the call and the callee is enabled. Step 6 Run ADD IMHSUFFIX to add, or MOD IMHSUFFIX to modify the intra- and inter-province roaming numbers.

This step is applicable only when the extended MSRN allocation function for the mode of random allocation is enabled.

Step 7 Run ADD MSRNCTR to configure the GMSC connected to the local office in the case of an intra-province incoming call. This step is optional.

This step is applicable only when the MSRN allocation control function is enabled.

Step 8 For the mode of allocation based on the MSC number, run ADD MHMSCCFG to add the mapping between the MSC number and the MSRN or HON. Step 9 For the mode of allocation based on the LAI number, run ADD MHLAICFG to add the mapping between the LAI number and the MSRN or HON. ----End

11.5.2 Configuraing Data at the UMG8900 Side


None.

11.5.3 Configuration Examples


Scenario 1
The scenario is as follows: The local MSOFTX3000 serves as the MSC server of the peer office. MSRN/HON prefix is set to K'8613901106. MSRN/HON suffix ID is set to 1, Start MSRN/HON suffix to 000, and End MSRN/HON suffix to 499. Inner MSRN/HON suffix ID is set to 2, Start MSRN/HON suffix to 500, and End MSRN/HON suffix to 599.

11-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

11 Enhanced MSRN Allocation Feature

Inner MSRN/HON suffix ID is set to 3, Start MSRN/HON suffix to 600, and End MSRN/HON suffix to 699. Inner MSRN/HON suffix ID is set to 4, Start MSRN/HON suffix to 700, and End MSRN/HON suffix to 799. Inner MSRN/HON suffix ID is set to 5, Start MSRN/HON suffix to 800, and End MSRN/HON suffix to 899. The number of the GMSC connected to the MSOFTX3000 is 8613901105.

Scripts
The scripts are as follows: Step 1 Modify VLR configuration. Description Script Set MSRN allocation mode to Allocate randomly. MOD VLRCFG: MSRNAM=RAND;

Step 2 Add a mobile national access code. Description Script Set Mobile national access code to K'139. ADD NACODE: NAC=K'139;

Step 3 Add an MSRN or HON prefix. Description Script Set MSRN/HON prefix to K'8613901106, and MSRN/HON suffix length to 3. ADD MHPREFIX: ID=1, HPFX=K'8613901106, SFXL=3;

Step 4 Add an MSRN or HON suffix. Description Script Set MSRN/HON suffix ID to 1, Start MSRN/HON suffix to 000, and End MSRN/HON suffix to 499. ADD MHSUFFIX: ID=1, PFXIDX=1, SFXS="000", SFXE="499", MSRNT=MSRN;

Step 5 Add an inner MSRN or HON suffix. Description Script Set Inner MSRN/HON suffix ID to 2, Start MSRN/HON suffix to 500, and End MSRN/HON suffix to 599. ADD IMHSUFFIX: ID=2, PFXIDX=1, SFXS="500", SFXE="599", MSRNT=MSRNOPNCL;

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

11-11

11 Enhanced MSRN Allocation Feature

HUAWEI MSOFTX3000 Feature Description

Step 6 Add an inner MSRN or HON suffix. Description Script Set Inner MSRN/HON suffix ID to 3, Start MSRN/HON suffix to 600, and End MSRN/HON suffix to 699. ADD IMHSUFFIX: ID=3, PFXIDX=1, SFXS="600", SFXE="699", MSRNT=MSRNOPCL;

Step 7 Add an inner MSRN or HON suffix. Description Script Set Inner MSRN/HON suffix ID to 4, Start MSRN/HON suffix to 700, and End MSRN/HON suffix to 799. ADD IMHSUFFIX: ID=4, PFXIDX=1, SFXS="700", SFXE="799", MSRNT=MSRNOPNCR;

Step 8 Add an inner MSRN or HON suffix. Description Script Set Inner MSRN/HON suffix ID to 5, Start MSRN/HON suffix to 800, and End MSRN/HON suffix to 899. ADD IMHSUFFIX: ID=5, PFXIDX=1, SFXS="800", SFXE="899", MSRNT=MSRNOPCR;

Step 9 Enable the extended MSRN allocation function of the VLR for the mode of random allocation. Description Script Enable the extended MSRN allocation function of the VLR for the mode of random allocation. MOD MSFP: ID=P200, MODTYPE=P1, BIT=11, BITVAL=1;

Step 10 Add MSRN allocation control. Description Script Add MSRN allocation control. ADD MSRNCTR: ADDRTYPE=GMSC, ADDRESS=K'8613901105;

----End

Scenario 2
The local MSOFTX3000 serves as the MSC server of the peer office. MSRN allocation mode is set to Allocate according to LAI number. There are two number ranges: The MSRN or HON of the cell in the 2G network ranges from 86136000040001 to 86136000040999. MSRN/HON prefix ID is set to 0, MSRN/HON suffix ID to 0, and LAI number to 460000001.

11-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. MSRN/HON prefix ID is set to 0, MSRN/HON suffix ID to 1, and LAI number to 460000003.

Scripts
The scripts are as follows: Step 1 Modify VLR configuration. Description Script Set MSRN allocation mode to Allocate according to LAI number. MOD VLRCFG: MSRNAM=LAI;

Step 2 Add a mobile national access code. Description Script Set Mobile national access code to K'136. ADD NACODE: NAC=K'136;

Step 3 Add an MSRN or HON prefix. Description Script Set MSRN/HON prefix to K'8613600004, and MSRN/HON suffix length to 4. ADD MHPREFIX: MHPREFIX=K'8613600004, MHSL=4;

Step 4 Add an MSRN or HON suffix. Description Script Set MSRN/HON suffix ID to 0, Start MSRN/HON suffix to 0001, and End MSRN/HON suffix to 0999. ADD MHSUFFIX: PREFIXINDEX=0, SUFFIXSTART="0001", SUFFIXEND="0999", NUMBERTYPE=MSRNHON;

Step 5 Add an MSRN or HON suffix. Description Script Set MSRN/HON suffix ID to 1, Start MSRN/HON suffix to 1000, and End MSRN/HON suffix to 1999. ADD MHSUFFIX: PREFIXINDEX=1, SUFFIXSTART="1000", SUFFIXEND="1999", NUMBERTYPE=MSRNHON;

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

11-13

11 Enhanced MSRN Allocation Feature

HUAWEI MSOFTX3000 Feature Description

Step 6 List MSRN or HON suffixes. Description Script List MSRN or HON suffixes. LST MHSUFFIX;

Step 7 Add mapping between the LAI number and the MSRN or HON. Description You must add a cell first. 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, and MSRN/HON suffix ID to 0. ADD MHLAICFG: LAINUM="460000001", PRESUFFINDEX=0;

Script

Step 8 Add mapping between the LAI and the MSRN or HON. Description You must add a cell first. The MSRN or HON of the cell in the 3G network ranges from 86136000041000 to 861360000419999. To add mapping between the LAI number and the MSRN or HON, set LAI number to 460000003, and MSRN/HON suffix ID to 1. ADD MHLAICFG: LAINUM="460000003", PRESUFFINDEX=1;

Script

----End

11.6 Service Management


None.

11.7 Charging and CDR


The charging module puts the roaming number to be obtained into the call detail record (CDR), and then reports the CDR to the billing center. The billing center sorts different CDRs, judges the types of calls, and charges the calls.

11.8 Service Interaction


None.

11-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

11 Enhanced MSRN Allocation Feature

11.9 Reference
11.9.1 Protocols and Specifications
None.

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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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 12.9.2 Acronyms and Abbreviations .........................................................................................................12-23

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 12-1 MS-originated call (early assignment)..........................................................................................12-4 Figure 12-2 MS-originated call (late assignment) ............................................................................................12-5 Figure 12-3 MS-terminated call (early assignment) .........................................................................................12-6 Figure 12-4 MS-terminated call (late assignment) ...........................................................................................12-8 Figure 12-5 Early resource assignment for the caller .....................................................................................12-10 Figure 12-6 Late resource assignment for the caller ......................................................................................12-12 Figure 12-7 Early resource assignment for the callee.....................................................................................12-14 Figure 12-8 Late resource assignment for the callee ......................................................................................12-16

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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

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

12.1 Service Description 12.2 Availability

12.3 Working Principle 12.4 Service Flow 12.5 Data Configuration 12.6 Service Management 12.7 Charging and CDR 12.8 Service Interaction 12.9 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-1

12 Early and Late Assignment Feature

HUAWEI MSOFTX3000 Feature Description

12.1 Service Description


12.1.1 Function Code
Name Early and Late Assignment of Resources for Mobile Subscribers Code WMFD-161100

12.1.2 Definition
Resource assignment refers to the process of wireless resource allocation in call establishment. There are two modes of assignments in call establishment, that is, early assignment and late assignment. 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, after sending the Call Proceeding message to the caller, the MSC server allocates traffic channels for the caller before routing the call to the network where the callee resides. In the call establishment, after sending the Call Proceeding message to the caller, the MSC server allocates traffic channels for the caller after routing the call to the network where the callee resides. Usually, the network resources are allocated after the MS of the callee rings.

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. Through the Setup message, the MSC server notifies the callee that the traffic channels are allocated in Late assignment mode. Then the callee sends the Call Confirmed message and then immediately the Alerting message to the MSC server. The MSC server determines when to allocate the traffic channels. Usually, the traffic channels are allocated after the callee sends the Connect message.

12-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

12.1.3 Benefits
Beneficiary Operator Description Late assignment can help to save the air interface resources. For example, if a subscriber dials the wrong number and immediately terminates the call, the MSC server needs not to allocate air interface resources for the subscriber. The operator can utilize well the air interface resources based on the actual assignment modes of each location area or service area. Early assignment can help to reduce the wait time of the subscribers and improve the call completion rate.

Subscriber

12.2 Availability
12.2.1 Requirements for NEs
The function is implemented through the cooperation of NodeB, RNC, and CN, as shown in Table 12-1. 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.

12.2.2 Requirements for License


Early and late assignment is a basic service. A license is not required.

12.2.3 Applicable Version


The applicable HUAWEI CS product versions are shown in Table 12-2. 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

12 Early and Late Assignment Feature

HUAWEI MSOFTX3000 Feature Description

12.3 Working Principle


The MSOFTX3000 supports both early and late assignments. The two assignment modes are both implemented by configuring the information table of the local location area or service area. 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 assignment mode for some special services, for example, emergency calls and data services, is early assignment.

12.3.1 MS-Originated Call (Early Assignment)


Figure 12-1 illustrates the MS-originated call flow for early assignment. 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. 2. 3. 4. The MS sends the Channel Request message. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. The MS requests the MM channel to be allocated through the CM Service Request message. The MSC server starts the authentication flow when the MM channel is being established. (optional)

12-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

5. 6. 7.

The MSC server starts the encryption flow when the MM channel is being established. (optional) After the MM channel is allocated, the MS sends the Setup message to the MSC server to request the call to be established. 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. The MSC server sends the assignment request and begins the traffic channel allocation. After the MS of the callee rings, 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.

8. 9.

10. The ring back tone is provided by the MSC server. 11. After the callee answers the call, the conversation between the two parties begins and the MS-originated call is established successfully.

12.3.2 MS-Originated Call (Late Assignment)


Figure 12-2 illustrates the MS-originated call flow for late assignment. 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

12 Early and Late Assignment Feature

HUAWEI MSOFTX3000 Feature Description

1. 2. 3. 4. 5. 6. 7.

The MS sends the Channel Request message. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. The MS requests the MM channel to be allocated through the CM Service Request. The network starts the authentication flow when the call is being established. (optional) The MSC server starts the encryption flow when the MM channel is being established. (optional) After the MM channel is allocated, the MS sends the Setup message to MSC server to request the call to be established. 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. After the phone of the callee rings, 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. After the traffic channel is allocated, the MSC server plays the ring back tone to the MS.

8. 9.

10. After the callee answers the call, the MS tunes to the traffic channel and the MS-originated call is established.

12.3.3 MS-Terminated Call (Early Assignment)


Figure 12-3 illustrates the MS-terminated call flow for early assignment. 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)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

The MS-terminated call flow for early assignment is as follows: 1. 2. 3. 4. 5. 6. 7. 8. The network sends the Paging message to request the call to be established. After detecting that it is the target MS by checking the IMSI/TMSI, the MS sends the Channel Request message to the network side. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. After the RR channel is allocated, the MS sends the Paging Response message to the network side. The MSC server begins to allocate the MM channel. The network starts the authentication flow when the call is being established. (optional) The MSC server starts the encryption flow when the MM channel is being established. (optional) After the MM channel is allocated, 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 MS sends the Call Confirmed message to the network.

9.

10. The MSC server begins to allocate the network resources after receiving the Call Confirmed message 11. The MS sends the Alerting message to the network only after the traffic channel is allocated successfully. 12. The mobile-terminated call is established successfully after the callee answers the call.

MS-Terminated Call (Late Assignment)


Figure 12-4 illustrates the MS-terminated call flow for late assignment.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-7

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. 2. 3. 4. 5. 6. 7. 8. The network sends the Paging message to request the call to be established. After detecting that it is the target MS by checking the IMSI/TMSI, the MS sends the Channel Request message to the network side. The BSC/RNC requests the RR channel to be allocated through the Immediate Assignment message. After the RR channel is allocated, the MS sends the Paging Response message to the network side. The MSC server begins to allocate the MM channel. The network starts the authentication flow when the call is being established. (optional) The MSC server starts the encryption flow when the MM channel is being established. (optional) After the MM channel is allocated, 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. The MSC server notifies the MS that the assignment mode is late assignment by the Setup message. The callee sends the Call Confirmed message to the MSC server.

9.

12-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

10. The callee sends immediately the Alerting message to the MSC server. 11. The callee sends the Connect message to the MSC server. 12. The MSC server delivers the assignment request after receiving the Connect message. 13. After the network resources are allocated for the callee, the MSC server sends the Connect Acknowledge message to the callee and the call is established successfully.

12.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. You can determine whether to start the processes by configuring system data. Therefore, the two processes are not included in the following flow chart.

12.4.1 Early Resource Assignment for the Caller


Figure 12-5 illustrates the flow of early resource assignment for the caller.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-9

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. 2. 3. 4. 5. 6. 7. 8. The MS sends the CM Service Request message to the MSC-O through the BSS. The MSC-O sends the CM Service Accept message to the MS through the BSS to indicate that the request is accepted. After receiving the CM Service Accept message, the MS sends the Setup message to the MSC-O through the BSS. The MSC-O sends the Call Proceeding message to the MS. The MSC-O requests routing information of the callee from the HLR. 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 HLR provides the routing information of the callee to the MSC-O.

12-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

9.

The MSC-O requests the BSS to allocate the channel and the BSS sends the assignment request to the MS.

10. After the channel is allocated, 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. 11. The MSC-O sends the Alerting message to the MS to indicate that the MS of the callee is ringing. 12. The MSC-O sends the Connect message to the MS to indicate that the callee has answered the call. 13. The MS sends the Connect Acknowledge message to the MSC-O and the call is established.

12.4.2 Late Resource Assignment for the Caller


Figure 12-6 illustrates the flow of late resource assignment for the caller.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-11

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. 2. 3. 4. 5. 6. 7. 8. The MS sends the CM Service Request message to the MSC-O through the BSS. The MSC-O sends the CM Service Accept message to the MS through the BSS to indicate that the request is accepted. After receiving the CM Service Accept message, the MS sends the Setup message to the MSC-O through the BSS. The MSC-O sends the Call Proceeding message to the MS. The MSC-O requests routing information of the callee from the HLR. 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 HLR provides the routing information of the callee to the MSC-O.

12-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

9.

The MSC-O sends the Alerting message to the MS to indicate that the MS of the callee is ringing.

10. The MSC-O requests the BSS to allocate the channel and the BSS sends the assignment request to the MS. 11. After the channel is allocated, 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. 12. The MSC-O sends the Progress message to the MS to indicate that the assignment is complete. 13. The MSC-O sends the Connect message to the MS to indicate that the callee has answered the call. 14. The MS sends the Connect Acknowledge message to the MSC-O and the call is established.

12.4.3 Early Resource Assignment for the Callee


Figure 12-7 illustrates the flow of early resource assignment for the callee.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-13

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. If no wireless connection is set up between the network and the callee, the MSC delivers the Paging message to the BSS and the BSS broadcasts the Paging message through the paging channel. After detecting that it is being paged, the MS sends the Channel Request message to the BSS to request a channel. The BSS returns the Immediate Assignment message to notify the MS to use a dedicated signaling channel. The MS sends the Paging Response message through the channel to the BSS and the BSS sends the Paging Response message to the MSC. The MSC sends the Setup message to the MS.

2.

3. 4.

12-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

5. 6. 7.

The MS returns the Call Confirmed message to the MSC after receiving the Setup message. 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. After the assignment is complete, 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. The MS sends the Alerting message to the MSC to indicate that the MS of the callee is ringing. After the callee has answered the call, the MS sends the Connect message to the MSC.

8. 9.

10. The MSC sends the Connect Acknowledge message to the MS and the call is established.

12.4.4 Late Resource Assignment for the Callee


Figure 12-8 illustrates the flow of late resource assignment for the callee.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-15

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. If there is no wireless connection between the network and the callee, the MSC delivers the Paging message to the BSS and the BSS broadcasts the Paging message through the paging channel. After detecting that it is being paged, the MS sends the Channel Request message to the BSS to request for a channel. The BSS returns the Immediate Assignment to indicate the MS to use a dedicated signaling channel. The MS sends the Paging Response message through the channel to the BSS and the BSS sends the Paging Response message to the MSC. The MSC sends Setup message to the MS.

2.

3. 4.

12-16

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

5. 6. 7. 8. 9.

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. After the callee has answered the call, the MS sends the Connect message to the MSC. The MSC requests the BSS to allocate the channel and the BSS sends the Assignment request to the MS. After the assignment is complete, 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.

10. The MSC sends the Connect Acknowledge message to the MS and the call is established.

12.5 Data Configuration


12.5.1 MSOFTX3000 Data Configuration
For 2G network, the assignment mode is configured when the GCI is being added. The steps are as follows: Step 1 Use the LST INOFFMSC command to check if the local MSC and the VLR numbers are configured. If they are not configured, use the SET INOFFMSC command to configure the local MSC and VLR numbers. Step 2 Use LST BSC command to check if the BSC that the cell belongs to and its destination signaling point code are configured. If they are not configured, use the ADD BSC command to add the BSC and its destination signaling point code. Step 3 Use the LST CALLSRC command to check if the call source code corresponding with the cell is configured. If it is not configured, use the ADD CALLSRC command to add the source code for the cell. Step 4 Use the LST OFC command to check if the office direction number is configured for the BSC that the cell belongs to. If it is not configured, use the ADD OFC command to add the office direction number for the BSC that the cell belongs to. Step 5 Use the LST LAIGCI command to check if the LAI that the cell belongs to is configured. If it is not configured, use the ADD LAIGCI command to add the LAI that the cell belongs to. (Configure the parameters based on the information obtained in the preceding query and set the location area type to LAI.) Step 6 Use the ADD LAIGCI 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 select GCI for the location area type.) ----End

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-17

12 Early and Late Assignment Feature

HUAWEI MSOFTX3000 Feature Description

For 3G network, the assignment mode is configured when the SAI is being added. 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 they are not configured, use the SET INOFFMSC command to configure them. Step 2 Use the LST RNC command to check if the RNC that the cell belongs to is configured. If it is not configured, use the ADD RNC command to add the RNC and its destination signaling point code. Step 3 Use the LST CALLSRC command to check if the call source code of the cell is configured. If it is not configured, use the ADD CALLSRC command to add the call source code corresponding with the cell. Step 4 Use the LST OFC command to check if the office direction number of the RNC that the cell belongs to is configured. If it is not configured, use the ADD OFC command to add the office direction number of the RNC that the cell belongs to. Step 5 Use the LST LAISAI command to check if the LAI that the cell belongs to is configured. If it is not configured, use the ADD LAISAI command to add the LAI that the cell belongs to. (Configure the parameters based on the information obtained in the preceding query and set the location area type as LAI.) 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.) ----End

12.5.2 HLR Data Configuration


None.

12.5.3 UMG8900 Data Configuration


None.

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

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. 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", LAIGCINAME="BSC1-LAI", MSCN="8613600004", VLRN="8613600004", LAICAT=LAI, LAIT=HVLR, BSCDPC1="C01", CSNAME="CS-1";

Step 2 Add a 2G cell. 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",LAIGCINAME="BSC1-GCI", MSCN="8613600004", VLRN="8613600004", LAICAT=GCI, LAIT=HVLR, ISEARASN=LATEASN, BSCDPC1="C01", CSNAME="CS-1"; The ISEARASN parameter is valid only when the value of the LAICAT parameter is GCI.

Description

----End

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-19

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. 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", LAISAINAME="RNC1-LAI", MSCN="8613600004", VLRN="8613600004", LAICAT=LAI, LAIT=HVLR, RNCID1=1, CSNAME="CS-1";

Step 2 Add the information of the 3G service area.

12-20

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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", LAISAINAME="RNC1-SAI", MSCN="8613600004", VLRN="8613600004", LAICAT=SAI, LAIT=HVLR, ISEARASN=EARLYASN, RNCID1=1, CSNAME="CS-1"; The ISEARASN parameter is valid only when the value of the LAICAT parameter is SAI.

Description

----End

12.6 Service Management


12.6.1 Querying the Resource Assignment Mode
2G Network
To query the resource assignment mode of a specified cell, perform the following steps: Step 1 Enter the LST LAIGCI command in the command line window of the LMT. Step 2 Enter the ID of the cell to be queried in the Global cell ID field. Step 3 Press F9 or click ----End If you want to query the assignment modes of all the cells, skip step 2. .

3G Network
To query the resource assignment mode of a specified service area, 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. Step 3 Press F9 or click ----End .

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

12-21

12 Early and Late Assignment Feature

HUAWEI MSOFTX3000 Feature Description

If you want to query the assignment modes of all the service areas, skip step 2.

12.6.2 Changing the Resource Assignment Mode


2G Network
To change the resource assignment mode of a specified cell, perform the following steps: Step 1 Enter the MOD LAIGCI command in the command line window of the LMT. Step 2 Enter the ID of the cell to be modified in the Global cell ID field. Step 3 Enter the MSC ID of the location area to be modified in the MSC number of the LA cell field. Step 4 Set the Location area type to Local VLR. Step 5 Set the Early assignment flag to the required mode. Step 6 Press F9 or click ----End .

3G Network
To change the resource assignment mode of a specified service area, perform the following steps: Step 1 Enter the MOD LAISAI command in the command line window of the LMT. Step 2 Enter the number of the service area to be modified in the 3G service area number field. Step 3 Enter the MSC number of the 3G service area to be modified in the MSC number of 3G service area field. Step 4 Set the 3G service area type to Local VLR. Step 5 Set the Early assignment flag to the required mode. Step 6 Press F9 or click ----End .

12.7 Charging and CDR


None.

12.8 Service Interaction


The setting of the resource assignment type has no effect on the supplementary services.

12-22

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

12 Early and Late Assignment Feature

12.9 Reference
12.9.1 Protocols and Specifications
None.

12.9.2 Acronyms and Abbreviations


Acronyms
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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 13-1 Triggering IN service (T-CSI).......................................................................................................13-4 Figure 13-2 Routing out the call directly to another office (T -CSI) ................................................................13-5 Figure 13-3 Ignoring IN service (T-CSI)..........................................................................................................13-6 Figure 13-4 Triggering IN service (early forwarding with O-CSI) ..................................................................13-7 Figure 13-5 Routing out the call directly to another office (early forwarding with O-CSI).............................13-8 Figure 13-6 Ignoring IN service (early forwarding with O-CSI) .....................................................................13-9

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Tables

Tables
Table 13-1 Name and function code of the IN service triggering.....................................................................13-2 Table 13-2 Processing modes of the IN services ..............................................................................................13-2 Table 13-3 NEs related to the IN service triggering .........................................................................................13-3 Table 13-4 Versions that support the IN service triggering...............................................................................13-3

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

13
About This Chapter
Section 13.1 Service Description 13.2 Availability

IN Service Triggering 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 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.

13.3 Working Principle 13.4 Service Flow 13.5 Data Configuration 13.6 Service Management 13.7 Charging and CDR 13.8 Service Interaction 13.9 References

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

13-1

13 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

13.1 Service Description


13.1.1 Function Code
Table 13-1 lists the name and function code of the IN service triggering. Table 13-1 Name and function code of the IN service triggering. Name CAMEL phase2 CAMEL phase3 Code WMFD-150100 WMFD-150200 Applicable Versions V100R005

13.1.2 Definition
If MSOFTX3000 is adopted in the GMSC/SSP networking, and if the SCP interconnected with the MSOFTX3000 uses private INAP protocol, 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). To solve this problem, the MSOFTX3000 uses three modes to process the IN service s, as shown in Table 13-2. 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. The MSOFTX3000 does not trigger IN service and connects the call to the MSC/SSP that can trigger the IN service normally. The connected to MSC/SSP triggers the IN service. The MSOFTX3000 does not trigger IN service and connects the call as an ordinary call.

The carrier can determine the processing mode based on the actual situation.

The IN service triggering feature is supported only by the GMSC and TMSC.

13.1.3 Benefits
Beneficiary Carrier Mobile subscriber Description The carrier can control the IN service s more flexibly, thus the competitiveness of the carriers is highly enhanced. The subscribers can enjoy the IN services.

13-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

13.2 Availability
13.2.1 Requirement for NEs
The IN service triggering feature requires the corporation of the SCP and CN. Table 13-3 lists the NEs related with the IN service triggering. 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.

13.2.2 Requirement for License


The IN service triggering is an optional feature of the Huawei wireless core network. You can obtain this service without any license.

13.2.3 Applicable Versions


Table 13-4 lists the Huawei CS product versions that support the IN service triggering. 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.3 Working Principle


After the MSOFTX3000 obtains IN service data from the HLR, it queries the IN service control data table, and then processes the IN call based on the query results. 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 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

Triggering IN Service (T-CSI)


If the call is an IN call of the MT type, and if the T-CSI subscription information is contained in the subscription data of the called party, the MSOFTX3000 triggers the IN service in the T-CSI mode. The call procedure is as shown in Figure 13-1. Figure 13-1 Triggering IN service (T-CSI)
GMSC (MSOFTX3000) 1.IAM 2.SRI 3.SRI_ACK(TCSI) 4. Query IN service control data table 5.IDP(DP12)

VMSCa

HLR

SCP

VMSCb

6. IN service triggering flow 7.SRI 8.SRI_ACK(MSRN) 9.IAM 10.ACM 11.ACM

12.

Call process

The call procedure is as follows: 1. 2. 3. 4. 5. 6. 7. The GMSC receives the IAM message from the VMSC of the calling 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. The GMSC queries the IN service control data table. The query result is "Triggering IN service ". 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. The SCP of the called triggers the IN service after receiving the IDP message. The IN service triggering process completes. The GMSC sends for the second time the SRI message to the HLR of the called party. The SRI message contains the suppression T-CSI cell.

13-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

8. 9.

The HLR responses the SRI_ACK to the GMSC. The SRI_ACK contains the MSRN number of the called party. The GMSC sends the IAM message to the VMSC of the called party according to the MSRN number of the called party.

10. The VMSC of the called party responses an ACM message to the GMSC. 11. The GMSC responses the ACM message to the VMSC of the calling party. 12. 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, and if the T-CSI subscription information is contained in the subscription data 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. The call procedure is as shown in Figure 13-2. Figure 13-2 Routing out the call directly to another office (T -CSI)
VMSCa 1.IAM 2.SRI 3.SRI_ACK(TCSI) 4. Query the IN service control data table 5IAM 6.ACM 7.ACM GMSC HLR MSC/SSP

8. Call process

The call procedure is as follows: 1. 2. 3. 4. 5. 6. 7. The GMSC receives the IAM message from the VMSC of the calling 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. The GMSC queries the IN service control data table. The query result is "Routing out the call directly to another office". 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 responses the ACM message to the VMSC of the calling party.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

13-5

13 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

8.

The call is established.

Ignoring IN Service (T-CSI)


If the call is an IN call of the MT type, and if the T-CSI subscription information is contained in the subscription data of the called party, the MSOFTX3000 does not trigger the IN service and connects the call as an ordinary call. The call procedure is as shown in Figure 13-3. Figure 13-3 Ignoring IN service (T-CSI)

VMSCa 1.IAM

GMSC

HLR

SCP

VMSCb

2.SRI 3.SRI_ACK(TCSI) 4. Query the IN service control data table 5.SRI 6.SRI_ACK(MSRN) 7.IAM 8.ACM 9.ACM 10. Call process

1. 2. 3. 4. 5. 6. 7. 8. 9.

The GMSC receives the IAM message from the VMSC of the calling 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. The GMSC queries the IN service control data table. The query result is "Ignoring IN service ". The GMSC sends for the second time the SRI message to the HLR of the called party. The SRI message contains the suppression T-CSI cell. The HLR responses the SRI_ACK to the GMSC. The SRI_ACK contains the MSRN number of the called party. 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. The GMSC responses the ACM message to the VMSC of the calling party.

10. The call is established.

13-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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, and if the called party subscribes to the call forwarding service and the O-CSI service, the MSOFTX3000 triggers the IN service in the O-CSI mode. The call procedure is as shown in Figure 13-4. Figure 13-4 Triggering IN service (early forwarding with O-CSI)

VMSCa 1.IAM

GMSC

HLR

SCP

VMSCb

2.SRI 4. Query the IN servie control data table 3.SRI_ACK (early forwarding with O-CSI)

5. Call forwarding flow 6.IDP(DP2)

7.

IN service triggering flow 8.SRI 9.SRI_ACK(MSRN) 10.IAM 11.ACM

12.ACM

13.

Call process

The call procedure is as follows: 1. 2. 3. The GMSC receives the IAM message from the VMSC of the calling 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 call forwarding subscription information and the O-CSI subscription information of the called party. The GMSC queries the IN service control data table. The query result is "Triggering IN service ". The GMSC launches call forwarding according to the call forwarding subscription information of the called party. 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.

4. 5. 6.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

13-7

13 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

7. 8. 9.

The SCP triggers the IN service after receiving the IDP message. The IN service triggering process completes. The GMSC sends an SRI message to the HLR of the forwarded-to party. The HLR of the forwarded-to party responses an SRI_ACK to the GMSC. The SRI_ACK contains the MSRN number of the forwarded-to party.

10. The GMSC sends an IAM message to the VMSC of the forwarded-to party according to the MSRN number of the forwarded-to party. 11. The VMSC of the forwarded-to party responses the ACM message to the GMSC. 12. The GMSC responses the ACM message to the VMSC of the calling party. 13. The call is established.

Routing Out the Call Directly to Another Office (Early Forwarding with O-CSI)
If the call is an IN call of the MF type, and if the called party subscribes to the call forwarding service and the O-CSI service, the MSOFTX3000 does not trigger the IN service and connects the call to the MSC/SSP which can trigger the IN service normally. The call procedure is as shown in Figure 13-5. Figure 13-5 Routing out the call directly to another office (early forwarding with O-CSI)

VMSCa 1.IAM

GMSC

HLR

MSC/SSP

2.SRI 3.SRI_ACK (early forwarding with O-CSI) 5.IAM 6.ACM 7.ACM

4.

Query the IN service control data table

8.

Call process

1. 2. 3.

The GMSC receives the IAM message from the VMSC of the calling 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 call forwarding subscription information and the O-CSI subscription information of the called party. The GMSC queries the IN service control data table. The query result is "Routing out the call directly to another office".

4.

13-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

5. 6. 7. 8.

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 responses the ACM to the VMSC of the calling party. The call is established.

Ignoring IN Service (Early Forwarding With O-CSI)


If the call is an IN call of the MF type, and if and if the called party subscribes to the call forwarding service and the O-CSI service, the MSOFTX3000 does not trigger the IN service and connects the call as an ordinary call. The call procedure is as shown in Figure 13-6. Figure 13-6 Ignoring IN service (early forwarding with O-CSI)

VMSCa 1.IAM

GMSC

HLR

SCP

VMSCb

2.SRI Query the IN service control data table 3.SRI_ACK (early forwarding with O-CSI)

4.

5.Call forwarding flow 6.SRI 7.SRI_ACK(MSRN) 8.IAM 9.ACM 10.ACM 11.Call process

The call procedure is as follows: 1. 2. 3. The GMSC receives the IAM message from the VMSC of the calling 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 call forwarding subscription information and the O-CSI subscription information of the called party. The GMSC queries the IN service control data table. The query result is "Ignoring IN service ". The GMSC launches call forwarding according to the call forwarding subscription information of the called party.

4. 5.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

13-9

13 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

6. 7. 8. 9.

The GMSC sends an SRI message to the HLR of the forwarded-to party. The HLR of the forwarded-to party responses an SRI_ACK to the GMSC. The SRI_ACK contains the MSRN number of the forwarded-to party. 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 VMSC of the forwarded-to party responses the ACM message to the GMSC.

10. The GMSC responses the ACM message to the VMSC of the calling party. 11. The call is established.

13.4 Service Flow


No special service flow.

13.5 Data Configuration


13.5.1 Data Configuration for MSOFTX3000
If MSOFTX3000 is adopted in the GMSC/SSP networking, and if the SCP interconnected with the MSOFTX3000 uses private INAP protocol, the MSOFTX3000 fails to trigger the IN service when handling the IN service subscribers (the subscribers subscribe to the IN service in the HLR). To solve this problem, 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 carrier requires that the MSOFTX3000 connects the calls as ordinary calls (ignores IN service). When configuring the IN service control data, you can configure different processing modes (triggering IN service, routing out the call directly to another office, and ignoring IN service) according to the IN service triggering type, IN service key, and SCP address. You need pay attention that if the operator configures the IN service control data by using the command ADD INSRVCTRL, the charging of the IN service subscribers is affected. Therefore, the operator must be cautious when configuring this data. 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.

See online help for the descriptions of the parameters of related commands.

13.5.2 Data Configuration for HLR9820


The HLR9820 can provide this service without any extra data configuration.

13.5.3 Data Configuration for UMG8900


The UMG8900 can provide this service without any extra data configuration.

13-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

13.5.4 Example
Scenario 1
In an IN call, assume that: The subscriber data of the called party contains the T-CSI subscription information. The IN service key is 1. The SCP address is 8613977888 and the SCP uses the INAP private protocol. The MSOFTX3000 can not trigger the IN service when processing this call. In this case, the carrier changes the number of the called party and the call is directly transited to another MSC/SSP which triggers the IN service. No CDR is generated for the IN call of the called party. Assume that: The number of the called party is added with a prefix 123. The routing selection name of Routing out the call directly to another office is 10. The routing selection source name 0 has been defined in the call source table. Routing name 0 already exists.

Scripts for Configuration


Step 1 Configure the routing analysis data. 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", RSSN="0", R=0, ISUP=NOCHG;

Step 2 Configure the number conversion data. 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", DCT=TYPE1, DCP=0, ND=K'123;

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

13-11

13 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

Step 3 Configure the IN service control data. 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, SK=1, SA=K'8613977888, PT=SR, RSN="10", NSP=MOO, CLDNCN="10"; If the processing is configured as routing out the call directly to another office, you must configure a new routing selective code and assign the correct service feature.

Step 4 Modify the integrated control data of the CDR. Description Modifying the integrated control data of the CDR: Unselect the CDR for IN call of the called party in the CDR control indication. Script Note MOD GBILLCTRL: BCF=AI_MTC-0; If you execute this command, the MSOFTX3000 does not generate a CDR for the IN call of the called party.

----End

Scenario 2
In an IN call, assume that: The subscriber data contains the call forwarding unconditional (CFU) and O-CSI subscription information. The IN service key is 2. The SCP address is 8613977888 and the SCP uses the INAP private protocol. The MSOFTX3000 can not trigger the IN service when processing this call. In this case, the carrier ignores the IN attributes of the call and connects the call as an ordinary call. No CDR is generated for the IN call of CFU.

13-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

Scripts for Data Configuration


Step 1 Configure the IN service control data. 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, SK=2, SA=K'8613977888, PT=IGNR;

Step 2 Modify the integrated control data of the CDR. Description Script Note Modifying the integrated control data of the CDR: Unselect the CDR for IN call of CFU in the CDR control indication. MOD GBILLCTRL: BCF=AI_CFW-0; If you execute this command, the MSOFTX3000 does not generate a CDR for IN call of CFU.

----End

Scenario 3
In an IN call, assume that: The subscriber data contains the CFU and O-CSI subscription information. The IN service key is 3. The SCP address is 8613977888. The MSOFTX3000 can trigger the IN service normally in the SCP. The carrier triggers the IN service and generates a CDR for the IN call of CFU.

Scripts for Data Configuration


Step 1 Configure the IN service control data. 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, SA=K'8613977888, PT=TRG;

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

13-13

13 IN Service Triggering Feature

HUAWEI MSOFTX3000 Feature Description

Step 2 Modify the integrated control data of the CDR. Description Script Note Modifying the integrated control data of the CDR: Select CDR for IN call forwarding. MOD GBILLCTRL: BCF=AI_CFW-1; If you execute this command, the MSOFTX3000 is restricted to generate a CDR for the IN call of CFU.

----End

13.6 Service Management


None.

13.7 Charging and CDR


If the operator configures the IN service control data by using the command ADD INSRVCTRL, the charging of the IN service subscribers is affected. Therefore, the operator must be cautious when configuring this data. 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. 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, and if the IN service is triggered in the O-CSI mode, CDR for IN call forwarding is generated. If CDR for IN call forwarding is not selected, no CDR for IN call forwarding is generated. If CDR for IN Called Party is selected, and if the IN service is triggered in the T-CSI mode, CDR for IN called party is generated. If CDR for IN Called Party is not selected, no CDR for IN called party is generated.

13.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 option Mobile subscriber as the calling party of the IN service triggering type in the IN service control data is not in current use. It is kept for later upgrade.

13-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

13 IN Service Triggering Feature

13.9 References
13.9.1 Specifications
None.

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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
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 14.5.2 Data Configuration on the UMG8900..............................................................................................14-9 14.5.3 Data Configuration Examples ..........................................................................................................14-9 14.6 Service Management ...............................................................................................................................14-15 14.7 Charging and CDR ..................................................................................................................................14-15 14.8 Service Interaction ..................................................................................................................................14-16 14.9 Reference ................................................................................................................................................14-16 14.9.1 Protocols and Specifications ..........................................................................................................14-16 14.9.2 Acronyms and Abbreviations .........................................................................................................14-16

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Figures

HUAWEI MSOFTX3000 Feature Description

Figures
Figure 14-1 Networking of MNP service .........................................................................................................14-4 Figure 14-2 External network subscriber calls a ported out local network subscriber .....................................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-6 Figure 14-4 MNP service flow in OR mode.....................................................................................................14-7 Figure 14-5 Local network subscriber calls a ported out local network subscriber based on the IN................14-8 Figure 14-6 Local network subscriber calls a ported out local network subscriber based on signaling ...........14-8

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

14
About This Chapter
The following table lists the contents of this chapter. Section 14.1 Feature Description Describes 14.2 Availability

MNP Feature

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.

14.3 Principle Description 14.4 Service Flows 14.5 Data Configuration 14.6 Service Management

14.7 Charging and 14.8 Service Interaction 14.9 Reference

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-1

14 MNP Feature

HUAWEI MSOFTX3000 Feature Description

14.1 Feature Description


14.1.1 Feature Code
Feature Name MNP Feature Feature Code WMFD-042500

14.1.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, and to preserve the original MSISDNs at the same time. All the services of the subscriber are provided by the new network. They are not affected by the original network. The new network also assigns a new International Mobile Subscriber Identity (IMSI) to the MNP subscriber. In one network, MNP subscribers and non-MNP subscribes enjoy service functions of no difference, but there are differences in service qualities, such as the additional call setup delay. 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. Independent subscription service: The original network has no impact upon the current services of subscribers. If certain services supported by the original network are not supported by the new network, subscribers cannot enjoy the services. Ported many times: There can be numbers ported both in and out in one network. One MSISDN can be ported for multiple times and can be ported back and forth in multiple networks. Independent service: It does not conflict with other mobile services provided by the system.

14.1.3 Service Benefits


Beneficiary Carriers Benefit Description For new carriers, the MNP feature attracts new subscribers and enhances competition capability. For mature carriers, the MNP service brings additional management charges and increases operation revenue. Mobile subscribers Based on the changes of locations, subscribers can choose different networks or more suitable carriers without changing their numbers. Subscribers can subscribe networks of one carrier in different areas and remain the original number. For example, a subscriber registers a number in area A. This number belongs to the number segment of area A. After moving to place B, the subscriber can register the same number in area B.

14-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

14.2 Availability
14.2.1 Related Network Elements
The realization of the MNP feature requires the cooperation of the network elements (NEs) listed in Table 14-1. 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.

14.2.2 License Support


The MNP feature is an optional feature of Huawei wireless core network. The MNP services are available only when the MSOFTX3000 License is obtained.

14.2.3 Version Support


Table 14-2 lists the product versions that support the MNP feature. 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.3 Principle Description


14.3.1 Functions of NEs
The HLR stores the subscription information, home area and home network information of subscribers. The MSC server provides services to subscribers based on their subscription information.

14.3.2 System Interior Processing


Figure 14-1 shows the typical networking of the MNP service.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-3

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, the SPS serves as the MNP-Signaling Relay Function (SRF) and Number Portability Database (NPDB). It is before the HLR in service flows and often configured in pairs. The MNP feature requires that the network addresses in the "Route on GT" mode, and use the SPS as the translation point. The 3G TS 23.066 defines two modes to realize the MNP. One is based on the IN, while the other is based on signaling relay. The MSC queries the MNP Service Processing Table to determine the subsequent processing type: IN based original call query, Release, or No processing. The IN based original call query mode is not usually used. 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)

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

14.4 Service Flows


14.4.1 QoR Mode
RN is the route number. Every carrier is assigned with one RN, such as C0101, and C0102. If there is no special note in this article, RNP4 refers to the RN of P4, RNx refers to RN of external network, and NonNP means that no number is ported.

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. Based on the result of querying related table, the NPDB determines whether to deliver the SRI to the HLR or return an SRlack message to the GMSC. When receiving the SRIack, the GMSC queries the MNP Service Processing Table. Based on the result, the GMSC processes as follows: If the returned MSRN is "Foreign RNx + MSISDN" or "NonNP + MSISDN", the GMSC disconnects the call. (If the prefix is RN, the REL message carries a disconnect cause value of 14. If the prefix is NonNP, the REL message carries a disconnect cause value of 1. In the latter case, the system generates an alarm.) Otherwise, the GMSC normally connects the call. The VMSC does failure processing to the REL message returned by the GMSC. If the cause value is 14, the VMSC re-routes the call to the NPDB to obtain the RNx.

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. 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 GMSC receives an IAM message sent by the VMSC. The message carries a called number with the number segment of the local network. The called number does not carry an RN prefix.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-5

14 MNP Feature

HUAWEI MSOFTX3000 Feature Description

2. 3. 4.

The GMSC sends an SRI to the NPDB. After querying related table, the NPDB returns an SRIack (RNx + MSISDN) to the GMSC. The GMSC sends a REL message to the VMSC. The VMSC disconnects the call. The call termination cause value is 14, indicating that the called number is ported out.
In the trial bill, the called number is the MSISDN. The call termination cause value is 14, 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. The caller thinks that the callee ported in the local network, but the called does not exist in the local network. Figure 14-3 shows the flow. 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. 2. 3. 4.

The VMSC sends an IAM message to the GMSC. The called number carries the RN prefix of the local network, that is, RNP4. The GMSC sends an SRI to the NPDB. After querying table, the NPDB returns an SRIack (NonNP + MSISDN or RNx + MSISDN) to the GMSC. The GMSC sends an REL message to the VMSC. The VMSC disconnects the call. The call termination cause value of 1, indicating that the called number is not allocated.
In the trial bill, the called number is RNP4 + MSISDN. The call termination cause value is 1, indicating that the called number is not allocated. NonNP + MSISDN returned by the STP means that this MSISDN is a non-NP subscriber.

14.4.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. If a called number ports to external network, the

14-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

NPDB returns an SRlack (RN + MSISDN). When receiving the SRlack, the GSMC queries the MNP Service Processing Table and selects a processing type. Figure 14-4 shows the MNP service flow in the OR mode. 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. 2. 3. 4.

The PSTN sends an IAM message to the GMSCa. The IAM message carries the information of the called number that belongs to the local network number segment. The GMSCa sends an SRI to the NPDB. After querying table, the NPDB returns an SRIack (RNx + MSISDN) to the GMSCa. The GMSCa routes the call to the correct network, such as the GMSCb.
In the GWI, the called number is the MSISDN. In this case, the subscriber is not charged. The called number in the GWO is RNx + MSISDN. (For a GV integrated office, the called number in the GWO is MSISDN. For a GMSC, the called number in the GWO is RNx + MSISDN.)

14.4.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 MSC routes the call to the NPDB or reports to the NPDB through an IDP message. Based on the result, the MSC sends the IAM out of the office or pages the callee.

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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-7

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,Cdpa=MSISDN) IDP (DP2,Cdpa=MSISDN) Connect (Cdpa=RNx+MSISDN) IAM (RNx+MSISDN)

1. 2. 3. 4.

The local network subscriber initiates a call, triggers the IN, and reports an IDP message to the NPDB. The NPDB transparently transfers the IDP message to the SCP. The SCP returns the CONNECT (RNx + MSISDN) message to the VMSC. The VMSC routes the call to the correct network.
IN bills are generated. In the MOC, the called number is the MSISDN. The translatedNumber is RNx + MSISDN.

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

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

1. 2. 3.

The subscriber initiates a call. The VMSC sends an SRI to the NPDB. After querying table, the NPDB returns an SRIack (RNx + MSISDN) to the VMSC. The VMSC routes the call to the correct network.
In the MOC, the called number is the MSISDN. The translatedNumber is RNx + MSISDN.

14.5 Data Configuration


14.5.1 Data Configuration on the MSOFTX3000
Step 1 Run ADD MNP to add records in the MNP Service Table. 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. Step 4 Run ADD CNACLD to add called number analysis data. Step 5 Run ADD SCPPARA to add SCP parameters. (This step is required only when the MNP processing type is IN-based MO query.) Step 6 Run ADD CLDPREANA to add called number pre-analysis data. Step 7 Run ADD AIDNUMPRO to add auxiliary number change data. Step 8 Run ADD CFPRO to add failure processing data. Step 9 Run ADD DNC to add number change data. ----End

14.5.2 Data Configuration on the UMG8900


None.

14.5.3 Data Configuration Examples


Case 1
QoR mode: An external network subscriber calls a ported out local network subscriber. The GMSC queries the NPDB. The NPDB returns an SRlack with the RNx prefix and the MSISDN. The calling office routes the call to a third-party network based on the RNx prefix.

Configuration Scripts
The data configuration of the local office is as follows: Step 1 Add the GT translation to the NPDB.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-9

14 MNP Feature

HUAWEI MSOFTX3000 Feature Description

Description

Add the GT translation to the NPDB to translate corresponding number segments to the NPDB.
Note: The SCCPDSP and SCCP subsystems require independent configuration.

Script

ADD SCCPGT: GTN="10", ADDR=K'48139075203, RESULTT=STP1, SPC="111111";

Step 2 Add the global translation code information of the IMSI. Description Script Add the global translation code information of the IMSI. ADD IMSIGT: MCCMNC=K'460077552000395, CCNDC=K'48139075203, MNNAME="MNP TEST";

Step 3 Configure the Called Number Pre-analysis Table. Description Script Configure the Called Number Pre-analysis Table. Set Processing type to No processing to prevent adding "00" when adjusting the called number. ADD CLDPREANA: CSCNAME=65534, CS=ALL, PFX=K'C0101, MINCLDLEN=6, CDADDR=ALL, CRP=ALL, PT=DONTPROC;

Step 4 Configure the MNP Service Table. Description Configure the MNP Service Table. Set Call source to 0, Call originator to MAP non-forwarding, Called prefix to C0101, Minimum number length to 5, Maximum number length to 20, MNP processing type to External network NP prefix, MNP processing type to Disconnect, Disconnect cause code to 142, and Alarm flag to No. ADD INMNP: CLDPFX=K'C0101, MINDNLEN=5, MAXDNLEN=20, MNPPFT=OTHER, MNPPRT=REL, FCC=CV142, ALMF=NO;

Script

----End The data configuration of the originating office: Step 1 Configure the Called NO Analysis Table. Description Script Configure the Called NO Analysis Table. ADD CNACLD: P=9, PFX=K'C0101, CSA=MLCT, RSN="5", MINL=5, MAXL=32, ICLDTYPE=PS; ADD CNACLD: PFX=K'139075203, MINL=3, MAXL=20, ICLDTYPE=MS;

14-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

Step 2 Add the GT translation to the NPDB. Description Add the GT translation to the NPDB to translate corresponding number segments to the NPDB.
Note: The SCCPDSP and SCCP subsystems require independent configuration.

Script

ADD SCCPGT: GTN=10, ADDR=K'48139075203, RESULTT=STP1, SPC="111111";

Step 3 Add the global translation code information of the IMSI. Description Script Add the global translation code information of the IMSI. ADD IMSIGT: MCCMNC=K'460077552000395, CCNDC=K'48139075203, MNNAME="MNP test";

Step 4 Configure the Called Number Pre-analysis Table. Description Script Configure the Called Number Pre-analysis Table. ADD CLDPREANA: CSCNAME=65534, CS=ALL, PFX=K'C0101, MINCLDLEN=6, CDADDR=ALL, CRP=ALL, PT=DONTPROC;

Step 5 Configure the Number Change Table. Description Script Configure the Number Change Table. Set the Number Change Table to add prefix to the called number. ADD DNC: DCN="1", DCT=TYPE1, ND=K'123;

Step 6 Configure the Call Failure Processing Table. Description Script Configure the Call Failure Processing Table. Set Failure cause code to 142 for failure processing. ADD CFPRO: FCC=CV142, FSC=0, RUT=CAT10, PT=CPA, DCN="1";

Step 7 Configure the Auxiliary Number Change Table.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-11

14 MNP Feature

HUAWEI MSOFTX3000 Feature Description

Description

Configure the Auxiliary Number Change Table.


Note: Configure the Number Change Table to delete the prefix "123".

Script

ADD AIDNUMPRO: CSCNAME="0", NUMTY=TY4, P=9, PFX=K'123, CDX=1;

----End

Case 2
QoR mode: An external network subscriber calls a local network subscriber. The caller thinks that the callee ported in the local network, but the callee does not exist in the local network. The GMSC queries the NPDB. The NPDB returns an SRlack with the NonNP prefix and the MSISDN. The GMSC sends a disconnecting message to the originating office.

Configuration Scripts
Step 1 Add the GT translation to the NPDB. Description Add the GT translation to the NPDB.
Note: The SCCPDSP and SCCP subsystems require independent configuration.

Script

ADD SCCPGT: GTN="10", ADDR=K'48139075203, RESULTT=STP1, SPC="111111";

Step 2 Add the global translation code information of the IMSI. Description Script Add the global translation code information of the IMSI. ADD IMSIGT: MCCMNC=K'460077552000395, CCNDC=K'48139075203, MNNAME="MNP test";

Step 3 Configure the Called Number Pre-analysis Table. Description Script Configure the Called Number Pre-analysis Table. Set Processing type to No processing to prevent adding "00" when adjusting the called number. ADD CLDPREANA: CSCNAME="65534", CS=ALL, PFX=K'C0101, MINCLDLEN=6, CDADDR=ALL, CRP=ALL, PT=DONTPROC;

14-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

Step 4 Configure the MNP Service Table. Description Configure the MNP Service Table. Set Call source to 0, Call originator to Wildcard, Called prefix to C0101, Minimum number length to 5, Maximum number length to 20, MNP processing type to Local network NP prefix, MNP processing type to Disconnect, Disconnect cause code to 142, and Alarm flag to No. ADD INMNP: CLDPFX=K'C0101, MINDNLEN=5, MAXDNLEN=20, MNPPFT=LOC, MNPPRT=REL, FCC=CV142, ALMF=YES;

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, the GMSC sends an SRI to the NPDB. If the called number ports out of the local network, the NPDB returns an SRlack (RNx + MSISDN). When receiving the SRlack, the GMSC queries the MNP Service Processing Table to select a processing type.

Configuration Scripts
Step 1 Add the GT translation to the NPDB. Description Add the GT translation to the NPDB.
Note: The SCCPDSP and SCCP subsystems require independent configuration.

Script

ADD SCCPGT: GTN="10", ADDR=K'48139075203, RESULTT=STP1, SPC="111111";

Step 2 Add the global translation code information of the IMSI. Description Script Add the global translation code information of the IMSI. ADD IMSIGT: MCCMNC=K'460077552000395, CCNDC=K'48139075203, MNNAME="MNP test";

Step 3 Configure the Called Number Pre-analysis Table. Description Script Configure the Called Number Pre-analysis Table. Set Processing type to No processing to prevent adding "00" when adjusting the called number. ADD CLDPREANA: CSCNAME="65534", CS=ALL, PFX=K'C0101, MINCLDLEN=6, CDADDR=ALL, CRP=ALL, PT=DONTPROC;

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-13

14 MNP Feature

HUAWEI MSOFTX3000 Feature Description

Step 4 Configure the MNP Service Table. Description Configure the MNP Service Table. Set Call source to 0, Call originator to Wildcard, Called prefix to C0101, Minimum number length to 5, Maximum number length to 20, MNP processing type to Local network NP prefix, and MNP processing type to No processing. ADD INMNP: CLDPFX=K'C0101, MINDNLEN=5, MAXDNLEN=20, MNPPFT=LOC, MNPPRT=DONTPROC;

Script

----End

Case 4
AcQ mode: A local network subscriber calls a ported out local network subscriber based on signaling. The originating office queries the NPDB. The NPDB returns an SRlack with the RNx and the MSISDN. The originating office routes to a third-party network based on the RNx.

Configuration Scripts
Step 1 Add the GT translation to the NPDB. Description Add the GT translation to the NPDB.
Note: The SCCPDSP and SCCP subsystems require independent configuration.

Script

ADD SCCPGT: GTN="10", ADDR=K'48139075203, RESULTT=STP1, SPC="111111";

Step 2 Add the global translation code information of the IMSI. Description Script Add the global translation code information of the IMSI. ADD IMSIGT: MCCMNC=K'460077552000395, CCNDC=K'48139075203, MNNAME="MNP test";

Step 3 Configure the Called Number Pre-analysis Table. Description Script Configure the Called Number Pre-analysis Table. Set Processing type to No processing to prevent adding "00" when adjusting the called number. ADD CLDPREANA: CSCNAME="65534", CS=ALL, PFX=K'C0101, MINCLDLEN=6, CDADDR=ALL, CRP=ALL, PT=DONTPROC;

14-14

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

14 MNP Feature

Step 4 Configure the Called NO Analysis Table. Description Script Configure the Called NO Analysis Table. ADD CNACLD: P=9, PFX=K'C0101, CSA=MLCT, RSN="5", MINL=5, MAXL=32, ICLDTYPE=PS;

Step 5 Configure the MNP Service Table. Description Configure the MNP Service Table. Set Call source to 0, Call originator to Wildcard, Called prefix to C0101, Minimum number length to 5, Maximum number length to 20, MNP processing type to Local network NP prefix, and MNP processing type to No processing. ADD INMNP: CLDPFX=K'C0101, MINDNLEN=5, MAXDNLEN=20, MNPPFT=LOC, MNPPRT=DONTPROC;

Script

----End

14.6 Service Management


None.

14.7 Charging and CDR


The charging and bill generating principles of the MNP feature are as follows: If IN services are triggered, IN bills are generated. If the roaming number brought back by the NPDB is (RN + MSISDN), the translatedNumber in the bill is RN + MSISDN. 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. = 0: Overseas requirement = 1: Domestic requirement Default value: 1 Bit 1: Controls the format of called numbers in the bill. = 0: Fill the numbers after adjustment. = 1: Fill the numbers the subscribers dial. Default value: 1
Bit 1 is valid only when bit 4 is set to 0. When bit 4 is set to 1, bit 1 is invalid.

It can also be controlled by bit 2 of the software parameter P1300:

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

14-15

14 MNP Feature

HUAWEI MSOFTX3000 Feature Description

Bit 2: Defines the filling principles of the called numbers in the GWO bill. 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. = 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. The MSRN prefix is the RN number.

14.8 Service Interaction


The MNP feature has service interaction with the ETSI interception. For details, refer to the design specifications of the ETSI interception.

14.9 Reference
14.9.1 Protocols and Specifications
The references of the MNP feature are as follows: 3GPP TS 23.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)

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

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
15 IP Fax Feature..........................................................................................................................15-1
15.1 Service Description ...................................................................................................................................15-2 15.2 Working Principle......................................................................................................................................15-2 15.3 Benefits .....................................................................................................................................................15-2 15.3.1 To Carriers........................................................................................................................................15-2 15.3.2 To Mobile Subscribers .....................................................................................................................15-2 15.4 Availability ................................................................................................................................................15-2 15.4.1 Application.......................................................................................................................................15-2 15.4.2 Requirements for Software ..............................................................................................................15-3 15.4.3 Requirements for Hardware .............................................................................................................15-3 15.5 Service Flow..............................................................................................................................................15-3 15.5.1 Classification of Call Model ............................................................................................................15-3 15.5.2 Processing Flow ...............................................................................................................................15-3 15.6 Data Configuration....................................................................................................................................15-7 15.6.1 Configuring Data at the MSOFTX3000 Side...................................................................................15-7 15.6.2 Data Configuration Example............................................................................................................15-9 15.7 Service Management ...............................................................................................................................15-10 15.8 Charging and CDR ..................................................................................................................................15-10 15.9 Service Interaction ..................................................................................................................................15-10

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Tables

HUAWEI MSOFTX3000 Feature Description

Tables
Table 15-1 Value options of Support FAX detection ........................................................................................15-8 Table 15-2 Value options of Support 2198 redundancy ....................................................................................15-8 Table 15-3 Value options of 2198 UP Mode.....................................................................................................15-8 Table 15-4 Value options of 2198 redundancy level.........................................................................................15-8 Table 15-5 Value options of 2198 redundancy CODEC type ...........................................................................15-9 Table 15-6 Value options of BICC support red.................................................................................................15-9

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

15 IP Fax Feature

15
About This Chapter
The following table lists the contents of this chapter. Section 15.1 Service Description 15.2 Working Principle 15.3 Benefits 15.4 Availability 15.5 Service Flow 15.6 Data Configuration 15.7 Service Management 15.8 Charging and CDR 15.9 Service Interaction Describes

IP Fax Feature

The function code and definition of this feature. The principle of the implementation of this feature. The benefits to the carrier and mobile subscribers when this service is used. The application and requirements of this feature. The service flow of the network when providing this feature. The data configuration that is required at the MSOFTX3000 side. The operations that the carrier and subscribers must perform for the implementation of 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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

15-1

15 IP Fax Feature

HUAWEI MSOFTX3000 Feature Description

15.1 Service Description


IP fax is the fax service over IP. Data transmission plays an important role in the fax process, because the quality of data transmission determines that of fax. The data stream redundancy is a solution to the data packet loss during transmission. Transmission supporting the data stream redundancy is a type of enhanced service. This service can improve the data transmission quality, and reduce or avoid the service termination caused by bad data transmission quality.

15.2 Working Principle


During a call, the MSC server determines whether to send 2198 redundancy parameter of the data service to the MGW based on data configuration. In addition, the MSC server determines whether to notify the MGW to start fax event detection after a call is initiated based on data configuration. The MGW reports fax tone detection event and fax status detection event. The MSC server sends indication of modifying codec property to the MGW based on reported detection events, thus to support data redundancy.

15.3 Benefits
15.3.1 To Carriers
The IP fax feature increases the quality of the fax data transmission and enhances the competitive edge of carriers.

15.3.2 To Mobile Subscribers


Mobile subscribers can enjoy the high-quality fax service.

15.4 Availability
15.4.1 Application
The MSOFTX3000 V100R005 provides the IP fax service. The TS62 service is applicable to visited MSC (VMSC), gateway MSC (GMSC), and tandem MSC (TMSC). The TS61 service is applicable to TMSC only. The limitations of the IP fax service is as follows: The VMSC cannot trigger the TS61 service that contains 2198 redundancy data. The VMSC does not support fax detection. To implement 2198 redundancy transmission for inter-office BICC fax, the TrFO function must be enabled. The modification of 2198 redundancy configuration is not allowed during data service calls.

15-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. The distributed interworking function (IWF) is not supported.

15.4.2 Requirements for Software


None.

15.4.3 Requirements for Hardware


None.

15.5 Service Flow


15.5.1 Classification of Call Model
TS61 fax processing on the TMSC TS62 fax processing on the GMSC, VMSC, or TMSC

15.5.2 Processing Flow


TS61 and TS62 Call Processing Flows on the TMSC when the ISUP/TUP/BICC Signaling is Used
ISUP/TUPISUP/TUP When a call is initiated, the TDM point sends the fax detection event to the gateway and meanwhile sends the 2198 data service redundancy modification request. When a fax call is initiated, the gateway reports the fax event, sends the CODEC modification request to the local-end gateway to modify the terminal point, and meanwhile sends the modification request to the peer end. If the local end is the outgoing side, it also needs to send the intermediate bearer request to the gateway. After the fax ends, the gateway reports the fax complete event and the local end sends the open EC operation request to the gateway.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

15-3

15 IP Fax Feature

HUAWEI MSOFTX3000 Feature Description

MSOFTX3000

(1) (2) (3)

(4) IP

Incoming side

Outgoing side

1. Report the fax detection event. 3. Return successful 1T modification response.

2. Send the 1T modification request. 4. Notify the peer end to send the CODEC modification request.

ISUP/TUPBICC When a call is initiated, the TDM point sends the fax detection event to the gateway and meanwhile sends the 2198 data service redundancy modification request. When a fax call is initiated, the gateway reports the fax event, sends the CODEC modification request to the local-end gateway to modify the terminal point, and meanwhile sends the modification request to the peer end. The BICC uses the CODEC re-negotiation flow to modify the IP point. After the fax ends, the gateway reports the fax complete event and the local end sends the open EC operation request to the gateway.

MSOFTX3000

(1) (2) (3)

(4) IP

Incoming side

Outgoing side

1. Report the fax detection event. 3. Return successful 1T modification response.

2. Send the 1T modification request. 4. Notify the peer end to send the CODEC modification request.

BICCISUP/TUP When a call is initiated, the TDM point sends the fax detection event to the gateway and meanwhile sends the 2198 data service redundancy modification request.

15-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

15 IP Fax Feature

When a fax call is initiated, the gateway reports the fax event, sends the CODEC modification request to the local-end gateway to modify the terminal point, and meanwhile sends the modification request to the peer end. The BICC uses the CODEC re-negotiation flow to modify the IP point. After the fax ends, 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. Report the fax detection event. 3. Return successful 1T modification response. 5. Return successful 2T modification response.

2. Send the 1T modification request. 4. Send the 2T modification request. 6. Notify the peer end to send the CODEC modification request.

"Send the 1T modification request" refers to the local-end terminal point modification request. "Send the 2T modification request" refers to the intermediate bearer modification request. For the case of switching the fax to the voice call, observe the original processing flow. This feature does not involve the processing of this part.

BICCBICC The MSOFTX3000 receives the CODEC modification request from another MSC (calling party/called party). The MSOFTX3000 sends the CODEC modification request to the gateway and meanwhile notifies 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.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

15-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 3. Return successful modification response. 5. Return successful modification response.

2. Send the CODED modification request 4. Send the CODED modification request. 6. 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. The TMSC sends the PREPARE BEARER REQ, which carries the redundancy parameter.

MSOFTX3000

(1)

(2)

(3)

(4)

Incoming side

IP

Outgoing side

1. PB with redundancy parameter 3. PB with redundancy parameter

2. PB response 4. 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, the local office negotiates with the peer office. If the message carrying the 2198 redundancy CODEC is received in an incoming BICC call, the local office judges whether it supports the 2198 redundancy capability and records the result. After the negotiation is completed, the MSOFTX3000 sends the CODEC modification request to the gateway.

15-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

15 IP Fax Feature

MSOFTX3000

BICC

MSOFTX3000

(1)

(2)

(3)

(4)

MGW
1. Send the modification request. 3. Send the modification request.

MGW
2. Return the modification request. 4. Return the modification request.

Intra-VMSC Cross-Gateway (Over IP) TS62 Call Processing Flow


The VMSC determines that the current service is a data service. The VMSC sends the PREPARE BEARER REQ, which carries the redundancy parameter.

MSOFTX3000

(1)

(2)

(3)

(4)

Incoming side

IP

Outgoing side

1. PB with redundancy parameter 3. PB with redundancy parameter

2. PB response 4. PB response

15.6 Data Configuration


15.6.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. Table 15-1 lists the value options of this parameter.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

15-7

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. (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. 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. The local office does not support the 2198 data redundancy. (default value)

Use the parameter 2198 UP Mode in the Local Office Information table to configure 2198 data redundancy. Table 15-3 lists the value options of this parameter. 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. (default value) The support mode is adopted for the 2198 UP mode of the local office.

Use the parameter 2198 redundancy level in the Local Office Information table to configure 2198 data redundancy. Table 15-4 lists the value options of this parameter. Table 15-4 Value options of 2198 redundancy level Value 1 2 Meaning The 2198 redundancy level of data service is level 1. (default value) The 2198 redundancy level of data service is level 1.

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. Table 15-5 lists the value options of this parameter.

15-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

15 IP Fax Feature

Table 15-5 Value options of 2198 redundancy CODEC type Value G.711u G.711a Meaning The codec used for 2198 redundancy of data services is G.711u. The codec used for 2198 redundancy of data services is G.711u. (default value)

Use the parameter 2198 redundancy payload type value in the Local Office Information table to configure 2198 data redundancy. The value range of this parameter is 96127. The default value is 97. Use the parameter BICC support red in the Office Direction table to configure whether to the office direction supports the redundancy parameters. Table 15-6 lists the value options of this parameter. Table 15-6 Value options of BICC support red Value Yes No Meaning The office direction supports the redundancy. (default value) The office direction does not support the redundancy.

Parameters 2198 UP Mode, 2198 redundancy level, 2198 redundancy CODEC type, and 2198 redundancy payload type value are attributes of 2198 redundancy. Thus, when Support 2198 redundancy is set to No, these parameters are not displayed in the parameter list.

P233 (H248 software parameter 2) It controls whether to forcibly change the UP mode to the transparent mode when the redundancy is sent. Bit 14:

= 0: The UP mode is not forcibly changed to the transparent mode when the redundancy is sent. = 1: The UP mode is forcibly changed to the transparent mode when the redundancy is sent.

15.6.2 Data Configuration Example


Scenario Description
The following lists a scenario description. Configure the local office information so that the local office supports the fax detection and 2198 data redundancy. Configure the office direction table so that redundancy is supported. Set bit14 of software parameter 233.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

15-9

15 IP Fax Feature

HUAWEI MSOFTX3000 Feature Description

Configuration Script
SET OFI: OFN="VMSC", LOT=LOCMSC, IN=NO, IN2=NO, NN=YES, NN2=YES, SN1=NAT, SN2=NATB, SN3=NAT, SN4=NATB, NPC="2A1101", INS=SP14, IN2S=SP24, NNS=SP24, NN2S=SP14, SPF=YES, SPFAXDT=YES, SPRED=YES, REDLEVEL=L1, REDPT=97, REDCODEC=G711a, UPMODE=TRANS; ADD OFC: ON="VMSC", OOFFICT=NATT, DOL=SAME, SIG=SCTP, IFSUPPORTRED=YES; MOD MSFP: ID=P233, MODTYPE=P1, BIT=14, BITVAL=1;

15.7 Service Management


No special management of the service is required.

15.8 Charging and CDR


None.

15.9 Service Interaction


None.

15-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
16 License Feature .......................................................................................................................16-1
16.1 Service Description ...................................................................................................................................16-2 16.1.1 Function Code..................................................................................................................................16-2 16.1.2 Application Scope ............................................................................................................................16-2 16.2 Working Principle......................................................................................................................................16-2 16.2.1 Working Principle of License...........................................................................................................16-2 16.2.2 Running Status of License ...............................................................................................................16-2 16.2.3 Invalidation of License.....................................................................................................................16-3 16.2.4 Alerting Mechanism of License .......................................................................................................16-3 16.3 Operation and Maintenance of License.....................................................................................................16-4 16.3.1 LOD LICENSE (Loading a License)...............................................................................................16-4 16.3.2 ROL LICENSE (Rolling Back a License) .......................................................................................16-5 16.3.3 LST LICENSE (Listing a License) ..................................................................................................16-6 16.3.4 DSP ESN (Displaying the System ESN)..........................................................................................16-7 16.3.5 STR LICCRC (Starting CRC Check of License).............................................................................16-9 16.3.6 DSP LICENSE (Display Running License File Status) ...................................................................16-9 16.3.7 DMP LICENSE (Dumping License File) ......................................................................................16-10 16.3.8 ULD LICENSE (Uploading License File to FTP Server).............................................................. 16-11 16.3.9 DLD LICENSE (Downloading License File from FTP Server) ....................................................16-12 16.4 License Control Items .............................................................................................................................16-12 16.4.1 Control Items .................................................................................................................................16-12 16.4.2 Resource Control Items..................................................................................................................16-15 16.5 Other Precautions ....................................................................................................................................16-17 16.5.1 License Checks ..............................................................................................................................16-17 16.5.2 License Invalidation and Prevention ..............................................................................................16-17 16.5.3 License Alarms...............................................................................................................................16-19 16.5.4 License Upgrading .........................................................................................................................16-20 16.5.5 Effects of BAM Operations on License .........................................................................................16-20 16.6 Reference ................................................................................................................................................16-21 16.6.1 Protocols and Specifications ..........................................................................................................16-21 16.6.2 Acornyms and Abbreviations .........................................................................................................16-21

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Tables

HUAWEI MSOFTX3000 Feature Description

Tables
Table 16-1 Parameters of the command LOD LICENSE .................................................................................16-4 Table 16-2 Parameters of the command LST LICENSE ..................................................................................16-6 Table 16-3 Parameters of the command DSP ESN...........................................................................................16-8 Table 16-4 Parameters of the command DSP LICENSE ..................................................................................16-9 Table 16-5 Parameters of the command DMP LICENSE...............................................................................16-10 Table 16-6 Parameters of the command ULD LICENSE ............................................................................... 16-11 Table 16-7 Alarms from host ..........................................................................................................................16-19 Table 16-8 Alarms from BAM........................................................................................................................16-19

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

16
About This Chapter
The following table lists the contents of this chapter. Section 16.1 Service Description 16.2 Working Principle 16.3 Operation and Maintenance of License 16.4 License Control Items 16.5 Other Precautions 16.6 Reference Describes

License Feature

The function code and application scope of the License feature. The working principles, running status, invalidation definition and alarm mechanism of the License feature. The O&M commands and cautions of the License feature. The control items and resource control items of the License feature. Other cautions in using the License feature. The acronyms in this chapter.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-1

16 License Feature

HUAWEI MSOFTX3000 Feature Description

16.1 Service Description


16.1.1 Function Code
This feature does not have a function code.

16.1.2 Application Scope


For providers, the License is a contract form of authorizing the usage scope and period of the sold products. For customers, the License is a contract form of being authorized with the usage scope and period of the purchased products. Through the License, customers also obtain the services promised by providers. Physically, the License is presented as License authorization certificates and License files. The License features of the MSOFTX3000 achieve customization of the service functions and quantity of the products. This document aims to help technical staff to use the License features correctly.

16.2 Working Principle


16.2.1 Working Principle of License
The License functions of the MSOFTX3000 are realized on the basis of Huawei License unified platform. The application of the License should conform to the related regulations of Huawei. 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.2.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, the status of the License is Normal. Trial: If the ESN in the License files loaded into the system is inconsistent with the ESN of the system, the status of the License is Trial.

16-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

Invalidating: If the License files loaded into the system is expired, or no valid License file is loaded into the system, the system triggers a 60-day invalidation alerting period. In this case, each control item of the License files can still be used for 60 days without any service restriction, but alarms indicating that the License is expired are sent every day. After the 60 days, the system enables the default minimum value. Default: After License files are expired for 60 days or the default minimum values are used for 60 days, the system runs under default License and provides only the default permitted License functions.

16.2.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. 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 feature is handled as "Invalidation of the whole License". It has four running status: Normal, Trial, 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 feature is handled as "Partial invalidation of the License". Each item of the License file also has four running status: Normal, Trial, Invalidating and Default.

16.2.4 Alerting Mechanism of License


For "Invalidation of the whole License", there are three types of alarms: When the whole License will be invalid in less than 90 days, the system sends a fault alarm every day indicating that the License will be expired. In the next day, the system recovers the fault alarm of the first day, and sends another alarm indicating that the License will be expired. The "Rest days" in the alarm represents how many days are left before the due date. After the whole License file is expired, there comes a 60-day invalidation alerting period. During this period, the original configuration values of the License are remained, but a fault alarm indicating that the License is expired is sent every day. In the next day, the system recovers the fault alarm of the first day, and sends another alarm indicating that the License is expired. After the 60-day invalidation alerting period, the default minimum value is enabled, and a fault alarm indicating that the License is expired is sent every day. In the next day, the system recovers the fault alarm of the first day, and sends another alarm indicating that the License is expired. For "Partial invalidation of the License", there are three types of alarms: When an item of a License file will be invalid in less than 30 days, a fault alarm indicating that the License item will be expired soon is sent every day. In the next day, the system recovers the fault alarm of the first day, and sends another alarm indicating that the License item will be expired. The "Rest days" in the alarm represents how many days are left before the due date. After a License item is expired, there comes a 60-day invalidation alerting period. During the period, the original configuration values of the License are remained, but a fault alarm indicating that the License is expired is sent every day. In the next day, the system recovers the fault alarm of the first day, and sends another alarm indicating that the License item is expired.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-3

16 License Feature

HUAWEI MSOFTX3000 Feature Description

After the 60-day invalidation alerting period, the system enables the minimum default value of the License item. After the whole License is expired, alarms indicating that the License items are expired are not sent, because the License items are expired if the whole License file is expired.

There are 10 alarm cause values for the event alarm "invalid license", but they are not displayed. When such event alarms occur, check the following: Whether the loaded License is normal. If not, you must load valid License files again. Whether the License of the host and the License of the BAM are consistent. If not, you must load valid License files again.

16.3 Operation and Maintenance of License

After getting License files, you must back up them to avoid unexpected incidents. License files are digitally subscribed; therefore, do not edit them. Or, the License becomes invalid. After the loading, run DSP LICENSE and TR LICCRC immediately to check whether the Licenses of the host and the BAM are consistent. If not, contact Huawei technical staff for consultation.

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

Parameter Description
Table 16-1 shows the parameters of the command LOD LICENSE. 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. Notes: The License must be in the License subdirectory under the installation directory, in the format of Lic*.dat. The input parameter cannot contain any other directory name.

16-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. The options are: BAM, and BAM and host. Notes: In general, you are recommended to use the default value of the parameter. This parameter must be set to BAM in certain special cases. That is, for any version between R002C01B022 and R002C01B031 (except B031), if it is required to be updated to any version later than R002C01B031, you must select BAM for loading. It is not required for any version later than R002C01B031.

Notes
Pay attention to the following when using this command. If the specified License does not exist, the License is verified to be incorrect, License decryption fails, or the License is expired, a message indicating failure in running the command is returned, together with related prompts. This does not affect the License in use. If the new License has fewer functions or a lower capacity than the original one, the command can be executed successfully, and each module uses the new License data. But an alarm indicating that the new License has less functions or lower capacity is generated. If the ESN of the specified License is inconsistent with that of the equipment, a prompt for successful loading is prompted, but an alarm indicating inconsistent ESNs is generated. In this case, the system is in trial running (the trial period is specified when applying License files). During this period, the functions of the License can be normally used. After the trail period, the system prompts that the trial period is expired, and the running mode turns to be Invalidating. The configuration values of the License remain, and subscribers are allowed to use the License for 60 days. After the 60 days, the running mode turns to be Default. The products run under the default License and provide only the default permitted License functions. If the system has ever loaded a License with an inconsistent ESN (that is, the system has trialed the License), any License with an inconsistent ESN cannot be loaded again. Therefore, when you find the License is in Trial status, you must apply for a formal License immediately. Or, the License only provides default functions when the Invalidating period is over.

16.3.2 ROL LICENSE (Rolling Back a License)


The host database can store only the License files of the latest 2 loadings. To switch over easily, you can run ROL LICENSE to roll back from the current License file to the License file of the last time. Then the last License is in use. Using this command, you can switch over

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-5

16 License Feature

HUAWEI MSOFTX3000 Feature Description

easily between the last two License files, and then the system obtains the rights to change different functions and customer capacities.

Parameter Description
The command ROL LICENSE has no parameter.

Notes
When the system performs the rollback operation, it rolls back to the last normal License configuration. Normal configuration here means the License files that have been successfully loaded in the system. This command is in fact to take the name of the License that has been successfully loaded last time, and then auto run LOD LICENSE to load the License. In general, you are recommended to run LOD LICENSE directly to reload the License.

16.3.3 LST LICENSE (Listing a License)


During maintenance, you can run LST LICENSE to check License files, including the loaded License files, and the unloaded License files under D:\MSOFTX3000\License.

Parameter Description
Table 16-2 shows the parameters of the command LST 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, namely the source type of the License. The parameter options are: Disk: to query the information of the License stored on the BAM disk. The parameter License name is displayed, and you can input the License you want to check. DB (database): to query the information of the License stored in the BAM database. The parameter File type is displayed, and you can select Current license or History license to check.

16-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. It specifies the name of the License to be displayed. Notes: When this parameter is in the default value, all the License files in Lic*.dat format in the License subdirectory under the installation directory are displayed. When the file name is typed in, the content of the License is displayed.

FT

Enumerati on

File type

The parameter is valid only when Source type is set to DB. It specifies the name of the License to be displayed. The parameter options are: Current license: to display the current License file in the database. This option is the default value. History license: to display the history License files in the database.

Notes
Pay attention to the following when using this command: When File name is null, the License files of which the names initiate with the characters "LIC" in the License subdirectory under the installation directory are displayed. Usually the License files from the License center of Huawei are initiated with "OR" or other letters. So, you are recommended to change the License name to "LICENSESerialNo" field content before loading the License. Only a complete file name with extension name can be typed in File name. License files must be located in the License subdirectory under the installation directory, without the directory name. These rules are also applicable to other License operation commands.

16.3.4 DSP ESN (Displaying the System ESN)


During deployment or maintenance, the entity serial number (ESN) information is needed when applying License files. You can run DSP ESN to query the ESN information.

Parameter Description
Table 16-3 shows the parameters of the command DSP ESN.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-7

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. The parameter options are: When LT is set to Current config in BAM, the ESN in the BAM server is displayed. When LT is set to Current config in Device, the ESN in the host is displayed. When LT is set to Input raw ESN, the system ESN information generated according to certain algorithm is displayed.

Notes
ESN means entity serial number. 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, therefore, must ensure the correctness of the ESN. The serial number of the equipment to be authorized is contained in License file. After the License is loaded to the equipment, the system compares the ESN in the License file with that of the equipment. The system authorizes corresponding services to the equipment only when the two ESNs are consistent. The following are the steps to obtain the ESN: Step 1 Install the BAM. Step 2 Configure the MSC number and the DPC number offline. The MSC and DPC number must be identical with the actual data of the current network; otherwise, errors occur in obtaining the ESN. Step 3 Run DSP ESN to obtain the ESN. Set Display type to Current config in BAM. ----End

When there are multiple signaling points, the ESN is irrelevant to the sequence of the signaling points. You can change the sequence of the configuration, but any other change leads to different ESNs. You cannot add or delete signaling points. When the system is running, you cannot modify the MSC number or signaling point number, otherwise the License may become invalid. If you do have to modify them, you must obtain a new ESN number based on the data after the modification, and then apply a new License.

16-8

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

16.3.5 STR LICCRC (Starting CRC Check of License)


During maintenance, you can run STR LICCRC to compare the consistency of the License data of the host and the BAM.

Parameter Description
The command STR LICCRC has no parameter.

Notes
Pay attention to the following when using this command: When the BAM originates STR LICCRC, the system checks whether the loaded Licenses of the BAM and the foreground host are consistent. The system compares the file names and CRC values only. The foreground host originates an automatic check every two hours. The BAM sends the information of the License loaded in the BAM to the host, irrespective of the check results. In this case, the host performs the following:

Check whether the information of the licenses loaded in the host and in the BAM are consistent. If the sizes and names of the licenses are identical, the licenses are considered consistent. If yes, the host enables the 2-hour basis check timer. If not, the host keeps the license of itself, enables the 10-minute basis check timer, and sends an event alarm indicating that both the licenses of the BAM and the host are valid but inconsistent.

16.3.6 DSP LICENSE (Display Running License File Status)


During maintenance, you can run DSP LICENSE to display the License status of the BAM and the host.

Parameter Description
Table 16-4 shows the parameters of the command DSP LICENSE. 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. The parameter options are: BAM: The License in the BAM server is displayed. Host: The License in the host is displayed. If no parameter is selected, both the licenses in the host and the BAM are displayed.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-9

16 License Feature

HUAWEI MSOFTX3000 Feature Description

Notes
DSP LICENSE is different from the command LST LICENSE. 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.

16.3.7 DMP LICENSE (Dumping License File)


During maintenance, you can run DMP LICENSE to dump License files. The backup files are stored under D:\MSOFTX3000\License and named "License + current time". 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. 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, namely the source type of the License. The parameter options are: DEV: The License files stored in the host are displaced. DB: The License files stored in the database are displaced. FT String File type The parameter is valid only when Source type is set to Database. It is used to specify the License files in the database to be dumped. 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. FN String File name The parameter is valid only when Source type is set to Database. It is used to specify the names of the current License files in the database to be dumped. The file names must begin with "Lic", such as Lic_current.dat.

16-10

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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 file must be named "LICENSEYYYYMMDDHHMMSS.txt" in which the letters in upper case in the latter part indicate the year, month, date, hour, minute and second of the current system time. This file is stored in the License subdirectory under the BAM installation directory. You are recommended to save the license manually instead of using the DMP method. When exporting the "Current license files" or "History license files" from the database to a file, you can name the file freely.

16.3.8 ULD LICENSE (Uploading License File to FTP Server)


Parameter Description
Table 16-6 shows the parameters of the command ULD LICENSE. 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. Optional. The default value is the IP address of the default file server. Subscriber name used to log in to the FTP server. Optional. The default value is the subscriber name for logging in to the default file server. Subscriber password used to log in to the FTP server. Optional. The default value is the subscriber password for logging in to the default file server. Directory name. The path on the FTP server where the files to be loaded (License files) are stored. Mandatory. Full name of the file to be loaded. Mandatory. Generated serial numbers of License files. Optional. By default, the content of the current License file is uploaded.

USR

Subscriber name

PWD

String

Password

DIR

String

Directory

FN FSN

String String

File name File serial number

Notes
This command uploads License file, obtains License files from the system and store them to a specified FTP server (similar to the command DLD LICENSE, network elements (NEs) also act as the FTP CLIENT).This command has a reverse function comparing to the command DLD LICENSE.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-11

16 License Feature

HUAWEI MSOFTX3000 Feature Description

16.3.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. The NEs act as the FTP clients.

Parameter Description
For more details of the parameters of the command DLD LICENSE, refer to 16.3.8 "ULD LICENSE (Uploading License File to FTP Server).

Notes
DLD LICENSE only downloads License files to NEs. The NEs still use the original License configuration data, even if the system is restarted. The new License is not effective, and no decryption and ESN comparison are conducted (These operations are performed while running the command LOD LICENSE).If the ESNs of the NEs are changed, the License files must be updated at the same time.

16.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. Default Value Disabled Scenario VMSC, GMSC, TMSC VMSC

When the HO module processes switching requests originated by the local office or incoming switching requests, query the destination route from the database to determine the type of the switching side (2G or 3G), and then decide whether the switching can be supported based on the License. Decide whether to enable the SMS based on the License when the MSC interacts with the SMC. When the CM and the BICC receive the Codec negotiation result from each other, decide whether to enable the TFO/TrFO function based on the License. If not, the TrFO does not deliver the Modify process to the gateway.

Disabled

SMS

Disabled

VMSC

TFO/TrFO

Disabled

VMSC, GMSC, TMSC

16-12

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

Control Items LCS

Description In the MT_LR, MO_LR and NI_LR processes, decide whether to reject the LCS requests based on the License. Decide whether to enable dual homing and handover functions based on the judgment of the License. Decide whether to perform signaling bearer conversion, forwarding and related configuration based on the judgment of the License. Decide whether to perform signaling forwarding and related configuration 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. Decide whether to enable the PS multimedia service based on the judgment of the License. Decide whether to enable the related configurations and services of VNOs based on the judgment of the License. Decide whether to enable related configurations and services of valid monitoring 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. Intra-office Iu-Flex means that one RNC can be connected to multiple MGWs under the control of one MSC Server. 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 eMLPP 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.

Default Value Disabled

Scenario VMSC

Dual homing

Disabled

VMSC, GMSC, TMSC VMSC, GMSC, TMSC VMSC, GMSC, TMSC VMSC, GMSC, TMSC VMSC VMSC

SG

Disabled

STP

Disabled

Mc interface encryption CS multimedia service Virtual network operator (VNO) Lawful interception

Disabled

Disabled Disabled

Disabled

VMSC, GMSC

Intra-office Iu-Flex

Disabled

VMSC

PRA access

Disabled

VMSC, GMSC VMSC, GMSC VMSC

eMLPP

Disabled

MNP

Disabled

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-13

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 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. The EIR function is built in the MSC. Decide whether to enable the EIR based on the License. Decide to enable the ARD 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 to enable the MAP Policing function based on the judgment of the License. Decide to enable the MGCF function 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 whether to enable the SNA connection mode sharing function based on the judgment of the License. Decide whether to enable the inter-office Iu-Flex function based on the judgment of the License. Decide whether to enable the Min-A-Flex function based on the judgment of the License.

Default Value Disabled

Scenario VMSC

Notification by SM

Disabled

VMSC, 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)

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. Decide whether to enable the SOR function based on the judgment of the License. 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. Decide whether to enable the NTP function based on the judgment of the License. Decide whether to enable subscriber tracing and signaling tracing functions based on the judgment of the License. Decide whether to enable the centralized signaling monitoring function based on the judgment of the License.

Default Value Disabled

Scenario VMSC

Disabled Disabled

VMSC VMSC

Disabled Disabled

VMSC VMSC, GMSC, TMSC VMSC, GMSC, TMSC VMSC, GMSC

Subscriber protocol tracing Centralized signaling monitoring

Disabled

Disabled

16.4.2 Resource Control Items


Resource Control Items Total number of subscribers Description Controlled in the DB. The number of the attached subscribers is limited in the VDB to be less than total number of subscribers. The number of intelligent connections realized by the IN (total IN subscriber number x ERL each IN subscriber). It controls the processing capability. The number of connected 2G subscriber calls (total number of 2G end office subscribers x ERL each subscriber). It controls the processing capability. The number of connected 3G subscriber calls (total number of 3G end office subscribers x ERL each subscriber). It controls the processing capabilities. Default Value 4000 Scenario VMSC

Total number of IN calls

100

VMSC, 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

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), including the ISUP trunk number and BICC trunk number. The number of the subscribers on call hold (total number of subscribers on call hold x ERL each subscriber). The number of the subscribers on call waiting (total number of subscribers on call waiting x ERL each subscriber). The number of the subscribers in a multiparty call (total number of subscribers in a multiparty call x ERL each subscriber). The number of data service subscribers (total number of data service subscribers x ERL each subscriber). 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. It limits the number of the 2M signaling links can be configured. It limits the number of multiple signaling points that can be configured. 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, 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

VMSC, GMSC VMSC, GMSC, TMSC VMSC, GMSC, TMSC Cluster service is ready for the VMSC. Cluster service is ready for the VMSC.

16-16

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

16.5 Other Precautions


16.5.1 License Checks
Timing Check
At 01:20 a.m. every day, 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, judge whether the allowed trial period is expired. If not, reduce one day from the rest days and send an alarm indicating that the License will be expired. If yes and the license file is in the 60-day invalidation alerting period, the system remains the original License configuration information and sends an alarm indicating that the License is expired. After 60 days, the License runs with the default configurations and provides the default allowed functions only. Step 2 If the License is in normal state, judge whether the rest days of the License are less than 90 days. If yes, an alarm indicating that the License will be expired is sent, and one day is reduced from the rest days in the check every day. If the usage period is exceeded and the license file is in the 60-day invalidation alerting period, the system remains the original License configuration information and sends an alarm indicating that the License is expired. After 60 days, the License runs with default configurations and provides the default allowed functions only. Step 3 If the License is handled by items, judge whether the rest days of an item are less than 30 days. If yes, an alarm indicating that the License will be expired is sent, and one day is reduced from the rest days in the check every day. If the usage period is exceeded and the license file is in the 60-day invalidation alerting period, the system remains the original License configuration information and sends an alarm indicating that the License is expired. ----End

Check from the Host


The foreground host originates an automatic check every two hours. At this time, the BAM sends the information of the License loaded in the BAM to the host, irrespective of the check results. In this case, the host performs the following: 1. Check whether the license files loaded in the host and in the BAM are consistent. If the sizes and names of the license files are identical, the license files are considered consistent. If they are consistent, the host enables the 2-hour periodic check timer and check every two hours from then on. If they are inconsistent, the host enables the 10-minute periodic check timer and sends an alarm indicating that the License is expired. The cause value of the alarm is that both the licenses of the BAM and the host are valid but inconsistent.

2. 3.

16.5.2 License Invalidation and Prevention


License invalidation contains normal invalidation and abnormal invalidation. Normal invalidation: The trial period of trial License is expired, or the running period of formal License which is specified in License files is expired.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

16-17

16 License Feature

HUAWEI MSOFTX3000 Feature Description

Abnormal invalidation: The License files are loaded normally in the system, but the License becomes invalid because of certain maloperations or specific conditions. Once the License becomes invalid, if you have legal License files, you can run LOD LICENSE to reload the License files. The following are certain symptoms of abnormal invalidation, and the methods to prevent them and solve them.

Invalid License on BAM


The symptoms are: When you run DSP LICENSE to check the License on the BAM, the file name is null, and the License control items are in their default minimum values. The tracing function on the operation console of the BAM is out of use. Alarms with ID 2381 and 2382 are generated, indicating that the current License files of the system are in their default values with which the system capacities are straightly limited. The solution to this case: Run LOD LICENSE to load valid License files.

Invalid License on host


The symptoms are: When you run DSP LICENSE to check the License on the host, the file name is null, and the License control items are in their default maximum values. Fault alarm "License is expired" (ID: 2183) and event alarm "License is invalid" (ID: 2246) appear in the alarm window. The solution to this case: Run LOD LICENSE to load valid License files.

License files Are Expired and not Reloaded


License files are expired and not reloaded. The symptoms are: Within the 60 days after the License is expired, you can run DSP LICENSE to check whether the running mode of the License is Invalidating. The file names and control items of the License are remained. Fault alarm "License is expired" (ID: 2183) appears in the alarm window. Within the 60 days after the License is expired, you can run DSP LICENSE to check whether the running mode of the License is Default. 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 solution to this case: Run LOD LICENSE to load valid License files.

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. When loading the License offline, you must set the parameter Position to BAM. At this time, the Licenses of the BAM and the host may be inconsistent. To ensure that the License files on

16-18

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

the BAM are normal, after the emergency workstation and the host are connected, run LOD LICENSE immediately to load the License to the host online. In this case, you cannot choose the parameter Position.

16.5.3 License Alarms


and Table 16-8 list the alarms related with the License. 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, you should especially pay attention to the alarms 2181, 2183, 2187, 2189, and 2246.

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

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.5.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. This does not affect the BAM and the services. In this case, you should load the License with the command LOD LICENSE. No other special operation is required.

Version Upgrading
If there are special requirements upon version upgrading, the details are given in the upgrade guide released with the version.

16.5.5 Effects of BAM Operations on License


When the BAM is abnormal, it does not affect the License of the host, because the host can run without the BAM. When restarting the Maintain process on the BAM, the License files that were successfully loaded last time are reloaded on the BAM. In this case, the related information of the License is recorded in the BAM database. If the record does not exist in the database, you can only load the default License instead of the BAM License in the memory. When upgrading the BAM, if all versions of R002 are upgraded to R003, you must run LOD LICENSE to reload the License files after the upgrade. Otherwise, the License files on the BAM are set to the minimum value if they cannot be used. This severely affects the system function. If the SMU boards are not restarted on the host, the original License remains. At this time, if the License on the host is different from that on the BAM, alarms indicating "License is expired" are generated every 10 minutes. If the SMU boards are restarted on the host, License is analyzed in the FLASH. If the Licenses on the host and the BAM are different, alarms "License is invalid" are generated every 10 minutes. When the BAM is reinstalled, the original information about the License is lost. The original License files cannot be auto loaded in the system when the BAM is restarted. You must load the License files manually.

16-20

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

16 License Feature

16.6 Reference
16.6.1 Protocols and Specifications
None.

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

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)

HUAWEI MSOFTX3000 Feature Description

Contents

Contents
17 NE User Dynamic Monitoring Feature ..............................................................................17-1
17.1 Function Description .................................................................................................................................17-2 17.1.1 Function Code..................................................................................................................................17-2 17.1.2 Definition .........................................................................................................................................17-2 17.1.3 Standard Compliance .......................................................................................................................17-3 17.1.4 System Specifications ......................................................................................................................17-3 17.1.5 Benefits ............................................................................................................................................17-4 17.1.6 Application Scenario ........................................................................................................................17-4 17.1.7 Application Limitations....................................................................................................................17-4 17.2 Availability ................................................................................................................................................17-4 17.2.1 Requirements for NEs......................................................................................................................17-4 17.2.2 Requirements for License ................................................................................................................17-5 17.2.3 Applicable Versions..........................................................................................................................17-5 17.2.4 Others...............................................................................................................................................17-5 17.3 Working Principle......................................................................................................................................17-5 17.3.1 Functions of NEs..............................................................................................................................17-5 17.3.2 Internal Processing of the System ....................................................................................................17-6 17.3.3 External Interfaces ...........................................................................................................................17-6 17.4 Service Flow..............................................................................................................................................17-6 17.4.1 Monitoring Flow of Online User......................................................................................................17-6 17.4.2 Reporting Flow of User Operation...................................................................................................17-6 17.4.3 Disconnection Flow of User Operation............................................................................................17-7 17.5 Function Maintenance ...............................................................................................................................17-7 17.5.1 Overview..........................................................................................................................................17-7 17.5.2 Maintenance Operations ..................................................................................................................17-7 17.6 Service Management ............................................................................................................................... 17-11 17.7 Charging and CDR .................................................................................................................................. 17-11 17.8 Performance Measurement...................................................................................................................... 17-11 17.9 Service Interaction .................................................................................................................................. 17-11 17.10 References .............................................................................................................................................17-12 17.10.1 Standards and Specifications........................................................................................................17-12 17.10.2 Glossary, Acronyms, and Abbreviations ......................................................................................17-12

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

Contents

HUAWEI MSOFTX3000 Feature Description

17.11 FAQ .......................................................................................................................................................17-12

ii

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

Figures

Figures
Figure 17-1 Local Maintenance Monitor tabbed page......................................................................................17-2 Figure 17-2 User Monitor interface..................................................................................................................17-8 Figure 17-3 Subscribed NE List interface ........................................................................................................17-8 Figure 17-4 User Monitor interface................................................................................................................17-10 Figure 17-5 User Session interface 1..............................................................................................................17-10 Figure 17-6 User Session interface 2..............................................................................................................17-10 Figure 17-7 Filtering interface........................................................................................................................ 17-11

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

iii

Tables

HUAWEI MSOFTX3000 Feature Description

Tables
Table 17-1 Function code of the NE user dynamic monitoring function..........................................................17-2 Table 17-2 Explanations of the Local Maintenance Monitor tabbed page........................................................17-3 Table 17-3 Specifications of the system ...........................................................................................................17-4 Table 17-4 Description of benefits....................................................................................................................17-4 Table 17-5 NEs that are involved in this function ............................................................................................17-5 Table 17-6 Version that supports this function..................................................................................................17-5

iv

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. Section 17.1 Function Description 17.2 Availability Describes The function code and definition of the service and the benefits of the service to carriers and mobile subscribers. The NEs required to implement the service, requirements for the license, and versions of the products applicable to the service. The functions of the NEs used to implement the service and the requirements on the networking. The flow of 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. The operations that carrier and mobile subscribers must perform when the service is provided. The procedure for performing charging and generating CDRs when the service is provided. The influence of the service on performance measurement and the implementation of performance measurement. The association between the service and other services as well as the restrictions on each other. The standards and specifications with which the service complies and the glossary, abbreviations, and acronyms used in this chapter. The frequently asked questions related to the service and the solutions.

17.3 Working Principle 17.4 Service Flow 17.5 Function Maintenance

17.6 Service Management 17.7 Charging and CDR 17.8 Performance Measurement 17.9 Service Interaction 17.10 References

17.11 FAQ

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

17-1

17 NE User Dynamic Monitoring Feature

HUAWEI MSOFTX3000 Feature Description

17.1 Function Description


17.1.1 Function Code
Table 17-1 specifies the function code of the NE user dynamic monitoring function. Table 17-1 Function code of the NE user dynamic monitoring function Name NE user dynamic monitoring function Code -

17.1.2 Definition
Through the network element (NE) user dynamic monitoring function, the network management system (NMS) monitors the operation information and status of online NE users in real time. The monitoring information is displayed on the Local Maintenance Monitor tabbed page on the M2000 client. Figure 17-1 shows the Local Maintenance Monitor tabbed page. For the explanations of the Local Maintenance Monitor tabbed page, see Table 17-2. Figure 17-1 Local Maintenance Monitor tabbed page

17-2

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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. By default, all names of the NEs that log in to the M2000 are specified. Specifies the name of the login user. By default, all names of the NEs that log in to the M2000 are specified. Specifies whether the user is a local user (LOCAL) or an NMS user (EMS). Specifies the IP address of the client that is connected to the NE. Specifies the login time of an NE user. Specifies the type of the service console through which the NE user logs in to the M2000, including O&M system and performance maintenance system. Specifies the login mode of an NE user, including by proxy (Yes) and not by proxy (No). Specifies the current status of an NE user, including online and unknown. A function button, used to display information in this page by selection. A function button, used to obtain the latest information. A function button, used to save all information displayed in the page. A function button, used to choose the operation results reported by the NE user. A function button, used to force a user to exit.

By proxy Status Filter Refresh Save Subscribe Force User to Exit

In this chapter, the NMS refers to the M2000.

17.1.3 Standard Compliance


None.

17.1.4 System Specifications


Table 17-3 lists the specifications of the system.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

17-3

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. Local user: It refers to users that are individually managed by each NE, including the default local user. The user of this type can log in to the NE for operation during system initial installation or disconnection from the NMS. Domain user: It refers to a user uniformly managed by the NMS. The user of this type is created, modified, authenticated or authorized by the NMS. After authorization, the user of this type can log in to the NE for operation, through the local maintenance terminal (LMT), and can also log in to the M2000 server for operation, through the M2000 client.

17.1.5 Benefits
Table 17-4 describes the benefits for the beneficiary. 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. The NMS can monitor the operation of the users of all NEs in real time, and obtain data configuration updates. The network can implement the centralized management of NE users. By clicking Force User to Exit to disconnect a user from an NE, the NMS can prevent the user from performing subsequent operations. Mobile subscriber -

17.1.6 Application Scenario


This function applies to GSM and UMTS R99/R4.

17.1.7 Application Limitations


All the operations involved in this function must be performed on the M2000.

17.2 Availability
17.2.1 Requirements for NEs
To implement this function, the M2000 must work with the MSC server. See Table 17-5.

17-4

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

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.

17.2.2 Requirements for License


No License is required for the availability of this function.

17.2.3 Applicable Versions


Table 17-6 shows the version of the HUAWEI core network (CN) that supports his function. Table 17-6 Version that supports this function Product MSC server MSOFTX3000 Applicable Version V100R005C10

17.2.4 Others
None.

17.3 Working Principle


17.3.1 Functions of NEs
The NE user dynamic monitoring function is implemented as follows: 1. 2. 3. The M2000 sends the corresponding commands to NEs. The NEs returns the command execution results to the M2000. The M2000, then, displays the result in the Local Maintenance Monitor pane.

Currently, the NE status displayed is reported by the NEs to the M2000 actively. The NMS need not monitor the operations of all NE online users because there are some operations that the NMS does not require. To monitor only the operations that are cared for by the NMS, a subscription and unsubscription mechanism is used between the NEs and NMS. To subscribe to users means to monitor the operations of the users; to unsubscribe to users means to cancel the monitoring of the operations of the users. Through the subscription and unsubscription mechanism, messages between the NEs and NMS are reduced, and the load of the NEs and NMS is lowered. The NE supports the forced disconnection from a user, through the disconnection command sent by the NMS. That is, the user is forced to exit the LMT and disconnect from the NE. After a user is disconnected from the NMS, the NE sends the disconnection message to the

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

17-5

17 NE User Dynamic Monitoring Feature

HUAWEI MSOFTX3000 Feature Description

LMT that the user belongs to, through the operation and maintenance port. At this time, a message is displayed on the LMT, indicating that the user is forcedly disconnected from the NMS.

17.3.2 Internal Processing of the System


Function Implementation
The login and logout of an NE user need to be reported to the NMS. When the NMS first connects to an NE, the NMS obtains the status of the online users of the NE automatically. But the NE must take the initiative to update its data to the NMS later.

Implementation of Monitoring of NE Online User Operation


When the NMS issues a command for monitoring an NE user, the NE reports the operations of the user to the NMS immediately. When the NMS issues a command to cancel the monitoring of an NE user, the NE stops reporting the operations of the user to the NMS. To monitor the operations of all the users of an NE, the NMS sends a command for monitoring all the users of an NE. To cancel the monitoring of the operations of all the users of an NE, the NMS sends a command for canceling the monitoring of all the users of an NE.

Implementation of Forced Disconnection of Online User Operation


When an NE receives a command, indicating disconnection from a user, the NE disconnects from all the LMTs that the user logged in to. When an LMT is disconnected from the NE, a message is displayed, indicating that the user is forcedly disconnected from the NMS. After a user is disconnected from the NMS, the NE sends the disconnection message to the LMT that the user belongs to, through the operation and maintenance port. At this time, a message is displayed on the LMT, indicating that the user is forcedly disconnected from the NMS.

17.3.3 External Interfaces


None.

17.4 Service Flow


17.4.1 Monitoring Flow of Online User
The login and logout of an NE user must be reported to the NMS through synchronization. The NMS can automatically obtain the online user status of NEs for the first time connection. For the following data update, the NEs report the status to the NMS actively. The user of an NE that is monitored can be a local or domain user.

17.4.2 Reporting Flow of User Operation


The NMS issues commands for subscribing to monitoring to an NE. After receiving the commands, the NE reports the operations of the user to the NMS through the synchronization report interface. The NMS issues commands for unsubscribing to monitoring to an NE. After receiving the commands, the NE stops reporting the operations of the user to the NMS.

17-6

Huawei Technologies Proprietary

Issue 02 (2007-06-10)

HUAWEI MSOFTX3000 Feature Description

17 NE User Dynamic Monitoring Feature

17.4.3 Disconnection Flow of User Operation


When the NMS issues commands for forcing user to exit, the NE reports the disconnection message to the LMT to which the user belongs to. When the NE disconnects from the LMT, the LMT cancels the user login, indicating that the user is disconnected from the NMS.

17.5 Function Maintenance


17.5.1 Overview
The NE user dynamic monitoring function is performed through GUI mode on the M2000 client. The function includes: Subscription Canceling the subscription Querying user subscription information Forcing user to exit Filtering

17.5.2 Maintenance Operations


Subscription
To subscribe to the monitoring, perform the following steps: Step 1 Choose System > User Monitor on the M20000 client. The User Monitor interface is displayed, as shown in Figure 17-2.

Issue 02 (2007-06-10)

Huawei Technologies Proprietary

17-7

17 NE User Dynamic Monitoring Feature

HUAWEI MSOFTX3000 Featu