01-04 Procedures for Intelligent Network Services(3)

8/18/2019 01-04 Procedures for Intelligent Network Services(3)

1/24

HUAWEI CSOFTX3000

Service Procedures Contents

Issue 02 (2007-01-15) Huawei Technologies Proprietary i

Contents

4 Procedures for Intelligent Network Services .......................................................................4-1

4.1 Architecture of WIN......................................................................................................................................4-2

4.1.1 Functional Entities in WIN .............................................................. .................................................... 4-2

4.1.2 Network Architecture...........................................................................................................................4-3

4.2 Procedure for IN Management Service ....................................................................... ..................................4-3

4.3 Procedure for PPC Service in Target Network........... ............................................................................ .......4-5

4.3.1 Procedure for Location Registration .................................................................... ................................4-5

4.3.2 Procedure for Call Origination.............................................................................................................4-6

4.3.3 Procedure for Call Termination............................................................................................................4-8

4.3.4 Procedure for Call Forwarding ........................................................... ...............................................4-10

4.4 Procedure for PPC Service in Overlay Network................................................................... ......................4-18

4.4.1 Call Procedure in the OVERLAY PPC Service ................................................................... ..............4-18

4.4.2 Procedure for Call Origination...........................................................................................................4-18

4.4.3 Procedure for Call Termination..........................................................................................................4-20

4.5 Procedure for PL Service ..................................................................... ....................................................... 4-21


2/24

Figures

HUAWEI CSOFTX3000

Service Procedures

ii Huawei Technologies Proprietary Issue 02 (2007-01-15)

Figures

Figure 4-1 Procedure for IN management service..............................................................................................4-4

Figure 4-2 Location registration procedure........................................................................................................4-5

Figure 4-3 Procedure for a call originated by a PPC subscriber.........................................................................4-6

Figure 4-4 Procedure for a call terminated to a PPC subscriber.................. ....................................................... 4-9 Figure 4-5 HLR-based CF procedure (CFNA).................................................................................................4-13

Figure 4-6 HLR-based CF procedure (CFU)....................................................................................................4-14

Figure 4-7 SCP-based CF procedure (CFNA)..................................................................................................4-15

Figure 4-8 SCP-based CF procedure (CFU).....................................................................................................4-17

Figure 4-9 Call origination in OVERLAY SSP service......... ..................................................................... ......4-19

Figure 4-10 Call termination in OVERLAY SSP service................................................................. ................4-21

Figure 4-11 Procedure for PL service registration............................................................................................4-22


3/24

HUAWEI CSOFTX3000

Service Procedures 4 Procedures for Intelligent Network Services

Issue 02 (2007-01-15) Huawei Technologies Proprietary 4-1

4 Procedures for Intelligent NetworkServices

About This Chapter

The following table lists the contents of this chapter.

Section Describes

4.1 Architecture of WIN The functional entities and network architecture of thewireless intelligent network.

4.2 Procedure for IN

Management Service

The procedure for IN management service.

4.3 Procedure for PPC Service

in Target Network

The procedures for location registration, call origination,

and call termination of PPC subscribers.

4.4 Procedure for PPC Servicein Overlay Network

The procedures for the PPC calls and SSP calls in theoverlay network.

4.5 Procedure for PL Service The registration procedure for PL service.


4/24

4 Procedures for Intelligent Network Services

HUAWEI CSOFTX3000

Service Procedures

4-2 Huawei Technologies Proprietary Issue 02 (2007-01-15)

4.1 Architecture of WIN

Based on the CDMA network architecture, the wireless intelligent network (WIN) is addedwith the following functional entities:

Service switching point (SSP)

Service control point (SCP)

Intelligent peripheral (IP)

Service management point (SMP)

Service creation environment (SCE)

Service management access point (SMAP)

4.1.1 Functional Entities in WIN

The CSOFTX3000 carries out IN services with the functional entities such as SSP, SCP, andIP.

SSP

The SSP provides the following functions:

Initiating IN services

Connecting calls

Playing announcements

Reporting responses to the SCP or releasing calls

SCP

The SCP is the core of the WIN. It has the following functions through the MAP interface:

Instructing the SSP to connect calls according to service logic

Instructing the IP to play announcements and collect subscriber information

Communicating with another SCP for service interaction

Managing subscriber accounts

IP

The IP has the following functions:

Supplying specialized resources

Converting speech to text and text to speech

