Mid Term Report (varun Gupta)

-

Mid Term Report

UNDERTAKEN AT BHARTI AIRTEL LTD. C-25, PHASE–II MOHALI

SUBMITTED TO: Prof. R.K. Agarwal H.O.D. E.C.E. Deptt.

SUBMITTED BY: VARUN GUPTA 509044245 E.C.E.

*************************************************************** LUDHIANA COLLEGE OF ENGG. & TECH. KATANI KALAN, LUDHIANA. *************************************************************** E.C.E., R.No. 509044245

VARUN GUPTA

ACKNOWLEDGEMENT A formal statement of acknowledgment is hardly sufficient to express my gratitude towards the personalities who have helped me to undertake and complete this project. Training in an organization like AIRTEL which is fuelled by the individuals with so much zest and energy, “teaming” up to form a formidable force, was in itself a true learning experience which is going to help me immensely in my career. There is no substitute to “Teamwork”. This is one of the many lessons I learnt during my training in BHARTI AIRTEL Ltd. I hereby convey my thanks to all those who have rendered their valuable help, support and guidance. I would thank Mr. Amit Sood for granting me the permission to work as a Trainee in this esteemed company and for providing me all the facilities. I am equally thankful to Er. Saurabh Bansal & Er. Rahul Dhawan for his valuable guidance and technical acumen that he has provided to me. In the end, I would like to thank the entire staff of Bharti Mobile, Mohali who have directly or indirectly helped in making my training a success and making it a fulfilling and a memorable experience.

VARUN GUPTA

E.C.E, R.No.509044245

VARUN GUPTA

PREFACE With the ongoing telecom revolution where innovations are taking place at the blink of an eye, it is impossible to keep the pace with the emerging trends. In organization where Making Things Right in the first instance is the driving motto, perfection and accuracy are inevitable. Excellence is an attitude that the whole of the human race is born with. It is the environment that makes sure that whether the result of this attitude is visible or otherwise. A well planned, properly executed and evaluated industrial training helps a lot in inculcating a professional attitude. It provides a linkage between the student and industry to develop an awareness of industrial approach to problem solving, based on a broad understanding of process and mode of operation of organization. During this period, the students get the real, first hand experience for working in the actual environment. Most of the theoretical knowledge that has been gained during the course of their studies is put to test here. Apart from this, the students get an opportunity to learn the latest technology, which immensely helps them in building their career.

E.C.E, R.No.509044245

VARUN GUPTA

Table of Contents •

Overview of Airtel

•

The GSM Network • Definition • Introduction

•

Block Diagram of GSM • GSM Network Elements • Network Major System • Network Element Figure • Switching system • Home Location Register (HLR) • Mobile Service Switching (MSS) • Visitor Location Register (VLR) • Authentication Centre (AUC) • Equipment Identity Register (EIR) • Base Station System (BSS) • Operation & Support • Mobile Station (MS) • GSM MS’s Consist

•

Frequency Band Of Operation

•

Radio Channel

•

Duplex Distance

•

Channel Concept

•

Transmission Rate

•

Access Rate

E.C.E, R.No.509044245

VARUN GUPTA

•

Interfaces To App-SMSC • Introduction • System Interfaces • Communication Interface • GSM Interface • SMPP-App SMSC Interface • SNMP Interface • Billing Interface • Hardware Interface • Software Interface

•

O&M Client Interface • Introduction • Performance Management • Session Management • System Management • Alerts • Customer Service Support • O&M App-SMSC Connectivity • O&M Client Description • Login • Alarm & Alert • Process List • Queue Details • Link Status • Message Status • Current Session Status • Rotate Log

E.C.E, R.No.509044245

VARUN GUPTA

OVER VIEW OF

Bharti Enterprises, India’s leading telecom conglomerate has been at the forefront of technology and has revolutionized with its world class services. Established in 1976, Bharti Enterprises has been a pioneering force in the telecom sector with many firsts and innovations to its credit. Working on the principle of providing end to end communication solution across the telecom value chain from manufacture of hardware to development of telecom software and from fixed line to cellular and wireless services, e-commerce, broadband, domestic long distance, undersea cable, infrastructure development and business solutions. Bharti Enterprises under cable chairmanship of Sunil Bharti Mittal is the only company to have brought to India the excellence and expertise of leading Telecom players of the world, Bharti Telecom, the manufacture division of Bharti is the largest sets under the brand name Beetel. Bharti televentures, the services division of Bharti has major interests in Basic, long Distance and Cellular, Broadband and Infrastructure Operations in the country.

E.C.E, R.No.509044245

VARUN GUPTA

