Emergency services for wireless data access networks

A system [100] for facilitating wireless data communication may include an operations center [110] configured to implement access control rules [305] within an emergency zone [200] and an access device [130/310] configured to provide data access to a network [320] for user devices [140] and emergency devices [210]. The access device [130/310] may include a memory [340] configured to store the access control rules [305] that provide preferential access to the network for the emergency devices [210] within the emergency zone [200].

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to network management and, more particularly, to systems and methods for managing networks during emergencies.

2. Description of the Related Art

Recent events have shown that communications systems should be devoted primarily to emergency use in emergencies or cases of widespread disaster. Allowing normal civilian traffic to compete with that from emergency communication devices of emergency workers is likely to give “busy signals” and very poor service to the emergency workers. As used herein, the term “emergency devices” and its variants denote, generally, communication devices employed by emergency workers. Emergency workers may include, for example, police, fire fighting personnel, rescue workers, or other civil or military authorities.

For some time, the traditional, “wired” telephone system in the United States has employed features that allow government personnel to take precedence in use of the telephone system during emergencies. Such “emergency override” or “emergency access” features have at least been proposed to be added to cellular telephony (i.e., transmission of sound or voice information) systems.

Wireless data (i.e., non-voice) technology, however, is sufficiently different from that of traditional telephone or cellular telephone systems that new techniques must be created in order to provide such an emergency override feature for wireless data services.

Consequently, a need exists for techniques for implementing emergency overrides in wireless data systems.

SUMMARY OF THE INVENTION

Systems and methods consistent with the present invention address this and other needs by discriminating between emergency devices and other devices and providing preferential access to the emergency devices.

In accordance with the purpose of the invention as embodied and broadly described herein, a system for facilitating wireless data communication may include an operations center configured to implement access control rules within an emergency zone and an access device configured to provide preferential access to a network to emergency devices over non-emergency devices within the emergency zone based on the access control rules.

In another implementation consistent with the present invention, a method may include determining a need for an emergency zone in which wireless data access is to be restricted to emergency devices and associating one or more access devices with the emergency zone. An emergency message may be sent to the one or more access devices for wireless data access within the emergency zone to be restricted to the emergency devices.

In a further implementation consistent with the present invention, a method may include validating an emergency message and implementing access control rules based on the emergency message. Access by wireless data devices may be controlled to give preference to emergency devices based on the access control rules.

In yet another implementation consistent with the present invention, a computer-readable medium that stores instructions executable by one or more processors to perform a method for controlling data access in a wireless network may include instructions for differentiating between emergency devices and non-emergency devices and instructions for allowing wireless data access to the emergency devices in an emergency zone. The computer-readable medium also may include instructions for limiting wireless data access to the non-emergency devices in the emergency zone.

DETAILED DESCRIPTION

The following detailed description of the invention refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention. Rather, the scope of the invention is defined by the appended claims and equivalents.

Methods and systems consistent with the principles of the invention may discriminate between emergency devices and other devices and provide preferential wireless data access to the emergency devices. In one implementation, the wireless data access may be exclusive to the emergency devices within an emergency zone.

Exemplary System

FIG. 1illustrates an exemplary wireless data system100in which the principles of the present invention may be implemented. System100may include a network operations center110and a number of wireless access points130-1,130-2, etc. (collectively “access points130”) connected via one or more wireline networks. It is also possible, though not illustrated inFIG. 1, that network operations center110and at least some of access points130may be connected via a wireless network. System100may also include a number of user devices140-1,140-2, etc. (collectively “user devices140”) that communicate with access points130via wireless links135. System100may include a single wireless LAN/WAN within a building, a campus-wide wireless network, or metro-scale or national-scale architectures.

Network operations center110may coordinate communication between access points130and some other network, such as the Internet. Network operations center110may also supervise and/or administer access points130, and may be able to alter the operation of access points130via changes in software, firmware, etc. Network operations center110may be operated by an Internet Service Provider (ISP) or other provider of access to wireless data services.

Wireline network120may be connected to access points130and may be configured to provide a given bandwidth of information to access points130. Wireline network120may include one or more physical interfaces, such as Ethernet or optical fiber, that facilitate data transfer between access points130and another network, such as the Internet.