Playing announcements, receiving DTMF signals, and recognizing speech as the SCPinstructed


5/24

HUAWEI CSOFTX3000



4.1.2 Network Architecture

The types of WIN architecture are:

Target networkIn the target network, the VMSC/GMSC provides the SSP function. Therefore, theVMSC/GMSC initiates all IN services and communicates with the SCP according toWIN protocols.

Overlay network

In the overlay network, the VMSC/GMSC does not provide the SSP function. Therefore,after analyzing the special segment that the calling or called number belongs to, the

VMSC/GMSC connects IN services to the SSP. Then the SSP communicates with theSCP to complete calls.

The following describes the service procedures for pre-paid charging (PPC) in each network.

For other IN service procedures, refer to the HUAWEI CSOFTX3000 Mobile SoftSwitch Center Feature Description Volume I.

4.2 Procedure for IN Management Service

IN management service enables a subscriber to query the account balance, recharge, or reportloss by dialing the access number.

The IN management service is needed in both the target work and overlay network to provide

the subscribers with various services. The procedure for the IN management service is as

shown in Figure 4-1.


6/24


HUAWEI CSOFTX3000

Service Procedures


Figure 4-1 Procedure for IN management service

MSCe SCP IP

1.CM ServiceRequest

2.ORREQ

3.SEIZERES

4.seizeres

5.CONNRES

7.INSTREQ

8.SRFDIR

10.srfdir

12.DISCONNRES

13.orreq

6.call setup

9.serving

11.instreq

1. An MS sends a CM Service Request message to the MSCe, requesting the INmanagement service.

2. The MSCe sends the SCP an ORREQ message containing the MIN, MDN andTRIGTYPE.

3. Upon receiving the message, the SCP sends an SEIZERES message, instructing the IPsto allocate the corresponding resources.

4. An IP able to provide resources returns a seizeres message, carrying the TLDN of the IP.

5. The SCP sends a CONNRES message to the MSCe, informing the MSCe of theresources allocated.

6. The MSCe sends encryption information to the IP.

7. The IP sends an INSTREQ information to the SCP.

8. The SCP sends an SRFDIR message, indicating that the announcement starts.

9. The IP provides the corresponding services.

10. The IP sends an srfdir message to the SCP, indicating that the announcement ends.

11. The SCP returns an instreq message to the IP.

12. The SCP sends MSCe a DISCONNRES message to release the IP resources, afterreceiving the srfdir message.

13. The SCP sends an orreq message to the MSCe, and releases the link.


7/24


8/24


HUAWEI CSOFTX3000

Service Procedures


4.3.2 Procedure for Call Origination

Figure 4-3 shows the call origination procedure for a PPC subscriber.

Figure 4-3

Procedure for a call originated by a PPC subscriber

MGWMSCe SCP

1.CM Service Request

2.ORREQ

3.orreq

4.ANLYZD

6.SEIZERES

7.seizeres

8.CONNRES

9.Add Request

10.Add Reply11.Assignment

Request

12.Assignment

Complete

13.INSTREQ

14.SRFDIR

15.Modify Reques t

19.srfdir

20.instreq

22.OANSWER

conversation

24.ODISCONNECT

25.odisconnect

23.MS

disconnect

17.Modify Reques t

18.Modify Reply

5.anlyzd

16.Modify Reply

21.anlyzd


9/24

HUAWEI CSOFTX3000



The following focuses on the communication between the MSCe and SCP in a call originated from a

PPC subscriber. For the messages over the A interface and message flow of establishing a bearer at thecalled side, see Chapter 3 "Procedure for Basic Calls and Short Message Services."

1. A PPC subscriber originates a call. The serving MSCe receives the dialed digits.

2. The MSCe detects the Origination_Attempt_Authorized trigger and sends the SCP anORREQ message according to the SCP routing address in TRIGADDRLIST.

3. After confirming that the subscriber has the PPC service activated and that the account balance is above the threshold, the SCP returns an orreq message, instructing the MSCe

to continue the call processing. The parameter DMH_SVCID in this message indicatesthat the invoked service is the PPC service.

4. The MSCe analyzes dialed digits and prepares to route the call. The MSCe detects theCalling_Routing_Address_Available trigger and sends an ANLYZD message to the SCPassociated with this trigger.

This message helps the SCP:

−

Compute the charging rate of this call according to the calling number and callednumber.

− Determine whether the balance is sufficient for this call.

