139218749 HUAWEI OCS Business Process Description

HUAWEI OCS V100R002C02

Business Process Description

Issue

01

Date

2010-07-28

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2010-2010. 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 mentioned in this document are the property of of their respective respective holders. holders.

Notice The purchased products, services and features are stipulated by the contract made between Huawei and the customer. All or part of the products, services and features described in this document document may not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, information, and recommendations in this document are provided "AS IS" without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations recommendations in this document do not constitute the warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

Issue 01 (2010-07-28)

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

i

HUAWEI OCS Business Process Description

About This Document

About This Document Intended Audience This document describes the business processes of the HUAWEI Online Charging System (OCS). This document is intended for: l

Policy planning engineers

l

Technical support engineers

Change History Updates between document issues are cumulative. Therefore, the latest document issue contains all updates made in previous issues.

Updates in Issue 01 (2010-07-28) Initial commercial release.

Issue 01 (2010-07-28)


iii


Contents

Contents About This Document...................................................................................................................iii Document...................................................................................................................iii 1 Overview of Business Business Processes... Processes........................................................ ..........................................................................................1-1 .....................................1-1 1.1 Concept of o f the OCS System............................................................................................................................1-2 1.2 System Networking.........................................................................................................................................1-2 Networking.........................................................................................................................................1-2

2 Call Charging Processes... Processes................................. ........................................................... .......................................................... ..............................................2-1 .................2-1 2.1 Overview.........................................................................................................................................................2-2 2.2 Process of Charging an Ordinary Call.............................................................................................................2-2 2.2.1 Process of Charging a Call Between Two OCS Subscribers.................................................................2-2 2.2.2 Process Process of Charging a Call Between an OCS Subscriber and a Subscriber of Another Network.........2-7 2.3 Process of Charging Charging a Forwarded Call............................................................................................................2-8 2.3.1 Process Process of Charging a Call That Is Forwarded Unconditionally............................................................2-8 2.3.2 Process Process of Charging a Call That Is Forwarded Conditionally.............................................................2-14 2.4 Reference.......................................................................................................................................................2-20 Reference .......................................................................................................................................................2-20

3 SMS Charging Charging Processes Processes............................................. .......................................................................................... ............................................................. ................3-1 3-1 3.1 Overview.........................................................................................................................................................3-2 Overview. ........................................................................................................................................................3-2 3.2 Process of Charging Charging an Ordinary Short Message Through DCC....................................................................3-2 3.3 Process of Charging Charging an Ordinary Short Message Based on SMPP+..............................................................3-3 3.4 Process of Charging Charging an Ordinary Short Message Based on CAMEL3...........................................................3-4 3.5 Reference.........................................................................................................................................................3-6 Reference...... ...................................................................................................................................................3-6

4 Activation Processes.... Processes........................................ ......................................................................... ......................................................................... ...................................... 4-1 4.1 Overview.........................................................................................................................................................4-2 4.2 Process of Activating an Account by Making the First Call...........................................................................4-2 4.3 Pr ocess ocess of Activating an Account Through the WebService Interface...........................................................4-4 4.4 Process of Activating Activating an Account on the SMAP............................................................................................4-5 4.5 Process of Activating Activating an Account Through IVR............................................................................................4-5 4.6 Pr ocess ocess of Activating an Account by Sending a Short Message.....................................................................4-7 4.7 Pr ocess ocess of Activating an Account by Recharging the Account by Using a Recharge Card.........................4-11 4.8 Reference............................................................................................................. Reference.......................................................................................................................................................4-12 ..........................................4-12

5 Recharge Processes. Processes....................... ............................................ ............................................ ............................................ ............................................. ............................5-1 .....5-1 5.1 Overview.........................................................................................................................................................5-2 5.2 Process of Recharging an Account by Using a Recharge Card Through IVR................................................5-2 Issue 01 (2010-07-28)


v


Contents

5.3 Process of Recharging an Account by Using a Recharge Recharge Card Through USSD............................................ 5-8 5.4 Process of Recharging an Account by Using a Recharge Card Through a Short Message..........................5-11 5.5 Process of Recharging an Account by Using a Recharge Card Manually....................................................5-14 5.6 Process of Recharging an Account by Cash..................................................................................................5-17 5.7 Process of Recharging an Account by Dialing a Recharge Access Code.....................................................5-18 5.8 Process of Recharging Recharging an Account Through the EVC..................................................................................5-19 5.9 Reference.......................................................................................................................................................5-22 Reference .......................................................................................................................................................5-22

6 Balance Query Processes.... Processes.............................. ..................................................... ..................................................... ..................................................6 ........................6-1 -1 6.1 Overview.........................................................................................................................................................6-2 Overview. ........................................................................................................................................................6-2 6.2 Process of Querying Querying the Account Balance of a Subscriber Through IVR......................................................6-2 6.2.1 Process Process of Querying the Account Balance of a Subscriber Through IVR When the Subscriber Is Free of Charge............................................................................................................................................................. Charge......................................................................... .................................................................................... 6-2 6.2.2 Process of Querying the Account Balance of a Subscriber Through IVR When the Subscriber Is Charged .........................................................................................................................................................................6-3 .... .....................................................................................................................................................................6-3 6.3 Process of Querying Querying the Account Balance of a Subscriber Through USSD...................................................6-4 6.3.1 Process Process of Querying the Account Balance of a Subscriber Through USSD When the Subscriber Is Free of Charge.........................................................................................................................................................6-4 6.3.2 Process of Querying the Account Balance of a Subscriber Through USSD When the Subscriber Is Charged .........................................................................................................................................................................6-5 ................ .........................................................................................................................................................6-5 6.4 Process of Querying Querying the Account Balance of a Subscriber by Sending a Short Message..............................6-6 6.4.1 Process Process of Querying the Account Balance of a Subscriber by Sending a Short Message When the Su bscriber Is Free of Charge...........................................................................................................................6-6 6.4.2 Process Process of Querying the Account Balance of a Subscriber by Sending a Short Message When the Subscriber Is Charged................................................................ Charged..................................................................................................................................... ..................................................................... 6-7 6.5 Process of Querying the Account Balance of a Subscriber Through the WebService WebService Interface.................... 6-9 6.6 Process of Querying the Account Balance of a Subscriber on the SMAP....................................................6-10 6.7 Reference.......................................................................................................................................................6-10 Reference...... .................................................................................................................................................6-10

7 Balance Transfer Processes.... Processes.............................. ..................................................... ..................................................... ..............................................7-1 ....................7-1 7.1 Overview.........................................................................................................................................................7-2 Overview....... ..................................................................................................................................................7-2 7.2 Process of Transferring Transferring a Balance Through the IVR......................................................................................7-2 7.3 Process of Transferring Transferring a Balance Through the USSD...................................................................................7-4 7.4 Process of Transferring Transferring a Balance Through the WebService Interface.......................................................... Interface.......................................................... 7-7 7.5 Process of Transferring Transferring a Balance on the SMAP............................................................................................7-8 7.6 Reference.........................................................................................................................................................7-9 Reference .........................................................................................................................................................7-9

8 Monthly Settlement Settlement Processes. Processes........................... ..................................................... ...................................................... ...........................................8-1 ................8-1 8.1 Overview.........................................................................................................................................................8-2 8.2 Monthly Settlement Settlement Process............................................................................................................................8-2 8.3 Process of Notifying Notifying a Subscriber of the Monthly Settlement by Short Message..........................................8-2 8.4 Reference.........................................................................................................................................................8-3 Reference .........................................................................................................................................................8-3

9 Registration Registration and Deregistration Processes.. Processes.............................. ......................................................... ..............................................9-1 .................9-1 9.1 Overview.........................................................................................................................................................9-2 Overview. ........................................................................................................................................................9-2 9.2 Subscriber Subscriber Registration Processes...................................................................................................................9-2 vi


Issue 01 (2010-07-28)


Contents

9.2.1 Process of Registering a Subscriber.......................................................................................................9-2 9.2.2 Process of Registering Subscribers in Batches......................................................................................9-3 9.3 Subscriber Deregistration Processes...............................................................................................................9-4 9.3.1 Process of Deregistering a Subscriber....................................................................................................9-4 9.3.2 Process of Deregistering Subscribers in Batches...................................................................................9-4 9.4 Reference.........................................................................................................................................................9-5 Reference .........................................................................................................................................................9-5

10 Password Change Chan ge Processes.... Processes....................................... ...................................................................... ..........................................................10-1 .......................10-1 10.1 Overview.....................................................................................................................................................10-2 Overview..... ................................................................................................................................................10-2 10.2 Process of Changing Changing a Password Through the WebService Interface........................................................10-2 10.3 Process of Changing Changing a Password on the SMAP..........................................................................................10-3 10.4 Process of Changing Changing a Password Through USSD.......................................................................................10-3 10.5 Process of of Changing a Password Through IVR..........................................................................................10-4 10.6 Reference.....................................................................................................................................................10-6 Reference.....................................................................................................................................................10-6

11 MMS Charging Charging Processes..... Processes....................................... .................................................................... ..............................................................11 ............................11-1 -1 11.1 Overview.....................................................................................................................................................11-2 Overview .....................................................................................................................................................11-2 11.2 Process of Charging Charging for the MMS Service Through DCC..........................................................................11-2 11.3 Process of of Charging for the MMS Service Through EMPP.......................................................................11-3 11.4 Reference.....................................................................................................................................................11-4 Reference.... .................................................................................................................................................11-4

12 GPRS Charging Processes Charging Processes............................................................ ....................................................................................................12-1 ........................................12-1 12.1 Overview.....................................................................................................................................................12-2 12.2 Process of Charging for the GPRS Service Through DCC.........................................................................12-2 12.3 Process Process of Charging for the GPRS Service Through CAMEL3.................................................................12-4 12.4 Reference.....................................................................................................................................................12-6 Reference.....................................................................................................................................................12-6

13 International Roaming Service Processes.........................................................................13-1 13.1 Overview.....................................................................................................................................................13-2 13.2 Process of Charging for an International Roaming Call.............................................................................13-2 13.2.1 13 .2.1 Process of Charging for an International Roaming Call in CAMEL2 Mode.....................................13-2 13.2.2 Process Process of Charging for an International Roaming Call in UCB Mode.............................................13-4 13.3 Process of of Charging for an International Short Message............................................................................13-7 13.3.1 Process Process of Charging for an International Short Message Based on SMPP+......................................13-7 13.4 Reference.....................................................................................................................................................13-8 Reference.....................................................................................................................................................13-8

14 FN Service Service Processes... Processes......................... ............................................. ............................................. ............................................ ........................................14-1 ..................14-1 14.1 Overview.....................................................................................................................................................14-2 Overview .....................................................................................................................................................14-2 14.2 Processes Processes of Enabling the FN Service for a Subscriber..............................................................................14-2 14.2.1 Process Process of Enabling the FN Service for a Subscriber Through IVR..................................................14-2 14.2.2 Process Process of Enabling the FN Service for a Subscriber Through the WebService Interface................14-4 14.2.3 Process Process of Enabling the FN Service for a Subscriber on the SMAP..................................................14-5 14.2.4 Processes Processes of Enabling the FN Service for a Subscriber Through USSD...........................................14-6 14.2.5 14 .2.5 Process of Enabling the FN Service for a Subscriber Through a Short Message..............................14-9 14.3 Processes Processes of Disabling the FN Service for a Subscriber...........................................................................14-10

Issue 01 (2010-07-28)


vii


Contents

14.3.1 Process of Disabling the FN Service for a Subscriber Through IVR...............................................14-10 14.3.2 Process of Disabling the FN Service for a Subscriber Through the WebService Interface.............14-11 14.3.3 Process of Disabling the FN Service for a Subscriber on the SMAP..............................................14-12 14.3.4 Processes of Disabling the FN Service for a Subscriber Through USSD........................................14-13 14.3.5 Process of Disabling the FN Service for a Subscriber Through a Short Message...........................14-15 14.4 Processes Processes of Adding or Changing an FN of a Subscriber.........................................................................14-16 14.4.1 Process Process of Adding or Changing an FN of a Subscriber Through IVR.............................................14-16 14.4.2 14 .4.2 Process of Adding or Changing an FN of a Subscriber Through the WebService Interface...........14-18 14.4.3 Process of Adding or Changing an FN of a Subscriber on the SMAP.............................................14-19 14.4.4 Processes of Adding or Changing an FN of a Subscriber Through USSD......................................14-20 14.4.5 Process of Adding or Changing an FN of a Subscriber Through a Short Message.........................14-23 14.5 Processes of Querying an FN of a Subscriber...........................................................................................14-24 14.5.1 Process of Querying an FN of a Subscriber Through IVR..............................................................14-24 14.5.2 Process of Querying an FN of a Subscriber Through the WebService Interface.............................14-25 14.5.3 Process of Querying an FN of a Subscriber on the SMAP..............................................................14-25 14.5.4 Processes of Querying an FN of a Subscriber Through USSD........................................................14-26 14.5.5 Process Process of Querying an FN of a Subscriber Through a Short Message...........................................14-28 14.6 Reference...................................................................................................................................................14-29 Reference.... ...............................................................................................................................................14-29

15 ICS Service Processes.......... Processes................................................................ ..................................................................................................15 ............................................15-1 -1 15.1 Overview.....................................................................................................................................................15-2 Overview..... ................................................................................................................................................15-2 15.2 Processes of Enabling the ICS Service for a Subscriber.............................................................................15-2 15.2.1 Processes Processes of Enabling the ICS Service for a Subscriber Through IVR.............................................15-2 15.2.2 Processes Processes of Enabling the ICS Service for a Subscriber Through the WebService Interface............15-4 15.2.3 Processes Processes of Enabling the ICS Service for a Subscriber on the SMAP.............................................15-5 15.3 Processes of Disabling the ICS Service for a Subscriber............................................................................15-6 15.3.1 Processes Processes of Disabling the ICS Service for a Subscriber Through IVR............................................15-6 15.3.2 Processes Processes of Disabling the ICS Service for a Subscriber Through the WebService Interface..........15-7 15.3.3 Processes Processes of Disabling the ICS Service for a Subscriber on the SMAP............................................15-8 15.4 Processes Processes of Adding or Changing an ICS number of a Subscriber.............................................................15-8 15.4.1 Process Process of Adding or Changing an ICS number of a Subscriber Through IVR................................15-9 15.4.2 Process Process of Adding or Changing an ICS number of a Subscriber Through the WebService Interface .....................................................................................................................................................................15-10 15.4.3 Process of Adding or Changing an ICS number of a Subscriber on the SMAP..............................15-11 15.5 Processes of Querying an ICS number of a Subscriber............................................................................15-12 15.5.1 Processes of Querying an ICS number of a Subscriber Through IVR.............................................15-13 15.5.2 Processes of Querying an ICS number of a Subscriber Through the WebService Interface...........15-13 15.5.3 Processes of Querying an ICS number of a Subscriber on the SMAP.............................................15-14 15.6 Process of ICS Monthly Settlement .........................................................................................................15-15 15.7 Reference............................................................................................................ Reference...................................................................................................................................................15-15 .......................................15-15

16 Home Zone Service Service Processes Processes........................... ...................................................... ...................................................... ........................................16-1 .............16-1 16.1 Overview.....................................................................................................................................................16-2 Overview..... ................................................................................................................................................16-2 16.2 Processes Processes of Enabling the Home Zone Service for a Subscriber................................................................16-2 viii


Issue 01 (2010-07-28)


Contents

16.2.1 Process of Enabling the Home Zone Service for a Subscriber Through IVR....................................16-2 16.2.2 Process of Enabling the Home Zone Service for a Subscriber Through the WebService Interface .......................................................................................................................................................................16-4 16.2.3 Process of Enabling the Home Zone Service for a Subscriber on the SMAP....................................16-5 16.3 Processes of Disabling the Home Zone Service for a Subscriber...............................................................16-6 16.3.1 Process of Disabling the Home Zone Service for a Subscriber Through IVR...................................16-6 16.3.2 Process of Disabling the Home Zone Service for a Subscriber Through the WebService Interface .......................................................................................................................................................................16-7 ................ .......................................................................................................................................................16-7 16.3.3 Process Process of Disabling the Home Zone Service for a Subscriber on the SMAP...................................16-8 16.4 Processes Processes of Adding or Changing a Home Zone of a Subscriber...............................................................16-8 16.4.1 Process Process of Adding or Changing a Home Zone of a Subscriber Through IVR...................................16-9 16.4.2 Process Process of Adding or Changing a Home Zone of a Subscriber Through the WebService Interface .....................................................................................................................................................................16-10 ................ .....................................................................................................................................................16-10 16.4.3 16 .4.3 Process of Adding or Changing a Home Zone of a Subscriber on the SMAP.................................16-11 16.5 Processes of Querying a Home Zone of a Subscriber...............................................................................16-12 16.5.1 Process of Querying a Home Zone of a Subscriber Through IVR...................................................16-13 16.5.2 Process of Querying a Home Zone of a Subscriber Through the WebService Interface.................16-14 16.5.3 Process of Querying a Home Zone of a Subscriber on the SMAP..................................................16-14 16.6 Reference............................................................................................................ Reference...................................................................................................................................................16-15 .......................................16-15

17 Child-Parent Card Card Service Processes........ Processes.................................................................................. ..........................................................................17-1 17-1 17.1 Overview.....................................................................................................................................................17-2 Overview..... ................................................................................................................................................17-2 17.2 Process of Subscribing Subscribing to a Product............................................................................................................17-2 17.2.1 Process Process of Subscribing to a Child-Parent Card Product Through the WebService Interface............17-3 17.3 Process of Unsubscribing Unsubscribing from a Product...................................................................................................17-4 17.3.1 Process Process of Unsubscribing from a Child-Parent Card Product Through the WebService Interface.. .17-4 17.4 Process of Changing Changing a Consumption Limit.................................................................................................17-5 17.4.1 Process Process of Changing a Consumption Limit Through the WebService Interface...............................17-5 17.4.2 Process Process of Changing a Consumption Limit on the SMAP.................................................................17-6 17.4.3 17 .4.3 Process of Changing a Consumption Limit Through the IVR...........................................................17-6 17.5 Process of Recharging a Child Card and a Parent Card..............................................................................17-7 17.5.1 Process of Recharging a Child Card and a Parent Card Through the IVR........................................17-8 17.5.2 Process of Recharging a Child Card and a Parent Card Through the USSD.....................................17-9 17.6 Process of Performing Monthly Settlement for a Child Card and a Parent Card......................................17-10 17.7 Reference............................................................................................................ Reference...................................................................................................................................................17-10 .......................................17-10

18 Passby Processes............................................. Processe s........................................................................................................ ........................................................................ .............18-1 18-1 18.1 Overview.....................................................................................................................................................18-2 Overview..... ................................................................................................................................................18-2 18.2 Process of Passing Passing by a Service Manually..................................................................................................18-2 18.3 Process of Passing Passing By a Service Automatically..........................................................................................18-4 18.4 Process of of Passing by a Service by the SCP Database................................................................................18-5 18.5 Process of Passing Passing by a Service by the Physical Database of the CBP......................................................18-8 18.6 Process of Passing Passing by Data Services by the MDSP....................................................................................18-8 18.7 Reference.......................................................................................................... Reference.....................................................................................................................................................18-9 ...........................................18-9

Issue 01 (2010-07-28)


ix


Contents

19 Audit Process......... Process................................................ ............................................................................... ........................................................................... ...................................19-1 19-1 19.1 Overview.....................................................................................................................................................19-2 19.2 Audit Process........................................................................................................... Process...............................................................................................................................................19-2 ....................................19-2 19.3 Reference.......................................................................................................... Reference.....................................................................................................................................................19-2 ...........................................19-2

A Glossary...................... Glossary...................................................................... ................................................................................................. ...............................................................A-1 ..............A-1 A.1 Numerics.................................................................................. Numerics........................................................................................................................................................A-2 ......................................................................A-2 A.2 A....................................................................................................................................................................A-2 A.3 B....................................................................................................................................................................A-2 A.4 C....................................................................................................................................................................A-3 A.5 D....................................................................................................................................................................A-4 A.6 E............................................................................................................................................................ E.....................................................................................................................................................................A-4 .........A-4 A.7 F.....................................................................................................................................................................A-4 A.8 G....................................................................................................................................................................A-5 A.9 H....................................................................................................................................................................A-5 A.10 I....................................................................................................................................................................A-5 A.11 M.............................................................................................. M..................................................................................................................................................................A-5 ....................................................................A-5 A.12 N..................................................................................................................................................................A-6 A.13 O..................................................................................................................................................................A-6 A.14 P...................................................................................................................................................................A-6 A.15 R..................................................................................................................................................................A-7 A.16 S...................................................................................................................................................................A-7 A.17 T...................................................................................................................................................................A-7 T........... ........................................................................................................................................................A-7 A.18 U..................................................................................................................................................................A-8 U........... .......................................................................................................................................................A-8 A.19 V..................................................................................................................................................................A-8 V........... .......................................................................................................................................................A-8 A.20 W.................................................................................................................................................................A-8 W.................................................................................................................................................................A-8

x


Issue 01 (2010-07-28)


Figures

Figures Figure 1-1 Ty pical physical networking diagram of the OCS............................................................................. OCS............................................................................. 1-3

Normal ormal process of charging the calling party in a call between two OCS subscribers......................2-3 Figure 2-1 N Normal ormal process of charging the called party in a call between two two OCS subscribers....................... 2-6 Figure 2-2 N Figure 2-3 N Normal ormal process of charging the calling party in a call made by an OCS subscriber to a subscriber of another network.....................................................................................................................................................2-7 netwo rk.....................................................................................................................................................2-7 Figure 2-4 Ch Charging arging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a third OCS subscriber.....................................................................................................................2-9 Figure 2-5 Ch Charging arging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a non-OCS subscriber....................................................................................................................2-12 Figure 2-6 Ch Charging arging process when a call made by a non-OCS s ubscriber to an OCS subscriber is unconditionally forwarded to another OCS subscriber.................................................................................................................2-13

Charging arging process when a call made by an OCS subscriber to another OCS subscriber is conditionally Figure 2-7 Ch forwarded to a third OCS subscriber...................................................................................................................2-15 Charging arging process when a call made by an OCS subscriber to another OCS subscriber is conditionally Figure 2-8 Ch forwarded to a non-OCS subscriber....................................................................................................................2-18 Figure 2-9 Ch Charging arging process when a call made by a non-OCS subscriber to an OCS subscriber is conditionally forwarded to another OCS subscriber.................................................................................................................2-19 Figure 3-1 Pr ocess ocess of charging an Ordinary Ordinary short message through DCC.......................................................... DCC.......................................................... 3-2 Figure 3-2 Pr ocess ocess of charging for an ordinary short message based on SMPP+................................................3-3 Figure 3-3 Pr ocess ocess of charging for an ordinary short message based on CAMEL3............................................3-5

ocess of activating an account by making the first call...................................................................4-3 Figure 4-1 Pr ocess Figure 4-2 Pr ocess ocess of activating an account through the WebService interface..................................................4-4 Figure 4-3 Pr ocess ocess of activating an account on the SMAP..................................................................................4-5 Figure 4-4 N Normal ormal process of activating an account through IVR...................................................................... IVR...................................................................... 4-6

Normal ormal process of activating an account by sending a short message through SMPP+....................4-8 Figure 4-5 N Normal ormal process of activating an account by sending a short message through CAMEL3...............4-10 Figure 4-6 N Figure 4-7 Pr ocess ocess of Activating an Account by Recharging the Account by Using a Recharge Card............4-11 Figure 5-1 Pr ocess ocess of recharging the personal account of a subscriber through IVR..........................................5-3 Figure 5-2 Pr ocess ocess of recharging the account account of another OCS subscriber through IVR..................................... 5-6

ocess of recharging an account through USSD...............................................................................5-9 Figure 5-3 Pr ocess Figure 5-4 N Normal ormal process of recharging an account by using a recharge card through a short message.........5-12 Figure 5-5 Normal process of recharging an account manually.........................................................................5-15 Figure 5-6 Normal process of recharging an account by cash...........................................................................5-17 Figure 5-7 Normal process of recharging the personal account of a subscriber by dialing the recharge access code .............................................................................................................................................................................5-18

Issue 01 (2010-07-28)


xi


Figures

Figure 5-8 Process of recharging an account through the EVC not in DCC mode............................................5-20 Figure 5-9 Process of recharging an account through the EVC in DCC mode..................................................5-21 Figure 6-1 Normal process of querying the account balance of a subscriber through IVR when the subscriber is free of charge.......................................................................................................................................... charge.........................................................................................................................................................6-2 ...............6-2 Figure 6-2 Normal process of querying the account balance of a subscriber through IVR when the subscriber is charged..................................................................................................................................................................6-3 Figure 6-3 N Normal ormal process of querying the account balance of a subscriber through USSD when the subscriber is free of charge.........................................................................................................................................................6-4 charge .........................................................................................................................................................6-4 Figure 6-4 N Normal ormal process of querying the account balance of a subscriber through USSD when the subscriber is charged..................................................................................................................................................................6-5 charged.......... ........................................................................................................................................................6-5 Figure 6-5 N Normal ormal process of querying the account balance of a subscriber by sending a short message when the subscriber is f ree ree of charge........................................................................ charge....................................................................................................................................6-6 ............................................................6-6

Normal ormal process of querying the account balance of a subscriber by sending a short message when the Figure 6-6 N subscriber is charged.............................................................................................................................................6-8 Figure 6-7 Normal process of querying the account balance of a subscriber through the WebService interface ...............................................................................................................................................................................6-9 ...................... .........................................................................................................................................................6-9 Figure 6-8 N Normal ormal process of querying the account balance of a subscriber on the SMAP..............................6-10 Figure 7-1 Pr ocess ocess of transferring a balance through the IVR.............................................................................7-3 Figure 7-2 Pr ocess ocess of transferring a balance through the USSD (triggered in U-CSI mode)..............................7-5

ocess of transferring a balance through the USSD (triggered in MAP mode)................................7-6 Figure 7-3 Pr ocess ocess of transferring a balance through the WebService interface.................................................7-7 Figure 7-4 Pr ocess Figure 7-5 Pr ocess ocess of transferring a balance on the SMAP.................................................................................7-8 Figure 8-1 Pr ocess ocess of notifying a subscriber of the monthly settlement by short message.................................8-2 Figure 9-1 Pr ocess ocess of registering a subscriber.....................................................................................................9-2

ocess of registering subscribers in batches......................................................................................9-3 Figure 9-2 Pr ocess Figure 9-3 Pr ocess ocess of deregistering a subscriber..................................................................................................9-4 Figure 9-4 Pr ocess ocess of deregistering subscribers in batches..................................................................................9-5 Figure 10-1 N Normal ormal process of changing a password through the WebService interface.................................10-2

Normal ormal process of changing a password on the SMAP.................................................................10-3 Figure 10-2 N Normal ormal process of changing a password through USSD...............................................................10-4 Figure 10-3 N Figure 10-4 N Normal ormal process of changing a password through IVR...................................................................10-5 Figure 11-1 N Normal ormal process of charging for the MMS service online through DCC........................................11-2 Figure 11-2 N Normal ormal process of charging for the MMS service online through EMPP......................................11-3

Process rocess of charging for the GPRS service through DCC...............................................................12-3 Figure 12-1 P Figure 12-2 P Process rocess of charging for the GPRS service through CAMEL3.......................................................12-5 Figure 13-1 N Normal ormal process of charging for an international roaming call in CAMEL2 mode........................13-3 Figure 13-2 Normal process of charging for an international roaming call in UCB mode................................13-5

Normal ormal process of charging for an international short message based on SMPP+........................13-7 Figure 13-3 N Normal ormal process of enabling the FN service for a subscriber through IVR....................................14-3 Figure 14-1 N Figure 14-2 N Normal ormal process of enabling the FN service for a subscriber through the WebService interface .............................................................................................................................................................................14-4 ...................... .......................................................................................................................................................14-4 Figure 14-3 N Normal ormal process of enabling the FN service for a subscriber on the SMAP...................................14-5 Figure 14-4 N Normal ormal process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode) .............................................................................................................................................................................14-7 ...................... .......................................................................................................................................................14-7

xii


Issue 01 (2010-07-28)


Figures

Figure 14-5 Normal process of enabling the FN s ervice for a subscriber through USSD (triggered in MAP mode) .............................................................................................................................................................................14-8 Figure 14-6 Normal process of enabling the FN service for a subscriber through a short message..................14-9 Figure 14-7 Normal process of disabling the FN service for a subscriber through IVR..................................14-11 Figure 14-8 Normal process of disabling the FN service for a subscriber through the WebService interface ...........................................................................................................................................................................14-12 Figure 14-9 N Normal ormal process of disabling the FN service for a subscriber on the SMAP................................14-13 Figure 14-10 Normal process of disabling the FN service for a subscriber through USSD (triggered in U-CSI mode) ...........................................................................................................................................................................14-14 ...................... .....................................................................................................................................................14-14 Figure 14-11 Normal process of disabling the FN service for a subscriber through USSD (triggered in MAP mode) ...........................................................................................................................................................................14-15 ...................... .....................................................................................................................................................14-15 Figure 14-12 Normal process of disabling the FN service for a subscriber through a short message.......... ...14-16 Figure 14-13 Normal process of adding or changing an FN of a subscriber through IVR..............................14-17

interface Figure 14-14 Normal process of adding or changing an FN of a subscriber through the WebService interface ...........................................................................................................................................................................14-18 ...................... .....................................................................................................................................................14-18 Figure 14-15 Normal process of adding or changing an FN of a subscriber on the SMAP.............................14-19 SMAP.............................14-19 Figure 14-16 Normal process of adding or changing an FN of a subscriber through USSD (triggered in U-CSI mode).................................................................................................................................................................14-21 mode)............ .....................................................................................................................................................14-21 Figure 14-17 Normal process of adding adding or or changing changing an FN of a subscriber through USSD (triggered (triggered in MAP mode) mode) ...........................................................................................................................................................................14-22 ...................... .....................................................................................................................................................14-22 Figure 14-18 Normal process of adding or changing an FN of a subscriber through a short message............14-23 Figure 14-19 Process of querying an FN of a subscriber through IVR............................................................14-24 Figure 14-20 Normal process of querying an FN of a subscriber through the WebService interface........... ..14-25 Figure 14-21 Process of querying an FN of a subscriber on the SMAP..........................................................14-26 Figure 14-22 Normal process of querying an FN of a subscriber through USSD (triggered in U-CSI mode) ...........................................................................................................................................................................14-27 ...................... .....................................................................................................................................................14-27 Figure 14-23 Normal process of querying an FN of a subscriber through USSD (triggered in MAP mode) ...........................................................................................................................................................................14-28 ...................... .....................................................................................................................................................14-28 Figure 14-24 Normal process of querying an FN of a subscriber through a short message.................. ..........14-29 Figure 15-1 N Normal ormal process of enabling the ICS service for a subscriber through IVR...................................15-3

Normal ormal process of enabling the ICS service for a subscriber through the WebService interface Figure 15-2 N .............................................................................................................................................................................15-4 ...................... .......................................................................................................................................................15-4 Figure 15-3 N Normal ormal process of enabling the ICS service for a subscriber on the SMAP..................................15-5 Figure 15-4 N Normal ormal process of disabling the ICS service for a subscriber through IVR..................................15-6 Figure 15-5 N Normal ormal process of disabling the ICS service for a subscriber through the WebService interface .............................................................................................................................................................................15-7 ...................... .......................................................................................................................................................15-7

Normal ormal process of disabling the ICS service for a subscriber on the SMAP.................................15-8 Figure 15-6 N Figure 15-7 N Normal ormal process of adding or changing an ICS number of a subscriber through IVR....................15-9 Figure 15-8 Normal process of adding or changing an ICS number of a subscriber through the WebService interface ...........................................................................................................................................................................15-11 ...................... .....................................................................................................................................................15-11 Figure 15-9 N Normal ormal process of adding or changing an ICS number of a subscriber on the SMAP................15-12 Figure 15-10 Process of querying an ICS number of a subscriber through IVR.............................................15-13 Figure 15-11 Normal process of querying an ICS number of a subscriber through the WebService interface ...........................................................................................................................................................................15-14 ...................... .....................................................................................................................................................15-14 Figure 15-12 Process of querying an ICS number of a subscriber on the SMAP............................................15-14 Figure 16-1 N Normal ormal process of enabling the Home Zone service for a subscriber through IVR.......................16-3

Issue 01 (2010-07-28)


xiii


Figures

Figure 16-2 Normal process of enabling the Home Zone service for a subscriber through the WebService interface .............................................................................................................................................................................16-4 Figure 16-3 Normal process of enabling the Home Zone service for a subscriber on the SMAP.....................16-5 Figure 16-4 Normal process of disabling the Home Zone service for a subscriber through IVR......................16-6 Figure 16-5 Normal process of disabling the Home Zone service for a subscriber through the WebService interface .............................................................................................................................................................................16-7 Figure 16-6 Normal process of disabling the Home Zone service for a subscriber on the SMAP....................16-8 Figure 16-7 Normal process of adding or changing a Home Zone of a subscriber through IVR......................16-9 Figure 16-8 Normal process of adding or changing a Home Zone of a subscriber through the WebService interface ...........................................................................................................................................................................16-11 Figure 16-9 Normal process of adding or changing a Home Zone of a subscriber on the SMAP...................16-12 Figure 16-10 Process of querying a Home Zone of a subscriber through IVR................................................16-13 Figure 16-11 Normal process of querying a Home Zone of a subscriber through the WebService interface ...........................................................................................................................................................................16-14 Figure 16-12 Process of querying a Home Zone of a subscriber on the SMAP..............................................16-15 Figure 17-1 Process of subscribing to a child-parent card product through the WebService interface.............17-3 Figure 17-2 Process of unsubscribing from a child-parent card product through the WebService interface .............................................................................................................................................................................17-4 Figure 17-3 Process of changing a consumption limit through the WebService interface................................17-5 Figure 17-4 Process of changing a consumption limit on the SMAP................................................................17-6 Figure 17-5 Process of changing a consumption limit through the IVR............................................................17-7 Figure 17-6 Process of recharging a common child card through the IVR........................................................17-8 Figure 18-1 Normal process of passing by a service manually..........................................................................18-3 Figure 18-2 Process of passing by a CAMEL2 voice call by the SCP database in the calling process.............18-5 Figure 18-3 P Process rocess of passing by a CAMEL2 voice call by the SCP database in the called process..............18-7 Figure 18-4 N Networking etworking about passing by data services by the MDSP.............................................................18-9

xiv


Issue 01 (2010-07-28)


1 Overview of Business Processes

1

Overview of Business Processes

About This Chapter

1.1 Concept of the OCS System The Online Charging System (OCS) is an uniform charging platform that helps telecom network carriers to charge voice, data and multimedia services of fixed, mobile, and data networks. 1.2 System Networking This chapter describes the typical networking and the function of each NE of the OCS system.

Issue 01 (2010-07-28)


1-1



1.1 Concept of the OCS System The Online Charging System (OCS) is an uniform charging platform that helps telecom network carriers to charge voice, data and multimedia services of fixed, mobile, and data networks. The OCS system helps telecom network carriers to conform to the complicated operation environment, new services, different cooperators, and detailed customer types. The OCS system can run on the Global System Of Mobile Telephone (GSM) network, Code Division Multiple Access (CDMA) network , Time Division Multiple Access (TDMA) network, Session Initiation Protocol (SIP) network and Next Generation Network (NGN). In addition, the system can precisely realize the credit control to subscribers at a maximum. In this way, the risk of arrears can be reduced, and the revenue loss of carriers can be reduced accordingly. The OCS system provides the functions such as: l

Product management management

l

Resource management

l

Rating and billing

l

Credit control

l

Recharge center

l

Call control

The OCS system is of good expendability and convergence. Through the convergence convergence with external charging system, the OCS system can provide a uniform charging platform, a uniform service management platform and a uniform customer care platform for prepaid subscribers, postpaid subscribers and hybrid subscriber.

1.2 System Networking This chapter describes the typical networking and the function of each NE of the OCS system. The OCS system is the core charging system in the carrier networking. The core components of the OCS system, the SCP, CBP, and BMP, form the typical networking of the OCS system. With these components, the OCS system provides diversified interfaces for external systems and interacts with the external systems flexibly. Figure 1-1 shows the typical physical networking diagram of the OCS system.

1-2


Issue 01 (2010-07-28)



Figure 1-1 Typical physical networking diagram of the OCS

BMP: Business Manager Point

CBP: Convergent Billing Point

CRM: Customer Relations Management

GFEP: General Front End Processor

GGSN: Gateway GPRS Support Node

HLR: Home Location Register

iMan iManag ager er I200 I2000: 0: Netw Networ ork k mana manage geme ment nt syst system em

iWEB iWEB:: Repo Report rt syst system em

MSC: Mobile Switching Center

MMSC: Multimedia Messaging Service Center

RBI: Record Bill Interface

SCP: Service Control Point

SMSC: Short Message Service Center

SSP: Service Switching Point

SS7: No.7 Signaling Network

URP: Universal Resource Platform

USAU: Un Universal Si Signaling Ac Access Po Point

UVC: Un Uniform Vo Voucher Ce Center

Issue 01 (2010-07-28)


1-3



BMP The BMP is the core component of the service operation management in the OCS system. The BMP manages the system, products, customers, resources, and charging and provides customer services. In certain networking, the BMP provides the third-party system with the WebService interface for handling customer services instead of directly providing the customer service function.

SCP The SCP provides the call access and call control functions in the OCS system.

CBP The OCS system separates the charging block from the SCP of intelligent networks and the mobile data service platform of data service networks. The CBP provides the charging and rating functions.

UVC In the OCS system, the UVC system manages recharge cards, including the operations of generating, stocking, releasing, activating, and permanently locking recharge cards. Only the recharge cards in active state can be used. If certain recharge cards are damaged or the passwords of the recharge cards are disclosed, the recharge cards in active state can be permanently locked. The recharge cards that are permanently locked cannot be used.

GFEP The GFEP converts protocols and forwards messages when other entities communicate with OCS entities. For example, when the SMSC communicates with the CBP, the GFEP converts the SMPP+ message sent by the SMSC to a Diameter message that can be identified by the CBP and sends the message to the CBP for charging. The GFEP adopts the TCP/IP protocol to communicate with other entities. The SOCKET connection is built up for communication.

