1 VARIOUS INTERFACES

1.1 OVERVIEW
Each interface between the GSM system entities is an open interface which is defined in the GSM specifications. The figure on the opposite page provides an overview of the protocols used on the interfaces. Between the BSC and the MSC the ITU-T Signaling System No.7 protocol is used with the different types of applications. Between the MS and the BSC the LAPD protocol is used. Entities on the same functional level are able to communicate with each other. The sloping lines in the figure indicate a mapping between messages from one to another protocol. The following figure shows the scheme of GSM signaling architecture.

Fig : 1 1.1.1 MS-BTS INTERFACE (UM)

The GSM standards identify this as the Um-Interface. Um is the radio or air interface consisting of three protocol layers: Layer 1: Radio subsystem layer (the timeslots on the radio carrier) Layer 2: LAPDm (modified version of ISDN LAPD protocol) Layer 3: Three protocols including:

1.1.1.1 RIL3-RR (Radio Interface Layer 3 - Radio Resource management) It is used for the direct MS - BSC communication. It comprises paging, radio-channel access, ciphering, hand over and radio-signal control procedures. An example of a RIL3-RR message is: MS report indicating the quality of the received signal. 1.1.1.2 RIL3-MM (Mobility Management) It is used for the communication between the MS and the MSC. It handles roaming and authentication procedures. An example of a RIL3-MM message is: MS location update. 1.1.1.3 RIL3-CM (Call Management) It is used for the communication between the MS and the MSC. It takes care of the ordinary call-control procedures such as call establishment and release, and access to services. The BSS performs a direct transfer of the RIL3-MM and RIL3-CM protocol messages between the MS and the MSC without BSS processing.

1.1.2 BTS-BSC INTERFACE (ABIS)

The Abis-interface consists of three protocol layers: Layer 1: physical layer Layer 2: LAPD Layer 3: BTSM (BTS Management Part) It is used to exchange control information between the BSC and the BTS. In the BTS there is a mapping between the BTSM protocol and the relevant RIL3-RR messages over the radio interface (RR).

1.1.3 BSC MSC INTERFACE (A)

The GSM standards identify this interface as the A-Interface. The transport and Signaling portions of the protocol are based on the ITU-T Signaling System No. 7. The application parts are GSM specific. Transport part - Message Transfer Part (MTP) of ITU-T SS7. Signalling part - connectionless and connection-oriented Signalling Connection Control Part (SCCP) of ITU-T SS7 Application part- BSS Application Part (BSSAP) The BSSAP includes two parts: 1. BSSMAP - BSS Management Application Part. BSSMAP supports all procedures between the MSC and the BSS that are related to resource management, maintenance and handover control. 2. DTAP - Direct Transfer Application Part. DTAP provides the protocol for the direct interface between the MSC and the MS. The DTAP part is not interpreted by the BSS. DTAP includes two classes of messages: DTAP-MM (Mobility Management functions) and DTAPCM (Call Management) functions.

It depends on the type of application part message to be transferred whether connectionless SCCP or connection-oriented SCCP is used. For example, connectionless SCCP is used when a paging request is sent from the MSC to the BSC. Connection-oriented SCCP is, for example, used when a wireless call has to be established.

1.1.4 MSC VLR INTERFACE (B)

The VLR is an integral part of the MSC. Each MSC in the PLMN has its own VLR. Although the B-Interface is shown as an open interface, it is implemented as an internal interface since the VLR always resides within the serving MSC.

1.1.5 MSC HLR INTERFACE (C)

The C-Interface uses the MAP protocol to retrieve routing information when calls to MSs are being set up through the MSC. The non-circuit-related Mobile Application Part (MAP) protocol is used independently of the physical location of the HLR. The MAP protocol uses Transaction Capability Application Part (TCAP) to manage the dialog between two network entities.

1.1.6 VLR HLR INTERFACE (D)

The D-Interface uses the MAP protocol to support the transfer of subscriber information and instructions relative to the cancellation or modification of subscriber information. The MAP protocol is used independently of the relative locations of the associated VLR and HLR.

1.1.7 MSC MSC INTERFACE (E)

The signaling on the E-interface consists of two components: 1. Trunk signaling - ITU-T Signaling System No.7 ISDN User Part (ISUP) signaling 2. Inter-Entity signaling- Uses the Mobile Application Part (MAP) protocol for interMSC handovers and SMS.

1.1.8 MSC EIR INTERFACE (F)

The F-Interface uses the MAP protocol to retrieve MS equipment identity related information from the EIR to determine whether or not to provide service to the MS.

1.1.9

VLR VLR INTERFACE (G)

The G-Interface uses the MAP protocol to support the transfer of subscriber information between VLRs when the associated MS moves from one VLR service area to another.

1.1.10 HLR AUC INTERFACE (H)

Access to the authentication database is always accomplished through the HLR; it is not a GSM defined open interface. The HLR interface to the AUC is implemented as an internal interface in the MSC. Other entities use the MAP interface to the HLR to access AUC data.

1.1.11 BSS - OMC AND MSC OMC INTERFACES

The OMC is connected to the BSS and the MSC via a synchronous X.25 interface. GSM-900 and GSM-1800 supports E1 communication interfaces whereas GSM-1900 supports T1 interfaces. In addition the OMC only allows selecting T1 interfaces if the BSS operates in the 1900 MHz band. The OMC is connected to the MSC via an asynchronous V.24 interface/ Each In addition to that, the OMC is connected to the MSC via an Asynchronous V.24 interface

1.1.12 MSC BILLING CENTER INTERFACE

Each MSC writes call accounting records to disk and the Billing Center can poll the MSC disks for the billing data or the MSC can initiate transfer of the billing data using the FTAM/X.25 protocol.