The user keys in the phone number for the landline subscriber and .. Send Button ..

presses the Send button Begin RR Connection Establishment Call related information needs to be transported from the mobile phone to the Mobile Switching Center (MSC). This requires the establishment of a Radio Resource (RR) connection to MSC. The first phase of the call setup just sets up this RR connection. RR CHANNEL REQUEST RR connection establishment is triggered by sending the Channel RACH Request message. This message requests the Base Station System (BSS) for allocation for radio resources for the RR connection setup. The mobile now waits for an assignment on the Access Grant Channel (AGCH). At this point the mobile is listening to the AGCH for a reply. Note: The RR CHANNEL REQUEST is sent on a Random Access Channel (RACH). This is a slotted aloha channel that can be used at random, without any coordination between the mobiles. Any mobile can transmit on this channel whenever it wishes. If two mobiles transmit on the channel at the same time, their messages will be lost in a collision. The mobiles will detect the collision via a timeout and retransmit the message after a random back off. Allocate The BSS allocates a Traffic Channel (TCH) to the mobile. The TCH allocation assigns a specifies a frequency and a timeslot on that frequency. After the mobile receives this message, the mobile shall only use the specified resources for communication with the mobile network. RR IMMEDIATE ASSIGNMENT The BSS transmits the radio resource assignment to the Mobile via the AGCH AGCH, Radio_Resource = (TCH, Frequency, Timeslot), Time Correction, Frequency Correction channel. The message also contains the time and frequency corrections. The time corrections allow the mobile to time it's transmissions so that they reach the BSS only in the specified slot. The frequency corrections correct for the Doppler shift caused by the mobile's motion. Apply the time and frequency corrections Adjust the frequency and timing based on the advice from the BSS. This step is required so that ransmissions from the mobile reach the base station at the precise time and with the correct frequency. Tune to the frequency and timeslot The mobile detunes from the AGCH and tunes to the specified radio channel. RR SABM + MM CM SERVICE REQUEST This is the first message that is sent after tuning to the channel. The Mobile TCH, SAPI = 0 initiates a LAPm connection with the BSC by sending a Set Asynchronous Balanced Mode (SABM) message. The service request message meant for the MSC is also sent in this message. The BSS replies with Unnumbered Acknowledge (UA) to complete the TCH, SAPI = 0 LAPm setup handshake SCCP CONNECTION REQUEST + MM CM SERVICE REQUEST The BSS receives the CM Service Request message from the mobile and SS7 forms a "BSSMAP COMPLETE LAYER 3 INFORMATION". The BSS then piggy backs the message on the SCCP connection request message. Check subscriber authentication MSC checks if the subscriber has been authenticated. In this case, the subscriber has already been authenticated, so the authentication procedure is skipped. Enable Ciphering BSSMAP CIPHER MODE COMMAND Since the subscriber has been successfully authenticated, the MSC initiates ciphering of the data being sent on the channel. The channel is ciphered so as so protect the call from eavesdropping.