− Convert the balance into the time that the call can maintain.

5. For an insufficient balance, the SCP sends the MSCe an anlyzd message containing the parameters ACCEDN (indicating that the service is rejected) and ANNLIST.

6. If the balance is sufficient, the SCP sends an SEIZERES message to the MSCerequesting the IP to play an announcement regarding the current balance of the

subscriber's account.

In this message, the parameters SpecializedResource and PrivateSpecializedResource

indicate the resources requested, and the PLIND indicates the preferred language.

7. The MSCe allocates a TLDN and sends it to the SCP through a seizeres message.

8. The SCP sends a CONNRES message to instruct the MSCe to set up a call leg to the IP.

9. The MSCe sends an Add Request message to instruct the MGW to set up a bearer at thecalling side.

10. The MGW returns an Add Reply message to indicate the successful bearer.

11. The MSCe sends an Assignment Request message to request the BSS to set up an Ainterface channel.

12. When the MS enters the assigned traffic channel, the BSS sends an AssignmentComplete message to the MSCe.

13. The MSCe sends an INSTREQ message to the SCP requesting call processing

instructions.

14. The SCP sends an SRFDIR message to the MSCe.

In this message, the ANNLIST parameter indicates the announcement to play.

15. The MSCe sends a Modify Request message to ask the MGW to modify the bearertopology and to connect the announcement resource to the calling party.

16. The MGW sends a Modify Reply message to the MSCe.

17. After the announcement is played to the calling party, the MSCe resends a ModifyRequest message, instructing the MGW to modify the bearer topology and to disconnectthe announcement resource with the calling party.

18. The MGW returns a Modify Reply message to the MSCe.

19. The MSCe sends an srfdir message to the SCP.


10/24


HUAWEI CSOFTX3000

Service Procedures


20. The SCP returns an instreq message and an anlyzd message to release the call leg to theMSCe.

21. The MSCe selects resources such as outgoing routes and connects the call to the called party.

22. After the called party answers, the call of the calling PPC subscriber is connected. TheMSCe detects the O_Answer trigger and sends an OANSWER message to the SCP.

Upon the receipt of the OANSWER message, the SCP begins deducting the subscriber'saccount balance. The call is connected.

23. After the calling MS ends the call, the MSCe detects the O_Disconnect trigger and sendsan ODISCONNECT message to the SCP.

24. Upon the receipt of the ODISCONNECT message, the SCP stops decrementing thesubscriber's account balance and returns an odisconnect message.

25. The MSCe releases the call.

4.3.3 Procedure for Call Termination

Figure 4-4 shows the procedure for a call terminated to a PPC subscriber.


11/24

HUAWEI CSOFTX3000



Figure 4-4 Procedure for a call terminated to a PPC subscriber

MSCe HLR SCP

1.Call origination2.LOCREQ

3.locreq

4.ANLYZD

5.anlyzd

6.LOCREQ

7.locreq

8.ANLYZD

9.anlyzd

11.TANSWER

conversation

13.TDISCONNECT

14.tdisconnect

10.MSanswer

12.MS

disconnect

The bearer establishing procedure for a call made to a PPCsubscriber is the same as that for a call made

to a common mobile subscriber. The following focuses on the procedure related to IN services.

1. An MS originates a call to a PPC subscriber. The originating MSCe receives the dialedMS address digits.

2. The MSCe detects the Mobile_Termination trigger and sends a LOCREQ message to theHLR associated with the called MS.

This message includes the following parameters:

− TRANSCAP: indicating that the MSCe can process TRIGADDRLIST

− WINCAP: indicating the WIN capability of the MSCe

− TRIGTYPE: indicating the Mobile_Termination trigger is detected

3. The HLR sends a locreq message to the MSCe.

In this message, the parameter TRIGADDRLIST indicates the required triggers

Initial_Termination, T_Answer, T_Disconnect, Location, andCalled_Routing_Address_Available.


12/24


HUAWEI CSOFTX3000

Service Procedures


4. The MSCe detects the Initial_Termination trigger and sends the SCP an ANLYZDmessage.

In this message, TRIGTYPE indicates that the Initial_Termination trigger is detected.

5. After confirming that the called subscriber has the PPC service activated and that the

account balance is above the threshold, the SCP sends the MSCe an anlyzd message.In this message, the DMH_SVCID parameter indicates that PPC is invoked.