THE GSM NETWORK DEFINITION Global system for mobile communication (GSM) is a globally accepted standard for digital cellular communication. GSM is the name of a standardization group established in 1982 to create a common European mobile telephone standard that would formulate specifications for a pan-European mobile cellular radio system operating at 900 MHz. It is estimated that many countries outside of Europe will join the GSM partnership.

INTRODUCTION Cellular telecommunication is one of the fastest growing and most demanding telecommunication applications. Currently, it represents a large and continuously increasing percentage of all new telephone subscriptions worldwide. In many cases, cellular solutions successfully compete with traditional wire networks and cordless telephones. In the future, cellular systems employing digital technology will become the universal method of telecommunication. A standardization group called Global System for Mobile communication (GSM) was established to formulate the specifications for this pan-European mobile cellular radio system. During 1982 to 1985, discussions centered on whether to develop an analogue or digital system. In 1985, GSM decided to develop a digital system. In 1986, companies participated in a field test in Paris to determine whether a narrowband or broadband solution would be employed. In May 1987, the narrowband Time Division Multiple Access (TDMA) solution was chosen. Concurrently, operators in 13 countries (two E.C.E, R.No.509044245

VARUN GUPTA

operators in the United Kingdom) signed the Memorandum of Understanding (MOU) which committed them to fulfilling GSM specifications and delivering a GSM system by July 1, 1991. This opened a large new market. The use of digital radio transmission and advanced handover algorithms between radio cells in networks provides significantly better frequency usage than analogue systems, thus increasing the number of subscribers.

BLOCK DIAGRAM OF GSM

E.C.E, R.No.509044245

VARUN GUPTA

GSM NETWORK ELEMENTS E.C.E, R.No.509044245

VARUN GUPTA

GSM stands for Global System for Mobile communication & is a globally accepted standard for digital cellular communication. GSM is the name of a standardization group established in 1982 to create a common European mobile telephone standard that would formulate specifications for a pan-European mobile cellular radio system operating at 900 MHz. It is estimated that many countries outside of Europe will join the GSM partnership. GSM provides recommendations, not requirements. The GSM specifications define the functions and interface requirements in detail but do not address the hardware. The reason for this is to limit the designers as little as possible but still to make it possible for the operators to buy equipment from different suppliers.

The GSM network is divided into three major systems: The switching system (SS) The base station system (BSS) The operation and support system (OSS)

The basic GSM network elements are in Figure:

E.C.E, R.No.509044245

VARUN GUPTA

GSM Network Elements

THE SWITCHING SYSTEM:

E.C.E, R.No.509044245

VARUN GUPTA

The switching system (SS) is responsible for performing call processing and

subscriber-related functions. The switching system includes the following functional units

HOME LOCATION REGISTER (HLR): The HLR is a centralized network database that stores and manages all mobile subscriptions belonging to a specific operator. It acts as a permanent store for a person’s subscription information until that subscription is cancelled. The information stored includes:  Subscriber identity  Subscriber supplementary services Subscriber location information Subscriber authentication information The HLR can be implemented in the same network node as the MSC or as a stand-alone database. If the capacity of a HLR is exceeded by the number of subscribers, additional HLRs may be added.

MOBILE SERVICES SWITCHING CENTRE (MSC) : The MSC performs the telephony switching functions of the system. It controls calls to and from other telephone and data systems. It also performs such functions as toll ticketing, network interfacing, common channel signaling, and others.

VISITOR LOCATION REGISTER (VLR) : The VLR database contains information about all the mobile subscribers currently located in an MSC service area. Thus, there is one VLR for each MSC in a network. The VLR temporarily stores subscription information so that the MSC can service all the subscribers currently visiting that MSC service area.

E.C.E, R.No.509044245

VARUN GUPTA

The VLR can be regarded as a distributed HLR as it holds a copy of the HLR information stored about the subscriber. When a subscriber roams into a new MSC service area, the VLR connected to that MSC requests information about the subscriber from the subscriber’s HLR. The HLR sends a copy of the information to the VLR and updates its own location information. When the subscriber makes a call, the VLR will already have the information required for call set-up.

AUTHENTICATION CENTRE (AUC) : A unit called the AUC provides authentication and encryption parameters that verify the user's identity and ensure the confidentiality of each call. The AUC protects network operators from different types of fraud found in today's cellular world. The AUC is a database connected to the HLR which provides it with the authentication parameters and ciphering keys used to ensure network security.

EQUIPMENT IDENTITY REGISTER (EIR): The EIR is a database that contains information about the identity of mobile equipment that prevents calls from stolen, unauthorized, or defective mobile stations. The AUC and EIR are implemented as stand-alone nodes or as a combined AUC/EIR node.

