WO2008027750A2

WO2008027750A2 - First responder ad-hoc communications

Info

Publication number: WO2008027750A2
Application number: PCT/US2007/076375
Authority: WO
Inventors: Brian K. Daly; Dewayne A. Sennett
Original assignee: At & T Mobility Ii Llc
Priority date: 2006-08-29
Filing date: 2007-08-21
Publication date: 2008-03-06
Also published as: WO2008027750A4; WO2008027750A3

Abstract

A system that facilitates ad-hoc communications of first responder (FR) wireless communications devices at an emergency location. The system includes FR devices that need to communicate with an emergency command center. Due to location at the event scene, the first FR device is incapable of direct wireless communications with a remote system. Accordingly, a wireless communications pathway facilitates the communications between the first FR device and the remote system. The wireless communications pathway comprises at least one of a PAN, a local IP network and a wireless macro network. The wireless communications pathway authenticates both the first FR device and the user via parameter data transmitted from the first FR device and facilitates communications using a device association protocol. Once a wireless communications pathway is established between the first FR device and the remote system, communications are then relayed from the first FR device to the remote system.

Description

Title: FIRST RESPONDER AD-HOC COMMUNICATIONS

BACKGROUND

[0001] First responders are organizations and personnel that provide law enforcement, safety and protection services to the public. The first responders include law enforcement officers such as police, sheriff, highway patrol, detectives, special law enforcement, FBI, DEA, military personnel, border patrol, and others. First responders also include fire and safety personnel, for example, firefighters, emergency medical services personnel, Red Cross personnel, and other emergency workers.

[0002] The communications systems and associated command and control capabilities used by first responders in responding to an incident or other emergency are typically limited to traditional radio communications. As a result, depending on the location of the various different groups of personnel that respond to emergency incidents, the first responders may be unable to communicate with each other. When location does not permit radio communication, groups of first responders who need to communicate with each other at an incident typically use "runners" to relay information. In some cases, inter-agency communications may occur by relaying information through the respective dispatch centers. However, this is a very slow and inefficient way of communicating. Thus, some groups of first responders may elect to just perform their respective tasks and operate without any type of unified communication or operation.

[0003] However, the lack of inter-operable communications between on-scene agencies can result in ineffective coordination, often with tragic results. Further, the lack of communications capability may cause inadequate situational awareness among the first responder personnel and among various first responder teams because there is no way to know the location of the various first responders at the incident scene without constant monitoring of voice communications. Integral to the lack of situational awareness at an incident site is the lack of an accurate system for maintaining accountability of the first responders at an incident site. The typical methods used to maintain accountability of first response personnel are manual methods, wherein some physical means is used for identifying whether a responder is present at the incident scene, and in some cases to identify where the responder is assigned during the emergency. Because these methods are manual, they do not provide a way to accurately account for all first responder personnel at an incident site, nor do they provide ways to track the actual location or movement of first responder personnel around the incident site as the emergency unfolds. Consequently, the incident command personnel do not have detailed information on the location of the first responders and can lose accountability of first responders. [0004] Furthermore, during catastrophic events such as September 11^th,

Hurricane Katrina and major building fires, first responders deep within the interiors of buildings and other structures where traditional radio communications may fail, may need to communicate emergency information to an emergency command center, a hospital, a mobile command post or other such location. For example, emergency information such as vital patient health information of trapped individuals may need to be transmitted to a hospital. Alternatively, first responders may need to collect information on a continuous basis from select sites within the area of the event without having to allocate or risk the safety of the first responders. This type of emergency information would typically be provided by some type of sensor devices, which may also be in a location where traditional radio communications would fail. Accordingly, it is necessary to provide first responders with an accurate way of communicating emergency information to emergency command centers and other first responders.

[0005] The lack of adequate means to communicate emergency information and intelligence information at incident sites results in incident commanders and first responder personnel that lack the detailed information and situational awareness of the incident scene to effectively respond to an emergency. The cascading effect typically results in slower response times to emergencies and a much higher level of risk for the first responders and incident victims.

SUMMARY

[0006] The following presents a simplified summary in order to provide a basic understanding of some aspects of the claimed subject matter. This summary is not an extensive overview, and it is not intended to identify key/critical elements of the claimed subject matter or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0007] Disclosed herein are systems, methods, apparatuses, and articles of manufacture that facilitate ad-hoc communications of first responder (FR) wireless communications devices at an emergency location. In more detail, it may be desirable to provide FR devices with an accurate system for transmitting emergency information to an emergency command center, hospital or other remote system where traditional radio communications would fail. Conventionally, however, there has been no implementation of a system or method to accurately undertake such action, especially during catastrophic events where first responder communication interoperability was a major problem.

[0008] In accordance with one aspect described herein, intermediate FR devices establish communications between the first FR device and a remote system. Specifically, the first FR device, incapable of direct communications with a remote system, initiates direct communications with an intermediate FR device using a device association protocol. The first FR device instructs the intermediate FR device that it needs to communicate with the remote system and cannot establish a direct communication path, and thus requests an available communication path to the remote system. The intermediate FR device authenticates the identity of both the first FR device and the user. The intermediate FR device initiates direct communications with the remote system and then instructs the remote system that communication traffic is pending from the first FR device. The first FR device then begins communications to the remote system via relaying information through the intermediate FR device(s). Accordingly, the emergency information can be transmitted to the intended location no matter the location of the first responder at the event scene. [0009] In another example, a local internet protocol (IP) network establishes communications between the first FR device and the remote system. Specifically, the first FR device, incapable of direct communications with a remote system, initiates direct communications with the local IP network using the device association protocol and requests an available communication path to the remote system via the IP network. The IP network authenticates the identity of both the first FR device and the user. The IP network then initiates direct communications with the remote system via the device association protocol and instructs the remote system that communication traffic is pending from the first FR device. The first FR device then begins communications to the remote system via relaying information through the IP network.

[0010] In another aspect described in greater detail herein, a macro wireless network establishes communications between the first FR device and the remote system. Specifically, the first FR device, incapable of direct communications with a remote system, initiates direct communications with an intermediate FR device using the device association protocol and requests an available communication path to the remote system. The intermediate FR device authenticates the identity of both the first FR device and the user. The intermediate FR device is also incapable of direct communications with the remote system, and so initiates direct communications with the macro wireless network via radio infrastructure. The intermediate FR device, using the device association protocol, requests an available communication path to the remote system via the macro wireless network. The macro wireless network initiates direct communications with the remote system via the device association protocol and instructs the remote system that communication traffic is pending from the first FR device. The first FR device then begins communications to the remote system via relaying information through the intermediate FR device and the macro wireless network.

[0011] To the accomplishment of the foregoing and related ends, certain illustrative aspects are described herein in connection with the following description and the annexed drawings. These aspects are indicative, however, of but a few of the various ways in which the principles disclosed herein can be employed and is intended to include all such aspects and their equivalents. Other advantages and novel features will become apparent from the following detailed description when considered in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] FIG. 1 illustrates a system that facilitates ad-hoc communications of first responder (FR) wireless communications devices at an emergency location. [0013] FIG. 2 illustrates the communications system, wherein intermediate devices establish communications between the first FR device and a remote system. [0014] FIG. 3 illustrates the communications system, wherein an IP network establishes communications between the first FR device and the remote system. [0015] FIG. 4 illustrates the communications system, wherein a macro wireless network establishes communications between the first FR device and the remote system.

[0016] FIG. 5 illustrates a communications system that facilitates ad-hoc communications of sensor information via a first FR device at an emergency location.