6. The MSCe detects the Location trigger and sends an LOCREQ message to the HLR.

In this message, the TRIGTYPE parameter indicates that the Location trigger is detected.

7. The HLR determines that the called MS is served by the originating MSCe, and thenreturns a locreq message indicating that the called MS is a local terminal.

8. The MSCe detects the Called_Routing_Address_Available trigger and sends the SCP anANLYZD message.

In this message, the parameter indicates a local call.

9. The SCP sends an anlyzd message to the MSCe.

10. The MSCe sends a Paging Request message to the BSC, instructing the MGW to set up a bearer, and sends the BSC an assigning message. After the called MS answers the call,the BSC returns the MSCe a Paging Response message.

11. The MSCe detects the T_Answer trigger and sends a TANSWER message to the SCP.The call is connected. SSP starts charging.

12. The called PPC subscriber ends the call.

13. The MSCe detects the T_Disconnect trigger and sends a TDISCONNECT message tothe SCP.

Upon receiving the TDISCONNECT message, the SCP stops deducting the subscriber'saccount balance.

14. The SCP returns a tdisconnect message.15. The MSCe releases the call.

4.3.4 Procedure for Call Forwarding

CF services provided by the system enable a called CDMA subscriber to forward incomingcalls to a third party.

If CDMA subscriber A registers a CF service, the forwarded-to number may be one of the

following:

B

B is the mobile directory number (MDN) of the subscriber.

C

C is the number of the public switched telephony network (PSTN) subscriber.

D

D is a specific voice mailbox number

The CF service is classified into the following types:

CFU

CFB

CFNA

CFD


13/24

HUAWEI CSOFTX3000



The following sections describe these CF services.

CFU

Call forwarding–unconditional (CFU) permits a called party to send all incoming calls

addressed to the called party's mobile directory number (MDN) to a directory number (DN) orthe subscriber's voice mailbox.

When CDMA subscriber A who has the CFU service activated is called, the call will always

be forwarded to other pre-set numbers, such as B, C, or D.

If subscriber A registers the CF abbreviated alert service, Subscriber A will receive a CF

abbreviated alert.

CFB

Call forwarding–busy (CFB) permits a called party to have the system send all incoming calls

addressed to the called party's MDN to a DN or to the designated voice mailbox, when thecalled party is busy.

When CDMA subscriber A who has the CFB service activated is called, the call is forwarded

to other numbers, such as B, C, or D if subscriber A is busy:

Subscriber busy includes:

Network-determined subscriber busy

This type of subscriber busy condition is determined by the home location register

(HLR). In this case, the subscriber is really busy. For example, the subscriber is inconversation.

Subscriber-determined busy

This type of subscriber busy condition is determined by the terminating MSCe. In thiscase, the subscriber directly refuses the call when the phone rings.

CFNA

Call forwarding–no answer (CFNA) permits a called party to have the system send incoming

calls addressed to the called party's MDN to a DN or the subscriber's voice mailbox, when thesubscriber fails to answer the call.

When subscriber A who has the CFNA service activated is called, the call is forwarded to B, C,and D in any of the following cases:

The system fails to page the MS or the subscriber does not answer the call when the phone rings.

The MS of the subscriber is deactivated.

The system does not know the current location of the MS.

The subscriber is inaccessible. For example, a DND service is active.

CFD

Call forwarding–default (CFD) permits a called party to send incoming calls addressed to the

called party's MDN to a DN or the subscriber's voice mailbox in some cases.

When subscriber A who has the CFD service activated is called, the call is forwarded to B, C,

and D in any of the following cases:


14/24


15/24

HUAWEI CSOFTX3000



Figure 4-5 HLR-based CF procedure (CFNA)

MSCe HLR SCP


3.locreq

4.ANLYZD

5.anlyzd

6.LOCREQ

7.locreq

8.ANLYZD

9.anlyzd

10.no answer

timeout

11.TRANUMREQ

12.tranumreq

13.ANLYZD

14.anlyzd

15.call forward

The contents in step 1 to step 9 is the same as that in the PPC call termination procedure.Therefore, the following description starts with step 10.

10. The called party (that is, the PPC subscriber who subscribes to the CFNA service)does not answer the call for a long time.

11. Judging that the subscriber meets the requirement for triggering the CFNA, theMSCe sends a TRANUMREQ message to the HLR, requesting a CF number.