Access points130may be configured to communicate wirelessly via one or more wireless technologies, such as radio frequency (RF) or optical (e.g., infrared) communication. In one implementation, access points130may be configured to use IEEE 802.11 standard protocols (and/or a variant such as 802.11b, 802.11a, or 802.11g) for wireless communication. In other implementations, other wireless protocols, such as a Bluetooth®-related protocol, may be employed by access points130. Access points130may also be configured to send and receive wireless, non-voice data via cellular telephone communication protocols, such as TDMA, CDMA, AMPS, etc. Further, each of access points130may have an associated effective area of coverage, depending upon the type of antenna employed. For example, an omnidirectional antenna may result in a roughly circular area of coverage, while a directional antenna may result in a cone or sector-shaped area.

User devices140may be configured (i.e., contain the necessary wireless hardware) to communicate wirelessly with access points130. User devices140may include laptop computers, hand-held PDAs, an Internet-enabled cell phone, or other such devices capable of communicating wireless data. Examples of wireless data services that may be employed by user devices140include, but are not limited to, e-mail messaging, instant messaging via a central system (e.g., AOL® Instant Messenger™, Yahoo!® Messenger™, etc.), text messaging, alphanumeric (two-way) paging, web browsing (e.g., Internet or intranet, possibly via HTML, XML, etc.), file transferring, and any other known or later-developed scheme for communication using text or binary data. Although device140-1inFIG. 1is shown connected to a single access point130-1, in fact, it may experience simultaneous connections to a number of access points130. Absent differentiated levels of service (e.g., “premium” verses “standard” levels of service), user devices140may be served in a non-discriminatory (e.g., first-come, first-served or round-robin) manner by access points130.

FIG. 2illustrates wireless data system100during an emergency. An area covered by system100in which the emergency exists may be designated as an emergency zone200. Although shown as a single zone encompassing part of system100, those skilled in the art will appreciate that emergency zone200may encompass all of system100, or that multiple emergency zones200may exist, covering discontiguous portions of system100. As a concrete example, all of the access points over an area of some city blocks may be declared an emergency zone. In addition to user devices140, one or more emergency devices210-1, etc. (collectively “emergency devices210”) may be present in emergency zone200.

In emergency zone200, some portion of the wireless access network may be needed for emergency services (e.g., Internet or intranet access) by fire fighters, police, Federal security services or other emergency personnel using emergency devices210. InFIG. 2, access points130-3and130-4fall within emergency zone200, and their operation may be altered during the emergency as described herein. Other access points (e.g., access point130-2) that may not be physically located within emergency zone200may have a coverage area that partially overlaps emergency zone200. In such instances, a default rule (e.g., always include, never include, or include based on percentage overlap) will determine whether such “bordering” access points130will be included in emergency zone200. It may be very desirable for emergency devices210within emergency zone200to receive all of the available capacity of access points130-3and130-4(or at least preferred access) during an emergency.

In operation, emergency devices210used by emergency service workers, such as firemen, police, medical personnel, and perhaps the military, may have exclusive use of wireless data system100(e.g., access points130-3and130-4) within emergency zone200. User devices140of other, normal (perhaps paying) users may be prevented from access to system100in emergency zone200, once such a zone is put into effect. User devices140may not be allowed to use system100within emergency zone200until emergency zone200is restored to normal (i.e., non-emergency) service. User devices140of these displaced users may, in some implementations consistent with the principles of the invention, be allowed to use other parts of wireless data system100outside of emergency zone200. Emergency devices210may, or may not, be able to access other portions of system100in a normal manner outside of emergency zone200.

Exemplary Access Control Schemes

FIG. 3schematically illustrates a number of access control schemes consistent with the principles of the invention. In the schemes illustrated inFIG. 3, one or more access point(s)130may communicate with a network320(e.g., the Internet, an intranet, etc.) via an access gateway310. In some implementations consistent with the principles of the invention (not shown), access gateway310may be located in network operations center110. In the implementation shown inFIG. 3, however, access gateway310may be located separate from network operations center110and may control traffic between access point(s)130and network320.