[0017] FIG. 6 is a flow diagram that is representative of a methodology for a communication system.

[0018] FIG. 7 is a flow diagram that is representative of a methodology for the communication system, wherein an IP network establishes communications between the first FR device and an emergency command center.

[0019] FIG. 8 is a flow diagram that is representative of a methodology for the communication system, wherein a macro wireless network establishes communications between the first FR device and the emergency command center.

[0020] FIG. 9 is a flow diagram that is representative of a methodology for the communication system, wherein sensors transmit information to a first FR device which routes the information to the emergency command center.

[0021] FIG. 10 illustrates a system for facilitating an interconnection network of communications on an ad-hoc basis among FR devices and external communication network.

[0022] FIG. 11 is an exemplary portable wireless device (PWD) for use with the communication system.

[0023] FIG. 12 is an exemplary networking environment for use with the communication system.

DETAILED DESCRIPTION

[0024] The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident, however, that such matter can be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the claimed subject matter. [0025] As used in this application, the terms "component" and "system" are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component can be, but is not limited to being, a process running on a processor, a processor, a hard disk drive, multiple storage drives (of optical and/or magnetic storage medium), an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a server and the server can be a component. One or more components can reside within a process and/or thread of execution, and a component can be localized on one computer and/or distributed between two or more computers.

[0026] Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computing device, such as a mobile handset, to implement the disclosed subject matter. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips...), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)...), smart cards, and flash memory devices (e.g., card, stick, key drive...). Additionally it should be appreciated that a carrier wave can be employed to carry computer-readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN). Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter. Moreover, the word "exemplary" is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. [0027] The ad-hoc communications system works with standard personal area networks (PAN), local IP, and macro networks to provide first responders with communication interoperability despite their location at an incident site. Generally, a first FR wireless communications device of an ad-hoc network requests communication with a mobile command post (MCP), emergency command center (ECC), hospital, or the like. The first FR device is incapable of direct wireless communications with the mobile command post and utilizes a wireless communications pathway to facilitate communications. The wireless communications pathway facilitates communications between the first FR device and the mobile command post using a device association protocol. Once communications are established, the first FR device can relay emergency information to the mobile command post via the wireless communications pathway. [0028] Turning now to the drawings, FIG. 1 illustrates a system 100 that facilitates ad-hoc communications of a first responder (FR) wireless communications device 102 at an emergency location. The FR devices can provide at least one of voice services {e.g., voice-over-IP (VoIP)), push-to-talk type voice services, streaming video services, file transfers or other types of data services {e.g., pictures, text, telemedicine, sensory data, Chemical Biological Radiological Nuclear Explosive (CBRNE) data). It is thus to be understood that any suitable voice services, video services and/or data transfer services for wireless communications devices are contemplated and intended to fall under the scope of the hereto-appended claims. The communication devices of the first responders have the abilities to communicate with the public macro wireless network {e.g., the cellular network), as well as a personal, local or wide-area network communications method {e.g., wireless personal area network (WPAN), wireless local area network (WLAN), wireless wide area network/metropolitan area network (WW AN/MAN), Bluetooth, ultra-wideband (UWB), P-25 radio, family radio service (FRS), general mobile radio service (GMRS), multi-use radio service (MURS)).

[0029] The first FR device 102 of system 100 requests communications with a remote system 106. The remote system is typically a mobile or stationary structure proximate to the incident site. The remote system can be a structure that was in existence before the incident occurred or it can be part of a temporary structure which was constructed after the incident occurred. For instance, the remote system can be part of an ECC, MCP, a hospital or any other suitable structure. Due to location at the event scene, the first FR device 102 is incapable of direct wireless communications with the remote system 106. Accordingly, a wireless communications pathway 104 facilitates the communications between the first FR device 102 and the remote system 106. In more detail, the pathway 104 facilitates communications between the first FR device 102 and the remote system 106 via a device association protocol. [0030] The device association protocol is a communications protocol configured to enable the reliable interchange of audio, text and/or video data over the imperfect communication channel(s) of the first responders. Data transferred via the device association protocol includes authentication information or parameter data. This data is used to authenticate the first FR device and a user of the first FR device. Encryption data, geographic data, device identification data, user identification data and biometric data can also be transferred via the device association protocol to an intermediate FR device or network. Once the wireless communications pathway 104 is established, the pathway 104 authenticates both the first FR device 102 and its user via the parameter data transmitted from the first FR device 102 and facilitates communications using the device association protocol.

[0031] Furthermore, once authentication is complete between the first FR device 102 and the remote system 106, data is then relayed from the first FR device 102 to the remote system 106. The data is IP packet-based, and is thus relayed in the form of IP packets to the remote system 106 via the wireless communications pathway 104. The IP packets are then reassembled into an audio/text stream upon reaching the remote system 106. Specifically, the remote system 106 would reassemble the packets of the audio stream that are addressed to this specific system. Typically, packets addressed to other wireless devices/systems would not be included in the audio stream even if this system is serving as a relay point between other FR devices. Thus, the wireless communications pathway 104 acts as an IP router to relay information in the form of IP packets from the first FR device 102 to the remote system 106, to be reassembled upon arrival.

[0032] Additionally, the wireless communications pathway 104 comprises at least one of a public macro wireless network {e.g., a cellular network), a personal IP network, a local IP network implemented at the emergency location, a wide-area network (e.g., WPAN, WLAN, WWAN/MAN, Bluetooth, UWB, P-25 radio, FRS, GMRS, MURS) and radio infrastructure for connecting an FR device to the macro network and on to the emergency command center.

[0033] To better illustrate operability of the system 100, a detailed example

200 of one particular utilization of such system 100 is provided herein. This example 200, however, is intended to aid in understanding of the system 100 and is not intended to limit use or operability of such system 100. Specifically, FIG. 2 illustrates the system 200 wherein intermediate FR devices 204 and 208 establish communications between the first FR device 202 and the remote system 206. Specifically, the first FR device 202, incapable of direct communications with a remote system 206, initiates direct communications with a second FR device 204 using the device association protocol. The first FR device 202 instructs the second FR device 204 that it needs to communicate with the remote system 206 and cannot establish a direct communication path, and thus requests an available communication path to the remote system 206.

[0034] The first FR device 202 also sends its corresponding parameter data to the second FR device 204. The parameter data comprises data related to at least one of encryption information, geographic location, device identification, user identification and authentication information. The second FR device 204 uses the parameter data to validate the identity of both the first FR device 202 and the user. The second FR device 204 then acknowledges the communication request from the first FR device 202 and indicates that the second FR device 204 is looking for an available communication path to the remote system 206. The second FR device 204 is also incapable of direct communications with the remote system 206, and so initiates direct communications with a third FR device 208 via the device association protocol.

[0035] The second FR device 204 queries the third FR device 208 as to whether it can communicate with the remote system 206. Upon confirmation, the second FR device 204 establishes a communication path to the third FR device 208. The third FR device 208 then authenticates the first FR device 202 and the user based on the parameter data transmitted from the second FR device 204. The third FR device 208 is capable of direct communications with the remote system 206, and thus initiates direct communications with the remote system 206. [0036] Once communications with the remote system 206 have been established, the third FR device 208 instructs the remote system 206 that communication traffic is pending from the first FR device 202. The remote system 206 then authenticates the first FR device 202 and the user based on the parameter data transmitted from the third FR device 208 and sends acknowledgement to the third FR device 208. The third FR device 208 sends acknowledgement to the second FR device 204. The second FR device 204 then sends acknowledgement to the first FR device 202 and informs the first FR device 202 that a communication path to the remote system has been established.

