HUAWEI MSOFTX3000

Feature Description Contents

Contents

5 Call Completion Supplementary Service..............................................................................5-1

About This Chapter .............................................................................................................................................5-1
5.1 Service Description .......................................................................................................................................5-2
5.1.1 Function Code......................................................................................................................................5-2
5.1.2 Definition .............................................................................................................................................5-2
5.1.3 Benefits ................................................................................................................................................5-3
5.2 Availability ....................................................................................................................................................5-4
5.2.1 Requirements for NEs..........................................................................................................................5-4
5.2.2 Requirements for License ....................................................................................................................5-4
5.2.3 Applicable Versions..............................................................................................................................5-4
5.3 Working Principle..........................................................................................................................................5-5
5.3.1 Service Data Management ...................................................................................................................5-5
5.3.2 Working Principle of CW.....................................................................................................................5-5
5.3.3 Working Principle of CH .....................................................................................................................5-6
5.4 Service Flow..................................................................................................................................................5-7
5.4.1 Service Flow of CW.............................................................................................................................5-7
5.4.2 Service Flow of CH ...........................................................................................................................5-10
5.5 Data Configuration......................................................................................................................................5-13
5.5.1 Configuring Data at the MSOFTX3000 Side.....................................................................................5-13
5.5.2 Configuring Data at the HLR Side.....................................................................................................5-15
5.6 Service Management ...................................................................................................................................5-15
5.6.1 Overview............................................................................................................................................5-15
5.6.2 Operations by Carriers .......................................................................................................................5-16
5.6.3 Operations by Mobile Subscribers .....................................................................................................5-16
5.7 Charging and CDR ......................................................................................................................................5-17
5.7.1 CW .....................................................................................................................................................5-17
5.7.2 CH......................................................................................................................................................5-18
5.8 Service Interaction ......................................................................................................................................5-19
5.8.1 CW .....................................................................................................................................................5-19
5.8.2 CH......................................................................................................................................................5-20
5.9 Reference ....................................................................................................................................................5-20
5.9.1 Protocols and Specifications ..............................................................................................................5-20

Issue 03 (2006-09-30) Huawei Technologies Proprietary i

 HUAWEI MSOFTX3000
Contents Feature Description

5.9.2 Acronyms and Abbreviations .............................................................................................................5-20

ii Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description Figures

Figures

Figure 5-1 Service flow when a subscriber accepts a waiting call .....................................................................5-7
Figure 5-2 Service flow when a subscriber rejects a waiting call.......................................................................5-9
Figure 5-3 Service flow for holding and retrieving a call................................................................................. 5-11

Figure 5-4 Service flow for alternating from the A-B call to the A-C call .......................................................5-12

Issue 03 (2006-09-30) Huawei Technologies Proprietary iii

HUAWEI MSOFTX3000
Feature Description Tables

Tables

Table 5-1 Name and code of the function...........................................................................................................5-2

Table 5-2 Name and definition of the CW and CH services...............................................................................5-2
Table 5-3 Beneficiaries and description of the benefits ......................................................................................5-3

Table 5-4 NEs required by the call completion supplementary services ............................................................5-4
Table 5-5 Applicable versions of HUAWEI wireless core network products .....................................................5-4
Table 5-6 Related software parameters.............................................................................................................5-14

Table 5-7 Operation modes of the call completion supplementary services.....................................................5-15

Table 5-8 Operations performed by mobile subscribers ...................................................................................5-16
Table 5-9 Interactions between the CW service and other services ..................................................................5-19

Table 5-10 Interactions between the CH service and other services.................................................................5-20

Issue 03 (2006-09-30) Huawei Technologies Proprietary v

HUAWEI MSOFTX3000
Feature Description
5 Call Completion Supplementary Service
About This Chapter
The following table lists the contents of this chapter.
Title
5.1 Service Description
5.2 Availability
5.3 Working Principle
5.4 Service Flow
5.5 Data Configuration
5.6 Service Management
5.7 Charging and CDR
5.8 Service Interaction
5.9 Reference
Issue 03 (2006-09-30) Huawei Technologies Proprietary
5 Call Completion Supplementary Service
Description
This section describes the function code, function
definition of this feature, and the benefits that carriers and
mobile subscribers can obtain from this feature.
This section describes the network elements (NEs) that
are required for the feature, whether Licenses are
required, and the version requirements of the NEs.
This section describes the functions of the NEs, and
networking requirements.
This section describes the service flow of the network
when providing this feature.
This section describes the data configurations that are
required on the MSOFTX3000 and the UMG8900.
This section describes the service operations that carriers
and mobile subscribers are required to implement when
the network provides this feature.
This section describes the charging and the generation of
CDRs when the network provides this feature.
This section describes the relationships and restrictions
between this feature and other services or features.
This section describes the protocols and specifications
that this feature must comply with, and the acronyms and
abbreviations of this chapter.
5-1
 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

