message transparently to the MSC via the BTS and BSC, using the previously

established logical connection.

 BASIC call setup information includes:
 Speech or DATA bearer capability
 Called & Calling Party Numbers
14. Call Setup establishment [MS --> BTS]
 After TMSI allocation the MS will initiate call establishment by
sending the "RIL3-CC Setup" message to the network/ MSC.
 SDCCH/I/CC Setup [Called & Calling Party Numbers, requested service, bearer capability]
 After TMSI allocation the MS will initiate call establishment by sending the
"RIL3-CC Setup" message to the network. The MS sends a setup message
transparently to the MSC via the BTS and BSC, using the previously established logical
connection.
15. Send Info for Outgoing Call (SIOC). [MSC --> VLR]
 Outgoing call subscription check: checks the subscription authority.
 Upon receiving SETUP request message, MSC sends to VLR a "MAP/B Send
Call Setup Information" message, which contains the information of what is
desired.
• The MSC sends the SIFOC message to the VLR, implements the call
restriction, subscription service and CUG check, and requests
outgoing calls

16. Call Complete (CC) -response of SIOC. [VLR --> MSC]

 If the originating MS is authorized for the desired services (such as, type of call
and destination), the VLR responds to MSC with a "MAP/B Call Complete"
message listing the MS capabilities, subscribed services, and parameters
needed by the network to properly allocate a channel for the call.
 Contains results of BAOC or any flavor of barring
17. Call Proceeding-SRI (MSISDN-B) an IAM message (ISUP) [MSC --> GMSC]
 Upon receiving "Complete Call" message from VLR, MSC analyzes the dialed
digits using GT analysis defined in GT analyses table and routes it to GMSC
with an IAM message (ISUP), in order to set up the connection and also
confirms MS with CALL_PROC that the IAM was sent, and that the MSC is
processing the call set up.
 Since MSISDN-B is a mobile subscriber and MSC
has no direct connection with HLR, it will send
Routing Information to GMSC with an IAM message
(ISUP) [ ISUP IAM (MSISDN-B)]
 An IAM is sent to the gateway MSC, in case of
ISDN (or other PLMN). The gateway MSC, in turn,
forwards the IAM to the ISDN exchange.

 The call proceeding indication [from MSC to MS], which is a response from the
GMSC on receiving IAM from MSC, is passed back to the MS transparently.
 The MSC confirms MS with CALL_PROC that the IAM was sent, and that the
MSC is processing the call set up.
 Call Setup [MSISDN-B]

CM service accepted

ISUP IAM (MSISDN-B) [MSC --> GMSC]

ISUP IAM (MSRN-B) [GMSC --> MSC]

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.
MOC-TCH Assignment Procedure
Establishment of traffic channel phase
 After "RIL3-CC Call Proceeding", if OACSU (Off Air Call Set Up) is not
active, MSC starts the TCH allocation by sends an Assignment Request
message to BSC,
17.1. TCH Assignment Request-[MSC --> BSC]
• TCH Assignment Request [Chn. Type, Priority, CIC，DL DTX， Queuing Flag]
17.2. Physical Context Request [ on SDCCH] [BSC --> BTS]

17.3. Physical Context Confirm [TA.MS/BS_TxPwr] [BTS --> BSC]

17.4. Channel Activation TCH [TA, MS/BS_TxPwr] [BSC --> BTS]

17.5. Channel Activation Ack. [BTS --> BSC]

17.6. Assignment Command [ on SDCCH] [BSC --> BTS --> MS]

 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]
17.7. SABM (FACCH) [MS --> BTS]
 On TCH if need signaling, then use Stealing Flag transfer TCH into
FACCH
17.8. UA [BTS --> MS]-Establish Indication [BTS --> BSC]