[0037] The first FR device 202 then begins communications to the remote system 206 via relaying information through the intermediate FR devices 204 and 208. As stated supra, the information is relayed in the form of IP packets, with the intermediate FR devices 204 and 208 acting as IP routers to relay the information from the first FR device 202 to the remote system 206. Additionally, the intermediate FR devices 204 and 208 would include relay and repeater capabilities that allow the intermediate FR devices to boost or repeat the received signal from the first FR device 202 and transmit or relay the signals to the remote system 206. [0038] In operation, these communications between the first FR device 202 and the remote system 206 via the intermediate FR devices 204 and 208 are IP based. Depending upon implementations in the FR devices and the congestion algorithms in the IP networks, it is possible for multiple communication sessions to be relayed by intermediate FR devices 204 and 208. It can also be an implementation choice that the second FR device 204 is limited to only relaying one communication session on a first served basis or based upon priority. For example, the relaying device (the second FR device 204) can give the first FR device 202 priority over another FR device or over wireless sensors trying to transmit sensor data.

[0039] To better illustrate operability of the system 100, another detailed example 300 of the system 100 is provided herein. As shown in FIG 3, a local IP network 304 establishes communications between the first FR device 302 and the remote system 306. Specifically, the first FR device 302, incapable of direct communications with a remote system 306, initiates direct communications with the local IP network 304 using the device association protocol and requests an available communication path to the remote system 306. The first FR device 302 also sends its corresponding parameter data to the IP network 304. The IP network 304 uses the parameter data to validate the identity of both the first FR device 302 and the user. The IP network 304 then acknowledges the communication request from the first FR device 302 and initiates direct communications with the remote system 306 via the device association protocol. [0040] The IP network 304 instructs the remote system 306 that communication traffic is pending from the first FR device 302. The remote system 306 then authenticates the first FR device 302 and the user based on the parameter data transmitted from the IP network 304 and sends acknowledgement to the IP network 304. The IP network 304 sends an acknowledgement to the first FR device 302 and signals the first FR device 302 that a communication path to the remote system 306 has been established. The first FR device 302 then initiates communications to the remote system 306 via relaying information through the IP network 304. Accordingly, the IP network 304 acts as an IP router to relay the information from the first FR device 302 to the remote system 306. [0041] The IP network 304 can be any type of ad-hoc IP network, such as a mesh network, a wireless fidelity (WiFi) network, or any other local ad-hoc IP network established at the scene of the emergency. It is thus to be understood that any suitable ad-hoc IP network is contemplated and intended to fall under the scope of the hereto-appended claims.

[0042] Furthermore, the implementation choice of which network the first FR device 302 contacts can be determined at the scene. For example, a first responder utilizing the first FR device 302, is located nearest to a mesh network set-up at the scene, and thus would initiate communications with the mesh network when attempting to communicate with a remote system out of the first FR device's range. Whereas, another first responder utilizing a second FR device is located nearest to a Wi-Fi network, and thus would initiate communications with the Wi-Fi network when attempting to communicate with a remote system out of range of the second FR device. Accordingly, implementation choice is based on proximity of the first responder to a particular IP network due to the first responder' s location at the incident (or emergency) site.

[0043] To better illustrate operability of the system 100, another detailed example 400 of system 100 is provided herein. As shown in FIG 4, a macro wireless network 410 establishes communications between the first FR device 402 and the remote system 406. Specifically, the first FR device 402, incapable of direct communications with a remote system 406 {e.g., the ECC, MCP), initiates direct communications with a second FR device 404 using the device association protocol and requests an available communication path to the remote system 406. The second FR device 404 is reachable by the first FR device 402 via direct radio communications over the personal, local or wide-area network communications method.

[0044] The first FR device 402 instructs the second FR device 404 that it needs to communicate with the remote system 406 and cannot establish a direct communications pathway. The first FR device 402 also sends its corresponding parameter data to the second FR device 404. The second FR device 404 uses the parameter data to validate the identity of one or both of the first FR device 402 and the user. The second FR device 404 is also incapable of direct communications with the remote system 406, but is capable of direct communications with a macro wireless network 410.

[0045] The second FR device 404 initiates direct communications with the macro wireless network 410 via a radio infrastructure 408. Specifically, the second FR device 404 initiates connection with the radio infrastructure 408, which in turn connects to the macro wireless network 410. The second FR device 404 queries the macro wireless network 410, via the device association protocol, to determine if the macro network 410 can communicate with the remote system 406. After confirmation, the second FR device 404 establishes a communication path to the macro wireless network 410 via the device association protocol. The macro wireless network 410 then uses the parameter data sent from the second FR device 404 to validate the identity of both the first FR device 402 and the user. [0046] The macro wireless network 410 then acknowledges the communication request from the second FR device 404 and initiates direct communications with the remote system 406 via the device association protocol. The macro wireless network 410 instructs the remote system 406 that communication traffic is pending from the first FR device 402. The remote system 406 then authenticates the first FR device 402 and the user based on the parameter data transmitted from the macro wireless network 410 and sends acknowledgement to the macro wireless network 410. The macro wireless network 410 sends acknowledgement to the second FR device 404. The second FR device 404 sends acknowledgement to the first FR device 402 and informs the first FR device 402 that a communication path to the remote system 406 has been established. [0047] Once the communication path has been established, the first FR device

402 commences communications to the remote system 406 via relaying information through the intermediate second FR device 404 and the macro wireless network 410. Accordingly, the second FR device 404 and the macro wireless network 410 act as IP routers to relay the information from the first FR device 402 to the remote system 406.

[0048] FIG. 5 illustrates a system 500 that facilitates ad-hoc communications of sensor information via a first FR device 502 at an emergency location. In one implementation, the sensors 508 are separate, independent devices from the first FR device 502. The sensors 508 can be placed at strategic locations around the event site or connected to patients/victims for vital telemedicine information. However, in an alternative implementation, one or more of the sensors 508 can also be integrated directly within the first FR device 502 as one congruent structure. [0049] Furthermore, the sensors 508 are in direct connection with the first FR device 502 either via wireless connectivity (e.g., Bluetooth network or WLAN) or are physically tethered to the first FR device 502 (e.g., serial communications technology). The sensors provide sensed information from sensor locations to the first FR device for communications to a desired location, such as the remote system 506. The sensed information comprises, but is not limited to, telemedicine data, blood pressure data, biochemical data, environmental data, images, cardiac data, and /or CBRNE data.

[0050] It is desired that sensor data of the sensors 508 of FIG. 5 be transmitted to the remote system 506, but direct communications of the sensor data to the remote system 506 is extremely unreliable or impossible. The sensors 508 are also unable to connect directly to either the macro wireless network or to the IP network that has been established on site (e.g., from the mobile command post). As stated supra, the sensors 508 provide information into the first FR device 502 either by hard wire or by wireless PAN connection. Accordingly, the sensors 508 transmit the sensed information to the first FR device 502 of system 500. The first FR device 502 then requests communications with the remote system 506 to deliver the sensed information from the sensors 508.

