TN - SP021 - E1 - 0 Call Flow and Supplementary Service Flow in CS Domain-65

TN_SP021_E1_0 Call Flow and
Supplementary Service Flow in CS domain
Reference:
· ZXWN MSC Server (V3.0) Technical Manual
· ZXWN MGW (V3.0) Media Gateway Technical Manual

Contents
1 Mobile Call Process......................................................................................................................................1
1.1 Basic Call Process................................................................................................................................1
1.1.1 UE Originated Call...................................................................................................................1
1.1.2 UE Terminated Call..................................................................................................................5
1.1.3 Call Release Process...............................................................................................................11
1.2 Bearer Setup Process.........................................................................................................................13
1.2.1 MO Bearer Setup Network Model.........................................................................................13
1.2.2 MT Bearer Setup Network Model..........................................................................................19
1.2.3 Call Release Signaling Process..............................................................................................29
2 SMS..............................................................................................................................................................33
2.1 SMS Function....................................................................................................................................33
2.2 SMS Process......................................................................................................................................33
2.2.1 SM MO Process......................................................................................................................33
2.2.2 SM MT Process......................................................................................................................34
2.2.3 Alert Message Process............................................................................................................36
3 Other Services.............................................................................................................................................39
3.1 Supplementary Services....................................................................................................................39
3.1.1 Supplementary Service Functions..........................................................................................39
3.1.2 Supplementary Service Operations........................................................................................40
3.2 Data Services.....................................................................................................................................45
3.3 Intelligent Services............................................................................................................................47
i
1 Mobile Call Process
 Key points
· Basic call process (including UE originated call, UE terminated call and call
release process)
· Bearer setup process of mobile originated call and terminated call
1.1 Basic Call Process
1.1.1 UE Originated Call
1.1.1.1 Network Structure for UE Originated Call
Fig. Basic Call Process-1 Network Structure of Basic UE Originated Call
The MS originated call involves these network units: UE, RNS, VMSCS/VLR, and
destination switch. The basic call setup process is as follows:
1. The sends the call originating message through the air interface. The message
1
contains the called address.
2. The RNS uses the lu interface to transfer this message to the VMSCS.
3. The VMSC sends the SIFOC message to the VLR, and checks the subscription
authority.
4. If the VLR recognizes the call, it returns the call completion indication.
5. After receiving the call completion indication, the VMSCS sets up the bearer
channel with the UE, analyzes the called address, and selects a trunk route to the
called party to send the IAM signaling to the peer switch.
1.1.1.2 Basic Singling Process
Fig. Basic Call Process-2 UE Originated Signaling Process
1. When the user originates a call, the CM sub-layer of the UE sends a Connection
2
Chapter 1 Mobile Call Process
Management service request message to the MM sub-layer and requests the MM

to set up a signaling connection. The MM requests the RRC to set up an RR
connection. The RRC sends the Channel Request message to the network. The
network returns the Immediate Assignment message. After the RR connection is
set up, the MM sends the Connection Management service request message
through the RR connection.
2. The RNS transparently transmits this message to the VMSC.
3. The VMSC sends the Process Access Request message to the VLRA.
4. The VLRA can start the authentication procedure or security procedure. The
VLR sends the Authenticate message to the MSC. The MSC and RNS
transparently transmit this message. The UE returns the Authentication
Response message. The MSC relays the Authentication Ack to the VLR.
· Authentication procedure: If the VLRA determines that the call of the UE is

legal, it sends the Process Access Request ack message to the VMSC. The
VMSC sends the CM Service Accept message to the RNS. The RNS
transparently transmits this message to the UE.
· Security procedure: The VLRA sends the Start Security Procedure message to
the VMSC. The VMSC transmits this message to the RNS. After receiving the
message, the RNS executes the security procedure. After successful completion
of the security procedure, the UE performs the subsequent operation as it
receives the CM Service Accept message.
5. If the UE receives the CM Service Accept message or the security procedure is

implemented successfully, the CC sub-layer of the UE sends the Set-up message
to the CC sub-layer of the MSC. The message includes the address of the called
user B and the bearer capability indication required for this call. The RNS
transparently transmits the CM layer message, but does not process it.
6. The VMSC exports a basic service type according to the bearer capability
parameters of the SETUP message, and determines whether the IWF resource is
required.
7. The VMSC sends the SIFOC message to the VLRA, implements the call
restriction, subscription service and CUG check, and requests outgoing calls.
The message contains the called number and basic service information.
3
TN_SP021_E1_0 Call Flow and Supplementary Service Flow in CS domain
8. If the VLRA judges that the MS can originate the call according to the
subscription information about the MS, the VLRA sends the Complete Call
message to the VMSC. Otherwise, it sends the SIFOC negative response to the
VMSC, and rejects the call setup.
9. The VMSC sends a Call Processing to the MS, which indicates that the call
request is accepted. If some bearer capability parameters need to be negotiated,
the call processing message will contain the modified bearer capability
parameters.
10. The VMSC generates the QoS parameters necessary for the RAB setup
according to the bearer capability parameters, sends the RAB Assignment
Request message to the RNS, and starts the RAB setup procedure.
11. After receiving the RAB assignment request, the RNS allocates the related
channel for the MS according to the QoS parameters of the RAB, and initiates
the RRC connection setup procedure between the MS and the network. After the
completion of the channel assignment, the RNS sends the RAB
AssignmentResponse message to the VMSC.
12. After receiving the RAB Assignment Response message, the VMSC implements
the number analysis on the called address in the SETUP message, and selects a
trunk route to the called party to send the IAM signaling to the peer switch
(taking the inter-switch signaling ISUP as an example).
13. If the call reaches the called party, the called party starts ringing. The terminal
switch returns the ACM message. The VMSC sends the Altering message to the
MS. The MS will hear the called ringing prompt tone.
14. After the called party picks up the phone, the terminal switch returns the ANM
message. The VMSC sends the Connect message to the MS.
15. The UE sends back the Connect Ack message. After receiving the message, the
VMSC connects the bidirectional channel. The caller and caller start talking.
16. If the caller hangs up first, the MS sends the Disconnect message to the network.
After receiving the message, the VMSC disconnects the voice channel, sends the
REL signaling to the terminal switch, releases the voice channel, and sends back
the Release message to the MS.
17. After receiving the Release message, the MS sends back the Release Complete
4
message to the network.
18. After receiving the Release Complete message, the MSC release call related
resources and the MM connection.
1.1.2 UE Terminated Call
1.1.2.1 Network Structure for UE Terminated Call
Fig. Basic Call Process-3 Network Structure for UE Terminated Call
When the mobile user acts as a callee, the network first pages the UE at the radio
interface. If the VPLMNB supports the Gs interface, that is, the UE sets up the relation
between the VLRB and SGSN, the paging message is sent out from the PS domain
first.
The basic called procedure is as follows:
1. After receiving the ISUP IAM, the GMSCB uses the MAP protocol to request
UEB route information from the HLRB.
2. The HLRB uses the MAP protocol to request the roaming number from the
VLRB.
3. The VLRB returns a Provide Roaming Number Ack message to the HLRB. The
message contains the roaming number.
5
4. The HLRB returns a Send Routing Info ack message to the GMSCB. The
message contains the roaming number.
5. The GMSCB analyzes the obtained roaming number, selects a trunk to the
VMSC, and sends an ISUP IAM message to the VMSC.
6. After receiving the IAM message, the VMSC sends the SIFIC message to the
VLR. The VLR finds the called subscription information according to the
MSRN and checks the subscription of the MS.
7. After successful check, the VLRB sends a paging request to the VMSC.
8. The VMSC pages the UE through the air interface.
9. After the UE responds, the VMSC sends the Page ack message to the VLRB.
The VLRB can implements the user access procedure for the MS through the
VMSC. After the completion of the user access procedure, the VLRB sends the
call completion indication to the VMSC. Then the VMSC sends the SETUP
message to the MS and starts the call setup.
6
1.1.2.2 Basic Signaling Process
Pre-paging
Fig. Basic Call Process-4 UE Terminated Signaling Process with the Prepaging Procedure
1. After receiving the IAM message, the GMSCB obtains the called number UEB.
After obtaining the home HLRB address of the UEB according to the MSISDN
of the UEB, the GMSCB sends an SRI message to the HLRB. If the GMSC
supports the prepaging procedure, it sets the related parameters in the SRI
message.
7
2. After receiving the SRI message, the HLRB obtains the MSISDN of the UE, and
finds the user record according to the MSISDN. After obtaining the number
VLRB of VLR where the UEB is located, the HLRB sends a roaming number
request (PRN) to the VLRB. In addition, the HLRB judges whether the
prepaging procedure is supported (The judgment condition is whether both
GMSCB and HLRB are supported). If it is supported, the related parameters are
set in the PRN message.
3. The VLRB receives the PRN request, and allocates a roaming number. If the
UEB is allowed to be served, it sends a paging request to the VMSCB, and
requests the VMSCB to page the UEB.
4. IF the radio channel between the network and the UEB has been established, the
VMSCB immediately responds to the call request. If the radio channel has not
been established, the VMSCB sends the paging request to the RNS. The RNS
broadcasts the paging message on the paging channel. If the Gs interface
(VLRB<->SGSN) exists between the VMSCB and SGSN, the paging is
originated through the SGSN.
5. In normal cases, the UEB in idle state monitors the paging channel at all times.
After receiving the paging message, the UEB sends the channel request to the
network..
6. The RNS sends the immediate assignment message to the UEB, and sets up the
signaling connection for the UEB.
7. After receiving the immediate assignment message, the UEB sends the paging
response message to the network through the signaling connection.
8. After receiving the paging response message, the RNS sets up the signaling
connection between the RNC and MSC, and transmits the paging response
message to the VMSCB through the Initial UE message.
9. After receiving the paging response, the VLRB sends the PRN Ack message to
the HLRB, and sets a timer for waiting for the GMSC call arrival.
10. Then the VLRB can implement the authentication procedure or security
procedure (Note: The MS user access procedure and GMSC call setup procedure
are implemented simultaneously, therefore, the call setup time can be shortened).
11. After receiving the PRN Ack message, the HLR sends the SRI Ack message to
8
the GMSC.
12. After receiving the SRI Ack message, the GMSCB analyzes the roaming
number, finds a trunk to the VMSCB according to the analysis result, and sends
the IAM signaling to the VMSCB.
13. After receiving the IAM message, the VMSCB sends the SIFIC message to the
VLRB, and requests incoming call authentication. The message contains the
roaming number.
14. The VLRB searches the currently activated service instance according to the
MSRN. After finding the instance, the VLRB sends the Call arrived message to
the MSCB, and stops monitoring the timer (Note: If the timer expires, the radio
connection established in the pre-calling will be released). Steps 4~17 are the
prepaging process. Steps 18~33 are the process that the system does not support
prepaging. The prepaging is an optional function. If the system supports the
prepaging function, perform Step 34 after completing the prepaging process. If
the system does not support the prepaging function, skip Steps 4~17 and go to
Step 18.
15. The VLRB sends the PRN ack (roaming number request response) message to
the HLRB. The message contains the roaming number.
16. The HLRB relays this message to the GMSCB, that is, it sends the PRI ack
(route information request response) message. The message contains the
roaming number.
17. After receiving the IAM message, the VMSCB sends the SIFIC message to the
VLRB, and requests incoming call authentication. The message contains the
roaming number.
18. The VLRB searches the user record of the UEB according to the roaming
number. After finding the record, the VLRB judges whether it is allowed to
access this call according to the user information about the UEB. If yes, the
VLRB sends the paging request to the VMSCB, and requests the VMSCB to
page the UEB.
19. If the radio channel between the network and the UEB has been established, the
VMSCB immediately responds to the call request. If the radio channel has not
been established, the VMSCB sends the paging request to the RNS. The RNS
broadcasts the paging message on the paging channel. If the Gs interface
9
(VLRB<->SGSN) exists between the VMSCB and the SGSN, the paging is
implemented through the SGSN.
20. In normal cases, the UEB in idle state monitors the paging channel at all times.
After receiving the paging message, the UEB sends the channel request to the
network.
21. The RNS sends the immediate assignment message to the UEB and sets up the
signaling connection for the UEB.
22. After receiving the immediate assignment message, the UEB sends the paging
response message to the network through the signaling connection.
23. After receiving the paging response message, the RNS sets up the signaling
connection between the RNC and the MSC through the Initial UE message, and
transmits the paging response message to the VMSCB.
24. The VMSCB sends the Process Access Request to the VLRB, which indicates
that the MS already responds to the paging message.
25. The VLRB can implement the authentication procedure or security procedure.
26. According to the result of the user access procedure, if the UEB is allowed to be
served, the VLRB sends the Process access request ack message to the VMSCB
and completes the user access procedure.
27. Then the VLRB sends the call completion message to the VMSCB.
28. After receiving the call completion message, the VMSCB sends the Set-up
message to the UEB. The message contains the required bearer capability for the
call. (If the caller originates the call from the PSTN, the bearer capability
parameter cannot be obtained. In this case, the SETUP message will not contain
the bearer capability parameter).
29. After receiving the Set-up message, the UEB conducts the compatibility check
for the SETUP message. If the check succeeds, the Call confirmed message is
sent to the network. If some bearer capability parameters need to be negotiated,
the message contains the modified bearer capability information.
30. After receiving the Call confirmed message, the VMSCB starts the channel
assignment procedure. This procedure is the same as the MO procedure.
31. After the completion of channel assignment, the UEB sends the Alerting
10
message to the network, and generates ringing tone to alert the user.
32. After receiving the Altering message, the VMSCB converts the message into
ACM message and sends it to the GMSCB. At the same time, the VMSCB
applies for a ringing alerting tone and connects this tone to the backward
channel for the caller.
33. The GMSCB relays this message to the originating switch.
34. After the user hears the ringing tone and answers the call (by pressing the call
key on the mobile phone), the UEB sends the Connect message to the network.
35. After receiving the Connect message, the VMSCB will:
· Send the UEBConnect ack message;
· Send the GMSCBANM message, forward this message to the originating switch
through the GMSCB, connect the bidirectional voice channel between the caller
and callee, and release the ringing tone;
· Send the call completion response message to the VLRB.
36. The call is in connected state. The call release procedure is the same as that of
the MO call.
1.1.3 Call Release Process
1.1.3.1 Network Originated Call Release Process
Fig. Basic Call Process-5 Network Originated Call Release Process
11
After the completion of the call, if the callee hangs up first, the network originates the
call release process to the caller.
1. After receiving the hang-up signal of the callee, the network sends the
Disconnect message to the caller.
2. After receiving the message, the UE sends the Release message to the network.
3. After receiving the message, the network sends the Release Complete message
to the UE and starts the MM connection release procedure.
4. The network sends the Iu Release Command to the RNS, and releases the Iu
interface signaling connection and related RAB resources.
5. After receiving the message, the RNC sends the Channel Release message to the
UE, requests the UE to release the Uu interface RR signaling connection and
related RAB resources, returns the Iu Release Complete message to the MSC,
and releases the Iu interface signaling connection and related RAB resources.
1.1.3.2 UE Originated Call Release Process
Fig. Basic Call Process-6 UE Originated Call Release Process
After the completion of the call, if the caller hangs up first, the MS originates the call
release process.
1. After the user hangs up, the UE sends the Disconnect message to the network.
2. After receiving the Disconnect message, the network sends the Release message
to the UE.
12
3. After receiving the message, the UE sends the Release Complete message.
4. After receiving the Release Complete message, the MSC starts releasing the
associated MM connection. The MSC sends the Iu Release Command to the
RNC, and requests the release of the Iu interface signaling connection and
related RAB resources.
5. After receiving the message, the RNC sends the Channel Release message to the
UE, requests the UE to release the Uu interface RR signaling connection and
related RAB resources, returns the Iu Release Complete message to the MSC,
and releases the Iu interface signaling connection and related RAB resources.
The signaling connection release is completed.
1.2 Bearer Setup Process
1.2.1 MO Bearer Setup Network Model
The figure below shows the MO network model. The real line indicates the call control
signaling, and the broken line indicates the bearer control signaling (The A interface
has no bearer control signaling). The MSC Server controls the context of the two
bearer terminations on the MGW. The bearer termination T1 is used as the bearer for
the RNC/BSC, while T2 is used as the bearer for the next MGW.
MSCS
T1 T2
RNC/BSC CTX1
MGW A
Fig. Bearer Setup Process-7 MO Network Model
According to the inter-office bearer setup mode, there are two types of call time
sequence. One is the forward bearer setup, the other is the backward bearer setup.
13
1.2.1.1 MO Forward Bearer Signaling Setup Process
Fig. Bearer Setup Process-8 shows the MO call setup time sequence in the forward
bearer setup mode.
UE RNC/BSC MSCS MGW
SETUP
CALL PROCEEDING Step1