RBI The RBI is the channel for record transportation between the CBP and billing center, operation system, and other systems. The RBI can also function as the channel for file transportation between any two OCS entities.

USAU To meet the requirements for network development, Huawei provides a universal signaling access platform for IN products, namely, the USAU. The USAU is based on the Open Standards Telecom Architecture (OSTA) platform, supporting the narrowband SS7 signaling protocol and broadband SIGTRAN protocol. It has higher signaling link processing capability and integration degree than the traditional SAU and provides more powerful signaling access capability for: l

1-4

MSC/SSP Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)

HUAWEI OCS Business Process Description l

HLR

l

URP

Issue 01 (2010-07-28)



1-5


2 Call Charging Processes

2

Call Charging Processes

About This Chapter

2.1 Overview In the OCS system, real-time charging for ordinary calls and forwarded calls is adopted. Calls are divided into into the following types: calls from calling parties and calls from called parties. 2.2 Process of of Charging an Ordinary Call Ordinary calls calls between subscribers are classified into the following types: ordinary calls between OCS subscribers subscribers and ordinary calls from OCS subscribers to other network subscribers. The following sections sections describe the processes of charging a calling party and a called party for the two types of calls, and the process for exception handling. handlin g. 2.3 Process of of Charging a Forwarded Call The forwarded forwarded calls are classified into the calls that are forwarded conditionally and the calls that are forwarded forwa rded unconditionally. The following sections describe the charging process of each type of forwarded forwarded call. 2.4 Reference Referenc e This section describes the terms used in the call processes.

Issue 01 (2010-07-28)


2-1



2.1 Overview In the OCS system, real-time charging for ordinary calls and forwarded calls is adopted. Calls are divided into the following types: calls from calling parties and calls from called parties. In the OCS system, after a voice call is triggered to the SCP through MSC/VLR/SSP, the SCP authenticates the incoming right and outgoing right of the call. After the call passes the authentication, the SCP sends a charging request to the CBP, and then the CBP authenticates and charges for the call, and the SCP controls the call. In this case, the OCS system can control, monitor, and charge for the call in real time. The common call charging processes include the following types: l

Process of charging for an ordinary call

l

Process of charging for a forwarded call

The following sections describe each call charging process in detail.

2.2 Process of Charging an Ordinary Call Ordinary calls between subscribers are classified into the following types: ordinary calls between OCS subscribers and ordinary calls from OCS subscribers to other network subscribers. The following sections sections descri be be the processes of of charging a calling party party and a called party party for the two types of calls, and the process for exception handling.

2.2.1 Process of Charging a Call Between Two OCS Subscribers This section describes the process of charging for a call between two OCS subscribers from three aspects: calling process, called process, and exception handling process.

Process of Charging a Calling Party Figure 2-1 shows the normal process of charging the calling party in a call between two OCS subscribers.

2-2


Issue 01 (2010-07-28)



Figure 2-1 Normal process of charging the calling party in a call between two OCS subscribers MSC/VLR/SSP

SCP

CBP

Subscriber makes a call Trigger call according to O-CSI IDP RRBE

Perform number analysis and basic authentication CCR{Initial}

CCA{Initial}

Perform authentication and budget

AC Continue Connect call ACR CCR{Update}

CCA{Update}

Perform rating, debiting and budget

AC ACR

Repeated

Subscriber hangs up ERB CCR{Terminate}

CCA{Terminate}

Perform rating and debiting

RC

MSC

Mobile Switching Center

VLR

Visitor Location Register

SSP

Service Switching Point

The process is described as follows: 1.

An OCS OCS subscri subscriber ber makes makes a call, call, and and the call is forward forwarded ed to the MSC/VL MSC/VLR/SSP R/SSP.. The MSC/VLR/SSP sends an Send Routing Information (SRI) message to the HLR and obtains the Originating CAMEL Subscription Information (O-CSI) from the HLR. Then the MSC/VLR/SSP determines the SCP that the subscriber belongs to and the service that needs to be triggered according to the GT code and service key in the O-CSI.

2.

Issue 01 (2010-07-28)

The MSC/VLR MSC/VLR/SSP /SSP reports reports the Initial Initial DP (IDP) (IDP) message message to to the SCP SCP to start start call call control. control.


2-3



The IDP message contains the information such as the service key, calling number, and called number. 3.

The SCP SCP deliver deliverss a Reques Requestt Report Report BCSM BCSM Event Event (RRBE) (RRBE) messag messagee to the the MSC/VLR MSC/VLR/SSP /SSP to request the dynamic configuration of the Event Detection Point (EDP). NOTE

The MSC/VLR/SSP creates a Basic Call State Model (BCSM) for each call. Each call has a series of states. A detection point is set between two states, that is, a breakpoint in a call.

4.

The SCP SCP perfo performs rms numb number er analy analysis sis and and basic basic auth authent entica icatio tion. n. The purpose of the authentication is to check whether the subscriber is an intra-network subscriber, whether the subscriber belongs to this SCP, whether the subscriber is in roaming state, and the call type (normal call or call to a special number).

5.

The SCP SCP sends sends a CCR{Init CCR{Initial} ial} message message to the CBP to initiate initiate an authentica authentication tion reque request. st. The CCR{Initial} message contains all the information required for charging, for example: l

Service-context-id: For example, [email protected].

l

request-type : Here, the value is Initial.

l

request-action: Here, the request action is fee deduction.

l

IN-Information: This service information group of the intelligent network contains the information such as the calling number, called number, and charging processing type.

6.

The CBP CBP perfor performs ms preproc preprocessin essing, g, authent authenticati ication, on, durati duration on precal precalcula culation, tion, and prededuction.

7.

The CBP CBP sends sends a CCA{In CCA{Initial} itial} message message to return return the authentica authentication tion result result and author authorized ized duration to the SCP. The authentication result contains the information about whether the subscriber state is normal and whether to notify the subscriber of the small balance.

8.

The SCP SCP sends sends a Continue Continue message message to prompt prompt the MSC/VLR MSC/VLR/SSP /SSP to connect connect the the call. call. In addition, the SCP delivers an AC message to monitor the call duration. If the call passes the authentication, the SCP determines the connection parameters. For example, the SCP may need to send an ATI message to the HLR to obtain the location of the called party.

9.

The MSC/VLR MSC/VLR/SSP /SSP connects connects the the call call and monitors monitors the the call call duration duration of of the subsc subscriber riber..

10. When the call call duration duration reaches reaches a segment segment duration, duration, the MSC/VLR/ MSC/VLR/SSP SSP reports reports an ACR message to the SCP. 11. The SCP sends sends a CCR{Update} CCR{Update} message message to the CBP to initiate initiate a fee deductio deduction n request. request. 12. The CBP performs performs rating, rating, debiting, debiting, duration duration precalcul precalculation ation,, and predeductio prededuction. n. The rating procedure is as follows: Find the key value of the subscriber according to the charged number, find the product that the subscriber subscribes to according to the key value and the corresponding subscription relation, and then perform the price policy rule of the product to perform the rating. The debiting procedure is as follows: Invoke the debiting module according to the rating result and process flag (for example, fee deduction) to deduct fees from the account. Then rate the reserved service volume that is newly applied for and invoke the debiting module again for reservation. 13. The CBP sends sends a CCA{Update} CCA{Update} message message to return return the processin processing g result and precal precalcula culated ted duration to the SCP. 2-4


Issue 01 (2010-07-28)



14. The SCP sends sends an AC AC message message to instruct instruct the MSC/VLR MSC/VLR/SSP /SSP to continu continuee the call call and monitor the call duration. 15. When the call call duration duration reaches reaches a segment segment duration, duration, the MSC/VLR/ MSC/VLR/SSP SSP reports reports an ACR message to the SCP. NOTE

The interactions from step 11 through step 15 can be performed multiple times until either of the parties in the call ends the call or the account account balance balance of the charged charged party is used up. up.

16. The subscribe subscriberr hangs up, and the the MSC/VLR/SS MSC/VLR/SSP P reports reports an Event Report Report BCSM (ERB) (ERB) message to the SCP. 17. The SCP sends sends a CCR{Terminat CCR{Terminate} e} message message to the CBP to initiate initiate a charging charging request request and to request the termination of this Diameter message session. 18. The CBP CBP perfor performs ms rating rating and and debitin debiting. g. 19. The CBP sends sends a CCA{Termin CCA{Terminate} ate} message message to return return the process processing ing result result to the SCP and and prompts the SCP to release release the call. 20. The SCP sends sends an RC message message to to prompt the the MSC/VLR/SS MSC/VLR/SSP P to disconnec disconnectt the call. call. The normal process of charging the calling party in a call between two OCS subscribers is complete.

Process of Charging a Called Party Figure 2-2 shows the normal process of charging the called party in a call between two OCS subscribers.

Issue 01 (2010-07-28)


2-5



Figure 2-2 Normal process of charging the called party in a call between two OCS subscribers MSC/VLR/SSPa

HLRb

MSC/VLR/SSPb

SCPb

CBPb

Subscriber A makes a call Initiate route query Perform route query

Return T-CSI Trigger call according to T-CSI IDP

RRBE CCR{Initial} CCA{Initial} AC Continue Request the query of MSRN Send PRN request query MSRN

Return result Return result Connect call

Connect call

HLR

Home Location Register

NOTE

Subscriber A and subscriber B are OCS subscribers. Subscriber A is the calling party, and subscriber B is the called party.


Subscriber Subscriber A makes makes a call to subscri subscriber ber B. B. The call reaches reaches MSC/VL MSC/VLR/SSP R/SSPa.

2.

MSC/VLR/SSPa sends an SRI request to HLR b. HLR b returns the Terminated-CAMEL Subscription Information (T-CSI) of subscriber B to MSC/VLR/SSPa.

3.

MSC/VLR/SSPa triggers the call to SCP b according to the T-CSI. After the call is triggered to SCP b, the subsequent fee deduction and CAP signaling interaction are the same as those in the calling process. For detailed process description, see step 2 through step 8 in the process of charging a calling party.

2-6

4.

SCP b delivers the Continue signaling to MSC/VLR/SSPa.

5.

MSC/VLR/SSPa sends an SRI request to HLR b again to request HLR b to return the Mobile Station Roaming Number (MSRN) of subscriber B.

6.

HLR b sends a Provide Roaming Number (PRN) request to MSC/VLR/SSP b to query the MSRN of subscriber B. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



7.

MSC/VLR/SSP b finds the MSRN of subscriber B and returns the MSRN to HLR b.

8.

HLR b returns the MSRN to MSC/VLR/SSP a.

9.

MSC/VLR/SSPa connects the call to MSC/VLR/SSP b.

10. 10. MSC/ MSC/VL VLR/ R/SS SSP P b connects the call to subscriber B. The call is connected. For the subsequent process, see step 10 through through step 20 in the process process of charging a calling calling party. Then the normal process of charging the called party in a call between two OCS subscribers is complete.

Exception Handling Process If an exception such as response timeout or network connection error occurs in the CBP, the SCP can determine whether to continue a call according to the related flags. If the SCP determines to continue the call, the SCP needs to record an offline CDR. Then the CBP can charge for the call according to the offline CDR.

2.2.2 Process of Charging a Call Between an OCS Subscriber and a Subscriber of Another Network This section describes the process of charging for a call between an OCS subscriber and a subscriber of another network from three aspects: calling process, called process, and exception handling process.

Process of Charging a Calling Party Figure 2-3 shows the normal process of charging the calling party in a call made by an OCS subscriber to a subscriber of another network. Figure 2-3 Normal process of charging the calling party in a call made by an OCS subscriber to a subscriber of another network MSC/VLR/SSPa

GMSC

External system

Subscriber A makes a call Trigger call Connect call


OCS subscri subscriber ber A makes makes a call to a subscribe subscriberr of another another network. network. The The call reaches reaches MSC/ MSC/ VLR/SSPa.

2.

MSC/VLR/SSPa determines that the called party is a subscriber of another network. Then MSC/VLR/SSPa triggers the call to the GMSC.

3.

The GMSC GMSC perform performss the subseq subsequent uent proce processing ssing and connec connects ts the call to to the called called party. party.

Issue 01 (2010-07-28)


2-7



NOTE

The process of charging the calling party of a call between an OCS subscriber and a subscriber of another network is the same as the process of charging a calling party described in 2.2.1 Process of Charging a Call Between Two OCS Subscribers. For detailed process description, see the process of charging a calling party described in 2.2.1 Process of Charging a Call Between Two OCS Subscribers.

Process of Charging a Called Party For the process of charging the called party in a call made by a subscriber of another network to an OCS subscriber, see the process of charging a called party in 2.2.1 Process of Charging a Call Between Two OCS Subscribers .

Exception Handling Process If an exception such as response timeout or network connection error occurs in the CBP, the SCP can determine whether to continue a call according to the related flags. If the SCP determines to continue the call, the SCP needs to record an offline CDR. Then the CBP can charge for the call according to the offline CDR.

2.3 Process of Charging a Forwarded Call The forwarded calls are classified into the calls that are forwarded conditionally and the calls that are forwarded unconditionally. The following sections describe the charging process of each type of forwarded call.

2.3.1 Process of Charging a Call That Is Forwarded Unconditionally The Call Forwarding Unconditional (CFU) process is invoked in either of the following cases: l

The call is forwarded unconditionally.

l

The called party is unreachable. When the called party is unreachable, the subscriber is in IMSI detached state on the HLR. After the MSC/VLR/SSP sends an SRI message to the HLR for the first time, the HLR returns the forward-to number.

The following sections describe the process of charging for a call that is forwarded unconditionally in the following scenarios: l

A call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a third OCS subscriber.

l

A call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a non-OCS subscriber.

l

A call made by a non-OCS subscriber to an OCS subscriber is unconditionally forwarded to another OCS subscriber.

Charging Process When a When a Call Made by an OCS Subscriber Sub scriber to Another OCS Subscriber Is Unconditionally Forwarded to a Third OCS Subscriber Figure 2-4 shows the charging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a third OCS subscriber. Assume that: 2-8


Issue 01 (2010-07-28)



l

Subscriber A, subscriber B, and subscriber C are OCS subscribers.

l

Subscriber A calls subscriber B, and the call is forwarded to subscriber C unconditionally.

l

Subscriber A, subscriber B, and subscriber C belong to the same SCP.

Figure 2-4 Charging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a third OCS subscriber MSC/VLR/SSP a

SCPa/b/c

CBPa/b/c

HLRb

HLRc

MSC/VLR/SSPc

Subscriber A makes a call Trigger call according to O-CSIa IDP CCR{Initial} CCA{Initial}


RRBE/AC/Continue SRI SRI ACK(O-CSIb

T-CSIb forward information)

、

、

Trigger call according to T-CSIb IDP CCR{Initial} CCA{Initial}


RRBE/AC/Continue Trigger call according to O-CSIb IDP CCR{Initial} CCA{Initial}


RRBE/AC/Continue SRI SRI ACK(T-CSIc) Trigger call according to T-CSIc IDP

CCR{Initial} CCA{Initial}


RRBE/AC/Continue SRI Send PRN request Return result

Query MSRN

SRI ACK(MSRN) Connect call

Issue 01 (2010-07-28)


2-9





2.

MSC/VLR/SSPa triggers the call according to the O-CSI of subscriber A and reports an IDP message to SCP a.

3.

SCPa sends a CCR{Initial} message to CBPa to initiate the authentication and budget requests.

4.

CBPa receives the authentication and budget requests from SCP a, performs authentication and budget, and then sends a CCA{Initial} message containing the authentication and budget results to SCPa.

5.

If the the aut authe hent ntic icat atio ion n is pass passed ed,, SCP SCPa sends the RRBE, AC, and Continue messages to prompt MSC/VLR/SSPa to connect the call.

6.

After After rec receiv eiving ing the the Cont Continu inuee messa message, ge, MSC/VL MSC/VLR/S R/SSP SPa sends an SRI message to HLR b through the MAP protocol.

7.

HLR b returns the O-CSI and T-CSI of subscriber B and the forward-to number to MSC/ VLR/SSPa.

8.

MSC/VLR/SSPa triggers the service according to the T-CSI of subscriber B and reports an IDP message to SCP b.

9.

SCP b sends a CCR{Initial} message to CBP b to initiate the authentication and budget requests.

10. If the the authen authentic ticati ation on is passe passed, d, CBP b sends a CCA{Initial} message to SCP b. Then SCP b delivers the RRBE, AC, and Continue messages to prompt MSC/VLR/SSPa to connect the call. 11. After receiving receiving the the Continue Continue message, message, MSC/VLR MSC/VLR/SSP /SSPa triggers the call forwarding process according to the information such as the O-CSI and forward-to number in the SRI message. Then MSC/VLR/SSPa reports an IDP message to SCP b. 12. After After recei receivin ving g the IDP IDP messag message, e, SCP b sends a CCR{Initial} message to CBP b to initiate the authentication and budget requests. 13. If the the authen authentic ticati ation on is passe passed, d, CBP b sends a CCA{Initial} message to SCP b. Then SCP b delivers the RRBE, AC, and Continue messages to prompt MSC/VLR/SSPa to connect the call. 14. After receiving receiving the Continu Continuee message, message, MSC/VLR/SS MSC/VLR/SSP Pa sends an SRI message to HLR c through the MAP protocol to obtain the information about subscriber C, for example, TCSI. 15. 15. MSC/ MSC/VL VLR/ R/SS SSP Pa triggers the service according to the T-CSI of subscriber C and reports an IDP message to SCP c. 16. After After recei receivin ving g the IDP IDP messag message, e, SCPc sends a CCR{Initial} message to CBPc to initiate the authentication and budget requests. 17. If the the authen authentic ticati ation on is passe passed, d, CBPc sends a CCA{Initial} message to SCPc. Then SCPc delivers the RRBE, AC, and Continue messages to prompt MSC/VLR/SSPa to connect the call. 18. 18. MSC/ MSC/VL VLR/ R/SS SSP Pa sends an SRI message to HLR c. 2-10


Issue 01 (2010-07-28)



19. HLRc sends a PRN request to MSC/VLR/SSPc to obtain the MSRN of subscriber C and returns the MSRN to MSC/VLR/SSPa for call connection. 20. After receiving receiving the the MSRN MSRN of subscrib subscriber er C, MSC/VLR MSC/VLR/SSP /SSPa connects the call. When the call ends, the charging process of this call is complete. NOTE

For the charging process after the call is connected, see 2.2 Process of Charging an Ordinary Call. MSC/VLR/SSPa sends the charging report and hang-up event to SCP a, SCP b, and SCPc.

Charging Process When a Call Made by an OCS Subscriber to Another OCS Subscriber Is Unconditionally Forwarded to a Non-OCS Subscriber Figure 2-5 shows the charging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a non-OCS subscriber. Assume that: l

Subscriber A and subscriber B are OCS subscribers.

l

Subscriber C is a non-OCS subscriber.

l


Issue 01 (2010-07-28)


2-11



Figure 2-5 Charging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a non-OCS subscriber MSC/VLR/SSPa

SCPa/b

CBPa/b

HLRb

HLRc

MSC/VLR/SSPc



RRBE/AC/Continue SRI SRI ACK(O-CSIb、T-CSIb、Forward information) Trigger call according to T-CSIb IDP CCR{Initial} CCA{Initial}





Query MSRN

SRI ACK（MSRN） Connect call

The charging process when a call made by an OCS subscriber to another OCS subscriber is unconditionally forwarded to a non-OCS subscriber is similar to the charging process as shown Proce ss When a Call Made by an OCS Subscriber to Another OCS Subscriber in Charging Process Is Unconditionally Forwarded to a Third OCS Subscriber. The only difference is that the call is not triggered according to the T-CSI of subscriber C because the call is forwarded to a non-OCS subscriber. The call is connected only after the MSRN of subscriber C is obtained through an FRN request. For the charging process after the call is connected, see 2.2 Process of Charging an Ordinary Call.

2-12


Issue 01 (2010-07-28)



Charging Process When a Call Made by a Non-OCS Subscriber to an OCS Subscriber Is Unconditionally Forwarded to Another OCS Subscriber Figure 2-6 shows the charging process when a call made by a non-OCS subscriber to an OCS subscriber is unconditionally forwarded to another OCS subscriber. Assume that: l

Subscriber A is a non-OCS subscriber.

l

Subscriber B and subscriber C are OCS subscribers.

l


Figure 2-6 Charging process when a call made by a non-OCS subscriber to an OCS subscriber is unconditionally forwarded to another OCS subscriber MSC/VLR/SSPa

SCPb/c

CBPb/c

HLRb

HLRc

MSC/VLR/SSPc

Subscriber A makes a call SRI SRI ACK(O-CSIb

T-CSIb Forward information)

、

、

Trigger call according to T-CSIb IDP CCR{Initial} CCA{Initial}




RRBE/AC/Continue SRI SRI ACK(T-CSIc) Trigger call according to T-CSIc IDP CCR{Initial} CCA{Initial}



Query MSRN

SRI ACK(MSRN) Connect call

Issue 01 (2010-07-28)


2-13



The charging process when a call made by a non-OCS subscriber to an OCS subscriber is unconditionally forwarded to another OCS subscriber is similar to the charging process as shown Proce ss When a Call Made by an OCS Subscriber to Another OCS Subscriber in Charging Process Is Unconditionally Forwarded to a Third OCS Subscriber. The only difference is that the call is not triggered according to the O-CSI of subscriber A because the call is made by a nonOCS subscriber. MSC/VLR/SSP a sends an SRI message to obtain the information such as OCSI, T-CSI, and forward-to number of subscriber B and then triggers the call directly. For the charging process after the call i s connected, see 2.2 Process of Charging an Ordinary Call.

2.3.2 Process of Charging a Call That Is Forwarded Conditionally The call forwarding conditional (CFC) process is invoked in any of t he following cases: l

The call is forwarded on no answer.

l

The call is forwarded on busy.

l

The called party is unreachable. When the called party is unreachable, the called party is in IMSI attached state on the HLR.

The following sections describe the process of charging for a call that is forwarded on busy from the following aspects: l

A call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a third OCS subscriber.

l

A call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a non-OCS subscriber.

l

A call made by a non-OCS subscriber to an OCS subscriber is conditionally forwarded to another OCS subscriber. subscriber.

Charging Process When a Call Made by an OCS Subscriber to Another OCS Subscriber Is Conditionally Forwarded to a Third OCS Subscriber Figure 2-7 shows the charging process when a call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a third OCS subscriber. Assume that:

2-14

l

Subscriber A, subscriber B, and subscriber C are OCS subscribers.

l

Subscriber A calls subscriber B, and the call is forwarded to subscriber C conditionally.

l

Subscriber A, subscriber B, and subscriber C belong to the same SCP.


Issue 01 (2010-07-28)



Figure 2-7 Charging process when a call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a third OCS subscriber MSC/VLR/SSPa

SCPa/b/c

CBPa/b/c

HLRb

MSC/VLR/SSPb

HLRc

MSC/VLR/SSPc

Subscriber A makes a call Trigger call according to O-CSIa IDP CCR{Initial}


CCA{Initial} RRBE/AC/Continue SRI

SRI ACK(T-CSIb、location of subscriber B) Trigger call according to T-CSIb IDP CCR{Initial} CCA{Initial}


RRBE/AC/Connect SRI Send PRN request Return result

Query MSRN

SRI ACK(MSRNb) Connect call Trigger call according to O-CSI b IDP CCR{Initial}

CCA{Initial}


RRBE/AC/Connect SRI SRI ACK(T-CSIc) Trigger call according to T-CSI c IDP CCR{Initial}

CCA{Initial}


RRBE/AC/Connect SRI

Send PRN request Return result

Query MSRN

SRI ACK(MSRNc) Connect call

Issue 01 (2010-07-28)


2-15





2.

MSC/VLR/SSPa triggers the call according to the O-CSI of subscriber A and reports an IDP message to the SCP a.

3.

SCPa sends a CCR{Initial} message to CBPa to initiate the authentication and budget requests.

4.

CBPa receives the authentication and budget requests from SCP a, performs authentication and budget, and then sends a CCA{Initial} message containing the authentication and budget results to SCPa.

5.

If the the aut authe hent ntic icat atio ion n is pass passed ed,, SCP SCPa sends the RRBE, AC, and Continue messages to prompt MSC/VLR/SSPa to connect the call.

6.

After After rec receiv eiving ing the the Cont Continu inuee messa message, ge, MSC/VL MSC/VLR/S R/SSP SPa sends an SRI message to HLR b through the MAP protocol.

7.

HLR b returns the T-CSI and location of subscriber B to MSC/VLR/SSPa.

8.

MSC/VLR/SSPa triggers the service according to the T-CSI of subscriber B and reports an IDP message to SCP b.

9.

SCP b sends a CCR{Initial} message to CBP b to initiate the authentication and budget requests.

10. If the the authen authentic ticati ation on is passe passed, d, CBP b sends a CCA{Initial} message to SCP b. Then SCP b delivers the RRBE, AC, and Connect messages to prompt MSC/VLR/SSPa to connect the call. 11. After receiving receiving the Connec Connectt message, message, MSC/VLR/SS MSC/VLR/SSP Pa delivers an SRI message to HLR b to obtain the MSRN of subscriber B. 12. HLR b sends a PRN request to MSC/VLR/SSP b to obtain the MSRN of subscriber B and returns the MSRN to HLR b. 13. HLR b returns the MSRN of subscriber B t o MSC/VLR/SSPa. Then MSC/VLR/SSPa connects the call to MSC/VLR/SSP b according to the MSRN. 14. 14. MSC/ MSC/VL VLR/ R/SS SSP P b triggers the CFC service according to the conditions such as the O-CSI and busy situation of subscriber B and reports an IDP message to SCP b. 15. SCP b sends a CCR{Initial} message to CBP b to initiate the authentication and budget requests. 16. If the the authen authentic ticati ation on is passe passed, d, CBP b sends a CCA{Initial} message to SCP b. Then SCP b delivers the RRBE, AC, and Connect messages to prompt MSC/VLR/SSP b to connect the call. 17. After receiving receiving the Connec Connectt message, message, MSC/VLR/SS MSC/VLR/SSP P b sends an SRI message to HLR c of subscriber C through the MAP protocol. 18. HLRc returns the T-CSI and location of subscriber C t o MSC/VLR/SSP b. 19. 19. MSC/ MSC/VL VLR/ R/SS SSP P b triggers the service according to the T-CSI of subscriber C and reports an IDP message to SCP c. 20. After After recei receivin ving g the IDP IDP messag message, e, SCPc sends a CCR{Initial} message to CBPc to initiate the authentication and budget requests. 2-16


Issue 01 (2010-07-28)



21. If the the authen authentic ticati ation on is passe passed, d, CBPc sends a CCA{Initial} message to SCPc. Then SCPc delivers the RRBE, AC, and Continue messages to prompt MSC/VLR/SSP b to connect the call. 22. After receiving receiving the Continu Continuee message, message, MSC/VLR/SS MSC/VLR/SSP P b delivers an SRI message to HLR c to obtain the MSRN of subscriber C. 23. HLRc sends a PRN request to MSC/VLR/SSPc to obtain the MSRN of subscriber C and returns the MSRN to HLR c. 24. HLRc returns the MSRN of subscriber C to MSC/VLR/SSP b. Then MSC/VLR/SSP b connects the call to MSC/VLR/SSPc according to the MSRN. When the call ends, the charging process of this call is complete. NOTE

For the charging process after the call is connected, see 2.2 Process of Charging an Ordinary Call. When either of the calling party or called party ends the call, MSC/VLR/SSP MSC/VLR/ SSP a sends the charging report and hang-up event to SCP a and SCP b, and MSC/VLR/SSP b sends the charging report, and hang-up event to SCP b and SCPc. Then the CBP node of each subscriber performs debiting.

Charging Process When a Call Made by an OCS Subscriber to Another OCS Subscriber Is Conditionally Forwarded to a Non-OCS Subscriber Figure 2-8 shows the charging process when a call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a non-OCS subscriber. Assume that: l


l

Subscriber C is a non-OCS subscriber.

l

Subscriber A calls subscriber B, and the call is forwarded to subscriber C conditionally.

Issue 01 (2010-07-28)


2-17



Figure 2-8 Charging process when a call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a non-OCS subscriber MSC/VLR/SSPa

SCPa/b

CBPa/b

HLRb

MSC/VLR/SSPb

HLRc

MSC/VLR/SSPc



RRBE/AC/Continue SRI SRI ACK(T-CSIb、location of subscriber B) Trigger call according to T-CSIb IDP CCR{Initial} CCA{Initial}


RRBE/AC/Connect SRI Send PRN request Query MSRN

Return result SRI ACK(MSRNb) Connect call

Trigger call according to O-CSIb IDP CCR{Initial}

CCA{Initial}


RRBE/AC/Connect SRI


Query MSRN


The charging process when a call made by an OCS subscriber to another OCS subscriber is conditionally forwarded to a non-OCS subscriber is similar to the charging process as shown i n Charging Process When a Call Made by an OCS Subscriber to Another OCS Subscriber Is Conditionally Forwarded to a Third OCS Subscriber. The only difference is that the call is not triggered according to the T-CSI of subscriber C because the call is forwarded to a nonOCS subscriber. The call is connected only after the MSRN of subscriber C is obtained through an FRN request. For the charging process after the call is connected, see 2.2 Process of Charging an Ordinary Call. 2-18


Issue 01 (2010-07-28)



Charging Process When a Call Made by a Non-OCS Subscriber to an OCS Subscriber Is Conditionally Forwarded to Another OCS Subscriber Figure 2-9 shows the charging process when a call made by a non-OCS subscriber to an OCS subscriber is conditionally forwarded to another OCS subscriber. Assume that: l

Subscriber A is a non-OCS subscriber.

l

Subscriber B and subscriber C are OCS subscribers.

l


Figure 2-9 Charging process when a call made by a non-OCS subscriber to an OCS subscriber is conditionally forwarded to another OCS subscriber MSC/VLR/SSPa

SCPb/c

CBPb/c

HLRb

MSC/VLR/SSPb

HLRc

MSC/VLR/SSPc

Subscriber A makes a call SRI SRI ACK(T-CSIb location of subscriber B) 、

Trigger call according to T-CSI b IDP CCR{Initial} CCA{Initial}


RRBE/AC/Connect SRI Send PRN request Return result

Query MSRN

SRI ACK(MSRNb) Connect call Trigger call according to O-CSI b IDP CCR{Initial}

CCA{Initial}


RRBE/AC/Connect SRI SRI ACK(T-CSIc) Trigger call according to T-CSIc IDP CCR{Initial}

CCA{Initial}


RRBE/AC/Connect SRI


Query MSRN


Issue 01 (2010-07-28)


2-19



The charging process when a call made by a non-OCS subscriber to an OCS subscriber is conditionally forwarded to another OCS subscriber is similar to the charging process as shown Proce ss When a Call Made by an OCS Subscriber to Another OCS Subscriber in Charging Process Is Conditionally Forwarded to a Third OCS Subscriber. The only difference is that the call is not triggered according to the O-CSI of subscriber A because the call is made by a non-OCS subscriber. MSC/VLR/SSPa sends an SRI message to directly obtain the information such as the T-CSI and location of subscriber B. For the charging process after the call is connected, see 2.2 Process of Charging an Ordinary Call.

2.4 Reference This section describes the terms used in the call processes. The Customized Applications for Mobile Network Enhanced Logic (CAMEL) is a set of GSM standards used in the GSM core network. The standards allow carriers to define certain services superior to the ordinary GSM service. The architecture of the CAMEL is based on the European Telecommunications Standards Institute (ETSI) of the mobile intelligent service. The call-related 3GPP CAMEL phase 3 series standards are as follows:

2-20

l

3GPP TS 29.078 V4.4.0 (2002-03) Release 4

l

3GPP TS 22.078 version 4.0.0 (2000-10) Release 4

l

3GPP TS 23.078 V4.4.0 (2002-03) Release 4


Issue 01 (2010-07-28)


3 SMS Charging Processes

3

SMS Charging Processes

About This Chapter

3.1 Overview An SMS char ging ging process r efers efers to the process in which the OCS system charges a subscriber when the subscriber subscriber sends or receives a short message. 3.2 Process of of Charging an Ordinary Short Message Through DCC The OCS system system supports the following function: The SMSC sends a Diameter protocol message to the CBP for for charging, that is, the CBP charges an ordinary short message through the DCC. 3.3 Process of Charging an Ordinary Short Message Based on SMPP+ In this solution solution GFEP communicates with SMSC via SMPP+ protocol and communicates with CBP via Diameter Diameter interface to achieve SMS charging. 3.4 Process of Charging an Ordinary Short Message Based on CAMEL3 The OCS system system supports the process of charging an ordinary short message based on CAMEL3. The MSC/VLR/SSP MSC/VLR/SSP sends a short message charging request to the corresponding SCP according to the subscri ption ption information information (CSI) of a subscriber. Then, the SCP SCP sends sends a DCC short message to the CBP for for charging. 3.5 Reference Referenc e This section describes the terms terms used in the SMS charging processes.

Issue 01 (2010-07-28)


3-1



3.1 Overview An SMS charging process refers to the process in which the OCS system charges a subscriber when the subscriber sends or receives a short message. The following sections describe the SMS charging processes of the following protocols: l

DCC

l

SMPP+

l

CAMEL3

The following sections describe each SMS charging process in detail.

3.2 Process of Charging an Ordinary Short Message Through DCC The OCS system supports the following function: The SMSC sends a Diameter protocol message to the CBP for charging, that i s, the CBP charges an ordinary short message through the DCC. NOTE

SMSC needs to support Huawei extension diameter protocol that is based on the 3GPP standard.

Figure 3-1 shows the process of charging an ordinary short message through DCC. Figure 3-1 Process of charging an Ordinary short message through DCC MSC/VLR/SSP Send short message

SMSC

CBP

Initiate SMS charging request CCR{Event} CCA{Event}

Authentication , rating and fee deduction

Deliver to called party CCR{Event}

CCA{Event}

Confirm charging/ Refund

Return result Return result

The process is described as follows: 3-2


Issue 01 (2010-07-28)



1.

A subscriber subscriber sends a short short message. message. The The chargin charging g request request of the short short message message reaches reaches the the MSC/VLR/SSP.

2.

The MSC/VL MSC/VLR/S R/SSP SP send sendss a char chargin ging g reque request st to the SMSC. SMSC.

3.

The SMSC SMSC sends sends a CCR{Even CCR{Event} t} message message to the CBP to initiate initiate a charging charging reque request. st.

4.

The CBP CBP perform performss authentic authentication ation,, rating, rating, and and charging charging,, and sends a CCA{Even CCA{Event} t} message message to return the processing result to the SMSC.

5.

After receiving receiving the result result from from CBP, CBP, the SMSC delive delivers rs the short message message to the the called called party.

6.

The SMSC SMSC sends sends a CCR{Even CCR{Event} t} message message to the CBP for for chargi charging ng confirm confirmation ation.. If fee refund is required, the CBP refunds the fee. For the detailed process, see the dotted box in red in the preceding figure.

7.

After confirming confirming the chargin charging g or refun refunding ding the the fee, fee, the CBP CBP sends sends a CCA{Ev CCA{Event} ent} messa message ge containing the processing result to the SMSC.

8.

The SMSC SMSC retur returns ns the charging charging result result to the the MSC/VL MSC/VLR/SSP R/SSP and the MSC/VL MSC/VLR/SS R/SSP P returns the charging result to the calling party. Then the process of charging for the short message through DCC protocol is complete.

3.3 Process of Charging an Ordinary Short Message Based on SMPP+ In this solution GFEP communicates with SMSC via SMPP+ protocol and communicates with CBP via Diameter interface to achieve SMS charging. Figure 3-2 shows the normal process of charging for an ordinary short message based on SMPP +. Figure 3-2 Process of charging for an ordinary short message based on SMPP+ MSC/VLR/SSP

SMSC

GFEP

CBP

Send short message Initiate SMS charging request SMPP+:Initiate SMS charging request CCR{Event} CCA{Event}

Authentication, rating and fee deduction

Return result Return result Return result

Deliver to called party Confirm charging request/Refund request CCR{Event} CCA{Event}

Confirm charging/ Refund

Return result

Issue 01 (2010-07-28)


3-3




A subscriber subscriber sends a short short message. message. The The chargin charging g request request of the short short message message reaches reaches the the MSC/VLR/SSP.

2.

The MSC/VL MSC/VLR/S R/SSP SP send sendss a char chargin ging g reque request st to the SMSC. SMSC.

3.

The SMSC forwards forwards the charging charging request request to to the the GFEP GFEP throug through h SMPP+. SMPP+.

4.

The GFEP GFEP conver converts ts the charging charging reque request st to a DCC message message,, and then sends sends a CCR{Event CCR{Event} } message to the CBP to initiate a charging request.

5.

The CBP CBP charges charges for the the short short message message and sends sends a CCA{Ev CCA{Event} ent} messag messagee to return return the the processing result to the GFEP. GFEP.

6.

The GFEP GFEP retur returns ns the the char chargin ging g resul resultt to the SMSC. SMSC.

7.

The SMSC returns the the charging result to the MSC/VLR/SSP. The MSC/VLR/SSP returns the charging result to the calling party.

8.

The SMSC SMSC checks checks the return return result result.. If the the charging charging is successf successful, ul, the SMSC sends a short short message to the called party. If the short message is successfully sent, the SMSC sends a short message to the GFEP for confirmation. If the short message is unsuccessfully sent, the SMSC sends a fee refund request to the GFEP.

9.

The GFEP GFEP sends a CCR{Even CCR{Event} t} message message to the the CBP for charging charging confir confirmatio mation n or fee refund. NOTE

When a short message refund is required, the SMSC sends a refund request to request the CBP to perform the refund operation. operation. The refund refund process process is similar to the the process of charging for a short message. For details, see the process in the dotted box in red, as shown in Figure 3-2.

10. After confir confirming ming the chargin charging g or refunding refunding the fee, fee, the CBP sends sends a CCA{Event} CCA{Event} message message containing the processing result to the GFEP. 11. The GFEP GFEP returns returns the charging charging result result to the SMSC. SMSC. Then the process process of charging charging for the the short message based on the SMPP+ protocol is complete.

3.4 Process of Charging an Ordinary Short Message Based on CAMEL3 The OCS system supports the process of charging an ordinary short message based on CAMEL3. The MSC/VLR/SSP sends a short message charging request to the corresponding SCP according to the subscription information (CSI) of a subscriber. Then, the SCP sends a DCC short message to the CBP for charging.