12. Judging that the subscriber signs up for the HLR-based CFNA and has the serviceactivated, the HLR returns a tranumreq message. The CF number is carried in theTERMLIST contained in the tranumreq message. Besides, the followinginformation is carried in the TRIGADDRLIST contained in the tranumreq message:

– O_Answer

– O_Disconnect

–

Calling_Routing_Address_Available


16/24


HUAWEI CSOFTX3000

Service Procedures


– address of the corresponding SCP

13. The MSCe detects a Calling_Routing_Address_Available trigger, and sends anANLYZD message to the SCP.

14. The SCP judges whether the account balance of the calling subscriber is sufficient

to initiate the CF call. If yes, the SCP returns an anlyzd message to the MSCe.

15. The CF succeeds.

CFU

Figure 4-6 shows the differences between the HLR-based CF procedure (CFU) and theHLR-based CF procedure (CFNA).

Figure 4-6 HLR-based CF procedure (CFU)

MSCe HLR SCP


3.locreq

4.ANLYZD

5.anlyzd

6.LOCREQ

7.locreq

8.ANLYZD

9.anlyzd

10.call forward

After the Location trigger is triggered and the LOCREQ message is sent, the HLR judgeswhether the subscriber signs up for the CFU and has the service activated. If yes, the

HLR returns the CF number directly in the TERMLIST contained in the locreq message.

the parameter REDIND in the message triggers the CFU. Meanwhile, TRIGADDRLIST in the message returns the following information:

– Calling_Routing_Address_Available

– O_Answer

– O_Disconnect



17/24

HUAWEI CSOFTX3000



Procedure for SCP-Based CF CFNA

Figure 4-7 shows the SCP-based CF procedure (CFNA). The PPC subscriber signs up for

the CF in the SCP. Therefore, the SCP here is classified into the following:– SCP (PPC)

– SCP (CFW)

Figure 4-7 SCP-based CF procedure (CFNA)

MSCe HLR SCP

1.Call origination

2.LOCREQ

3.locreq

4.ANLYZD

5.anlyzd

6.LOCREQ

7.locreq

8.ANLYZD

9.anlyzd

10.no answer

timeout

SCP

CFW PPC

11.TNOANS

12.tnoans

13.ANLYZD

14.anlyzd

15.call forward

As Figure 4-7 shows, the contents in step 1 to step 9 is the same as that in the PPC call

origination procedure. Therefore, the following description starts with step 10.


18/24


HUAWEI CSOFTX3000

Service Procedures


10. The called party (that is, the PPC subscriber who subscribes to the CFNA service)does not answer the call for a long time.

11. Judging that the subscriber meets the requirement for triggering the CFNA, anddetecting the T_No_Answer at the same time, the MSCe sends a TNOANS message

to the SCP, requesting a CF number.12. Judging that the subscriber signs up for the SCP-based CFNA and has the service

activated, the SCP returns the CF number. The CF number is carried in TERMLISTcontained in the tnoans message. Besides, the following information is carried inTRIGADDRLIST contained in the tnoans message:

– O_Answer

– O_Disconnect

– Calling_Routing_Address_Available


13. The MSCe detects the Calling_Routing_Address_Available trigger, and sends an

ANLYZD message to the SCP.14. The SCP judges whether the account balance of the calling subscriber is sufficient

to initiate the CF call. If yes, the SCP returns an anlyzd message to the MSCe.


The differences between the two services lie in step 2. After the

Mobile_Termination trigger is triggered, the HLR judges whether the subscribersigns up for the CFNA and has the service activated. If yes, TRIGADDRLIST

contained in the locreq message carries the following triggers:

– Initial_Termination

– Location

– T_Answer

– T_No_Answer

– T_Disconnect

– Called_Routing_Address_Available

The triggers are use to instruct the MSCe to handle PPC call origination, and to trigger

the SCP-based CF when requirements are met.

CFU

Figure 4-8 shows the SCP-based CF procedure (CFU).


19/24

HUAWEI CSOFTX3000



Figure 4-8 SCP-based CF procedure (CFU)

MSCe HLR SCP

1.Call origination

2.LOCREQ

3.locreq

4.ANLYZD

5.anlyzd

6.ANLYZD

7.anlyzd

SCP

CFW PPC

10.call forward

8.ANLYZD

9.anlyzd

1. The MSCe receives the dialed number from the MS.

2. The MSCe triggers the Mobile_Termination trigger, and sends a LOCREQ message tothe MSCe.

