If a radio connection between the network and MSB is already established, VMSCB responds immediately

to the page request. If no radio connection exists, VMSCB sends a page request to BSSB, and BSSB
broadcasts the page on the paging channel.

If MSB detects the page, it sends a channel request to BSSB, which responds with an immediate
assignment command, to instruct MS to use the specified signaling channel.
MS then sends a page response on the signaling channel; BSS relays this to VMSCB.
VMSCB sends a Process access request message to VLRB to indicate that MSB has responded to paging.
If VLRB determines that MSB is allowed service, it sends a Process access request ack to
VMSCB

The Process access request ack message triggers a Start security procedures message towards BSSB; if
VMSCB has not received a Start security procedures message from VLRB, the Start security procedures
message indicates no ciphering.

VLR then sends a Complete call message to VMSCB.

VMSCB sends a Set-up message towards MSB. The Set-up message may include bearer capability information for
the call.
When MSB receives the Set-up message from BSSB, it responds with a Call confirmed message. The
Call Confirmed message includes bearer capability information if any of the negotiable parameters of the
bearer capability has to be changed.
When VMSCB receives the Call confirmed message via BSSB, it sends an Allocate channel message to
BSSB.
BSSB instructs MSB to tune to a traffic channel by sending an Assignment command.
When MSB has tuned to the specified traffic channel it responds with an Assignment complete, message,
which BSSB relays to VMSCB as an Allocation complete, and sends an Alerting message to indicate that
the called user is being alerted. VMSCB sends an ACM to GMSCB, which relays it to the originating
exchange.

VLRB may then initiate authentication,

MSC sends a Process access request message to VLR to indicate that MSB has
responded to paging.

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

24. CC [VLR --> MSC]
 Provided that the called MS is capable and authorized to receive the call, the
VLR sends back to the MSC a "MAP/B Complete Call" message, giving the
information needed to properly assign a channel for the call. The LA1 and the
mobile TMSI are parts of the "MAP/B Complete Call" message.

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

ISUP IAM (MSRN-B) [GMSC --> MSC]
ISUPIAM (MSRN)
ISUP IAM (called number)
ISUPACM (alert of the called user)
ISUPANM (off-hook of the called user)

Paging request

UDT/BSSM/Paging [IMSI, (TMSI), CIs] [MSC --> BSC]

I/CCH/ Paging Cmd [Paging-Group, TMSI/IMSI] [BSC --> BTS]
CCCH (PCH)/RR PAG_REQ [TMSI/IMSI] [BTS --> MS]