Normal Process Figure 3-3 shows the process of charging for an ordinary short message based on CAMEL3.

3-4


Issue 01 (2010-07-28)



Figure 3-3 Process of charging for an ordinary short message based on CAMEL3 MSC/VLR/SSP Send short message

SMSC

SCP

CBP

IintialDP SMS RequestReportSMSEvent CCR{Initial} CCA{Initial}

Request charging

ContinueSMS Connect short message Return result

Deliver to called party

EventReportSMS

CCR{Terminate} CCA{Terminate}

Confirm charging

ReleaseSMS


A subscribe subscriberr sends sends a short short message. message. The upstre upstream am chargin charging g request request of the short short message message reaches the MSC/VLR/SSP.

2.

The MSC/V MSC/VLR/SS LR/SSP P sends sends an an InitialD InitialDP P SMS SMS message message to the the SCP to request request charging. charging.

3.

The SCP returns returns a RequestRep RequestReportS ortSMSEve MSEvent nt message message to the the MSC/VLR MSC/VLR/SSP /SSP..

4.

After receiving receiving the request request,, the SCP SCP sends sends a CCR{Ini CCR{Initial} tial} message message to the the CBP to initiate initiate a charging request.

5.

The CBP prededucts prededucts the short short message message fee fee and and sends sends a CCA{Initi CCA{Initial} al} message message to return return the processing result to the SCP. SCP.

6.

The SCP SCP retur returns ns Conti Continue nueSMS SMS messag messagee to the the MSC/V MSC/VLR/ LR/SS SSP. P.

7.

After receiving receiving the Continu ContinueSMS eSMS message, message, the the MSC/VLR MSC/VLR/SSP /SSP delivers delivers a message message to prompt the SMSC to connect connect the short message.

8.

The SMSC SMSC returns returns result result to MSC/VLR/ MSC/VLR/SSP SSP and deliver deliverss the short short messa message ge to the the called called party.

9.

After receiving receiving the reques request, t, the MSC/VLR/SS MSC/VLR/SSP P sends sends an EventRepor EventReportSMS tSMS message message to the SCP to confirm the charging.

10. The SCP sends sends a CCR{Terminat CCR{Terminate} e} message message to the CBP to initia initiate te a charging charging confirmat confirmation ion request. 11. The CBP confirms confirms the chargi charging ng and sends sends a CCA{Terminat CCA{Terminate} e} message message to return return the processing result to the SCP. SCP. 12. After receiv receiving ing a DCC message message indicating indicating that that the fee deduction deduction is successf successful, ul, the SCP delivers the ReleaseSMS message to the MSC/VLR/SSP. Then the process of charging for the short message based on the CAMEL3 protocol is complete. Issue 01 (2010-07-28)


3-5



NOTE

Since standard CAMEL3 protocol does not support MT flow, OCS CAMEL3 SMS solution does not support SMS MT charging either.

Exception Handling Process If the CBP fails to deduct the short message fee, the SCP delivers a message to release the short message according to the result code returned by the CBP.

3.5 Reference This section describes the terms used in the SMS charging processes. The Short Message Peer to Peer (SMPP) protocol is an open message transfer protocol. Through this protocol, the entities beyond the wireless network, for example, SMS entity, can i nteract with the SMSC. The unmovable entities that submit short messages to the SMSC and receive the short messages delivered by the SMSC are called extended SMS entities. The basic Diameter protocol is an Authentication, Authorization and Accounting (AAA) protocol based on the AAA AAA frame. The application application protocol extended extended based on the basic Diameter protocol is the Diameter Credit Control (DCC) protocol. The DCC protocol defines the charging mechanism for prepaid subscribers and uses credit control to achieve the charging based on sessions and events. events. Therefore, the the requirement for charging charging prepaid subscribers subscribers is met. The short message-related 3GPP CAMEL phase 3 series standards are as follows:

3-6

l

3GPP TS 29.078 V4.4.0 (2002-03) Release 4

l


l

3GPP TS 23.078 V4.4.0 (2002-03) Release 4


Issue 01 (2010-07-28)


4 Activation Processes

4

Activation Processes

About This Chapter

4.1 Overview The initial state state of a new prepaid subscriber is idle. The corresponding numbers can be used after the subscriber subscriber is activated. 4.2 Process of of Activating an Account by Making the First Call When a subscriber subscriber in Idle state dials any number, the system activates the subscriber automatically, automatically, sends the activation response message via short message to t he subscriber, and plays announcements announcements to the subscriber. 4.3 Process of of Activating an Account Through the WebService Interface After an external exte rnal system receives an activation request from a subscriber, the external system invokes the WebService WebService interface through the BMP and activates the account of the subscriber on the CBP. This activation process is called the process of activating an account through the WebService interface. i nterface. 4.4 Process of of Activating an Account on the SMAP In this process, process, an operator handles the request of activating an account on the SMAP after receiving the request. 4.5 Process of of Activating an an Account Through IVR This section describes the process of activating an account through IVR. 4.6 Process of Activating an Account by Sending a Short Message This section describes the process of activating an account by sending a short message. 4.7 Process of Activating an Account by Recharging the Account by Using a Recharge Card This section describes the process of activating an account by recharging the account by using a recharge card. 4.8 Reference This section describes the terms used in the activation processes.

Issue 01 (2010-07-28)


4-1



4.1 Overview The initial state of a new prepaid subscriber is idle. The corresponding numbers can be used after the subscriber is activated. The system provides several ways to activate the subscriber: l

Activate subscribers by first call by dialing any number.

l

The OCS provides a WebService interface interface to activate subscribers. CRM system can send the WebService command to activate subscribers.

l

The OCS provides the GUI to help activate subscribers, and allows operators to activate subscribers on the SMAP.

l

An idle subscriber can dial the access code of the IVR process to activate the personal account.

l

A subscriber can send a short message to activate the personal account through SMPP+ or CAMEL3.

l

A subscriber can dial the access code of the IVR process to trigger the activation process to activate the personal account.

4.2 Process of Activating an Account by Making the First Call When a subscriber in Idle state dials any number, the system activates the subscriber automatically, sends the activation response message via short message to the subscriber, and plays announcements announcements to the subscriber. Figure 4-1 shows the process of activating an account by making the first call.

4-2


Issue 01 (2010-07-28)



Figure 4-1 Process of activating an account by making the first call MSC/VLR/SSP Subscriber dials IVR access code

CBP

SCP

IDP RRBE CCR{Initial} Authenticate CCA{Initial}

Deliver system notification voice Select a language type

Deliver system notification voice

Send the language type CCR{Initial} Activate and recharge CCA{Initial} CCR{Terminate}

CCA{Terminate}

Confirm recharge and write CDR

CCR{Terminate}

Deliver activation result


CCA{Terminate}


A subscrib subscriber er dials dials the the IVR IVR access access code. code. The call reaches reaches the the MSC/VLR/ MSC/VLR/SSP. SSP.

2.

The MSC/VLR MSC/VLR/SSP /SSP of the visited visited area area reports reports an an IDP message message to trigge triggerr the call call to the SCP of the home area.

3.

The SCP SCP deliver deliverss an RRBE RRBE message message to the MSC/VLR/SS MSC/VLR/SSP P accordin according g to the the service service logic logic to request the dynamic configuration of the EDP.

4.

The SCP SCP sends sends a CCR{Init CCR{Initial} ial} message message to request request the the CBP to to authentic authenticate ate the the subscrib subscriber er state.

5.

After performin performing g the authen authenticat tication, ion, the the CBP sends sends a CCA{Initia CCA{Initial} l} message message contai containing ning the authentication result to the SCP.

6.

The SCP SCP also also delivers delivers the first first activat activation ion voice voice to the MSC/VLR MSC/VLR/SSP /SSP according according to the authentication result returned by the CBP. Then the MSC/VLR/SSP plays the first activation voice to the subscriber.

7.

The subscr subscriber iber chooses chooses a language language type type accor according ding to voice voice that that is played. played. The language type is the same as the language type used in the result notification voice or short message in the activation.

Issue 01 (2010-07-28)


4-3



8.

The MSC/VL MSC/VLR/S R/SSP SP send sendss the the langu language age type type to the the SCP. SCP.

9.

When recei receiving ving the the authentic authentication ation result result indicating indicating that that the subscriber subscriber is not activat activated ed from from the CBP, the SCP delivers a CCR{Initial} message to the CBP for activation and recharge.

10. The CBP activates and and pre-recharges pre-recharges the account of the subscriber, subscriber, and then returns returns a CCA {Initial} message to the SCP. 11. The SCP sends sends a CCR{Terminate CCR{Terminate} } message to the CBP accordi according ng to the processing processing result result returned by the CBP to confirm the recharge. 12. The CBP confirms confirms the recha recharge rge and sends sends a CCA{Terminate CCA{Terminate} } message message containing containing the processing result to the SCP. SCP. 13. The SCP sends sends a CCR{Term CCR{Terminate inate} } message message to request request the CBP CBP to write a CDR. CDR. 14. The CBP writes writes a CDR and sends sends a CCA{Terminat CCA{Terminate} e} message message containing containing the proces processing sing result to the SCP. 15. The SCP deliver deliverss a notification notification voice voice to the MSC/VLR/SSP MSC/VLR/SSP accor according ding to the processi processing ng result returned by the CBP. 16. The MSC/VLR/SSP MSC/VLR/SSP plays the activation result voice to the subscriber. subscriber. Then Then the process process of activating an account by making the first call is complete. NOTE

Due to needing to play announcement or send short message in activation flow, the network operator needs to load the corresponding announcement and the short message center needs to support SMPP protocol.

4.3 Process of Activating an Account Through the WebService Interface After an external system receives an activation request from a subscriber, the external system invokes the WebService interface through the BMP and activates the account of the subscriber on the CBP. This activation process is called the process of activating an account through the WebService interface. Figure 4-2 shows the normal process of activating an account through the WebService interface. interface. Figure 4-2 Process of activating an account through the WebService interface External system Activation request

BMP

CBP

Invoke the WebService interface to activate Activation request

Return activation result



Activate



Issue 01 (2010-07-28)


1.


A subscribe subscriberr sends sends an activa activation tion reque request st to the the OCS system system through through an an external external system. system. The external system refers to a system that accesses the OCS system externally. The external system is a foreground that can process subscriber requests.

2.

The extern external al system system recei receives ves the the activatio activation n request request from from the the subscribe subscriberr and forwards forwards the the activation request to the BMP through the WebService interface.

3.

The BMP forwa forwards rds the activ activati ation on requ request est to the the CBP. CBP.

4.

The CBP CBP activate activatess the account account of the subscr subscriber iber and and returns returns the activati activation on result result to the BMP.

5.

The BMP returns returns the activation activation result result to to the externa externall system, system, and the the external external system system returns returns the activation result to the subscriber. Then the process of activating an account through the WebService interface is complete.

4.4 Process of Activating an Account on the SMAP In this process, an operator handles the request of activating an account on the SMAP after receiving the request. Figure 4-3 shows the normal process of activating an account on the SMAP. Figure 4-3 Process of activating an account on the SMAP SMAP Activation request

BMP

CBP

Invoke the WebService interface to activate Activation request




Activate


A subsc subscrib riber er initia initiates tes an activa activatio tion n requ request est..

2.

After the request request is sent sent to the SMAP, SMAP, the SMAP sends the request request to the BMP through through the WebService interface.

3.

The BMP forwa forwards rds the activ activati ation on requ request est to the the CBP. CBP.

4.

The CBP CBP activate activatess the account account of the subscr subscriber iber and and returns returns the activati activation on result result to the BMP.

5.

The BMP BMP returns returns the the activati activation on result result to the SMAP, SMAP, and the the SMAP SMAP returns returns the activati activation on result to the subscriber. Then the process of activating an account on the SMAP is complete.

4.5 Process of Activating an Account Through IVR This section describes the process of activating an account through IVR. Issue 01 (2010-07-28)


4-5



Normal Process Figure 4-4 shows the normal process of activating an account through IVR. Figure 4-4 Normal process of activating an account through IVR MSC/VLR/SSP Subscriber dials IVR access code

CBP

SCP

IDP RRBE CCR{Event} Authenticate CCA{Event}

Deliver system notification voice

Deliver system notification voice CCR{Initial} Activate and recharge CCA{Initial} CCR{Terminate}



CCA{Terminate}


The process is described as follows:

4-6

1.


2.


3.


4.

The SCP SCP sends sends a CCR{Eve CCR{Event} nt} message message to request request the CBP CBP to authen authenticat ticatee the subscr subscriber iber state.

5.

After performin performing g the authen authentica tication, tion, the the CBP sends a CCA{Even CCA{Event} t} message message contai containing ning the the authentication result to the SCP.

6.

The SCP SCP also also delivers delivers the first first activat activation ion voice voice to the MSC/VLR MSC/VLR/SSP /SSP according according to the authentication result returned by the CBP. Then the MSC/VLR/SSP plays the first activation voice to the subscriber.

7.

The SCP SCP deliver deliverss a CCR{Ini CCR{Initial} tial} message message to the CBP CBP for for activat activation ion and and rechar recharge. ge.

8.

The CBP activates activates and and pre-rec pre-recharg harges es the accou account nt of the subscriber subscriber,, and then then returns returns a CCA {Initial} message to the SCP.


Issue 01 (2010-07-28)


9.


The SCP SCP sends sends a CCR{Termina CCR{Terminate} te} message message to the CBP accor according ding to to the processin processing g result result returned by the CBP to confirm the recharge and write a CDR.

10. The CBP confirm confirmss the recharge recharge and and writes writes a CDR, then the the CBP sends sends a CCA{Terminate CCA{Terminate} } message containing the processing result to the SCP. 11. The SCP deliver deliverss a notification notification voice voice to the MSC/VLR/SSP MSC/VLR/SSP accor according ding to the processi processing ng result returned by the CBP. 12. The MSC/VLR/SSP MSC/VLR/SSP plays the activation result voice to the subscriber. subscriber. Then Then the process process of activating an account through IVR is complete.

Exception Handling Process If the DCC message that is sent by the SCP to the CBP for activation fails to be processed, the SCP delivers the activation failure voice to the MSC/VLR/SSP according to the processing result returned by the CBP.

4.6 Process of Activating an Account by Sending a Short Message This section describes the process of activating an account by sending a short message.

Process of Activating an Account by Sending a Short Message Through SMPP+ Figure 4-5 shows the normal process of activating an account by sending a short message through SMPP+.

Issue 01 (2010-07-28)


4-7



Figure 4-5 Normal process of activating an account by sending a short message through SMPP+

MSC/VLR/SSP Subscriber sends short message

SMSC

SMS charging request

GFEP

SMPP+: SMS charging request

SC P

CBP

RCOMM: SMS charging request CCR{Event} CCA{Event}

Charging request

Determine according to return result CCR{Initial}

CCA{Initial} CCR{Terminate} CCA{Terminate}

Activate and recharge Confirm recharge and write CDR

CCR{Event} CCA{Event} Return result

Charging request

Return result

Connect short message

Return result and release short message

Return result and release short message

Release short message


4-8

1.

A subscribe subscriberr sends sends a short short message. message. The upstre upstream am chargin charging g request request of the short short message message reaches the MSC/VLR/SSP.

2.

The MSC/ MSC/VLR VLR/SS /SSP P forwa forwards rds the the chargi charging ng reque request st to the the SMSC. SMSC. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



3.


4.

The GFEP GFEP converts converts the charg charging ing request request to an RCOMM message message and and sends sends the the RCOMM RCOMM message to the SCP.

5.

After receiving receiving the RCOMM RCOMM messag message, e, the SCP sends sends a CCR{Event CCR{Event} } message message to to the CBP for charging.

6.

After receiving receiving the chargin charging g request, request, the CBP CBP determine determiness whether whether the the subscrib subscriber er is in in idle state and sends a CCA{Event} message containing the result to the SCP.

7.

If the CBP CBP returns returns the the result result that that the subscr subscriber iber is in idle state, state, the SCP SCP sends sends a CCR{Initial CCR{Initial} } message to the CBP for first activation and recharge.

8.

The CBP CBP activate activatess and pre-rech pre-recharge argess the accou account nt of the the subscribe subscriberr and returns returns the processing result to the SCP. SCP.

9.

The SCP SCP sends sends a CCR{Termina CCR{Terminate} te} message message to the CBP accor according ding to to the processin processing g result result returned by the CBP to confirm the recharge and write a CDR. NOTE

After step 9 is performed, the subscriber is activated. The option of continuing to send this short message or releasing this short message after the subscriber is activated is configurable. When the option of continuing to send this message is configured, the operatio ns in the dotted red box in Figure 4-5 are performed. Otherwise, the SCP releases this short message. Steps 10 through 12 describe the operations in the dotted red box in Figure 4-5.

10. After receiving receiving the message indicating that the subscriber subscriber is activated successfully, the SCP sends a CCR{Event} message to request the CBP to charge the short message. 11. The CBP charges charges the short short message message and sends sends a CCA{Event} CCA{Event} message message containing containing the processing result to the SCP. SCP. 12. The SCP returns returns the processing processing result result to the GFEP, GFEP, the GFEP returns returns the processin processing g result to the SMSC, SMSC, and the the SMSC sends the short message to the subscriber. Then the process of activating an account by sending a short message through SMPP+ is complete.

Process of Activating an Account by Sending a Short Message Through CAMEL3 Figure 4-6 shows the normal process of activating an account by sending a short message through CAMEL3.

Issue 01 (2010-07-28)


4-9



Figure 4-6 Normal process of activating an account by sending a short message through CAMEL3 MSC/VLR/SSP

SCP

CBP

Subscriber sends short message InitialDP SMS RequestReportSMSEvent CCR{Initial} CCA{Initial}

Charging request

Determine according to return result CCR{Initial} CCA{Initial} CCR{Terminate} CCA{Terminate}

Activate and recharge



Charging request

ContinueSMS Connect short message EventReport SMS CCR{Terminate}

CCA{Terminate}

Confirm charging

ReleaseSMS Release short message

For the description of the process, see 3.4 Process of Charging an Ordinary Short Message Based on CAMEL3 and Process of Activating an Account by Sending a Short Message Through SMPP+. The operations in the dotted red box in Figure 4-6 are performed when the option of continuing to send the short message is configured after the SCP receives the message indicating that the CBP activates the account successfully. If the option of releasing the short message is configured after the account of the subscriber is activated, the operations under the dotted red box are performed.

4-10


Issue 01 (2010-07-28)



4.7 Process of Activating an Account by Recharging the Account by Using a Recharge Card This section describes the process of activating an account by recharging the account by using a recharge card. Figure 4-7 shows the normal process of activating an account by recharging the account by using a recharge card. Figure 4-7 Process of Activating an Account by Recharging the Account by Using a Recharge Card MSC/VLR/SSP Subscriber dials IVR access code

SCP

CBP

VC

IDP RRBE

CCR{Event} CCA{Event}

Authenticate

System plays voice to interact with subscriber Subscriber chooses to recharge Verification is passed, and system continue to play voice to i nteract with subscriber

Blacklist verification

Enter recharged number and recharge card password Execute recharge card authentication request Authenticate Execute authentication response CCR{Initial}

CCA{Initial}

Debit and reward

Execute recharge resetting request Execute recharge resetting response CCR{Terminate} CCA{Terminate}

Reset


Return recharge result

Issue 01 (2010-07-28)


4-11



The process of activating an account by recharging the account by using a recharge card is similar to the process of recharging an account by using a recharge card. After a subscriber dials the access code of the IVR management process, the system authenticates the subscriber. If a subscriber has not been activated, the SCP invokes the first activation process. In addition, t he SCP interacts with the subscriber by playing voices to obtain recharge card information. After receiving the first activation request reported through the recharge request from the SCP, the CBP processes the recharge card information, activates the subscriber, and recharges the account. For process details, see 5.2 Process of Recharging an Account by Using a Recharge Card Through IVR .

4.8 Reference This section describes the terms used in the activation processes. None.

4-12


Issue 01 (2010-07-28)


5 Recharge Processes

5

Recharge Processes

About This Chapter Chap ter

5.1 Overview A prepaid su bscriber can use use a service only only when the subscriber subscriber has sufficient account balance and the account account balance is valid. When the account balance is insufficient, the subscriber needs to recharge the the account in time. 5.2 Process of of Recharging an Account by Using a Recharge Card Through IVR Carrier distri butes butes the scratch cards, cards, which have printed printed with face value and password under cover. Subscr ibers ibers can buy the card, scratch the cover and get the PIN, and then he/she can recharge the account via OCS IVR self care management flow. 5.3 Process of of Recharging an Account by Using a Recharge Card Through USSD In this process, process, a subscriber recharges an account by sending a USSD short message. 5.4 Process of of Recharging an Account by Using a Recharge Card Through a Short Message This section describes the process of recharging an account by using a recharge card through a short message. message. 5.5 Process of of Recharging an Account by Using a Recharge Card Manually This section describes the process of recharging an account manually by using a recharge card. 5.6 Process of Recharging an Account by Cash This section describes the process of recharging an account by cash. 5.7 Process of Recharging an Account by Dialing a Recharge Access Code This section describes the process of recharging an account by dialing a recharge access code. 5.8 Process of Recharging an Account Through the EVC This section describes the process of recharging an account through the EVC. 5.9 Reference This section briefly describes the basic terms related to the recharge processes.

Issue 01 (2010-07-28)


5-1



5.1 Overview A prepaid subscriber can use a service only when the subscriber has sufficient account balance and the account balance is valid. When the account balance is insufficient, the subscriber needs to recharge the account in time. A subscriber can recharge the account in any of the following modes: l

Through IVR In this mode, a subscriber can recharge the personal account or the account of another subscriber by dialing the access code of the IVR process and performing operations according to the voices played on the main menu of the IVR process.

l

Through USSD In this mode, a subscriber can send a USSD string or a short message to recharge an account. The short message needs to contain the recharge access code and the password of the recharge card. If the subscriber wants to recharge the account of another subscriber, the short message also needs to contain the number of the recharged party.

l

By using a recharge card through a short message In this mode, a subscriber can send a short message containing the password of a recharge card to a specified access code to recharge an account.

l

Manually In this mode, a Web page or third-party platform can be used to invoke the WebService interface to recharge the account of a subscriber by using a recharge card.

l

By cash In this mode, a subscriber can recharge an account by cash through different access channels, for example, customer service centers, banks, and ATMs. When a subscriber recharges an account by cash, the SMAP or a third-party platform is used to invoke the WebService interface to perform the recharge.

l

By dialing a recharge access code In this mode, a subscriber can dial a specified recharge access code to recharge an account through the VC.

l

Through the EVC In this mode, a dealer can use the account transfer function to recharge the account of a subscriber. The specific process is: A dealer prepays a certain amount. When a subscriber wants to recharge an account, the recharge amount is deducted from the account of the dealer and transferred to the call fee account of the subscriber.

The following sections describe each recharge process in detail.

5.2 Process of Recharging an Account A ccount by Using a Recharge Card Through IVR Carrier distributes the scratch cards, which have printed with face value and password under cover. Subscribers can buy the card, scratch the cover and get the PIN, and then he/she can recharge the account via OCS IVR self care management flow. 5-2


Issue 01 (2010-07-28)



Process of Recharging the Personal Account of a Subscriber Through IVR Figure 5-1 shows the process of recharging the personal account of a subscriber through IVR. Figure 5-1 Process of recharging the personal account of a subscriber through IVR MSC/VLR/SSP Subscriber dials IVR access code

SCP

CBP

VC

IDP CCR{Initial} CCA{Initial}

Authenticate

RRBE System plays voice to interact with subscriber Subscriber chooses to recharge Verification is passed, and system continue to play voice to interact with subscriber


Enter recharged number and recharge card password Execute recharge card authentication request Authenticate Execute authentication response CCR{Initial}

CCA{Initial}

Debit and reward


Reset


CCR{Terminate} CCA{Terminate} Return recharge result



2.


3.

The SCP SCP sends sends a CCR{I CCR{Init nitial ial} } messag messagee to the CBP CBP for for authen authentic ticati ation. on.

Issue 01 (2010-07-28)


5-3



4.


5.

The SCP SCP deliver deliverss an RRBE RRBE message message to the MSC/VLR/SS MSC/VLR/SSP P accordin according g to the the service service logic logic to request the dynamic configuration of the EDP. Then the SCP determines the EDPs that need to be reported to the SCP.

6.

If the authentica authentication tion is passed, passed, the SCP plays plays voice voicess to interac interactt with the the subscrib subscriber. er. NOTE

The operations in the dotted red box in Figure 5-1 are interactions between the SCP and the subscriber.

7.

The subscr subscriber iber chooses chooses to recharge recharge the accoun accountt by using using a rechar recharge ge card. card.

8.

After receiving receiving the rechar recharge ge reques requestt from the subscr subscriber, iber, the SCP SCP checks checks whethe whetherr the subscriber is blacklisted.

9.

If the subscriber subscriber is not blackl blacklisted isted,, the SCP SCP plays plays voices voices to prompt prompt the subscr subscriber iber to to enter enter the recharged number and the password of the recharge card. The subscriber enters the required information as prompted.

10. If the subscriber subscriber is not not in the recharge blacklist, and if the recharged recharged subscriber subscriber is an an OCS subscriber, the SCP sends a message for authenticating the recharge card to the home VC of the recharge card through the INAP Execute interface. 11. The VC verifies the password of the recharge recharge card card and returns the verification result to the the SCP. The VC checks whether the password of the recharge card is correct. If the password of the recharge card is incorrect, the VC returns the verification result to the SCP. In addition, after the recharge card fails to pass the authentication, the SCP records an authentication failure. When the number of authentication failures reaches the threshold, the SCP sends an RCOMM message to request the BMP to blacklist the subscriber. The subscriber cannot recharge the account before being released from the blacklist. After the subscriber recharges the account by using the recharge card successfully, the number of authentication failures is cleared. 12. The SCP checks the verification result result returned by the VC. If the recharge recharge card card passes the authentication, the SCP sends a CCR{Initial} message to the CBP for recharge. 13. The CBP sends sends a CCA{Initial} CCA{Initial} message message contain containing ing the recharge recharge result result to the SCP. SCP. After receiving the recharge request, the CBP recharges the account of the subscriber. If certain resources need to be rewarded to the subscriber, the CBP also processes the resource reward. 14. The SCP checks the recharge result returned returned by the CBP. If the recharge recharge is successful, successful, the SCP sends a request for resetting the recharge card through the INAP Execute interface. 15. The VC modifies modifies the recharg rechargee card informati information on and returns returns the modifica modification tion result result to the SCP. The VC changes the recharge card status to a status indicating that the recharge card is used and records the information such as the recharged number and recharge time. 16. The SCP checks the modification result result returned by the VC. If the the VC resets resets the recharge card successfully, the SCP sends a CCR{Terminate} message to request the CBP to confirm the recharge. 17. After confirm confirming ing the recharge recharge,, the CBP sends a CCA{Termina CCA{Terminate} te} message message containing containing the confirmation result to the SCP. After receiving the confirmation request, the CBP submits the recharge transaction to perform debiting on the recharge recharge and preference preference and to record the recharge recharge log and CDR. 5-4


Issue 01 (2010-07-28)



The confirmation result returned to the SCP contains the notification contents of the recharge short message sent to the subscriber. 18. The SCP sends sends a CCR{Terminat CCR{Terminate} e} message message to request request the CBP to end the recharg recharge. e. 19. The CBP ends ends the recharge recharge and sends sends a CCA{Terminate CCA{Terminate} } message message containing containing the processing result to the SCP. SCP. 20. After the the recharge recharge is complete, complete, the SCP SCP plays a voice voice or sends a short short message message to notify the subscriber of the recharge result. Then the process of recharging the personal account of a subscriber through IVR is complete. NOTE l

The SCP delivers the ID of the short message that needs to be sent to the subscriber to the SMSC. Then the SMSC delivers the short message to the subscriber.

l

The SCP delivers the ID of the voice that needs to be played to the subscriber to the MSC/VLR/SSP. Then the MSC/VLR/SSP plays the voice to the subscriber.

Process of Recharging the Account of Another OCS Subscriber Through IVR Figure 5-2 shows the process of recharging the account of another OCS subscriber through IVR.

Issue 01 (2010-07-28)


5-5



Figure 5-2 Process of recharging the account of another OCS subscriber through IVR MSb

MSC/VLR/SSP

SCP

CBP

SCPb

CBPb

VC

Subscriber dials IVR access code IDP CCR{Initial} Authenticate CCA{Initial} RRBE System plays voice to interact with subscriber Subscriber chooses to recharge Verification is passed, and system continue to play voice to interact with subscriber


Enter recharged number and recharge card password Execute recharge

Execute recharge card authentication request Execute authentication response

Authenticate


Debit and reward

Execute recharge card resetting request Reset Execute resetting response CCR{Terminate}

Execute recharge confirmation response

CCA{Terminate}


CCR{Terminate} CCA{Terminate} Notify of recharge result Notify of recharge result

MS b

OCS subscriber to be recharged.

SCP b

Home SCP of the MSISDN of the recharged subscriber.

CBP b

Home CBP of the MSISDN of the recharged subscriber.


5-6

1.


2.

The MSC/VLR MSC/VLR/SSP /SSP of the visited visited area area reports reports an an IDP message message to trigge triggerr the call call to the SCP of the home area. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



3.

The SCP SCP sends sends a CCR{I CCR{Init nitial ial} } messag messagee to the CBP CBP for for authen authentic ticati ation. on.

4.


5.


6.

If the authentica authentication tion is passed, passed, the SCP plays plays voice voicess to interac interactt with the the subscrib subscriber. er. NOTE

The operations in the dotted red box in Figure 5-2 are interactions between the SCP and the subscriber.

7.

The subscr subscriber iber chooses chooses to recharge recharge the accoun accountt by using using a rechar recharge ge card. card.

8.

After receiving receiving the rechar recharge ge reques requestt from the subscr subscriber, iber, the SCP SCP checks checks whethe whetherr the recharging number and recharged number are blacklisted.

9.

If the subscriber subscriber is not blackl blacklisted isted,, the SCP SCP plays plays voices voices to prompt prompt the subscr subscriber iber to to enter enter the recharged number and the password of the recharge card. The subscriber enters the required information as prompted.

10. The SCP determines that the recharged number is the MSISDN MSISDN of another OCS OCS subscriber. subscriber. Then the SCP forwards the recharge request of the subscriber to SCP b through the INAP Execute interface. 11. SCP b sends a message for authenticating the recharge card to the home VC of the recharge card through the INAP Execute interface. 12. The VC verifies the password of the recharge recharge card and returns the verification verification result to SCP b. The VC checks whether the recharge card exists and whether the status of the recharge card is normal. Then the VC returns a result containing the information such as the face value, status, and validity period of the recharge card to SCP b. 13. SCP b checks the result returned by the VC. If the recharge card passes the authentication, SCP b sends a CCR{Initial} message to CBP b for recharge. 14. After receiving receiving the the rechar recharge ge request request from SCP b, CBP b performs the recharge and processes the resource reward if available. Then CBP b sends a CCA{Initial} message containing the processing result to SCP b. 15. After the recharge recharge is succes successful, sful, SCP b sends a request for resetting the recharge card through the INAP Execute interface. 16. The VC modifies modifies the recharg rechargee card informati information on and returns returns the modifica modification tion result result to SCP b. The VC changes the recharge card status to a status indicating that the recharge card is used and records the information such as the recharged number and recharge time. 17. SCP b checks the result returned by the VC. If the recharge card is resetted successfully, SCP b sends a CCR{Terminate} message to CBP b to submit the recharge transaction. 18. After receiving receiving the request, request, the CBP performs debiting on the recharge recharge and and preference preference and records the recharge log and CDR. Then the CBP sends a CCA{Terminate} message containing the processing result to SCP b. 19. SCP b returns the recharge result to the home SCP of the recharging subscriber through the INAP Execute interface. 20. The SCP of the rechar recharging ging subscribe subscriberr sends a CCR{Termin CCR{Terminate} ate} message message to request request the CBP of the recharging subscriber to end the recharge. Issue 01 (2010-07-28)


5-7



21. The CBP sends sends a CCA{Terminat CCA{Terminate} e} message message containing containing the process processing ing result result to the SCP. 22. SCP b delivers the recharge result to the recharged subscriber. 23. The SCP notifies the recharging subscriber of the recharge recharge result. Then the process of recharging the account of another OCS subscriber through IVR is complete.

Exception Handling Process The exceptions that may occur when the subscriber recharges the account are as follows: 1.

Symptom: Symptom: After After the the SCP SCP sends sends a CCR{Init CCR{Initial} ial} messag messagee to the the CBP for charg charging, ing, the the SCP SCP does not receive the CCA{Initial} message returned by the CBP within the specified duration. Possible cause and exception handling: If the SCP does not receive the CCA{Initial} message returned by the CBP within the specified duration, the SCP sends a CCR{Event} message again to the CBP to query the recharge status of the subscriber. If a success message is returned, it indicates that the recharge is successful. If a failure message is returned, it indicates that the recharge fails. If the SCP still does not receive the CCA{Event} message returned by the CBP within the specified duration, the SCP considers that the recharge is successful.

2.

Symptom: Symptom: After After the the SCP sends a message message through through the INAP Execute Execute interfa interface ce to request request the VC to reset the recharge card, the SCP does not receive the response message from the VC within the specified duration. Possible cause and exception handling: When the SCP does not receive the result of resetting the recharge card from the VC, the SCP sends a request for authenticating the recharge card to the VC to query the recharge card status and performs the following processing according according to the query result: (1) If the VC returns returns a message message indica indicating ting that that the recharge recharge card card is not reset, reset, the SCP SCP sends a DCC message to request the CBP to cancel the recharge and notifies the subscriber that the recharge fails. (2) If the VC returns returns a message message indicati indicating ng that the recha recharge rge card card is already already reset, reset, the SCP SCP considers that the recharge card is reset successfully and continues the subsequent processing. (3) If the SCP still still does not not receive receive the result result of resetting resetting the recha recharge rge card card from the VC, VC, the SCP continues the subsequent processing in the interest of the subscriber.

3.

Symptom: Symptom: After After the the SCP SCP sends sends a CCR{Te CCR{Termina rminate} te} message message to request request the CBP CBP to confirm confirm the recharge, the SCP does not receive the CCA{Terminate} message from the CBP within the specified duration. Possible cause and exception handling: When the SCP does not receive the CCA {Terminate} message from the CBP within the specified duration, the SCP considers that the recharge is successful in the interest of the subscriber.

5.3 Process of Recharging an Account A ccount by Using a Recharge Card Through USSD In this process, a subscriber recharges an account by sending a USSD short message.

Normal Process Figure 5-3 shows the process of recharging an account through USSD. 5-8


Issue 01 (2010-07-28)



Figure 5-3 Process of recharging an account through USSD MSC/VLR/SSP USSD recharge request

HLR

USSD recharge request

SCP

CBP

VC

MAP: USSD recharge request CCR{Event} Authenticate CCA{Event} Blacklist verification Execute recharge card authentication request Execute authentication response CCR{Initial} CCA{Initial}

Debit and reward

Execute recharge resetting request Reset Execute recharge resetting request CCR{Terminate}

Deliver recharge result



CCA{Terminate}



A subscribe subscriberr sends sends a USSD USSD rechar recharge ge request request.. The request request reaches reaches the MSC/VLR/ MSC/VLR/SSP. SSP. The request contains the information such as the recharge access code and the password of the recharge card. If the subscriber wants to recharge the account of another subscriber, the request also contains the MSISDN of the recharged subscriber.

2.

The MSC/V MSC/VLR/SS LR/SSP P forwar forwards ds the the request request to the HLR throug through h the MAP signaling. signaling.

3.

The HLR HLR route routess the requ request est to to the SCP SCP throu through gh the the MAP signal signaling ing..

4.

The SCP SCP sends sends a CCR{Eve CCR{Event} nt} message message to the CBP for for authenti authenticatio cation. n. For example, example, the the CBP checks whether the information such as the subscriber state is normal.

5.

The CBP CBP authenti authenticates cates the subscri subscriber ber and and sends sends a CCA{Ev CCA{Event} ent} messag messagee containi containing ng the processing result to the SCP. SCP.

6.

The SCP SCP parses parses the acces accesss code. code. After After determinin determining g that the the service service is is the rechar recharge ge service, service, the SCP triggers the recharge service process, checks whether the subscriber is in the recharge blacklist, and authenticates t he recharged subscriber.

Issue 01 (2010-07-28)


5-9



7.

If the subscriber subscriber is not in the rechar recharge ge blacklist blacklist,, and if if the recha recharged rged subscriber subscriber is an OCS OCS subscriber, the SCP sends a message for authenticating the recharge card to the home VC of the recharge card through the INAP Execute interface.

8.

The VC verif verifies ies the password password of the the rechar recharge ge card card and returns returns the the verifica verification tion result result to the the SCP. The VC checks whether the password of the recharge card is correct. If the password of the recharge card is incorrect, the VC returns the verification result to the SCP. In addition, after the recharge card fails to pass the authentication, the SCP records an authentication failure. When the number of authentication failures reaches the threshold, the SCP sends an RCOMM message to request the BMP to blacklist the subscriber. The subscriber cannot recharge the account before being released from the blacklist. After the subscriber recharges the account by using the recharge card successfully, the number of authentication failures is cleared.

9.

The SCP SCP checks checks the the verifica verification tion result result return returned ed by the the VC. If the recharge recharge card passes passes the authentication, the SCP sends a CCR{Initial} message to the CBP for recharge.

10. The CBP sends sends a CCA{Initial} CCA{Initial} message message contain containing ing the recharge recharge result result to the SCP. SCP. After receiving the recharge request, the CBP recharges the account of the subscriber. If certain resources need to be rewarded to the subscriber, the CBP also processes the resource reward. 11. The SCP checks the recharge result returned returned by the CBP. If the recharge recharge is successful, successful, the SCP sends a request to VC for resetting the recharge card through the INAP Execute interface. 12. The VC modifies modifies the recharg rechargee card informati information on and returns returns the modifica modification tion result result to the SCP. The VC changes the recharge card status to a status indicating that the recharge card is used and records the information such as the recharged number and recharge time. 13. The SCP checks the modification result result returned by the VC. If the the VC resets resets the recharge card successfully, the SCP sends a CCR{Terminate} message to request the CBP to confirm the recharge. 14. After confirm confirming ing the recharge recharge,, the CBP sends a CCA{Termina CCA{Terminate} te} message message containing containing the confirmation result to the SCP. After receiving the confirmation request, the CBP submits the recharge transaction to perform debiting on the recharge recharge and preference preference and to record the recharge recharge log and CDR. The confirmation result returned to the SCP contains the notification contents of the recharge short message sent to the subscriber. 15. After receiving receiving the confirmation result result returned returned by the CBP, the SCP returns returns the recharge recharge result to the HLR, the HLR returns the recharge result to the MSC/VLR/SSP, and the MSC/ VLR/SSP returns the recharge result to the subscriber. Then the process of recharging an account through USSD is complete. The recharge result returned by the SCP contains the information such as the account balance of the subscriber subscriber and the validity period period of the account.