Initial Address
Bearer Information
Context ($) ADD.request ($) Step2

Establish Bearer +
Context (C1) ADD.reply (T2) Change Through - Connection
Bearer Establishment
UMTS:
Context (C1) ADD.request ($)

Prepare Bearer +
Context (C1) ADD.reply (T1)
Change Through - Connection Step3
RAB ASSIGNMENT REQ
Bearer Establishment and Iu UP
Initialization UP Init
RAB ASSIGNMENT COMPL
UP Init Ack
GSM:
Context (C1) ADD.request (T1)

Reserve Circuit + Step4
ASSIGNMENT REQUEST
ASSIGNMENT COMPL
Continuity Step5
Fig. Bearer Setup Process-8 MO Call Setup Time Sequence in the Forward Bearer Setup Mode
14
UE RNC/BSC MSCS MGW
Address Complete
ALERTING
Answer
Context (C1 ) MOD.request (T1) Change Through-Connection +

Activate Inter-Working
Function
Context (C1 ) MOD.reply (T1) (when applicable) +
Step6
Activate Voice Processing
Function (when applicable)
Context (C1 ) MOD.request (T2)
Context (C1 ) Function (when applicable) +
MOD.reply (T2)
Activate Voice Processing
CONNECT
Fig. Bearer Setup Process-9 MO Call Setup Time Sequence in the Forward Bearer Setup Mode (Continued)
Process description:
Step 1: In originating a call, the user dials the called number on the mobile phone, and
then presses the call key. The MS starts to set up the call. The MS first applies for a
control channel, and sets up an MM connection with the MSC Server to complete
necessary user access operations (including the authentication and encryption
procedure). After these operations are performed, the MS sends a Setup message to the
MSC Server. This message contains the information such as the called number and
bearer characteristics. After receiving the Setup message, the MSC Server conducts
necessary service check and judges whether the user has the right to originate the
service. If the check succeeds, the MSC Server sends the CallProceeding message to
notify the MS of the call proceeding. Because the forward bearer is set up, the IAM
message is combined and forwarded to the next node. The IAM message indicates that
the bearer is set up in the forward bearer setup mode. If the access bearer has not been
established, the IAM message indicates that there is a subsequent Continuity message.
Step 2: After receiving the Bearer Information message which shall contain the bearer
address of the incoming bearer termination that the next node applies for, and binding
reference and bearer attributes sent by the next node, the MSC Server can use the
information to send the ADD command to the MGW to set up the outgoing bearer
termination. In this way, the forward bearer is established, and the Establish Bearer
procedure is included. The created bearer termination T2 requests the incoming bearer
termination of the next node to establish the bearer connection. The Change Through-
15
Connection procedure indicates that the external continuity of the created bearer
termination is bidirectional.
Step 3: The RNC establishes the RAB. The radio bearer setup mode is unrelated to the
network bearer setup mode, but both are implemented by the RNC through the MSCS.
Then the MSC Server starts the RAB setup procedure: The MSC Server first applies
for a T1 from the MGW through the PrepareBear procedure. After successful
application, the MSC Server obtains MGW Address and BNCID parameter
corresponding to T1, converts the bearer service parameters into related RAB
parameters, and sends the RAB parameters through the RAB assignment request. The
RNC uses the received MGW address and BNCID to initiate the bearer setup
procedure to the MGW. After the bearer is established, the system starts the IuUP
initialization procedure. After the completion of initialization, the RNC sends the RAB
assignment completion message to the MSC Server. The RAB assignment is
completed.
4: The RAB of the BSC is established. For calls accessed by the BSC, the Reserver
Circuit message is sent to use the terrestrial circuit. After the circuit is used
successfully, the assignment procedure is initiated to the BSC.
5: The MSCS sends the Continuity message to the backward office, which indicates
that the frontage bearer has been set up successfully.
6: Upon the arrival of the call, the ringing tone is sent to the called party, and called
switch sends the AddressComplete message to the MSC Server. The MSC Server sends
the ALERTING message to the MS. The MS will hear the ringing tone. After the called
user picks up the phone, the called switch returns the Answer message to the caller.
After receiving this message, the MSC Server requests the MGW to connect T1 and T2
through the ChangeThrough –Connection procedure, and optionally initiates the
Activate IWF procedure (for data services) and the Activate VoiceProcessingFunction
procedure (for example, echo suppression function). After these procedures are
completed, the MSC Server sends the CONNECT message to the MS. The caller talks
to the callee.
1.2.1.2 MO Backward Bearer Setup Signaling Process
The figure below shows the MO time sequence in the backward bearer setup mode.
16
RN MS
UE RNC/BSC MSCS MGW
E C C W
SETUP
CALL PROCEEDING
UMTS:
Context (C$) ADD.request ($)

