MOC

Connect – DTAP message sent by MSC to the MS to indicate that the call has
been accepted

 The very moment the called party takes the call, the GMSC sends an ANM back to the
active MSC. Then the MS receives a CON message and the two parties are finally
connected (Note: Without CON_ACK)
 The GMSC sends an ISUP ANM message to the MSC when the called party answers.
The MSC sends a connect message to the MS transparently.
 When the users press the “Send” button, the MS transparently sends a CON
message to the MSC/VLR, that is conveyed to the peer as ANS message (ISUP).
Furthermore, the MSC/VLR sends the CON_ACK message to the MS, which
indicates start of the call and also initiates charging

MS chooses not to accept the call; he rejects the setup with an "RIL3-CC Release Complete" message to
the MSC.
On the other hand, if the called MS chooses to accept the call, it responds with an "RIL3-CC Call
Confirmed" message.
Conversation now starts between the calling and called MSs

including the calling party and the connection services required

On receiving the paging request, the MS requests the BSC to assign a control channel.

MSC/VLR2 receives the call. At this point, the MSRN is marked free and may be reassigned for other
calls.

The very moment the called party takes the call, the ISDN exchange sends an ANM back to the active MSC. Then
the MS receives a CON message and the two parties are finally connected (Note: Without CON_ACK)

The destination exchange sends an ISUP ANM message to the MSC when the called party answers. The MSC sends
a connect message to the MS transparently.

MTC

48. Conversation [MSC --> BSC --> BTS --> MS]

 After receiving a "RIL3-CC Call Confirmation" message from MS, the MSC
sends a " TUP/ISUP Address Complete" message to GMSC that in turn is sent
to Calling MSC
 At this time the calling party gets the ring tone.
49. Call Release [MSC --> BSC --> BTS --> MS]
 After receiving a "RIL3-CC Call Confirmation" message from MS, the MSC
sends a " TUP/ISUP Address Complete" message to GMSC that in turn is sent
to Calling MSC
 At this time the calling party gets the ring tone.

Call Proceeding

Progress

Conversation

ISUP ACM.
 At this stage MSC sends a TUP/ISUP Address Complete" message to GMSC
that in turn is sent to the ISDN switching center
 ACM
On receiving the ISUP ACM message from the destination exchange GMSC, indicating that a connection is being
set up to the called party, the MSC sends an alert message to the MS. This results in a call progress tone being fed
to the MS.

The called MSC sends an ISUP ANM message to the MSC when the called party answers.

The MSC sends a connect message to the MS transparently. On receiving a connect acknowledgment, the MSC
initiates charging the MS for the call.

At this time the calling party gets the ring tone. At the same time the MS is assigned a TCH by the
previously described channel assignment procedure

Now MS rings or buzzes to alert the subscriber of the incoming call and the MS sends an "RIL3-CC
Alerting" message to the MSC to inform that the subscriber has been alerted.

CALLPROCeeding
Is sent by the MSC in case of a Mobile Originating Call, inorder to inform the MS that the address information
which the MS has sent to the MSC in the SETUP message was received and processed. From the perspective
of the MSC, CALL_PROC can be regarded as a confirmation that the ISUP Initial Address Message (IAM) was
sent. The consequence for the MS is that the MSC does not need, or is not even able to process additional
address information.

ALERTing
The MSC sends this message in case of a Mobile Originating Call to the MS.
In case of a Mobile Terminating Call, the MS sends an ALERT to the MSC. ALERT corresponds to the Address
Complete Message (ACM) of ISUP and is responsible for the generation of a ring back tone at the receiving
end. ALERT is always sent to that side of the call, which initiated it. This is important for protocol analysis.
PROGRESS
If, for a Mobile Originating Call, interworking or transportof inband signaling should become necessary, then
the PROGRESS message is sent instead of ALERT. Examples are calls to automated information services or
voice-mail boxes. In this case, the PROGRESS message can be regarded as a substitute for ALERT.

On receiving the ISUP ACM message from the destination exchange GMSC, indicating that a connection is being
set up to the called party, the MSC sends an alert message to the MS. This results in a call progress tone being fed
to the MS.