[0051] Due to location at the event scene, the first FR device 502 is also incapable of direct wireless communications with the remote system 506. Accordingly, a wireless communications pathway 504 facilitates the communications between the first FR device 502 and the remote system 506. The wireless communications pathway 504 authenticates the first FR device 502 and the user, as well as the associated sensors via parameter data transmitted from the first FR device 502 and facilitates communications using a device association protocol. The sensors are authenticated to prevent unauthorized sensors being placed on the network by individuals of malicious intent. Once a wireless communications pathway 504 is established between the first FR device 502 and the remote system 506, sensory information is then relayed from the first FR device 502 to the remote system 506 {e.g., hospital, ECC, or MCP).

[0052] Generally, the wireless communications pathway 504 can comprise any of the communication paths previously defined in FIGs. 2-4 including the relay/repeater functionalities. Specifically, the first FR device 502 can relay the sensory information to intermediate FR devices to reach the remote system 506. Alternatively, the first FR device 502 can utilize an IP network or macro wireless network to communicate with the remote system 506. Further, the first FR device 502 can be capable of communicating with a combination of networks, such as a public macro wireless network and a wide-area network. In general, the wireless communications pathway 504 can comprise at least one of a public macro wireless network {e.g., a cellular network), a personal IP network, a local IP network implemented at the emergency location, a wide-area network {e.g., WPAN, WLAN, WWAN, MAN, Bluetooth, UWB, P-25 radio, FRS, GMRS, MURS) and radio infrastructure for connecting an FR device to the macro network and on to the emergency command center.

[0053] Referring to FIGs. 6-9, methodologies in accordance with various aspects of the claimed subject matter are illustrated. While, for purposes of simplicity of explanation, the methodologies are shown and described as a series of acts, it is to be understood and appreciated that the claimed subject matter is not limited by the order of acts, as some acts may occur in different orders and/or concurrently with other acts from that shown and described herein. For example, those skilled in the art will understand and appreciate that a methodology can alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all illustrated acts may be required to implement a methodology in accordance with the claimed subject matter. Additionally, it should be further appreciated that the methodologies disclosed hereinafter and throughout this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methodologies to computers. The term article of manufacture, as used herein, is intended to encompass a computer program accessible from any computer-readable device, carrier, or media.

[0054] Turning specifically to FIG. 6, a methodology 600 of facilitating ad- hoc communications for FR communications devices at an emergency location is illustrated. The methodology 600 starts at 602, and at 604 a first FR device is received. The first FR device is used for communicating emergency services information at the emergency location. The first FR device needs to contact an emergency command center (ECC) to communicate the emergency services information, but is unable to establish direct communications with the ECC due to location at the event scene.

[0055] Accordingly, the first FR device initiates communications with a nearby device which is reachable with direct radio communications over the personal, local or wide-area network communications method via a device association protocol. At 606, the first FR device requests an available communications path to the ECC via the intermediate FR device. The first FR device then sends parameter data to the intermediate FR device for authentication. At 608, the intermediate FR device receives the parameter data and uses the data to authenticate both the first FR device and the user. The intermediate FR device then sends acknowledgement to the first FR device.

[0056] The methodology 600 then proceeds to 610, where it is determined if the first intermediate FR device can establish direct communications with the ECC. If direct communications with the ECC can be established, then at 612 the first intermediate FR device initiates communications with the ECC. The first intermediate FR device instructs the ECC that traffic is pending from the first FR device. At 614, the ECC authenticates the first FR device and the user based on parameter data received from the first intermediate FR device. At 616, the first FR device relays emergency information to the ECC through the first intermediate FR device.

[0057] If direct communications with the ECC cannot be established by the first intermediate FR device, then at 618 the first intermediate FR device initiates communications with a subsequent intermediate FR device via the device association protocol. The subsequent intermediate FR device authenticates the first FR device and its user via the parameter data forwarded from the first intermediate FR device and acknowledges whether or not the second intermediate FR device can establish direct communications with the ECC. If direct communications cannot be established, the subsequent or second intermediate FR device initiates communications with a third intermediate FR device and a fourth intermediate FR device, etc., until direct communications with the ECC can be reached. [0058] If the second intermediate FR device can establish direct communications with the ECC, then at 612 the second intermediate FR device initiates direct communications with the ECC. At 614, the ECC authenticates the first FR device and its user based on parameter data received from the second intermediate FR device. Finally, at 616, the first FR device relays the emergency information to the ECC through the intermediate devices. The methodology 600 stops at 620. [0059] Furthermore, the intermediate FR devices include relay and repeater capability to boost and transmit the signals to various networks, the ECC and/or other intermediate FR devices. The emergency information communicated between the first FR device and the ECC includes at least one of voice data, text data, voice services, PTT voice services, streaming video services, file transfer services, and local data sensed by the first FR device at a current location of the first FR device. [0060] Now turning to FIG. 7, a methodology 700 of facilitating ad-hoc communications for FR communications devices at an emergency location utilizing an IP network is illustrated. The methodology 700 starts at 702, and at 704 a first FR device is received. The first FR device needs to contact the ECC to communicate emergency services information, but is unable to establish direct communications with the ECC due to location at the event scene. Accordingly, the first FR device initiates communications with an IP network that was established at the scene of the incident. The IP network can be any kind of ad-hoc IP network, such as a mesh network, a Wi-Fi network, or any other ad-hoc IP network established at the scene of the emergency. Furthermore, implementation choice of the type of IP network contacted by the first FR device can be determined at the scene. [0061] At 706, the first FR device utilizes a device association protocol to request an available communications path to the ECC via the IP network. The first FR device then sends parameter data to the IP network for authentication. At 708, the IP network receives the parameter data and uses the data to authenticate both the first FR device and the user. The methodology 700 then proceeds to 710, where the IP network initiates communications with the ECC. The IP network instructs the ECC that traffic is pending from the first FR device. At 712, the ECC authenticates the first FR device and its user based on parameter data received from the IP network. [0062] At 714, communications are established between the first FR device and the ECC. The IP network then sends acknowledgement to the first FR device that communications have been established with the ECC. At 716, the first FR device relays emergency information to the ECC through the IP network. The methodology 700 stops at 718. As stated supra, the emergency information communicated between the first FR device and the ECC includes at least one of voice data, text data, voice services, PTT voice services, streaming video services, file transfer services, and local data sensed by the first FR device at a current location of the first FR device. [0063] Now turning to FIG. 8, a methodology 800 of facilitating ad-hoc communications for FR communications devices at an emergency location utilizing a wireless macro network is illustrated. The methodology 800 starts at 802, and at 804 a first FR device is received. The first FR device needs to contact the ECC to communicate emergency services information, but is unable to establish direct communications with the ECC due to location at the event scene. Accordingly, the first FR device initiates communications with a nearby intermediate FR device(s) which is reachable with direct radio communications over the personal, local or wide- area network communications method via a device association protocol. At 806, the first FR device requests an available communications path to the ECC via the intermediate FR device.

[0064] The first FR device then sends parameter data to the intermediate FR device for authentication. At 808, the intermediate FR device receives the parameter data and uses the data to authenticate both the first FR device and the user. However, the intermediate FR device is also unable to establish direct communications with the ECC. The intermediate FR device can communicate with a macro wireless network via radio infrastructure. The intermediate FR device connects to the radio infrastructure, and the radio infrastructure connects to the macro wireless network. The macro wireless network can be any kind of public wireless network {e.g., cellular network) or public safety network or a city wide WiFi, WLAN, WiMax network. [0065] At 810, the intermediate FR device initiates a device association protocol on the macro wireless network requesting an available communications path to the ECC. The intermediate FR device then sends parameter data to the macro wireless network for authentication. At 812, the macro wireless network receives the parameter data and uses the data to authenticate both the first FR device and the user. The methodology 800 then proceeds to 814, where the macro wireless network initiates communications with the ECC. The macro wireless network instructs the ECC that traffic is pending from the first FR device. At 816, the ECC authenticates the first FR device and the user based on parameter data received from the macro wireless network.