Prepare Bearer +
RAB ASSIGNMENT REQ
Bearer Establishment and Iu UP

Initialization
GSM:
Context (C$) ADD.request (T1)

Reserve Circuit +
Step2
ASSIGNMENT REQUEST
ASSIGNMENT COMPL

Prepare Bearer
Initial Address
Step3
UP Init
UP Init Ack
Fig. Bearer Setup Process-10 MO Setup Time Sequence in the Backward Bearer Setup Mode
17
UE RNC/BSC MSCS MGW

E C C W
Address Complete
ALERTING
Answer
Context (C1 ) MOD.request (T1) Change Through-Connection +

Step3
Activate Inter-Working Function
Context (C1 ) MOD.reply (T1) (when applicable) + Activate
Voice
Processing Function (when
applicable)
Context (C1 ) MOD.request (T2)
Function (when applicable) +
Context (C1 ) MOD.reply (T2) Activate Voice
Processing
CONNECT
Fig. Bearer Setup Process-11 MO Setup Time Sequence in the Backward Bearer Setup Mode (Continued)
1. In originating a call, the user dials the called number on the mobile phone, and
then presses the call key. The MS starts to set up the call. The MS first applies
for a control channel, and sets up an MM connection with the MSC Server to
complete necessary user access operations (including the authentication and
encryption procedure). After these operations are performed, the MS sends a
Setup message to the MSC Server. This message contains the information such
as the called number and bearer characteristics. After receiving the Setup
message, the MSC Server conducts necessary service check and judges whether
the user has the right to originate the service. If the check succeeds, the MSC
Server sends the CallProceeding message to notify the MS of the call
proceeding. Because the backward bearer is set up, the RAB assignment
procedure starts before the IAM message is sent to the backward office.
2. If the user is accessed to the BSC, the circuit assignment procedure is

implemented.
3. After the completion of the RAB assignment, the PrepareBear procedure is

implemented to apply for a network bearer T2 from the MGW. The
InitialAddress message containing the MGW-ID, MGW address and BNC ID
corresponding to T2 is sent to the backward office. The other setup modes are
the same as the forward setup modes.
18
1.2.2 MT Bearer Setup Network Model
After receiving the call request from other offices, that is, the callee is a user of the
local MSC Server/VLR, the MSC Server/VLR starts the MS called setup process. In
this case, the MSC Server/VLR already allocates an MSRN to this call. The called
number in the IAM message is this MSRN. The MSRN is set in the original called
number in the IAM.
Fig. Bearer Setup Process-12 shows the MT network model. The real line indicates the
call control signaling. The broken line indicates the bearer control signaling (The A
interface has no bearer control signaling). The MSCS Server controls the contexts of
the two bearer terminations on MGW B. The bearer termination T1 is used as the
bearer for the RNC/BSC, and the bearer termination T2 is used as the bearer for MGW
A selected by the GMSC Server. The GMSC Server controls the contexts of the two
bearer terminations on MGW A. The bearer termination T3 is used as the bearer for
MGW B selected by the MSC Server, while the bearer termination T4 is used as the
bearer for the previous MGW.
GMSCS MSCS
T4 T3 T2 T1
CTX2 CTX1 RNC/BSC

MGW A MGW B
Fig. Bearer Setup Process-12 MT Network Model
According to the intra-office bearer setup mode, there are two types of call time
sequence. One is the forward bearer setup, and the other is the backward bearer setup.
19
1.2.2.1 MT Forward Bearer Setup Signaling Process
The figures below show the MT time sequence in the forward bearer setup mode.
GMSCS MGW A MSCS MGW B RNC/BSC UE
Initial Address
HLR Interrogation
Step1
Initial Address
Paging + Security
SETUP
Step2
CALL CONFIRMED
Context ($) ADD.request($)

Prepare Bearer +
Context (C1) ADD.reply Change Through- Connection Step3
( T2)
Bearer Information
Context ($) ADD.request($)

Step4
Context (C2) ADD.reply (
T3 Establish Bearer +
) Change Through - Connection
Bearer
Establishment
Prepare Bearer + Step5
Context (C2) ADD. reply Change Through - Connection
( T4)
Bearer Information
UP Init
UP Init Ack
Context (C2) NOTIFY.request(T4)
Bearer Established
Context (C2) NOTIFY.reply(T4)
UP Init
Continuity Step6
UP Init Ack
Context (C1) NOTIFY.request (T2)
Context (C1) NOTIFY.reply(T2) Bearer Established

Continuity
Step7
Fig. Bearer Setup Process-13 MT Call Setup Time Sequence in the Forward Bearer Setup Mode
20
GMSCS MGW A MSCS MGW B RNC /BSC UE
UMTS:

Prepare Bearer +
Context (C1) ADD.reply ( T1)
Change Through- Connection
RAB ASSIGNMENT REQ Step8
Bearer
Establish.
and Iu UP
Initializa.
GSM:

Reserve Circuit +
ASSIGNMENT REQUEST
ASSIGNMENT COMPL
ALERTING
Address Complete
Address Complete Context (C1) MOD.request ( T2)
Send Tone (start providing a Step10
Context (C1) MOD.reply (T2) ringing tone for a speech call)
CONNECT
Context (C1) MOD.request ( T1) Change Through- Connection + Activate

Inter - Working Function (when
Context (C1) MOD.reply (T1) applicable) + Activate Voice Processing
Context (C1) MOD.request ( T2) Step11
Stop Tone (stop prov iding a ringing tone
Context (C1) MOD.reply (T2) for speech call) + Activate Interworking
Function (when applicable) + Activate
Answer Voice Processing Function (when
applicable)
Context (C2) MOD.request ( T3) Activate Voice Processing Function
13 (when applicable)
Context (C2) MOD.reply ( T3)
Context (C2) MOD.request ( T4) Activate Voice Processing Function Step12

(when applicable)
Context (C2) MOD.reply (T4)
Answer
Fig. Bearer Setup Process-14 MT Call Setup Time Sequence in the Forward Bearer Setup Mode (Continued)
21
Step 1: After receiving the IAM message of the previous node, the GMSC Server
requests the called route information from the HLR. The HLR requests the roaming
number from the VLR. After obtaining the roaming number of the callee, the HLR
returns the called route information to the GMSC Server. The GMSC Server can select
the MGW, or select it after receiving the Bearer Information message to forward the
IAM message to the MSC Server. The message indicates that the current bearer setup
mode is forward bearer setup.
Step 2: After receiving the IAM message, the MSCS Server/VLR sends the paging
message to the callee. If there is a radio channel between the network and the callee,
the callee directly sends back the paging response message. If no radio channel exists,
the UE sends the channel request message to the RNS, and sends back the paging
response message after the RNS assigns the channel. The MSC Server/VLR
authenticates the UE. If the encryption is required, the MSC Server/VLR requests the
RNS to encrypt the air channel for the user. The RNS sends encryption command to the
mobile phone. After activating the encryption mode, the mobile phone sends the
encryption completion message to the RNS. The RNS sends the response message to
the MSC Server/VLR. The MSC Server/VLR sends the SETUP message to the UE.
The UE returns the CALL CONFIRMED message, which indicates that the UE is
ready.
Step 3: After receiving the CALL CONFIRMED message from the UE, the MSC
Server/VLR starts to set up the incoming bearer termination, selects MGW B, and
sends the ADD command to MGW B. In this way, the forward bearer is established.
This procedure includes the Prepare Bearer procedure. The Change Through-
Connection procedure indicates that the external continuity of the created bearer
termination is bidirectional. After setting up the incoming bearer termination T2 for the
MSC Server, the MGW B returns the success response to the MSC Server.
Step 4: The MSC Server sends the Bearer Information containing the bearer address of
T2, binding reference and bearer attributes to the GMSC Server. If the GMSC Server
has not selected an MGW before, it can select an MGW here. The GMSC Server sends
the ADD command message to MGW A. This message involves the Establish Bearer
procedure and bearer attributes of the peer terminal in the Bearer Information. The
Change Through-Connection procedure indicates that the external continuity of the
created bearer termination is bidirectional. The bearer termination T3 on MGW A
requests the bearer termination T2 on MGW B to set up the bearer connection.
22
Step 5: The GMSC Server starts the incoming bearer setup procedure. Because of the
forward bearer setup mode, the GMSC Server sends the ADD command to MGW A,
and the Prepare Bearer procedure is implemented. The Change Through-Connection
procedure indicates that the external continuity of the created bearer termination is
bidirectional. After setting up the incoming bearer termination T4 for the GMSC
Server, the MGW A returns the success response message to the GMSC Server. The
message contains the bearer address of T4, binding reference and optional bearer
attributes. The GMSC Server notifies the previous node of the bearer attributes of T4
through the Bearer Information message.
Step 6: The previous node of the GMSC Server applies for an outgoing termination.
This termination automatically requests the bearer termination T4 on MGW A to set up
the bearer connection, and transfers the user plane initialization information to T4. In
this case, the T4 associated user plane returns the user plane initialization success
response. MGW A considers that the bearer connection is established successfully, and
sends a notification message to the GMSC Server. At the same time, MGW A transmits
the user plane initialization information to T2 on MGW B. The T2 associated user
plane returns the user plane initialization success response to MGW B which considers
that the bearer connection is established successfully and sends a notification message
to the MSC Server.
Step 7: After receiving the incoming bearer connection setup success indication, the
GMSC Server receives the Continuity message sent from the previous node, and
forwards the Continuity message to the MSC Server. In this case, the MSC Server
considers that the network bearer connection has been established successfully. For 3G
user access, go to Step 8. For 2G user access, go to Step 9.
Step 8: The MSCS Server starts the access bearer connection setup procedure. The
MSCS Server sends the ADD command to the MGW B, and the Prepare Bearer
procedure is implemented. The Change Through-Connection procedure indicates that
the external continuity of the created bearer termination is bidirectional. After the
completion of the access bearer termination setup, MGW B sends the success response
to the MSC Server. The MSC Server starts the RAB assignment procedure. The RNC
confirms that the bearer connection has been established. After the completion of the
user plane initialization procedure, the RAB assignment success response is sent to the
MSC Server. Go to Step 10.
Step 9: The MSCS Server starts the access bearer connection setup procedure. The
23
MSCS Server sends the ADD command to MGW B, and the Reserve Circuit procedure
is implemented. The Change Through-Connection procedure indicates that the external
continuity of the created bearer termination is unidirectional. After setting up the access
bearer termination, MGW B sends the success response to the MSC Server. The MSCS
Server starts the access channel setup procedure. The RNC returns the access channel
setup success response. Go to Step 10.
Step 10: The UE plays the ringing tone for the user, and sends the Alerting message to
the MSC Server. The MSCS Server forwards the ACM message to the GMSC Server,
and starts playing the ringback tone for the caller. That is, the MSC Server sends the
Modify command to the MGW B, and the Send Tone procedure is implemented. The
MSC Server notifies T2 to play the ringback tone.
Step 11: After the callee picks up the phone, the UE sends the Connect message to the
MSC Server, sends the Modify command to MGW B, and requires the change of the
access termination attributes. For example, the Change Through-Connection procedure
requires the external continuity attribute of the access termination to be changed to
bidirectional. The optional Activate Interworking Function procedure requires the
access termination to activate the interworking function and the optional Active Voice
Processing Function. The UE sends another Modify command to MGW B to modify
the attributes of the incoming termination. For example, the Stop Tone procedure stops
playing a ringing tone for the caller, activates the interworking function (optional) and
activates the voice processing function (optional). After completing the above
termination modifying procedure, the MSC Server forwards the Answer message to the
GMSC Server.
Step 12: The GMSC Server receives the Answer message. If it is required to activate
the voice processing function, that is, to modify two terminations in the managed
context, two Modify messages are used respectively. Otherwise, the Answer message is
directly forwarded to the previous node.
1.2.2.2 MT Backward Bearer Setup Signaling Process
The figures below show the MT time sequence in the backward bearer setup mode.
24
Initial Address + Bearer Information
HLR Interrogation
Step1
Context ($) ADD.request ($)
Establish Bearer +
UP Init
UP Init Ack
Step2
Context (C2) NOTIFY.request( T4)
Bearer Established
Context (C2) NOTIFY.reply (T4)
Context
ADD.request ($)
(C2)
Prepare Bearer + Step3
Initial Address
Step4
Paging + Security
SETUP
Step5
CALL
CONFIRMED
Context ($) ADD.request ($)
Establish Bearer +
Context (C1) ADD.reply (T2) Change Through - Connection Step6
UP Init
UP Init Ack
Context (C1) NOTIFY.request( T2) Step7
Bearer Established
Context (C1) NOTIFY.reply (T2)
Fig. Bearer Setup Process-15 MT Call Setup Time Sequence in the Backward Bearer Setup Mode
25
UMTS:

Prepare Bearer +
RAB ASSIGNMENT REQ Step8
Bearer
Establish.
and Iu UP
Initializa.
GSM:

Reserve Circuit +
Step9
ASSIGNMENT REQUEST
ASSIGNMENT COMPL
ALERTING
Address Complete
Address Complete
Context (C1) MOD.request ( T2) Step10
Send Tone (start providing a
Context (C1) MOD.reply (T2) ringing tone for a speech call)
CONNECT
Context (C1) MO D.request ( T1)
Change Through- Connection + Activate
Context (C1) MOD.reply (T1) Interworking Function (when applicable)
+ Activate Voice Processing Function
Context (C1) MOD.request ( T2) (when applicable) Step11
Stop Tone (stop providing a ringing
Context (C1) MOD.reply (T2) tone for speech call) + Activate
Interworking Function (when
Answer applicable) + Activate Voice
Processing Function (when applicable)
(when applicable)

Step12
(when applicable)
Answer
Fig. Bearer Setup Process-16 MT Call Setup Time Sequence in the Backward Bearer Setup Mode (Continued)
26
Step 1: After receiving the IAM message of the previous node, the GMSC Server
requests the called route information from the HLR. The HLR requests the roaming
number from the VLR. After obtaining the roaming number of the callee, the HLR
returns the called route information to the GMSC Server. The GMSC Server can select
the MGW to apply for the incoming bearer termination. Because of the backward
bearer setup mode, the ADD command involves the Establish Bearer procedure and
contains the bearer address, binding reference and bearer attributes provided by the
previous node contained in the IAM message. The Change Through-Connection
procedure requires the external continuity attribute of the created bearer termination of
MGW A to be bidirectional. After setting up the incoming bearer termination T4,
MGW A returns the success response to the GMSC Server.
Step 2: T4 on MGW A requests the bearer termination of the previous MGW to set up
the bearer. When the user plane initialization procedure is completed, namely after the
bearer connection is set up, MGW A sends a notification message to the GMSC Server.
Step 3: After successful setup of GMSC Server incoming bearer, the GMSC Server
starts to set up the outgoing bearer termination. Because of the backward bearer setup
mode, the ADD command involves the Prepare Bearer procedure. The Change
Through-Connection procedure requires the external continuity attribute of the created
bearer termination of MGW A to be bidirectional. After setting up the outgoing bearer
termination T3, MGW A returns the success response message to the GMSC Server.
The message contains the bearer address, binding reference and optional bearer
attributes of the created bearer termination.
Step 4: After the GMSC Server applies for the outgoing bearer termination T3, the new
IAM message is combined, which contains the bearer address of the outgoing bearer
termination of the GMSC Server, binding reference and bearer attributes. The message
is sent to the MSC Server/VLR, which indicates that the bearer setup mode of the
current call is backward bearer setup.
Step 5: The MSCS Server/VLR receives the IAM message, and sends the paging
message to the callee. If the radio channel exists between the network and the callee,
the callee directly sends back the paging response message. If the radio channel does
not exist, the UE sends the channel request message to the RNS. After the RNS assigns
the channel, it sends back the paging response message. The MSC Server/VLR
authenticates the UE. If the encryption is required, the MSC Server/VLR requires the
RNS encrypt the air channel for the user. The RNS sends an encryption command to
27
the MS. After activating the encryption mode, the MS sends the encryption completion
message to the RNS. The RNS sends the response message to the MSC Server/VLR.
The MSC Server/VLR sends the SETUP message to the UE. The UE sends back the
CALL CONFIRMED message, which indicates that the UE is ready.
Step 6: After receiving the CALL CONFIRMED message from the UE, the MSCS
Server/VLR starts to set up the incoming bearer link, selects the MGW B, and sends
the ADD command to MGW B. Because of the backward bearer setup mode, the
Establish Bearer procedure is implemented and the command contains the bearer
address of the outgoing bearer termination of the GMSC Server, binding reference and
bearer attributes. The Change Through-Connection procedure indicates that the
external continuity of the created bearer termination is bidirectional. After setting up
the incoming bearer termination T2, MGW B returns the success response to the MSC
Server.
Step 7: T2 on MGW B requests the bearer termination T3 on MGW A to set up the

bearer. When the user plane initialization procedure is completed, namely after the
bearer connection is set up, MGW B sends a notification message to the MSC Server.
For 3G user access, go to Step 8. For 2G user access, go to Step 9.
Step 8: After successful setup of the incoming bearer, the MSC Server starts to set up
the access bearer connection. The MSC Server sends the ADD command to MGW B.
The Prepare Bearer procedure is implemented. The Change Through-Connection
bidirectional. After setting up the access bearer termination, MGW B sends the success
response message to the MSC Server. The MSC Server starts the RAB assignment
procedure. The RNC confirms that the bearer connection is established. After the
completion of the user plane initialization procedure, the RNC sends the RAB
assignment completion response to the MSC Server. Go to Step 10.
Step 9: After setting up the incoming bearer connection, the MSCS Server starts to set
up the access bearer connection. The MSCS Server sends the ADD command to MGW
B. The Reserve Circuit procedure is implemented. The Change Through-Connection
unidirectional. After setting up the access bearer termination, MGW B sends the
success response to the MSC Server. The MSCS Server starts the access channel setup
procedure. The RNC returns the access channel setup success response. Go to Step 10.
Step 10: The UE plays the ringing tone for the user, and sends the Alerting message to
28
the MSC Server. The MSCS Server forwards the ACM message to the GMSC Server,
and starts to play the ringback tone for the caller. That is, the MSC Server sends the
Modify command to MGW B and notifies T2 to play the ringback tone. The Send Tone
procedure is implemented.
Step 11: After the callee picks up the phone, the UE sends the Connect message to the
MSC Server. The MSC Server sends the Modify command to MGW B to modify the
attributes of the access termination. For example, the Change Through-Connection
procedure requires the external continuity attribute of the access termination to be
modified to bidirectional. The optional Activate Interworking Function procedure
requires the access termination to activate the interworking function and the optional
Active Voice Processing Function. The UE sends another Modify command to MGW B
to modify the attributes of the incoming termination. For example, the Stop Tone
procedure requires the MSCS to send another Modify command to MGW B to modify
the attributes of the incoming termination, or the Stop Tone procedure stops playing a
ringing tone for the caller, activates the interworking function (optional) and activates
the voice processing function (optional). After completing the above termination
modifying procedure, the MSC Server forwards the Answer message to the GMSC
Server.
Step 12: The GMSC Server receives the Answer message. If it is required to activate
the voice processing function, that is, to modify two terminations in the managed
context, two Modify messages are used respectively. Otherwise, the Answer message is
directly forwarded to the previous node.
1.2.3 Call Release Signaling Process
To efficiently use the radio frequency resources, the mobile communication system
adopts the First Party Release mode. When a user hangs up, the call release process is
started. There is no difference between the caller on-hook process and the callee on-
hook process. The following describes the MS on-hook and the network side on-hook
processes respectively.
1.2.3.1 MS On-hook
Fig. Bearer Setup Process-17 shows the MS on-hook process.
29
UE RNC/BSC MSCS MGW
DISCONNECT
Release
REL
Step1
RLC
UMTS:
IU RELEASE CMD
Bearer Release
IU RELEASE COMPLETE
Context (C1 ) SUB.request (T1)
Release Termination
Context(C1) SUB.reply (T1)
GSM:
CLEAR COMMAND
CLEAR COMPLETE
Step2-3
Context (C1) SUB.request (T1)
Release Termination
Release Complete
Context (C1) MOD.request (T2)

Release Bearer +
Context (C1) MOD.reply (T2) Change Through - Connection

Release Termination
Context (C1) SUB.reply (T2)
Bearer Release
Fig. Bearer Setup Process-17 MS On-hook Process
1: When the MS is being hooked on, a DISCONNECT message is sent to the MSCS.
Then the MSCS sends a RELEASE message to the MS. The MS returns the release
completion message to the MSCS.
2: If the user is accessed through the RNC, the network bearer and Iu connection are
released.
3: If the user is accessed through the BSC, the network bearer and the A interface
30
connection are released.
1.2.3.2 Network Side On-hook
Fig. Bearer Setup Process-18 shows the network side on-hook process.
UE RNC/BSC MSCS MGW
Release
DISCONNECT
Context (C1) MOD.request (T2)

Release Bearer +
Context (C1) MOD.reply (T2) Change Through - Connection