5.1 Service Description

5.1.1 Function Code
Table 5-1 lists the name and code of the function.

Table 5-1 Name and code of the function

Name Code

Call completion supplementary services WMFD-020400

5.1.2 Definition
The call completion supplementary services provide two services: call waiting (CW) and call
hold (CH). Subscribers can choose either one to process two calls at the same time.
Table 5-2 lists the name and definition of the CW and CH services.

Table 5-2 Name and definition of the CW and CH services

Name Definition

CW The CW service enables a mobile subscriber to be notified of

an incoming call notification under the following conditions:
z There is no idle service channel for the incoming call.
z The subscriber is in conversation, or has a call on hold.
The subscriber can determine to accept, reject, or ignore the
incoming call. The caller receives notifications during call
waiting.
For one subscriber, only one waiting call is allowed, and the
system disconnects the subsequent incoming calls instantly.

5-2 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Name Definition

CH The CH service enables a mobile subscriber to interrupt the

current call temporarily, and retrieve the call later if required.
When the call is interrupted, the system reserves the traffic
channel allocated for the call.
When a call is on hold, and no active call is set up, a
subscriber can:
z Retrieve the held call.
z Set up an active call.
z Disconnect the held call.
When a call is on hold, and an active call is set up, the
subscriber can:
z Alternate from one call to the other.
z Disconnect the active call.
z Disconnect the held call.
z Disconnect both the active call and the held call.
For one subscriber, only one held call is allowed.

5.1.3 Benefits
Table 5-3 lists the beneficiaries and description of the benefits.

Table 5-3 Beneficiaries and description of the benefits

Beneficiary Description

Carriers The call completion supplementary services add values of services,

and improve the call completion rate.
Mobile Subscribers can activate and deactivate the CW service freely. This
subscribers indicates that subscribers can control the CW service flexibly. After
the CW service is activated, a subscriber can answer another call in
conversation. Therefore, the subscriber can select the one that is more
important.
When the CH service is activated, a subscriber can hold the current
call, and answer another call. This minimizes the possibility of
missing calls, and improves the call completion rate.

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-3

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

5.2 Availability
5.2.1 Requirements for NEs
Table 5-4 lists the network elements (NEs) required by the call completion supplementary
services.

Table 5-4 NEs required by the call completion supplementary services

UE/MS Node RNC/BSC MSC MGW SGSN VLR HLR
B/BTS server

√ √ √ √ √ - √ √

Note:
UE = user equipment; MS = mobile station; BTS = base transceiver station; RNC = radio network
controller; BSC = base station controller; MSC = mobile switching center; MGW = media gateway;
SGSN = serving GPRS support node; VLR = visitor location register; HLR = home location register

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

5.2.2 Requirements for License

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

5.2.3 Applicable Versions

Table 5-5 lists the applicable versions of HUAWEI wireless core network products that the
call completion supplementary services support.

Table 5-5 Applicable versions of HUAWEI wireless core network products

Product Applicable Version

MSC server MSOFTX3000 V100R002 and later versions

MGW UMG8900 V100R002 and later versions

5-4 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

5.3 Working Principle

5.3.1 Service Data Management
Management on Service Data
The HLR performs the following functions:
z Completes the management operations of carriers on service data
z Modifies the subscription information stored in the HLR
z Updates the subscription information in the VLR by inserting subscriber data

Activation and Deactivation of CW

When a subscriber initiates the activation or deactivation operation, the MSC transparently
sends the operation message to the HLR. The HLR modifies the subscription information
stored in the HLR based on the message, and then updates the subscription information in the
VLR by inserting subscriber data.
For the CH service, there is no activation or deactivation operation.

5.3.2 Working Principle of CW