[0066] At 818, communications are established between the first FR device and the ECC. The macro wireless network then sends acknowledgement to the first FR device. At 820, the first FR device relays emergency information to the ECC through the intermediate FR device and macro wireless network. The methodology 800 stops at 822. Furthermore, the intermediate FR device(s) include relay and repeater capability to repeat and relay the signals to the ECC, the macro wireless network and/or other intermediate FR devices.

[0067] Turning specifically to FIG. 9, a methodology 900 of facilitating ad- hoc communications for FR communications devices at an emergency location utilizing sensors is illustrated. The methodology 900 starts at 902, and at 904 at least one sensor is received. The sensors can be placed at strategic locations around the event site or are connected to patients/victims for telemedicine information. The sensors provide sensed information from a first FR device to a desired location, such as the ECC. The sensors of the first FR device can be independent structures, separate from the first FR device or integrated within the first FR device as one congruent structure, for example. The sensors are in direct connection with the first FR device via wireless connectivity {e.g. , Bluetooth network or W-LAN) or tethered to the first FR device (e.g., serial communications technology). The sensors need to transmit sensed information to the ECC, but are unable to directly communicate with the ECC. The sensors are also unable to communicate directly with either the macro wireless network or the IP network that has been established on site (e.g., from mobile command post). [0068] At 906, the sensors transmit the sensed information to the first FR device via hard wire or wireless PAN connection. The first FR device needs to contact the ECC to communicate the sensed or emergency information collected from the sensors. However, due to location at the incident site, the first FR device is unable to establish direct communications with the ECC. Accordingly, the first FR device initiates communications with a nearby device which is reachable with direct radio communications over the personal, local or wide-area network communications method via a device association protocol.

[0069] At 908, the first FR device requests an available communications path to the ECC via the intermediate FR device. The first FR device then sends parameter data to the intermediate FR device for authentication. At 910, the intermediate FR device receives the parameter data and uses the data to authenticate the first FR device, the user and the associated sensor information. The intermediate FR device then sends acknowledgement to the first FR device.

[0070] The methodology 900 then proceeds to 912, where the intermediate FR device initiates communications with the ECC. The intermediate FR device instructs the ECC that traffic is pending from the first FR device. At 914, the ECC authenticates the first FR device, the user and the associated sensor information based on parameter data received from the intermediate FR device. At 916, the first FR device relays emergency information from the sensors to the ECC through the intermediate FR device. The methodology 900 stops at 918. [0071] If direct communications with the ECC cannot be established by the intermediate FR device, then the intermediate FR device can initiate communications with subsequent intermediate FR device(s) via the device association protocol until communications with the ECC can be established. Further, the intermediate FR devices include relay and repeater capabilities to boost and transmit the signals to various networks, the ECC and/or other intermediate FR devices. The sensor information communicated between the first FR device and the ECC comprises, but is not limited to, at least one of telemedicine data, blood pressure data, biochemical data, environmental data, images, cardiac data, and CBRNE data. [0072] Referring now to FIG. 10, there is illustrated a system 1000 for providing an interconnection network of communications, on an ad-hoc basis, among the FR devices and between the ad-hoc network of devices and external communication networks. FR devices 1002, 1004, 1006, 1008 and 1010 are the communication devices of the first responders. The FR devices 1002-1010 have the ability to communicate with the public macro wireless network (e.g., the cellular network) as well as a personal, local or wide-area network communications method (e.g., WPAN, WLAN, WWAN₅MAN, Bluetooth, UWB, P-25 radio, FRS, GMRS, MURS). The FR devices 1002-1010 can also provide voice services (e.g., VoIP), push-to-talk type voice services, streaming video services, file transfers, other types of data services (e.g., pictures, text, telemedicine, sensory data, CBRNE data) and relay/repeater capability.

[0073] Sensors 1018 are sensor type devices such as blood pressure monitors, biochemical sensors, weather stations, cameras, and EKG. As shown in FIG. 10, the sensors 1018 communicate directly with FR device 1010 (or any other suitable sensor subsystem that provides communications with the FR device 1010) to transmit sensory information to a remote system (e.g., emergency command center, hospital, and mobile command post). However, the sensors 1018 can be capable of direct communications with other FR devices as well. The sensors 1018 are incapable of direct communications with the macro wireless network 1014, local IP network 1012 and the remote system. Accordingly, the sensors 1018 utilize their communications with the FR devices 1002-1010 to transmit the sensory information to an intended location, such as the remote system.

[0074] Furthermore, the system 1000 can include IP network 1012 and macro wireless network 1014. The IP network 1012 is a local IP based network at the disaster scene (e.g., at a mobile command post, fire engine, communications van). Macro wireless network 1014 is the public wireless network (e.g., cellular network) or public safety network or a city wide WiFI, WLAN, WiMax network. Tower 1016 represents the radio infrastructure used to connect to the macro wireless network 1014. Typically, the FR devices 1002-1010 need to communicate emergency information to the remote system, but due to location at the event scene, are unable to establish direct communications with the remote system. Accordingly, FR devices 1002-1010 can utilize any of the above-described processes as shown in FIGS. 1-9 to deliver the emergency information to the remote system.

[0075] Referring now to FIG. 11, there is illustrated a detailed schematic block diagram of portable wireless device (PWD) 1100 (e.g., mobile handset, push-to-talk handset, FR device) that operates in accordance with the subject invention. The PWD 1100 includes a processor 1102 for controlling and processing all onboard operations and functions. A memory 1104 interfaces to the processor 1102 for storage of data and one or more applications 1106 (e.g., a video player software, user feedback component software, etc.). The applications can include the client that provides estimation execution of a task for characterizing the local mobile environment and then transmitting the characterization data to the base station. Other applications can include voice recognition of predetermined voice commands that facilitate initiation of the user feedback signal.

[0076] The applications 1106 can be stored in the memory 1104 and/or in a firmware 1108, and executed by the processor 1102 from either or both the memory 1104 or/and the firmware 1108. The firmware 1108 also stores startup code for execution in initializing the handset 1100. A communications component 1110 interfaces to the processor 1102 to facilitate wired/wireless communications with external systems, e.g., cellular networks, VoIP networks, and so on. The handset 1100 includes devices such as a cellular telephone, a PDA with mobile communications capabilities, and messaging-centric devices. [0077] The handset 1100 includes a display 1112 for displaying text, images, video, telephony functions (e.g., a Caller ID function), setup functions, and for user input. The display 1112 can also accommodate the presentation of multimedia content. A serial I/O interface 1114 is provided in communication with the processor 1102 to facilitate serial communication (e.g., USB, and/or IEEE 1394) via a hardwire connection, and other serial input devices (e.g., a keyboard, keypad, and mouse). This supports updating and troubleshooting the handset 1100, for example. Audio capabilities are provided with an audio I/O component 1116, which can include a speaker for the output of audio signals related to, for example, indication that the user pressed the proper key or key combination to initiate the user feedback signal. The audio I/O component 1116 also facilitates the input of audio signals via a microphone to record data and/or telephony voice data, and for inputting voice signals for telephone conversations.