Expect ciphered data from the mobile Ciphering on the radio link is enabled in three steps. As a first step, the BSS starts expecting ciphered data from the mobile but continues to send data in clear. Since the mobile has not been informed about the ciphering, all data received from the mobile will be in error. RR CIPHERING MODE COMMAND The BSS sends the CIPHERING MODE COMMAND to the mobile. The mobile mode = CLEAR will be able to receive this message as the transmission from the BSS is still in clear. Enable ciphering for received and transmitted As a second step, the Mobile receives data the message and enables ciphering in transmit and receive directions. This action will result in all BSS data being received in error. (The BSS is still transmitting data in clear.) RR CIPHERING MODE COMPLETE Ciphering has already been enabled, so this message is transmitted with mode = CIPHERED ciphering. The BSS will receive this message as it is already expecting ciphered data in the receive direction. Enable ciphering of data transmitted to the The third and final step in the ciphering mobile handshake. The BSS enables the ciphering in transmit direction. From this point on ciphering is enabled in both directions. BSSMAP CIPHER MODE COMPLETE BSS replies back to the MSC, indicating that ciphering has been successfully enabled. RR Connection Establishment Completed At this point a connection has been setup between the Mobile and the MSC. From this point onward, the BSS is just acting as a conduit for transporting the signaling messages between the Mobile and the MSC. Call Setup CC SETUP The Mobile sends the setup message to establish a voice call. The message Dialed Digits contains the dialed digits and other information needed for call CC CALL PROCEEDING The mobile is informed that the call setup is in progress. Connecting... At this point, the mobile phone displays a message on the screen to indicate that call setup is being attempted. Mode Modify allocate The MSC allocates a voice circuit on one Voice circuit towards BSS the digital trunks between the MSC and the BSS. BSSMAP ASSIGNMENT REQUEST MSC informs the BSS about the allocated voice circuit. The call is also Voice circuit switched from signaling to voice. RR CHANNEL MODE MODIFY The BSS notifies the Mobile about the changeover to voice mode. RR CHANNEL MODE MODIFY ACKNOWLEDGE Mobile acknowledges. BSSMAP ASSIGNMENT COMPLETE The BSS responds back to the MSC.

Call is outgoing to other network or PSTN ISUP INITIAL ADDRESS MESSAGE The MSC routes the call and sends the call towards the called subscriber SS7, Dialed Digits ISUP ADDRESS COMPLETE MESSAGE The PSTN indicates to the MSC that it has received all the digits and the called SS7 subscriber is being rung. CC ALERTING The MSC informs the mobile that the called subscriber is being alerted via a ring Alerting Tone ISUP ANSWER The called subscriber answers the call. CC CONNECT The MSC informs the mobile that the call has been answered. CC CONNECT ACKNOWLEDGE Acknowledge the recipt of CC CONNECT. Connected Display that the call has been connected. Conversation The call has entered the conversation phase. The speech path has been setup between the mobile subscriber and the land-line subscriber. Call Release End Button: The mobile subscriber hits End to clear the call. CC DISCONNECT The mobile sends the disconnect message to the MSC. ISUP RELEASE The MSC initiates release on the PSTN side. Disconnect Voice Path The MSC disconnects the voice path and also releases the voice circuit between CC RELEASE The MSC informs the Mobile that it has initiated call release ISUP RELEASED The MSC informs the PSTN that the call release has been completed. ISUP RELEASE COMPLETE The PSTN informs that call release has been completed at its end. CC RELEASE COMPLETE Mobile indicates that the call has been released. RR Connection Release BSSMAP CLEAR COMMAND

Call release has been completed, now the RR connection is released by the MSC. RR CHANNEL RELEASE The BSS initiates RR release with the mobile. BSSMAP CLEAR COMPLETE The BSS informs the the MSC that the RR connection has been released. RR DISC The mobile sends a disconnect message to release the LAPm connection. RR UA The BSS replies with an Unnumbered Acknowledge message. The BSS releases the TCH channel. Call Released Indication Mobile goes back to the default display to indicate that call has been completely released.

GSM MOBILE TERMINATING VOICE CALL

Mobile Terminated Call In this example, the call is originating from outside the PLMN. Route Establishment to find the MSC/VLR
The calling party dials the MSISDN for the mobile subscriber. The PSTN identifies the network (PLMN) that the dialed MSISDN belongs to and will locate a GMSC for that network. The PSTN sends an Initial Address message to the GMSC. The GMSC forwards the MSISDN to the HLR and requests routing information for it. The HLR looks up the MSISDN and determines the IMSI and the SS7 address for the MSC/VLR that is servicing the MS. The HLR then contacts the servicing MSC/VLR and asks it to assign a Mobile Station Routing Number (MSRN) to the call. The MSC/VLR allocates the MSRN and forwards it to the HLR.