Network operations center110may be configured to implement access control rules305in access point(s)130or access gateway310(or possibly a combination thereof) to control access to network320. In one implementation, control rules305may be implemented by access point(s)130themselves. In another implementation, control rules305may be implemented by access gateway310that is “upstream” from access points130(e.g., in more or less centralized gateways where the wireless data traffic is channeled into, for example, a main metro-area network run by a service provider). These access point and gateway implementations are similar to each other, and any differences in implementation will be described in greater detail below.

AlthoughFIG. 3shows arrows from network operations center110to access point130and access gateway310, this does not necessarily mean that network operations center110transfers access control rules305to access point130and access gateway310each time that access to network320needs to be controlled. Rather, network operations center110may, during an emergency, just trigger access control rules305that are already resident in access point(s)130or access gateway310. Thus,FIG. 3is intended to convey that network operations center110may implement access control rules305in access point130and/or access gateway310, and should not limit the manner of implementation of these rules305.

Many formats for access control rules305are possible, and many techniques for implementing access control rules305exist. Whenever a device (e.g., access point130or gateway310) is ready to forward information (e.g., a data packet), it may check certain fields in the packet content against access control rules305. Common fields used for such access control may include source and/or destination addresses (e.g., IP addresses) for the information. In some implementations, it may be very desirable to check the requesting devices' (e.g., devices140or210) Medium Access Control (MAC) address, which is a globally-unique IEEE 802.2 address used for a given device's wireless transceiver. If this MAC address is prohibited by a rule in access control rules305(e.g., the address does not correspond to an emergency device210), the packet from such device may be discarded. Alternatively, the packet may be processed normally if sent from an emergency device210. By proper configuration of access control rules305, such techniques may be used to discard all messages from normal user devices140, and provide priority service to those from emergency devices210used by emergency workers.

There are a number of ways in which such rule sets305may be implemented. Although a few concrete examples are provided herein, the principles of the invention encompass other known ways of enforcing rules. For example, one way is to require all emergency devices210to have special kinds of MAC addresses. For IEEE 802.2 MAC addresses, one field lists the company that made the device. One value from this field may be used to designate emergency devices210, no matter which company manufactures them. Another way to enforce rules305is to maintain a wide-area (e.g., city-wide) list of all MAC addresses of emergency devices210. This address list scheme does not require any special use of fields in MAC addresses, but an up-to-date list of such addresses may need to be maintained. A wireless data service provider, however, may already maintain a complete list of all acceptable MAC addresses of its customers, to help combat fraudulent theft of service.

Another scheme to enforce rules305may be to require all users to “log in” (i.e., provide authentication information such as an identifier and/or password) to system100, either via human interaction or via some automated protocols such as Dynamic Host Configuration Protocol (DHCP), or a combination of the two. During this authentication process, device210(and/or its human operator) can supply sufficient information to claim emergency priority, and the device identifier can then be looked up in, for example, a designated “emergency” table. In fact, such a scheme may be implemented in a straightforward manner by an “emergency password” that emergency personnel may enter to gain priority access to system100. Other schemes are possible, including pre-assigned identifiers (e.g., codes or alpha-numeric strings) that uniquely identify not only the type of device (i.e., an emergency device210), but also the user of the device.

Any of the access control schemes using rules305described herein may be implemented via instructions and/or programs stored on computer-readable media in access point(s)130or access gateway310. Once a set of access rules305is in operation, it will have the effect of “choking off” all user traffic from user devices140, while allowing traffic to/from emergency devices210through the affected access points130and/or gateways310serving emergency zone200. When the emergency has ended, network operations center110may issue new rule sets and/or commands that undo this effect and restore system100to normal service.

Access Control in Gateways:

Because a given (metro) gateway310may cover a large number of access points130, it is possible that only some subset of its covered access points130may be associated with a given emergency zone200. Access control rules305may be stored in a memory (not shown) of gateway310. Thus, access control rules305introduced into gateway(s)310should specify two different items: 1) the access control scheme (i.e., the “substance” of access control rules305), and 2) the affected access points130(i.e., the “targets” of access control rules305). Gateway(s)310may then discard all normal user packets from the affected (i.e., associated with emergency zone200) access points130, but may treat all other types of traffic normally.

Access Control in Access Points:

