Documente Academic
Documente Profesional
Documente Cultură
Contents
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
Tables
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
Title Description
5.1 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.
5.2 Availability This section describes the network elements (NEs) that
are required for the feature, whether Licenses are
required, and the version requirements of the NEs.
5.3 Working Principle This section describes the functions of the NEs, and
networking requirements.
5.4 Service Flow This section describes the service flow of the network
when providing this feature.
5.5 Data Configuration This section describes the data configurations that are
required on the MSOFTX3000 and the UMG8900.
5.6 Service Management This section describes the service operations that carriers
and mobile subscribers are required to implement when
the network provides this feature.
5.7 Charging and CDR This section describes the charging and the generation of
CDRs when the network provides this feature.
5.8 Service Interaction This section describes the relationships and restrictions
between this feature and other services or features.
5.9 Reference This section describes the protocols and specifications
that this feature must comply with, and the acronyms and
abbreviations of this chapter.
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.
Name Definition
5.1.3 Benefits
Table 5-3 lists the beneficiaries and description of the benefits.
5.2 Availability
5.2.1 Requirements for NEs
Table 5-4 lists the network elements (NEs) required by the call completion supplementary
services.
√ √ √ √ √ - √ √
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.
----End
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
MSC server
PSTN C GMSC server HLR B MS B
B
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
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.
MSC server
PSTN C GMSC server HLR B MS B
B
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
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.
A wants to retrieve
the A-B call.
RETRIEVE
RETRIEVE ack
CPG
FACILITY
CALL A-B ACTIVE
Figure 5-4 Service flow for alternating from the A-B call to the A-C call
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
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.
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.
Generating CDRs
The command MOD GBILLCTRL is used to generate the call detail records (CDRs) of the
CW and CH services.
For the CH service, the service is activated when it is provided, and the service is deactivated when it is
withdrawn.
Operations
On the MS, mobile subscribers can perform the operations listed in Table 5-8.
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.
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.
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.
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.
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.
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
CW Call Waiting
CH Call Hold