Using Packet Radio in Emergencies
How packet radio can assist in times of emergencies: a Proposal
Perhaps there is no better application for
packet radio than during emergency operations. This would include all
manner of software applications: APRS, the "classical" AX25 BBS'es,
the *NOS family of client/server platforms, FlexNet, FBB, etc. All can
play a part in establishing a communications network over a
disaster-stricken zone!
This article will attempt to descriptively
"paint a scene" in considerable detail about how digital radio communications
might adjunctively assist the authorized, government agencies with
their search and rescue efforts. Nothing extraordinarily new will be
put forward, just common sense practices that are well known and have
served faithfully in the past. However, it will try to show where packet
radio can add something above and beyond the usual level of voice radio
communications, such as: using email to send personal identification photos,
cartographic information, or photographic damage assessment. (Please see
"Related Topics" for Pine email links.)
And, taken together with this best-case
"scenario," will be embeded an implicit proposal which, it is hoped,
might be useful in formulating emergency management policies, mostly to
be considered by the Amateur Radio Community, i.e., ARES and RACES; but
perhaps, taken under advisement by government authorities as well.
|
A Packet Proposal...
So why use packet or digital (computer-assisted)
radio networks in times of emergency? Why not just use voice? While voice
modes are essential to any emergency operation, and packet radio might appear to
be a "luxury," there are several persuasive reasons to employ packet modes
despite what might be considered high overhead costs.
All are related to network-centric operations and will be elaborated
on in the following sections: continuous connectivity, expandable networks,
and analytical evaluation.
- Continous Connectivity
-
One thing that packet stations do very well is to
automatically stay in touch with each other. Beacons and beacon responses
are the usual means. Very often location information or station status
information can be included in the broadcast. GPS data can be sent in a
scheduled or synchronized broadcast, or at anytime. If this data is tied
into a local map, even monitoring operators, who are not familiar with the
local area, can immediately assist in dispatching meaningful directives
to operatives in the field.
Sometimes when a mobile station goes silent, this information can be of
value to those at command headquarters. This could indicate that some
accident or worse, has befallen an ERV, Emergency Rescue/Response Vehicle.
If a mobile station has failed to send a beacon broadcast in its alloted
time slot, an alert can be posted. Requests to a voice link may not be
fully reliable since personel are often busy with real life situations
that keep them from answering calls until the local emergency is over.
But a "ping" to a packet station will almost always come back if it is up
and on the air!
The background transmissions of mail traffic is another packet strength,
in fact, maybe one of its most salient. Once mail routes have been set up,
the mail handlers are relentless, grinding away until the mail gets through!
This acitivity continues regardless of other packet events in progress. So
while a station operator might be in a QSO "chat" situation, the mail
packets keep interjecting themselves into the transmissions as usual...
This concept of continuous connectivity is at the heart of any synchronized,
highly coordinated operation, whether the objective be civilian or military.
The benefits of knowing where everyone is at any point in time and space,
especially when the "battlefield" is always in a state of flux, can be
of great value to those responsible for the success of the outcome...
- Expandable Networks
-
One of the great strengths of TCP/IP and AX.25
based networks is its ability to grow the net in real time. For example,
most emergency operations would emanate from a central headquarters which
would have as its base a link to the internet. From this point outward,
connections could be made to mobile vehicles acting as central nodes in
the field. These links might be via satelite phone or radio gateway links
if reachable. These mobile, central stations, probably trucks, would
position themselves at the disaster's "edge" and hold these positions
until instructed otherwise. The working vehicles, probably vans, jeeps,
Hummers, or SUV'es, would be the ERV'es, Emergency Rescue Vehicles,
which could be either land or water based, or both. It is the ERVes'
mission to penetrate the disaster area reporting back to the mobile,
central stations which in turn would report back to headquarters.
The network structure as described above looks like the classical
hierarchial design with one point of origin branching out to many nodes which
in turn branch out to many more nodes until a tree-like structure and a
chain-of-command are established. And, this is true, with one important
exception. As the situation changes, the network can re-configure itself to
accomodate the communications needs of the operation. What began as a "pure"
hierarchial structure now has transformed itself into a network design. This
implies that new intervening nodes can "spring up" and join the net as
needed. This does not threaten the chain-of-command, but rather makes it
more adaptable and flexible based on the changing disaster conditions.
And because the network is expandable, other nodes which may not be
"officially" part of the operation could be used by the emergency net. For
example, many hams run packet stations and quite a few are adapting them
to run in emergency conditions. Whether manned or not, VHF stations could
be left running and available for use by the emergency nets, providing a
relay point in the network design. They would be an integral part of the net
until the batteries expired... If solar powered, they could remain in service
continuously during the daylight hours and possibly at night if
battery-charging capability were installed.
This concept of the expandable net does not always require that each
participant be equipted with voice radio or packet radio. Anyone with a
vehicle or boat could potentially join the "net" by finding a node
station (ERV) to check in with and give a report of the situation. So
even average volunteer citizens could offer help by simply taking a
litte extra time to rendezvous with their attached ERV and make a report
to a radio operator or packet operator. In other words, don't function as
a maverick, but rather as part of a networked team!
To boost inclusivity even further, perhaps temporary radio licenses could be
granted to organizations during times of emergencies. For example, most
people can operate a computer, or can be easily trained to do so. If that
person were a member of a volunteer organization, not necessarily ham radio,
they might be able to receive some basic training in regard to packet
operations, enabling them to run an emergency station on an ERV in times of
emergency only. This might vastly increase the number of station operators
to man the net. When the crisis is over, these operators would no longer be
authorized to work packet stations. (However, they could be encouraged to
obtain radio licenses through their "parent" organizations for emergency
preparedness...
The concluding point here, and one we often forget, is that networks are
made up of people! The technology pales in the shadow of disaster.
It should be there in its enabling role, but not acting as an abstruction
to the willingness of people to join together and communicate in times
of emergency!
- Analytical Evaluation
-
Since packet radio is intimately tied together
with computer technology, a paper trail or snap-shot of any sequence of
events may be captured and scrutinized at some later time. Imagine trying
to tape record all the voice conversations, which could perhaps be done
but certainly not easily. With packet all the events are stored on a hard
drive somewhere!
Recently, Ham radio emergency preparedness groups such as ARES and RACES
have moved toward including a packet component in their emergency operations
just for these very reasons: that all the events may be analyzed and
performance evaluated so that corrections may be made in future. With this
data, a nearly complete simulation of the rescue operation could be
reconstructed, not only visually but also statistically . These results
could point to the areas that need work or that perhaps failed altogether.
While no one likes to see where they "goofed," this information is
extraordinarily valuable to planners and emergencies coordinators!
- Conclusions...
-
This "imaginary" scenario of an ideal emergency
net has been meant to inspire you and get you thinking about the many ways
that communication technologies and people can work together. Many of the
"pesky" details have been glossed over, since perhaps their solutions are
still "dancing about" in someone's head! The basic plea is for
coordination, integration, and cooperation...
Sound familiar? :) (Nothing radically new has been proposed here, just
common sense application of what is already known to have worked in the
past, only perhaps at a higher level of integration.)
I am hoping this will inspire you to take action and fill in some of the
missing pieces of which there are always many. If we work together, there
is almost nothing that cannot be overcome...
(For a more generalized discussion about the current status of packet radio
and why it should be used in times of disaster, please see
The Status of Packet Radio. To view an index page for general
emergency-related information, please see
Emergency Communications and Informational Resources.)
(Courtesy KBNorton Computer Services)
|