Access point130may include a wireless transceiver330and a processing module340(e.g., CPU plus memory, such as RAM). Using access control rules305, processing module340may limit access of user devices140to network320via wireless transceiver330. Various schemes may be implemented by processing module340to implement access control rules305.

In one implementation, processing module340may allow any form of packet communication across the wireless transceiver330. Processing module340may only discard packets once they have entered access point130via wireless link135.

In another implementation, access point130refuses to allow user device140to transmit a packet across wireless link135. This scheme may not produce a significantly better effect than discarding data packets at access point130, but it does keep wireless link135clear of potential interference from normal user devices140that are busy (e.g., continuously trying to connect to the Internet to find out what is going on). In such an implementation, network operations center110may install a list of approved MAC addresses in access point130that contains the allowed emergency service devices210. Alternatively access point130may be provided with rules for allowable MAC addresses (e.g., addresses with a field set to some known value, etc.). Whenever access point130is engaging in a typical communications protocol “handshake” for packet transfer across wireless link135, processing unit340may consult this list or table for acceptable emergency devices210.

For those systems100that use a 4-way handshake (e.g., RTS-CTS-DATA-ACK) including a Request to Send (RTS) message, and that include the originating device identifier in the RTS, the following scheme may be used to deny packets from wireless link135. User device140(or emergency device210) may send an RTS message that includes its device identifier. Access point130may compare this device identifier against its list of approved MAC addresses. If the identifier is not in this list, access point130may ignore the RTS. This prevents the corresponding data packet from being sent by device140, because device140will not receive the Clear to Send (CTS) message corresponding to the ignored RTS. Otherwise, access point130may process the request normally—send a CTS message, accept the wireless data from device210, and send an Acknowledgment (ACK) message to complete the handshake.

For those systems100that use only a two-way handshake (i.e., that do not have the RTS/CTS part of the 4-way protocol), the following scheme may be used to deny packets. User device140(or emergency device210) may send a data frame that includes its device identifier. Access point130may compare this device identifier against its list of approved MAC addresses. If the identifier is not in this list, access point130may ignore the data. Otherwise access point130may process the wireless data normally by sending a return ACK message. In either of the 4-way or 2-way handshake cases, the effect is to ignore data frames sent by non-emergency devices140. The IEEE 802.11 standard, for example, mandates that an unsuccessful transmitting device140go into a “back off” mode where it remains silent for a random time interval, and the interval may increase with the number of failed attempts to transmit the frame. In effect, this back off mode tends to leave more of wireless channel135“clear” and available for use by emergency service devices210.

As previously described, the list/table of approved MAC addresses in either access point130or access gateway310may be adjusted as necessary by commands from network operations center110. Such adjustment may include the removal of this list when the emergency has ended in any zone200, so that wireless system100may return to normal operation.

Exemplary Access Control Processing

FIG. 4illustrates an exemplary method400of initiating access control in an emergency zone200. Method400may be performed, for example, by network operations center110and/or network operators associated therewith. Processing may begin with network operators determining that one or more emergency zone(s)200need to be put into effect [act410]. In addition to such a determination, the extent of emergency zone(s)200(i.e., those access point(s)130or gateways(s)310that should be associated with emergency zone(s)200) may also be determined. Those skilled in the art will appreciate that various schemes for associating access point(s)130and/or gateways(s)310with emergency zone(s)200may be used, including predetermined (e.g., lists of devices that correspond to geographical areas, such as city blocks), ad hoc (e.g., determined by a large concentration of emergency devices210), and/or phased-in (e.g., varying with time and/or geography) approaches.

Processing may continue by the network operators giving commands at one or more network operations centers110that these access point(s)130and/or gateways(s)310should be associated with an emergency zone200[act420]. If emergency zone200is associated with one or more access point(s)130and one or more gateway(s)310[act430], network operation center(s)110may send commands to all the affected access points130and all of the affected access gateways310[act440], which contain the access rules/lists. If, on the other hand, only access points or only access gateways310are to be associated with emergency zone200[act450], network operation center(s)110may send commands to all the affected access point(s)130[act460] or to all of the affected access gateway(s)310[act470]. In either event, the control messages may be protected by cryptographic measures to ensure both the privacy and the integrity of the control messages. Such encryption may also provide a measure of confidence that such commands are properly authorized.