3. Judging that the called subscriber signs up for the SCP-based CFU and has the serviceactivated, the HLR returns a locreq message. TRIGADDRLIST in the locreq messageincludes at least the following triggers:

– Initial_Termination

– Advanced_Termination

–

Called_Routing_Address_Available– Location

4. Detecting and triggering the Initial_Termination trigger, MSCe sends an ANLYZDmessage to the SCP (PPC).

5. The SCP (PPC) judges whether the PPC service of the subscriber is activated, and theaccount balance of the calling subscriber is sufficient to initiate the CF call. If yes, theSCP returns an anlyzd message to the MSCe.

6. The MSCe detects the Advanced_Termination triggers, and sends an ANLYZD messageto the SCP (CWF).

7. The SCP (CFW) judges whether the subscriber signs up for the SCP (CFW) and has theservice activated. If yes, the SCP returns the CF number in TERMLIST contained in the

anlyze message.


20/24


HUAWEI CSOFTX3000

Service Procedures


8. The MSCe detects the Calling_Routing_Address_Available trigger, and sends anANLYZD message to the SCP.

9. The SCP judges whether the account balance of the calling subscriber is sufficient toinitiate the CF call. If yes, the SCP returns an anlyzd message to the MSCe.


4.4 Procedure for PPC Service in Overlay Network

In the overlay network, the CSOFTX3000 can implement the following IN services:

OVERLAY PPC

If the CSOFTX3000 does not have SSP functions, the system overlays the PPC service

to intelligent equipment in the PSTN.

OVERLAY SSP

The CSOFTX3000 serves as a separate SSP in the switching network. It can handle INservices but cannot serve as the VMSC. The OVERLAY SSP can be initiated by the

access code or by number segment. The initiation mode is determined through dataconfiguration. See the HUAWEI CSOFTX3000 Mobile SoftSwitch Center ConfigurationGuide Volume II .

4.4.1 Call Procedure in the OVERLAY PPC Service

Take the IAM message as an example for the messages from the local office to the PSTN. If alocal PPC subscriber originates a call, the MSCe overlays the call to the SSP as follows:

1. The MSCe obtains the SSP access code according to dialed digits and sends an IAM

message to the SSP.2. The SSP initiates IN services and forwards the IAM message to the terminating MSCe.

The following steps are the same as that in common calls.

If a PPC subscriber is the called party, the procedure in overlay services is the same as that incommon calls.

4.4.2 Procedure for Call Origination

Figure 4-9 shows the origination procedure in the OVERLAY SSP service. Here supposes thatOVERLAY SSP service is initiated by number segment and that a PPC subscriber calls a

PSTN subscriber.


21/24

HUAWEI CSOFTX3000



Figure 4-9 Call origination in OVERLAY SSP service

SSP SCP PSTN

1.IAM

2.ORREQ

3.orreq

4.ANYLZD

5.anylzd

6.IAM

7.ACM

8.ACM

9.ANM

11.OANSWER

10.ANM

conversation

12.REL

14.ODISCONNEC

T

13.REL

15.odisconnect

16.RLC

17.RLC

MSCe

1. A PPC subscriber originates a call. The originating MSCe analyzes the special numbersegment that the calling number belongs to, adds corresponding SSP access code as the prefix of the called number, connects the call to the SSP, and sends an IAM message to

the SSP.

2. The SSP detects the Calling_Num_Seg trigger and sends an ORREQ message to the SCPassociated with the PPC subscriber.

3. After confirming that the subscriber has the PPC service activated and the account balance is above the threshold, the SCP returns an orreq message to indicate that the call processing continues. This message contains the triggers O_Answer, O_Disconnect, andCalling_Routing_Address_Available. The parameter DMH_SVCID indicates that the

invoked service is the PPC service.

4. The SSP analyzes dialed digits and prepares to route the call. The SSP detects theCalling_Routing_Address_Available trigger and sends an ANLYZD message to the SCPassociated with this trigger.

This message helps the SCP:


22/24


HUAWEI CSOFTX3000

Service Procedures


− Compute the charging rate of this call according to the calling number and callednumber.

− Convert the money in the balance into the time that the call can last.

− Determine whether the balance is sufficient for this call.

The procedure for playing announcement here is similar to that in calls originated from a PPC subscriberin the target network. The difference is that here the SSP needs to send a CON message to ask the