[0078] The handset 1100 includes a slot interface 1118 for accommodating a SIS (subscriber identity system) module in the form factor of a card subscriber identity module (SIM) 1120, and interfacing the SIM card 1120 to the processor 1102. However, it is to be appreciated that the SIM card 1120 can be manufactured into the handset 1100, and updated by downloading data and software thereinto. [0079] The handset 1100 can process IP data traffic via the communications component 1110 to accommodate IP traffic from an IP network such as, for example, the Internet, a corporate intranet, a home network, a person area network, etc. , via an ISP or cable provider. Thus, VoIP traffic can be utilized by the handset 1100, and IP- based multimedia content can be received in either an encoded or a decoded format. [0080] A video and/or imaging processing component 1122 (e.g., a camera) can be provided for decoding encoded multimedia content. The handset 1100 also includes a power source 1124 in the form of batteries and/or an AC power subsystem, which power source 1124 interfaces to an external power system or charging equipment (not shown) via a power I/O component 1126. [0081] The handset 1100 can also include a dataform reader 1128 suitably designed to read many types of dataforms. For example, the reader 1128 can scan product bar codes of two and three dimensions, and other types of indicia. [0082] The handset 1100 can also include a video decoder component 1130 for processing video content received and transmitted. A location tracking component 1132 facilitates geographically locating the handset 1100. As described hereinabove, this can occur when the user initiates the feedback signal automatically or manually. [0083] A user input component 1134 facilitates the user initiating the quality feedback signal. The input component can include such conventional input device technologies such as a keypad, keyboard, mouse, stylus pen, and touch screen, for example.

[0084] A relay/repeater component 1136 that facilitates the user boosting or repeating the received signal(s) from other wireless communications devices. The relay/repeater component 1136 then enables the user transmitting or relaying the boosted signals to another location.

[0085] The handset 1100 can also include sensors 1138 that transmit sensed information to a desired location. The sensors 1138 transmit information into the handset 1100 either by hard wire or by wireless PAN connection. [0086] Now turning to FIG. 12, such figure depicts a GSM/GPRS/IP multimedia network architecture 1200 that includes a GSM core network 1201, a GPRS network 1230 and an IP multimedia network 1238. The GSM core network 1201 includes a Mobile Station (MS) 1202, at least one Base Transceiver Station (BTS) 1204 and a Base Station Controller (BSC) 1206. The MS 1202 is physical equipment or Mobile Equipment (ME), such as a mobile phone or a laptop computer that is used by mobile subscribers, with a Subscriber identity Module (SIM). The SIM includes an International Mobile Subscriber Identity (IMSI), which is a unique identifier of a subscriber. The MS 1202 includes an embedded client 1202a that receives and processes messages received by the MS 1202. The embedded client 1202a may be implemented in JAVA and is discuss more fully below. [0087] The embedded client 1202a communicates with an application 1202b that provides services and/or information to an end user. One example of the application may be navigation software that provides near real-time traffic information that is received via the embedded client 1202a to the end user. The navigation software may provide road conditions, suggest alternate routes, etc. based on the location of the MS 1202. Those of ordinary skill in the art understand that there are many different methods and systems of locating an MS 1202. [0088] Alternatively, the MS 1202 and a device 1202c may be enabled to communicate via a short-range wireless communication link, such as Bluetooth®. For example, a Bluetooth SIM Access Profile may be provided in an automobile (e.g., device 1202c) that communicates with the SIM in the MS 1202 to enable the automobile's communications system to pull information from the MS 1202. The Bluetooth communication system in the vehicle becomes an "embedded phone" that employs an antenna associated with the automobile. The result is improved reception of calls made in the vehicle. As one of ordinary skill in the art would recognize, an automobile is one example of the device 1202c. There may be an endless number of devices 1202c that use the SIM within the MS 1202 to provide services, information, data, audio, video, etc. to end users.

[0089] The BTS 1204 is physical equipment, such as a radio tower, that enables a radio interface to communicate with the MS. Each BTS may serve more than one MS. The BSC 1206 manages radio resources, including the BTS. The BSC may be connected to several BTSs. The BSC and BTS components, in combination, are generally referred to as a base station (BSS) or radio access network (RAN) 1203. [0090] The GSM core network 1201 also includes a Mobile Switching Center

(MSC) 1208, a Gateway Mobile Switching Center (GMSC) 1210, a Home Location Register (HLR) 1212, Visitor Location Register (VLR) 1214, an Authentication Center (AuC) 1218, and an Equipment Identity Register (EIR) 1216. The MSC 1208 performs a switching function for the network. The MSC also performs other functions, such as registration, authentication, location updating, handovers, and call routing. The GMSC 1210 provides a gateway between the GSM network and other networks, such as an Integrated Services Digital Network (ISDN) or Public Switched Telephone Networks (PSTNs) 1220. In other words, the GMSC 1210 provides interworking functionality with external networks.

[0091] The HLR 1212 is a database that contains administrative information regarding each subscriber registered in a corresponding GSM network. The HLR 1212 also contains the current location of each MS. The VLR 1214 is a database that contains selected administrative information from the HLR 1212. The VLR contains information necessary for call control and provision of subscribed services for each MS currently located in a geographical area controlled by the VLR. The HLR 1212 and the VLR 1214, together with the MSC 1208, provide the call routing and roaming capabilities of GSM. The AuC 1216 provides the parameters needed for authentication and encryption functions. Such parameters allow verification of a subscriber's identity. The EIR 1218 stores security-sensitive information about the mobile equipment.

[0092] A Short Message Service Center (SMSC) 1209 allows one-to-one Short

Message Service (SMS) messages to be sent to/from the MS 1202. A Push Proxy Gateway (PPG) 1211 is used to "push" (e.g., send without a synchronous request) content to the MS 1202. The PPG 1211 acts as a proxy between wired and wireless networks to facilitate pushing of data to the MS 1202. A Short Message Peer to Peer (SMPP) protocol router 1213 is provided to convert SMS-based SMPP messages to cell broadcast messages. SMPP is a protocol for exchanging SMS messages between SMS peer entities such as short message service centers. It is often used to allow third parties, e.g., content suppliers such as news organizations, to submit bulk messages.

[0093] To gain access to GSM services, such as speech, data, and short message service (SMS), the MS first registers with the network to indicate its current location by performing a location update and IMSI attach procedure. The MS 1202 sends a location update including its current location information to the MSC/VLR, via the BTS 1204 and the BSC 1206. The location information is then sent to the MS's HLR. The HLR is updated with the location information received from the MSC/VLR. The location update also is performed when the MS moves to a new location area. Typically, the location update is periodically performed to update the database as location updating events occur.

[0094] The GPRS network 1230 is logically implemented on the GSM core network architecture by introducing two packet-switching network nodes, a serving GPRS support node (SGSN) 1232, a cell broadcast and a Gateway GPRS support node (GGSN) 1234. The SGSN 1232 is at the same hierarchical level as the MSC 1208 in the GSM network. The SGSN controls the connection between the GPRS network and the MS 1202. The SGSN also keeps track of individual MS's locations and security functions and access controls.

[0095] A Cell Broadcast Center (CBC) 1233 communicates cell broadcast messages that are typically delivered to multiple users in a specified area. Cell Broadcast is one -to-many geographically focused service. It enables messages to be communicated to multiple mobile phone customers who are located within a given part of its network coverage area at the time the message is broadcast. [0096] The GGSN 1234 provides a gateway between the GPRS network and a public packet network (PDN) or other IP networks 1236. That is, the GGSN provides interworking functionality with external networks, and sets up a logical link to the MS through the SGSN. When packet-switched data leaves the GPRS network, it is transferred to an external TCP-IP network 1236, such as an X.25 network or the Internet. In order to access GPRS services, the MS first attaches itself to the GPRS network by performing an attach procedure. The MS then activates a packet data protocol (PDP) context, thus activating a packet communication session between the MS. the SGSN, arc the GGSN.