The following section describes the working principle of the CW service.
Step 1 When subscriber B is in conversation, the MSC receives a call from C to B (a C-B call).
Step 2 The MSC queries the subscription information of B. If the CW service is activated for B, the
MSC processes the CW service.
Step 3 The MSC sends a SETUP message for setting up the C-B call to the MS. The message carries
a CW indication.
Step 4 Currently, an A-B call is active or on hold. Therefore, the MS informs B of the incoming call
based on the CW indication. At the same time, the MS sends a response to the MSC,
indicating that B is busy.
Step 5 After receiving the response, the MSC waits for the ALERTING message from the callee.
Step 6 Upon receiving the ALERTING message, the MSC starts the CW timer T2 and the no-reply
timer T3. The MSC then waits for the answer of B. At the same time, the MSC sends an
ALERTING or ACM message to C, carrying the CW indication. Before B answers or
disconnects the call, the MSC of B plays an announcement to C, instructing C to wait for the
call.
Step 7 If B answers before T2 and T3 time out, the MS sends a CONNECT message to the MSC for
connecting the C-B call.
Step 8 The MSC sends a response to the MS, and sends an acknowledge to C, indicating that the C-B
call is set up.
Step 9 If B rejects the call before T2 and T3 time out, the MSC follows the normal flow to
disconnect the waiting call.
Step 10 If T2 or T3 times out, the MSC sends a DISCONNECT message to B and C respectively,
instructing them to release the C-B call.

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-5

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

----End

5.3.3 Working Principle of CH

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

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

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

5-6 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

5.4 Service Flow

5.4.1 Service Flow of CW
Accepting a Waiting Call
The following section describes the flow of the CW service under the following conditions:
z The CW service is activated for B.
z An A-B call is active.
z The fixed network subscriber C calls B.
z B accepts the waiting call.
Figure 5-1 shows the call flow.

Figure 5-1 Service flow when a subscriber accepts a waiting call

MSC server
PSTN C GMSC server HLR B MS B
B

CALL A-B ACTIVE

IAM
SRI
PRN
PRN ack
SRI ack
IAM
SETUP
Call CONFIRMED
ALERTING
ACM
ACM
B wants to connect
the waiting call.

CONNECT

CONNECT ack
ANM
ANM

CALL B-C ACTIVE

IAM: Initial Address Message SRI: Send Routing Information

PRN: Provide Roaming Number ACM: Address Complete Message
ANM: Answer Message ack: Acknowledge

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-7

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

The service flow when a subscriber accepts a waiting call is as follows:

Step 1 The PSTN subscriber C sends an IAM message to the gateway mobile switching center
(GMSC) server.
Step 2 The GMSC server forwards the IAM message to MSC server B after obtaining the mobile
station roaming number (MSRN) of MS B by sending an SRI request.
Step 3 MSC server B sends a SETUP message to MS B. The value of the Signal Information element
in the message is 7 (call waiting tone on).
Step 4 MS B returns a CALL CONFIRMED message. The value of the Cause information element
in the message is 17 (user busy).
Step 5 MSC server B allocates channels with the BSC or RNC.
Step 6 MS B sends an ALERTING message.
Step 7 MSC server B sends an ACM message to the GMSC server, carrying a CW indication. MSC
server B then follows the indication to play an announcement to C, instructing C to wait for
the call.
Step 8 If B answers, MS B sends a CONNECT message to MSC server B.
Step 9 MSC server B returns a CONNECT ack message to MS B.
Step 10 MSC server B sends an ANM message to the GMSC server, instructing C to answer.
Step 11 The B-C call is set up.
----End

The transaction identifier of the signaling messages for the B-C call is different from that for the A-B
call. Thus MS B and MSC server B can identify the signaling messages.

Rejecting a Waiting Call

The following section describes the flow of the CW service under the following conditions:
z The CW service is activated for B.
z An A-B call is active.
z The fixed network subscriber C calls B.
z B rejects the waiting call.
Figure 5-2 shows the call flow.

5-8 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Figure 5-2 Service flow when a subscriber rejects a waiting call

MSC server
PSTN C GMSC server HLR B MS B
B

CALL A-B ACTIVE

IAM
SRI
PRN
PRN ack
SRI ack
IAM
SETUP
CALL CONFIRMED
ALERTING
ACM
ACM B rejects the call
from C.
DISCONNECT
RELEASE
REL
RELEASE
REL COMPLETE
RLC
RLC

IAM: Initial Address Message SRI: Send Routing Information

PRN: Provide Roaming Number ACM: Address Complete Message
REL: Release ack: Acknowledge
RLC: Release Complete

The service flow when a subscriber rejects a waiting call is as follows:

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

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-9

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

Step 8 If B rejects the call, MS B sends a DISCONNECT message to MSC server B. The value of
the Cause information element in the message is 17 (user busy).
Step 9 MSC server B returns a RELEASE message to release the B-C call.
Step 10 MS B returns a RELEASE COMPLETE message, indicating that the release of the B-C call is
complete at the MS side.
Step 11 MSC server B sends an REL message to the GMSC server for call release. The value of the
Cause information element is 17 (user busy).
Step 12 The GMSC server returns an RLC message, indicating that the call release is complete.
----End