Paging (MS ID（TMSI+IMSI/IMSI） ，Cell ID（LAC/LAC+CI）

 When the MSC receives an IAM from the GWMSC, it queries the VLR to get the
location area identity (LAI) of where the MS is currently roaming and invokes the
paging procedure.
 Since The LA1 and the mobile TMSI are parts of the "MAP/B Complete Call"
message. The MSC uses this information to route a "BSSMAP Page" message to
all BSS cells in that LA
 BSSMAP PAGING message to the BSC
 The BSC sends a PAGING COMMAND message to each one of the BTSs supporting
the cells indicated in the PAGING message.
 The BTS formats a PAGING REQUEST message (type 1, 2 or 3) and sends this out at
the appropriate time on the PCH on the air interface
 MS detects TMSI, or IMSI on paging channel MS asks
channel request on RACH.
 The MS receives the PAGING REQUEST message which
contains either its IMSI or TMSI.
 The MS starts the immediate assignment procedure by sending the
CHANNEL REQUEST message on the RACH with a timing
advance of '0'.

.
  The BSS in turn sends "RIL3-RR Page Request" for the MS.
 BSS then pages the called MS over their paging channels with an "RIL3-RR
Paging Request" message on the PAGCH
 On receiving the paging request, the MS requests the BSC to assign a control channel,
the terminating MS proceeds through the same connection request procedure [
step 1-5],

 Upon receipt of a "paging request" message, if access to the network is

allowed, the addressed MS shall within 0.5 sec initiate the immediate
assignment procedure by requesting a channel through the Reverse Access
Channel.

 The establishment of the main signaling link is then initiated using an "SABM"
message with the information field containing the "Paging Response" message

7. BSC broadcast TMSI, of MS in paging channel (PCH).

MSC used LAI given by VLR to determine which BSC should page, included in
the message is the TMSI.

25. Paging request [MSC --> BSC --> BTS --> MS]
26. RR Channel Request [MS --> BTS]
 Upon receipt of a "paging request" message, if access to the network is
allowed, the addressed MS shall within 0.5 sec initiate the immediate
assignment procedure by requesting a channel through the Reverse Access
Channel.


 CCCH (RACH)/RR CHAN_REQ [reason, refer.]
o reason for the request
 response to a paging
o refer
 Rnd. Nbr. (Random Number)
27. Channel Required [BTS --> BSC]
 I/CCM/CHAN_RQD [CHAN_REQ, TA, FN] [Est Cause, Rnd Nbr, FN, TA]
 The BTS decodes the CHAN_REQ, calculates the distance MS ↔ BTS
Timing Advance (TA) and returns the complete information in a
CHAN_RQD to the BSC.
28. Channel activation- Ch Act [BSC --> BTS]
 BSC informs the BTS which channel type to activate and which channel
number to reserve.
 I/DCM/CHAN_ACT [Type, BS/MS-Power, DTX?] [TA BS/MS TxPwr
--> Max,Chann]
29. Channel activation ack [BTS --> BSC]
 I/DCM/CHAN_ACT_ACK [Frame Number]
 BTS confirms the acknowledgement.
30. Immediate Assignment Command [BSC --> BTS --> MS]
 BSC asks to BTS to assign the reserved channel to MS.
• I/CCM//IMM_ASS_CMD [refer, TA, channel, FN]
 BTS transmits the same message on AGCH- The BTS sends this
information over an AGCH to the MS
• CCCH (AGCH)/RR IMM_ASS_CMD [TA, channel, refer., FN]
 Immediate assignment command [allocates a SDCCH- Dedicated
Signaling Channel Assignment on AGCH]
 The MS finds “its” IMM_ASS_CMD by means of the request reference,
which the CHAN_REQ already contain

31. SABM (paging response (TMSI, LAI) on SDCCH) [MS --> BTS]
 The MS requests the BTS to establish a Layer 2 connection (LAPD), by
sending a SABM. It contains a PAG_RSP, which identifies the subscriber
(IMSI or TMSI) and specifies the requested service.
  Page Response (TMSI, LAI) on SDCCH

32. UA (paging response) [BTS --> MS]
 The BTS confirms establishment of the Layer 2 connection by repeating
the PAG_RSP message in a UA message (LAPD) and, at the same time,
passes this information to the BSC.
33. ESTABLISH INDICATION (paging response) [BTS --> BSC]
 The BTS confirms establishment of the Layer 2 connection by repeating
the PAG_RSP message in a UA message (LAPD) and, at the same time,
passes this information to the BSC.
34. SCCP connection request (paging response) [BSC --> MSC]
SCCP CONNECTION REQUEST + BSSMAP COMPLETE LAYER 3 INFORMATION
The BSC partly processes the PAG_RSP (the BSC needs the Mobile
Station Classmark) and adds the LAC and the CI. This entire information
is put as a CL3I (BSSM) in a (SCCP) and then sent to the MSC. At the
same time, the CR serves as a request for a SCCP connection
35. CC (SCCP Connection Confirm)-SCCP Conn Confirm [MSCS --> BSC]
CONNECTION CONFIRM (CC)

 The MSC confirms the logical connection by sending an SCCP connection confirmed
message.
 The MSC answers CR with a CC if it is able to provide the requested SCCP
connection. From this time on, a logical connection exists from the MS to
the MSC/VLR.
 The CR is answered with a CC, if the MSC is able to provide the
requested SCCP connection. A logical connection between MS and
MSC/VLR exists from this time on

 Finally, the MSC sends a connection confirm message back to the BSC. This
means that the circuit-switched connection is established on the A interphase.

 Connect Confirmed – SCCP message from the MSC to the BSC indicating that a
signaling connection can be made between the two entities. It contains the following
information:
• Destination Local Reference Number (same as the source local reference sent in
the CMSRQ msg) *
• Source Local Reference Number*

Paging Response - Similar to the CM SERVICE REQUEST message except

the enveloped DTAP message is PGRSP instead of CMSRQ.
 Paging Response (Mobile ID, Classmark2, Priority）
 Upon recognizing its TMSI in the paging message, the terminating MS proceeds
through the previously described process of channel request through the
Reverse Access Channel to gain assignment of a SDCCH and get connected to
the MSC.

 After the MS is connected to the MSC [ step 1-5], the MSC issues a "MAP/B
Process Access Request" message to the VLR.to perform identification,
authentication, ciphering, and TMSI reallocation procedure as discussed for
the originating MS

After the MS is connected to the MSC, the MSC issues a "MAP/B Process Access Request" message to
the VLR.
If the TMSI, sent by the MS, does not agree with that stored in the VLR, the VLR may request MS go
through the previously described identification procedure. The MS may also be required to go through the
authentication and ciphering processes, as previously described.

 Upon recognizing its TMSI in the paging message, the terminating MS proceeds
through the same connection request procedure [ step 1-4], identification,
authentication, ciphering, and TMSI reallocation procedure as discussed for
the originating MS
• After the MS is connected to the MSC [ step 1-4], the MSC issues a
"MAP/B Process Access Request" message to the VLR to proceeds
through identification, authentication, ciphering, and TMSI
reallocation procedure as discussed for the originating MS
  After the MS is connected to the MSC [ step 1-4], The MS sends a Paging
response message transparently to the MSC
• After the MS is connected to the MSC [ step 1-4], the MSC issues a
"MAP/B Process Access Request" message to the VLR to proceeds
through identification, authentication, ciphering, and TMSI
reallocation procedure as discussed for the originating MS

 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.
 On receiving the paging request, the MS requests the BSC to assign a control channel,
the terminating MS proceeds through the same connection request procedure [
step 1-5],
 After the MS is connected to the MSC [ step 1-5], The MS sends a Paging
response message transparently to the MSC
 After the MS is connected to the MSC [ step 1-5], The MS sends a Paging
response message transparently to the MSC

• After the MS is connected to the MSC [ step 1-4], the MSC issues a
"MAP/B Process Access Request" message to the VLR to proceeds
through identification, authentication, ciphering, and TMSI
reallocation procedure as discussed for the originating MS
• The MSC/VLR answers the PAG_RSP with an AUTH_REQ. This
message is conveyed to the BSC via the established SCCP connection

Process Request
Call Arrived
 Upon recognizing its TMSI in the paging message, the terminating MS proceeds
through the same connection request procedure [ step 1-4], identification,
authentication, ciphering, and TMSI reallocation procedure as discussed for
the originating MS

• After the MS is connected to the MSC, the MSC issues a "MAP/B

Process Access Request" message to the VLR to proceeds through
identification, authentication, ciphering, and TMSI reallocation
procedure as discussed for the originating MS

 After the MS is connected to the MSC, the MSC issues a "MAP/B Process
Access Request" message to the VLR to proceeds through identification,
authentication, ciphering, and TMSI reallocation procedure as discussed for
the originating MS
 The VLR answers the "MAP/B Process Access Request" message with the
following message
• At this stage, the network may initiate authentication and
subsequently starts the cipher mode. TMSI, if required, may
also be assigned. After TMSI allocation the MS will initiate call
establishment by sending the "RIL3-CC Setup" message to the
network/ MSC.
 If identification is required, the VLR first sends a "MAP/B
Provide IMSI" message to the MSC
 If the VLR determines that authentication is required, it t sends a
"MAP/B Authenticate" message to the MSC, which in turn sends
an "RIL3-MM Authentication Request" message, containing
RAND, to the MS over the air.
 Ciphering begins with the VLR sending the MSC a "MAP/B Set
Cipher Mode" message containing the value of Kc for use.
 After completing the ciphering process, the message is sent from
VLR to MSC for reallocation of the TMSI if desired ("Forward
new TMSI"). A "TMSI Reallocation Complete" message is sent
from MS to BSS after reallocating a new TMSI.
 VLR can thus allocate a TMSI to the MS via the TMSI Reallocation
Command message.
 After TMSI allocation, the MSC sends the MS a n "RIL3-CC Call
Setup" message giving the phone numbers of both the calling (MS-ISDN
number) and called (MS-ISDN number) parties and the type of service
requested MS.
 The MS performs a comparability check and responds to MSC
with an "RIL3-CC Call Confirmation" message that is forwarded
to MSC. At this stage MSC sends a TUP/ISUP Address Complete"
message to GMSC. At this time the calling party gets the ring tone.
 Identification Procedure- IMSI- Optional
 The Identification procedure is used to identify the MS when the VLR fails to recognize
the TMSI sent by MS due to any reason. The Identification procedure is initiated by
VLR-IMSI/TMSI/IMEI
 Mobile Identity [TMSI/IMSI]

Identity Request – DTAP message from the Network to the MS requesting its IMSI/TMSI/IMEI
• VLR first sends a "MAP/B Provide IMSI" message to the MSC
• MSC sends an "RIL3-MM Identity Request" message to the MS
• The MS responds by returning an "RIL3-MM Identity Response" message,
containing its IMSI, to the MSC.
• The MSC then sends the "MAP/B IMSI acknowledge" to the VLR

• The MSC/VLR sends the authentication request to the BSC, using the previously
established SCCP connection. The BSC passes this request to the MS transparently. The
authentication request message contains two important parameters: a

36. Authentication Request -Ki /SRES

 If the VLR determines that authentication is required, it sends a
"MAP/B Authenticate" message to the MSC, which in turn sends
an "RIL3-MM Authentication Request" message, containing
RAND, to the MS over the air.

 The authentication process may also be run either with TMSI or IMSI
received by the VLR

 If the VLR determines that authentication is required, it t sends a

"MAP/B Authenticate" message to the MSC, which in turn sends
an "RIL3-MM Authentication Request" message, containing
RAND, to the MS over the air.
(4). The MSC may decide to authenticate the MS at this time. It sends the authentication request message
over the established SCCP connection to the BSC, which transparently passes this to the MS via the BTS.
The authentication request message contains two important parameters: a 128-bit random number (RAND)
and a 3-bit ciphering key sequence number (CKSN).
(5). The MS sends the SRES value as a parameter within the authentication response message to the MSC.
(6). The VLR compares the SRES received from the MS to the SRES value available with it as a result of the
previous send authentication procedure with the HLR/AuC. The MS is successfully authenticated if the
two value matches.

(13). Up on receiving "MAP/B Service Request" message from MSC, VLR determines whether the
authentication is required or not, if required
(14). VLR sends request to HLR for authentication parameters for this IMSI.VLR Send
Authentication Information (SAI) request to HLR for this IMSI ["MAP/D Send Parameters"]