FIG. 5illustrates an exemplary method500of implementing access control in an emergency zone200in accordance with implementations of the present invention. When a device (e.g., access point130and/or gateway310) receives an emergency message from network operations center110, it may validate the message [act510]. The authentication, integrity, etc. of the emergency message may be verified at this point. For example, the emergency message may be decrypted using an emergency decryption key resident in access point130and/or gateway310.

When the emergency message has been verified, access control rules305may be implemented [act520]. In one implementation, access point130and/or gateway310may extract access control rules305from this message and install them into local memory (e.g., in processing module340). Such local memory may be RAM, and/or non-volatile memory (such as flash memory) so rules305can survive across power outages. In another implementation, rules305may already be resident in access point130and/or gateway310, and the emergency message may provide one or more parameters to initialize and/or specify the operation of access control rules305(e.g., duration such as an automatic “sunset” period, a phase-in time, whether currently operating user devices140will be immediately disconnected, etc.).

Once access control rules305have been established, these rules305may control access to network320for user devices140and emergency devices210[act530]. Such access control may filter wireless data packets according to any of the above-described schemes. For example, access may be controlled based on a source/destination IP address, a MAC address, manual or automatic authentication schemes, etc.

Access point130and/or gateway310may continue such filtering until it receives subsequent commands [act540]. Such subsequent commands may, for example, alter access control rules305in effect, in which case act530would continue under the altered rules305. For example, different sets of control rules305may be used for early-stage, mid-stage, and late-stage emergencies. If the emergency is over, a “rescind emergency” message may be received, and access control rules may be removed and/or inactivated [act550]. In this manner, wireless data service may revert to normal for user devices140and emergency devices210. In some implementations, for example when user devices140are in a “backed off,” inactive mode for wireless data communications, access point130and/or gateway310may send an “all clear” or other initialization signal that lets devices140know that data communication is once again available.

CONCLUSION

Systems and methods consistent with the present invention may discriminate between emergency devices and other devices and provide preferential wireless data access to the emergency devices during an emergency.

The foregoing description of preferred embodiments of the present invention provides illustration and description, but is not intended to be exhaustive or to limit the invention to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of the invention.

For example, although preventing user devices140from accessing system100has been disclosed, other access schemes are possible that are more graduated. For example, emergency devices210may be given (perhaps much higher) priority in emergency zone200than user devices140, but user devices140need not be completely denied access to system100. Further, various observations (e.g., total bandwidth available in view of the bandwidth used by emergency devices210) may be used to allow some access by user devices140during the emergency. For example, if only a handful of emergency devices210are vying for system resources, some user devices140may be allowed access by rules305. In one implementation consistent with the principles of the invention, some user devices140(e.g., those on a “premium” service plan) may retain limited wireless data capability (perhaps deferring to emergency devices210) during an emergency, while other user devices (e.g., those on a “standard” or “minimum” service plan) may completely lose wireless data access during the emergency.

Further, although wireless data (e.g., text, pictures, etc.) has been defined as being “non-voice” herein, such wireless data may include Voice over IP (VoIP) data, even though such data may be used to carry sound. “Wireless data” as used herein encompasses text or binary data (even if such data is used to carry voice), but may exclude typical cellular-telephone-originated voice calls. VoIP wireless data, for example, may be viewed as “packetized” data, because it may be sent in individual packets with header information on each packet. Such packetized data may be conceptually distinguished from circuit-oriented services, such as calls from cell phones.

Also, while series of acts have been described with regard toFIGS. 4 and 5, the order of the acts can be varied in other implementations consistent with the present invention, and non-dependent acts can be implemented in parallel. Further, the acts in these figures may be implemented as instructions, or groups of instructions, in a computer-readable medium, such as an optical, magnetic, solid-state, integrated circuit, or other type of typical medium read by processors. For example, operation center110, access point130, and/or gateway310may include a processor configured to execute such instructions on the computer-readable medium to perform the acts inFIGS. 4 and 5.

No element, act, or instruction used in the description of the present invention should be construed as critical or essential to the invention unless explicitly described as such. As used herein, the article “a” is intended to include one or more items. Where only one item is intended, the term “one” or similar language is used. The scope of the invention is not limited to the foregoing description, and is instead defined by the appended claims and their equivalents.