THE BASE STATION SYSTEM (BSS): All radio-related functions are performed in the BSS, which consists of base station controllers (BSCs) and the base transceiver stations (BTSs). BSC – The BSC provides all the control functions and physical links between the MSC and BTS. It is a high-capacity switch that provides functions such as handover, cell configuration data, and control of radio frequency (RF) power levels in base transceiver stations. A number of BSCs are served by an MSC.

E.C.E, R.No.509044245

VARUN GUPTA

BTS – The BTS handles the radio interface to the mobile station. The BTS is the radio equipment (transceivers and antennas) needed to service each cell in the network. A group of BTSs are controlled by a BSC.

THE OPERATION AND SUPPORT SYSTEM: The operations and maintenance centre (OMC) is connected to all equipment in the switching system and to the BSC. The implementation of OMC is called the operation and support system (OSS). The OSS is the functional entity from which the network operator monitors and controls the system. The purpose of OSS is to offer the customer cost-effective support for centralized, regional and local operational and maintenance activities that are required for a GSM network. An important function of OSS is to provide a network overview and support the maintenance activities of different operation and maintenance organizations. One of the most important tasks in a mobile telephony system is to continuously keep track of where mobile stations are located. One primary function of the Mobile Services Switching Centre (MSC) and Visitor Location Register (VLR) is to store information, such as location area, about different mobile stations. It is the responsibility of the mobile station to always inform the network about changes in its location and it must also continuously verify that it is tuned to the strongest frequency.

MOBILE STATION: A Mobile Station (MS) is used by a mobile subscriber to communicate with the cellular system. Several types of mobile stations exist, each allowing the subscriber to make and receive calls. Manufacturers of mobile stations offer a variety of designs and features to meet the needs of different markets. The range or coverage area of a mobile station depends on, for example, the output power of the mobile station.

E.C.E, R.No.509044245

VARUN GUPTA

Different types of mobile stations have different output power capabilities and therefore, different ranges. For example, hand-held telephones have a lower output power, (resulting in a shorter range), than a car installed phone with roof mounted antenna.

Ranges for different types of MS’s

GSM MS’s consist of: A mobile terminal A Subscriber Identity Module (SIM): Unlike other standards, in GSM the subscriber is separated from the mobile terminal. Each subscriber’s information is stored as a "smart card" SIM. The SIM can be plugged into any GSM mobile terminal. This brings the advantages of security and portability for subscribers. For example, subscriber A’s mobile terminal may have been stolen. However, subscriber A’s own SIM can be used in another person’s mobile terminal and the calls will be charged to subscriber A.

E.C.E, R.No.509044245

VARUN GUPTA

FREQUENCY BAND OF OPERATION: Frequency bands are allocated on the GSM Band first come first serve basis for first three operations in a state 900 brands for next three operations 1800 band & for further next three operators 1800 band is allotted .

Frequency bands allotted to Airtel in North region: In Punjab In Haryana In Rajastan In HP In J&K

900 band 1800 band 900 band 900 band 900 band

RADIO CHANNEL: A mobile station communicates with a base station via a radio channel. A radio channel is a bi-directional radio transmission path. Each radio channel has two distinct frequencies; one for downlink and one for uplink. • Downlink is defined as the transmission path from the base station to the mobilestation. •

Uplink is defined as the transmission path from the mobile station to the base station.

E.C.E, R.No.509044245

VARUN GUPTA

The base station transmits on one frequency while the mobile station transmits on another frequency. This creates a full duplex communication path. That is, simultaneous communication in both directions.

GSM 900 Uplink frequency

GSM1800

GSM 1900

890-915 MHZ 1710-1785 MHZ 1850-1910 MHZ

Downlink frequency 935-960 MHZ 1805-1880 MHZ 1930-1990 MHZ

E.C.E, R.No.509044245

VARUN GUPTA

DUPLEX DISTANCE: The distance between one uplink frequency and its corresponding downlink frequency is called the duplex distance. The duplex distance varies for different frequency bands, refer to Table below:

Duplex distance

CHANNEL CONCEPT: The carrier separation is 200 KHz; this provides 124 carriers in GSM 900 band, 374 carriers in GSM 1800 band and 299 carriers in GSM 1900 band. Since each carrier is shared by eight mobile subscribers, the total numbers of channels are: 124*8=992 channels in GSM 900 374*8=2992 channels in GSM 1800 299*8=2392 channels in GSM 1900 E.C.E, R.No.509044245

VARUN GUPTA