5-10

Symptom: Symptom: After After the the SCP SCP sends sends a CCR{Init CCR{Initial} ial} messag messagee to the the CBP for charg charging, ing, the the SCP SCP does not receive the CCA{Initial} message returned by the CBP within the specified duration. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



Possible cause and exception handling: If the SCP does not receive the CCA{Initial} message returned by the CBP within the specified duration, the SCP sends a CCR{Event} message again to the CBP to query the recharge status of the subscriber. If a success message is returned, it indicates that the recharge is successful. If a failure message is returned, it indicates that the recharge fails. If the SCP still does not receive the CCA{Event} message returned by the CBP within the specified duration, the SCP considers that the recharge is successful. 2.


3.


5.4 Process of Recharging an Account A ccount by Using a Recharge Card Through a Short Message This section describes the process of recharging an account by using a recharge card through a short message.

Normal Process Figure 5-4 shows the normal process of recharging an account by using a recharge card through a short message.

Issue 01 (2010-07-28)


5-11



Figure 5-4 Normal process of recharging an account by using a recharge card through a short message MSC/VLR/SSP

SMSC

SMS recharge request SMS recharge request

GFEP

SCP

CBP

VC

SMPP: Recharge request Return success response Parse SMS content RCOMM: Recharge request Verify Execute recharge card authentication request Authenticate Execute authentication response CCR{Initial} CCA{Initial}

Debit and reward

Execute recharge card resetting request Execute recharge card resetting response CCR{Terminate}

Deliver recharge Deliver recharge result result Deliver recharge result Deliver recharge result

CCA{Terminate}

Reset



A subscribe subscriberr sends sends a rechar recharge ge request request through through a short short messag message. e. The request request reaches reaches the MSC/VLR/SSP. The recharge request contains the information such as the password of a recharge card.

5-12

2.

The MSC/VLR MSC/VLR/SSP /SSP authentica authenticates tes the the subscrib subscriber. er. If If the subscr subscriber iber has the the right right to send send this short message, the MSC/VLR/SSP forwards the short message to the SMSC.

3.

After receiving receiving the short short message message,, the SMSC forwa forwards rds the the short short message message to the GFEP GFEP through SMPP3.4 according to the ID of the External Short Message Entity (ESME).

4.

After receiving receiving the short short message message sent by by the SMSC, SMSC, the the GFEP GFEP directly directly returns returns a respon response se message to the SMSC.

5.

The GFEP GFEP parse parsess the short short messag messagee contents contents and and sends sends an RCOMM RCOMM messa message ge to intera interact ct with the SCP.

6.

After receiving receiving the RCOMM RCOMM message message,, the SCP SCP verifie verifiess the subscr subscriber iber and authen authenticat ticates es the recharged number. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



By verifying the subscriber, the SCP checks whether the subscriber is in the recharge blacklist. The recharge recharge blacklist records are are stored on the SCP. SCP. When the number of of consecutive attempts for the subscriber to enter the recharge password reaches the maximum, the subscriber enters the recharge blacklist. A subscriber in recharge blacklist state cannot recharge accounts any more. By authenticating the recharged number, the SCP determines whether the recharged number is an OCS subscriber. 7.

If the subscriber subscriber is not in the rechar recharge ge blacklist blacklist,, and if if the recha recharged rged subscriber subscriber is an OCS OCS subscriber, the SCP sends a message for authenticating the recharge card to the home VC of the recharge card through the INAP Execute interface.

8.

The VC verif verifies ies the password password of the the rechar recharge ge card card and returns returns the the verifica verification tion result result to the the SCP.

9.


10. The CBP sends sends a CCA{Initial} CCA{Initial} message message contain containing ing the recharge recharge result result to the SCP. SCP. 11. The SCP checks the recharge result returned returned by the CBP. If the recharge recharge is successful, successful, the SCP sends a request to VC for resetting the recharge card through the INAP Execute interface. 12. The VC modifies modifies the recharg rechargee card informati information on and returns returns the modifica modification tion result result to the SCP. 13. The SCP checks the modification result result returned by the VC. If the the VC resets resets the recharge card successfully, the SCP sends a CCR{Terminate} message to request the CBP to confirm the recharge. 14. After confirm confirming ing the recharge recharge,, the CBP sends a CCA{Termina CCA{Terminate} te} message message containing containing the confirmation result to the SCP. 15. After the recharge is successful, the SCP delivers a short message to notify the subscriber of the recharge result through the SMSC. Then the process of recharging an account by using a recharge card through a short message is complete.



2.

Symptom: Symptom: After After the the SCP sends a message message through through the INAP Execute Execute interfa interface ce to request request the VC to reset the recharge card, the SCP does not receive the response message from the VC within the specified duration. Possible cause and exception handling: When the SCP does not receive the result of resetting the recharge card from the VC, the SCP sends a request for authenticating the recharge card to the VC to query the recharge card status and performs the following processing according according to the query result:

Issue 01 (2010-07-28)


5-13



(1) If the VC returns returns a message message indica indicating ting that that the recharge recharge card card is not reset, reset, the SCP SCP sends a DCC message to request the CBP to cancel the recharge and notifies the subscriber that the recharge fails. (2) If the VC returns returns a message message indicati indicating ng that the recha recharge rge card card is already already reset, reset, the SCP SCP considers that the recharge card is reset successfully and continues the subsequent processing. (3) If the SCP still still does not not receive receive the result result of resetting resetting the recha recharge rge card card from the VC, VC, the SCP continues the subsequent processing in the interest of the subscriber. 3.


5.5 Process of Recharging an Account A ccount by Using a Recharge Card Manually This section describes the process of recharging an account manually by using a recharge card.

Normal Process Figure 5-5 shows the normal process of recharging an account manually.

5-14


Issue 01 (2010-07-28)



Figure 5-5 Normal process of recharging an account manually

Foreground Recharge request

BMP

SCP

CBP

VC

Recharge request Blacklist verification RCOMM recharge request Execute recharge card authentication request Authenticate Authentication response CCR{Initial} CCA{Initial}

Debit and reward

Execute recharge card resetting request Recharge card resetting response CCR{Terminate}



Return recharge CCA{Terminate} result

Reset



A subscriber subscriber sends a recharge recharge reques request. t. The recha recharge rge request request reaches reaches the the OCS foregr foreground. ound.

2.

After receiving receiving the the recharge recharge request, request, the the OCS foregr foreground ound forwa forwards rds the recharge recharge request request to the BMP through Web pages, WebService interface, or SMAP.

3.

The BMP checks checks whether whether the the subscribe subscriberr is in the the recharge recharge black blacklist. list. If the subscrib subscriber er is not not in the recharge blacklist, the BMP sends an RCOMM message containing the recharge request to the SCP. The recharge request contains the information such as the MSISDN of the subscriber, sequence number, and password of a recharge card.

4.

Issue 01 (2010-07-28)

The SCP SCP determi determines nes that that the recharge recharged d number number is an an OCS subscr subscriber iber according according to the RCOMM message sent by the BMP, and then sends a message for authenticating the recharge card to the home VC of the recharge card through the INAP Execute interface.


5-15



5.

The VC verif verifies ies the password password of the the rechar recharge ge card card and returns returns the the verifica verification tion result result to the the SCP.

6.


7.

The CBP CBP sends sends a CCA{Initial CCA{Initial} } message message containing containing the recha recharge rge result result to the SCP.

8.

The SCP SCP checks checks the recha recharge rge result result returne returned d by the CBP. CBP. If the the recharge recharge is successfu successful, l, the SCP sends a request to VC for resetting the recharge card through the INAP Execute interface.

9.

The VC VC modifies modifies the recharge recharge card informatio information n and return returnss the modific modification ation result result to the the SCP.

10. The SCP checks the modification result result returned by the VC. If the the VC resets resets the recharge card successfully, the SCP sends a CCR{Terminate} message to request the CBP to confirm the recharge. 11. After confirm confirming ing the recharge recharge,, the CBP sends a CCA{Termina CCA{Terminate} te} message message containing containing the confirmation result to the SCP. 12. The SCP sends sends an RCOMM RCOMM message message contain containing ing the rechar recharge ge result result to the BMP. BMP. The recharge result contains the information such as the recharge amount, validity period of the account after the recharge, and recharge bonus. 13. The BMP returns returns the rechar recharge ge result result to the OCS foreground foreground,, and the OCS foregro foreground und returns the recharge result to the subscriber. Then the process of recharging an account manually is complete.



2.

Symptom: Symptom: After After the the SCP sends a message message through through the INAP Execute Execute interfa interface ce to request request the VC to reset the recharge card, the SCP does not receive the response message from the VC within the specified duration. Possible cause and exception handling: When the SCP does not receive the result of resetting the recharge card from the VC, the SCP sends a request for authenticating the recharge card to the VC to query the recharge card status and performs the following processing according according to the query result: (1) If the VC returns returns a message message indica indicating ting that that the recharge recharge card card is not reset, reset, the SCP SCP sends a DCC message to request the CBP to cancel the recharge and notifies the subscriber that the recharge fails. (2) If the VC returns returns a message message indicati indicating ng that the recha recharge rge card card is already already reset, reset, the SCP SCP considers that the recharge card is reset successfully and continues the subsequent processing.

5-16


Issue 01 (2010-07-28)



(3) If the SCP still still does not not receive receive the result result of resetting resetting the recha recharge rge card card from the VC, VC, the SCP continues the subsequent processing in the interest of the subscriber. 3.


5.6 Process of Recharging an Account A ccount by Cash This section describes the process of recharging an account by cash. Figure 5-6 shows the normal process of recharging an account by cash. Figure 5-6 Normal process of recharging an account by cash Recharge access channel

BMP

CBP

Recharge request Invoke the WebService interface to recharge Recharge request Return recharge result Notify subscriber of recharge result

Recharge and reward



A subscribe subscriberr sends sends a cash cash rechar recharge ge request request through through a recha recharge rge acces accesss channel. channel. The recharge access channel can be the SMAP or a third-party platform that is used to invoke the WebService interface to recharge.

2.

The rechar recharge ge access access channe channell invokes invokes the WebSe WebService rvice interface interface provided provided by the the OCS system system to initiate a cash recharge request to the BMP.

3.

The BMP forwards forwards the recha recharge rge request request of the subscriber subscriber to the the CBP. CBP.

4.

The CBP CBP perform performss the cash cash recha recharge rge and and process processes es the resource resource reward reward if available. available. In addition, the CBP records the recharge log and CDR and returns the recharge result to the BMP.

5.

The BMP returns returns the recha recharge rge result result to the the recharge recharge access access channel, channel, and the recharge recharge acces accesss channel returns the recharge result to the subscriber. Then the process of recharging an account by cash is complete.

Issue 01 (2010-07-28)


5-17



5.7 Process of Recharging an Account by Dialing a Recharge Access Code This section describes the process of recharging an account by dialing a recharge access code.

Normal Process A subscriber needs to dial different recharge access codes for recharging the personal account and for recharging the account of another subscriber. After a subscriber dials a recharge access code, the SCP directly forwards the call to the process of recharging the personal account or the process of recharging recharging the account of another another subscriber according according to the recharge recharge access code code without interacting with the subscriber through voices. Figure 5-7shows the normal process of recharging the personal account of a subscriber by dialing the recharge access code. For the process of recharging the account account of another subscriber by by dialing the recharge recharge access access code, code, see the process of recharging the account of another subscriber through IVR in 5.2 Process of Recharging an Account by Using a Recharge Card Through IVR . Figure 5-7 Normal process of recharging the personal account of a subscriber by dialing the recharge access code MSC/VLR/SSP

SCP

CBP

VC

Subscriber dials recharge access code IDP RRBE CCR{Event} Authenticate CCA{Event} Blacklist verification Execute recharge card authentication Authenticate Execute authentication response CCR{Initial}

CCA{Initial}

Debit and reward


Reset



5-18


Issue 01 (2010-07-28)



For the description of the process, see 5.2 Process of Recharging an Account by Using a Recharge Card Through IVR .



2.


3.


5.8 Process of Recharging an Account A ccount Through the EVC This section describes the process of recharging an account through the EVC. Through the EVC, an account can be recharged: l l

Issue 01 (2010-07-28)

Not in DCC mode In DCC mode Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-19



The following sections describe the process of recharging an account through the EVC in each mode in detail.

Process of Recharging an Account Through the EVC Not in DCC Mode Figure 5-8 shows the process of recharging an account through the EVC not in DCC mode. Figure 5-8 Process of recharging an account through the EVC not in DCC mode Dealer

BMP

EVC

CBP

Recharge request Recharge request Update dealer account Invoke the WebService interface to recharge Recharge request Return recharge result Return recharge result


Confirm dealer account update Deliver recharge result



A subsc subscrib riber er send sendss a recha recharge rge reques requestt to a dealer dealer..

2.

The dealer dealer receives receives the the rechar recharge ge request request and sends sends the the recharg rechargee request request to to the EVC. EVC.

3.

The EVC EVC receives receives the rechar recharge ge request request,, updates updates the account account balance balance of the dealer, dealer, prededucts the recharge amount, and forwards the recharge recharge request to the BMP through the WebService interface.

4.

The BMP BMP invokes invokes the the cash cash rechar recharge ge service service of the OCS system system and reques requests ts the CBP to recharge the account of the subscriber.

5.

The CBP recharge rechargess the account account of of the subscr subscriber iber and and returns returns the the recharge recharge result result to the BMP BMP and the subscriber.

6.

After receiving receiving the rechar recharge ge result, result, the BMP BMP returns returns the the rechar recharge ge result result to the EVC. EVC.

7.

The EVC EVC updates updates the account account balanc balancee of the the dealer dealer accord according ing to the the recharg rechargee result result returned returned by the BMP and confirms confirms the account update of of the dealer. If the recharge fails, fails, the EVC rolls back the prededucted amount.

8.

The EVC EVC returns returns the the recharg rechargee result result to the the dealer dealer and the the subscrib subscriber. er. Then Then the the process process of of recharging an account through the EVC not in DCC mode is complete.

Process of Recharging an Account Through the EVC in DCC Mode Figure 5-9 shows the process of recharging an account through the EVC in DCC mode. 5-20


Issue 01 (2010-07-28)



Figure 5-9 Process of recharging an account through the EVC in DCC mode Dealer

EVC

CBP

Recharge request Recharge request Update dealer account CCR{Initial} CCA{Initial}

Authenticate and recharge

CCR{Terminate} CCA{Terminate} Return recharge result

Confirm recharge

Confirm dealer account update



A subsc subscrib riber er send sendss a recha recharge rge reques requestt to a dealer dealer..

2.

The dealer dealer receives receives the the rechar recharge ge request request and sends sends the the recharg rechargee request request to to the EVC. EVC.

3.

The EVC EVC receives receives the rechar recharge ge request request,, updates updates the account account balance balance of the dealer, dealer, prededucts the recharge recharge amount, and sends sends a CCR{Initial} message to the CBP for recharge.

4.

After receiving receiving the CCR{Init CCR{Initial} ial} messag message, e, the CBP perform performss authentic authentication ation and preprerecharge on the subscriber. If the subscriber is in arrears, the CBP generates a work order and sends a CCA{Initial} message containing the authentication result to the EVC.

5.

After receiving receiving the authen authenticat tication ion result, result, the the EVC EVC sends sends a CCR{Term CCR{Terminate inate} } message message to request the CBP to confirm the recharge.

6.

After receiving receiving the the recharge recharge confirmat confirmation ion message message,, the CBP performs performs the the recharge recharge.. If a recharge preference preference is available, the CBP also triggers the recharge preference and writes the recharge log and CDR. If the subscriber is suspended because of arrears before the recharge, the CBP sends a work order to resume the subscriber.

7.

After processing processing the rechar recharge, ge, the the CBP sends a CCA{Term CCA{Terminate inate} } message message contai containing ning the the recharge result to the EVC. The recharge result contains the i nformation about the recharge amount, preference, and notification short message for the recharge. NOTE

If the EVC requests to cancel the recharge, the EVC sends a CCR{Terminate} message to request the CBP to roll back the recharge. Then the CBP rolls back the recharge and performs the subsequent processing. processing.

8.

Issue 01 (2010-07-28)

The EVC EVC updates updates the account account balanc balancee of the the dealer dealer accord according ing to the the recharg rechargee result result returned returned by the CBP and confirms the account update of the dealer. If the recharge fails, the EVC rolls back the prededucted amount. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

5-21



9.

The EVC EVC returns returns the recharge recharge result result to the deale dealerr and the the recharg recharged ed party. party. Then Then the proce process ss of recharging an account through the EVC in DCC mode is complete.

5.9 Reference This section briefly describes the basic terms related to the recharge processes. None.

5-22


Issue 01 (2010-07-28)


6 Balance Query Processes

6

Balance Query Processes

About This Chapter Chap ter

6.1 Overview This section describes describes the balance query modes and balance query processes that are supported by the OCS system. system. 6.2 Process of Querying the Account Balance of a Subscriber Through IVR This section describes describes the process of querying the account balance of a subscriber through IVR. In this process, process, the subscriber may be free of charge or charged. 6.3 Process of Querying the Account Balance of a Subscriber Through USSD This section describes describes the process of querying the account balance of a subscriber through USSD. In this process, process, the subscriber may be free of charge or charged. 6.4 Process of Querying the Account Balance of a Subscriber by Sending a Short Message This section describes the process of querying the account balance of a subscriber by sending a short message. message. In this process, the subscriber may be free of charge or charged. 6.5 Process of Querying the Account Balance of a Subscriber Through the WebService Interface Interface This section describes the process of querying the account balance of a subscriber through the WebService interface. i nterface. 6.6 Process of Querying the Account Balance of a Subscriber on the SMAP This section describes the process of querying t he account balance of a subscriber on the SMAP. 6.7 Reference This section briefly describes the basic terms related to the balance query processes.

Issue 01 (2010-07-28)


6-1



6.1 Overview This section describes the balance query modes and balance query processes that are supported by the OCS system. A prepaid subscriber can query the personal account balance. The balance query modes supported by the OCS system are as follows: l

Querying the account balance of a subscriber through IVR

l

Querying the account balance of a subscriber through USSD

l

Querying the account balance of a subscriber by sending a short message

l

Querying the account balance of a subscriber through the WebService interface

l

Querying the account balance of a subscriber on the SMAP

The following sections describe each balance query process in detail.

6.2 Process of Querying the Account Balance of a Subscriber Through IVR This section describes the process of querying the account balance of a subscriber through IVR. In this process, the subscriber may be free of charge or charged.

6.2.1 Process of Querying the Account Balance of a Subscriber Through IVR When the When the Subscriber Subscriber Is Free of Charge Figure 6-1 shows the normal process of querying the account balance of a subscriber through IVR when the subscriber is free of charge. Figure 6-1 Normal process of querying the account balance of a subscriber through IVR when the subscriber is free of charge MSC/VLR/SSP

SCP

CBP

Subscriber dials IVR access code to query balance Send balance query request CCR{Event}

Return balance query result


CCA{Event}

Query balance



Issue 01 (2010-07-28)



1.

A subscribe subscriberr sends sends a request request of querying querying the balanc balancee through through IVR. IVR. The request request reaches reaches the MSC/VLR/SSP.

2.

The MSC/VL MSC/VLR/S R/SSP SP forw forward ardss the the reque request st to to the the SCP. SCP.

3.

The SCP SCP sends sends a CCR{Eve CCR{Event} nt} message message to request request the CBP CBP to query query the the account account balance balance of the subscriber.

4.

The CBP CBP queries queries the accoun accountt balance balance of of the subscribe subscriberr and sends a CCA{Event CCA{Event} } message message containing the query result to the SCP.

5.

The SCP SCP deliver deliverss the query result result to the the MSC/VLR/ MSC/VLR/SSP, SSP, and the the MSC/VLR/ MSC/VLR/SSP SSP notifie notifiess the subscriber of the query result. Then the process of querying the account balance of a subscriber through IVR when the subscriber is free of charge is complete.

6.2.2 Process of Querying the Account Balance of a Subscriber Through IVR When the Subscriber Is Charged Figure 6-2 shows the normal process of querying the account balance of a subscriber through IVR when the subscriber is charged. Figure 6-2 Normal process of querying the account balance of a subscriber through IVR when the subscriber is charged MSC/VLR/SSP Subscriber dials IVR access code to query balance

SCP

CBP

Send balance query request CCR{Initial} CCA{Initial}

Query balance

CCR{Terminate}



CCA{Terminate}

Deduct fee


A subscriber sends a request of querying the balance through IVR. The request reaches the MSC/VLR/SSP.

2.

The MSC/VL MSC/VLR/S R/SSP SP forw forward ardss the the reque request st to to the the SCP. SCP.

3.

The SCP SCP sends sends a CCR{Init CCR{Initial} ial} message message to request request the the CBP to to query query the account account balance balance of the subscriber and to deduct the balance query fee.

4.

The CBP prededucts prededucts the the balance balance query query fee, fee, querie queriess the account account balanc balancee of the subsc subscriber riber,, and then sends a CCA{Initial} message containing the processing result to the SCP.

5.

After receiving receiving the proce processing ssing result result returne returned d by the CBP, CBP, the the SCP sends a CCR {Terminate} message to request the CBP to confirm the fee deduction.

Issue 01 (2010-07-28)


6-3



6.

The CBP CBP confirms confirms the fee fee deducti deduction on and returns returns the processing processing result result to the SCP.

7.

The SCP SCP deliver deliverss the processing processing result result to the the MSC/VLR MSC/VLR/SSP /SSP,, and the MSC/VL MSC/VLR/SS R/SSP P returns the processing result to the subscriber. Then the process of querying the account balance of a subscriber subscriber through IVR when when the subscriber is charged charged is complete.

6.3 Process of Querying the Account Balance of a Subscriber Through USSD This section describes the process of querying the account balance of a subscriber through USSD. In this process, the subscriber may be free of charge or charged.

6.3.1 Process of Querying the Account Balance of a Subscriber Through USSD When the Subscriber Is Free of Charge Figure 6-3 shows the normal process of querying the account balance of a subscriber through USSD when the subscriber is free of charge. Figure 6-3 Normal process of querying the account balance of a subscriber through USSD when the subscriber is free of charge MSC/VLR/SSP

SCP

CBP

Send USSD balance query request U-CSI triggers service Send USSD balance query request




Query balance


6-4

1.

A subscribe subscriberr sends sends a USSD USSD string string to query the persona personall account account balanc balance. e. The The request request reaches the MSC/VLR/SSP.

2.

The MSC/VLR MSC/VLR/SSP /SSP triggers triggers the the USSD USSD service service according according to the U-CSI U-CSI and forwards forwards the the request to the SCP.

3.

The SCP SCP sends sends a CCR{Eve CCR{Event} nt} message message to request request the CBP CBP to query query the the account account balance balance of the subscriber.

4.

The CBP CBP queries queries the accoun accountt balance balance of of the subscribe subscriberr and sends a CCA{Event CCA{Event} } message message containing the query result to the SCP. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)


5.


The SCP SCP deliver deliverss the query result result to the the MSC/VLR/ MSC/VLR/SSP, SSP, and the the MSC/VLR/ MSC/VLR/SSP SSP notifie notifiess the subscriber of the query result. Then the process of querying the account balance of a subscriber through USSD when the subscriber is free of charge is complete.

6.3.2 Process of Querying the Account Balance of a Subscriber Through USSD When the Subscriber Is Charged Figure 6-4 shows the normal process of querying the account balance of a subscriber through USSD when the subscriber is charged. Figure 6-4 Normal process of querying the account balance of a subscriber through USSD when the subscriber is charged MSC/VLR/SSP

SCP

CBP

Send USSD balance query request U-CSI triggers service Send USSD balance query request


Query balance

CCR{Terminate}



CCA{Terminate}

Deduct fee


A subscribe subscriberr sends sends a USSD USSD string string to query the persona personall account account balanc balance. e. The The request request reaches the MSC/VLR/SSP.

2.

The MSC/VLR MSC/VLR/SSP /SSP triggers triggers the the USSD USSD service service according according to the U-CSI U-CSI and forwards forwards the the request to the SCP.

3.

The SCP SCP sends sends a CCR{Init CCR{Initial} ial} message message to request request the the CBP to to query query the account account balance balance of the subscriber and to deduct the balance query fee.

4.

The CBP prededucts prededucts the the balance balance query query fee, fee, querie queriess the account account balanc balancee of the subsc subscriber riber,, and then sends a CCA{Initial} message containing the processing result to the SCP.

5.

After receiving receiving the proce processing ssing result result returne returned d by the CBP, CBP, the the SCP sends a CCR {Terminate} message to request the CBP to confirm the fee deduction.

6.

The CBP CBP confirms confirms the fee fee deducti deduction on and returns returns the processing processing result result to the SCP.

7.

The SCP SCP deliver deliverss the processing processing result result to the the MSC/VLR MSC/VLR/SSP /SSP,, and the MSC/VL MSC/VLR/SS R/SSP P returns the the processing processing result to the subscriber. Then the process of querying the account balance of a subscriber subscriber through USSD when the subscriber is charged is complete. complete.

Issue 01 (2010-07-28)


6-5



6.4 Process of Querying the Account Balance of a Subscriber by Sending a Short Message This section describes the process of querying the account balance of a subscriber by sending a short message. In this process, the subscriber may be free of charge or charged.

6.4.1 Process of Querying the Account Balance of a Subscriber by Sending a Short Message When the Subscriber Is Free of Charge Figure 6-5 shows the normal process of querying the account balance of a subscriber by sending a short message when the subscriber is free of charge. Figure 6-5 Normal process of querying the account balance of a subscriber by sending a short message when the subscriber is free of charge MSC/VLR/SSP Send SMS balance query request

SMSC

GFEP

SCP

CBP

Send SMS balance query request SMPP: Balance query request Return success response Parse SMS content RCOMM: Balance query request CCR{Event}

RCOMM: Balance query result

Deliver balance query short message


CCA{Event}

Generate dynamic short message


6-6

A subscribe subscriberr sends sends a short short message message to to query query the personal personal accoun accountt balance. balance. The balanc balancee query request reaches the MSC/VLR/SSP. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)

Query balance



2.


3.

After receiving receiving the short short message message,, the SMSC forwa forwards rds the the short short message message to the GFEP GFEP through SMPP3.4 according to the ID of the ESME (External Short Message Entity).

4.


5.


6.

After receiving receiving the RCOMM RCOMM message message,, the SCP SCP determi determines nes whethe whetherr the subscr subscriber iber needs needs to be charged for sending this short message according to the related flag. If the subscriber is free of charge, the SCP sends a CCR{ Event} message to request the CBP to query the account balance of the subscriber.

7.

The CBP CBP queries queries the accoun accountt balance balance of of the subscribe subscriberr and sends a CCA{Event CCA{Event} } message message containing the query result to the SCP.

8.

The SCP SCP returns returns the the balance balance query query result result to the the GFEP GFEP and writes writes a dynamic dynamic short short message message according to the balance query result returned by the CBP. Then the SCP delivers the dynamic short message to the SMSC.

9.

The SMSC SMSC deliver deliverss a short short message message containin containing g the balanc balancee query query result result to the subscriber subscriber.. Then the process of querying the account balance of a subscriber by sending a short message when the subscriber is free of charge is complete.

6.4.2 Process of Querying the Account Balance of a Subscriber by Sending a Short Message When the Subscriber Is Charged Figure 6-6 shows the normal process of querying the account balance of a subscriber by sending a short message when the subscriber is charged.

Issue 01 (2010-07-28)


6-7



Figure 6-6 Normal process of querying the account balance of a subscriber by sending a short message when the subscriber is charged MSC/VLR/SSP Send SMS balance query request

SMSC

Send SMS balance query request

GFEP

SCP

CBP

SMPP: Balance query request Return success response Parse SMS content RCOMM: Balance query request CCR{Initial} CCA{Initial}

Query balance

CCR{Terminate}

RCOMM: Balance query result


CCA{Terminate}

Generate dynamic short message



6-8

1.

A subscribe subscriberr sends sends a short short message message to to query query the personal personal accoun accountt balance. balance. The balanc balancee query request reaches the MSC/VLR/SSP.

2.


3.

After receiving receiving the short short message message,, the SMSC forwa forwards rds the the short short message message to the GFEP GFEP through SMPP3.4 according to the ID of the ESME.

4.


5.


6.

After receiving receiving the RCOMM RCOMM message message,, the SCP SCP determi determines nes whethe whetherr the subscr subscriber iber needs needs to be charged for sending this short message according to the related flag. If the subscriber needs to be charged, the SCP sends a CCR{Initial} message to request the CBP to query the account balance of the subscriber. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)

Deduct fee



7.

The CBP queries queries the account account balance balance of the subscriber subscriber and sends sends a CCA{Ini CCA{Initial} tial} messa message ge containing the query result to the SCP.

8.

The SCP SCP sends sends a CCR{Termina CCR{Terminate} te} message message to request request the CBP CBP to deduc deductt the balance balance query query fee.

9.

After deducting deducting the the balanc balancee query query fee, fee, the the CBP CBP sends sends a CCA{Termin CCA{Terminate} ate} message message containing the processing result to the SCP.

10. The SCP returns returns the balance balance query query result result to the GFEP and and generates generates a dynamic dynamic short short message according to the balance query result returned by the CBP. Then the SCP delivers the dynamic short message to the SMSC. 11. The SMSC delivers a short message containing the balance query result to the subscriber. subscriber. Then the process of querying the account balance of a subscriber by sending a short message when the subscriber is charged is complete.

6.5 Process of Querying the Account Balance of a Subscriber Through the WebService Interface This section describes the process of querying the account balance of a subscriber through the WebService interface. Figure 6-7 shows the normal process of querying the account balance of a subscriber through the WebService interface. Figure 6-7 Normal process of querying the account balance of a subscriber through the WebService interface External system Balance query request

BMP

CBP

Invoke the WebService interface to query balance Balance query request Return result

Query balance



A subscriber subscriber sends a balance balance query query reque request st to the OCS system system through through an externa externall system. system. The external system refers to a system that accesses the OCS system externally. The external system is a foreground that can process subscriber requests.

2.

The externa externall system system receives receives the the balance balance query query request request from from the the subscriber subscriber and forward forwardss the request to the BMP through the WebService interface. interface.

3.

The The BMP BMP for forwa ward rdss the the requ reques estt to the the CBP CBP..

Issue 01 (2010-07-28)


6-9



4.

The CBP queries queries the account account balance balance of the subscribe subscriberr and return returnss the balanc balancee query query result result to the BMP.

5.

The BMP BMP returns returns the the balanc balancee query query result result to the extern external al system, system, and and the external external system system returns the balance query result to the subscriber. Then the process of querying the account balance of a subscriber subscriber through the WebService WebService interface interface is complete.

6.6 Process of Querying the Account Balance of a Subscriber on the SMAP This section describes the process of querying t he account balance of a subscriber on the SMAP. Figure 6-8 shows the normal process of querying the account balance of a subscriber on the SMAP. Figure 6-8 Normal process of querying the account balance of a subscriber on the SMAP SMAP

BMP

CBP

Balance query request Balance query request Balance query request Return result

Query balance


The process of querying the account balance of a subscriber on the SMAP is similar to the process of querying the account balance of a subscriber through the WebService interface. interface. The only difference is that the SMAP replaces the external system. For the description of the process, see 6.5 Process of Querying the Account Balance of a Subscriber Through the WebService Interface.

6.7 Reference This section briefly describes the basic terms related to the balance query processes. None.

6-10


Issue 01 (2010-07-28)


7 Balance Transfer Processes

7

Balance Transfer Processes

About This Chapter

7.1 Overview This section describes a balance transfer and the associated processes. 7.2 Process of of Transferring a Balance Through the IVR This section describes the process process of transferring a balance through the IVR. 7.3 Process of of Transferring a Balance Through the USSD This section describes the process of transferring a balance through throug h the USSD. 7.4 Process of of Transferring a Balance Through the WebService Interface Interface This section describes the process of transferring a balance through the WebService interface. interface. 7.5 Process of of Transferring a Balance on the SMAP This section describes the process of transferring a balance on the SMAP. 7.6 Reference Referenc e This section describes the terms used in balance transfer processes.

Issue 01 (2010-07-28)


7-1



7.1 Overview This section describes a balance transfer and the associated processes. In the OCS, balances can be transferred between the accounts of prepaid subscribers. During a balance transfer, transfer, only the balance of the main account can can be transferred. The balance of the free resource account and bonuses cannot be transferred. The common balance transfer processes are as follows: l

Process of transferring a balance through the IVR

l

Process of transferring a balance through the USSD

l

Process of transferring a balance through the WebService interface

l

Process of transferring a balance on the SMAP

The following sections describe each balance transfer process in detail.

7.2 Process of Transferring a Balance Through the IVR This section describes the process of transferring a balance through the IVR. Figure 7-1 shows the process of transferring a balance through the IVR.

7-2


Issue 01 (2010-07-28)



Figure 7-1 Process of transferring a balance through the IVR SCP

BMP

CBPo(out)

CBPi(in)

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber selects to transfer the balance

Send request of checking whether subscriber needs to be charged Return result

Play voice to notify subscriber of fee to be deducted Subscriber confirms fee

Balance transfer request

Check whether subscriber needs to be charged

Analyzes the balance transfer message IDL balance transfer start request

Return result

Perform the authentication and balance transfer. Deducts the handling fee

Balance transfer start request Return result Balance transfer stop request

Return result IDL balance transfer stop request Return result Return result

Balance transfer Submit the balance transfer transaction and writing CDRs

Submit the balance transfer transaction, writes CDRs

Return result

The process description is as follows: 1.

A subscrib subscriber er dials dials the the IVR IVR access access code, code, applying applying for a balance balance trans transfer. fer.

2.

The SCP SCP interac interacts ts with with the subscr subscriber iber by by playing playing a voice. voice. (See the first first dotted dotted box in red in the preceding figure.) The subscriber selects to transfer the balance.

3.

The SCP sends sends a fee query query reques requestt to the BMP. BMP.

Issue 01 (2010-07-28)


7-3



4.

The BMP receives receives the the request, request, queries queries the the fees, fees, determin determines es whether whether the the subscriber subscriber needs needs to be charged for the balance transfer, and then returns a result to the SCP.

5.

The SCP SCP perform performss operatio operations ns accordi according ng to the result result from the BMP BMP as follows: follows: l

l

If the subscriber does not need to be charged, the SCP directly sends the balance transfer request to the BMP to proceed with the operations in step 6. If the subscriber needs to be charged, the operations in the second dotted red box in the preceding preceding figure are figure are performed. The SCP plays a voice to notify the subscriber of the fee to be deducted for the balance transfer. After the subscriber confirms the fee deduction, the SCP sends the balance transfer request to the BMP.

6.

The BMP analyz analyzes es the the bala balance nce transf transfer er messag message. e.

7.

The BMP BMP sends sends an an IDL IDL balanc balancee transf transfer er star startt reques requestt to CBP CBP o of the transfer-out party.

8.

Afte Afterr rec recei eivi ving ng the the req reque uest st,, CBP CBPo performs the authentication and balance transfer. If any handling fee needs to be deducted according to the result of fee query, CBP o also deducts the handling fee, and then returns the processing result to the BMP.

9.

The BMP BMP receive receivess the result, result, and then then sends sends a balanc balancee transfer transfer start start reques requestt to CBPi of the transfer-in party for the balance transfer.

10. CBPi performs the balance transfer, and then returns the result to the BMP. 11. The BMP receiv receives es the result, result, and then then sends a balance balance transfe transferr stop request request to CBPi of the transfer-in party for submitting the balance transfer transaction and writing CDRs. 12. CBPi submits the balance transfer transaction, writes CDRs, and returns the result to the BMP. 13. The BMP receive receivess the result, result, and then sends sends an IDL balance balance transfer transfer stop stop request request to CBPo of the transfer-out party for submitting the balance transfer transaction. 14. CBPo submits the balance transfer transaction, writes CDRs, and returns the result to the BMP. 15. The BMP returns returns the balanc balancee transfer transfer result result to to the SCP. SCP. 16. The SCP returns the balance transfer result result to the the subscriber. subscriber. The process of transferring a balance through the IVR IVR ends.

7.3 Process of Transferring a Balance Through the USSD This section describes the process of transferring a balance through the USSD. The process of transferring a balance through the USSD varies according to network connection, and can be divided into the following categories: l

Process triggered in U-CSI mode

l

Process triggered in MAP mode

The specific triggering mode of a process depends on the actual network deployment.

Process of Transferring a Balance Through the USSD (Triggered in U-CSI Mode) Figure 7-2 shows the process of transferring a balance through the USSD (triggered in U-CSI mode). 7-4


Issue 01 (2010-07-28)



Figure 7-2 Process of transferring a balance through the USSD (triggered in U-CSI mode) MSC/VLR/SSP

SCP

BMP

CBPo(out)

CBPi(in)

Apply for balance balance transfer through the USSD U-CSI triggers service Apply for balance transfer through Send request of the USSD checking whether subscriber needs to be charged Return result Notify subscriber of Notify subscriber fee to be deducted of fee to be deducted Subscriber confirms fee Subscriber confirms fee



Analyzes the balance transfer message IDL balance transfer start request Return result


Balance transfer start request Return result Balance transfer stop request Return result IDL balance transfer stop request Return result Return result




The process of transferring a balance through the USSD (triggered in U-CSI mode) is similar to the process of transferring a balance through the IVR. During the process, the SCP queries fees from the BMP. If any fee needs to be deducted, the SCP confirms the fee deduction with the subscriber. Then, the CBPo of the transfer-out party deducts the fee. For process details, see 7.2 Process of Transferring a Balance Through the IVR .

Issue 01 (2010-07-28)


7-5