[0097] In a GSM/GPRS network, GPRS services and GSM services can be used in parallel. The MS can operate in one three classes: class A, class B, and class C. A class A MS can attach to the network for both GPRS services and GSM services simultaneously. A class A MS also supports simultaneous operation of GPRS services and GSM services. For example, class A mobiles can receive GSM voice/data/SMS calls and GPRS data calls at the same time. A class B MS can attach to the network for both GPRS services and GSM services simultaneously. However, a class B MS does not support simultaneous operation of the GPRS services and GSM services. That is, a class B MS can only use one of the two services at a given time. A class C MS can attach for only one of the GPRS services and GSM services at a time. Simultaneous attachment and operation of GPRS services and GSM services is not possible with a class C MS.

[0098] A GPRS network 1230 can be designed to operate in three network operation modes (NOMl, N0M2 and N0M3). A network operation mode of a GPRS network is indicated by a parameter in system information messages transmitted within a cell. The system information messages dictates a MS where to listen for paging messages and how signal towards the network. The network operation mode represents the capabilities of the GPRS network. In a NOMl network, a MS can receive pages from a circuit switched domain (voice call) when engaged in a data call. The MS can suspend the data call or take both simultaneously, depending on the ability of the MS. In a N0M2 network, a MS may not received pages from a circuit switched domain when engaged in a data call, since the MS is receiving data and is not listening to a paging channel In a N0M3 network, a MS can monitor pages for a circuit switched network while received data and vise versa.

[0099] The IP multimedia network 1238 was introduced with 3GPP Release 5, and includes an IP multimedia subsystem (IMS) 1240 to provide rich multimedia services to end users. A representative set of the network entities within the IMS 1240 are a call/session control function (CSCF), a media gateway control function (MGCF) 1246, a media gateway (MGW) 1248, and a master subscriber database, called a home subscriber server (HSS) 1250. The HSS 1250 may be common to the GSM network 1201, the GPRS network 1230 as well as the IP multimedia network 1238.

[00100] The IP multimedia system 1240 is built around the call/session control function, of which there are three types: an interrogating CSCF (I-CSCF) 1243, a proxy CSCF (P-CSCF) 1242, and a serving CSCF (S-CSCF) 1244. The P-CSCF 1242 is the MS's first point of contact with the IMS 1240. The P-CSCF 1242 forwards session initiation protocol (SIP) messages received from the MS to an SIP server in a home network (and vice versa) of the MS. The P-CSCF 1242 may also modify an outgoing request according to a set of rules defined by the network operator (for example, address analysis and potential modification). [00101] The I-CSCF 1243 forms an entrance to a home network and hides the inner topology of the home network from other networks and provides flexibility for selecting an S-CSCF. The I-CSCF 1243 may contact a subscriber location function (SLF) 1245 to determine which HSS 1250 to use for the particular subscriber, if multiple HSS 's 1250 are present. The S-CSCF 1244 performs the session control services for the MS 1202. This includes routing originating sessions to external networks and routing terminating sessions to visited networks. The S-CSCF 1244 also decides whether an application server (AS) 1252 is required to receive information on an incoming SIP session request to ensure appropriate service handling. This decision is based on information received from the HSS 1250 (or other sources, such as an application server 1252). The AS 1252 also communicates to a location server 1256 (e.g., a Gateway Mobile Location Center (GMLC)) that provides a position (e.g., latitude/longitude coordinates) of the MS 1202. [00102] The HSS 1250 contains a subscriber profile and keeps track of which core network node is currently handling the subscriber. It also supports subscriber authentication and authorization functions (AAA). In networks with more than one HSS 1250, a subscriber location function provides information on the HSS 1250 that contains the profile of a given subscriber.

[00103] The MGCF 1246 provides interworking functionality between SIP session control signaling from the IMS 1240 and ISUP/BICC call control signaling from the external GSTN networks (not shown). It also controls the media gateway (MGW) 1248 that provides user-plane interworking functionality (e.g., converting between AMR- and PCM-coded voice). The MGW 1248 also communicates with other IP multimedia networks 1254.

[00104] What has been described above includes examples of the claimed subject matter. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the claimed subject matter, but one of ordinary skill in the art may recognize that many further combinations and permutations of such matter are possible. Accordingly, the claimed subject matter is intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term "includes" is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term "comprising" as "comprising" is interpreted when employed as a transitional word in a claim.

Claims

CLAIMSWhat is claimed is:

1. A system that facilitates ad-hoc communications of first responder (FR) wireless communications devices at an emergency location, comprising: a first FR wireless communications device of an ad-hoc network requesting communications with a remote system, the first FR device incapable of direct wireless communications with the remote system; and a wireless communications pathway that facilitates communications between the first FR device and the remote system using a device association protocol.

2. The system of claim 1 , wherein the remote system is part of an emergency command center.

3. The system of claim 2, wherein the wireless communications pathway comprises at least one of a personal area network (PAN), an emergency services site IP-base network, a public safety network, and a macro wireless network.

4. The system of claim 3, wherein the first FR device communicates emergency information to the remote system via the wireless communications pathway.

5. The system of claim 4, wherein the information communicated between the first FR device and the mobile command center includes at least one of voice data, text data, voice services, PTT voice services, streaming video services, file transfer services, and local data sensed by the first FR device at a current location of the first FR device.

6. The system of claim 1 , further comprising a second FR wireless communications device capable of direct communications with the first FR device and incapable of direct communications with the remote system, the first FR device initiates direct communications with the second FR device using the device association protocol and requests an available communication path to the remote system.

7. The system of claim 6, wherein the second FR device includes a repeater and relay capability that enables the first FR device to relay information to the remote system.

8. The system of claim 7, further comprising parameter data of the first FR device that is sent from the first FR device to the second FR device.

9. The system of claim 8, wherein the parameter data comprises data related to at least one of encryption information, geographic location, device identification, user identification and authentication information.

10. The system of claim 9, wherein the second FR device uses the parameter data to authenticate the first FR device and a user of the first FR device.

11. The system of claim 10, further comprising a third FR wireless communications device capable of direct communications with the second FR device and the remote system, the second FR device initiates direct communications with the third FR device using the device association protocol and requests an available communication path to the remote system.

12. The system of claim 11 , wherein the third FR device establishes a direct communications path with the remote system and using the device association protocol, instructs the remote system that traffic is pending from the first FR device.

13. The system of claim 12, wherein the first FR device is notified that communications are established to the remote system, and information from the first FR device is relayed through the second and third FR devices to the remote system.

14. The system of claim 1, wherein the communications pathway includes a local IP network that facilitates communication between the first FR device and the remote system, the first FR device initiates communications with a second FR wireless communications device over the IP network using the device association protocol, and requests an available communication path to the remote system via the second FR device.

15. The system of claim 14, wherein the IP network establishes a direct communications path with the remote system using the device association protocol, and instructs the remote system that traffic is pending from the first FR device.

16. The system of claim 15, wherein the first FR device is notified that a direct communications pathway has been established to the remote system and information from the first FR device is transmitted through the IP network to the remote system.

17. The system of claim 16, wherein the IP network is a mesh network.