originating MSC to set up a playing channel after the bearer and IP resources are prepared.

5. The SCP sends an anlyzd message to the SSP.

6. The SSP connects the call to the terminating PSTN and sends an IAM message.

7. After the called party's phone rings, the PSTN sends an ACM message to the SSP.

8. The SSP forwards the ACM message to the originating MSCe.

9. After the called party hooks off, the PSTN sends an ANM message to the SSP.

10. The SSP forwards the ANM message to the originating MSCe.

11. The SSP sends an OANSWER message to the SCP. Upon the receipt of the message, theSCP begins decrementing the subscriber's account balance. The call is connected.

12. After the calling MS ends the call, the originating MSC sends an REL message to theSSP.

13. The SSP forwards the REL message to the PSTN.

14. Upon detection of the O_Disconnect trigger, the SSP sends an ODISCONNECTmessage.

15. Upon the receipt of the ODISCONNECT message, the SCP stops decrementing theaccount balance and returns an odisconnect message.

16. Upon the receipt of the REL message, the PSTN returns an RLC message to the SSP.

17. The SSP forwards the RLC message to the originating MSCe. The MSCe releases thecall.

4.4.3 Procedure for Call Termination

Take a call between mobile subscribers as an example. Most procedures are the same as thosein common calls. Figure 4-10 focuses on the differences to show the termination procedure in

the OVERLAY SSP service.


23/24

HUAWEI CSOFTX3000



Figure 4-10 Call termination in OVERLAY SSP service

MSCe-O SSP HLR MSCe-T

CM ServiceRequest

LOCREQ

locreq

4.IAM

5.ACM

6.ANM

Conversation

SCP

1.IAM

2.ANYLZD

3.anylzd

ACM

ANM

1. The originating MSCe (MSCe-O) analyzes the special number segment that the callednumber belongs to, sends an IAM message to the SSP, and connects the call to the SSP.

2. The SSP sends an ANLYZD message to the SCP associated with the called party.TRIGTYPE indicates that the SSP detects the Calling_Num_Seg trigger.

3. The SCP sends an anlyzd message to the SSP.

4. The SSP connects the call to the terminating MSCe (MSCe-T) and sends an IAMmessage to the MSCe-T.

5. After the called party's phone rings, the MSCe-T sends an ACM message to the SSP.The SSP then forwards the message to the MSCe-O.

6. After the called party hooks off, the MSCe-T sends an ANM message to the SSP. TheSSP then forwards the message to the MSCe-O. The call is connected.

The following steps are the same as those in common calls. Therefore they are omitted.

4.5 Procedure for PL Service

Preferred language (PL) service provides the subscriber with the ability to specify thelanguage for network services. PL is associated with voice communication services, based on

the TIA/EIA-41-D and ANSI/TIA/EIA-664 protocols.


24/24


HUAWEI CSOFTX3000

Service Procedures

Figure 4-11 shows the procedure for the PL service registration.

Figure 4-11 Procedure for PL service registration

BSC MSCe(MGW) VLR

1.CM_SERVICE_REQ

2.FEATREQ(DIGITS)

3.featreq(PLANGIND)

5.Clear Command

7.QUALDIR(PLANGIND)

9.QUALDIR

10.qualdir

8.qualdir

4.Feature Notification

HLR

6.Clear Complete

1. The MS sends a CM_SERVICE_REQ message through the BSC to the MSCe. TheMSCe judges that the subscriber dials the feature codes through the data configuration.Then the MSCe triggers the feature service.

2. The MSCe sends a FEATREQ message to the HLR associated with the MS, containingthe dialed digits.

3. The HLR detects the Preferred Language request and sends a featreq message to theserving MSCe. The featreq message includes an indication of the new preferred language.The serving MSCe stores the new preferred language information.

4. After receiving the featreq message, the MSCe sends a Feature Notification message to

the BSC according to the indication contained in the featreq message.5. The MSCe sends a Clear Command information, instructing the BSC to release the call.

6. The BSC releases the call, and returns a Clear Complete message to the MSCe.

7. The HLR reports the change in the service profile of the MS by sending a QUALDIRmessage to the VLR where the MS is registered.

8. The VLR returns a qualdir message to the HLR.

9. The VLR reports the change in the service profile of the MS by sending a QUALDIRmessage to the serving MSCe.

10. The MSCe returns a qualdir message to the VLR.

Documents

01-04 Procedures for Intelligent Network Services(3)