Process of Transferring a Balance Through the USSD (Triggered in MAP Mode) Figure 7-3 shows the process of transferring a balance through the USSD (triggered in MAP mode). Figure 7-3 Process of transferring a balance through the USSD (triggered in MAP mode) MSC/VLR/SSP

HLR

SCP

BMP

Apply for balance transfer through the USSD Apply for balance transfer through Apply for the USSD balance transfer Send request of through USSD checking whether subscriber needs to be charged Return result Notify subscriber Notify subscriber of fee to be of fee to be deducted deducted Subscriber confirms fee

Subscriber confirms fee

CBPo(out)

CBPi(in)


Notify subscriber of fee to be deducted



Analyzes the balance transfer message IDL balance transfer start request Return result


Balance transfer start request Return result

Balance transfer

Submit the balance transfer Return result transaction and writing Submit the CDRs balance transfer transaction, writes CDRs

Balance transfer transfer stop request

IDL balance transfer stop request Return result Return result

Return result

Return result

Return result

The process of transferring a balance through the USSD (triggered in MAP mode) is similar to the process of transferring a balance through the USSD (triggered in U-CSI mode). During the process, the SCP performs performs a fee query query on the BMP. If any fee needs to be deducted, deducted, the SCP confirms the fee deduction with the subscriber. Then, CBPo of the transfer-out t ransfer-out party deducts the 7-6


Issue 01 (2010-07-28)



fee. For process details, see Process of Transferring a Balance Through the USSD (Triggered in U-CSI Mode).

7.4 Process of Transferring a Balance Through the WebService Interface This section describes the process of transferring a balance through the WebService interface. interface. Figure 7-4 shows the process of transferring a balance through the WebService interface. interface. Figure 7-4 Process of transferring a balance through the WebService interface External system

BMP

Subscriber applies for balance transfer Balance transfer request

CBPo(out)

Analyzes the balance transfer message IDL balance transfer start request Return result Balance transfer start request

CBPi(in)


Return result Balance transfer stop request Return result IDL balance transfer stop request Return result Return result



Return result


A subscribe subscriberr applies applies for for a balanc balancee transfer transfer.. The reque request st is sent sent to an an external external system. system.

2.

The exte externa rnall system system send sendss the subs subscri criber ber requ request est to to the BMP. BMP.

3.

The BMP BMP analyzes analyzes the balanc balancee transfer transfer message, message, and and checks checks whethe whetherr any fee needs needs to to be deducted.

4.

The BMP BMP sends sends an an IDL IDL balanc balancee transf transfer er star startt reques requestt to CBP CBP o of the transfer-out party.

5.

Afte Afterr rec recei eivi ving ng the the req reque uest st,, CBP CBPo performs the authentication and balance transfer. If any handling fee needs to be deducted, CBP o also deducts the handling fee, and then returns the processing result to the BMP.

Issue 01 (2010-07-28)


7-7



6.

The BMP BMP receive receivess the result, result, and then then sends sends a balanc balancee transfer transfer start start reques requestt to CBPi of the transfer-in party for the balance transfer.

7.

CBPi performs the balance transfer, and then returns the result to the BMP.

8.

The BMP BMP receives receives the result, result, and then then sends sends a balance balance transf transfer er stop stop request request to CBPi of the transfer-in party for submitting the balance transfer transaction and writing CDRs.

9.

CBPi submits the balance transfer transaction, writes CDRs, and returns the result to the BMP.

10. The BMP receive receivess the result, result, and then sends sends an IDL balance balance transfer transfer stop stop request request to CBPo of the transfer-out party for submitting the balance transfer transaction. 11. CBPo submits the balance transfer transaction, writes CDRs, and returns the result to the BMP. 12. The BMP return returnss the balance balance transfer transfer result result to the the external external system. system. 13. The external external system system returns returns the result result to the subscriber subscriber.. The process process of transferrin transferring ga balance through the WebService WebService interface interface ends.

7.5 Process of Transferring a Balance on the SMAP This section describes the process of transferring a balance on the SMAP. Figure 7-5 shows the process of transferring a balance on the SMAP. Figure 7-5 Process of transferring a balance on the SMAP SMAP

BMP

Subscriber applies for balance transfer Balance transfer request

CBPo(out)

Analyzes the balance transfer message IDL balance transfer start request Return result Balance transfer start request

CBPi(in)


Return result Balance transfer stop request Return result IDL balance transfer stop request Return result Return result



Return result

7-8


Issue 01 (2010-07-28)



The process of transferring a balance on the SMAP is similar to the process of transferring a balance through the WebService WebService interface. interface. After a subscriber applies for a balance transfer, transfer, an operator handles the request on the SMAP. By invoking the WebSservice interface, the operator transfers the balance for the subscriber on the BMP and CBP. If any handling fee needs to be deducted, CBPo of the transfer-out party deducts the handling fee. For process details, see 7.4 Process of Transferring a Balance Through the WebService Interface .

7.6 Reference This section describes the terms used in balance transfer processes. None.

Issue 01 (2010-07-28)


7-9


8 Monthly Settlement Processes

8

Monthly Settlement Processes

About This Chapter

8.1 Overview Monthly settlement refers to one-off fee deduction performed by the OCS system at specified intervals. 8.2 Monthly Settlement Process This section describes the typical monthly settlement process. 8.3 Process of of Notifying a Subscriber of the Monthly Settlement by Short Message After the monthly monthly settlement, settlement, the system sends a short message to a subscriber. This section describes the process of notifying a subscriber of the monthly settlement by short message. 8.4 Reference Referenc e This section describes the terms used in the monthly settlement processes.

Issue 01 (2010-07-28)


8-1



8.1 Overview Monthly settlement refers to one-off fee deduction performed by the OCS system at specified intervals. This section describes the following processes related to monthly settlement: l

Monthly settlement process This section describes the process of performing the monthly settlement of the OCS system.

l

Process of notifying a subscriber of the monthly settlement by short message This section describes the process of notifying a subscriber of the monthly settlement by short message.

8.2 Monthly Settlement Process This section describes the typical monthly settlement process. The monthly settlement process is i s a periodical charging process. After a subscriber subscribes to a product, the monthly settlement of the product is performed on a specified date of a period. The scheduled transaction mechanism inside the OCS system triggers the monthly settlement and settles the monthly rental of the product. Bill cycle refers to a period for charging and bill run.

8.3 Process of Notifying a Subscriber of the Monthly Settlement by Short Message After the monthly settlement, the system sends a short message to a subscriber. This section describes the process of notifying a subscriber of the monthly settlement by short message. Figure 8-1 shows the process of notifying a subscriber of the monthly settlement by short message. Figure 8-1 Process of notifying a subscriber of the monthly settlement by short message SMSC

Send SMS notification

GFEP


SSMFEP


RBI

Monthly settlement SMS file

CBP

Obtain monthly settlement SMS file

Generate monthly settlement SMS file



Issue 01 (2010-07-28)



1.

The OCS OCS system system periodi periodically cally runs or or triggers triggers in real real time the the monthly monthly settle settlement ment proce process ss of a subscriber. Then the CBP writes a monthly settlement short message to a monthly settlement SMS file.

2.

The RBI RBI obtains obtains the monthly monthly settleme settlement nt SMS file from the the CBP periodica periodically lly and and sends sends the file to the SSMFEP. Generally, the SSMFEP is deployed on the SCP.

3.

The SSMF SSMFEP EP sends sends the the month monthly ly settle settlemen mentt SMS file file to the the GFEP. GFEP.

4.

The GFEP GFEP sends sends the the monthly monthly settleme settlement nt SMS file to to the SMSC, SMSC, and and the SMSC delivers delivers the monthly settlement SMS file to the subscriber. Then the process of notifying a subscriber of the monthly settlement by short message is complete.

8.4 Reference This section describes the terms used in the monthly settlement processes. None.

Issue 01 (2010-07-28)


8-3


9 Registration and Deregistration Processes

9

Registration and Deregistration Processes

About This Chapter

9.1 Overview OCS provide GUI/Web Service interface to create a new subscriber. 9.2 Subscriber Registration Processes While creating subscriber, user has to provide the information of the customer. After the operation is complete, the customer information, subscriber information, and account information f or or the new subscriber are generated. 9.3 Subscriber Deregistration Processes The OCS system system provides the deregistration function and a scheduled task for clearing deregistration data deregistration data periodically. 9.4 Reference This section describes the terms used in the registration and deregistration processes.

Issue 01 (2010-07-28)


9-1



9.1 Overview OCS provide GUI/Web Service interface to create a new subscriber. This section describes the processes of registering and deregistering an OCS subscriber and the processes of registering registering and deregistering OCS subscribers in batches. batches.

9.2 Subscriber Registration Processes While creating subscriber, user has to provide the information of the customer. After the operation is complete, the customer information, subscriber information, and account information for the new subscriber are generated.

9.2.1 Process of Registering a Subscriber Figure 9-1 shows the process of registering a subscriber. Figure 9-1 Process of registering a subscriber CRM

BMP

CBP

SCP

Registration request Registration request Verify Synchronize registration data

Process registration request

Return result

Synchronize registration data Return result




A user requests requests being being registe registered red as as an OCS OCS subscribe subscriber. r. The registrati registration on request request reach reaches es the CRM system.

2.

The CRM CRM syste system m forwar forwards ds the the regis registra tratio tion n reque request st to the the BMP. BMP.

3.

After receiving receiving the regist registratio ration n request request,, the BMP verif verifies ies the the user user data. data. The user data that needs to be verified includes the current resources, main product, and account of the user. The subsequent registration processing can be performed only when the user data is correct.

9-2


Issue 01 (2010-07-28)



4.

After the user user data data passes passes the the verific verification ation,, the BMP BMP reques requests ts the CBP to synchroniz synchronizee the user data.

5.

The CBP CBP register registerss the user user as as an OCS OCS subscrib subscriber er and and returns returns the the processi processing ng result result to the BMP.

6.

The BMP BMP forward forwardss the regist registratio ration n request request to the SCP. SCP. After After recei receiving ving the the registra registration tion request, the SCP synchronizes the user data and returns the processing result to the BMP.

7.

The BMP BMP returns returns the the proces processing sing result result to the CRM system, system, and and the CRM system system return returnss the processing result to the user. Then the process of registering a subscriber is complete.

9.2.2 Process of Registering Subscribers in Batches Figure 9-2 shows the process of registering subscribers in batches. Figure 9-2 Process of registering subscribers in batches CRM

BMP

CBP

SCP

FTP: Batch registration file Batch registration request Request response Verify Synchronize registration data

Return result


Synchronize registration data Return result


Return result


The CRM CRM system system trans transfers fers the batch batch registrat registration ion file file to the BMP BMP through through FTP.

2.

After transferr transferring ing the batch registrati registration on file, file, the CRM system system sends sends a request request of registe registering ring subscribers in batches to the BMP again.

3.

After After recei receivin ving g the reque request, st, the the BMP resp respond ondss to the requ request est..

4.

After the user data passes data passes the verification, verification, the BMP requests the CBP to synchronize the user data.

5.

The CBP CBP register registerss the users users as as OCS subscr subscribers ibers and return returnss the proce processing ssing result result to the BMP.

6.

The BMP BMP forward forwardss the regist registratio ration n request request to the SCP. SCP. After After recei receiving ving the the registra registration tion request, the SCP synchronizes the user data and returns the processing result to the BMP.

Issue 01 (2010-07-28)


9-3



7.

The BMP BMP returns returns the the process processing ing result result to the CRM CRM system. system. Then Then the process process of registerin registering g subscribers in batches is complete.

9.3 Subscriber Deregistration Processes The OCS system provides the deregistration function and a scheduled task for clearing deregistration data deregistration data periodically. periodically.

9.3.1 Process of Deregistering a Subscriber Figure 9-3 shows the process of deregistering a subscriber. Figure 9-3 Process of deregistering a subscriber CRM Deregistration request

BMP

CBP

SCP

Deregistration request Process deregistration request Deregistration request

Process deregistration request

Return result

Deregistration request Return result Return result


Return result


A subscribe subscriberr requests requests being deregiste deregistered. red. The deregis deregistrati tration on request request reaches reaches the the CRM system.

2.

The CRM CRM syste system m forwar forwards ds the the deregi deregistr strati ation on reque request st to the the BMP. BMP.

3.

The BMP BMP process processes es the deregistr deregistration ation request request and and requests requests the CBP CBP to deregis deregister ter the the subscriber.

4.

The CBP CBP processe processess the dereg deregistra istration tion request request and return returnss the proce processing ssing result result to the the BMP.

5.

The BMP BMP requests requests the the SCP to to deregister deregister the subscri subscriber. ber. The The SCP deregiste deregisters rs the subscr subscriber iber and returns the processing result to the BMP.

6.

The BMP BMP returns returns the the proces processing sing result result to the CRM system, system, and and the CRM system system return returnss the processing processing result result to the subscriber. Then the process of deregistering a subscriber is complete.

9.3.2 Process of Deregistering Subscribers in Batches Figure 9-4 shows the process of deregistering subscribers in batches. 9-4


Issue 01 (2010-07-28)



Figure 9-4 Process of deregistering subscribers in batches CRM

BMP

Send deregistration data Deregistration request

CBP

SCP

Retrieve deregistration data

Process deregistration request Deregistration request Return result


Deregistration request Return result


Return result


The BMP BMP retriev retrieves es in batche batchess the data data of of the subsc subscriber riberss to be deregiste deregistered red and and sends sends the subscriber data to the CRM system as a file.

2.

After receiving receiving the subscr subscriber iber data, data, the CRM CRM system system sends sends a batch batch deregis deregistrati tration on request request to the BMP.

3.

The BMP processe processess the batch batch deregis deregistrati tration on request request and and requests requests the the CBP to to deregiste deregisterr the subscribers in batches.

4.

The CBP CBP processe processess the batch batch dereg deregistra istration tion reque request st and returns returns the processing processing result result to the BMP.

5.

The BMP requests requests the SCP to dereg deregister ister the subscriber subscriberss in batches. batches.

6.

The SCP SCP deregiste deregisters rs the subscribe subscribers rs in batches batches and return returnss the proce processing ssing result result to the BMP. The BMP returns the processing result to the CR M system. Then the process of deregistering subscribers in batches is complete.

9.4 Reference This section describes the terms used in the registration and deregistration processes. None.

Issue 01 (2010-07-28)


9-5


10 Password Change Processes

10

Password Change Processes

About This Chapter

10.1 Overview This section describes the password change processes of the OCS system. 10.2 Process of Changing a Password Through the WebService Interface This section describes the pr ocess ocess of changing a password through the WebService interface. 10.3 Process of Changing a Password on the SMAP This section describes the process of changing a password on the SMAP. 10.4 Process of Changing a Password Through USSD This section describes the process of changing a password through USSD. 10.5 Process of Changing a Password Through IVR This section describes the process of changing a password through IVR. 10.6 Reference Reference This section describes the terms used in the password change processes.

Issue 01 (2010-07-28)


10-1



10.1 Overview This section describes the password change processes of the OCS system. OCS subscribers must enter their personal service passwords when applying for services. The subscribers can change their passwords in any of the following modes: l

Through the WebService interface

l

On the SMAP

l

Through USSD

l

Through IVR

The following sections describe each password change process in detail.

10.2 Process of Changing a Password Through the WebService Interface This section describes the process of changing a password through the WebService interface. Figure 10-1 shows the normal process of changing a password through the WebService interface. Figure 10-1 Normal process of changing a password through the WebService interface Third-party BMP platform Password change request Password change request Return result

Verify and change password

Return result


10-2

1.

A subscriber subscriber sends a password password change change reque request. st. The request request reache reachess a third-par third-party ty platform. platform.

2.

The third-p third-party arty platfo platform rm forwar forwards ds the password password change change request request to the the BMP throu through gh the WebService interface.

3.

The BMP BMP verifies verifies the new new and old old password passwordss of the the subscribe subscriber. r. After After the the new and old old passwords pass the verification, verification, the BMP changes changes the password of the subscriber.

4.

After changing changing the the password password successfu successfully, lly, the the BMP returns returns the the processin processing g result result to the the third-party platform, and the third-party platform returns the processing result to the subscriber. Then the process of changing a password through the WebService interface interface is complete. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



10.3 Process of Changing a Password on the SMAP This section describes the process of changing a password on the SMAP. Figure 10-2 shows the normal process of changing a password on the SMAP. Figure 10-2 Normal process of changing a password on the SMAP SMAP Password change request

BMP

Password change request Return result

Verify and change password

Return result


A subscr subscribe iberr sends sends a pass passwor word d change change requ request est on on the SMAP SMAP..

2.

The SMAP SMAP forwards forwards the the request request to the the BMP through through the WebServic WebServicee interfac interface. e.

3.

The BMP BMP verifies verifies the new new and old old password passwordss of the the subscribe subscriber. r. After After the the new and old old passwords pass the verification, verification, the BMP changes changes the password of the subscriber.

4.

After changing changing the the password password successfu successfully, lly, the the BMP returns returns the the processin processing g result result to the the SMAP, and the SMAP returns the processing result to the subscriber. Then the process of changing a password through the WebService interface is complete.

10.4 Process of Changing a Password Through USSD This section describes the process of changing a password through USSD. Figure 10-3 shows the normal process of changing a password through USSD.

Issue 01 (2010-07-28)


10-3



Figure 10-3 Normal process of changing a password through USSD MSC/VLR/SSP

SCP

BMP

Send USSD password change request U-CSI triggers service Send USSD password change request Verify password consistency Password change request Return result Return result

Verify old password and change password

Return result


A subscriber subscriber sends a USSD USSD password password change change request. request. The request request reache reachess the MSC/VL MSC/VLR/ R/ SSP. The password change request contains the USSD access code, old password of the subscriber, and new password of the subscriber.

2.

The MSC/VLR MSC/VLR/SSP /SSP triggers triggers the the USSD USSD service service according according to the U-CSI U-CSI and forwards forwards the the password change request request to the SCP.

3.

After receiving receiving the the request, request, the the SCP check checkss whether whether the subscr subscriber iber can can change change the password password and whether the old and new passwords of the subscriber are correct.

4.

After the passwor password d verifica verification tion is passed, passed, the SCP sends sends an an RCOMM RCOMM message message to to request request the BMP to change the password.

5.

The BMP BMP verifies verifies the old old password password.. After After the old passwor password d passes passes the verificati verification, on, the BMP changes the password of the subscriber and returns the processing result to the SCP.

6.

The SCP SCP returns returns the proce processing ssing result result to the the MSC/VLR MSC/VLR/SSP /SSP,, and the MSC/VL MSC/VLR/SS R/SSP P returns the processing result to the subscriber. Then the process of changing a password through USSD is complete.

10.5 Process of Changing a Password Through IVR This section describes the process of changing a password through IVR. Figure 10-4 shows the normal process of changing a password through IVR.

10-4


Issue 01 (2010-07-28)



Figure 10-4 Normal process of changing a password through IVR MSC/VLR/SSP Subscriber dials IVR access code

SCP

BMP

CBP

IDP RRBE CCR{Event} Authenticate CCA{Event}

Play voice to collect old and new passwords of subscriber Subscriber enters old and new passwords Verify password consistency Password change request Password change response Play voice to indicate password change result

Verify old password and change password

PA



2.

The MSC/VLR/ MSC/VLR/SSP SSP report reportss an IDP IDP message message to trigger trigger the call to the SCP SCP of the the home area. area.

3.

The SCP return returnss an RRBE RRBE mess message age to the the MSC/V MSC/VLR/ LR/SSP SSP..

4.

The SCP SCP sends sends a CCR{Eve CCR{Event} nt} message message to request request the CBP CBP to authen authenticat ticatee the subscr subscriber iber state.

5.

The CBP CBP authenti authenticates cates the subscri subscriber ber state state and and sends sends a CCA{Eve CCA{Event} nt} message message containing containing the authentication result to the SCP. The subscriber can perform the subsequent password change operations only after the subscriber state passes the authentication.

6.

The SCP SCP also also plays plays the relate related d voices voices to inter interact act with with the subscriber subscriber according according to the authentication result returned by the CBP to obtain the old and new passwords of the subscriber. The dotted red box in Figure 10-4 shows the interactions.

7.

The subs subscri criber ber ente enters rs the old old and and new pass passwor words ds as promp prompted ted..

8.

The SCP SCP checks checks whethe whetherr the subscr subscriber iber can can change change the passwor password d and whether whether the the new password and confirm confirm password are the same. same.

9.

If the verificati verification on is passed, passed, the SCP SCP forwar forwards ds the password password request request to the BMP.

10. The BMP verifies verifies the old old password password of the subscriber subscriber.. If the old password password is correct, correct, the BMP changes the password of the subscriber. 11. The BMP returns returns the passwo password rd change change result result to the the SCP. SCP. Issue 01 (2010-07-28)


10-5



12. The SCP deliver deliverss a voice to the MSC/VLR/S MSC/VLR/SSP SP accordin according g to the password password change change result, result, and the MSC/VLR/SSP plays the voice to notify the subscriber of the password change result. Then the process of changing a password through IVR is complete.

10.6 Reference This section describes the terms used in the password change processes. None.

10-6


Issue 01 (2010-07-28)


11 MMS Charging Processes

11

MMS Charging Processes

About This Chapter

11.1 Overview This section describes the terms related to multimedia message service (MMS) charging and the classifications of MMS charging processes. 11.2 Process of Charging for the MMS Service Through DCC This section describes the process of charging for the MMS service online through DCC. 11.3 Process of Charging for the MMS Service Through EMPP This section describes the process of charging for the MMS service online through EMPP. 11.4 Reference This section describes the terms used in the charging processes of MMS.

Issue 01 (2010-07-28)


11-1



11.1 Overview This section describes the terms related to multimedia message service (MMS) charging and the classifications of MMS charging processes. The MMS service can be charged online through any of the following protocols: l

DCC

l

EMPP

The following sections describe each charging process of the data service in detail.

11.2 Process of Charging for the MMS Service Through DCC This section describes the process of charging for the MMS service online through DCC. Figure 11-1 shows the normal process of charging for the MMS service online through DCC. Figure 11-1 Normal process of charging for the MMS service online through DCC MMSC

CBP

MMS charging request CCR{Event} Charge CCA{Event} Deliver to called party CCR{Event} CCA{Event}

MMSC MMSC

Refund

Mult Multim imed edia ia Mes Messa sagi ging ng Ser Servi vice ce Cen Cente ter r


11-2

1.

A subscrib subscriber er sends sends a multimedia multimedia message. message. The The MMS MMS charging charging request request reache reachess the MMSC.

2.

The MMSC MMSC send sendss a CCR{Ev CCR{Event ent} } messag messagee to the the CBP for char chargin ging. g.

3.

The CBP CBP processes processes the chargi charging ng request request and and sends sends a CCA{Even CCA{Event} t} message message contai containing ning the the processing result to the MMSC. MMSC.

4.

After receiving receiving the result result indica indicating ting that that the charging charging is is successf successful, ul, the MMSC sends sends a multimedia message to the called subscriber.


Issue 01 (2010-07-28)



5.

If the subscriber subscriber fails to send send the multime multimedia dia message message,, the multime multimedia dia message message fee needs needs to be refunded. Then the operations in the dotted red box in Figure 11-1 are performed, the MMSC sends a CCR{Event} message to the CBP for refund.

6.

The CBP CBP processe processess the refund refund request request and sends a CCA{Even CCA{Event} t} message message contai containing ning the the processing result to the MMSC. MMSC. Then Then the process of charging charging for the MMS MMS service service through DCC is complete.

11.3 Process of Charging for the MMS Service Through EMPP This section describes the process of charging for the MMS service online through EMPP. Figure 11-2 shows the normal process of charging for the MMS service online through EMPP. Figure 11-2 Normal process of charging for the MMS service online through EMPP MMSC MMS charging request

GFEP

CBP

MMS charging request CCR{Event}

Request response

CCA{Event}

Authentication, Rating and fee deduction

confirm/refund request CCR{Event} Request response

CCA{Event}

Confirm charging and refund

NOTE

During the process of charging for the MMS service online through EMPP, the MMSC registers itself on the GFEP when attempting to connect to the GFEP. After the MMSC registers itself on the GFEP successfully, the connection between the MMSC and GFEP is created successfully. Then the GFEP converts the EMPP protocol to a DCC message and sends the DCC message to the CBP for authentication. After the authentication is passed, the subsequent charging operations can be performed normally.

The process is is described as as follows: 1.

A subscrib subscriber er sends sends a multimedia multimedia message. message. The The MMS MMS charging charging request request reache reachess the MMSC.

2.

The MMSC MMSC forw forward ardss the charg charging ing requ request est to to the GFEP GFEP thro through ugh EMPP EMPP..

3.

The GFEP GFEP converts converts the the protoco protocoll and sends sends a CCR{Eve CCR{Event} nt} messag messagee to the CBP CBP to apply for authorization, rating and charging.

4.

After receiving receiving the message message,, the CBP proces processes ses the the charging charging request request and and sends sends a CCA {Event} message containing the processing result to the GFEP.

Issue 01 (2010-07-28)


11-3



5.

The GFEP GFEP retur returns ns the the proc process essing ing result result to the the MMSC MMSC..

6.

After receiving receiving the process processing ing result result return returned ed by the CBP, CBP, the GFEP sends a CCR{Event CCR{Event} } message to request the CBP to confirm the charging. If the multimedia message fee needs to be refunded, the GFEP sends a CCR{Event} message to the CBP for refund.

7.

The CBP CBP confirms confirms the chargi charging ng or refunds refunds the fee, and then then sends sends a CCA{Eve CCA{Event} nt} message message containing the processing result to the GFEP.

8.

Then the the proces processs of chargi charging ng for the MMS MMS service service online through through EMPP EMPP is comple complete. te.

11.4 Reference This section describes the terms used in the charging processes of MMS. None.

11-4


Issue 01 (2010-07-28)


12 GPRS Charging Processes

12

GPRS Charging Processes

About This Chapter

12.1 Overview This section describes the terms related to the GPRS service charging and the classifications of GPRS charging processes. 12.2 Process of Charging for the GPRS Service Through DCC OCS communicates with external data service components through Diameter and performs real time authentication authentication and charging for data services. 12.3 Process of Charging for the GPRS Service Through CAMEL3 OCS communicates communicates with external data service components through Diameter and performs real time authentication authentication and charging for data services. 12.4 Reference This section describes the terms used in the charging processes of GPRS.

Issue 01 (2010-07-28)


12-1



12.1 Overview This section describes the terms related to the GPRS service charging and the classifications of GPRS charging processes. The GPRS service can be charged online through any of the following protocols: l

DCC

l

CAMEL3

The following sections describe each charging process of the data service in detail.

12.2 Process of Charging for the GPRS Service Through DCC OCS communicates with external data service components through Diameter and performs real time authentication and charging for data services. Figure 12-1 shows the process of charging for the GPRS service through DCC.

12-2


Issue 01 (2010-07-28)



Figure 12-1 Process of charging for the GPRS service through DCC SGSN Activate PDP Context Request

GGSN

CBP

Create PDP Context Request CCR{Initial}

Activate PDP Context Response Use service

CCA{Initial}

Create PDP Context Response

Authentication , rating and reservation

Data Traffic Delivery Monitor traffic CCR{update} CCA{update}

Rating,charging and reservation Repeatable

Deactivate PDP Context Request Delete PDP Context Request CCR{Terminate}

CCA{Terminate}

Rating,charging and terminate session

Delete PDP Context Response Deactivate PDP Context Response

SGSN

Serving GPRS Support Node

PDP

Packet Data Protocol


When a subscriber subscriber requests requests for for WAP/We WAP/Web b visit, visit, the SGSN SGSN detec detects ts PDP context context activati activation on request from MS (Mobile Station), then sends the Create PDP context request to GGSN.

2.

The GGSN GGSN analyzes analyzes the reque request st and and sends sends the the request request to the correspon corresponding ding CBP.

3.

After receiving receiving the the request, request, the the CBP perfo performs rms authent authenticati ication, on, rating, rating, and and reserva reservation, tion, and and sends a CCA{Initial} message containing the processing result to the GGSN.

4.

The The GGS GGSN N sen sends ds the the resu result lt to to the the SGS SGSN. N.

5.

The SGSN SGSN sends sends the result result to to the subscri subscriber. ber. Then Then the the subscribe subscriberr can use use the GPRS servic service. e.

6.

A data channel channel is establishe established d between between the the subscrib subscriber er and and the GGSN and thus thus the GGSN can monitor the service usage of the subscriber.

7.

When the alloca allocated ted duratio duration n is used used up, the GGSN GGSN sends sends a CCR{Up CCR{Update} date} message message to the the CBP to request more duration.

Issue 01 (2010-07-28)


12-3



8.

The CBP CBP debits debits the fees generated generated in the previous previous duratio duration n and perfo performs rms rating rating and reservation.

9.

The CBP CBP sends sends a CCA{Upd CCA{Update} ate} messag messagee containi containing ng the processin processing g result result to the the GGSN. GGSN. NOTE

Steps 7 to 9, that is, the processes described in the previous dotted box in red, can be repeated.

10. When the subscriber stops using the service, service, the SGSN receives receives a PDP context context deactivation deactivation request. 11. The SGSN SGSN sends the the request request of deleting deleting the the PDP context context to the the GGSN. GGSN. 12. The GGSN GGSN sends a CCR{Termina CCR{Terminate} te} message message to request request the CBP to confirm confirm the charging charging and write a CDR. 13. The CBP confirms confirms the the charging, charging, writes writes a CDR, and ends ends the session. session. In addition, addition, the CBP CBP sends a CCR{Terminate} message to return the processing result. 14. The GGSN GGSN sends sends PDP Contex Contextt Deletion Deletion Respons Responsee to the SGSN. SGSN. 15. The SGSN sends the PDP context context deactivation deactivation request to the subscriber. subscriber. Then Then the process of charging for the GPRS service through DCC is complete.

12.3 Process of Charging for the GPRS Service Through CAMEL3 OCS communicates with external data service components through Diameter and performs real time authentication and charging for data services. Figure 12-2 shows the process of charging for the GPRS service through CAMEL3.

12-4


Issue 01 (2010-07-28)



Figure 12-2 Process of charging for the GPRS service through CAMEL3 SGSN

SCP

CBP

GPRS use request InitialDP GPRS Request Report GPRS Event CCR{Initial} CCA{Initial}

Authentication, rating and reservation

ApplyChargingGPRS Continue GPRS Use GPRS ApplyCharging ReportGPRS CCR{update}

Rating, accounting CCA{update} and reservation

ApplyChargingGPRS

Repeatable

GPRS use ends EventReportGPRS CCR{Terminate} CCA{Terminate}

Rating, accounting and terminate session

Release GPRS

1.

When a subscriber subscriber requests requests for for WAP/We WAP/Web b visit, visit, the SGSN SGSN detec detects ts PDP context context activati activation on request.

2.

The SGSN SGSN trigger trigger the service service accordin according g to CSI, CSI, send InitialDP InitialDP GPRS GPRS message message to the SCP. SCP.

3.

The SCP SCP sends sends Requ Request est Repo Report rt GPRS GPRS Event Event oper operati ation on to the the SGSN. SGSN.

4.

The SCP SCP sends sends CCR{Ini CCR{Initial} tial} message message to the CBP CBP for for authent authenticati ication on and and reserva reservation. tion.

5.

The CBP CBP perform performss authentic authentication ation,, rating rating and and reservati reservation, on, and and then sends CCA{Initial} CCA{Initial} message to the SCP. l

If charge by time, the SCP sends Apply Charging GPRS with the monitoring time to the GGSN and sends Continue GPRS operation to home SGSN.

l

If charge by volume, the SCP sends Apply Charging GPRS with the monitoring traffic and time to the SGSN.

6.

The SCP SCP sends sends ContinueG ContinueGPRS PRS opera operation tion to instruct instruct the the SGSN SGSN to continue continue GPRS session session or PDP context processing.

7.

The SCP SCP sends sends ApplyCh ApplyChargi argingGPR ngGPRS S operati operation on to instruct instruct SGSN SGSN to monitor monitor the consumption of the subscriber.

8.

When When the allo alloca cated ted usag usagee slice slice has bee been n used used up, the the SGSN SGSN sends sends ApplyChargingReportGPRS to the SCP.

Issue 01 (2010-07-28)


12-5



9.

The SCP SCP sends sends CCR{Upd CCR{Update} ate} message message to CBP, reporting reporting used used volume volume/time /time and reque request st for reservation again.

10. The CBP processes processes the charging charging request, request, performs performs debiting debiting on the previous previous applicatio application, n, makes new reservation for the subscriber, and returns a CCA{Update} message containing the processing result to the SCP. 11. The SCP sends sends ApplyCharg ApplyChargingGP ingGPRS RS operation operation to instruct instruct SGSN SGSN to monitor monitor the consumption of the subscriber. NOTE

The operations in the dotted red box in Figure 12-2 can be performed circularly according to the actual service usage of the subscriber until the subscriber exhausts the account balance.

12. When the the subscriber subscriber stops stops using using the GPRS GPRS service, service, the SGSN SGSN sends sends ApplyChargingReportGPRS and EventReportGPRS EventReportGPRS to the SCP. 13. The SCP sends sends CCR{Term CCR{Terminate inate} } message message to CBP, reportin reporting g used volume. volume. 14. The CBP commits commits the charge charge according according to the message message,, and then sends sends a CCA{Terminate CCA{Terminate} } message containing the processing result to the SCP. 15. The SCP sends sends ReleaseGP ReleaseGPRS RS to tear down down the existing existing GPRS Session Session or PDP. PDP. Then the process of charging for the GPRS service service through CAMEL3 is complete. complete.

12.4 Reference This section describes the terms used in the charging processes of GPRS. The GPRS-related 3GPP CAMEL phase 3 series standards are as follows:

12-6

l

3GPP TS 29.078 V4.4.0 (2002-03) Release 4

l


l

3GPP TS 23.078 V4.4.0 (2002-03) Release 4


Issue 01 (2010-07-28)


13

13 International Roaming Service Processes

International Roaming Service Processes

About This Chapter

13.1 Overview This section describes interface roaming services and the main processes related to the services. 13.2 Process of Charging for an International Roaming Call This section describes the process of charging for an international roaming call. 13.3 Process of Charging for an International Short Message This section describes the process of charging for an international short message based on the SMPP+ protocol. protocol. 13.4 Reference This section describes describes the terms used in the charging processes of international roaming service.

Issue 01 (2010-07-28)


13-1



13.1 Overview This section describes interface roaming services and the main processes related to the services. Common international roaming services are as follows: l

Call service

l

SMS

The following sections describe these services.

13.2 Process of Charging for an International Roaming Call This section describes the process of charging for an international roaming call. An international roaming call can be charged in either of the following modes: l

CAMEL2 mode

l

USSD Call Back (UCB) mode

The following sections describe the process of charging for an international roaming call in each mode.

13.2.1 Process of Charging for an International Roaming Call in CAMEL2 Mode Figure 13-1 shows the normal process of charging for an international roaming call in CAMEL2 mode. Assume that:

13-2

l

MSC/VLR/SSP MSC/VLR/SSP is the the visited country of subscriber A.

l

SCPa and CBPa are the home SCP and CBP of subscriber A.


Issue 01 (2010-07-28)



Figure 13-1 Normal process of charging for an international roaming call in CAMEL2 mode MSC/VLR/SSP

SCPa

CBPa

Subscriber makes a call Trigger call according to O-CSI IDP RRBE

Perform number analysis and basic authentication CCR{Initial}

CCA{Initial}


AC Continue Connect call ACR CCR{Update}

Perform rating debiting and budget 、

CCR ACK AC ACR Subscriber hangs up ERB CCR{Terminate}

CCR ACK

Perform rating and debiting

RC

The process of charging for an international roaming call in CAMEL2 mode is similar to the process of charging for an ordinary ordinary call. After subscriber A makes makes an international roaming call, the call reaches the MSC/VLR/SSP of the visited area. Then the MSC/VLR/SSP triggers the call to SCPa according to the O-CSI of subscriber A. For the subsequent process description, see the process of charging a calling party described in 2.2.1 Process of Charging a Call Between Two OCS Subscribers . NOTE

In the process of charging for an international roaming call in CAMEL2 mode, the carrier of the home network needs to sign a roaming agreement with the carrier of the visited network so that the CAMEL signaling of the visited network can communicate with the CAMEL signaling of the home network.

Issue 01 (2010-07-28)


13-3



13.2.2 Process of Charging for an International Roaming Call in UCB Mode The following problems exist when a prepaid subscriber roams internationally: l

The international roaming function cannot be enabled for the subscriber based on the credit of the subscriber.

l

The home SCP of the subscriber can be triggered through the Visited Mobile Switching Center (VMSC) only when the VMSC of the visited area supports the CAMEL2.

In this case, the carrier can enable the capability of only being a called party for the subscriber. The specific call process is: When an international roaming subscriber makes a call, a USSD request is sent to the home network of the subscriber. Then a special device is used to initiate two calls to the subscriber and to the called party respectively. When both the calling and called parties respond to the calls, calls, the special device connects the two calls calls so that the subscriber can can talk with the called party. This i s called the UCB scheme. Figure 13-2 shows the normal process of charging for an international roaming call in UCB mode. Assume that:

13-4

l

Subscriber A roams to another country.

l

Subscriber A makes an international roaming call to subscriber B.

l

Both subscriber A and subscriber B are OCS subscribers.


Issue 01 (2010-07-28)



Figure 13-2 Normal process of charging for an international roaming call in UCB mode MSC/VLR

SSP

SCPa

CBPa

HLRa

SCPb

CBPb

MSC/VLR b

Send USSD code Send USSD request Return result Return result Trigger call according to USSD code ICA RRBE/ Continue IDP CCR{Event} CCA{Event}

RRBE/AC /Continue


IAI ACK ERB ProvideAvail DN ACK Connect OnePort ACK ICA RRBE/ Continue IDP CCR{Event} CCA{Event}


RRBE/AC/Continue IAI ACK ERB ProvideAvail DN ACK Connect OnePort ACK

Issue 01 (2010-07-28)


13-5




Subscriber Subscriber A roams roams to anothe anotherr country country and and makes makes a USSD USSD call. call. The The call call reaches reaches the MSC/ MSC/ VLR of the visited area. The MSC/VLR of the visited area routes the USSD call to HLR a.

2.

HLRa routes the USSD call to SCP a.

3.