Step1
Release Termination
Context (C1) SUB.reply (T2)
Release Complete
REL
Bearer Release
RLC
UMTS:
IU RELEASE CMD
Bearer Release
Step2
IU RELEASE COMPLETE
Context (C1 ) SUB.request (T1)
SUB.reply (T1) Release Termination

Context(C1)
GSM:
CLEAR COMMAND
CLEAR COMPLETE Step3
Context (C 1) SUB.request (T1)
Release Termination
Fig. Bearer Setup Process-18 Network Side On-hook Process
1: After MS is being hooked on, a Release message is sent to the MSCS. After
receiving this message, the MSCS sends a DISCONNECT message to the UE to
31
release the network bearer and termination through the ReleaseBear and
ReleaseTermination procedures. After receiving the message, the UE sends the release
message to the MSCS. After releasing the resource successfully, the MSCS sends the
release completion message.
2: If the user is accessed through the RNC, after the release completion message is
received, the radio bearer and Iu connection are released.
3: If the user is accessed through the BSC, after the release completion message is
received, the terrestrial circuit and A interface connection of the user are released.
32
2 SMS
 Key points
· SMS process.
2.1 SMS Function

The SMS is divided into point-to-point SMS and broadcast SMS. The MSC only
involves the point-to-point SMS.
The point-to-point SMS provides services for messages with limited length through the
service center (SC) between the MS of the UMTS PLMN and short message entity
(SME). The SC can store and forward message, and is an SMS processing entity
integrating the storage, interaction and trunk functions. The function of the UMTS
PLMN is to support the short message transmission between the SC and the MS.
The point-to-point SMS defines two services, SM MO and SM MT. The SM MOs are
short messages sent by the MS to the SC. These messages may be sent to other MSs or
fixed network users. The SM MTs are short message forwarded by the SC to the MS.
These messages may be from the MS (SM MO), voice channel, telegraph or fax.
The point-to-point SMS process involves:
1. SM MO process.
2. SM MT process.
3. Transmission of alert messages.
2.2 SMS Process
2.2.1 SM MO Process
The figure below shows the SM MO process.
33
SC SMS_IWMSC HLR MSCS/VLR MS
CM_SER_REQ
STEP 1
CM_SER_REQ_ACK
CP DATA(RP DATA)
FORWARD_SHORT_MESSAGE
MESSAGE_TRANSFER STEP2
DELIVERY_REPORT
DELIVERY_REPORT
CP DATA(RP ACK)
STEP3
Fig. SMS Process-19 SMS Process Initiated by the MS
Step 1: (CM_SER_REQ MSMSCS/VLR)
To send a short message, the MS first sets up the MM connection, and sends the
CM_SER_REQ message to the MSCS/VLR. The MSCS/VLR returns the
CM_SER_RSP message or the CM_SER_RJT message to the MS. If the service
response message is sent, the MSCS authenticates the MS.
Step2: (CPDATA(RPDATA) MSMSCS/VLR)
The MS sends the CPDATA message to the MSCS/VLR. After receiving this message,
the MSCS/VLR checks whether the messages is restricted or prohibited by the
supplementary services. If the processing of the short message is not prohibited, the
MSCS/VLR transmits the message to the IWMSC. The IWMSC is responsible for the
interface processing with the SC.
3: (DELIVERY_REPORT IWMSCMSCS/VLR)
After receiving the short message sent by the mobile user, the SC returns the
processing result to the MS. After receiving the Delivery Report message, the
MSCS/VLR sends an acknowledgement message to the MS.
2.2.2 SM MT Process
Fig. SMS Process-20 shows the SM MT process.
34
SC IW/GMSC HLR MSC/VLR MS

MESSAGE_TRANSFER
SEND_ROUTING_INFO
FOR_SHORT_MSG
FORWARD_SHORT_MESSAGE
STEP1
PAGE
PAGE_RSP
STEP2
CPDATA(RPDATA)
CPDATA(RPACK)
STEP3
DELIVERY REPORT
DELIVERY REPORT
DELIVERY REPORT
STEP4
Fig. SMS Process-20 SM MT Process
1: (Forward_sIU_RELOCrt_message IW/GMSCMSCS/VLR )
If the received SM is for a mobile user, the SC sends it to the subordinate ingress
GMSCS. The ingress GMSCS sends a route request message to the HLR. The HLR
finds the route of the MSCS/VLR, and then sends the route information to the GMSCS.
The GMSCS finds the MSCS/VLR to which the MS belongs according to the route
information, and transmits the SM to the MSCS/VLR.
Step2: (PAGE MSCS/VLRMS)
After receiving the Forward_sIU_RELOCrt_message, if the VLR has no MS related

data, the MSCS/VLR directly returns the transmission failure message to the GMSCS.
If the VLR has the MS related data, the MSCS/VLR sends the PAGE message to the
MS. After the MS returns the PAGE-RSP message, the MSCS/VLR authenticates the
MS and verifies that the user is a legal user.
Step3: (CPDATA(RPDATA) MSCS/VLRMS)
After the user is proved to be a legal user, the MSCS/VLR sends an SM to the MS.
After receiving the SM, the MS returns the processing result to the MSCS/VLR: It
returns an acknowledgement message if the processing succeeds or returns the failure
cause if the processing fails. If the MS has no sufficient space to store the SM, the
failure cause may indicate that the SC storage capacity is insufficient.
35
4: (Delivery Report MSCS/VLRGMSCS)
After receiving the acknowledgement message from the MS, the MSCS/VLR converts
the message into the MAP signaling and sends it to the MSCS. The GMSCS forwards
the signaling to the SC.
2.2.3 Alert Message Process
In the HLR, there are two SM flag bits: MNRF (It also exists in the VLR) and MCEF
(The memory of the MS is full). If these two flag bits are set to 1, no SM is sent to the
MS any more. Therefore, if the MS is reachable or has free memory, the MSCS/VLR
sends an alert message to the HLR to initiate subsequent operations.
1. The MNRFs in the HLR and VLR are set to 1, but the MCEF in the HLR is not
set to 1.
When the MNRF in the HLR is set to 1 but the MCEF is not set to 1, if the MS
is reachable, the MSCS/VLR sends a notification message to the HLR. The HLR
considers that the system allows the SC to send an SM to the MS, and sends an
alert message to the SC. Fig. SMS Process-21 shows the service process.
SC SMS_IWMSC HLR MSCS/

MS
VLR
Ready For SM
Alert Service Center
Fig. SMS Process-21 Alert Message Process (1)
1) When the MSCS/VLR finds that the MS responds to a call or the PAGE
message of other services (namely, the user is reachable), the MSCS/VLR sends
the Ready For SM notification message to the HLR.
2) After receiving the notification message, the HLR modifies the MNRF, and
checks the MCEF. If the MCEF is not set to 1, it indicates that the MS has
available free memory. Then the HLR sends an alert message to the SC to alert
36
that it can send an SM to the MS.
2. The MCEF in the HLR is set to 1, but the MNRF is not set to 1.
The MCEF only exists in the HLR. When the MS has free memory, it sends a
notification message to the MSCS/VLR. The MSCS/VLR sends a notification
message to the HLR. Fig. SMS Process-22 shows the service process.
SC SMS_IVVMSC HLR MSCS/

MS
VLR
Ready For SM Req
Ready For SM
Alert Service Center CPDATA（RPACK）
Fig. SMS Process-22 Alert Message Process (2)
Process Description:
1) When the MS has free memory, it sends a notification message to the

MSCS/VLR.
2) After receiving the notification message, the MSCS/VLR sends a notification

message to the HLR, and sends a response message to the MS.
3) The HLR modifies the MCEF and checks the MNRF. If the MNRF is not set to
1, the HLR sends an alert message to the SC.
3. Both the MCEF and the MNRF are set to 1.
If both the MNRF and the MCEF in the HLR are set to 1, and the notification message
sent from the MSCS/VLR is received, only the related flag bit is modified. The alert
message is sent to the SC only when both the flag bits are set to 0.
37
3 Other Services
 Key points
· Supplementary service functions.
· Data service functions.
· Intelligent service functions.
3.1 Supplementary Services
3.1.1 Supplementary Service Functions
Based on basic services, supplementary services allow users to change the

incoming/outgoing call processing of the network according their own needs, or
provide some information for users to intelligently use some regular service through
the network.
The CS related supplementary services of the UMTS involve nine types and 21
services, as shown in Table Supplementary Services-1.
Table Supplementary Services-1 UMTS Supplementary Services
No. Type Category Abbreviation

1 Calling Line Identification Presentation CLIP
2 Number Calling Line Identification Restriction CLIR
3 identification Connected Line Identification Presentation COLP
4 Connected Line Identification Restriction COLR
5 Call Forwarding Unconditional CFU
6 Call Forwarding Busy CFB
7 Call forwarding Call Forwarding on No Reply CFNRy
Call Forwarding on Mobile Subscriber Not
8 CFNRc
Reachable
9 Call waiting CW
Call completion
10 Call hold HOLD
11 Multiparty service Multiparty Service MPTY
12 Closed User Group Closed User Group CUG
39
No. Type Category Abbreviation
13 Alert of Call Charging (Information) AOCI
Charging alert
14 Alert of Call Charging (CDR) AOCC
15 Barring of All Outgoing Calls BAOC
16 Barring of Outgoing International Calls BOIC
Barring of Outgoing International Calls
17 except those directed to the Home PLMN BOIC-Exhc
Call barring
Country
18 Barring of All Incoming Calls BAIC
Barring of Incoming Calls when Roaming
19 BIC-Roam
Outside the Home PLMN Country
Explicit Call
20 Explicit Call Transfer ECT
Transfer
21 Call Deflection Call Deflection CD
In the MSCS, the supplementary services involve two function blocks. One includes
basic operations such as provision and registration of supplementary services. The
other includes the supplementary and modification functions for basic services, such as
call related supplementary services, call independent supplementary services and
password management functions.
3.1.2 Supplementary Service Operations
The basic operation procedure of supplementary services involves the provision,

withdrawal, register, erasing, activation, deactivation, Interrogating and invoking, as
well as the password management process.
1. Provision: Mobile users subscribe supplementary services from service

providers (carriers). The users can implement service registration only after
provision.
2. Withdrawal: The user applies for unregister or the carrier unregisters a

supplementary service. After the unregister, the carrier does not provide the
supplementary service for the user any more.
The provision and withdrawal are completed through the handling console. All
supplementary services can be used only after they are provisioned.
3. Register: The user registers the data related to the supplementary service in the
MSCS/VLR and HLR.
The register operation is applicable to call forwarding service. It involves the
40
following cases:
1) CFU: The register request includes the supplementary service code (It indicates
the CFU) and the forwarding number.
2) CFB and CFNRc: The operation is the same as the CFU operation. The
difference is that the supplementary service code is CFB.
3) CFNA: The register request contains the supplementary service code and the
forwarding number, as well as the time of the no-answer timer.
The register operation is completed through the handling console or initiated by