18. The system of claim 1 , wherein the communications pathway includes a macro wireless network that facilitates communications between a second FR device and the remote system, the second FR device initiates communications with the macro wireless network using the device association protocol and requests an available communication path to the remote system.

19. The system of claim 18, wherein the macro wireless network establishes communications with the remote system using the device association protocol, and instructs the remote system that traffic is pending from the first FR device.

20. The system of claim 19, wherein the first FR device is notified that a communications pathway has been established to the remote system, and information from the first FR device is transmitted through the second FR device and macro wireless network to the remote system.

21. The system of claim 1 , wherein the first FR device comprises at least one sensor for providing sensed information from the first FR device to a desired location.

22. The system of claim 21 , wherein the sensed information comprises at least one of telemedicine data, blood pressure data, biochemical data, environmental data, images, cardiac data, and Chemical Biological Radiological Nuclear Explosive (CBRNE) data.

23. The system of claim 22, wherein the sensor comprises wireless connectivity for transmitting the sensed information to the first FR device via at least one of a Bluetooth network and a W-LAN.

24. The system of claim 22, wherein the sensor tethers to the first FR device via a serial communications technology.

25. A method of facilitating ad-hoc communications for FR communications devices at an emergency location, comprising: receiving a first FR wireless communications device for communicating emergency services information at the emergency location; requesting communications with an emergency command center (ECC) using a device association protocol via one or more intermediate FR wireless communications devices, the first FR device incapable of direct communications with the ECC; authenticating the first FR device via the one or more intermediate FR devices using authentication data of the first FR device; and establishing communications between the first FR device and the ECC via the one or more intermediate FR devices.

26. The method of claim 25, further comprising: initiating direct communications with a second and a third FR communications devices of the one or more intermediate FR devices, wherein direct communications are initiated with the third FR device via the second FR device; requesting an available communication path to the ECC; establishing a direct communications path with the ECC via the third FR device; and instructing the ECC that traffic is pending from the first FR device.

27. The method of claim 26, further comprising: notifying the first FR device that a direct communications pathway has been established to the ECC; and relaying information from the first FR device through the second and third FR devices to the ECC.

28. The method of claim 25, further comprising: initiating direct communications with an IP network using the device association protocol via the first FR device; requesting an available communication path to the ECC; establishing a direct communications path with the ECC via the IP network; instructing the ECC that traffic is pending from the first FR device; and notifying the first FR device that a direct communications pathway has been established to the ECC.

29. The method of claim 25, further comprising: initiating direct communications with the one or more intermediate FR devices using the device association protocol; requesting an available communication path to the ECC; initiating direct communications with a macro wireless network via the one or more intermediate FR devices; requesting an available communication path to the ECC; establishing a direct communications path with the ECC via the one or more intermediate FR devices and the macro wireless network; and instructing the ECC that traffic is pending from the first FR device.

30. The method of claim 29, further comprising: notifying the first FR device that a direct communications pathway has been established to the ECC; and relaying information from the first FR device through the one or more intermediate FR devices and macro wireless network to the ECC.

31. The method of claim 25, wherein the first FR device comprises at least one sensor for providing sensed information from the first FR device to a desired location.

32. The method of claim 31 , wherein the sensors are housed within the first FR device.

33. The method of claim 31, wherein the sensors are a separate unit of the first FR device and communicate with the first FR device via wireless connectivity.

34. A system that facilitates ad-hoc communications of FR wireless devices at an emergency location, comprising: a first FR wireless communications device at the emergency location requesting communications with a mobile command post (MCP), the first FR device incapable of direct wireless communications with the MCP; a second FR wireless communications device at the emergency location in one of direct and indirect communications with a wireless communications pathway that facilitates automatic communications between the first FR device and the MCP using a device association protocol; and a third FR wireless communications device at the emergency location in direct communication with the wireless communications pathway that facilitates automatic communications between the first FR device and the MCP using the device association protocol, wherein the second FR device indirectly communicates with the MCP via the third FR device.

35. The system of claim 34, wherein the second and third FR devices include a repeater capability.

36. The system of claim 35, wherein the device association protocol includes authentication information the second FR device uses to authenticate the first FR device and a user of the first FR device.

37. The system of claim 36, wherein the first FR device passes encryption data, geographic data, device identification data, user identification data, biometric data and authentication data via the device association protocol to the second FR device.

38. The system of claim 34, wherein the wireless communications pathway is a combination of networks, such that the first FR device relays data indirectly through a PAN to the second FR device, which in turn relays data indirectly through an IP network to the third FR device, which in turn relays data indirectly through a macro network to the MCP.

39. A system that facilitates ad-hoc communications of FR wireless devices at an emergency location, comprising: a first FR wireless communications device at the emergency location requesting communications with an ECC, the first FR device incapable of direct wireless communications with the ECC; and an IP network at the emergency location in direct communications with a wireless communications pathway that facilitates automatic communications between the first FR device and the ECC using a device association protocol.

40. The system of claim 39, wherein the IP network is a local IP network configured at the emergency location for emergency services communications, the IP network transmits data of the first FR device to the ECC.

41. A system that facilitates ad-hoc communications of FR wireless devices at an emergency location, comprising: a first FR wireless communications device at the emergency location requesting communications with an ECC, the first FR device incapable of direct wireless communications with the ECC; a second FR wireless communications device at the emergency location in one of direct and indirect communications with a wireless communications pathway that facilitates automatic communications between the first FR device and the ECC using a device association protocol; and a macro wireless network at the emergency location in direct communication with the wireless communications pathway that facilitates automatic communications between the first FR device and the ECC using the device association protocol, wherein the second FR device indirectly communicates with the ECC via the macro wireless network.

42. The system of claim 41 , wherein the second FR device communicates with the macro wireless network via a radio infrastructure that connects to the macro wireless network.

43. The system of claim 42, wherein the second FR device relays data of the first FR device indirectly through the macro wireless network to the ECC.

44. A system that facilitates ad-hoc communications of FR wireless devices at an emergency location, comprising: at least one sensor at the emergency location transmitting emergency information to a first FR wireless communications device, the first FR device requesting communications with an ECC and being incapable of direct wireless communications with the ECC; and a second FR wireless communications device at the emergency location in one of direct and indirect communications with a wireless communications pathway that facilitates automatic communications between the first FR device and the ECC using a device association protocol.

45. The system of claim 44, further comprising a third FR wireless communications device at the emergency location in direct communication with the wireless communications pathway that facilitates automatic communications between the first FR device and the ECC using the device association protocol, wherein the second FR device indirectly communicates with the ECC via the third FR device.

46. The system of claim 44, wherein the emergency information comprises at least one of telemedicine data, blood pressure data, biochemical data, environmental data, images, cardiac data, and CBRNE data.

47. The system of claim 46, wherein the at least one sensor is housed within the first FR communications device.

48. The system of claim 46, wherein the at least one sensor is a separate unit of the first FR device and communicates with the first FR device via wireless connectivity.

49. A system of facilitating ad-hoc communications for FR communications devices at an emergency location, comprising: means for receiving at a second FR wireless communications device, a request from a first FR wireless communications device to access a MCP at the emergency location; means for authenticating the first FR device via the second FR device using authentication data received from the first FR device; means for establishing a communications pathway between the first FR device and the MCP; and means for communicating information between the first FR device and the MCP.

50. The system of claim 49, wherein the communications pathway includes at least one of a PAN, an emergency services site IP -base network, a public safety network, and a macro cellular network.