The transaction identifier of the signaling messages for the B-C call is different from that for the A-B
call. Thus MS B and MSC server B can identify the signaling messages.

5.4.2 Service Flow of CH

Holding and Retrieving a Call
The following section describes the service flow for holding and retrieving a call under the
following conditions:
z The CH service is activated for A.
z An A-B call is active.
z B is a mobile subscriber.
Figure 5-3 shows the service flow.

5-10 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Figure 5-3 Service flow for holding and retrieving a call

MSC server MSC server

MS A MS B
A B

CALL A-B ACTIVE

A wants to hold the

A-B call.
HOLD
HOLD ack
CPG
FACILITY
CALL A-B on HOLD

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

CPG: Call Progress ack: Acknowledge

The service flow for holding and retrieving a call is as follows:

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

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-11

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

Alternating from One Call to the Other

The following section describes the service flow for alternating from one call to the other
under the following conditions:
z The CH service is activated for A.
z An A-B call is active.
z An A-C call is on hold.
z B and C are mobile subscribers.
Figure 5-4 shows the service flow for alternating from the A-B call to the A-C call.

Figure 5-4 Service flow for alternating from the A-B call to the A-C call

MSC MSC MSC

MS A MS B MSC
server A server B server C
Call A-B active, call A-C on hold

A wants to alternate
from the A-B call to the
A-C call.
HOLD
RETRIEVE
HOLD ack
CPG
RETRIEVE ack FACILITY
CPG
FACILITY
Call A-B on hold, call A-C active

CPG: Call Progress ack: Acknowledge

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

5-12 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Step 7 MSC server C sends a FACILITY message to MS C. In the message, the invoke component is
NotifySS, in which CallOnHold-indicator is callRetrieved. The message is used to inform MS
B that the call is retrieved.
----End

The transaction identifier of the signaling messages for the A-C call is different from that for the A-B
call. Thus MS A and MSC server A can identify the signaling messages.

5.5 Data Configuration

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

Enabling the Service

No additional data is required to enable the service.

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

Related Software Parameters

Table 5-6 lists the related software parameters.

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-13

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

Table 5-6 Related software parameters

Name Meaning Value Default

Value