the MS. Fig. Supplementary Services-23 shows the service process initiated by
the MS.
MSCS/VLR HLR
MAP_REGISTER_SS_ ind Step A
MAP_REGISTER_SS_ rsp Step B
Fig. Supplementary Services-23 Register Operation Process
Step A: The MS initiates the register operation of supplementary services to the

MSCS/VLR. The MSCS/VLR sends the register operation request
MAP_REGISRER_SS_ind to the HLR.
Step B: The HLR registers successfully, and sends the response

MAP_REGISRER_SS_rsp to the MSCS/VLR.
4. Erase: Erasing the supplementary service related data registered by the user in
the MSCS/VLR and HLR.
The erase operation is applicable to the call forwarding service. This operation
can be performed through the handling console or by the MS. Fig.
Supplementary Services-24 shows the service process initiated by the MS.
41
UE MSCS/VLR HLR
SS_Facility
Erase SS
MAP_Erase_SS
Step A
MAP_Erase_SS_Ack
Step B
SS_Facility_Ack
Fig. Supplementary Services-24 Erase Operation Process
Step A: The UE initiates a supplementary service erasing operation to the

MSCS/VLR. The MSCS/VLR sends an erasing request to the HLR.
Step B: After HLR erases the service successfully, it sends a response message
to the MSCS/VLR. The MSCS/VLR sends a response message to the UE.
5. Activation: It is an operation related to supplementary services, which is used to

activate the supplementary service between the MSCS/VLR and the HLR. This
operation can be performed through the service handling console or by the MS.
The activation operation is applicable to call forwarding, call waiting and call
barring services. In activating the call barring function, the user needs to provide
the password. For other two types of supplementary services, the password is
not required.
Fig. Supplementary Services-25 shows the activation operation process initiated

by the MS.
MSCS/VLR HLR
MAP_ACTIVATE_SS_ind
Step A
MAP_GET_PASSWORD_req
Step B
MAP_GET_PASSWORD _cnf
Step C
MAP_ACTIVATE_SS_rsp
Step D
Fig. Supplementary Services-25 Activation Operation Process
42
Step A: The user initiates the supplementary service activation request to the
MSCS. The MSCS sends the MAP_ACTIVATE_SS_ind to the VLR. The VLR
sends the MAP_ACTIVATE_SS_ind to the HLR.
Step B: In activating the call barring supplementary service, the HLR sends a
request for obtaining user password to the VLR.
Step C: The HLR receives the user password obtaining response from the VLR.
Step D: The HLR returns the MAP_ACTIVATE_SS_rsp to the VLR.
6. Deactivation: It is an operation related to supplementary services, which is used

to deactivate the supplementary service between the MSCS/VLR and the HLR.
This operation can be performed through the handling console or by the MS.
The deactivation operation is applicable to call forwarding, call waiting and call
barring services. In deactivating the call barring function, the user needs to
provide the password. For other two types of supplementary services, the
password is not required. The operation process is the same as that of activating
the supplementary service.
7. Interrogate: Interrogating the data related to the supplementary service. This

operation is applicable to CFU service and incoming call barring service. The
interrogating of other supplementary services is processed in the VLR. The user
can interrogate data through the handling console or the MS. The MSCS/VLR
needs to participate in the interrogating procedure initiated by the MS. Fig.
Supplementary Services-26 shows the service process.
MSCS/VLR HLR
MAP_INTERROGATE_SS_ind
Step A
MAP_INTERROGATE_SS_rsp
Step B
Fig. Supplementary Services-26 Interrogating Operation Process
43
Step A: The user initiates a request for interrogating supplementary service

status to the MSCS/VLR. The MSCS/VLR sends the MAP_INTERROGATE
_SS_ind request to the HLR.
Step B: The HLR returns the response to the VLR.
8. Invoke: It is an operation related to supplementary services, which is used to

invoke the supplementary service after the MSCS/VLR checks whether the
mobile user has subscribed the supplementary service.
9. Register password
This operation is applicable to call barring supplementary services only. The

mobile user can perform this operation to register or modify the password for
call barring supplementary services. Only the authorized user can perform this
operation.
This operation can be performed through the handling console or by the MS.
The MSCS/VLR needs to participate in the register password operation initiated
by the MS. Fig. Supplementary Services-27 shows the service process.
MSCS/VLR HLR
MAP_REGISTER_PASSWORD
Step A
Step B
Step C
Step D
Step E
Step F
Step G
MAP_REGISTER_PASSWORD_rsp
Step H
Fig. Supplementary Services-27 Password Register Process
Step A: The user initiates the register password request to the MSCS/VLR. The
44
MSCS/VLR sends the MAP_REGISTER_PASSWORD message to the HLR.
Step B: The HLR sends the request for obtaining user password (which has been
registered by the user) to the MSCS/VLR.
Step C: The HLR receives the user password obtaining response from the
MSCS/VLR.
Step D: The HLR sends the request for obtaining user password (new password
of the user) to the MSCS/VLR.
Step E: The HLR receives the user password obtaining response from the
MSCS/VLR.
Step F: The HLR sends the request for obtaining user password (new password
of the user) to the MSCS/VLR.
Step G: The HLR receives the user password obtaining response from the
MSCS/VLR.
Step H: The HLR returns the response message MAP_REGISTER_

PASSWORD_rsp to the VLR.
10. Get password: It is an operation related to supplementary services. It is

applicable to call barring supplementary services only. The service process is
similar to that of registering password.
3.2 Data Services

Most of current mobile communication systems focus on providing voice services. In
the informationization era, the demand for data services is increasingly urgent. There is
no doubt that mobile communication technologies can be used to provide data services,
to expand the application range and to better satisfy the requirements for data services.
The ZXWN MSCS of ZTE can provide data services.
Mobile data services are implemented by adding the IWU to the MGW. The MSCS
controls and invokes data services according to the services subscribed or initiated by
the user. The MSCS can offer all data services including G3/G4 fax, intelligent
telegraph, videotext and computer data, and provide circuit data bearer services
required in the UMTS protocol, as well as the interworking function for various
networks such as PSTN, ISDN, CSPDN, PSPDN, DDN and the Internet.
In the PLMN, the circuit data services are classified into the following eight types (see
45
3GPP TS22.002): 3.1 kHz audio, V.110, X.31 Flag Stuffing, V.120, Bit Transparent
Mode, PIAFS, Frame Tunnelling Mode and multimedia call. Different data services
need different bearer capabilities, while the bearer capabilities are determined by the
bearer capability information element (BCIE) in the Set-up message. According to the
requirements of 3GPP for circuit data services, the following three bearer capabilities
are required: 3.1 kHz audio ex PLMN, RDI and UDI. Table 5.2-1 shows the bearer
capability necessary for circuit data services.
Table Data Services-1 UMTS Circuit Data Services
Service Name Attribute Bearer Capability FNUR

Asynchronous/tran
28.8 kbit/s
sparent mode
3.1 kHz audio
Synchronous/
3.1 kHz audio 28.8 kbit/s
transparent mode
Synchronous/ non-
9.6/14.4/19.2/28.8 kbit/s
transparent mode
56 kbit/s
V.110 Transparent UDI/RDI
56 kbit/s
X.31 Flag Synchronous/ non-
UDI/RDI 9.6/14.4/19.2/28.8/38.4/48/56 kbit/s
Stuffing transparent
V.120 Non-transparent UDI/RDI 9.6/14.4/19.2/28.8/38.4/56 kbit/s
Bit UDI 64 kbit/s
Synchronous/
Transparent
transparent RDI 56 kbit/s
Mode
Asynchronous/
PIAFS UDI/RDI 32/64 kbit/s
non-transparent
Frame
Asynchronous/ 9.6/14.4/19.2/28.8/38.4/43.2/57.6
Tunnelling UDI/RDI
non-transparent kbit/s
Mode
3.1 kHz audio 28.8/33.6 kbit/s
Multimedia Synchronous/
RDI 56 kbit/s
call transparent
UDI 32/64 kbit/s
3.3 Intelligent Services

The intelligent network (IN) is intended to serve all communication networks, that is, it
not only serves PSTN, PSPDN and N-ISDN, but also serves B-ISDN and the mobile
communication network. It is not in the paratactic relationship with the original
communication network, but serves telecommunication networks and enhances their
46
functions.
Fig. Intelligent Services-28 shows the IN application fields.
End-User
End-User
Service INTERNET Mobile
Provider PSPDN Network
SMS SCP DB
CCS7 NETWORK
SSP IP
N-ISDN
PSTN
B-ISDN
End-User
End-User End-User
Fig. Intelligent Services-28 IN Application Fields
The IN is the “Nerve center” of the telecommunication network. The IN concept model
(INCM) is a framework for designing and describing the intelligent system. This model
describes the IN system and functions from different planes and objects, including the
service plane, general function plane, distributed function plane and physical plane, as
shown in Table 5.3-1.
Table Intelligent Services-2 IN System and Functions
Plane Name Object Processing Object

Service user
1 Service plane (SP) SF/service
Network carrier
2 General function plane (GFP) Service designer SIB/GFL
Distributed function plane
3 Software developer FEA/FE
(DFP)
4 Physical plane (PHP) Equipment manufacturer PE/INAP/CAP
Fig. Intelligent Services-29 shows the INCM structure.
47
Service 2
Service 1
SF SFn
SF2 1 Service plane
SF1
SP
POI
SIB1
BCP SIB3
POR General function plane
SIB2
GFP
SCF SSF SMF