Note: It is important to remember that the MSC/VLR assigns a MSRN to the call not to the MS itself.
The HLR forwards the MSRN as well as routing information for the servicing MSC/VLR to the GMSC. The GMSC sends an Initial Addressing message to the servicing MSC/VLR and uses the MSRN to route the call to the MSC/VLR. Once the servicing MSC/VLR receives the call, the MSRN can be released and may be made available for reassignment.

Paging the Mobile Station

The MSC/VLR then orders all of its BSCs and BTSs to page the MS. Since the MSC/VLR does not know exactly which BSC and BTS the MS is monitoring, the page will be sent out across the entire Location Area.

Initial Setup
The MS receives the Page Request (PAG_REQ) on the PCH. The MS recognizes that the page is intended for it, based on a TMSI or an IMSI. The MS sends a Channel Request (CHAN_REQ) message on the RACH. The BSS responds on the AGCH by sending an Immediate Assignment (IMM ASS) message which assigns an SDCCH to the MS. At this point, the network does not know that the MS is the one that it is paging, it only knows that this MS wants access to the network. The MS immediately switches to the assigned SDCCH and sends a Paging Response (PAG_RES) message on the SDCCH. This lets the network know that the MS is responding to its page.

Authentication
Before the network will provide any services to the MS, the network will require the MS to authenticate itself. The BSS sends an Authentication Request (AUTH_REQ) message to the MS. The RAND serves as the "challenge" for authentication. The MS calculates the proper SRES based on the RAND that was given and sends the SRES to the BSS in anAuthentication Response (AUTH_RESP) message. The BSS verifies the SRES. If the SRES is correct then the MS is authenticated and allowed access to the network. Once the MSC/VLR has authenticated the MS, it will order the BSS and MS to switch to cipher mode using the CIPH_MOD_CMD message. Once the MS in encryption mode, the VLR will normally assign a new TMSI to the MS.

Establishing a Channel
Once the MS is authenticated and in encryption mode, The MSC sends a Setup Message to the BSS, the BSS forwards the SETUP message to the MS on the assigned SDCCH.the assigned SDCCH. The SETUP message may include the Calling Line Identification Presentation (CLIP), which is essentially caller ID. The MS responds by sending a Call Confirmed (CALL_CON) message; which indicates that the MS is able to establish the requested connection. The BSS relays the message up to the MSC.

Call Setup
The BSS then sends an Assignment Command (ASS_CMD) message to the MS on the assigned SDCCH. The ASS_CMD message assigns a Traffic Channel (TCH) to the MS. The MS immediately switches to the TCH and responds with an Assignment Complete (ASS_COM) message on the FACCH. The MS begins ringing once it has established the TCH. Remember that all signaling that occurs on the traffic channel actually occurs on a FACCH, which is a time slot that is stolen from the TCH and used for signaling. The MS sends an ALERT message to the MSC on the FACCH. The BSS forwards the ALERT message through the PSTN to the calling party and the caller hears the line ringing.

Call Establishment
Once the user answers the call (by pressing the send button), the MS will send a Connect CON message to the MSC. The Connect message is forwarded back to the caller's switch to activate the call. The MSC sends a Connect Acknowledge CON_ACK message to the MS and the call is established.

Call Disconnect
Disconnect happens the same way as for any other call. In this example, the calling party initiates the disconnect. When the calling party hangs up, the calling party's switch initiates a Release (REL) message. The message is forwarded to the serving MSC, which is then forwarded to the BSS. The BSS will send a Disconnect (DISC) message to the MS on the FACCH. The MS confirms release of the call by sending a Release (REL) message on the FACCH, which is forwarded to the MSC. The MSC sends e Release Complete (REL_COM) message through the BSS to the MS. As far as call control (CC) is concerned, the connection has been terminated. The MS still has a TCH assigned to it, so the BSS sends a Channel Release (CHAN_REL) message to the MS. This releases the radio resource on the Air Interface. The MS responds be sending a final Disconnect message and returns to idle.