P19 (ISUP It determines z = 0: If the callee who has registered 1

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

5-14 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Name Meaning Value Default

Value

P129 (CHG It determines z = 0: Generate intermediate CDRs. 1

Parameter 1) whether to z = 1: Generate event CDRs.
Bit 7 generate
intermediate
CDRs or event
CDRs when
the times of
the handover
or
supplementary
service
operations
exceed the
limit.
P130 (CHG It determines z = 0: Generate event CDRs. 1
Parameter 2) whether to z = 1: Not generate event CDRs.
Bit 10 generate event
CDRs when
the subscriber,
in call active
state, invokes
the CW
service.

5.5.2 Configuring Data at the HLR Side

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

5.6 Service Management

5.6.1 Overview
The call completion supplementary services have two operation modes, as listed in Table 5-7.

Table 5-7 Operation modes of the call completion supplementary services

Operation Operation Interface Service Operations
Mode

Operations by HLR z Provide the service.

carriers z Withdraw the service.
z Activate the service (for the CW
service only).
z Deactivate the service (for the CW
service only).

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-15

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

Operation Operation Interface Service Operations

Mode

Operations by MS z Activate the service (for the CW

mobile service only).
subscribers z Deactivate the service (for the CW
service only).
z Release and reject a waiting call.
z Hold an active call, and accept a
waiting call.
z Set up a call, and hold the original
active call.
z Accept a waiting call, and hold an
active call.
z Alternate from an active call to a
held call.
z Retrieve a held call, and release an
active call.
z Release a held call.
z Release both the active call and the
held call.

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

5.6.2 Operations by Carriers

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

5.6.3 Operations by Mobile Subscribers

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

Operations
On the MS, mobile subscribers can perform the operations listed in Table 5-8.

Table 5-8 Operations performed by mobile subscribers

Service Type Operation Type Step

CW Activate the CW On the MS, dial "43#", and then press the Send key.
service.
CW Deactivate the On the MS, dial "#43#", and then press the Send
CW service. key.

5-16 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Service Type Operation Type Step

CW Release and On the MS, dial "0", and then press the Send key.
reject a waiting
call.
CW Release an active On the MS, dial "1", and then press the Send key.
call, and answer a
waiting call.
CW Hold an active On the MS, dial "2", and then press the Send key.
call, and accept a
waiting call.
CH Set up a call, and On the MS, dial the called number of the new call,
hold the original and then press the Send key.
active call.
CH Alternate from an On the MS, dial "2", and then press the Send key.
active call to a
held call.
CH Retrieve a held On the MS, dial "1", and then press the Send key.
call, and release
an active call.
CH Release a held On the MS, dial "0", and then press the Send key.
call.
CH Release both the On the MS, press the Release key.
active call and the
held call.

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

5.7 Charging and CDR

5.7.1 CW
The MSOFTX3000 provides two ways to generate CDRs for the CW service:
z Independent charging
z Segment charging
Independent charging means that the MSOFTX3000 generates the following CDRs:
z The event CDR containing the CW indicator and time stamp based on the CW
notification
z The original MOC or MTC CDR for the whole A-B call

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-17

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

The integrated Gateway Bill (iGWB) integrates the event CDR into the supplementary service
domain of the original mobile originated call (MOC) or mobile terminated call (MTC) CDR
to generate the final MOC or MTC CDR.
Segment charging means that the MSOFTX3000 generates an intermediate MOC or MTC
CDR at the time when a CW notification is generated. The billing center combines the group
of CDRs, and processes other charging. The CW indicator and time stamp are in the last CDR.
The MSOFTX3000 controls the mode for generating CDRs and the frequency for generating
event or intermediate CDRs through the integrated CDR control tables of CHG Parameter 1
Bit 7.
Usually, independent charging is adopted. The following gives an example of independent
charging for the CW service.
The scenario is as follows:
z A in the local office calls B in another office.
z C in another office calls A when A is in conversation with B.
The supplementary service domain in the MOC CDR generated by the local office for the A-B
call records the supplementary service operation. The supplementary service indicator is CW,
and the time stamp is the time when a SETUP message is sent to A.

5.7.2 CH
The MSOFTX3000 provides two ways to generate CDRs for the CW service:
z Independent charging
z Segment charging
Independent charging means that the MSOFTX3000 generates the following CDRs:
z The event CDR containing the CH indicator and time stamp based on the hold and
retrieve operations
z The original MOC or MTC CDR for the whole call
The iGWB integrates the event CDR into the supplementary service domain of the original
MOC or MTC CDR to generate the final MOC or MTC CDR.
Segment charging means that the MSOFTX3000 generates an intermediate MOC or MTC
CDR at the time of the hold and retrieve operations. The billing center combines the group of
CDRs and processes other charging. The CH indicator and time stamp are in the last CDR.
The MSOFTX3000 controls the mode for generating CDRs, and the frequency for generating
event or intermediate CDRs through the integrated CDR control tables of CHG Parameter 1
Bit 7.
Usually, independent charging is adopted. The following gives an example of independent
charging for the CH service.
The scenario is as follows:
z A in the local office calls B in another office.
z A holds the call when A is in conversation with B.
The supplementary service domain in the MOC CDR generated by the local office for the A-B
call records the supplementary service operation. The supplementary service indicator is CH,
and the time stamp is the time when A sends a HOLD message.

5-18 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

5.8 Service Interaction

5.8.1 CW
Table 5-9 lists the interactions between the CW service and other services.

Table 5-9 Interactions between the CW service and other services

Service Interaction

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

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-19

 HUAWEI MSOFTX3000
5 Call Completion Supplementary Service Feature Description

Service Interaction

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

5.8.2 CH
Table 5-10 lists the interactions between the CH service and other services.

Table 5-10 Interactions between the CH service and other services

Service Interaction

CH and CW If both CW and CH services are activated, a subscriber can use the CH
service to answer a waiting call.
If the subscriber is in conversation, and has a call on hold, the subscriber
can still receive a CW indication, but cannot answer the call.
If the subscriber is not in conversation, but has a call on hold, the
subscriber can receive a CW indication.
CH and The CH and MPTY services are compatible.
MPTY If both CH and MPTY services are activated, a subscriber can hold an
active MPTY call, set up another call, and retrieve the MPTY call after the
new call is complete.

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

5.9.2 Acronyms and Abbreviations

Acronym/Abbreviation Full Name

CW Call Waiting

5-20 Huawei Technologies Proprietary Issue 03 (2006-09-30)

HUAWEI MSOFTX3000
Feature Description 5 Call Completion Supplementary Service

Acronym/Abbreviation Full Name

CH Call Hold

Issue 03 (2006-09-30) Huawei Technologies Proprietary 5-21