IF
Distributed function plane
SDF SSF SRF
DFP
SCP IP
Physical plane
SDP SSP
PHP
Fig. Intelligent Services-29 INCM
The following describes the concepts of IN services and service features (SFs) from the
view of the SP (namely network user) and service provider (namely network carrier).
Services are provided by the telecommunication department or service providers to
satisfy the requirements of users for communication. The differences of services are
reflected on the basic service units (namely SF) that users can sense. One service can
consist of several SFs, and can select other SFs to enhance the service function. By
designing and combining multiple SFs, the network carrier can provide diversified new
services for network users and present accurate service definitions. In the design of
complicated new service, the SF and the service module constructed by SF are used as
infrastructure modules. In the consideration of modularization and reuse, the service is
fractionized into SFs. The modular design idea will be frequently mentioned below,
which is one of souls of the IN.
From the view of the service designer, the GFP reflects the general functions of the IN.
Based on the IN services provided for IN users, the GEP abstracts some function
modules simulating network functions from the angle of the whole network to support
and ensure the implementation of various SFs in the service plane. The abstracted
48
function modules are called service independent blocks (SIBs). The general function
plane processes SIBs and describes the objects such the general service logic (GSL)
which constructs the logical relation between SIBs of the service. The modular division
provides flexibility for the SIB to form SFs. The service designer can create featured
value-added services by combining the SIB chain according to the SF description and
the GSL.
The DFP processes the function entity (FE) and information flow (IF). For the software
developer, there are nine function entities, including call control access function
(CCAF), call control function (CCF), service switching function (SSF), special
resource function (SRF), service control function (SCF), service data function (SDF),
service management function (SMF), service management access function (SMAF),
and service creation environment function (SCEF). These FEs transfer IF, and work
together to complete the SIB function and GSL.
The PHP processes the physical entity (PE) which implements various FEs. This plane
is oriented to the equipment manufacturer. It integrates the logical FEs of the DFP into
the specific PE, and converts the IF between FEs to INAP (CAP in the mobile IN). In
developing these PEs, the following basic requirements shall be satisfied:
1. Each FE in the DFP shall be able to correspond to the related PE in the PHP.
2. In the same PE, there can be one or multiple FEs.
3. One FE cannot be distributed in two PEs.
4. Two same FEs can correspond to different PEs.
5. The PEs can be grouped into a PE system.
6. Each PE shall provide a standard interface.
7. On the basis of the FE conversion and standard interface, the manufacturers

shall be able to develop PEs.
8. The manufacturers can support mature technologies and new technologies, and
apply them to PEs.
The arrangement between PEs is implemented based on the INCM. According to ITU
recommendations, the SCF and SDF can be integrated in different PEs to form an SCP
and an SDP, or integrated in one PE to form an SDP. In addition, the SCF, SDF,
SSF/CCF and SRF can be integrated in one PE to form an SN. The SCEF is integrated
in one PE to form an SCE device. The SMF and SMAF are integrated in one PE to
49
form an SMS. The SSF/CCF and CCAF are integrated in one PE to form an SSP. In
constructing an IN within a large range, separate the SCF from the SSF physically and
use the SS7 network to connect them.
The CAMEL is the extension and development of the IN in the mobile field. With the
development of the GSM protocol from Phase1, Phase2 to Phase2+, a complete set of
standards has been established, which define the supplementary services including call
barring, call forwarding, number identification, number identification restriction, call
waiting, call hold, three-party service, closed user group, call diverting, call forwarding
busy and preferred route. The GSM in Phase2+ also faces the challenges such as
increasing demand for new services and establishment of enormous protocols and
standards. Based on the success experience of IN, the ETSI first puts forward the first
phase protocol (CAMEL Phase1) of the Mobile IN in GSM Phase2+ Release96, and
then enters the second phase (CAMEL Phase2) in GSM Phase2+Release97. At present,
the 3GPP R99 standards expand the CAMEL, and the mobile IN steps into the third
phase (CAMEL Phase3). The R5 protocol already establishes and accomplished the
standard of CAMEL Phase4. With the concept of modular structure of IN, the mobile
IN has an absolute advantage in service processing, service generation, service
management and charging, in comparison to the traditional GSM network.
The mobile intelligence is a network feature, which is different from the supplementary
services in the UMTS network. Compared with the traditional service processing, the
IN service processing mode is quite different. The processing of supplementary
services in traditional UMTS network is combined with the call processing. The
processing is completed under the control of the MSC, and the service process cannot
be changed. To provide new supplementary services, the network carrier shall upgrade
the software versions of all related nodes in the whole mobile network, even including
the software of the charging center. The poor stability, high risk and high cost of the
version upgrade directly affect the running of the network. In the IN, the service
processing is separated from the call processing. With the modular division of network
functions, each switching node only completes the basic call processing. The service
logic control is implemented by the SCP. The generation of new services is
implemented by the SCE. The SMP is responsible for managing services and
submitting new services. The IN adopts the modular design idea to construct services.
According to the attributes of new services, the network carrier uses the SIB to design
service logic and construct SIB chain to obtain new services. In this way, the network
carrier can easily generate competitive CAMEL_OSS value-added services different
50
from UMTS standard services. Even if the mobile user roams outside the HPLMN, the
OSS still can gain service support. It is cost effective for offering new services. The
services can be offered in the whole network, and the operation risk is greatly reduced.
According to the related description of CAMEL function structure in the UMTS

protocol, the mobile IN consists of HLR, gsmSCF, GMSCS (with the gsmSSF
function), MSCS/VLR(with the gsmSSF function) and gsmSRF (independent
intelligent IP peripheral or combined with the MSCS/VLR). In CAMEL Phase3, the
gateway mobile location center (GMLC) will be introduced. To implement mobile IN
services, the VPLMN, IPLMN, HPLMN and CAMEL service control (SCF) shall be
able to exchange information. In the HPLMN and the VPLMN, it is required to add
extra labels to the records of mobile users who register CAMEL service.
Fig. Intelligent Services-30 shows the basic structure of the network.
Home Network HLR MAP gsmSCF
MAP CAP
CAP MAP
gsmSSF VLR gsmSSF

Incoming GMSC MSC
Roaming leg MS
line Server Server
MAP
MO call - Outgoing
Forwarded leg leg
(or Forwarding
Interrogating CAP leg)
Network Visited Network
Home/Interrogating/Visited
gsmSRF Network
Server
Fig. Intelligent Services-30 CAMEL Function Structure
HLR: It stores the user related CAMEL subscription information including the O-CSI,
D-CSI, T-CSI, VT-CSI, SMS-CSI, TIF-CSI, U-CSI and SS-CSI. The UG-CSI acts on
the CAMEL subscription information about all users. Where, the O/D/VT-CSI, SMS-
CSI and SS-CSI are transmitted to the VLR in the case of user location update or data
change. The O/D/T-CSI is sent to the GMSC in the route response message. The
CAMEL subscription information such as TIF-CSI, U-CSI and UG-CSI are only stored
51
in the HLR.
VLR: It stores the CAMEL subscription information such as O-CSI, D-CSI, VT-CSI,
SMS-CSI and SS-CSI of the mobile users roaming in the local VLR area.
GMSC Server: It provides CCF in the IN and the means to set up and control bearer
services for network users.
gsmSCF: It is the GSM service control function. It provides service logic for
implementing logic control for the call request CAMEL OSS services, and handles
service related behaviors.
gsmSSF: It is the GSM service switching function. It provides the means to identify the
call request CAMEL OSS service processing, and interacts with the call processing and
call service logic.
gsmSRF Server: It is the GSM specialised resource function. Through the resource
control such as DTMF receiver, voice identification function, procedure conversion,
notification and voice processing, it implements the interaction between all end users
with the network.
As the emerging service network in the mobile communication industry, the mobile IN
system can not only solve the problems appeared in the current telecommunication
industry such as defaulting and malicious overdraft, reduce operation risks of
telecommunication carriers and ensure normal profit by providing mobile prepaid
services, but also provide diversified value-added services flexibly, economically and
efficiently, and provide prompt, high quality and human-centered services for users
through the integration with the business system, customer service center and bank
system. Now, the mobile IN system is one of the new service growth portions for
telecommunication carriers.
Presently, the ZXWN MSCS/SSP (V3.0) system complies with CAMEL mobile
intelligent Phase 3 specifications. It provides these functions:
1. Mobile Pre-Paid Service (MPPS)
This service is a typical prepaid service. When the user registers the MPPS, the
network carrier allocates a unique account corresponding to the user number. All
call costs of the MPPS user are deducted from the account. Once the balance of
the account is insufficient or the account expires, the network refuses to provide
communication services for the user, till the user recharges the account. This
52
service allows the carrier to set the maximum daily or monthly call cost limit for
users. This can protect the economic interest of users.
Through the real-time control mechanism and rapid charging function of the
Mobile IN, the MPPS can efficiently prevent the interest of network carriers
from being hurt by defaulting and malicious overdraft, reduce the operation risks
of telecommunication carriers, ensure normal operation profit, and create
considerable call cost accumulation profit for carriers. By adopting reasonable
charging policy, the network carriers can gain more users, improve the network
utilization and gain more profit.
2. Mobile Virtual Private Network (MVPN)
This service provides the network service similar to the PBX function on the
mobile network for users. This service can be used to set up a cross-region and
even multinational virtual private network. The call costs of all users in the
MVPN are deducted from the same group account. The MVPN adopts an
independent numbering plan. The intra-network users can call each other by
dialing short numbers. This service allows the MVPN administrator to manage
the call authorities of intra-network users, control call costs, and provide CDRs
and statistics data periodically.
Through the flexible routing mechanism, call control mechanism and diversified
charging functions, the MVPN service provides powerful communication
management functions for group users. By managing the call authorities of
group members (for example, intra-network call only, outgoing call barring and
outgoing call restriction) and controlling call costs (for example, controlling the
upper limit of monthly call costs), the group can enhance the internal
management and control the communication expense. Through the periodical
call records and statistics data, the management personnel can know the working
status of employees. This reduces the enterprise switch investment, device
upgrade and maintenance costs, and operation costs. Network carriers can adopt
different charging rates for intra-network calls and off-network calls to gain
group users, improve the network utilization and gain more operation profit
through the high traffic of group users. With the successful development of the
MVPN service, network carriers can create more value .
3. Familiar Numbers Service (FNS)
53
This service sets up a familiar number table for users. When an FNS user dials
the familiar number in the table or a relative whose number is listed in the table
calls the user, the network provides call rate preference. The user can modify
and maintain the familiar number table by accessing the service management
center through the telephone and the Internet.
The advantage of the FNS is that the user can enjoy the preferred rate to reduce
call cost. This stimulates the frequency of using services. For network carriers,
they can provision the FNS to attract network users, improve the network
utilization and gain more profit.
4. Mobile Advertising (MAD)
This service provides the advertising access number for advertisement

applicants, and sets up the advertising customer accounts. All mobile or fixed
users dialing the advertisement access number can call other users freely after
listening to the advertisement of the applicant. The rated call costs are deducted
from the account of the advertising customer. To ensure the effectiveness of the
advertisement, a simple test is conducted after the advertisement for the user
who dials the number. The user can make free calls only after completing the
test. The test results are collected by the network.
The MAD service introduces the advertisement into the mobile communication
field and provides new advertisement media. The MAD service can be used to
carry out the activities such as online social survey and questionnaire. It can
motivate the enthusiasm of survey objects and enhance the effect. Advertising
customers can use the MAD service to promote the reputation of their products.
Common user can enjoy free calls within the rated time or fee. Network carriers
can fully use the network resources and gain considerable advertising fees.
5. Specialized Charging Service (SCS)
This service is a typical service using “Diversified IN charging functions”. It