When the call routing in the ISDN is complete (it rings), then the ISDN exchange sends an ACM back to the
gateway MSC, which forwards the ACM to the active MSC. The receipt of the ACM is indicated to the MS as
ALERT or PROGRESS message.

On receiving the ISUP ACM message from the destination exchange, indicating that connection is being set up to
the called party, the MSC sends an alert message to the MS. This results in a call progress tone being fed to the
MS

When the MSC/VLR receives the ANS message (ISUP) from the called side, then the call is through connected,
i.e., the called party CON message is transparently has accepted the call. The sent to CON the MS. The actual call
begins with receiving the message. CON_ACK message to the MSC/VLR The MS sends a in order to acknowledge
this message and start of charging

Conversation
SRI (MSISDN-B) an IAM message (ISUP)

which is transparently sent from the MS to the MSC/VLR, contains the directory number of the called
party.
After the MSC/VLR received this information, it sends (in case of ISDN) an IAM message (ISUP), in
order to set up the connection. The network confirms with CALL_PROC that the IAM was sent, and that
the MSC is processing the call set up

After receiving the TCH Assignment Response message, the MSC 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).

The MSC analyses the called party number, creates an ISUP IAM message, and sends it to the destination switch in
order to establish the connection
receives "Complete Call" message from VLR1.

MSC Checks the class of service from VLR database. MSC sends VLR the message "Send Info O/G
Call". VLR verifies its database and if MS is eligible for making O/G call, VLR1 reples MSC with the
message "Complete Call".

If MSA is not eligible for making O/G call announcement will be fed to MSA. It will be transmitted to
MSA by FACCH.

If MSC receives "Complete Call" message from VLR1. MSC analyzes the dialled digits using GT
analysis defined in GT analyses with NP=1 and routes it to GMSC
Since MSISDN-B is a mobile subscriber, MSC/VLR has to go for HLR Enquire for subscriber B. There
is no direct connection between MSC and HLR. MSC/VLR will send Routing Information to GMSC.
It refers to GT analysis with NP=1

The GMSC refers to GT analysis for NP=1, TON = NAT or INT, depends on MSISDN format received by
GMSC. GT analsis in GMSC refers to HLR..
GMSC requests routing information for the GSM subscriber from HLR.[Send_Routing_Info (MSISDN-
B)]

HLR2 uses MSISDN-B and finds out IMSI and the SS7 address of MSC/VLR which is serving MS-B at
that moment. SS7 address of the serving MSC/VLR was obtained by HLR during LU of MS-B. In this
case, MS-B is present in MSC/VLR2 area. HLR 2 sends Provide Routing Number message (PRN) to
MSC/VLR2. HLR 2 sends IMSI number of MS-B to VLR2 as data
MSC/VLR2 allocates a temporary roaming number (MSRN). The MSRN is then passed to the HLR

HLR 2 Passes MSRN to GMSC

GMSC uses MSRN and refers to digit analysis and finds out the route to MSC/VLR 2. GMSC 2 GMSC 2
sends MSRN as the reference number for the call to establish and sends ISUP messae IAM to
MSC/VLR2.

MSC/VLR2 receives the call. At this point, the MSRN is marked free and may be reassigned for other
calls.

IAM (MSISDN) SRI

SRI-Send Routing Information REQ(MSISDN)= IAM(MSISDN- B)
MAP message sent from the GMSC to the HLR requesting information on how to route a call
towards a mobile subscriber.
PRN -Provide Roaming Number REQ(IMSI)
HLR to the serving VLR requesting a roaming number for the called subscriber. It includes:
PRN_ACK- Provide Roaming Number ACK/response (MSRN)
SRI_ACK -Send Routing Information ACK (response) (MSRN)
MAP message sent from the HLR to the GMSC returning either the Roaming Number of the requested subscriber,
forwarding information or an Error