17.9. Assignment Complete/Allocation complete [MS --> BTS --> BSC--> MSC

17.10. RF Channel Release (SD) [BSC --> BTS]

17.11. RF Channel Release Ack [BTS --> BSC]

At this time the calling party gets the ring tone.

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.
IAM
Establish TCH first, then connect another part. Alerting transfer on TCH

When the traffic channel assignment process is complete (indicated by the Allocation complete message from BSSA
to VMSCA), VMSCA constructs an ISUP IAM using the B subscriber address, and sends it to the destination
exchange.
MSC also assigns the TCH through an "RIL3-CC Assignment Command." After receiving the "RIL3-CC
Assignment Complete" message from MS, MSC sends a "TUP/ISUP Initial Address Mobile" message
(IAM) to the PSTNIISDN switching center.

SRI (MSISDN-B)

 Upon receiving "Complete Call" message from VLR, MSC analyzes the dialled
digits using GT analysis defined in GT analyses with NP=1 and routes it to
GMSC
 The SETUP message, which is transparently sent from the MS to the MSC,
contains the directory number of the called party. After the MSC received this
information, it sends (in case of ISDN) an IAM message (ISUP), in order to set
up the connection.
 The MSC confirms with CALL_PROC that the IAM was sent, and that the
MSC is processing the call set up.

 Upon receiving "Complete Call" message from VLR, 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 SETUP message provides the network with the number which the MS has
dialed. An IAM is sent to the gateway MSC, in case of ISDN (or other PLMN).
The gateway MSC, in turn, forwards the IAM to the ISDN exchange

An IAM is sent to the gateway MSC, in case of ISDN (or other PLMN). The gateway MSC, in turn,
forwards the IAM to the ISDN exchange
  After Call Confirmed- DTAP message sent by the
called MS to the MSC to confirm the attempted
incoming call setup.

MS an "RIL3-CC Call Proceeding" message to MS.

MSC also assigns the TCH through an "RIL3-CC Assignment Command."

After receiving the "RIL3-CC Assignment Complete" message from MS,

MSC sends a "TUP/ISUP Initial Address Mobile" message (IAM) to the GMSC.

When the called party receives this message [IAM], it rings to alert the subscriber and returns a
"TUP/ISUP Address Complete" message to the GMSC, which in turn alerts the MSC by sending
"TUP/ISUP Address Complete" Message (ACM).
The MSC then sends an "RIL3-CC Alerting" message to the MS, informing that the called party has
been alerted.

18. SRI (MSISDN-B) an IAM message (ISUP) [GMSC --> HLR]

 When GMSC receives an ISUP IAM, The GWMSC has no means to find out where the
called MS is. It needs help from the HLR, which is constantly getting updated on MS
location as a result of the update location procedure
 The GMSC then identifies the subscriber's HLR based on the MSISDN, and
invokes the MAP operation SRI (MSISDN-B) as a parameter towards the HLR
to find out where the MS is presently located.
 GMSC request to the HLR to Provide MSRN(PRN)
of B-Party.
 SRI (MSISDN-B)
19. PRN -Provide Roaming Number REQ(IMSI) [HLR --> VLR]
 PRN(IMSI)
 The HLR knows in which VLR LA the MS is presently located and sends to
VLR a "MAP/D Provide MSRN" message to obtain the MSRN
 The HLR searches for a MSISDN entry in its record, retrieves the address of the current
serving MSC/VLR and the address of the IMSI. The HLR then initiates the provide
roaming number procedure toward VLR.
 HLR checks the VLR of the called no. and sends the
PRN signal.
Because of past location updates, the HLR already knows the VLR that currently
serves the subscriber. To obtain a mobile station roaming number (MSRN), the
HLR queries the VLR using the operation provideRoamingNumber with the IMSI
as a parameter.

The VLR assigns an MSRN from a pool of available numbers and sends the
MSRN back to the HLR in an acknowledgement.

PRN(IMSI)

HLR checks the VLR of the called no. and sends the
PRN signal.

 HLR to the serving VLR requesting a roaming number for the called subscriber.
 HLR 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 sends Provide Routing Number message (PRN) to MSC/VLR.
• HLR sends IMSI number of MS-B to VLR2 as data
• HSS translates the MSISDN to an IMSI

The HLR searches for a MSISDN entry in its record, retrieves the address of the current
serving MSC/VLR and the address of the IMSI.
 The HLR then initiates the provide roaming number procedure toward VLR
20. PRN_ACK- Provide Roaming Number ACK/response (MSRN) [VLR --> HLR]
 The VLR assigns a temporary number, i.e., MSRN for routing purposes and provides this
number to the requesting HLR
 The VLR provides in response a "MAP/D MSRN Acknowledgment" message.

Because the GMSC now knows the MSC in which the MS is currently located, it
generates an IAM with the MSRN as the called party number.
 When the MSC receives the IAM, it recognizes the MSRN and knows the IMSI
for which the MSRN was allocated. The MSRN is then returned to the pool for
use on a future call.
PRN(MSRN)

TMSI: By checking the LAC CI of the called party, exact cell in which the B-
Party no is latched has been found. So VLR can send a signal to the exact BTS
of B-Party. Signal is the TMSI of the called no
 MSC/VLR2 allocates a temporary roaming number (MSRN). The MSRN is then
passed to the HLR

21. SRI_ACK -Send Routing Information ACK (response) (MSRN) [HLR --> GMSC]
 On receiving the MSRN from the VLR in the provide roaming number response message,
the HLR forwards the MSRN to the GWMSC in a response message to the previously
received send routing info.
 The HLR then sends to the GMSC a "MAP/C Routing Information
Acknowledgment" message identifying to the GSM system where the MS is and
its MSRN

PRN(MSRN)

 MAP message sent from the HLR to the GMSC returning either the Roaming Number of
the requested subscriber, forwarding information or an Error
 HLR Passes MSRN to GMSC
 On receiving the MSRN from the VLR in the provide roaming number response
message, the HLR forwards the MSRN to the GWMSC in a response message to the
previously received send routing info.

22. IAM(MSRN)-Send Info I/C call [IAM(MSRN)] ISUP [GMSC --> MSC]
 Since the GMSC now knows the whereabouts of mobile and GWMSC has all the
necessary information to route the incoming call to the called MS. It sends an ISUP IAM
message to the serving MSC. The MSRN received from the VLR is passed as the called
party number parameter within the IAM message
 GMSC uses MSRN and refers to digit analysis and finds out the route to serving
MSC
 GMSC sends MSRN as the reference number for the call to establish and sends
ISUP message IAM to Serving MSC.

 Now the GWMSC has all the necessary information to route the incoming call to the
called MS. It sends an ISUP IAM message to the serving MSC
 The MSRN received from the VLR is passed as the called party number
parameter within the IAM message
This allows the Gateway-MSC to initiate routing of the call request towards the active MSC/VLR, by
means of the MSRN. For this purpose, an IAM message (ISUP) is used. After receiving the IAM, the MS
is searched in the whole Location Area, by means of PAGING messages

Since the GMSC now knows the whereabouts of mobile, it sends the IAM message to the proper MSC
where the mobile is presently located

When GMSC receives an ISUP IAM, it requests routing information from HLR using the MAP protocol.
HLR requests a roaming number from VLR, also using the MAP protocol, and
VLR returns a roaming number in the Provide Roaming Number Ack.
HLR returns the roaming number to GMSC in the Send Routing Info ack.

GMSC uses the roaming number to construct an ISUP IAM, which it sends to serving MSC.
When MSC receives the IAM, it requests information to handle the incoming call (SIFIC) from VLR, over an
internal interface of the MSC
If VLR determines that the incoming call is allowed, it requests MSC to page the MS.
VMSC pages the MS using radio interface signaling.
When the MS responds, MSC informs VLR in the Page ack message. MSC informs its VLR that MS has responded
VLRB instructs MSC to connect the call in the Complete call, and MSC establishes a traffic channel to the MS

Security Procedures - Authentication Ciphering, Equipment validation

Call Arrived
Call Complete
23. SIFIC/SIIC [MSC --> VLR]
 When the MSC receives an IAM from the GWMSC, The MSC sends to the VLR
a "MAP/B Send Information" message requesting the called MS's capabilities,
subscribed services, and parameters needed by the network to properly allocate
a channel for the call
 When the MSC receives the IAM, it recognizes the MSRN and knows the IMSI
for which the MSRN was allocated. The MSRN is then returned to the pool for
use on a future call.

 The MSC then queries the VLR, with a "MAP/B Send Information for
Incoming Call Setup" message requesting the called MS's capabilities,
subscribed services, and required parameters by the network to properly allocate
a channel for the call.

When MSC receives the IAM, it requests information to handle the incoming call (SIFIC) from VLR, over an
internal interface of the MSC

Because the GMSC now knows the MSC in which the MS is currently located, it generates an
IAM with the MSRN as the called party number.

When VMSCB receives an IAM from GMSCB it sends to VLRB a request for information to
handle the incoming call, using a Send Info for Incoming Call (SIFIC) message containing the
roaming number received in the IAM

If VLR recognizes the roaming number, and MS is allowed service, it sends a request to MSC to
page MS