allows the user to select specific charging service package. The user can enjoy
the contracted preference policy including preferred rate based on call time
period, preferred rate based on call duration and preferred rate based on
originating call area. The SCS user can subscribe desired packages and enjoy the
preference.
The carrier can provision the SCS and provide diversified preference services
54
for users to gain more network users, more communication market shares and
more profit.
6. Multiple Subscriber Profile (MSP)
This service allows a mobile user to possess multiple lines with only one USIM
card. Each line corresponds to one MSISDN. Different lines have different
subscription options. Mobile users can use MSs with different identities (such as
individual, commercial) at different charging rates. In originating a call, the user
can select any line to provide the service. In terminating a call, the line is
determined by the called MSISDN.
Another MSP service solution provides intelligent role selection through the
incoming call screening function of the mobile IN. This solution provides single
user numbers. This saves number resources, but restricts the selection range of
other supplementary services for users.
The MSP service brings great advantages of online life to mobile users. The role
selection allows the user to fully enjoy diversified network services. In this way,
the carrier can gain more network users and more communication market shares.
7. Mobile Bank Service (MBKS)
This service provides an e-commerce interface between the mobile IN and the
bank. This service allows the MS to implement account management including
password, account inquiry and transfer service. Compared with the exiting
telephone banking, the IN services have these advantages:
· Centralized SCP deployment, single interface with the bank, and easy to control
and manage.
· The signaling mode is used to set up the data channel between the originating
office and the private network of the bank. In this way, less circuit resources are
required.
· With the MBKS, the banking systems can provide a unified bank access number
and bank interface within a province or the country. This improves the security
of the network and standardize the banking services.
8. Business Assistant Service
This service provides comprehensive commercial tools and information

services. Combining the USSD and SMS technologies, it provides important
55
schedule record, alert function, incoming call recording function, conference

bulletin function, etiquette delivery function and public information query
function.
In addition, it involves mobile intelligent value-added services such as mobile

freephone service, outgoing call screening service, call-back service, and instant
inquiry service. With the ZXWN intelligent IN system, the network carrier can
develop and generate various services, enhance network functions, and promote
the service level.
56
Appendix A Terms
Name Full Spelling

AAA Authentication Authorization Accounting
AAL2 ATM Adaptation Layer type 2
AAL5 ATM Adaptation Layer type 5
AH Authentication Header
ATM Asynchronous Transfer Mode
DHCP Dynamic Host Configuration Protocol
DiffServ Differentiated Service
GRE Generic Routing Encapsulation
HLR Home Location Register
ICMP Internet Control Message Protocol
IETF Internet Engineering Task Force
IKE Internet Key Exchange
IMSI International Mobile Station Identity
IntServ Integrated Service
IPCP IP Control Protocol
IPsec IP Security
IPv6 IP Version 6
ISAKMP Internet Security Association and Key Management Protocol
IWF Inter Work Function
L2TP Layer2 Tunnel Protocol
LAES Lawfully Authorized Electronic Surveillance
LAN Local Area Network
LCP Link Control Protocol
MGW Media Gateway
MIP Mobile IP
MS Mobile Station
MSC Mobile Switching Center
NCP Network Control Protocol
PAP Password Authentication Protocol
PPP Point to Point Protocol
QoS Quality of Service
RADIUS Remote Authentication Dial in User Service
RSVP Resource Reservation Protocol
SDH Synchronous Digital Hierarchy
57
Name Full Spelling
STM Synchronous Transfer Mode
TCP Transfer Control Protocol
TOS Type of Service
UDP User Datagram Protocol
UDR User Data Record
VLR Visit Location Register
VPN Virtual Private Network
WAN Wide Area Network
58
Appendix B Abbreviations
Abbreviations Full Spelling

A3 Authentication algorithm A3
A5/X Encryption algorithm A5/0-7
A8 Ciphering key generating algorithm A8
ACK ACKnowledgement
ACM Accumulated Call Meter
ACM Address Complete Message
AE Application Entity
APB ATM Process Board
AoC Advice of Charge

AoCC Advice of Charge Charging supplementary service
AoCI Advice of Charge Information supplementary service
ASE Application Service Element
ASIG Analog Signalling
ASN.1 Abstract Syntax Notation One
AuC Authentication Centre
B-interface
BAIC Barring of All Incoming Calls supplementary service
BAOC Barring of All Outgoing Calls supplementary service
BCCH Broadcast Control Channel
BCTL Back Control
BCSN Backplane of Circuit Switch Network
BDT Back Digital Trunk
BCTC Backplane of ConTrol Center
BFBI Back Fiber Bus Interface
BHCA Busy hour Calling Attempt
Barring of Incoming Calls when Roaming outside
BIC-Roam
the home PLMN country supplementary service
BNET Back Network
BO all Barring of Outgoing call supplementary services
BOIC Barring of Outgoing International Calls supplementary service
Barring of Outgoing International Calls except those directed to the
BOIC-exHC
home PLMN Country supplementary service
BPSN Backplane of Packet Switch Network
BS Basic Service (group)
59
BS Bearer Service
BSG Basic Service Group
BSNM Back S Network
BTS Base Transceiver Station
BUSN Backplane of Universal Switch Network
C-interface
CAI Charge Advice Information
CB Cell Broadcast
CBC Cell Broadcast Centre
CBCH Cell Broadcast Channel
CBK Clear Back signal
CC Country Code
Call Control
CCF Conditional Call Forwarding
CCITT The International Telegraph and Telephone Consultative Committee
Cct Circuit
CF all Call Forwarding services
CFB Call Forwarding on mobile subscriber Busy supplementary service
Call Forwarding on mobile subscriber Not Reachable supplementary
CFNRc
service
CFNRy Call Forwarding on No Reply supplementary service
CFU Call Forwarding Unconditional supplementary service
CGC Cirduit Group Congestion signal
CI Cell Identity
CUG Index
CLKG CLOCKGenerator
CLKI CLOCK Interface
CLI Calling Line Identity
CLIP Calling Line Identification Presentation supplementary service
CLIR Calling Line Identification Restriction supplementary service
CM Connection Management
CMD CoMmanD
CMP Control Main Processor
COLI COnnected Line Identity
COLP COnnected Line identification Presentation supplementary service
COLR COnnected Line identification Restriction supplementary service
DTB Digital Trunk Board
GGLP GGSN Line Processor
COLP COnnected Line identification Presentation supplementary service
GGMP GGSN Main Processor
60
GGUP GGSN GTP-U Processor
GLI GE Line Interface
GERAN GSM Enhanced Radio Access Network
IMAB IMA Board
IPB IP Process Board
IPI IP bearer Interface
IWFB IWF Board
MNIC Multi-service Network Interface Card
MONB MONIOTR BOARD
MPB Main Process Board
MRB Media Resource Board
OMP Operation Main Processor
PLI POS Line Interface
PSN Packet Switch Network
PWRD POWER Distributor
RMP Router Main Processor
RPB Router Protocol process Board
SDHB SDH Board
SDTB Sonet Digital Trunk Board
SDU Selection and Distrubution Unit
SGBP SGSN Gb Processor
SGLP SGSN General Line Processor
SGMP SGSN Main Processor
SGSP SGSN Processor
SGUP SGSN GTP-U Processor
SIUP SGSN Iu Processor
SMP Signal Main Processor
SPB Sigaling Process Board
TFI TDM Fibre Interface
TSNB TDM Switch Network Board
UIM Universal Interface Module
VTC Voice Transcoder Card
61

TN - SP021 - E1 - 0 Call Flow and Supplementary Service Flow in CS Domain-65

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

TN - SP021 - E1 - 0 Call Flow and Supplementary Service Flow in CS Domain-65

Caricato da

Copyright:

Formati disponibili

TN_SP021_E1_0 Call Flow and

Supplementary Service Flow in CS domain

· ZXWN MGW (V3.0) Media Gateway Technical Manual

1 Mobile Call Process......................................................................................................................................1

1.1 Basic Call Process................................................................................................................................1

1.1.1 UE Originated Call...................................................................................................................1

1.1.2 UE Terminated Call..................................................................................................................5

1.1.3 Call Release Process...............................................................................................................11

1.2 Bearer Setup Process.........................................................................................................................13

1.2.1 MO Bearer Setup Network Model.........................................................................................13

1.2.2 MT Bearer Setup Network Model..........................................................................................19

1.2.3 Call Release Signaling Process..............................................................................................29

2.1 SMS Function....................................................................................................................................33

2.2 SMS Process......................................................................................................................................33

2.2.3 Alert Message Process............................................................................................................36

3.1 Supplementary Services....................................................................................................................39

3.1.1 Supplementary Service Functions..........................................................................................39

3.1.2 Supplementary Service Operations........................................................................................40

3.2 Data Services.....................................................................................................................................45

3.3 Intelligent Services............................................................................................................................47

· Bearer setup process of mobile originated call and terminated call

1.1 Basic Call Process

1.1.1 UE Originated Call

1.1.1.1 Network Structure for UE Originated Call

Fig. Basic Call Process-1 Network Structure of Basic UE Originated Call

1.1.1.2 Basic Singling Process

Fig. Basic Call Process-2 UE Originated Signaling Process

Management service request message to the MM sub-layer and requests the MM

2. The RNS transparently transmits this message to the VMSC.

· Authentication procedure: If the VLRA determines that the call of the UE is

5. If the UE receives the CM Service Accept message or the security procedure is

message to the network.

1.1.2 UE Terminated Call

1.1.2.1 Network Structure for UE Terminated Call

Fig. Basic Call Process-3 Network Structure for UE Terminated Call

The basic called procedure is as follows:

8. The VMSC pages the UE through the air interface.

1.1.2.2 Basic Signaling Process

33. The GMSCB relays this message to the originating switch.

35. After receiving the Connect message, the VMSCB will:

· Send the UEBConnect ack message;

· Send the call completion response message to the VLRB.

1.1.3 Call Release Process

1.1.3.1 Network Originated Call Release Process

Fig. Basic Call Process-5 Network Originated Call Release Process

1.1.3.2 UE Originated Call Release Process

Fig. Basic Call Process-6 UE Originated Call Release Process

1.2 Bearer Setup Process

1.2.1 MO Bearer Setup Network Model

Fig. Bearer Setup Process-7 MO Network Model

1.2.1.1 MO Forward Bearer Signaling Setup Process

UE RNC/BSC MSCS MGW

CALL PROCEEDING Step1

Context ($) ADD.request ($) Step2

Context (C1) ADD.request ($)

Context (C1) ADD.request (T1)

UE RNC/BSC MSCS MGW

Context (C1 ) MOD.request (T1) Change Through-Connection +

1.2.1.2 MO Backward Bearer Setup Signaling Process

Context (C$) ADD.request ($)

Bearer Establishment and Iu UP

RAB ASSIGNMENT COMPL

Context (C$) ADD.request (T1)