DTAP Setup.
SETUP (calling party nbr）
SIIC/CC
Call Confirmed- DTAP message sent by the called MS to the MSC to confirm the attempted incoming
call setup.
Alerting – DTAP message sent by MSC to the MS to indicate that called user alerting has begun

Connect – DTAP message sent by MSC to the MS to indicate that the call has been accepted

Connect Ack – DTAP message sent by the MS to the MSC to indicate that the call is being accepted.
Disconnect - DTAP message sent by the MS to the MSC indicating that the call needs to be torn down.

ACM

3. Call processing
18. Progress -The MSC then sends the MS an "RIL3-CC Call Proceeding" message to MS.
• The MSC sends a Call Processing to the MS, which indicates that the call
request is accepted.

Progress – DTAP message from the MSC to the MS indicating the progress of the call in the event of
interworking

Progress – DTAP message from the MSC to the MS indicating the progress of
the call in the event of interworking

Establish TCH first, then connect another part. Alerting transfer on TCH

The mobile is informed that the call setup is in progress. At this point the mobile phone displays a
message "Connecting….." on the screen to indicate that call setup is being attempted.

19. MSC sends an Assignment Request message to BSC, which contains the CIC allocated to A interface
• RIL3-CC Assignment Command
• TCH Assignment Request [Chn Type， Priority， CIC，DL DTX，
Queuing Flag]

20.Physical Context Request [ on SDCCH]

21.Physical Context Confirm [TA.MS/BS_TxPwr]
22.Channel Activation TCH [TA,MS/BS_TxPwr]
23.Channel Activation Ack.
24.Assignment Command [ on SDCCH]
 The BTS delivers received information further on towards the MS. Contents: channel description,
power levels, cell channel description, channel mode (Full / Half) and mobile allocation.
 Assignment Command [MA， TS， HSN， MAIO，MS_TxPwr]
25.SABM (FACCH)
 On TCH if need signaling, then use Stealing Flag transfer TCH into FACCH

UA-Establish Indication
Assignment Complete
Allocation complete
IAM

RF Channel Release (SD)

RF Channel Release Ack
Call Proceeding Call Proceeding

MSC constructs an ISUP IAM using the B subscriber address, and sends it to the destination exchange.
Assignment Request
Physical Context Request

The VMSC sends the SIFOC message to the VLR, and checks the subscription authority.
If the VLR recognizes the call, it returns the call completion indication.

After receiving the call completion indication, the MSCS sets up/ assigns the TCH 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.

Called Number Analysis Process

Roaming Number Analysis Process
After receiving an MSRN from the HLR, the MSC analyzes the MSRN, which is called the second-time
number analysis. The analysis on the MSRN aims to check whether the MSRN is allocated by the local
MSC.

If the MSRN is allocated by any other MSC, the local MSC performs route analysis based on the route
selection code and route selection source code obtained through analysis of the MSRN and finally obtains
the circuit identification code (CIC) of the outgoing circuit.

Upon receiving this message, The MSC exports a basic service type according to the bearer capability
parameters of the SETUP message, and determines whether the IWF resource is required.

The MSC sends the SIFOC message to the VLR, implements the call restriction, subscription service and
CUG check, and requests outgoing calls. The message contains the called number and basic service
information.

If the VLR judges that the MS can originate the call according to the subscription information about the
MS, the VLR sends the Complete Call message to the MSC. Otherwise, it sends the SIFOC negative
response to the MSC, and rejects the call setup.

The MSC 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.
After receiving the TCH Assignment Response message, the MSC 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).

When the user of an MS wishes to originate a call, the MS establishes communication with the network using radio
interface signaling, and sends a message containing the address of the called party. MSC requests information to
handle the outgoing call (SIFOC) from VLR, over an internal interface of the MSC/VLR.

If VLR determines that the outgoing call is allowed, it responds with a Complete Call. VMSCA:

MSC VLR B MAP

MSC HLR C MAP
HLR   VLR D MAP

TIP: HLR sends MSISDN in PRN to VLR to search MSRN. VLR receives MSIDN in ISD
message.

MSC sends IAM to GMSC.

IAM
Called MSISDN = B-Number. Calling MSISDN = A-Number
Send Routing Information (SRI) >> MSISDN >>
The GMSC starts to analyze the B-number

Provide Routing Number (PRN) >> IMSI >>