SCPa returns a USSD response to HLR a.

4.

HLRa returns a response to the MSC/VLR.

5.

SCPa sends the Initial Call Attempt (ICA), RRBE, and Continue messages to request the SSP to initiate a call to subscriber A (call A).

6.

The SSP SSP trigger triggerss the called called process process of subscribe subscriberr A and sends an IDP message message to SCP SCP a. In addition, the SSP sends a CCR{Event} message to CBPa to request authentication.

7.

Afte Afterr the the auth authen enti tica cati tion on is is pass passed ed,, CBP CBPa sends a CCA{Event} message to return the authentication result to SCPa.

8.

SCPa delivers the RRBE, AC, and Continue messages according to the returned authentication result.

9.

After receiving receiving the request request,, the SSP SSP sends sends an an Initial Initial Address Address Message Message with with Additiona Additionall Information (IAI) message to the MSC/VLR of the visited area to request the MSC/VLR to connect the call to subscriber A.

10. The MSC/V MSC/VLR LR returns returns an ACK ACK message message to the SSP. 11. After subscr subscriber iber A answers answers the call, call, the SSP reports reports an ERB ERB message message to notify SCPa that the call is connected to subscriber A successfully. 12. SCPa sends the ProvideAvailDN request to the SSP and applies to the SRF for an available DN. The DN functions as the unique identifier of call A. 13. The SSP SSP receives receives the the request request and delivers delivers a DN to to SCPa. 14. SCPa sends the ConnectOnePort request to the SSP to connect call A to the SRF resource. 15. The SSP receives the request, connects connects call A to the SRF resource, resource, and returns a result to SCPa. Then the call to subscriber A is initiated successfully. 16. The SSP SSP initiates initiates a call to subscribe subscriberr B (call (call B). SCP SCPa delivers the ICA, RRBE, and Continue messages to the SSP. 17. The SSP trigge triggers rs the called called process process of subscri subscriber ber B and sends sends an IDP messag messagee to SCP b. In addition, the SCP b sends a CCR{Event} message to CBP b to request authentication. 18. After the authentica authentication tion is passe passed, d, CBP CBP b sends a CCA{Event} message to return the authentication result to SCP b. 19. SCP b delivers the RRBE, AC, and Continue messages according to the returned authentication result. 20. After recei receiving ving the reque request, st, the SSP SSP sends an an IAI message message to MSC/VLR MSC/VLR b to request MSC/ VLR b to connect the call to subscriber B. 21. 21. The The MS MSC/V C/VLR b returns an ACK message to the SSP. 22. After subscr subscriber iber B answers answers the call, call, the SSP reports reports an ERB message message to notify notify SCPa that the call is connected to subscriber B successfully. 23. SCPa sends the ProvideAvailDN request to the SSP and applies to the SRF for an available DN. The DN functions as the unique identifier of call B. 13-6


Issue 01 (2010-07-28)



24. The SSP SSP receives receives the the request request and delivers delivers a DN to to SCPa. 25. SCPa sends the ConnectOnePort request to the SSP to connect call B to an SRF resource. 26. The SSP receive receivess the request, request, connects connects call call A with call B according according to the two DNs, DNs, and returns a result to SCP a. Then the call between subscriber A and subscriber B is connected. When the call ends, subscriber A is charged as a called party. Then the process of charging for an international roaming call in UCB mode is complete.

13.3 Process of Charging for an International Short Message This section describes the process of charging for an international short message based on the SMPP+ protocol.

13.3.1 Process of Charging for an International Short Message Based on SMPP+ This section describes the process of charging for an international short message based on SMPP +. Figure 13-3 shows the normal process of charging for an international short message based on SMPP+. Figure 13-3 Normal process of charging for an international short message based on SMPP+ MSC/VLR/SSP Send short message

SMSC

GFEP

Send SMS charging request SMPP+:send SMS charging request

SCP

RCOMM:send SMS charging request

CBP


Perform charging

Return result Return result Return result Return result

Deliver to called party Send refund request

Send refund request


Perform refund


Issue 01 (2010-07-28)


13-7




A subscriber subscriber sends an internati international onal roamin roaming g short short message. message. The The upstream upstream chargi charging ng request request of the short message reaches the MSC/VLR/SSP.

2.

The MSC/VLR/ MSC/VLR/SSP SSP of of the visite visited d country country routes routes the the short short message message chargi charging ng request request to the home SMSC of the subscriber.

3.


4.

The GFEP GFEP converts converts the charg charging ing request request to an RCOMM message message and and sends sends the the RCOMM RCOMM message to the home SCP.

5.

After receiving receiving the RCOMM RCOMM messa message, ge, the the SCP sends a CCR{Event} CCR{Event} message message to the home home CBP to initiate a charging request.

6.

The CBP CBP charges charges for the the short short message message and sends sends a CCA{Ev CCA{Event} ent} messag messagee to return return the the processing result to the SCP. SCP.

7.

The SCP SCP returns returns the charging charging result result to the GFEP. GFEP. Then Then the GFEP return returnss the chargin charging g result result to the SMSC.

8.

If the charging charging is successful successful,, the SMSC SMSC return returnss the charg charging ing result result to the MSC/VLR MSC/VLR/SSP /SSP and delivers the short message to the called party.

9.

The MSC/VLR MSC/VLR/SSP /SSP returns returns the charging charging result result to to the callin calling g party. party. Then Then the proce process ss of charging for an international short message based on the SMPP+ protocol is complete. NOTE

Refunds are required only when a short message fails to be sent. When a short message refund is required, the SMSC sends a refund request to request the CBP to perform the refund operation. The refund process is similar to the process of charging for a short message. For details, see the process in the dotted box in red, as shown in Figure 13-3.

13.4 Reference This section describes the terms used in the charging processes of international roaming service. None.

13-8


Issue 01 (2010-07-28)


14 FN Service Processes

14

FN Service Processes

About This Chapter

14.1 Overview This section describes the Familiarity Number (FN) service and the FN service processes. 14.2 Processes Processes of Enabling the FN Service for a Subscriber This section describes the pr ocesses ocesses of enabling the FN service for a subscriber. 14.3 Processes Processes of Disabling the FN Service for a Subscriber This section describes the processes of disabling the FN service for service for a subscriber. 14.4 Processes Processes of Adding or Changing an FN of a Subscriber This section describes the processes of adding or changing an FN of a subscriber. 14.5 Processes Processes of Querying an FN of a Subscriber This section describes the processes of querying an FN of a subscriber. 14.6 Reference Reference This section describes the terms used in the FN service processes.

Issue 01 (2010-07-28)


14-1



14.1 Overview This section describes the Familiarity Number (FN) service and the FN service processes. The FN service is a preferential service provided by the carrier to subscribers. When the FN service is enabled for a subscriber, the subscriber can set the frequently used numbers to FNs. After setting a number to an FN successfully and the setting takes effect, the subscriber can enjoy a discount or charge rate preference when making calls or sending short messages to this FN. The maximum number of FNs that an FN service subscriber can set is determined by the carrier. The common FN service processes are as follows: l

Processes of enabling the FN service for a subscriber

l

Processes of disabling the FN service for a subscriber

l

Processes of querying, adding or changing an FN of a subscriber

The FN service can be processed on the SMAP, through the WebService interface, interface, IVR, USSD, or short messages.

14.2 Processes of Enabling the FN Service for a Subscriber This section describes the processes of enabling the FN service for a subscriber. The FN service can be enabled through the WebService interface, IVR, on the SMAP, USSD, or short messages. The following sections describe each process in detail.

14.2.1 Process of Enabling the FN Service for a Subscriber Through IVR Figure 14-1 shows the normal process of enabling the FN service for a subscriber through IVR.

14-2


Issue 01 (2010-07-28)



Figure 14-1 Normal process of enabling the FN service for a subscriber through IVR SCP

BMP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to enable Send request of FN service checking whether subscriber needs to be charged Return result Play voice to notify subscriber of fee to be deducted Subscriber confirms fee


FN service request Verify data One-off fee deduction request Return result

Deduct fee

Enable FN service Return result Return result


A subscrib subscriber er dials dials the the IVR IVR access access code to subscri subscribe be to the FN FN service. service.

2.

The SCP SCP plays plays voices voices to to interact interact with with the subscribe subscriber. r. The first dotted dotted red box box in Figure 14-1 shows the interactions. Then the subscriber chooses to subscribe to the FN service.

3.

The SCP SCP request requestss the BMP BMP to check check whether whether the the subscrib subscriber er needs needs to be charge charged d for subscribing to the FN service.

4.

The BMP BMP determin determines es whether whether the the subscri subscriber ber needs needs to be charg charged ed for subscribin subscribing g to the the FN service and returns a result to the SCP.

5.

The SCP SCP processe processess the subscr subscription iption request request accordi according ng to the the result result return returned ed by the BMP. BMP.

Issue 01 (2010-07-28)

l

If the subscriber does not need to be charged for subscribing to the FN service, step 6 is proceeded with.

l

If the subscriber needs to be charged for subscribing to the FN service, the operations in the second dotted red box in Figure 14-1 are performed. The SCP plays a voice to notify the subscriber of the fee that needs to be deducted for the service subscription. After the subscriber confirms the fee deduction, step 6 is proceeded with. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

14-3



6.

The SCP forwar forwards ds the the subsc subscrip riptio tion n reque request st to the BMP. BMP.

7.

The The BMP BMP veri verifi fies es the the sub subsc scri ribe berr data data.. The subscriber data includes the MSISDN of the subscriber, subscriber state, operation type, and validity of the service ID, which are transferred by the interface.

8.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP sends sends a one-o one-off ff fee fee deductio deduction n request to the CBP to deduct the fee if the subscriber needs to be charged. After deducting the fee, the CBP returns the processing result to the BMP.

9.

The BMP enables enables the FN service service for for the subsc subscriber riber and returns returns the the process processing ing result result to the the SCP.

10. The SCP returns the processing result result to the subscriber. Then Then the process of enabling the FN service for a subscriber through IVR is complete.

14.2.2 Process of Enabling the FN Service for a Subscriber Through the WebService Interface Figure 14-2 shows the normal process of enabling the FN service for a subscriber through the WebService interface. Figure 14-2 Normal process of enabling the FN service for a subscriber through the WebService interface External BMP system Subscriber applies for FN service Subscriber

CBP

applies for FN service Verify data Authenticate One-off fee deduction request Return result

Deduct fee



14-4

1.

A subscribe subscriberr applies applies for for the FN service service.. The subsc subscriptio ription n request request reach reaches es an extern external al system.

2.

The extern external al system system forwards forwards the subsc subscriptio ription n request request to the BMP throug through h the changeservice interface of the WebService interface.

3.

The The BMP BMP veri verifi fies es the the sub subsc scri ribe berr data data.. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

Issue 01 (2010-07-28)



The subscriber data includes the MSISDN of the subscriber, subscriber state, operation type, and validity of the service ID, which are transferred by the interface. 4.

After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP authenti authenticates cates the subscrib subscriber. er. l

If the subscriber needs to be charged for subscribing to the FN service, the operations in the dotted red box in Figure 14-2 are performed. That is, the BMP invokes the oneoff real-time fee deduction interface to deduct the fee on the CBP.

l

If the subscriber does not need to be charged for subscribing to the FN service, step 5 is proceeded with.

5.

The BMP enables enables the FN service service for for the subsc subscriber riber and returns returns the the process processing ing result result to the the external system.

6.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of enabling the FN service for a subscriber through the WebService interface is complete.

14.2.3 Process of Enabling the FN Service for a Subscriber on the SMAP Figure 14-3 shows the normal process of enabling the FN service for a subscriber on t he SMAP. Figure 14-3 Normal process of enabling the FN service for a subscriber on the SMAP SMAP Subscriber applies for FN service

BMP

CBP

Subscriber applies for FN service Verify data Authenticate One-off fee deduction request Return result

Deduct fee



A subsc subscrib riber er appl applies ies for for the the FN servic servicee on the the SMAP SMAP..

2.

The SMAP SMAP sends sends subscr subscriber iber reques requests ts to the the BMP by invoking invoking the WebSer WebService vice interface interface (changeservice interface).

3.


Issue 01 (2010-07-28)


14-5



4.

After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP authenti authenticates cates the subscrib subscriber. er. If the subscriber needs to be charged for subscribing to the FN service, the operations in the dotted red box in Figure 14-3 are performed. That is, the BMP invokes the one-off realtime fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for subscribing to the FN service, step 5 is proceeded with.

5.

The BMP enables enables the FN service service for for the subsc subscriber riber and returns returns the the process processing ing result result to the the SMAP.

6.

The SMAP SMAP returns returns the the process processing ing result result to the the subscrib subscriber. er. Then Then the the process process of enabling enabling the the FN service for a subscriber on the SMAP is complete.

14.2.4 Processes of Enabling the FN Service for a Subscriber Through USSD This section describes the processes of enabling the FN service for a subscriber through USSD. The trigger modes of the processes of enabling the FN service for a subscriber through USSD include the following: l

In U-CSI mode

l

In MAP mode

The specific trigger mode of a process depends on the actual network deployment.

Process of Enabling the FN Service for a Subscriber Through USSD (Triggered in U-CSI Mode) Figure 14-4 shows the normal process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode).

14-6


Issue 01 (2010-07-28)



Figure 14-4 Normal process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode) MSC/VLR/SSP

SCP

BMP

CBP

Apply for FN service through USSD U-CSI triggers service Apply for FN service through USSD

Check whether subscriber needs to be charged Return result


Notify subscriber of Notify subscriber fee to be deducted of fee to be deducted Subscriber confirms fee


FN service request Verify data One-off fee deduction request Return result

Deduct fee

FN service request Return result

Enable FN service


The process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode) is similar to the process of enabling the FN service for a subscriber through IVR. In the process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode), the SCP determines whether the subscriber needs to be charged on the BMP. If yes, the SCP requests the subscriber to confirm the fee that needs to be deducted, and the BMP sends a one-off fee deduction request to request the CBP to deduct the fee. For the description of the process, see 14.2.1 Process of Enabling the FN Service for a Subscriber Through IVR .

Process of Enabling the FN Service for a Subscriber Through USSD (Triggered in MAP Mode) Figure 14-4 shows the normal process of enabling the FN service for a subscriber through USSD (triggered in MAP mode). Issue 01 (2010-07-28)


14-7



Figure 14-5 Normal process of enabling the FN service for a subscriber through USSD (triggered in MAP mode)

MSC/VLR/SSP Apply for FN service through USSD

SCP

Apply for FN service through USSD

HLR

BMP

MAP: FN service request Check whether subscriber needs to be charged Return result

Notify subscriber of fee to be Notify subscriber deducted of fee to be deducted Subscriber confirms fee Subscriber confirms fee

Notify subscriber of fee to be deducted

CBP


Subscriber confirms fee FN service request Verify data One-off fee deduction request Return result FN service request Return result

Deduct fee

Enable FN service


Return result

Return result

The process of enabling the FN service for a subscriber through USSD (triggered in MAP mode) is similar to the process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode) in the OCS system. The only difference is the trigger mode. For the description of the process, see Process of Enabling the FN Service for a Subscriber Through USSD (Triggered in U-CSI Mode).

14-8


Issue 01 (2010-07-28)



14.2.5 Process of Enabling the FN Service for a Subscriber Through a Short Message This section describes the process of enabling the FN service for a subscriber through a short message. Figure 14-6 shows the normal process of enabling the FN service for a subscriber through a short message. Figure 14-6 Normal process of enabling the FN service for a subscriber through a short message MSC/VLR/SSP Subscriber sends a short message to apply for FN service

SMSC

GFEP

SCP

BMP

CBP

FN service request SMPP: FN service request Return response Parse SMS contents RCOMM: FN service request FN service request Verify data One-off fee deduction request Return result FN service request Return result

Deduct fee

Enable FN service

Return result Return result Return result Return result Return result


A subscribe subscriberr sends sends a short short message message to to subscribe subscribe to the FN service service.. The subscr subscription iption request request reaches the MSC/VLR/SSP.

2.

The MSC/VLR MSC/VLR/SSP /SSP authentica authenticates tes the the subscrib subscriber. er. If If the subscr subscriber iber has the the right right to send send this short message, message, the MSC/VLR/SSP MSC/VLR/SSP forwards the short message to the SMSC.

Issue 01 (2010-07-28)


14-9



3.

The SMSC SMSC forwar forwards ds the short message message to the the GFEP GFEP through through SMPP3 SMPP3.4 .4 accordi according ng to the the ID of the ESME.

4.

The GFEP GFEP direc directly tly retu returns rns a respon response se messa message ge to the the SMSC SMSC..

5.


6.

After receiving receiving the RCOMM RCOMM message message,, the SCP SCP request requestss the BMP to enable enable the FN service service for the subscriber.

7.


8.

After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP authenti authenticates cates the subscrib subscriber. er. If the subscriber needs to be charged for subscribing to the FN service, the operations in the dotted red box in Figure 14-6 are performed. That is, the BMP invokes the one-off realtime fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for subscribing to the FN service, step 9 is proceeded with.

9.

The BMP requests requests the CBP to to enable enable the FN servi service ce for for the the subscri subscriber. ber.

10. The CBP enable enabless the FN service service and and returns returns the processi processing ng result result to the BMP. BMP. 11. The BMP returns returns the process processing ing result result to the SCP, and the SCP SCP returns returns the processing processing result result to the subscriber. Then the processes of enabling the FN service for a subscriber through a short message is complete.

14.3 Processes of Disabling the FN Service for a Subscriber This section describes the processes of disabling the FN service for a subscriber. The FN service can be disabled through the WebService interface, IVR, on the SMAP, USSD, or short messages. The following sections describe each process in detail.

14.3.1 Process of Disabling the FN Service for a Subscriber Su bscriber Through IVR Figure 14-7 shows the normal process of disabling the FN service for a subscriber through IVR.

14-10


Issue 01 (2010-07-28)



Figure 14-7 Normal process of disabling the FN service for a subscriber through IVR SCP

BMP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to disable FN service FN service unsubscription request Verify data

Return result

Disable FN service

Return result


A subscribe subscriberr dials dials the IVR IVR access access code code to send a request request for for unsubsc unsubscribin ribing g from the FN FN service.

2.

The SCP SCP plays plays voice voicess to intera interact ct with with the subscribe subscriber. r. The The dotted dotted red red box box in Figure 14-7 shows the interactions. Then the subscriber chooses to unsubscribe from the FN service.

3.

The SCP SCP forwa forwards rds the the unsub unsubscr script iption ion requ request est to to the BMP. BMP.

4.


5.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP disable disabless the FN service service for the the subscriber and returns the processing result to the SCP.

6.

The SCP SCP returns returns the process processing ing result result to the subscr subscriber. iber. Then the process process of disablin disabling g the FN service for a subscriber through IVR is complete.

14.3.2 Process of Disabling the FN Service for a Subscriber Su bscriber Through the WebService Interface Figure 14-8 shows the normal process of disabling the FN service for a subscriber through the WebService interface.

Issue 01 (2010-07-28)


14-11



Figure 14-8 Normal process of disabling the FN service for a subscriber through the WebService interface External system Subscriber applies for FN service unsubscription

BMP

Unsubscription request Verify data Disable FN service Return result Return result


A subscribe subscriberr sends sends a request request for unsubsc unsubscribin ribing g from the FN service. service. The The unsubsc unsubscriptio ription n request reaches an external system.

2.

The extern external al system system forwards forwards the unsubsc unsubscriptio ription n request request to the the BMP through through the changeservice interface of the WebService interface.

3.


4.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP disable disabless the FN service service for the the subscriber and returns the processing result to the external system.

5.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of disabling the FN service for a subscriber through the WebService interface is complete.

14.3.3 Process of Disabling the FN Service for a Subscriber on the SMAP Figure 14-9 shows the normal process of disabling the FN service for a subscriber on the SMAP.

14-12


Issue 01 (2010-07-28)



Figure 14-9 Normal process of disabling the FN service for a subscriber on the SMAP SMAP

BMP

Subscriber applies for FN service unsubscription Unsubscription request Verify data Disable FN service Return result Return result


A subscribe subscriberr sends sends a request request for unsubsc unsubscribin ribing g from the FN service service on the SMAP. SMAP.

2.


3.


4.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP disable disabless the FN service service for the the subscriber and returns the processing result to the SMAP.

5.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of disabl disabling ing the FN service for a subscriber on the SMAP is complete.

14.3.4 Processes of Disabling the FN Service for a Subscriber Through USSD This section describes the processes of disabling the FN service for a subscriber through USSD.

Process of Disabling the FN Service for a Subscriber Through USSD (Triggered in U-CSI Mode) Figure 14-10 shows the normal process of disabling the FN service for a subscriber through USSD (triggered in U-CSI mode).

Issue 01 (2010-07-28)


14-13



Figure 14-10 Normal process of disabling the FN service for a subscriber through USSD (triggered in U-CSI mode) MSC/VLR/SSP

SCP

BMP

CBP

Apply for FN service unsubscription through USSD U-CSI triggers service Apply for FN service unsubscription through USSD

FN service unsubscription request Verify data FN service unsubscription request Return result

Return result

Disable FN service

Return result

Return result

The process of disabling the FN service for a subscriber through USSD (triggered in U-CSI mode) is similar to the process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode). For the description of the process, see Process of Enabling the FN Service for a Subscriber a Subscriber Through USSD (Triggered in U-CSI Mode) .

Process of Disabling the FN Service for a Subscriber Through USSD (Triggered in MAP Mode) Figure 14-10 shows the normal process of disabling the FN service for a subscriber through USSD (triggered in MAP mode).

14-14


Issue 01 (2010-07-28)



Figure 14-11 Normal process of disabling the FN service for a subscriber through USSD (triggered in MAP mode)

MSC/VLR/SSP Apply for FN service unsubscription through USSD

SCP

FN service unsubscription request

HLR

MAP: FN service unsubscription request

BMP

CBP

FN service unsubscription request Verify data FN service unsubscription request Return result Return result

Return result

Return result

Disable FN service

Return result

The process of disabling the FN service for a subscriber through U SSD (triggered in MAP mode) is similar to the process of enabling the FN service for a subscriber through USSD (triggered in MAP mode). For the description of the process, see Process of Enabling the FN Service for a Subscriber Through USSD (Triggered in MAP Mode) .

14.3.5 Process of Disabling the FN Service for a Subscriber Su bscriber Through a Short Message This section describes the process of disabling the FN service for a subscriber through a short message. Figure 14-12 shows the normal process of disabling the FN service for a subscriber through a short message.

Issue 01 (2010-07-28)


14-15



Figure 14-12 Normal process of disabling the FN service for a subscriber through a short message MSC/VLR/SSP Subscriber sends a short message to unsubscribe from FN service

SMSC

FN service unsubscription request

GFEP

SCP

BMP

CBP

SMPP: FN service unsubscription request Return response Parse SMS contents RCOMM: FN service unsubscription request

FN service unsubscription request Verify data FN service unsubscription request Return result

Disable FN service


Return result

Return result

The process of disabling the FN service for a subscriber through a short message is similar to the process of enabling the FN service for a subscriber through a short message. In the process of disabling the FN service for a subscriber through a short message, a service unsubscription message is sent, and fee deduction is not required. For the description of the process, see 14.2.5 Process of Enabling the FN Service for a Subscriber Through a Short Message.

14.4 Processes of Adding or Changing an FN of a Subscriber This section describes the processes of adding or changing an FN of a subscriber. After the FN service is enabled for a subscriber, the subscriber can add or change an FN through the WebService interface, IVR, on the SMAP, USSD, or short messages. The following sections describe each process in detail.

14.4.1 Process of Adding or Changing an FN of a Subscriber Through IVR Figure 14-13 shows the normal process of adding or changing an FN of a subscriber through IVR. 14-16


Issue 01 (2010-07-28)



Figure 14-13 Normal process of adding or changing an FN of a subscriber through IVR SCP

BMP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to add/change FN



Play voice to notify subscriber of fee to be deducted Subscriber confirms fee FN adding/changing request Verify data Authenticate One-off fee deduction request Deduct fee Return result


Add/Change FN


A subscri subscriber ber sends a request request of adding adding or changi changing ng an an FN FN through through IVR.

2.

The SCP SCP plays plays voices voices to to interact interact with with the subscribe subscriber. r. The first dotted dotted red box box in Figure 14-13 shows the interactions. Then the subscriber chooses to add or change an FN.

3.

The SCP SCP request requestss the BMP BMP to check check whether whether the the subscrib subscriber er needs needs to be charge charged d for subscribing to add or change an FN.

4.

The BMP BMP determin determines es whether whether the the subscrib subscriber er needs needs to be charge charged d for subscr subscribing ibing to to add or or change an FN and returns a result to the SCP.

5.


Issue 01 (2010-07-28)

l

If the subscriber does not need to be charged for subscribing to add or change an FN, step 6 is proceeded with.

l

If the subscriber needs to be charged for subscribing to add or change an FN, the operations in the second dotted red box in Figure 14-13 are performed. The SCP plays Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

14-17



a voice to notify the subscriber of the fee that needs to be deducted for the service subscription. After the subscriber confirms the fee deduction, step 6 i s proceeded with. 6.

The SCP SCP forwa forwards rds the the addi adding ng or chan changin ging g reques requestt to the the BMP. BMP.

7.


8.

After the subscr subscriber iber data data passes passes the the verifica verification, tion, the the BMP authentica authenticates tes the FN to be be added added or changed. The BMP accumulates the FN that needs to be added or changed by group to check whether the FN group exists, whether the number of FNs in the FN group reaches the maximum, and whether the FN can be added or changed according to the restrictions of the system on FNs.

9.

After the FN FN passes passes the verificati verification, on, the the BMP adds or or changes changes the FN for the the subscrib subscriber er and returns the processing result to the SCP. NOTE

If the subscriber needs to be charged for adding or changing the FN, the operations in the third dotted red box in Figure 14-13 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for adding or changing the FN, step 9 is proceeded with.

10. The SCP returns returns the process processing ing result result to the subscriber. subscriber. Then Then the process process of adding adding or changing an FN of a subscriber through IVR is complete.

14.4.2 Process of Adding or Changing an FN of a Subscriber Through the WebService Interface Figure 14-14 shows the normal process of adding or changing an FN of a subscriber through the WebService WebService interface. Figure 14-14 Normal process of adding or changing an FN of a subscriber through the WebService interface External system Apply for adding/changing FN

BMP

CBP

Apply for adding/changing FN Verify data Authenticate One-off fee deduction request Return result

Return result

Deduct fee

Add/Change FN

Return result

14-18


Issue 01 (2010-07-28)




A subscriber subscriber sends a request request of adding adding or or changing changing an FN. FN. The reque request st reaches reaches an an external external system.

2.

The extern external al system system forward forwardss the request request to the BMP BMP through through the changeser changeservice vice interf interface ace of the WebService interface.

3.


4.


5.

After the FN FN passes passes the verificati verification, on, if the subscr subscriber iber needs needs to be charg charged ed for adding adding or changing the FN, the operations in the dotted red box in Figure 14-14 are performed. That is, the BMP adds or changes an FN for the subscriber and returns the processing result to the external system. If the subscriber does not need to be charged for adding or changing the FN, step 5 is proceeded with.

6.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of adding or changing an FN of a subscriber through the WebService interface interface is complete.

14.4.3 Process of Adding or Changing an FN of a Subscriber on the SMAP Figure 14-15 shows the normal process of adding or changing an FN of a subscriber on the SMAP. Figure 14-15 Normal process of adding or changing an FN of a subscriber on the SMAP SMAP Apply for adding/changing FN

BMP

CBP

Apply for adding/changing FN Verify data Authenticate One-off fee deduction request Return result

Deduct fee

Add/Change FN Return result Return result

Issue 01 (2010-07-28)


14-19




A subscrib subscriber er sends sends a request request of adding adding or changi changing ng an FN on the SMAP. SMAP.

2.


3.


4.


5.

After the FN FN passes passes the verificati verification, on, if the subscr subscriber iber needs needs to be charg charged ed for adding adding or changing the FN, the operations in the dotted red box in Figure 14-15 are performed. That is, the BMP adds or changes an FN for the subscriber and returns the processing result to the SMAP. If the subscriber does not need to be charged for adding or changing the FN, step 5 is proceeded is proceeded with. wi th.

6.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of adding adding or changing an FN of a subscriber on the SMAP is complete.

14.4.4 Processes of Adding or Changing an FN of a Subscriber Through USSD This section describes the processes of adding or changing an FN of a subscriber through USSD. The process of adding or changing an FN of a subscriber through USSD (triggered in U-CSI or MAP mode) is similar to the processes of enabling the FN service for a subscriber through USSD (triggered in U-CSI or MAP mode).

Process of Adding or Changing an FN of a Subscriber Through USSD (Triggered in U-CSI Mode) Figure 14-16 shows the normal process of adding or changing an FN of a subscriber through USSD (triggered in U-CSI mode).

14-20


Issue 01 (2010-07-28)



Figure 14-16 Normal process of adding or changing an FN of a subscriber through USSD (triggered in U-CSI mode) MSC/VLR/SSP

SCP

BMP

CBP

Apply for adding/changing FN through USSD U-CSI triggers service Apply for adding/changing FN through USSD



Return result Notify subscriber of Notify subscriber fee to be deducted of fee to be deducted Subscriber confirms fee

Subscriber confirms fee Add/Change FN Verify data One-off fee deduction request Return result

Deduct fee

Add/Change FN

Return result

Add/Change FN


Return result

The process of adding or changing an FN of a subscriber through USSD (triggered in U-CSI mode) is similar to the process of enabling the FN service for a subscriber through USSD (triggered in U-CSI mode). For the description of the process, see Process of Enabling the FN Service for a Subscriber Through USSD (Triggered in U-CSI Mode) .

Process of Adding or Changing an FN of a Subscriber Through USSD (Triggered in MAP Mode) Figure 14-16 shows the normal process of adding or changing an FN of a subscriber through USSD (triggered in MAP mode).

Issue 01 (2010-07-28)


14-21



Figure 14-17 Normal process of adding or changing an FN of a subscriber through USSD (triggered in MAP mode) MSC/VLR/SSP

SCP

HLR

BMP

CBP

Apply for adding/changing FN through USSD

Apply for adding/changing FN through USSD

MAP: FN adding/changing request

Check whether subscriber needs to be charged Return result

Notify subscriber of fee to be Notify subscriber deducted of fee to be Notify subscriber deducted of fee to be deducted Subscriber confirms fee Subscriber Subscriber confirms fee confirms fee


FN adding/changing request Verify data One-off fee deduction request Return result

Deduct fee

Add/Change FN FN Return result

Add/Change FN


Return result

Return result

The process of adding or changing an FN of a subscriber through USSD (triggered in MAP mode) is similar to the process of enabling the FN service for a subscriber through USSD (triggered in MAP mode). For the description of the process, see Process of Enabling the FN Service for a Subscriber Through USSD (Triggered in MAP Mode) .

14-22


Issue 01 (2010-07-28)



14.4.5 Process of Adding or Changing an FN of a Subscriber Through a Short Message This section describes the process of adding or changing an FN of a subscriber through a short message. Figure 14-18 shows the normal process of adding or changing an FN of a subscriber through a short message. Figure 14-18 Normal process of adding or changing an FN of a subscriber through a short message MSC/VLR/SSP

SMSC

GFEP

SC P

BMP

CBP

Subscriber sends a short message to apply for adding/changing FN Add/Change FN

SMPP: Add/Change FN Return response Parse SMS contents RCOMM: Add/Change FN Add/Change FN Verify data One-off fee deduction request Return result

Deduct fee

Add/Change FN

Return result

Add/ Change FN


The process of adding or changing an FN of a subscriber through a short message is similar to the process of enabling the FN service for a subscriber through a short message. For the description of the process, see 14.2.5 Process of Enabling the FN Service for a Subscriber Through a Short Message .

Issue 01 (2010-07-28)


14-23



14.5 Processes of Querying an FN of a Subscriber This section describes the processes of querying an FN of a subscriber. An FN service subscriber can query an FN through the WebService interface, IVR, on the SMAP, USSD, or short messages. The following sections describe each process in detail.

14.5.1 Process of Querying an FN of a Subscriber Through IVR Figure 14-19 shows the process of querying an FN of a subscriber through IVR. Figure 14-19 Process of querying an FN of a subscriber through IVR SCP

BMP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to query FN Query FN Verify data Query FN Return result Return result


A subscr subscribe iberr sends sends a requ request est of of queryi querying ng an FN FN throug through h IVR. IVR.

2.

The SCP SCP plays plays voice voicess to intera interact ct with with the subscribe subscriber. r. The The dotted dotted red red box box in Figure 14-19 shows the interactions. Then the subscriber chooses to query an FN.

3.

The SCP forwar forwards ds the the quer queryin ying g reque request st to to the the BMP. BMP.

4.


14-24

5.

After the subscrib subscriber er data data passes passes the the verifica verification, tion, the the BMP querys querys the FN for the subscrib subscriber er and returns the processing result to the SCP.

6.

The SCP SCP returns returns the process processing ing result result to the subscr subscriber. iber. Then the process process of queryin querying g an FN of a subscriber thr ough ough IVR is complete.


Issue 01 (2010-07-28)



14.5.2 Process of Querying an FN of a Subscriber Through the WebService Interface Figure 14-20 shows the normal process of querying an FN of a subscriber through the WebService interface. Figure 14-20 Normal process of querying an FN of a subscriber through the WebService interface External system

BMP

Apply for querying FN Apply for querying FN Verify data Query FN Return result Return result


A subscribe subscriberr applies applies for for querying querying an FN. FN. The subscripti subscription on request request reach reaches es an external external system.

2.

The extern external al system system forwards forwards the subsc subscriptio ription n request request to the BMP throug through h the QuerySubscriberServiceInfo QuerySubscriberServiceInfo interface of the WebService interface.

3.


4.

After the subscrib subscriber er data data passes passes the the verifica verification, tion, the the BMP querys querys the FN for the subscrib subscriber er and returns the processing result to the external system.

5.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of querying an FN of a subscriber through the WebService interface is complete.

14.5.3 Process of Querying an FN of a Subscriber on the SMAP Figure 14-21 shows the process of querying an FN of a subscriber on the SMAP.

Issue 01 (2010-07-28)


14-25



Figure 14-21 Process of querying an FN of a subscriber on the SMAP SMAP

BMP

Apply for querying FN Apply for querying FN Verify data Return result

Query FN

Return result


A subscri subscriber ber applies applies for for queryin querying g an FN of of a subscribe subscriberr on the SMAP. SMAP.

2.

The SMAP SMAP sends sends subscr subscriber iber reques requests ts to the the BMP by invoking invoking the WebSer WebService vice interface interface (the QuerySubscriberServiceInfo QuerySubscriberServiceInfo interface).

3.


4.

After the subscrib subscriber er data data passes passes the the verifica verification, tion, the the BMP querys querys the FN for the subscrib subscriber er and returns the processing result to the SMAP.

5.

The SMAP SMAP returns returns the process processing ing result result to the the subscri subscriber. ber. Then Then the the process process of of querying querying an an FN of a subscriber on the SMAP is complete.

14.5.4 Processes of Querying an FN of a Subscriber Through USSD This section describes the process of querying an FN of a subscriber through USSD.

Process of Querying an FN of a Subscriber Through USSD (Triggered in U-CSI Mode) Figure 14-22 shows the normal process of querying an FN of a subscriber through USSD (triggered in U-CSI mode).

14-26


Issue 01 (2010-07-28)



Figure 14-22 Normal process of querying an FN of a subscriber through USSD (triggered in UCSI mode) MSC/VLR/SSP

SCP

BMP

CBP

Apply for querying FN through USSD U-CSI triggers service Apply for querying FN through USSD Query FN Verify data Query FN Query FN Return result Return result

Return result

Return result

The process of querying an FN of a subscriber through USSD (triggered in U-CSI mode) is similar to the process of disabling the FN service for a subscriber through USSD (triggered in U-CSI mode). For the description of the process, see Process of Disabling the FN Service for a Subscriber Through Subscriber Through USSD (Triggered in U-CSI Mode) .

Process of Querying an FN of a Subscriber Through USSD (Triggered in MAP Mode) Figure 14-23 shows the normal process of querying an FN of a subscriber through USSD (triggered in MAP mode).

Issue 01 (2010-07-28)


14-27



Figure 14-23 Normal process of querying an FN of a subscriber through USSD (triggered in MAP mode)

MSC/VLR/SSP

SCP

HLR

BMP

CBP

Apply for querying FN through USSD Apply for querying FN MAP: Apply for querying FN Apply for querying FN Verify data Apply for querying FN Query FN Return result Return result Return result

Return result

Return result

The process of of querying an FN of a subscriber through USSD (triggered in i n MAP mode) is similar to the process of disabling the FN service for a subscriber through t hrough USSD (triggered in MAP mode). For the description of the process, see Process of Disabling the FN Service for a Subscriber Through USSD (Triggered in MAP Mode) .

14.5.5 Process of Querying an FN of a Subscriber Through a Short Message This section describes the process of querying an FN of a subscriber through a short message. Figure 14-24 shows the normal process of querying an FN of a subscriber through a short message.

14-28


Issue 01 (2010-07-28)



Figure 14-24 Normal process of querying an FN of a subscriber through a short message MSC/VLR/SSP

SMSC

GFEP

SCP

BMP

CBP

Subscriber sends a short message to query FN FN query request SMPP: FN query request Return response Parse SMS contents RCOMM: FN query request FN query request Verify data FN query request Return result

Query FN


The process of querying an FN of a subscriber through a short message is simil ar to the process of disabling the FN service for a subscriber through a short message. For the description of the process, see 14.3.5 Process of Disabling the FN Service for a Subscriber Through a Short Message.

14.6 Reference This section describes the terms used in the FN service processes. None.

Issue 01 (2010-07-28)


14-29


15 ICS Service Processes

15

ICS Service Processes

About This Chapter

15.1 Overview Overview This topic describes the Incoming Call Screening (ICS) service and the main processes associated with with the service. 15.2 Processes of Enabling the ICS Service for a Subscriber This section describes the processes of enabling the ICS service for a subscriber. 15.3 Processes of Disabling the ICS Service for a Subscriber This section describes the processes of disabling the ICS service for a subscriber. 15.4 Processes of Adding or Changing an ICS number of a Subscriber This section describes the processes of adding or changing an ICS number of a subscriber. 15.5 Processes of Querying an ICS number of a Subscriber This section describes the processes of querying an ICS number of a subscriber. 15.6 Process of ICS Monthly Settlement This topic describes describes the process of performing monthly settlement of the ICS service. 15.7 Reference Reference This section describes the terms used in the ICS service processes.