Each of these channels, which is one time slot on a TIME DIVISION MULTIPLE ACCESS frame, is called a physical channel. A variety of information is transmitted between the BTS and the MS. There are different types of logical channels depending on the type of information being transmitted. Each logical channel is used for a specific purpose, e.g. paging, call setup or speech. These logical channels are mapped onto the physical channels.

TRANSMISSION RATE: The transmission rate over the air is 270 k bit/s. This is true for GSM 900, GSM 1800 and GSM 1900. The amount of information transmitted over a radio channel over a period of time is known as the transmission rate. Transmission rate is expressed in bits per second or bit/s.

ACCESS METHOD: The Air Interface uses the Time Division Multiple Access (TDMA) technique to transmit and receive traffic and signaling information between the BTS and MS. The TDMA technique is used to divide each carrier into eight time slots. These time slots are then assigned to specific users, allowing up to eight conversations to be handled simultaneously by the same carrier.

E.C.E, R.No.509044245

VARUN GUPTA

APP-SMSC

E.C.E, R.No.509044245

VARUN GUPTA

[

Interfaces to App SMSC Introduction: Telesoft’s Application Short Message Service Center (App SMSC) is a store and forward delivery mechanism, enabling two-way message routing between applications and mobile handsets. The application supports: • Application to Application short messaging • Application to Mobile short messaging Telesoft App SMSC is available with multiple variants of supported message delivery attempts. The capacity of the current installation is 80 m/s with 8 E1 links.

E.C.E, R.No.509044245

VARUN GUPTA

System Interfaces App SMSC makes cross-application messaging possible by interfacing with external applications over Short Message Peer to Peer (SMPP) Protocol and with the GSM network over Mobile Application Part (MAP). App SMSC makes the following assumptions visa-vi its interface to the GSM network: • Network runs on ITU-T compliant MAPv2/v3 protocol. • The Gateway Mobile switch Center (GMSC) is the main entry or exit point in the network, which is connected to the external network on E1 links. • The MSC and the App SMSC interface on an E1 through SS7 signaling messages. • The App SMSC has a separate point code.

E.C.E, R.No.509044245

VARUN GUPTA

Figure : SMSCNetwork Connectivity. App SMSC is a middleware application that interfaces with ESME over SMPP Protocol and GSM network over MAP

Communication Interface: The App SMSC interfaces with the GSM network use the E1 interface card, capable of understanding Map V2 and V3 messaging protocols. On the LAN/WAN front, the App SMSC uses the Ethernet interface. It interacts with the ESME and Maintenance Terminal (PC) using the TCP/IP protocol.

GSM Interface: Mobile Application Part/ITU-T Signaling System No 7 (MAP/SS7) interface to the MSC is inbuilt into the App SMSC architecture and performs basic operations such as obtaining routing information for short messages, receiving short message alerts and forwarding short messages. The MAP Protocol supports Phase 1 and Phase 2 of SMS operations.

E.C.E, R.No.509044245

VARUN GUPTA

The MAP interface is based on GSM ETSI specification 9.02 and uses general SS7 protocols to enable the connection between an App SMSC and any common ITU-T- based SS7 network. App SMSC deploys the MAP Interface to communicate with network elements such as the MSC and the Home Location Register (HLR). App SMSC can simultaneously connect to two MSCs using a single card over the MAP Interface.

SMPP- App SMSC Interface: App SMSC kernel communicates with the external applications using data communication networks over SMPP Version 3.3 and 3.4, an open, industry standard protocol designed to provide a flexible data communications interface for short message transfer between SMS applications outside the mobile network and App SMSC. The underlying transport interface between the App SMSC and ESME is based on TCP/IP or X.25 network connection. SMPP is an application layer protocol and is not intended to offer transport functionality. Hence, it is assumed that an underlying network connection would provide reliable point-to-point data transfer.

E.C.E, R.No.509044245

VARUN GUPTA

Figure : SMPP in context of App SMSC

SMPP support is inbuilt into the App SMSC. The SMPP module control external interface access to the App SMSC and interact with the App SMSC kernel functionality App SMSC allows a total number of 60 application sessions at any given point of time. Operators can trace connections in troubled situations. All the traffic is logged and applications can be charged for the messages they have sent. Message exchange between an ESME and App SMSC via SMPP may be categorized under three distinct groups of transactions: • Send Only: Messages sent from the ESME to the App SMSC. (Transmitter mode) • Receive Only: Messages sent from the App SMSC to the ESME (Receiver Mode) • Send and Receive Only: Messages sent from the ESME to the App SMSC and messages sent from the App SMSC to the ESME. (Transceiver Mode)

E.C.E, R.No.509044245

VARUN GUPTA

As the name suggests, send-only applications can merely submit short messages to the App SMSC. The short messages are transmitted to the MSC if the destination is a mobile or delivered directly if the destination is a non-mobile entity. An application must explicitly request for status reports of sent messages. A receiving application gets messages from the App SMSC. Messages could constitute short messages or status reports. Send and Receive Applications can send and receive messages over a single SMPP connection. The application performs the following operations towards the App SMSC: • • • • • • • • • • • • • • • •

Login to App SMSC Logout of App SMSC Transmit messages to single or multiple destinations via the App SMSC Receive messages via the App SMSC from other SMEs (e.g. mobile stations). Query the status of a short message stored on the App SMSC Cancel or replace a short message stored on the App SMSC Send a registered short message (for which a ‘delivery receipt’ will be returned by the App SMSC to the message originator) Schedule the message delivery date and time Select the message mode, i.e. transaction or store and forward. In the transaction mode messages are not stored. Set the delivery priority of the short message Set the delivery time of the short message Set the short message validity period Associate a service type with each message e.g. voice mail notification Change interface parameters Enquire values of the interface parameters

E.C.E, R.No.509044245

VARUN GUPTA

Operations from the App SMSC towards the application are: • Deliver a short message • Deliver status report

Common operation, alive, can be used by both entities to check whether the link is alive. Each message, operation, or response consists of a header, data, and trailer part of the message. All messages are assigned a packet number.

Simple Network Management Protocol Interface: The Send Network Management Protocol (SNMP) Server interacts with the O&M client over SNMP Version 2c. The SNMP server monitors crucial system health specifics such as I/O, CPU Usage etc, Link Functionality, and Process Status and feeds them into the O&M client.

Figure : SNMP in context of App SMSC

The server client interaction is asynchronous in nature i.e. the client polls and the server responds.

E.C.E, R.No.509044245

VARUN GUPTA

The SNMP client and server are integral to the O&M client and server. The SNMP client uses Simple Network Management Protocol (SNMP) to communicate with the SNMP server. The interaction between the SNMP client and the SNMP sever is confined to sending and receiving information on system resources usage such as memory utilization, CPU usage etc. All other clientserver interaction is conducted over User Datagram Protocol.

The O&M client uses the User Datagram Protocol (UDP) to poll the server for real-time statistics on number of SMPP sessions, queue length and any other interaction.

Billing Interface: The App SMSC Billing Interface enables the operator to collect charging data for short message traffic from the CDR log files and prepare this data for transfer to the billing center. The billing information is read from the App SMSC log files. All short message traffic passing through App SMSC is logged enabling flexible billing. The amount of collected data can be filtered according to the type of message or according to the message tariff class.

Hardware Interface: The following hardware configuration is recommended for the App SMSC server: • Sun Fire 280R server with two 1.2 GHz Ultra SPARC-III processors, • 8MB-cache, 2GB memory, • Two 73GB 10,000rpm HH internal FCAL disk drivers, • Sun Quad Fast Ethernet PCI card • ADAX HDC E1 interface card – four E1 ports will also be required for interfacing with the GMSC.

Software Interface: SS7 GSM MAP would be used to interface to GMSC (MSC). These comply with GSM specification 9.02 v7.5.3 and 4.17.1. The various components of the stack are shown below:

E.C.E, R.No.509044245

VARUN GUPTA

Figure 4: Stack Components

O&M Client Interface Introduction: Continuous service availability, manageability and transaction guarantee are mission critical components to satisfy a demanding and growing generation of mobile users. Telesoft’s Short Message Service Center, a store and forward messaging delivery system, is designed with an inbuilt module to monitor operational efficacy of the system round-the-clock and ensures constant service availability. The Operations and Maintenance module is a powerful 24/7 back-office surveillance mechanism to closely monitor App SMSC performance, measure process efficiency, schedule tasks for the systems and manage process workflow. Equipped with a user-friendly graphic interface, the O&M module provides an extensive set of front-end administrative options that help operators map App SMSC performance metrics and undertake immediate corrective measures in case of non-performance without delay. The Operations & Maintenance module, essentially, helps perform the following functions: E.C.E, R.No.509044245

VARUN GUPTA

Performance Management: The O&M module analyses the traffic and resource utilization of the entire App SMSC. Extensive minute-by-minute traffic monitoring facilities track messaging stages between submission and delivery, provides real-time statistics on total number of failed and successful transmissions and identify congestion. Based on this data, operators can initiate immediate preventive action to avoid undue traffic spurts, prevent blockages and regulate traffic flow. The critical performance data that enables operators to regulate overall App SMSC performance are:

•

Link Status: Indicates the functional status of the link and alerts administrators on dysfunctional links.

•

Messages per Minute: Minute-by-minute report on number of successful and failed application originated, application terminated, mobile originated and mobile terminated transmissions.

•

Messages Per Hour: Hourly statistics on successful and failed message transmissions

•

Queue Details: Threshold values defined for each queue and current size of the queue help operators to analyze traffic flow on the system

Session Management: Administrators have the option to track session traffic and block, terminate and resume sessions responsible for disrupting messaging traffic.

E.C.E, R.No.509044245

VARUN GUPTA

System Management: Process-based system performance metrics can be reviewed and system levels errors adversely impacting performance can be fixed. Processes cornering excessive CPU resources and memory usage can be temporarily disabled to economize system resource usage.

Alerts: System overloads or malfunctioning can slowdown App SMSC operations. The O&M module has an inbuilt script that keeps track of key system health operations such as high CPU utilization. Link congestion, Link Down, Point code inaccessible. The module sends an SMS alerts to the operator in case of system malfunctioning. Through alerting capabilities, network troubles are identified, correlated, and corrected quickly

Customer Service Support: The Operations and Maintenance module can complement operator’s customer support set-up. Online, real-time availability of queue statistics can initiate remedial action, ensure continuous service availability, improve customer accountability and have a positive impact on the end-customer.

O&M-App SMSC Connectivity: The Operations and Maintenance module is a standalone application modeled on client-server architecture. The O&M client is a handy tool to monitor critical App SMSC processes from the front end. The O&M client interacts with the O&M server that interfaces with the App SMSC.

E.C.E, R.No.509044245

VARUN GUPTA

Figure 5: O&M connectivity to App SMSC Server

O&M Client Description: Operators can visualize and manage different constituents of App SMSC infrastructure from an easy to use graphical interface. The client interface provides dynamic screen updates, point and click functionality, predictable navigation and easy to learn operational capabilities. The chapter will help system operators to familiarize themselves with various GUI screens The various administrative options in order of their screen appearance are. • • • • • • • •

Login Alarms and Alerts Query Management Log Rotation & Log Enabling Reset Counters Options Status

Each administrative option is discussed in greater detail in the subsequent sections. The sections in this chapter have the same layout as the GUI interface. Relevant screenshots have been used to complement the description of each section and familiarize users with the product’s look and feel.

E.C.E, R.No.509044245

VARUN GUPTA

Login: The screen allows administrators to access various administrative options.

Figure : Login Screen

E.C.E, R.No.509044245

VARUN GUPTA

 User Name: Type user name. The user name should not exceed 30 characters.  Password: Type password. The password should not exceed 15 characters  Click SUBMIT to validate user name and password. In the event of incorrect user name or password, a pop-up window displays an error message.  Click “Option” to exit screen.

Alarms and Alerts: The screen provides dynamic updates on vital App SMSC statistics such as: • CPU Usage • Messages per minute • Messages per hour • Traffic congestion • Memory Usage • Swap Memory usage • Queue Size The screen displays four tables: • Process Table • Messages Per Minute • Messages Per Hour • Queue Details

E.C.E, R.No.509044245

VARUN GUPTA

z Figure : Alarms and Alerts

Process List: All process details are displayed in tabular format.

Figure : Process Table

 Process Name: This parameter signifies the name of the App SMSC process. The processes monitored are:

E.C.E, R.No.509044245

VARUN GUPTA

Esmsc: The esmsc is the primary App SMSC executable and contains the App SMSC business logic. • Database (MySQL): The App SMSC Database stores information critical for processing messages. The database houses critical information such as SMPP Accounts, Alert Note Table, Hourly SMPP and MO Statistics, Retry Policy, App SMSC Counters and Submit SM Backup Table. •

 Memory Usage: This parameter signifies memory (RAM) used by a particular process. Total RAM should not exceed 50 per cent of total memory.  CPU Usage: This parameter signifies CPU utilization by a particular process. No single process should consume more than 80 per cent of CPU memory. If total CPU usage exceeds 80 per cent, restart App SMSC.  Status: This parameter signifies functional status of the process – running or stopped. Running indicates a specific process is functional. Down indicates the specific process is dysfunctional.

Right click current status to Start or Stop a specific process as the case may be. Administrators must exercise the Stop option if a process is cornering a significant portion of CPU and memory resource. Alternately a process can be stopped to undertake regular maintenance work. No single process should consume more than 80 per cent of total CPU resource. Restart the process if App SMSC is consuming excessive CPU resources. Resource Usage The table provides details of Blocks Sent, Blocks Received and CPU Usage. 

E.C.E, R.No.509044245

VARUN GUPTA

Figure : Resource Usage

 Blocks Sent: Refers to numbers of UDP, TCP/IP and SNMP packets/blocks sent to the App SMSC Server.  Blocks Received: Number of packets UDP, TCP/IP and SNMP packets/blocks read by the App SMSC Server. Blocks Sent and Blocks Received enable administrators to analytically investigate behavior of packet flow at a given point of time. Heavy oscillations or wide variations in Blocks Sent and Blocks Received is indicative of disturbances on the system and may need corrective action.  CPU Usage: Refers to input and output packet usage. CPU usage is calculated as User per cent + System per cent

If CPU usage exceeds configured threshold value, system administrators need to take instant corrective action. High CPU usage could be attributed to: • Increased log file size. • Certain processes may be consuming large amounts of CPU or memory. In the event of high CPU usage: • Check length of the message queue. The length of the Application Queue • Should not breach threshold limit of 30,000 messages. • Rotate Logs • Divert traffic to another App SMSC

E.C.E, R.No.509044245

VARUN GUPTA

Queue Details: Administrators can access queue- based break-up of messaging traffic. This helps the administrator to view size of each queue and immediately pinpoint location of any traffic jam.

Figure : Queue Details

 Queue Names: The parameter specifies the App SMSC queues. The queues are: • MO-SMPP Queue: Stores messages pending towards an ESME Application Queue The App Q is the primary App SMSC queue. It stores the mobile and application originated messages to be processed by the App SMSC. The configured queue threshold is 10,000 messages •

Response Queue: Stores the response packets from the MSC before they are retrieved for further processing by the App SMSC. •

Store and Forward Queue: Stores the reference to a message until it reaches its final destination. The queue handles multiple messages for the same destination.

 Threshold: The parameter specifies the maximum queue size limit. The values are dependent on hardware capabilities.  Size: The parameter refers to number of messages currently in the queue.  Message Table The table provides administrators per minute and hourly statistics on successful and failed message transmissions. The statistics are available for E.C.E, R.No.509044245

VARUN GUPTA

application-originated messages, application terminated messages, mobile originated messages and mobile terminated messages.

Figure : Message Table on he Alarms and Admin Screen

 Message Per Minute: The table specifies number of successful and failed messages at that minute.  Message Per Hour: The table specifies number of hourly successful and failed transmissions.  Traffic Rate: The parameter specifies the rate at which App SMSC processes messages.  Traffic rate is calculated as (Total number of successful messages per minute + Total Number of failed messages per minute) / 60

E.C.E, R.No.509044245

VARUN GUPTA

Low traffic rate is indicative of network congestion. The possible reasons are: • Message input rate exceeds message output rate. • Stack is down • Process Failure • Blocked GSM network  Time-out: The parameter specifies number of message that could not be delivered on account of internal processing failure. The possible reasons for timed-out messages are a busy network or low system resources. Timed-out messages whose validity period has not expired are retried for delivery.

System Parameters The parameter specifies the total RAM and SWAP memory available, memory used and memory free

Figure : Memory Table in Alarms and Alerts screen

Note: A swap file is a space on a hard disk used as the virtual memory extension of a computer's real memory (RAM). Having a swap file allows your computer's operating system to pretend that you have more RAM than you actually do. The least recently used files in RAM can be "swapped out" to your hard disk until they are needed later so that new files can be "swapped in" to RAM. One advantage of a swap file is that it can be organized as a single contiguous space so that fewer I/O operations are required to read or write a complete file.  Alarm Off

Figure : Alarm Off

E.C.E, R.No.509044245

VARUN GUPTA

An auditory alarm is triggered when memory usage overshoots the safety threshold. The alarm is triggered in event of the following conditions. • The Memory usage overshoots the safety threshold: The remaining (Memory Free) should not be less than 1000K. Swap Free should not be less than 1000k. • Excessive CPU utilization by a process • A link is down. Green indicates a functional link is functional. Red indicates a dysfunctional link. Figure : Link Down

Link Status: The App SMSC maintains a connection with the MSC over E-1 links. The links perform the critical function of exchanging data packets and signals between the App SMSC and the MSC. Dysfunctional links could lead to a system overload and delay message delivery. The O&M module monitors and records the functional status of these links to ensure round-the-clock availability.

E.C.E, R.No.509044245

VARUN GUPTA



. Link:

Each E-1 link has multiple time slots. The parameter specifies the time slots on the E-1 link.

 Status: The parameter indicates the status of the link. • Down indicates dysfunctional link • Running indicates functional link.



 Date/Time: The parameter indicates the date and time the specific link went down/came up

Message Status: E.C.E, R.No.509044245

VARUN GUPTA

This screen displays current list of pending application and mobile originated messages. Operators have the option to search for specific pending messages. Originating and destination numbers constitute the search parameters.

Figure : Message Status

 Source: Refers to Originating Number  Destination: Refers to Destination Number  Date/Time: Date/Time of Transmission or Acknowledgement.

 Status: This parameter specifies the message status. • Pending indicates the message is yet to be delivered. • In Process indicates the message is being processed by the App SMSC. E.C.E, R.No.509044245

VARUN GUPTA

 Click “Message” to view the contents of a specific message. The content of binary messages is not available to the operator.  Select to Delete: To remove a specific message check “Select to Delete” and Click DELETE. Only pending messages can be deleted. A window pops-up to reconfirm the command.

Current Session Status: Session refers to the number of parallel connections an ESME can maintain with the App SMSC. Current Session Status Details are displayed on the screen. The screen allows you to terminate, block and resume a session.

Figure : Current Session Status

 Specific Session: List session status details of a specific session. E.C.E, R.No.509044245

VARUN GUPTA

 Status: The parameter specifies current session status of the message. Sessions status is dynamically updated on checking either “Terminate”, “Block”, or “Resume” against a particular session.  Session: This parameter specifies the session id.  Connected Duration: The parameter specifies the time for which an ESME was connected to the App SMSC.  Message Sent: The parameter specifies total number of messages sent in that session.  Check “Terminate” to cease message transmission by a particular session. Administrators can terminated a session when the user account has expired.  Check “Block” to drop message packets sent by a particular session. Administrators can block a session when the App SMSC is in a surge condition.  Check “Resume” to recommence message flow for Blocked session. Administrator cannot resume terminated sessions. Administrators have the option to Terminate, Block and Resume all sessions by checking the relevant radio button and then pressing OK.

Rotate Log: App SMSC maintains a log of all messaging transactions. The records are available as logs files stored in text format. The log files help the administrator to: • Trace messages • Trace number of delivery attempts • Trace delivery failure cause • Generate bills

• Generate statistics • Logs can also be used for debugging E.C.E, R.No.509044245

VARUN GUPTA

These log files can however grow to a humongous size unless administered in some way. The screen provides administrators three options •

Rotate Logs: File rotation consists of closing the current log file and opening a new one to break the log files into convenient sizes. Administrator can rotate Session, Event and Audit logs.

•

Enable Logs: SMPP Session Logs contain packet traces of the traffic exchanged between the App SMSC and the client. To conserve network resources, SMPP logs are generated on request. Administrators can generate (enable) these logs from the front-end.

•

Disable Logs: Administrators can halt SMPP logging by exercising the disable session log option.

Figure : Log Details

ROTATE LOG: E.C.E, R.No.509044245

VARUN GUPTA

File rotation means closing the current log file and opening a new one to break the log files into convenient sizes. Administrator can rotate Session logs from the O&M client. SMPP session logs contain packet traces of the traffic exchanged between the App SMSC and the client.  Rotate All Session Logs • Check ALL SYSTEM ID • Click OK  Rotate Specific Session Logs • Check SPECIFIC SYSTEM ID • Check SPECIFIC SESSION • Check SESSION NAME to rotate a specific Session Log • Click OK  Enable Log/Disable Logs SMPP logs are generated on request. The screen allows you to enable or disable logs for: • All system id • Specific system id • Specific session under a particular system id

Figure : Enable/Disable Log

E.C.E, R.No.509044245

VARUN GUPTA

 Enable Logs for all System id • Check ALL SYSTEM ID • Check ENABLE • Click OK  Disable Logs for all System id • Check ALL SYSTEM ID • Check DISABLE  Enable Logs for Specific System ID • Check SPECIFIC SYSTEM ID to enable/disable • Check ALL SESSIONS to enable/disable all sessions of a specific system lid • Check SPECIFIC SESSION to enable/disable specific sessions of a specific system id. • Check ENABLE to enable logs  Disable Logs for Specific System ID • Check SPECIFIC SYSTEM ID to enable/disable • Check ALL SESSIONS to enable/disable all sessions of a specific system lid • Check SPECIFIC SESSION to enable/disable specific sessions of a specific system id. • Check DISABLE to disable logs

E.C.E, R.No.509044245

VARUN GUPTA

Reset Counters To set the number of counts to zero. Administrator can reset MO and AO counters.

Figure : Reset Counters

E.C.E, R.No.509044245

VARUN GUPTA