Topic: Basic Steps In The Formation Of A Call

BASIC STEPS IN THE FORMATION OF A CALL

CONTENT : 1. Connection Request 2. Paging Procedure 3. Identification Process 4. Authentication 5. Ciphering 6. Call Clearing 7. IMSI Attach and Detach

1.CONNECTION REQUEST

To get any type of service from the system, the mobile has to request the service. This can occur in many ways. For example, the mobile unit may request a channel or can respond for the system page, IMSI attach, IMISI detach, normal and periodic location updating, call set up, or supplementary services .(As shown in Table 1) As shown in figure As a first step the mobile will request service on the Reverse Access Channel (RACH). If the request is not answered by the network within a set time the mobile will repeat the message a predetermined number of times, till it is answered. Upon receiving the message, BSS sends an acknowledgement with the same random number as originally received over the AGCH channel along with the channel number for SDCCH. The assigned SDCCH channel is usually at 1/8 TCH (SDCCH +SACCH) rate. One-eighth TCH simply means these channels transmit data once every eight frames; their data rate is only 1/8 of TCH/F.
3

1.CONNECTION REQUEST

It should be noted that the SACCH can also be assigned with SDCCH. SACCH is also assigned when the mobile gets the assignment of a TCH. The MS at this point sends SABM frame (Set Asynchronous Balanced Mode) as initial message. This will allow MS to set up link layer protocol (layer2) over the radio path. This message contains the reason for the specific message. If the response is result of paging, the mobile provides a RIL3-RR paging response If the response is the result of location updating or IMSI attach, the resulting message by mobile is RIL-MM location updating request For IMSI detach the message on the application layer is RIL3-MM IMSI detach For call setup and supplementary services the message is RIL3-CC (Application Layer; Call Control Management) and shown in Table-1
4

1.CONNECTION REQUEST

Table-1
Type of Connection Request by Mobile and Their Responses

Reason for Access

Paging response Location update or IMSI attach IMSI detach Call setup and supplementary services

Initial Message
RIL-3 RR paging response RIL-3 MM location update RIL-3 MM IMSI detach RIL-3CC (Application layer; call control management)

1.CONNECTION REQUEST
MS BSS MSC VLR HLR AUC

RIL3-RR Channel request (on RACH) RIL 3-RR immediate Assign (on AGCH; assigns a SDCCH channel) SABM < Identity of message>(SDCCH) Initial Message Unnumbered acknowledge (UA) SCCP Connection Request BSSMAP Complete Layer 3 information

SCCP Connection Confirm

Fig. Connection Request Procedure 6

1.CONNECTION REQUEST

SABM frame contains the setup request (CM Service Request) to the network.
In response to a SABM frame message, BSS sends an Unnumbered Acknowledge (UA) message. At this point, BSS requests connection to MSC through a SCCP connection request message, to which the service request information is attached as a BSSMAP complete layer 3 information message. MSC in turn responds to BSS by a SCCP connection message. One of the response messages is a result of paging. It should be noted that the RIL 3-MM and RIL-3 CC messages are between MS and MSC and pass directly through BSS. In other words, the BSS is transparent to these messages. BSSMAP messages are between BSC and MSC
7

2.PAGING PROCEDURE

Necessary Steps For Paging Procedure:

The network initiates the paging procedure by broadcasting a paging request message on the appropriate paging sub-channel. The use of a sub-channel narrows the time when a group of mobile users will be looking for their page. Mobile users do not have to continuously monitor the PCH and can perform other tasks. There are three types of paging messages : A paging request message includes, for each paged message by MS, an indication that defines how mobiles of different capabilities shall code the field in the Channel Request message. The information received in the Channel Request can be used by the network to assign a suitable channel. A paging request message may include more than one MS identification. The choice of message depends on the number MSs to be paged and types of identities that are used. The maximum number of paged MSs per message is four when using only TMSIs for the identification of the MSSs.
8

i)

ii)

2.PAGING PROCEDURE

iii) The Ms is required to receive and analyze the paging messages and immediate assignment messages sent on the paging sub-channel corresponding to its paging subgroup. Upon the receipt of a Paging Request message, if the access to the network is allowed, the addressed message shall within 0.5sec initiate the immediate assignment procedure by requesting a channel through Revese 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 as shown in Figure 2