Issue 01 (2010-07-28)


15-1



15.1 Overview This topic describes the Incoming Call Screening (ICS) service and the main processes associated with the service. The ICS service indicates the service of screening unnecessary incoming calls for subscribers. The service supports blacklists and whitelists. l

Blacklist: When a call is made from a subscriber number that is in a blacklist, the call cannot be connected.

l

Whitelist: When a call is made from a subscriber number that is in a whitelist, the call is connected.

The ICS service includes the following processes: l

Processes of enabling the ICS service for a subscriber

l

Processes of disabling the ICS service for a subscriber

l

Processes of adding or changing an ICS number of a subscriber

l

Processes of querying an ICS number of a subscriber

l

Process of ICS monthly settlement

15.2 Processes of Enabling Enabli ng the ICS Service for a Subscriber This section describes the processes of enabling the ICS service for a subscriber. The ICS service can be enabled through the WebService interface, IVR or on the SMAP. The following sections describe each process in detail.

15.2.1 Processes of Enabling the ICS Service for a Subscriber Through IVR Figure 15-1 shows the normal process of enabling the ICS service for a subscriber through IVR.

15-2


Issue 01 (2010-07-28)



Figure 15-1 Normal process of enabling the ICS service for a subscriber through IVR SCP

BMP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to enable Send request of ICS service checking whether subscriber needs to be charged Return result Play voice to notify subscriber of fee to be deducted Subscriber confirms fee


ICS service request Verify data One-off fee deduction request Return result

Deduct fee

Enable ICS service Return result Return result


A subscrib subscriber er dials dials the the IVR IVR access access code to subscri subscribe be to the ICS ICS servic service. e.

2.

The SCP SCP plays plays voices voices to to interact interact with with the subscribe subscriber. r. The first dotted dotted red box box in Figure 15-1 shows the interactions. Then the subscriber chooses to subscribe to the ICS service.

3.

The SCP SCP request requestss the BMP BMP to check check whether whether the the subscrib subscriber er needs needs to be charge charged d for subscribing to the ICS service.

4.

The BMP BMP determine determiness whether whether the the subscrib subscriber er needs needs to be charged charged for subscri subscribing bing to to the ICS ICS service and returns a result to the SCP.

5.


Issue 01 (2010-07-28)

l

If the subscriber does not need to be charged for subscribing to the ICS service, step 6 is proceeded with.

l

If the subscriber needs to be charged for subscribing to the ICS service, the operations in the second dotted red box in Figure 15-1 are performed. The SCP plays a voice to notify the subscriber of the fee that needs to be deducted for the service subscription. After the subscriber confirms the fee deduction, step 6 is proceeded with. Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

15-3



6.


7.


8.


9.

The BMP BMP enables enables the the ICS service service for for the subscr subscriber iber and and returns returns the the process processing ing result result to the SCP.

10. The SCP returns the processing result result to the subscriber. Then Then the process of enabling the ICS service for a subscriber through IVR is complete.

15.2.2 Processes of Enabling the ICS Service for a Subscriber Through the WebService Interface Figure 15-2 shows the normal process of enabling the ICS service for a subscriber through the WebService interface. Figure 15-2 Normal process of enabling the ICS service for a subscriber through the WebService interface External BMP system Subscriber applies for ICS service Subscriber

CBP

applies for ICS service Verify data Authenticate One-off fee deduction request Return result

Deduct fee



15-4

1.

A subscribe subscriberr applies applies for for the ICS service service.. The subscr subscription iption request request reache reachess an extern external al system.

2.


3.


Issue 01 (2010-07-28)





If the subscriber needs to be charged for subscribing to the ICS service, the operations in the dotted red box in Figure 15-2 are performed. That is, the BMP invokes the oneoff real-time fee deduction interface to deduct the fee on the CBP.

l

If the subscriber does not need to be charged for subscribing to the ICS service, step 5 is proceeded with.

5.

The BMP BMP enables enables the the ICS service service for for the subscr subscriber iber and and returns returns the the process processing ing result result to the external system.

6.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of enabling the ICS service for a subscriber through the WebService interface is complete.

15.2.3 Processes of Enabling the ICS Service for a Subscriber on the SMAP Figure 15-3 shows the normal process of enabling the ICS service for a subscriber on the SMAP. Figure 15-3 Normal process of enabling the ICS service for a subscriber on the SMAP SMAP Subscriber applies for ICS service

BMP

CBP

Subscriber applies for ICS service Verify data Authenticate One-off fee deduction request Return result

Deduct fee



A subsc subscrib riber er appl applies ies for for the the ICS ICS servi service ce on on the SMAP. SMAP.

2.

The SMAP SMAP send sendss subsc subscrib riber er reques requests ts to the the BMP. BMP.

3.


4.

Issue 01 (2010-07-28)

After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP authenti authenticates cates the subscrib subscriber. er. If the subscriber needs to be charged for subscribing to the ICS service, the operations in the Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

15-5



dotted red box in Figure 15-3 are performed. That is, the BMP invokes the one-off realtime fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for subscribing to the ICS service, step 5 is proceeded with. 5.

The BMP BMP enables enables the the ICS service service for for the subscr subscriber iber and and returns returns the the process processing ing result result to the SMAP.

6.

The SMAP SMAP returns returns the the process processing ing result result to the the subscrib subscriber. er. Then Then the the process process of enabling enabling the the ICS service for a subscriber on the SMAP is complete.

15.3 Processes of Disabling the ICS Service for a Subscriber This section describes the processes of disabling the ICS service for a subscriber. The ICS service can be disabled through the WebService interface, IVR and on the SMAP. The following sections describe each process in detail.

15.3.1 Processes of Disabling the ICS Service for a Subscriber Through IVR Figure 15-4 shows the normal process of disabling the ICS service for a subscriber through IVR. Figure 15-4 Normal process of disabling the ICS service for a subscriber through IVR SCP

BMP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to disable ICS service ICS service unsubscription request Verify data

Return result

Disable ICS service

Return result


15-6

1.

A subscribe subscriberr dials dials the IVR IVR access access code code to send a request request for for unsubsc unsubscribin ribing g from the ICS ICS service.

2.

The SCP SCP plays plays voice voicess to intera interact ct with with the subscribe subscriber. r. The The dotted dotted red red box box in Figure 15-4 shows the interactions. Then the subscriber chooses to unsubscribe from the ICS service.

3.


4.


Issue 01 (2010-07-28)




After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP disables disables the the ICS service service for the subscriber and returns the processing result to the SCP.

6.

The SCP SCP returns returns the process processing ing result result to the subscr subscriber. iber. Then the process process of disablin disabling g the ICS service for a subscriber through IVR is complete.

15.3.2 Processes of Disabling the ICS Service for a Subscriber Through the WebService Interface Figure 15-5 shows the normal process of disabling the ICS service for a subscriber through the WebService interface. Figure 15-5 Normal process of disabling the ICS service for a subscriber through the WebService interface External system

BMP

Subscriber applies for ICS service unsubscription Unsubscription request Verify data Disable ICS service Return result Return result


A subscribe subscriberr sends sends a request request for unsubsc unsubscribin ribing g from the ICS ICS service service.. The unsubs unsubscript cription ion request reaches an external system.

2.


3.


4.

After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP disables disables the the ICS service service for the subscriber and returns the processing result to the external system.

5.

The external system returns the processing result to the subscriber. Then the process of disabling the ICS service for a subscriber through the WebService interface is complete.

Issue 01 (2010-07-28)


15-7



15.3.3 Processes of Disabling the ICS Service for a Subscriber on the SMAP Figure 15-6 shows the normal process of disabling the ICS service for a subscriber on the SMAP. Figure 15-6 Normal process of disabling the ICS service for a subscriber on the SMAP SMAP

BMP

Subscriber applies for ICS service unsubscription Unsubscription request Verify data Disable ICS service Return result Return result


A subscribe subscriberr sends sends a request request for unsubsc unsubscribin ribing g from the ICS ICS service service on the SMAP. SMAP.

2.


3.


4.

After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP disables disables the the ICS service service for the subscriber and returns the processing result to the SMAP.

5.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of disabl disabling ing the ICS service for a subscriber on the SMAP is complete.

15.4 Processes of Adding or Changing an ICS number of a Subscriber This section describes the processes of adding or changing an ICS number of a subscriber. After the ICS service is enabled for a subscriber, the subscriber can add or change an ICS number through the WebService interface, IVR or on the SMAP. The following sections describe each process in detail.

15-8


Issue 01 (2010-07-28)



15.4.1 Process of Adding or Changing an ICS number of a Subscriber Through IVR Figure 15-7 shows the normal process of adding or changing an ICS number of a subscriber through IVR. Figure 15-7 Normal process of adding or changing an ICS number of a subscriber through IVR SCP

BMP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to add/change an ICS number




ICS number adding/changing request Verify data Authenticate One-off fee deduction request Deduct fee Return result


Add/Change ICS number


A subscrib subscriber er sends sends a request request of adding adding or changi changing ng an ICS numbe numberr through through IVR.

2.

The SCP SCP plays plays voices voices to to interact interact with with the subscribe subscriber. r. The first dotted dotted red box box in Figure 15-7 shows the interactions. Then the subscriber chooses to add or change an ICS number.

3.

The SCP SCP request requestss the BMP BMP to check check whether whether the the subscrib subscriber er needs needs to be charge charged d for subscribing to add or change an ICS number.

Issue 01 (2010-07-28)


15-9



4.

The BMP BMP determin determines es whether whether the the subscrib subscriber er needs needs to be charge charged d for subscr subscribing ibing to to add or or change an ICS number and returns a result to the SCP.

5.

The SCP SCP processe processess the subscr subscription iption request request accordi according ng to the the result result return returned ed by the BMP. BMP. l

If the subscriber does not need to be charged for subscribing to add or change an ICS number, step 6 is proceeded with.

l

If the subscriber needs to be charged for subscribing to add or change an ICS number, the operations in the second dotted red box in Figure 15-7 are performed. The SCP plays a voice to notify the subscriber of the fee that that needs to be deducted for the service subscription. After the subscriber confirms the fee deduction, step 6 i s proceeded with.

6.


7.


8.

After the subscri subscriber ber data data passes passes the verificati verification, on, the BMP authent authenticate icatess the ICS ICS number number to be added or changed. changed.

9.

After the ICS ICS number number passes passes the the verific verification ation,, the BMP BMP adds adds or changes changes the ICS number number for the subscriber and returns the processing result to the SCP. NOTE

If the subscriber needs to be charged for adding or changing the ICS number, the operations in the third dotted red box in Figure 15-7 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for adding or changing the ICS number, step 9 is proceeded with.

10. The SCP returns returns the process processing ing result result to the subscriber. subscriber. Then Then the process process of adding adding or changing an ICS number of a subscriber through IVR is complete.

15.4.2 Process of Adding or Changing an ICS number of a Subscriber Through the WebService Interface Figure 15-8 shows the normal process of adding or changing an ICS number of a subscriber through the WebService interface.

15-10


Issue 01 (2010-07-28)



Figure 15-8 Normal process of adding or changing an ICS number of a subscriber through the WebService interface External system Apply for adding/changing an ICS number

BMP

CBP

Apply for adding/changing an ICS number Verify data Authenticate One-off fee deduction request Return result

Return result

Deduct fee

Add/Change ICS number

Return result


A subscribe subscriberr sends sends a request request of adding adding or or changing changing an ICS number. number. The request request reaches reaches an external system.

2.


3.


4.


5.

After the ICS ICS number number passes passes the the verific verification ation,, the BMP BMP adds adds or changes changes the ICS number number for the subscriber and returns the processing result to the external system. NOTE

If the subscriber needs to be charged for adding or changing the ICS number, the operations in the dotted red box in Figure 15-8 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for adding or changing the ICS number, step 5 is proceeded with.

6.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of adding or changing an ICS number of a subscriber through the WebService interface interface is complete.

15.4.3 Process of Adding or Changing an ICS number of a Subscriber on the SMAP Figure 15-9 shows the normal process of adding or changing an ICS number of a subscriber on the SMAP. Issue 01 (2010-07-28)


15-11



Figure 15-9 Normal process of adding or changing an ICS number of a subscriber on the SMAP SMAP Apply for adding/changing an ICS number

BMP

CBP

Apply for adding/changing an ICS number Verify data Authenticate One-off fee deduction request Return result

Deduct fee

Add/Change ICS number Return result Return result


A subscrib subscriber er sends sends a request request of adding adding or changi changing ng an ICS numbe numberr on the SMAP. SMAP.

2.


3.


4.


5.

After the ICS ICS number number passes passes the the verific verification ation,, the BMP BMP adds adds or changes changes the ICS number number for the subscriber and returns the processing result to the SMAP. NOTE

If the subscriber needs to be charged for adding or changing the ICS number, the operations in the dotted red box in Figure 15-9 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for adding or changing the ICS number, step 5 is proceeded with.

6.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of adding adding or changing an ICS number of a subscriber on the SMAP is complete.

15.5 Processes of Querying an ICS number of a Subscriber This section describes the processes of querying an ICS number of a subscriber. An ICS service subscriber can query an ICS number through the WebService interface, IVR or on the SMAP. The following sections describe each process in detail.

15-12


Issue 01 (2010-07-28)



15.5.1 Processes of Querying an ICS number of a Subscriber Through IVR Figure 15-10 shows the process of querying an ICS number of a subscriber through IVR. Figure 15-10 Process of querying an ICS number of a subscriber through IVR SCP

BMP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to query an ICS number

Query ICS numbers Verify data

Return result

Query ICS number

Return result


A subscr subscribe iberr sends sends a reque request st of quer queryin ying g an ICS ICS number number thro through ugh IVR. IVR.

2.

The SCP SCP plays plays voice voicess to intera interact ct with with the subscribe subscriber. r. The The dotted dotted red red box box in Figure 15-10 shows the interactions. Then the subscriber chooses to query an ICS number.

3.


4.


5.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP querys querys the ICS ICS number number for for the subscriber and returns the processing result to the SCP.

6.

The SCP SCP returns returns the process processing ing result result to the subscr subscriber. iber. Then the process process of queryin querying g an ICS number of a subscriber through IVR is complete.

15.5.2 Processes of Querying an ICS number of a Subscriber Through the WebService Interface Figure 15-11 shows the normal process of querying an ICS number of a subscriber through the WebService interface.

Issue 01 (2010-07-28)


15-13



Figure 15-11 Normal process of querying an ICS number of a subscriber through the WebService interface External system Apply for querying an ICS number

BMP

Apply for querying an ICS number Verify data Query ICS number



A subscribe subscriberr applies applies for for querying querying an ICS number. number. The subscriptio subscription n request request reache reachess an external system.

2.


3.

The BMP verifies the subscriber data. The subscriber data includes the MSISDN of the subscriber, subscriber state, operation type, and validity of the service ID, which are transferred by the interface.

4.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP querys querys the ICS ICS number number for for the subscriber and returns the processing result to the external system.

5.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of querying an ICS number of a subscriber through the WebService interface is complete.

15.5.3 Processes of Querying an ICS number of a Subscriber on the SMAP Figure 15-12 shows the process of querying an ICS number of a subscriber on the SMAP. Figure 15-12 Process of querying an ICS number of a subscriber on the SMAP SMAP Apply for querying an ICS number

BMP

Apply for querying an ICS number Verify data Return result

Query ICS number

Return result

15-14


Issue 01 (2010-07-28)




A subscrib subscriber er applie appliess for querying querying an an ICS number number of a subscri subscriber ber on on the SMAP. SMAP.

2.


3.


4.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP querys querys the ICS ICS number number for for the subscriber and returns the processing result to the SMAP.

5.

The SMAP SMAP returns returns the process processing ing result result to the the subscri subscriber. ber. Then Then the the process process of of querying querying an an ICS number of a subscriber on the SMAP is complete.

15.6 Process of ICS Monthly Settlement This topic describes the process of performing monthly settlement of the ICS service. An operator can set the monthly or daily settlement function for each ICS product. The rental of an ICS product is collected by a scheduled event. After the rental is collected, the system generates associated CDRs.

15.7 Reference This section describes the terms used in the ICS service processes. None.

Issue 01 (2010-07-28)


15-15


16 Home Zone Service Processes

16

Home Zone Service Processes

About This Chapter

16.1 Overview This section describes the Home Zone service and the Home Zone service processes. 16.2 Processes of Enabling the Home Zone Service for a Subscriber This section describes the processes of enabling the Home Zone service for a subscriber. 16.3 Processes Processes of Disabling the Home Zone Service for a Subscriber This section describes the processes of disabling the Home Zone service servic e for a subscriber. 16.4 Processes Processes of Adding or Changing a Home Zone of a Subscriber This section describes the processes of adding or changing a Home Zone of a subscriber. 16.5 Processes Processes of Querying a Home Zone of a Subscriber This section describes the processes of querying a Home Zone of a subscriber.

Issue 01 (2010-07-28)


16-1



16.1 Overview This section describes the Home Zone service and the Home Zone service processes. The system sets a home zone based on the Cell Identification (ID). A home zone can contain one or several cells. A subscriber can set the zone where the call i s initiated to home zone through the management process, or select a zone to be home zone in the business hall. The common FN service processes are as follows: l

Processes of enabling the Home Zone service for a subscriber

l

Processes of cancelling the Home Zone service for a subscriber

l

Processes of adding or changing the Home Zone service for a subscriber

l

Processes of querying the Home Zone service for a subscriber

The Home Zone service can be processed on the SMAP, through the WebService interface, IVR.

16.2 Processes of Enabling the Home Zone Service for a Subscriber This section describes the processes of enabling the Home Zone service for a subscriber. The Home Zone service can be enabled through the WebService interface, IVR, on the SMAP. The following sections describe each process in detail.

16.2.1 Process of Enabling Enabling the Home Zone Service for a Subscriber Through IVR Figure 16-1 shows the normal process of enabling the Home Zone service for a subscriber through IVR.

16-2


Issue 01 (2010-07-28)



Figure 16-1 Normal process of enabling the Home Zone service for a subscriber through IVR SCP

BMP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to enable Home Zone service




Home Zone service request Verify data One-off fee deduction request Return result

Deduct fee

Enable Home Zone service Return result Return result


A subscrib subscriber er dials dials the the IVR IVR access access code to subscri subscribe be to the Home Home Zone Zone service. service.

2.

The SCP SCP plays plays voices voices to to interact interact with with the subscribe subscriber. r. The first dotted dotted red box box in Figure 16-1 shows the interactions. Then the subscriber chooses to subscribe to the Home Zone service.

3.

The SCP SCP request requestss the BMP BMP to check check whether whether the the subscrib subscriber er needs needs to be charge charged d for subscribing to the Home Zone service.

4.

The BMP BMP determin determines es whether whether the subscr subscriber iber needs needs to be charg charged ed for subscribin subscribing g to the the Home Zone service and returns a result to the SCP.

5.


Issue 01 (2010-07-28)

l

If the subscriber does not need to be charged for subscribing to the Home Zone service, step 6 is proceeded with.

l

If the subscriber needs to be charged for subscribing to the Home Zone service, the operations in the second dotted red box in Figure 16-1 are performed. The SCP plays a voice to notify the subscriber of the fee that needs to be deducted for the service subscription. After the subscriber confirms the fee deduction, step 6 i s proceeded with.


16-3



6.


7.


8.


9.

The BMP BMP enables enables the the Home Home Zone service service for for the subscr subscriber iber and and returns returns the proces processing sing result to the SCP.

10. The SCP returns the processing result result to the subscriber. Then Then the process of enabling the Home Zone service for a subscriber through IVR is complete.

16.2.2 Process of Enabling the Home Zone Service for a Subscriber Through the WebService Interface Figure 16-2 shows the normal process of enabling the Home Zone service for a subscriber through the WebService interface. Figure 16-2 Normal process of enabling the Home Zone service for a subscriber through the WebService interface External BMP system Subscriber applies for Home Zone Subscriber service applies for Home Zone service

CBP

Verify data Authenticate One-off fee deduction request Return result

Deduct fee



16-4

1.

A subscribe subscriberr applies applies for for the Home Zone Zone service service.. The subscr subscription iption request request reache reachess an external system.

2.


3.


Issue 01 (2010-07-28)





If the subscriber needs to be charged for subscribing to the Home Zone service, the operations in the dotted red box in Figure 16-2 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP.

l

If the subscriber does not need to be charged for subscribing to the Home Zone service, step 5 is proceeded with.

5.

The BMP BMP enables enables the the Home Home Zone service service for for the subscr subscriber iber and and returns returns the proces processing sing result to the external system.

6.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of enabling the Home Zone service for a subscriber through the WebService interface is complete.

16.2.3 Process of Enabling the Home Zone Service for a Subscriber on the SMAP Figure 16-3 shows the normal process of enabling the Home Zone service for a subscriber on the SMAP. Figure 16-3 Normal process of enabling the Home Zone service for a subscriber on the SMAP SMAP Subscriber applies for Home Zone service

BMP

CBP

Subscriber applies for Home Zone service Verify data Authenticate One-off fee deduction request Return result

Deduct fee



A subscr subscribe iberr applie appliess for the Home Home Zone Zone serv service ice on the the SMAP. SMAP.

2.


3.

The The BMP BMP veri verifi fies es the the sub subsc scri ribe berr data data..

Issue 01 (2010-07-28)


16-5




After the subscrib subscriber er data data passes passes the verifi verificatio cation, n, the BMP BMP authenti authenticates cates the subscrib subscriber. er. If the subscriber needs to be charged for subscribing to the Home Zone service, the operations in the dotted red box in Figure 16-3 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for subscribing to the Home Zone service, step 5 is proceeded with.

5.

The BMP BMP enables enables the the Home Home Zone service service for for the subscr subscriber iber and and returns returns the proces processing sing result to the SMAP.

6.

The SMAP SMAP returns returns the the process processing ing result result to the the subscrib subscriber. er. Then Then the the process process of enabling enabling the the Home Zone service for a subscriber on the SMAP is complete.

16.3 Processes of Disabling the Home Zone Service for a Subscriber This section describes the processes of disabling the Home Zone service for a subscriber. The Home Zone service can be disabled through the WebService interface, IVR, on the SMAP. The following sections describe each process in detail.

16.3.1 Process of Disabling the Home Zone Service for a Subscriber Through IVR Figure 16-4 shows the normal process of disabling the Home Zone service for a subscriber through IVR. Figure 16-4 Normal process of disabling the Home Zone service for a subscriber through IVR SCP

BMP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to disable Home Zone service Home Zone service unsubscription request Verify data


Disable Home Zone service



Issue 01 (2010-07-28)



1.

A subscribe subscriberr dials dials the IVR acces accesss code to send send a request request for unsubs unsubscribi cribing ng from from the Home Zone service.

2.

The SCP SCP plays plays voice voicess to intera interact ct with with the subscribe subscriber. r. The The dotted dotted red red box box in Figure 16-4 shows the interactions. Then the subscriber chooses to unsubscribe from the Home Zone service.

3.


4.


5.

After the subscr subscriber iber data data passes passes the verific verification, ation, the BMP BMP disables disables the the Home Zone service service for the subscriber and returns the processing result to the SCP.

6.

The SCP SCP returns returns the process processing ing result result to the subscr subscriber. iber. Then the process process of disablin disabling g the Home Zone service for a subscriber through IVR is complete.

16.3.2 Process of Disabling the Home Zone Service for a Subscriber Through the WebService Interface Figure 16-5 shows the normal process of disabling the Home Zone service for a subscriber through the WebService interface. Figure 16-5 Normal process of disabling the Home Zone service for a subscriber through the WebService interface External BMP system Subscriber applies for Home Zone service unsubscription Unsubscription request Verify data

Return result

Disable Home Zone service

Return result


A subscrib subscriber er sends sends a request request for unsubsc unsubscribin ribing g from from the Home Zone service. service. The unsubscription request reaches an external system.

2.


3.


Issue 01 (2010-07-28)


16-7



4.

After the subscr subscriber iber data data passes passes the verific verification, ation, the BMP BMP disables disables the the Home Zone service service for the subscriber and returns the processing result to the external system.

5.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of disabling the Home Zone service for a subscriber through the WebService interface is complete.

16.3.3 Process of Disabling the Home Zone Service for a Subscriber on the SMAP Figure 16-6 shows the normal process of disabling the Home Zone service for a subscriber on the SMAP. Figure 16-6 Normal process of disabling the Home Zone service for a subscriber on the SMAP SMAP

BMP

Subscriber applies for Home Zone service unsubscription Unsubscription request Verify data Disable Home Zone service Return result Return result


A subscribe subscriberr sends sends a reque request st for unsubscrib unsubscribing ing from from the Home Zone service service on the SMAP. SMAP.

2.


3.


4.

After the subscr subscriber iber data data passes passes the verific verification, ation, the BMP BMP disables disables the the Home Zone service service for the subscriber and returns the processing result to the SMAP.

5.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of disabl disabling ing the Home Zone service for a subscriber on the SMAP is complete.

16.4 Processes of Adding Adding or Changing a Home Zone of a Subscriber This section describes the processes of adding or changing a Home Zone of a subscriber. 16-8


Issue 01 (2010-07-28)



After the Home Zone service is enabled for a subscriber, the subscriber can add or change a Home Zone through the WebService interface, interface, IVR, on the SMAP. The following sections describe each process in detail.

16.4.1 Process of Adding or Changing a Home Zone of a Subscriber Through IVR Figure 16-7 shows the normal process of adding or changing a Home Zone of a subscriber through IVR. Figure 16-7 Normal process of adding or changing a Home Zone of a subscriber through IVR SCP

BMP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to add/change Home Zone




Home Zone adding/changing request Verify data Authenticate One-off fee deduction request Deduct fee Return result


Add/Change Home Zone


A subscrib subscriber er sends sends a request request of adding adding or changi changing ng a Home Zone through through IVR. IVR.

2.

The SCP plays voices voices to interact with the subscriber. The first dotted red box in Figure 16-7 shows the interactions. Then the subscriber chooses to add or change a Home Zone.

Issue 01 (2010-07-28)


16-9



3.

The SCP SCP request requestss the BMP BMP to check check whether whether the the subscrib subscriber er needs needs to be charge charged d for subscribing to add or change a Home Zone.

4.

The BMP BMP determin determines es whether whether the the subscrib subscriber er needs needs to be charge charged d for subscr subscribing ibing to to add or or change a Home Zone and returns a result to the SCP.

5.

The SCP SCP processe processess the subscr subscription iption request request accordi according ng to the the result result return returned ed by the BMP. BMP. l

If the subscriber does not need to be charged for subscribing to add or change a Home Zone, step 6 is proceeded with.

l

If the subscriber needs to be charged for subscribing to add or change a Home Zone, the operations in the second dotted red box in Figure 16-7 are performed. The SCP plays a voice to notify the subscriber of the fee that that needs to be deducted for the service subscription. After the subscriber confirms the fee deduction, step 6 i s proceeded with.

6.


7.


8.

After the subscrib subscriber er data data passes passes the the verifica verification, tion, the the BMP authentica authenticates tes the Home Zone Zone to be added or changed. changed. The BMP accumulates the Home Zone that needs to be added or changed by group to check whether the the number of Home Zones reaches the maximum, and whether the Home Zone can be added or changed according to the restrictions of the system on Home Zones.

9.

After the Home Home Zone Zone passes passes the verificati verification, on, the the BMP adds adds or changes changes the the Home Zone for the subscriber and returns the processing result to the SCP. NOTE

If the subscriber needs to be charged for adding or changing the Home Zone, the operations in the third dotted red box in Figure 16-7 are performed. That is, the BMP invokes the one-off real-time fee deduction interface to deduct the fee on the CBP. If the subscriber does not need to be charged for adding or changing the Home Zone, step 9 is proceeded with.

10. The SCP SCP retur returns ns the proc process essing ing resul resultt to the subscriber. subscriber. Then the process of adding or changing a Home Zone of a subscriber through IVR is complete.

16.4.2 Process of Adding or Changing a Home Zone of a Subscriber Through the WebService Interface Figure 16-8 shows the normal process of adding or changing a Home Zone of a subscriber through the WebService interface.

16-10


Issue 01 (2010-07-28)



Figure 16-8 Normal process of adding or changing a Home Zone of a subscriber through the WebService interface External system Apply for adding/changing Home Zone

BMP

CBP

Apply for adding/changing Home Zone Verify data Authenticate One-off fee deduction request Return result

Return result

Deduct fee

Add/Change Home Zone

Return result


A subscribe subscriberr sends sends a request request of adding adding or or changing changing a Home Zone. Zone. The reque request st reaches reaches an an external system.

2.


3.


4.

After the subscrib subscriber er data data passes passes the the verifica verification, tion, the the BMP authentica authenticates tes the Home Zone Zone to be added or changed. changed. The BMP accumulates the Home Zone that needs to be added or changed by group to check whether the number of Home Zones reaches the maximum, and whether the Home Zone can be added or changed according to the restrictions of the system on Home Zones.

5.

After the Home Home Zone Zone passes passes the verificat verification, ion, if the subscr subscriber iber needs needs to to be charge charged d for adding adding or changing the Home Zone, the operations in the dotted red box in Figure 16-8 are performed. That is, the BMP adds or changes changes a Home Zone for the the subscriber and returns returns the processing result to the external system. If the subscriber does not need to be charged for adding or changing the Home Zone, step 5 is proceeded with.

6.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of adding or changing a Home Zone of a subscriber through the WebService interface interface is complete.

16.4.3 Process of Adding or Changing a Home Zone of a Subscriber on the SMAP Issue 01 (2010-07-28)


16-11



Figure 16-9 shows the normal process of adding or changing a Home Zone of a subscriber on the SMAP. Figure 16-9 Normal process of adding or changing a Home Zone of a subscriber on the SMAP SMAP Apply for adding/changing Home Zone

BMP

CBP

Apply for adding/changing Home Zone Verify data Authenticate One-off fee deduction request Return result

Deduct fee

Add/Change Home Zone Return result Return result


A subscrib subscriber er sends sends a request request of adding adding or changi changing ng a Home Zone on the the SMAP. SMAP.

2.


3.


4.

After the subscrib subscriber er data data passes passes the the verifica verification, tion, the the BMP authentica authenticates tes the Home Zone Zone to be added or changed. changed. The BMP accumulates the Home Zone that needs to be added or changed by group to check whether the number of Home Zones reaches the maximum, and whether the Home Zone can be added or changed according to the restrictions of the system on Home Zones.

5.

After the Home Home Zone Zone passes passes the verificat verification, ion, if the subscr subscriber iber needs needs to to be charge charged d for adding adding or changing the Home Zone, the operations in the dotted red box in Figure 16-9 are performed. That is, the BMP adds or changes changes a Home Zone for the the subscriber and returns returns the processing result to the SMAP. If the subscriber does not need to be charged for adding or changing the Home Zone, step 5 i s proceeded with.

6.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of adding adding or changing a Home Zone of a subscriber on the SMAP is complete.

16.5 Processes of Querying a Home Zone of a Subscriber This section describes the processes of querying a Home Zone of a subscriber. 16-12


Issue 01 (2010-07-28)



a Home Zone service subscriber can query a Home Zone t hrough the WebService interface, IVR, on the SMAP. The following sections describe each process in detail. 16.5.1 Process of Querying a Home Zone of a Subscriber Through IVR 16.5.2 Process of Querying a Home Zone of a Subscriber Through the WebService Interface

16.5.1 Process of Querying a Home Zone of a Subscriber Through IVR Figure 16-10 shows the process of querying a Home Zone of a subscriber through IVR. Figure 16-10 Process of querying a Home Zone of a subscriber through IVR SCP

BMP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber chooses to query Home Zone Query Home Zone Verify data

Return result

Query Home Zone

Return result


A subscr subscribe iberr sends sends a reque request st of quer queryin ying g a Home Home Zone Zone throug through h IVR. IVR.

2.

The SCP SCP plays plays voice voicess to intera interact ct with with the subscribe subscriber. r. The The dotted dotted red red box box in Figure 16-10 shows the interactions. Then the subscriber chooses to query a Home Zone.

3.


4.


5.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP querys querys the Home Home Zone Zone for the subscriber and returns the processing result to the SCP.

6.

The SCP SCP returns returns the process processing ing result result to the subscr subscriber. iber. Then the process process of queryin querying ga Home Zone of a subscriber through IVR is complete.

Issue 01 (2010-07-28)


16-13



16.5.2 Process of Querying a Home Zone of a Subscriber Through the WebService Interface Figure 16-11 shows the normal process of querying a Home Zone of a subscriber through the WebService interface. Figure 16-11 Normal process of querying a Home Zone of a subscriber through the WebService interface External system Apply for querying Home Zone

BMP

Apply for querying Home Zone Verify data

Return result

Query Home Zone

Return result


A subscribe subscriberr applies applies for for querying querying a Home Home Zone. Zone. The subscriptio subscription n request request reach reaches es an external system.

2.


3.


4.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP querys querys the Home Home Zone Zone for the subscriber and returns the processing result to the external system.

5.

The extern external al system system return returnss the proce processing ssing result result to the the subscribe subscriber. r. Then Then the proce process ss of querying a Home Zone of a subscriber through the WebService interface is complete.

16.5.3 Process of Querying a Home Zone of a Subscriber on the SMAP Figure 16-12 shows the process of querying a Home Zone of a subscriber on the SMAP.

16-14


Issue 01 (2010-07-28)



Figure 16-12 Process of querying a Home Zone of a subscriber on the SMAP SMAP Apply for querying Home Zone

BMP

Apply for querying Home Zone Verify data Return result

Query Home Zone

Return result


A subscrib subscriber er applie appliess for querying querying a Home Zone of a subscriber subscriber on the SMAP. SMAP.

2.

The SMAP SMAP sends sends subscr subscriber iber reques requests ts to the the BMP by invoking invoking the WebSer WebService vice interface interface (the QuerySubscriberServiceInfo QuerySubscriberServiceInfo interface).

3.


4.

After the subscr subscriber iber data data passes passes the verifi verificatio cation, n, the BMP querys querys the Home Home Zone Zone for the subscriber and returns the processing result to the SMAP.

5.

The SMAP SMAP return returnss the proce processing ssing result result to the subscribe subscriber. r. Then Then the proce process ss of query querying ing a Home Zone of a subscriber on the SMAP is complete.

16.6 Reference This section describes the terms used in the Home Zone service processes. None.

Issue 01 (2010-07-28)


16-15


17 Child-Parent Card Service Processes

17

Child-Parent Card Service Processes

About This Chapter

17.1 Overview Overview This section describes the child-parent card service and the associated processes. 17.2 Process of Subscribing to a Product After a subscriber subscriber subscribes to a child-parent card product, the association between child cards and the parent parent card is set up. This section describes the process of subscri bing subscri bing to a child-parent child-parent card product. 17.3 Process of Unsubscribing from a Product This section describes the processes of unsubscribing from a child-parent card product. 17.4 Process of Changing a Consumption Limit This section describes the process of changing a consumption limit of a child card. 17.5 Process of Recharging a Child Card and a Parent Card This section describes the process of recharging a child card and a parent card. 17.6 Process of Performing Monthly Settlement for a Child Card and a Parent Card This section describes describes the process of performing monthly settlement for a child card and a parent card. 17.7 Reference This section describes the terms used in child-parent card service processes.

Issue 01 (2010-07-28)


17-1



17.1 Overview This section describes the child-parent card service and the associated processes. In the child-parent card service, multiple child cards can be affiliated to a parent card and share the same account with the parent card. A subscriber with a parent card can set a monthly consumption limit for each child card. When a subscriber with a child card uses the resources in the account of the parent card, the subscriber uses the free sources first. The free resources of the parent card are not restricted by the consumption limit. After a card is set as a child card, it cannot be set as the parent card. Child cards are divided into common child cards and special child cards: l

A common child card has no separate account. The fees of all the services used by the subscriber with a common child card are deducted from the account of the parent card. If the monthly consumption of the subscriber with a common child card exceeds the limit that is set by the parent card, the services of the common child card will be suspended. If the balance of the parent card is insufficient or the parent card is in non-active state, a subscriber with a common child card cannot use the account of the parent card for payment. In addition, the services of the common child card will also be suspended.

l

A special child card has a separate account. The system supports the function of setting the sequence for using the account of a special child card and the account of the parent card.

l

A subscriber with a parent card can apply to the system for canceling a normal child card. After the cancellation is successful, the child card is deleted from the child card list of the parent card, and the the lifecycle status of the child card is changed changed to disabled. NOTE

A card cannot function as a child card and the parent card at the same time. One child card can correspond to only one parent card, but one parent card can correspond to multiple child cards. Moreover, the number of child cards can be configured.

Common child-parent card service processes are as follows: l

Process of subscribing to a product

l

Process of unsubscribing from a product

l

Process of changing a consumption limit

l

Process of querying the balance of a common child card

l

Process of recharging a child card and a parent card

l

Process of performing monthly settlement for a child card and a parent card

The following sections describe the preceding child-parent card service processes in detail.

17.2 Process of Subscribing to a Product After a subscriber subscribes to a child-parent card product, the association between child cards and the parent card is set up. This section describes the process of subscribing to a child-parent card product.

17-2


Issue 01 (2010-07-28)



17.2.1 Process of Subscribing to a Child-Parent Card Product Through the WebService Interface Figure 17-1 shows the process of subscribing to a child-parent card product through the WebService interface. Figure 17-1 Process of subscribing to a child-parent card product through the WebService interface External BMP system Subscriber applies for child-parent Invoke the card product WebService

CBP

SCP

interface to order product Authenticate Update the subscription data Data synchronization request Return result

Update the subscription data

Data synchronization request Return result




A subscriber subscriber subscribe subscribess to a child-pa child-parent rent card card product product.. The produc productt subscriptio subscription n request request is sent to an external system.

2.

By invoking invoking the WebServic WebServicee interface interface,, the externa externall system system sends the product product subscr subscription iption request to the BMP.

3.

After receiving receiving the the product product subscr subscription iption reque request, st, the BMP BMP performs performs authen authenticat tication ion to check check whether the subscriber has any child-parent card product.

4.

After the authent authenticati ication on is passed, passed, the BMP BMP updates updates the the subscript subscription ion data data of the the child-pa child-parent rent card products of the subscriber in the physical database.

