What is INMCC?

INMCC is Indian Mission Control Centre. The main goal of this design is to search via
satellites for the land users/ship/aircraft that are in a distress situation and then to inform the
rescue centres about this distress situation, so that they can take actions immediately.

Terms Used
LUT -Local User Terminal (ground stations that

receive signal from the satellites).

SPOC -Search and Rescue Point of Contact.

BEACONS -The radio beacons are activated automatically/

manually at the time of emergency which is

received by the satellites.

COSPAS-SARSAT -The Cospas-Sarsat is an international satellite

system for search and rescue, comprised of a

constellation of satellites in polar and

geostationary orbits and a network of ground

stations.

MCC -Mission Control Centre (main system which

informs the search and rescue system about the

distress.

Abstract
The INMCC system consists of six different systems for performing the operations as separate
modules. Here we are considering only one module which is the communication module. The
main function of this module is to receive messages from LUTs and to save the received
information in the SQL tables for future reference. Validating the information received from
LUT and placing the details of destination to be rescued on the output tables is done by alert
processing module. Another function of the communication module is to read these messages
from the output tables and to convert them into a suitable format for RCCs, SPOCs, etc.

Software and Hardware Requirements

Department Of Telecommunication Page 1

Software Configurations:

Communications Output Message Converter:

Convert output messages to RCCs, SPOCs, and MCCs to proper format and pass output
messages to Communications for transmission.

Required Operating System: Windows 2000

Required Softwares: Microsoft Visual C++ 5.0 (or higher), ODBC Driver 2.6

Communications Input Message Converter:

This program takes input data from the Communication Module and puts it to the appropriate
database tables. A separate thread passes output LUT data to Communication in order to
communicate with the LUT.

Required Operating System: Windows 2000

Required Softwares: Microsoft Visual C++ 5.0 (or higher), ODBC Driver 2.6

Communications Processor:

Communicates with LUT, MCC, and RCC via X.25, X.400 and FTP.

Required Operating System: Windows 2000

Required Softwares: ODBC Driver 2.6

Hardware Configurations:

Processor: Intel P IV 1.8 GHz

RAM: 512 MB

HDD: 80 GB

INTRODUCTION TO THE SYSTEM:

Department Of Telecommunication Page 2

COSPAS-SARSAT, a space-based Search And Rescue (SAR) system, is listening for
emergency signals from an aircraft, ship or person in trouble. Once COSPAS-SARSAT hears
a signal on an emergency frequency, it is able to rapidly locate the source of the signal and to
transmit the location to SAR personnel.

The COSPAS-SARSAT system detects the signals from emergency radio beacons.
These are three kinds of emergency radio beacons, classified by who uses them. Aircraft uses
Emergency Locator Transmitters (ELTs); ships uses Emergency Position Indicating Radio
Beacons (EPIRBs); and Personal Locator Beacons (PLBs) are used by people taking part in
land activities such as hiking, camping, or canoeing in the wilderness.

The location of the received beacon is determined by the Doppler Frequency analysis
performed in the ground stations. The relative motion of the satellites causes the Doppler shift
as it orbits with respect to the stationary beacon on the Earths, surface. The satellite relays
these distress signals to a ground station known as a LUT where the origin of the distress call
is calculated. The ground station then relays this information to an MCC, which alerts the
SAR resource.

EXISTING SYSTEM IMPLEMENTATION PLAN:

Department Of Telecommunication Page 3

 NETWORK
PRINTER

MCCDbs

MCCProc

LAN PC
SWIT SWITC Lucknow-
CH H Serial
MCCPrim
GEOLUT-
RS232

Bangalor
e-RS232
MCCComm
AFTN-
Modem

MCCPrim

ISTRAC
MCCLinux NETWORK

Fig. System Diagram Of INMCC

Department Of Telecommunication Page 4

Primary Functions:

 Convert all input me

us.

 Receive and send m

 Convert output mess

 Process X.400 and E

 Receive orbital elem

COMMUNICATION PROCESS
Department Of Telecommunication Page 5
Data Structures:

Inputmessage Table And Inputprocess Table:

Communication input message converter is responsible for receiving data from the
LUTs and to store the information in the inputmessage table. This inputmessage table is
transforms into new table called inputprocess table which is full information is done only
when full information is completely received from the LUT. This inputprocess table is an
input for the alert process model. This model will validate the data and verifies it. After
verifying this module will store its data in the outputprocess table.

Output Message And Output Processing Table:

The output processing table is used by the Communication processing module to send
an output message(or to process a command).An output message ,identified by foreign key
”OutMsgld” in the output processing table, is a group of data that are to be transmitted as a
unit to a destination. For each output message there is a row in the Output Message Table that
contains “OutMsgld” as a primary key. After the message has been successfully sent to the
destination it is entered in the output message table.

An entry (row) in the Output Processing Table, identified by field “outProcId” , is by

an alert processing module for each destination that is supposed to receive a particular output
message.

Once written an entry in the Output Processing Table, the Communications Data
Converter will read the entry. The Com converter will then read in the appropriate output
Data Structure(s) convert them to external format, and give them to Communication module
to transmit.

LUTconfig table:

The comm input converter will read the input data from the LUTs and stores the
information about the LUT in the LUTs table. This will be used by the alert process module to
filter any redundant information that is received from the same LUT. By using this table the
comm input converter will create an entry in the input message table.

Department Of Telecommunication Page 6

Existing System Drawbacks:

 The MCC_COM exe available on the communication system does

not get connected certain times to named IO pipe and this happens
only when the system is rebooted.

 There is no proper user interface available to the operator to check

the system status.

 The system does not notify the operator if any services are stopped
and if there is any failure.

 The system does not provide the archival procedure for the database
tables and log files being generated in the communication system.

Future Enhancements:

 Web based monitoring control for the whole system can be provided
as the operator can access the system remotely.

 FTP/VPN should be established as a module of communication to

transmit the alert messages.

 In case, if any one of the communication medium fails the alert

messages can be sent via SMS services.

 The communication between the MCC_LUT can be made Ethernet

enabled with IP security instead of point to point serial links.

 The communication between MCCs, RCCs, and SPOCs can also be

made Ethernet enabled.

 The present system makes use of the local Linux server for
transmitting the emails. As a future enhancement Microsoft
Exchange server can also be used.

Department Of Telecommunication Page 7

Department Of Telecommunication Page 8
Reference Documents:
1. Introduction to the COSPAS-SARSAT System C/S G.003 Issue 5 – Revision 1
October 1999.

2. COSPAS-SARSAT Mission Control Centre Standard Interface Description C/S A.002

Issue 4 – Revision 12 October 2008.

3. COSPAS_SARSAT Data Distribution Plan C/S A.001 Issue 4 – Revision 11 October

2008.

4. Handbook On Distress Alert messages For Rescue Coordination Centres (RCCs),

Search And Rescue Points of Contact (SPOCs), And Imo Ship Security Competent
Authorities C/S G.007 issue 1 – Revision 1 October 2009.

Websites:
1. http://www.cospas-sarsat.org

2. http://www.inmcc.istrac.org

3. http://www.imo.org/index.html

4. http://www.itu.int/aboutitu/index.html

5. http://www.icao.int/

Department Of Telecommunication Page 9