Pages - Menu

Monday, 25 August 2014

Adhoc Network Protocol

ABSTRACT
To provide a secure routing and data transfer between the nodes using location aided routing protocol. An ad-hoc mobile network is a collection of mobile nodes that are dynamically and arbitrarily located in such a manner that the interconnections between nodes are capable of changing on a continual basis. The primary goal of such an ad-hoc network routing protocol is correct and efficient route establishment between a pair of nodes so that messages may be delivered in a timely manner.
            Multicasting is to send single copy of a packet to all of those of clients that requested it, and not to send multiple copies of a packet over the same portion of the network, nor to send packets to clients who don’t want it.
            The Adhoc Multicast Routing Protocol (AMRoute) presents a novel approach for robust IP Multicast in mobile ad-hoc networks by exploiting user-multicast trees and dynamic logical cores. It creates a bi-directional, shared tree for data distribution using only group senders and receivers as tree nodes. Unicast tunnels are used as tree links to connect neighbors on the User-multicast tree. Thus AMRoute does not need to be supported by network nodes that are not interested/capable of multicast, and group State Cost is incurred only by group senders and receivers. Also, the use of tunnels as tree links implies that tree structure does not need to change even in case of a dynamic network topology, which reduces the signaling traffic and packet loss. Thus AMRoute does not need to track network dynamics; the underlying Unicast protocol is solely responsible for this function.
AMRoute does not require a specific Unicast routing protocol; therefore, it can operate seamlessly over separate domains with different Unicast protocols. We have nges the current core node, so that the efficiency of the protocol can be improved. tried to overcome the transient loops in the mesh creation. Also we have implemented the Dynamic core migration technique by using a timer which periodically cha

                                                                                

81: Public Health Emergency Services
               
Vision
This project deals with develop Health Services Booking System. The system will providing ambulances and staff to deal with medical emergencies services.
Project Specification
This system can be used as an application for the Medical service centers to manage the ambulance information as well as the immediate responses for needed people. The system also maintains the information of Patients.
Functional Components
Community-Based Planning: 
Ambulance services must be represented in the planning processes at the local, state and federal level. 

Personnel Protection & Safety: 
All medics, including those who have the potential to respond in a mutual aid capacity, must have appropriate access to personal protective equipment, training, exercises and vaccines and antidotes.

The call center of Emergency Management and Research Institute took up the case and Geographical Information System (GIS) identified the exact location where the patient had collapsed.

When attending a call, the user check for the similar calls and search for the ambulance which is located to that area and ambulance is  staffed by:

ü  One driver
ü  One helper
ü  One experienced paramedic
ü  One trained medical officer, if required

In briefly the ambulance possesses all equipment standardized to enable a flawless transfer of patient during interruption of drug therapy or monitoring.
User InterfaceRequirements
Browser Based
Database Requirements
Centralized
Integration Requirements
Web/Pervasive enabled


Preferred Technologies


Solutions must be created using 
·         HTML, CSS (Web Presentation )
·         JavaScript (Client-side Scripting)
·         Java  (as programming language)
·         JDBC, JNDI, Servlets, JSP  (for creating web applications)
·         Eclipse with MyEclipse Plug-in (IDE/Workbench)
·         Oracle/Ms-Access
·         Windows XP/2003 or Linux/Solaris (Operating System)
·          Tomcat5.0.
Other Details
The application should be highly secured and with different levels & categories of access control.





































No comments:

Post a Comment