5.

At the same time, the BMP BMP sends sends a data synchroniz synchronization ation request request to the CBP. CBP.

6.

The CBP CBP updates updates the the child-pa child-parent rent card product product data data in the the memory memory databa database, se, and and then then returns the result to the BMP.

7.

The BMP BMP sends sends a data data sync synchro hroniz nizati ation on reque request st to the the SCP. SCP.

8.

The SCP SCP updat updates es data, data, and and then then retur returns ns the the resul resultt to the the BMP. BMP.

Issue 01 (2010-07-28)


17-3



9.

The BMP BMP returns returns the the product product subscr subscription iption result result to the the external external system system.. Then, Then, the extern external al system returns the result to the subscriber. The process of subscribing to a child-parent card product through the WebService WebService interface interface ends. NOTE

A subscriber who subscribes to a child-parent card product automatically becomes the parent card subscriber.

17.3 Process of Unsubscribing from a Product This section describes the processes of unsubscribing from a child-parent card product.

17.3.1 Process of Unsubscribing from a Child-Parent Card Product Through the WebService Interface Figure 17-2 shows the process of unsubscribing from a child-parent card product through the WebService interface. Figure 17-2 Process of unsubscribing from a child-parent card product through the WebService interface External BMP system Subscriber applies for product unsubscription Unsubscription request

CBP

SCP

Authenticate Update the subscription data Data synchronization request Return result


Data synchronization request

Return result



NOTE

Before unsubscribing from a child-parent card product, you must cancel all the child cards bound to the parent card. card.

The process of unsubscribing from a child-parent card product is similar to the process of subscribing to a child-parent card product. The only difference is that the external system invokes 17-4


Issue 01 (2010-07-28)



the WebService interface to perform product unsubscription on the BMP in the process of unsubscribing from a child-parent card product. For process details, see 17.2.1 Process of Subscribing to a Child-Parent Card Product Through the WebService Interface .

17.4 Process of Changing a Consumption Limit This section describes the process of changing a consumption limit of a child card. A subscriber with a parent card can set a monthly consumption limit for each child card. If the subscriber with the parent card sets Support Consumption Limit on Child Card to No, it indicates that a subscriber with a child card can use the balance of the parent card account without limit. The subscriber with the parent card can set the consumption limit of each child card through the IVR or WebService interface. interface. After the accumulated consumption of a child card reaches the consumption limit, the subscriber with the child card cannot use the account of the parent card for consumption. The OCS will notify the subscriber with the child card of this case by playing a voice or sending sending a short message. The cycle of the consumption consumption limit is the same as the bill cycle. Therefore, the OCS clears the consumption amount of the subscriber with the child card after the bill cycle ends. The common methods of changing a consumption limit are as follows: l

Through the WebService interface

l

On the SMAP

l

Through the IVR

17.4.1 Process of Changing a Consumption Limit Through the WebService Interface Figure 17-3 shows the process of changing a consumption li mit through the WebService interface. Figure 17-3 Process of changing a consumption limit through the WebService interface interface External BMP CBP system Changing the Invoke the consumption WebService limit request Interface to change the consumption limit Changing the consumption limit request Verify data

Return result

Change the consumption limit


The process description is as follows: Issue 01 (2010-07-28)


17-5



1.

A subscriber subscriber sends a request request for changing changing the the consumptio consumption n limit of of a child child card. card. The reque request st is sent to an external system.

2.

After receiving receiving the request request,, the extern external al system system sends sends the the request request to to the BMP BMP through through the the WebService interface.

3.

The BMP receiv receives es the the requ request est,, and and then then sends sends it to the CBP. CBP.

4.

After receiving receiving the the request, request, the the CBP verif verifies ies data data to check check whether whether the the child-pa child-parent rent card card service is enabled for the subscriber.

5.

After the verific verification ation is passed, passed, the the CBP changes changes the the consumpti consumption on limit, limit, and and then returns returns the result to the BMP.

6.

The BMP BMP returns returns the result result to the external external system system,, and then then the external external system system returns returns the result to the subscriber. The process of changing the consumption limit through the WebService interface ends.

17.4.2 Process of Changing a Consumption Limit on the SMAP Figure 17-4 shows the process of changing a consumption li mit on the SMAP. Figure 17-4 Process of changing a consumption limit on the SMAP SMAP Changing the consumption limit request

BMP

Invoke the WebService Interface to change the consumption limit

CBP

Changing the consumption limit request Verify data

Return result



The process of changing a consumption limit on the SMAP is similar to the process of changing a consumption limit through the WebService interface. For process details, see 17.4.1 Process of Changing a Consumption Limit Through the WebService Interface .

17.4.3 Process of Changing a Consumption Limit Through the IVR Figure 17-5 shows the process of changing a consumption li mit through the IVR.

17-6


Issue 01 (2010-07-28)



Figure 17-5 Process of changing a consumption limit through the IVR SCP

CBP

Subscriber dials IVR access code Play voice to interact with subscriber Subscriber selects to change the consumption limit

Changing the consumption limit request Verify data

Return result


Return result


A subscr subscribe iberr dials dials the IVR IVR acces accesss code. code. The The call call reache reachess the SCP. SCP.

2.

The SCP SCP interac interacts ts with with the subscr subscriber iber by playing playing a voice. voice. The subscriber subscriber selects selects to change change the consumption limit.

3.

The SCP sends sends the the subs subscr cribe iberr requ request est to the the CBP. CBP.

4.

The CBP receives receives the the subscriber subscriber request, request, and then verifi verifies es data, data, such such as checkin checking g whether whether the subscriber has any child-parent card product.

5.

After the verific verification ation is passed, passed, the CBP change changess the consump consumption tion limit limit for the the subscrib subscriber. er. Then, the CBP returns the result to the SCP.

6.

The SCP SCP returns returns the result result to the subscri subscriber. ber. The proces processs of changin changing g a consump consumption tion limit limit through the IVR ends.

17.5 Process of Recharging a Child Card and a Parent Card This section describes the process of recharging a child card and a parent card. The process of recharging a child-parent card account is the same as the process of recharging a common account. The recharge includes recharging a parent card, common child cards, and special child cards. l

In the case of recharging a parent card, the process is the same as the process of recharging a common account through recharge cards.

l

In the case of recharging a common child card, the recharge amount is directly added to the account of the parent card because the common child card has no separate account.

l

In the case of recharging a special child card, system processing varies according to recharge modes.

The processes of recharging a common child card and a special child card are described respectively according to the IVR and USSD recharge modes. Issue 01 (2010-07-28)


17-7



17.5.1 Process of Recharging a Child Card and a Parent Card Through the IVR Process of Recharging a Common Child Card Through the IVR Figure 17-6 shows the process of recharging a common child card through t he IVR. Figure 17-6 Process of recharging a common child card through the IVR MSp

MSC/VLR/SSP

SCPc

CBPc

SCPp

CBPp

VC

Subscriber dials IVR access code IDP CCR{Initial} Authenticate CCA{Initial} RRBE System plays voice to interact with subscriber Subscriber chooses to recharge Verification is passed, and system continue to play voice to i nteract with subscriber


Enter recharged number(parent card ) and recharge card password Execute recharge

Execute recharge card authentication authentication request Execute authentication authentication response

Authenticate


Debit and reward

Execute recharge resetting request Execute recharge resetting response

Reset

CCR{Terminate}

Execute recharge confirmation response

Confirm recharge and CCA{Terminate} write CDR

CCR{Terminate} CCA{Terminate} Return recharge result Return recharge result

NOTE

A subscriber with a common child card initiates a recharge request. In the preceding figure, the subscript c indicates the NE corresponding to the subscriber with a common child card, and the subscript p indicates the NE corresponding to the subscriber with the parent card.

17-8


Issue 01 (2010-07-28)



The process of recharging a common child card through the IVR is similar to the process of recharging another account through the IVR. When recharging a common child card, enter the number of the parent card as the recharged number. After the recharge succeeds, the system notifies both the subscriber with the child card and the subscriber with the parent card of the recharge result at the same time. For process details, see the process of recharging another account in 5.2 Process of Recharging an Account by Using a Recharge Card Through IVR .

Process of Recharging a Special Child Card Through the IVR When a subscriber with a special child card initiates a recharge request, the subscriber can select to recharge the account of the parent card or the personal account. If the subscriber selects to recharge the personal account, the recharge process is the same as the process of recharging the personal account account through through the IVR. If the subscriber subscriber selects selects to recharge recharge the account account of the parent parent card, the recharge process is the same as the process of recharging another account through the IVR. For process details, see the process of recharging another account and the process of recharging the personal account in 5.2 Process of Recharging an Account by Using a Recharge Card Through IVR .

17.5.2 Process of Recharging a Child Card and a Parent Card Through the USSD Process of Recharging a Common Child Card Through the USSD A subscriber with a common child card can send one of the following recharge codes to recharge the account: l

*USSD access code* code * password of a recharge card #: #: In this case, the recharge amount goes to the account of the parent card, and the recharged number is changed to the number of the parent card.

l

*USSD access code* code* password of a recharge card *mobile phone number #: #: In this case, the recharge amount goes to the corresponding mobile phone number. If the CBP checks that the mobile phone number is bound to a child card but the child card does not have a separate account, the recharge amount goes to the account of the corresponding parent card.

For process details, see 5.3 Process of Recharging an Account by Using a Recharge Card Through USSD.

Process of Recharging a Special Child Card Through the USSD A subscriber with a special child card card can send one of the following recharge codes to recharge the account: l

*USSD access code* code * password of a recharge card card #: #: In this case, the recharge amount directly goes to the account of the child card.

l

*USSD access code* code* password of a recharge card *mobile phone number #: #: In this case, the recharge amount goes to the corresponding mobile phone number. If the CHG checks that the mobile phone number is bound to a child card but the child card does not have a separate account, the recharge amount goes to the account of the corresponding parent card.

For process details, see 5.3 Process of Recharging an Account by Using a Recharge Card Through USSD USSD. Issue 01 (2010-07-28)


17-9



17.6 Process of Performing Monthly Settlement for a Child Card and a Parent Card This section describes the process of performing monthly settlement for a child card and a parent card. The rules of deducting rentals of a child card and a parent card are as follows: l

Common child card If the system fails to deduct the monthly rental of the child-parent card product of the parent card, the account of the parent card cannot be used to pay fees for the child card, and all the services cannot be used.

l

Special child card The rental deduction method of a special child card is the same as that of a common child card. When the system fails to deduct the monthly rental of the child-parent card product of the parent card, the account of the parent card cannot be used to pay fees for the child card. If deducting other monthly rentals of the parent card fails, the function of using the account of the parent card to pay fees for the child card is not affected.

After recharge is successful, the rules of deducting owing monthly rentals are as follows: l

Recharging a common child card The process of deducting the owing monthly rental of t he parent card is triggered. If the child card also owes the monthly rental, the owing monthly rental of the child card is deducted when the child card uses services or a scheduled task periodically deducts the owing monthly rental.

l

Recharging the parent card by the subscriber with a special child card The process of deducting the owing monthly rental of t he parent card is triggered. If the child card also owes the monthly rental, the owing monthly rental of the child card is deducted when the child card uses services or a scheduled task periodically deducts the owing monthly rental.

l

Recharging the parent card The sequence of deducting the owing monthly rentals for different child cards depends on the sequence in which the child cards use services. If no child cards use services, a scheduled task periodically deducts the owing monthly rentals.

17.7 Reference This section describes the terms used in child-parent card service processes. None.

17-10


Issue 01 (2010-07-28)


18 Passby Processes

18

Passby Processes

About This Chapter 18.1 Overview Overview In the OCS system, system, service passby passby refers to a solution to connecting services such as the call service and SMS SMS directly in certain cases so that subscribers can use the services normally. 18.2 Process of Passing by a Service Manually This section describes the concept of manual passby and the process of passing by a service manually. 18.3 Process of Passing By a Service Automatically This section describes the process of passing by a service automatically. 18.4 Process of Passing by a Service by the SCP Database This section describes the process of passing by a service by the S CP database. 18.5 Process of Passing by a Service by the Physical Database of the CBP This section describes the process of passing by a service by the physical database of the CBP. 18.6 Process of Passing by Data Services by the MDSP This section describes the process of passing by data services by the MDSP. 18.7 Reference Reference This section briefly section briefly describes describes the basic terms related to the passby processes.

Issue 01 (2010-07-28)


18-1


18 Passby Processes

18.1 Overview In the OCS system, service passby refers to a solution to connecting services such as the call service and SMS directly in certain cases so that subscribers can use the services normally. A service can be passed by in any of the following ways: l

Manually When the carrier performs an operation such as upgrade, capacity expansion, inspection, and migration on a device, the carrier can pass by certain subscribers or number segments. When the operation is complete, an operator needs to manually instruct the SCP to end the service passby. If no operator instructs the SCP to end the service passby, the subscribers and number segments remain in passby state.

l

Automatically When the CBP is busy, a system fault occurs in the CBP, or a fault occurs in the communication link between the SCP and CBP, the OCS system automatically passes by the services such as calls and short messages so that subscribers can use the services normally. The passby ends when the fault is rectified.

l

By the SCP database When an exception occurs in the SCP database, the SCP database passes by services so that subscribers can use the services normally. In this case, the effect of the fault on subscriber experience can be reduced. The passby ends when the database fault is rectified.

l

By the physical database of the CBP The physical database of the CBP is used in certain cases, for example, recharge rollback. If the physical database of the CBP is faulty, the service use of subscribers may be affected. In this case, services are passed by when the physical database of the CBP is faulty to reduce the effect of the fault on the service use of subscribers. The passby ends when the database fault is rectified.

l

By the MDSP MDSP passing by data services means that the MDSP decides whether to pass by services according to configuration information when an exception occurs on the message links between the MDSP and the CBP.

When the passby ends, the OCS system charges the subscriber based on the offline CDRs generated during the passby.

18.2 Process of Passing by a Service Manually This section describes the concept of manual passby and the process of passing by a service manually. The manual passby modes include the following: l

Passing by services according to service types For example, the SCP can pass by voice calls and short messages.

l

18-2

Passing by services according to CBP nodes


Issue 01 (2010-07-28)


18 Passby Processes

When the SCP connects to multiple CBP nodes, if a CBP node restricts calls, the SCP may consider that all the CBP nodes restrict calls. In this case, the OCS system supports passing by services according according to the ID of a CBP node. node. l

Pass by services unconditionally

l

Passing by services according to number segments The SCP can pass by services according to a specific number segment.

l

Passing by services according to discrete numbers The SCP can pass by services according to a specific number.

Normal Process The process of passing by a service manually, which corresponds to the three procedures in red in Figure 18-1, is described as follows: 1.

Before Before the passby passby,, determine determine the number number segments segments that that need to be passe passed d by or data such as CBP node IDs, and then update the number segments or data to the SCP.

2.

During During the passby passby,, when a call call of a subscr subscriber iber is passed passed by, by, the CBP CBP rededu rededucts cts fees fees according to the passby CDRs generated by the SCP.

3.

After After the the passb passby y ends, ends, disab disable le the the passby passby flag flagss on the the SCP. SCP.

Figure 18-1 shows the normal process of passing by a service manually. Figure 18-1 Normal process of passing by a service manually SMAP

SCP

CBP

Update the passby flag Update flag of passing by number segments

Before passby

Update flag of passing by number segments Trigger service

Read service passby flag Determine whether the number segment of the number needs to be passed by

During passby

Generate passby CDR Send passby CDR

Resume service passby flag After passby

Rededuct fees based on passby CDR

Resume flag of passing by number segments Resume flag of passing by number segments

Issue 01 (2010-07-28)


18-3


18 Passby Processes


An operato operatorr updates updates the passby passby flag on the SMAP SMAP at at the service service maintenanc maintenancee website website and and marks the data such as the number segments that need to be passed by.

2.

The SMAP SMAP synchroniz synchronizes es the updated updated passby passby flag to the the SCP through through the the BMP. BMP.

3.

A subscri subscriber ber makes a call. call. Then the service service is trigger triggered ed to to the SCP.

4.

The SCP SCP reads reads the the passby passby flag flag and and determine determiness whether whether the the number number segme segment nt that that the subscriber number belongs to needs to be passed by. If the number segment does not need to be passed by, the SCP processes the call according to the normal service process. Otherwise, the SCP passes by the call and connects the call directly, and the CBP will not process the call.

5.

When When the the call call ends ends,, the the SCP SCP gene generat rates es a passby passby CDR. CDR.

6.

The SCP SCP sends sends the passby passby CDR to to the CBP. CBP. Then Then the CBP rededuc rededucts ts fees fees based based on the the passby CDR.

7.

After the passby passby ends, ends, the the operator operator needs needs to update update the the passby passby flag flag on the the SMAP SMAP at at the service maintenance website and disable the passby flag.

8.

The SMAP SMAP synchr synchroniz onizes es the updated updated flag flag of passing passing by number number segments segments to the the SCP. SCP. After the flag of passing by number segment is disabled, the subsequent service process runs according to the normal service process.

Exception Handling Process When the CBP rededucts fees based on the passby CDR, if the account balance of the subscriber is insufficient, the fee rededuction fails, and the CBP changes the subscriber state to suspend. The subscriber state becomes normal only after the subscriber recharges the account and the fee rededuction is successful.

18.3 Process of Passing By a Service Automatically This section describes the process of passing by a service automatically.

Normal Process The OCS system provides a fault tolerance mechanism. When the CBP is busy, a system fault occurs in the CBP, or a fault occurs in the communication link between the SCP and CBP, the OCS system automatically passes by the services such as calls and short messages as configured so that subscribers can use the services normally. In addition, the corresponding passby CDRs are generated on the SCP. After the fault is rectified, the CBP performs rating and charging on the subscribers based on the passby CDRs, and the passby ends automatically.

Exception Handling Process When the CBP rededucts fees based on the passby CDR, if the account balance of the subscriber is insufficient, the fee rededuction fails, and the CBP changes the subscriber state to suspend. The subscriber state becomes normal only after the subscriber recharges the account and the fee rededuction is successful. 18-4


Issue 01 (2010-07-28)


18 Passby Processes

18.4 Process of Passing by a Service by the SCP Database This section describes the process of passing by a service by the SCP database. When an exception occurs in the SCP database, the SCP database passes by services so that subscribers can use the services normally. When the SCP passes by services, the simplified voice call service or SMS service based on CAMEL2/3 needs to be enabled to support the calls and short messages initiated by subscribers. After the simplified voice call service or SMS service based on CAMEL2/3 is enabled, enabled, the system does not perform perform service operations operations involving the database, for example, number analysis and fee calculation. The CDRs are recorded directly.

Process of Passing By a CAMEL2 Short Message by the SCP Database If the SCP database is configured to pass by a CAMEL2 short message sent by a subscriber, the SCP determines whether the process is the SMS process according to the service key value. If yes, the SCP records a w_smo offline CDR.

Process of Passing By a CAMEL2 Voice Call by the SCP Database in the Calling Process Figure 18-2 shows the process of passing by a CAMEL2 voice call by the SCP database in the calling process. Figure 18-2 Process of passing by a CAMEL2 C AMEL2 voice call by the SCP database in the calling process MSC/VLR/SSP

SCP

CBP

Subscriber makes a call Trigger call according to O-CSI IDP Determine service key RRBE FCI Continue Connect call Accumulate call duration

Subscriber hangs up ERB RC

Record offline CDR

The process is described as follows: Issue 01 (2010-07-28)


18-5


18 Passby Processes

1.

A subscribe subscriberr makes makes a CAMEL2 CAMEL2 voice voice call call when when the SCP databa database se is config configured ured to to pass by CAMEL2 voice calls. Then the call reaches the MSC/VLR/SSP. The MSC/VLR/SSP determines the subscriber type according to the number segment of the subscriber. If the subscriber is a postpaid subscriber, the MSC/VLR/SSP delivers the Connection message. If the subscriber is a prepaid subscriber, the MSC/VLR/SSP sends an SRI message to the HLR and obtains the O-CSI of the subscriber from the HLR. Then the MSC/VLR/SSP determines the SCP that the subscriber belongs to and the service that needs to be triggered according to the GT code and service key in the O-CSI.

2.

The MSC/V MSC/VLR/SS LR/SSP P reports reports an IDP IDP message message to the SCP to start start call call contro control. l. The IDP message contains the information such as the service key, calling number, and called number.

3.

The SCP SCP determine determiness whether whether the service service is a call call service service accor according ding to the the service service key key value and whether the SCP database is configured to pass by voice calls. If yes, the SCP delivers an RRBE message to the MSC/VLR/SSP to request the dynamic configuration of the EDP. NOTE

The MSC/VLR/SSP creates a BCSM for each call. Each call has a series of states. A detection point is set between two states, that is, a breakpoin breakpointt in a call.

4.

The SCP SCP sends sends a Continue Continue message message to prompt prompt the MSC/VLR MSC/VLR/SSP /SSP to connect connect the the call. call. In addition, the SCP delivers an FCI message.

5.

When the callin calling g party party or called called party party hangs hangs up, up, the the MSC/VLR/ MSC/VLR/SSP SSP reports reports an ERB message to the SCP, and the SCP records an offline CDR (w_abr CDR).

6.

The SCP SCP sends sends an RC message message to prompt prompt the MSC/VLR/SS MSC/VLR/SSP P to discon disconnect nect the call. call. Then Then the call ends.

Process of Passing By a CAMEL2 Voice Call by the SCP Database in the Called Process Figure 18-3 shows the process of passing by a CAMEL2 voice call by the SCP database in the called process.

18-6


Issue 01 (2010-07-28)


18 Passby Processes

Figure 18-3 Process of passing by a CAMEL2 voice call by the SCP database in the called process MSC/VLR/SSP a

HLRb

MSC/VLR/SSP b

SCPb

CBPb

Subscriber A makes a call Initiate route query Perform route query

Return T-CSI Trigger call according to T-CSI IDP

Determine service key RRBE FCI Continue Request the query of MSRN Send PRN request Query MSRN

Return result Return result Connect call

Connect call Accumulate call duration

Subscriber hangs up ERB

RC

Record offline CDR


When the SCP SCP database database is configur configured ed to pass by by CAMEL2 CAMEL2 voice voice calls, calls, subscr subscriber iber A makes makes a call to subscriber B. The call reaches MSC/VLR/SSPa. NOTE

Assume that: l


l

Subscriber A is the calling party, and subscriber B is the called party.

If the calling party is a non-OCS subscriber, the called process of an OCS subscriber is similar to this process.

2.

MSC/VLR/SSPa sends an SRI request to HLR b. HLR b returns the T-CSI of subscriber B to MSC/VLR/SSPa.

3.

MSC/VLR/SSPa triggers the call to SCP b according to the T-CSI.

Issue 01 (2010-07-28)


18-7


18 Passby Processes

4.

SCP b determines whether the service is a call service according to the service key value and whether the SCP database is configured to pass by voice calls. If yes, the SCP b delivers an RRBE message to MSC/VLR/SSPa to request the dynamic configuration of the EDP.

5.

SCP b sends a Continue message to prompt MSC/VLR/SSPa to connect the call. In addition, the SCP b delivers an FCI message.

6.

MSC/VLR/SSPa sends an SRI request to HLR b again to request HLR b to return the MSRN (Mobile Station Roaming Number) of subscriber B.

7.

HLR b sends a PRN request to MSC/VLR/SSP b to query the MSRN of subscriber B.

8.

MSC/VLR/SSP b finds the MSRN of subscriber B and returns the MSRN to HLR b.

9.

HLR b returns the MSRN to MSC/VLR/SSP a.

10. 10. MSC/ MSC/VL VLR/ R/SS SSP Pa connects the call to MSC/VLR/SSP b. 11. 11. MSC/ MSC/VL VLR/ R/SS SSP P b connects the call to subscriber B. Then the call is connected. 12. When the the calling calling party party or called called party hangs hangs up, up, MSC/VLR/S MSC/VLR/SSP SP b reports an ERB message to the SCP b, and the SCP b records an offline CDR (w_abr CDR). 13. The SCP b sends an RC message to prompt the MSC/VLR/SSP b to disconnect the call. Then the call ends.

Process of Passing By a CAMEL3 Short Message by the SCP Database If the SCP database is configured to pass by CAMEL3 short messages, when a subscriber sends a CAMEL3 short message, the SCP determines whether the service is the SMS service according to the service key value. If yes, the SCP connects the CAMEL3 short message directly and records a w_smo offline CDR.

18.5 Process of Passing by a Service by the Physical Database of the CBP This section describes the process of passing by a service by the physical database of the CBP. When the CBP database is faulty, for example, the database is busy, or the database is disconnected, the physical database of the CBP passes by services to ensure that the services not accessing the physical database are not affected. In this case, the effect of the fault on the service use of subscribers can be reduced. The processes that need to use the physical database of the CBP include the following: SMS confirmation process, recharge rollback process, fee rededuction process, product unsubscription process (the rental table needs to be queried), and idle-subscriber load process. When the physical database is faulty, the insert, update, delete, and query operations involved in the preceding processes can still be performed.

18.6 Process of Passing by Data Services by the MDSP This section describes the process of passing by data services by t he MDSP. MDSP passing by data services means that the MDSP decides whether to pass by services according to configuration information when an exception occurs on the message links between the MDSP and the CBP. 18-8


Issue 01 (2010-07-28)


18 Passby Processes

If the MDSP decides to pass by data services, all the services are not authenticated and charged by the CBP, and the MDSP MDSP generates pass-by pass-by CDRs. After the CBP is recovered, recovered, the MDSP MDSP does not pass by services, and all the services are authenticated and charged on the CBP in normal DCC message mode. The pass-by CDRs generated on the MDSP during the pass-by process are collected by the Mediation and are sent to t he CBP for rating and fee deduction. Figure 18-4 shows the networking about the pass-by of data services on the MDSP. Figure 18-4 Networking about passing by data services by the MDSP DCC

CBP

FTP

RBI

FTP

Mediation

MDSP

According to the preceding figure, when the communication between the MDSP and the CBP is normal, interaction is carried out through DCC messages. When the communication is abnormal, the MDSP passes by services, the Mediation collects offline CDRs, and then the CDRs are sent to the CBP t hrough the RBI for rating and fee deduction.

18.7 Reference This section briefly describes the basic terms related to the passby processes. None.

Issue 01 (2010-07-28)


18-9


19 Audit Process

19

Audit Process

About This Chapter 19.1 Overview This section describes the audit process of the OCS system. 19.2 Audit Process This section describes the audit process. 19.3 Reference This section describes the terms used in the audit process.

Issue 01 (2010-07-28)


19-1


19 Audit Process

19.1 Overview This section describes the audit process of the OCS system. The OCS system supports auditing accounting and CDRs. l

Auditing accounting The accounting audit function includes the functions of balancing accounting and balancing fund account data. The function of balancing accounting refers to the function of balancing the general ledger of the system. The function of balancing fund account data refers to the function of checking whether accounting data is balanced according to the formula of balancing fund account account data.

l

Auditing CDRs The CDRs that can be audited include the following types: –

CDRs of the UVC and CBP

–

Call CDRs of the SCP and CBP

–

Transfer CDRs

–

Offline CDRs of the SCP

–

CDRs of the EVC and CBP

19.2 Audit Process This section describes the audit process. Each financial item of a system can be audited through financial methods. The accounting audit function of the OCS system is: The OCS system records the account balance of a subscriber at the beginning of each bill cycle and the account balance of the subscriber at the end of each bill cycle. Then the OCS system uses the accounting balancing formula to check whether the actual account balance of the subscriber is the same as the account balance calculated according to the fees on the CDRs (including the consumption CDRs and payment CDRs) of the subscriber. The accounting balancing formula is as follows: Account balance of a subscriber at the end of a bill cycle = Account balance of the subscriber at the beginning of this bill cycle + Payment amount of this bill cycle - Consumption amount of this bill cycle The accounting balancing function is used to audit the charging precision of CDRs. The function is also used to check whether the account balance of a subscriber has been changed abnormally. For example, if the account balance of a subscriber has been changed manually on a day, the accounting data of the subscriber on that day is unbalanced.

19.3 Reference This section describes the terms used in the audit process. None.

19-2


Issue 01 (2010-07-28)


A Glossary

A

Glossary

Lists all terms, acronyms, and abbreviations used in the OCS for your reference.

Issue 01 (2010-07-28)


A-1


A Glossary

A.1 Numerics 3G

Third Generation Mobile Communication

A.2 A AAA

Authentication, Authorization and Accounting

AC

Apply Charging

account

An entity through which a customer can pay for the telecommunications services provided by a carrier. carrier.

account adjustment

A process to adjust account items on which the t wo parties of a settlement cannot benefit equally.

account book

A book that records the information about the i ncome and expense of each fee item in the account by class. An account matches one or more account books. An account book often records the information such as account number, bill cycle, and account book subject.

accumulator

The accumulation of the service usage, consumption, and recharge fees of a subscriber.

ACK

Acknowledgement

ACR

Apply Charging Report

activation

An operation that enables a subscriber to use different telecommunications services provided by a carrier. After being activated, a subscriber account enters the active period, and the state of the subscriber is Active.

admission limit

The minimum consumption amount that a carrier sets for a subscriber in a bill cycle. If the consumption amount of a subscriber does not reach the minimum consumption amount that the carrier sets, the OCS system deducts the minimum consumption amount that the carrier sets.

APN

Access Point Name

appendant product

A type of products that are set by carriers, apart from main products. In general, an appendant product includes value-added services or preferential tariffs.

AVP

Attribute Value Pairs

A.3 B bill

A list through which a carrier provides the service fee information periodically for a subscriber. A bill records the information such as the final balance and the t he fees for using the services and products. Bills are classified into detail bills and summary bills. A carrier charges a subscriber according to the information on the bill.

bill cycle

Settlement cycle. The interval can be set according to the operation strategy of a carrier and is one month in general. When a bill cycle ends, the OCS calculates the fees that a subscriber needs to pay in the bill cycle and generates a bill.

A-2


Issue 01 (2010-07-28)


A Glossary

bill run

A process of calculating the billing result such as the monthly fee, discount, incentive, usage summary, free unit, rebate, and other charge and credit (OCC).

BMP

See Business Management Point

brand

A name that a carrier defines for a combination of products after segmenting t he markets according to the ages, consumption habits, and consumption levels of users to facilitate the promotion. A carrier sells the combination of products by brand to the specified user groups to make profits.

Business Management Point

A network element that manages the operation of services, such as product management, charging management, resource management.

A.4 C CAC

Charging Area Cell

call control

A function of processing a call, consisting of creating, monitoring, maintaining, connecting, and releasing a call and providing service features.

call screening

A service of call control. If the service is enabled for a subscriber, the subscriber can maintain a screening table that records information such as discrete numbers, number segments, areas, time segments, and passwords. Before a call is connected, the system determines whether to continue the call according to the current attribute of the calling subscriber and information such as the screening table, screening type, screening strategy, and screening mode.

CAZ

Charging Area Zone

CBS

See Convergent Billing System

CC

Customer Care

CCBS

Customer Care & Billing System

CDMA

Code Division Multiple Access

CDR

Call Detail Record

charging event

An event that occurs when a subscriber uses a service provided by the carrier. The event is used for charging by the charging module.

Convergent Billing Point

A network element that receives external charging requests and performs online charging and offline charging.

Convergent Billing System

A system that supports multi-network, multi-service, and multi-charging modes. CBS refers to Convergent Billing System. The key features of the CBS are as follows: 1. Convergence of service networks The convergent charging system provides the exact, real-time, and flexible charging and unified customer services for the products and services that are supported by the networks such as the fixed network, 2G, 3G, NGN, and IPTV. 2. Convergence of multiple services The convergent charging system supports the unified charging of voice services and data services. 3. Convergence of rating categories Subscribers can switch between the prepaid mode and postpaid mode. 4. Convergence of online charging and offline charging The convergence of online charging and offline charging is useful in the integrated network environment, especially when certain components in the network cannot trigger the online charging request in real time.

Issue 01 (2010-07-28)


A-3


A Glossary

credit control

A process of controlling the consumption amount of the telecommunications services for a subscriber according to the remaining call fee and credit limit of the subscriber.

credit limit

An amount that a subscriber can overdraw.

CRM

Customer Relationship Management

CUG

Closed User Group

customer

An individual, an enterprise, or a corporation that uses the products or services provided by the carrier or the the partner of the carrier. carrier.

A.5 D day end

An operation that is performed by the system to generate journals according to the Double Entry data in the system.

DCC

Diameter Credit Control

deactivation

An operation that disables a postpaid subscriber to use different telecommunications telecommunications services provided by a carrier. After being deactivated, a subscriber account enters the Disable state.

deregistration

An operation of deregistering a subscriber. After being deregistered, a subscriber cannot use the products and services that are provided by the carrier.

DS

Data Service

A.6 E e-voucher center

A service that provides recharge and payment functions for subscribers through virtual recharge cards. Carriers can issue the virtual recharge cards by setting up distributor channel in the tree mode. Compared with the traditional recharge through real recharge cards, the recharge through virtual recharge cards can save the card cost and enable carriers to understand the precise information about transactions and inventories in time.

ENIP

Enhanced Network Intelligent Platform

A.7 F Familiarity Number

A mobile number that a subscriber sets, which can enjoy a preferential tariff when a call is made between this mobile number and the mobile number of the subscriber.

fee item

A detailed item of the consumption fees of a subscriber. For example, the local call fee item and national toll call fee item.

FEP

Front End Processor

FN

See Familiarity Number

free resource

A resource that a carrier provides for subscribers for free use. Free resources include a certain number of short messages, the call duration, and the data traffic.

FTP

File Transfer Protocol

A-4


Issue 01 (2010-07-28)


A Glossary

A.8 G GGSN

Gateway GPRS Support Node

GPRS

Generally Packet Radio System

GSM

Global System for Mobile Communications

GUI

Graphic User Interface

GW

Gateway

A.9 H HLR

Home Location Register

HTTP

Hypertext Transfer Protocol

A.10 I ICP

Information Content Provider

ID

Identification/Identity

IMSI

International Mobile Subscriber Identity

IN

Intelligent Network

installment rebate

A preference policy with which a carrier returns certain fees to a customer in multiple bill cycles.

IP

Internet Protocol

IPCG

IP Charging Gateway

IPSec

IP Security Protocol

IVR

Interaction Voice Response

A.11 M main product

Basic product that a subscriber must subscribe to for using network resources before subscribing to appendant products. In general, a main product includes basic network services and basic tariffs. In the OCS, the subscription instance of a main product corresponds to one subscriber.

MCC

Mobile Country Code

MMS

Multimedia Messaging Service

MMSC

Multimedia Messaging Service Center

MO

Mobile Originated

monthly settlement

System operation of generating monthly settlement data on the basis of the double-entry bookkeeping data recorded recorded by the system.

Issue 01 (2010-07-28)


A-5


A Glossary

MSC

Mobile Switching Center

MSISDN

Mobile Subscriber International ISDN/PSTN Number

MT

Mobile Terminated

A.12 N NE

Network Element

A.13 O OCS

See Online Charging System

Online Charging System

A system that implements the convergence of online charging and offline charging, voice service charging and data service charging, prepaid subscriber management and postpaid subscriber management. The OCS system provides the functions such as rating, subscriber balance management, and real-time monitor.

A.14 P package

A set of services that a carrier uses to propaganda and launch a brand to attract subscribers.

PIN

Personal Identity Number

pool period

A period in which a subscriber of an account that is in Disable state does not recharge the account after the deletion period An account in this period is in Pool state. A subscriber in Pool state cannot perform any operations. The OCS system deletes the subscriber account and reclaims the number resources after the pool period.

POS

Postpaid Subscriber

postpaid

A mode in which a subscriber is allocated a certain credit and the subscriber does not need to pay fees in advance when using a telecommunications service.

PPS

Prepaid Subscriber

prepaid

The mode in which a subscriber pays for the telecommunication services provided by a carrier in advance.

price plan

A set of pricing policies provided by a carrier for a group of telecommunications services. The charging system can calculate the fees for using the service based on the service usage and pricing plan of a subscriber.

PRM

Partner Relationship Management

product

A combination of one or more services with predefined tariff. Carriers can directly sell the combination of services to customers.

PSTN

Public Switched Telephone Network

A-6


Issue 01 (2010-07-28)


A Glossary

A.15 R rating

To perform the fee calculation on t he preprocessed service records according to charging resources, tariffs, subscriber information, and product information.

RBT

Ring Back Tone

roaming in

A process for a subscriber to access the home telecommunications network from a nonhome telecommunications network.

roaming out

A process for a subscriber to access a non-home telecommunications network from the home telecommunications network.

A.16 S SDP

Service Data Point

service

A group of functions, material objects, or procedures that a service provider develops for sale in products. A service does not have any price and cannot be sold to subscribers.

settlement

A process of allocating the collected service fees that are generated during the cooperation between partners when a telecommunications service involves the communication resources or value-added service resources of multiple partners. The fee allocation is based on the resource usage and agreement that is signed by the partners in advance.

SIM

Subscriber Identity Module

SMAP

Service Management Access Point

SMG

Short Message Gateway

SMP

Service Management Point

SMS

Short Message Service

SMSC

Short Message Service Center

SP

Service Provider

SSP

Service Switching Point

suspension period

The period in which a subscriber account is not recharged after the activation period. An account in the suspension period is in Suspend state. Generally, the balance and bonus resources of an account in Suspend state are available. The subscriber is restricted in using certain services. For example, a subscriber of an account that is in Suspend state cannot use the free resource account for making calls. If a subscriber recharges an account during the suspension period, the account returns to Active state. At the same time, the validity period of the account is extended.

A.17 T tariff

The designation of the pricing, discount policies, and applicable rules of a product.

TCP

Transfer Control Protocol

Issue 01 (2010-07-28)


A-7


A Glossary

A.18 U upper limit

The maximum consumption amount that a carrier sets for a subscriber in a bill cycle. If the consumption amount if a subscriber exceeds the maximum consumption amount that the carrier sets, the OCS system still deducts the maximum consumption amount that the carrier sets.

URL

Universal Resource Locator

USSD

Unstructured Supplementary Service Data

UVC

Uniform Voucher Center

A.19 V VC

Voucher Center

VPN

Virtual Private Network

A.20 W WISG

A-8

Wireless Integrated Service Gateway


Issue 01 (2010-07-28)

139218749 HUAWEI OCS Business Process Description

Recommend Documents