2.PAGING PROCEDURE

MS Paging Request on paging channel (1)

Network

Channel request on Random Access Channel (RACH) (2) IMM Assigns SDCCH Channel (3) SABM ( Paging Response, initial message (4) Fig.2 Paging procedure
10

3.IDENTIFICATION PROCEDURE

Identification procedure is used to identify the MS/SIM by its IMSI if the VLR does not recognize the TMSI sent by the MS. This can be the result of the mobile changing the MSC/VLR area from the last time it access the system or due to similar reason. If identification is required, the VLR first sends a MAP/B Provide IMSI message to the MSC as shown in Fig,3. As a result of this message , MSC sends an RIL3- MM Request message to the MS. The MS respond by returning an RIL3-MM Identity Response message, containing its IMSI, to the MSC. In fig 3 we designate this operation by <IMSI>, meaning that the message contains the mobile IMSI. It should be noted that this is the only time that the IMSI is sent over the air unencrypted. Normally TMSI is sent over the air, and IMSI is not required
11

3.IDENTIFICATION PROCEDURE

MSC then sends the MAP/B IMSI acknowledge to the VLR. If the IMSI is currently in the VLR, then the VLR must get the individual users file from the HLR, which identifies its IMSI To do this, the VLR sends HLR a MAP/D Update Location message. Assuming the IMSI is, in fact, registered in the HLR, the HLR responds with a MAP/D Update Location Result message followed by a MAP/D Insert Subscriber Data message containing other pertinent data needed by the VLR. VLR acknowledges the data transfer with a MAP/D Insert Subscriber Data Result message to HLR.

12

3.IDENTIFICATION PROCEDURE MS BSS MSC VLR MAP/B Provide IMSI RIL 3 MM identity Request RIL 3 MM Identity Response MAP/B IMSI Acknowledge MAP/D Update Location MAP/D Update Location Result MAP/D Insert Subscriber Data MAP/D Insert Subscriber Data Result HLR AUC

<IMSI>

Fig 3 Mobile Identification Process

13

4.AUTHENTICATION PROCEDURE

Authentication process may be run at each and every location update and at the initiation of every service request. Authentication process starts at VLR. If the VLR determines that authentication is required, it sends a MAP/D Send Parameters message to HLR, which relays the message to AUC. AUC then draws a value for the random challenge RAND and applies Algorithms A3 and A8 to generate the response SRES and cipher key. The AUC then returns the triplet ( RAND , SRES ,Kc ) value VLR in a MAP/D Send Parameter Result message. Actually the AUC normally calculates and sends a few such triplets at a time for each requesting MS, so the VLR only has to request parameters from the AUC if it has no stored unused triplets for the particular MS.

14

4.AUTHENTICATION PROCEDURE

The VLR then sends a MAP/B Authenticate message to the MSC, which in turn sends RIL3-MM Authentication Request message , containing RAND, to the MS over the air. The MS calculates the required response SRESc using Algorithm A3 and authentication key Ki stored in the SIM. SRESc is returned to the MSC in a RIL3 MM Authentication Response message. The MSC compares SRESc with SRES (SRES response is already at MSC as it has been sent to MSC by VLR as a part of MAP/B authenticate message), and if they agree, it sends the an RIL3-MM Service Accept message. The MSC also sends the VLR a MAP/B Authentication Complete message If SRESc and SRES disagree, the MSC sends the MS an RIL3-MM Service Reject message and terminates the request for service.( Authentication process is shown in Figure 4)
15

4.AUTHENTICATION PROCEDURE
MS BSS MSC VLR HLR AUC

MAP/D Send Parameters MAP/D Send Parameters Results MAP/B Authenticate RIL3-MM Authentication Request RIL3-MM Authentication Response MAP/B Authentication Complete RIL3 MM Service Accept (Conditional) RIL3-MM Service Reject ( I f not accepted) MAP/D Authentication Complete

Fig. 4 Authentication Process.

16

5.CIPHERING

Encryption ( or ciphering ) is normal required for all user transaction over the RF link once the user has been authenticated by the system. This is an optional feature and may or may not be included in the particular system. Thus, the decision to switch encryption is dependent upon the operator. Ciphering begins with the VLR sending the MSC a MAP/B Set Cipher Mode message containing the value Kc for use. This Kc is generated during authentication by using Algorithm A8 at AUC. The MSC sends the new ciphering mode and ciphering key to BSS in a BSSMAP Cipher Command message to the MS. The BSS in turn sends an RIL3-RR Ciphering Mode Command message to the MS The MS then switches to encrypted transmission and reception and sends back an RIL3-RR Cipher Mode Complete message in encrypted mode.
17

5.CIPHERING

After BSS receives this message, it sends a BSSMAP Ciphering Mode Complete message to the MSC to indicate that the encryption process is complete.( Shown in Fig.5)

18

5.CIPHERING
MS BSS MSC Yes BSSMAP Cipher Mode Command RIL3- RR Cipher Mode Command RIL3 RR Cipher Mode Complete VLR HLR AUC

MAP/B Set Cipher Mode

BSSMAP Cipher mode Complete

Fig.5 Encryption Process

19

6.CALL CLEARING

(i) (ii) (iii)

Call clearing can be initiated by either the land- based user or mobile user. Network Initiated ( Mobile Terminated Call) Mobile- Initiated ( Network Terminated Cal ) NET WORK INITIIATED (MOBILE-TERMINATED CALL) The release process in this case starts with a Release request from PSTN. Upon receiving this message the network (MSC) initiates the clearing of a call by sending a Disconnect Messages to MS. The MS in turn responds by a Release Channel Message in DTAP protocol to the MSC. Upon receiving the Release Channel Message from the MS, the network sends a Release Complete to the MS and sends the confirmation message for channel release to PSTN. (Call clearing process as initiated by land is shown in Fig.6(a).

20

6.CALL CLEARING
MS BSS MSC VLR HLR PSTN

CONVERSATION
Release (REL) RIL3- RR Disconnect (BSSMAP) Disconnect Message

Release (DTAP)

Release Confirmed (REL CONF)

Release Complete RIL3-RR Release Complete (BSSMAP)

Fig.6(a) Call Clearing ,Mobile Terminated

21

6.CALL CLEARING

(ii) MOBILE- INITIATED (NETWORK TERMINATED CALL) MS initiates the clearing of a call by sending a Disconnect Message to the network. The clearing procedure applies with the exchange of the Release and Release Complete Message from the network and MS, respectively. Upon receiving the Disconnect Message from MS, MSC can send the Release message to PSTN without waiting for the Release Complete Message from the MS as shown in Fig.6(b).

22

6.CALL CLEARING
MS BSS MSC VLR HLR PSTN

CONVERSATION
RIL3- RR Disconnect (BSSMAP) Disconnect Message Release (DTAP) Release (REL) Release Confirmed (REL CONF)

RIL3-RR

Release Complete

Release Complete (BSSMAP)

Fig.6(b) Call Clearing Network Terminated

23

7.IMSI ATTACH AND DETACH

The IMSI attach and detach procedures register and unregister the mobile to the system. If the mobile is attached , he will be paged in the LA where he is present. If the mobile is detached, the system will not waste its resources in paging for an incoming call. Registering and unregistering are necessary for the system to page or not to page the mobile. IMSI ATTACH PROCEDURE: The IMSI attach procedure is used by the MS to indicate that it has reentered the active state ( Power On). The IMSI attach is also performed as a part of the location updating procedure. The IMSI attach procedure is a complement of the IMSI detach procedure, and it is used to indicate that the IMSI is now active in the network. IMSI attach is invoked if attach/detach procedures are required by the network and an IMSI is activated in a MS ( that is, activation of a MS with plug-in SIM) within the coverage area of the network or when a MS with an IMSI activated out side the coverage area enters the coverage area.
24

7.IMSI ATTACH AND DETACH

IMSI attach is marked in MSC/VLR with an attach flag. This flag is related to IMSI. The Following sequence of events describes the IMSI attach procedure as shown in the Fig.7(a). Upon turning the power on , MS sends an RIL3-RR Channel Request Message on the Reverse Access Channel to BSS. The network assigns the channel and the BSS sends an RIL3-RR IMM Assignment Message to Ms over the AGCH for the connection request message. This message assigns the SDCCH to Mobile. After the channel is assigned, MS sends an RIL3-MM IMSI Attach message over the SDCCH to BSS, which is forwarded to MSC and then to VLR as a MAP/B protocol message. VLR acknowledges MSC as IMSI Attach Acknowledge as a MAP/B protocol, which is forwarded to BSS then to MS. MSC also sends Clear Command for the channel release to BSS as BSSMAP protocol, which is then forwarded to MS. Upon receiving the RIL3-RR Disconnect signal from MS , a Clear Complete message is sent to MSC as BSSMAP protocol.

25

7.IMSI ATTACH AND DETACH

MS BSS
MOBILE TURNS ON
RIL3-RR Channel Request On RACH RIL3-RR IMM Assign On AGCH SABM<identity of message> (SDCCH) : establishes the signaling link UA (SDCCH) RIL3-MM IMSI attach (SDCCH) : Causes the mobile to seize a dedicated SDCCH channel

MSC

VLR

HLR

<TMSI>
IRL3-RR IMSI attach ack. (SDCCH) RIL3-RR Channel Release (SDCCH) RIL3-RR DISC (SDCCH) UA (SDCCH) BSSMAP Clear Complete IMSI attach ack.

: The VLR is requested to mark the IMSI as active. <TMSI> System can now page MS IMAP/B IMSI attach ack. for PSTN/ISDN calls
MAP/B Attach IMSI

BSSMAP Clear Command : Clear command MSC asks the BSS to release the allocated dedicated resources

Fig. 7(a) IMSI Attch

26

7.IMSI ATTACH AND DETACH

IMSI DETACH PRCEDURE:

Similar to IMSI attach, the IMSI detach procedure may be invoked by a MS if the MS is deactivated or if the SIM is detached from the MS. A flag (ATT) broadcasted in the System Information Message on the BCCH is used by the network to indicate to the MS whether the detach procedure is required. The procedure causes the MS to be declared as inactive in the network. Once IMSI is detach is active , MS can neither transmit nor receive. The system will also not page.

27

7.IMSI ATTACH AND DETACH

The IMSI detach procedure starts with MS sending an RIL3_RR Channel Request message on RACH to BSS . BSS assigns the SDCCH and notifies the channel assignment over AGCH. MS then sends an RIL3-MM IMSI Detach Indication message to the BSS> The message identifies the MS ( indicated here as <IMSI> ) and contains an eight-bit code indicating IMSI detach. After receiving the IMSI Detach Indication message from MS, the BSS forwards this message in a BSSMAP complete layer 3 information message to MSC. MSC in turn updates the state of MS in the VLR with a MAP/B Detach IMSI message. At this stage all terminating calls to Ms are rejected and the system does not page the mobile any more

28

7.IMSI ATTACH AND DETACH

VLR forwards this message to HLR as MAP/D Deregister Mobile Subscriber, and HLR marks MS as unregistered. HLR forwards a MAP/B Deregistration Accepted message to VLR, which in turn sends a MAP/B Acknowledge IMSI Detachment message to MSC. No response is returned to the MS as shown in the attached sequence chart ,Fig.7(b) This is rightly so because the mobile would be switched off before the return message is sent from the BSS to MS. MSC sends BSSMAP Clear Command to BSS to clear the SDCCH channel assigned to MS. The BSS acknowledges via a BSSMAP Clear Complete message to MSC. These commands for IMSI detach procedure are shown in Fig.7(b)

29

7.IMSI ATTACH AND DETACH

MS
Mobile turns off
RIL3-RR Cannel Request

BSS

MSC

VLR

HLR

on RACH
RIL3-RR IMM Assign (AGCH) SABM <identity> (SDCCH) : establishes the signaling link UA < identity> (SDCCH) RIL3-MM IMSI Detach < TMSI > BSSMAP Complete MAP/B Detach IMSI <TMSI> : The VLR sets the MSI detach flag MAP/D Deregister Mobile Sub : AGCH; assigns SDCCH

<IMSI> MAP/D Deregistration Accepted

BSSMAP Clear Command BSSMAP Clear Complete MAP/B Acknowledge IMSI Detachment

Fig. 7(b) IMSI Detach

30