Source: https://patents.google.com/patent/US7865713
Timestamp: 2018-04-23 15:31:57
Document Index: 400148735

Matched Legal Cases: ['Application No. 60', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 600', 'art 11', 'art 11']

US7865713B2 - Application-aware wireless network system and method - Google Patents
Application-aware wireless network system and method Download PDF
US7865713B2
US7865713B2 US11966912 US96691207A US7865713B2 US 7865713 B2 US7865713 B2 US 7865713B2 US 11966912 US11966912 US 11966912 US 96691207 A US96691207 A US 96691207A US 7865713 B2 US7865713 B2 US 7865713B2
US11966912
US20080162921A1 (en )
Jamsheed Bugwadia
Yun Freund
Roy Gignac
Dan Simone
Gary Eugene Morain
A technique for dynamically responding to threats in a wireless network involves deploying a single network including APs capable of booting from a plurality of software images. Individual APs can switch (or be switched) between multiple sets of software so that network managers can select the AP software most appropriate for a given instance. For example, if a threat is detected, multiple APs can be switched to sensor mode to deal with the threat. As another example, all of the APs can be switched to sensor mode after hours. Alternatively, a server can provide the software image(s) needed for an AP to operate in accordance with a desired functionality.
This application claims priority to U.S. Provisional Patent Application No. 60/877,907, filed Dec. 28, 2006, which is hereby incorporated by reference in its entirety.
An access point (AP) is a device used by wireless clients to connect to a network. An AP functions as a standalone entity in some implementations and functions in cooperation with distribution hardware in other implementations. Distribution hardware may include a wireless switch used to manage APs and provide network-connectivity to wireless clients. A wireless domain may refer to a group of wireless switches that are configured to exchange relevant information, and using this information make informed decisions. A known device is a station (e.g., a wireless AP or client device) that is part of a network wireless installation. A rogue device is a station that is considered harmful for a network wireless installation because it is, for example, violating policies or hampering wireless access to the network.
A traditional approach to rogue detection has been to (1) use a second set of hardware in addition to APs, or (2) provide an integrated network that provides both data services and rogue detection services. The advantage of the first approach is that a user can select the best devices for the job, though this often results in higher capital and operational expenditures. The second approach saves money by using a single network and point of administration, but the user may have to compromise product feature sets because of the need to use a single vendor.
These are but a subset of the problems and issues associated with wireless access point authentication, and are intended to characterize weaknesses in the prior art by way of example. The foregoing examples of the related art and limitations related therewith are intended to be illustrative and not exclusive. Other limitations of the related art will become apparent to those of skill in the art upon a reading of the specification and a study of the drawings.
The proposed system can offer, among other advantages, improved wireless network functionality. This and other advantages of the techniques described herein will become apparent to those skilled in the art upon a reading of the following descriptions and a study of the several figures of the drawings.
FIGS. 1A and 1B depict an example of a system having a plurality of multi-boot access points (APs).
FIGS. 2A, 2B, and 2C depict a wireless domain that includes a plurality of multi-boot APs.
FIG. 3 depicts an example of a multi-boot AP device.
FIG. 4 depicts an example of a system for changing boot1 statically at an AP.
FIG. 5 depicts an example of a system for changing boot1 dynamically at an AP.
FIG. 6 depicts a flowchart 600 of an example of a method for booting an AP using a boot image.
FIGS. 1A and 1B depict an example of a system 100 having a plurality of multi-boot access points (APs). In the example of FIGS. 1A and 1B, the system 100 includes distribution system 102, and a plurality of multi-boot APs 104-1 to 104-N (referred to collectively as multi-boot APs 104). In the example of FIG. 1A, the system 100 includes a station 110 that is associated, for illustrative purposes, with the multi-boot AP 104-2. Presumably, since the station 106 has associated with the multi-boot AP 104-2, the multi-boot AP 104-2 has booted software that enables operation as a traditional AP. However, any of the multi-boot APs 104 can be switched to a different mode by booting different software.
In the example of FIG. 1B, the multi-boot AP 104-2 becomes aware that the station 106 is a rogue 108. When the multi-boot AP 104-2 becomes aware of the rogue 108, the association ends. Although in the example of FIG. 1B the rogue 108 appears to be disassociated from the multi-boot AP 104-2, the rogue 108 could be detected before an actual association with the multi-boot AP 104-2.
The determination that the station 106 is the rogue 108 may be made at the distribution system 102, or by some other one or more of the multi-boot APs 104 that are configured in, for example, a sensor mode. The multi-boot AP 104-2 can be rebooted with different software that gives the multi-boot 104-2, e.g., sensor functionality to help deal with the rogue 108 with, e.g., countermeasures. In an illustrative embodiment, when the multi-boot AP 104-2 is in sensor mode, no association is possible. Some of the advantages of the system 100 are explored later.
FIGS. 2A, 2B, and 2C depict a wireless domain 200 that includes a plurality of multi-boot APs. The wireless domain 200 may include, by way of example but not limitation, a Trapeze Networks, Inc. MOBILITY DOMAIN™ wireless domain. In the example of FIG. 2A, the wireless domain 200 includes a plurality of multi-boot APs 202 configured in network connectivity mode (APs 202) and a plurality of multi-boot APs 204 configured in sensor mode (sensors 204). The APs 202 and the sensors 204 are organized in an arbitrary or implementation-specific pattern in the mobility domain 200.
In the example of FIG. 2B, a rogue 206 is detected in the wireless domain 200. When the rogue 206 is detected, an alarm may be generated. The alarm can lead to a change in the functionality of the APs 202 and/or sensors 204. One example of a change is illustrated in the example of FIG. 2C.
In the example of FIG. 2C, APs 202 in the vicinity of the rogue 206 are switched to sensors 204. For illustrative purposes, the changed sensors are shaded in the example of FIG. 2C. In an illustrative embodiment, the determination as to which APs to change to sensors may depend upon implementation-specific configurations or capabilities. For example, APs may be changed to sensors when a risk score exceeds a threshold value.
In another illustrative embodiment, the threshold value may be set, and the risk score may increase based upon activities or events associated with a station. In another illustrative embodiment, the number of APs to convert is also either statically or dynamically configurable. For example, the number of APs converted may be based upon the severity of an event that triggers the conversion. In another illustrative embodiment, multiple APs may be converted for other reasons. For example, if at least three APs are in sensor mode, then triangulation may be facilitated. Additional APs may improve the accuracy of a triangulation technique.
In another illustrative embodiment, the amount of investigation predicted to be required may have a bearing on the number of APs converted. In another illustrative embodiment, the system may convert APs depending upon the location of the event that triggers the conversion. In another illustrative embodiment, the location of the APs may have a bearing upon the choice of APs to convert. In another illustrative embodiment, the amount of load on an AP may have a bearing on whether the AP is converted. For example, if an AP that has a lot of stations associated with it is selected for conversion to a sensor, it may be decided that the conversion is not worth the disruption of service to the associated stations, if any.
FIG. 3 depicts an example of a multi-boot AP device 300. In the example of FIG. 3, the device 300 includes memory 302, a processor 304, one or more radios 306-1, 306-2 (referred to collectively as radios 306), a primary boot 308, one or more supplemental boots 310-1, 310-2 (referred to collectively as supplemental boots 310), one or more network interfaces 312-1, 312-2 (referred to collectively as network interfaces 312), and a bus 314 to which each of the other components are coupled.
In an illustrative embodiment, the memory 302 may be primary memory such as random access memory (RAM). Any applicable known or convenient memory may be used. In an illustrative embodiment, the processor 304 may be a central processing unit (CPU), a microprocessor, or some other processor capable of executing code stored in the memory 302. Any applicable known or convenient processor may be used. In an illustrative embodiment, the radios 306 may be set to work on the same technology/protocol. The radios may have different configurations, such as different channel operations or modes. The radios 306 may also be set to work on different technology/protocols, such as 802.11a for one and 802.11b/g for another. Any known or convenient radio technology may be used.
In an illustrative embodiment, the primary boot 308 is embodied in a computer-readable medium. The computer-readable medium may include, by way of example but not limitation, flash memory. In an illustrative embodiment, the supplemental boots 310 are embodied in a computer-readable medium, as well. In an illustrative embodiment, the network interfaces 312 may include Ethernet interfaces. However, any applicable known or convenient network interfaces could be used.
In an illustrative embodiment that has two boot partitions, boot0 and boot1, the primary boot 308 is the first boot partition, boot0, and a supplemental boot 310-1 is the second boot partition, boot1. (In this illustrative embodiment, there is only one supplemental boot.) The device 300 will first attempt to boot from the boot1. If that fails, or if the boot1 partition is marked bad, it will fall back to boot0.
In a specific implementation, Trapeze Networks software may be loaded into boot0, and third-party software into boot1. That way, the device 300 will boot under control of third-party software. To switch back, the boot1 partition is marked bad, which causes the device 300 to fall back to Trapeze Networks software. In at least one implementation, the Trapeze Networks software is read-only so that the image is always available, but this is an implementation-specific decision. In this implementation, only one third-party software image is provided in boot1, but it can be swapped out for another image.
FIG. 4 depicts an example of a system 400 for changing boot1 statically at an AP. As used herein, changing boot1 statically refers to making the change by an administrator. Dynamically changing boot1 on the other hand, which is discussed later with reference to FIG. 5, involves changing boot1 in accordance with detected events, a schedule, or other environmental stimuli.
In the example of FIG. 4, the system 400 includes a network administrator 402, a management system 404, a switch 406, and an AP 408. The network administrator 402 may include a human and/or artificial entity. The management system 404 may be embodied in a computer-readable medium and may include, by way of example but not limitation, a TRAPEZE NETWORKS RINGMASTER™ management system. The switch 406 may include, by way of example but not limitation, a MOBILITY EXCHANGE™ or MX® switch. The AP may include a MOBILITY POINT™ or MP® AP.
In the example of FIG. 4, the switch 406 includes a primary boot image 410, one or more supplemental boot images 412-1 to 412-N (referred to collectively as the supplemental boot images 412), and an AP configuration database 414. The AP 408 includes the primary boot image 410 (boot0) and one of the supplemental boot images 412 (boot1).
In the example of FIG. 4, in operation, the network administrator 402 may trigger changes to boot1 at the AP 408 using the management system 404. The control application 404, upon receiving an appropriate command from the network administrator 402 sends a command to the switch 406 to change boot1, as appropriate. The network administrator 402 may also enter the appropriate command to the switch 406. The network administrator 402 may or may not be able to also change boot0 at the AP 408 using CLI or other commands. However, it may be desirable to provide the capability of allowing installation of the primary boot image at installation or re-installation.
When the command is received at the switch 406, the AP configuration database 414 on the switch 406 is updated to indicate that the AP 408 should use one of the supplemental boot images 412. The switch 406 then provides the appropriate boot image of the supplemental boot images 412 to the AP 408, which the AP 408 stores as boot1.
While the example of FIG. 4 depicts components that may be used for static AP boot image installation, in some embodiments it may be desirable to add dynamic AP boot image installation (or switching between boot images at the AP). Some examples of events leading to dynamic conversion may include by way of example but not limitation:
Automatic conversion of an AP to an IDS sensor based on an alarm.
Automatic conversion of all APs to IDS sensors based on time, so that the entire wireless network stops offering service when the facility closes and instead runs an intrusion detection application. The conversion would be reversed when the facility re-opens so that service is again provided to users.
By automating the conversion in a management system, it may be possible to select the “best” AP for conversion. In the case of a rogue, it will likely be detected by several APs. In an illustrative embodiment, the management system can select an AP based on a policy that includes the strongest signal strength, to pick the “closest” AP, or the least loaded AP, so as to minimize user disruption.
The management system can manage AP conversions so as to ensure that a minimum set of APs are being used to provide service and prevent service from falling below a threshold. Likewise, the management system can manage the AP pool so that a minimum level of third-party functionality is maintained.
The management system can assess threat levels based on, for example, a risk-based score so that there is a minimum threshold score for conversion, and progressively higher scores result in conversion of larger numbers of APs to security services.
The management system can link conversion events to a rollback, so that an AP can be “leased” to a third-party application and reclaimed at the end of a given time duration. It would also be possible for that application to extend its lease.
FIG. 5 depicts an example of a system 500 for changing boot images dynamically at an AP. The system 500 includes a management system 502, one or more third party applications 504-1 to 504-N (referred to collectively as third party applications 504), one or more wireless domains 506-1 to 506-N (referred to collectively as wireless domains 506), a server 508, a switch 510, and an AP 512.
The third party applications 504 include applications that provide functionality to the server 508 that may be of use in a wireless domain. For example, the third party applications 504 may include security applications. The wireless domains 506 provide RF data to the server 508. It should be noted that the switch 510 may be included in one of the wireless domains 506, and may provide RF data (not shown).
The server 508 may include an AP selector 514, a scheduler 516, AP images 518, and a command system 520. The AP selector 514 can receive requests for conversion from multiple sources and unify them. For example, the AP selector 514 may receive input from the third party applications 504, the wireless domains 506 (e.g., in the form of RF data), or from other applicable sources that serve to improve the accuracy of the AP selector 514 (not shown). The AP selector 514 may include an engine for making probabilistic assessments of risk prior to image selection. The AP selector may initially convert a few APs on the first request from a third-party system, and progressively add more if the situation is not resolved. The AP selector 514, after determining a course of action based upon the risk assessment, provides a command to the command system 520.
The scheduler 516 may include a timer that is set according to implementation-specific parameters. For example, the timer may be associated with a running time between conversion of APs, times when an enterprise is open (e.g., switching to network connectivity mode during work hours), or some other schedule. The scheduler 516 provides a command to the command system 520 based upon the configured schedule(s).
The AP images 518 are available to the command system 520. It may be that the AP images 518 are not needed even when an AP image is to be changed. For example, the AP 512 may include multiple boot images, including the image to which the switch 510 (as instructed by the command system 520) attempts to switch the AP 512. It may be that the AP images 518 are needed because the AP 512 can only hold a single image (requiring a new image with each AP image change), or because the AP 512 does not include the image that is needed based upon the desired functionality.
Using techniques described herein, multiple IDS partners may be used for statistical defense against attacks. APs could also be dedicated on-demand to location functions and “spotlighting” particular client devices.
FIG. 6 depicts a flowchart 600 of an example of a method for booting an AP using a boot image. This method and other methods are depicted as serially arranged modules. However, modules of the methods may be reordered, or arranged for parallel execution as appropriate. In the example of FIG. 6, the flowchart 600 starts at module 602 where a plurality of software images are provided. The software images may be provided at a server or at an AP.
In the example of FIG. 6, the flowchart 600 continues to module 604 where a boot image is selected from the plurality of software images. The boot image may be selected after a determination is made as to the desired functionality for an AP at a given time. The determination may be based upon, for example, risk assessment, according to a schedule, or to sign a spotlight on a particular station.
In the example of FIG. 6, the flowchart 600 continues to module 606 where an AP is booted using the boot image. Then the flowchart 600 ends. Presumably, the AP then operates in accordance with the functionality of the boot image.
As used herein, a wireless network refers to any type of wireless network, including but not limited to a structured network or an ad hoc network. Data on a wireless network is often encrypted. However, data may also be sent in the clear, if desired. With encrypted data, a rogue device will have a difficult time learning any information (such as passwords, etc.) from clients before countermeasures are taken to deal with the rogue. The rogue may be able to confuse the client, and perhaps obtain some encrypted data, but the risk is minimal (even less than for some wired networks).
It should be noted that not all technologies include the term AP in the literature. For example, SGSN technology does not refer to an access point as an “AP.” However, all wireless access technologies require something comparable (i.e., a node at which wireless communications are received and/or transmitted). For example, an independent basic service set (BSS) includes stations that access the service area by directly communicating with one another; thus, the access nodes are the stations themselves. Accordingly, AP is considered to be generally applicable to any technology, regardless of actual verbiage used to describe a BSS with equivalent functionality.
a plurality of software images embodied in a computer-readable medium;
a management interface through which one of the plurality of software images is designated as a boot image;
a processor that implements the boot image in a boot procedure;
radio hardware through which functionality associated with the boot image is applied to a wireless domain.
2. The device of claim 1, wherein the plurality of software sets include a primary software set and one or more subordinate software sets.
3. The device of claim 1, wherein at least one of the software sets is associated with wireless network connectivity.
4. The device of claim 1, wherein at least one of the software sets is associated with wireless network security.
5. The device of claim 1, further comprising an interface through which new software images may be received.
6. The device of claim 1, wherein the management interface is implemented using XML.
an access point (AP), including a management interface, capable of booting from a plurality of software sets;
a management engine embodied in a computer-readable medium;
wherein, in operation, the management engine selects one of the plurality of software sets with which the AP boots through the management interface of the AP.
8. The system of claim 7, wherein the plurality of software sets include a primary software set and one or more subordinate software sets.
9. The system of claim 7, wherein at least one of the software sets is associated with wireless network connectivity.
10. The system of claim 7, wherein at least one of the software sets is associated with wireless network security.
11. The system of claim 7, wherein, in operation, the management engine receives a selection from an administrator and selects the one of the plurality of software sets in accordance with the selection.
12. The system of claim 7, wherein, in operation, the management engine dynamically selects the one of the plurality of software sets.
13. The system of claim 7, wherein, in operation, the management engine uses time of day to select the one of the plurality of software sets.
14. The system of claim 7, wherein, in operation, the management engine prevents observed devices from obtaining wireless connectivity at particular times of day.
15. The system of claim 7, wherein, in operation, the management engine selects the one of the plurality of software sets to enable more detailed investigation of an event.
16. The system of claim 7, further comprising an independent management system, wherein the management engine is included in the independent management system.
providing a plurality of software images;
selecting a boot image from the plurality of software images;
booting an access point (AP) using the boot image.
18. The method of claim 17, further comprising selecting the boot image according to time of day.
19. The method of claim 17, further comprising selecting the boot image to investigate an event.
20. The method of claim 17, wherein the boot image is a first boot image, further comprising:
setting a risk threshold;
assigning a risk score based upon events in a wireless environment;
selecting a second boot image from the plurality of software images if the risk score exceeds the risk threshold.
US11966912 2006-12-28 2007-12-28 Application-aware wireless network system and method Active 2029-07-19 US7865713B2 (en)
US87790706 true 2006-12-28 2006-12-28
US11966912 US7865713B2 (en) 2006-12-28 2007-12-28 Application-aware wireless network system and method
US20080162921A1 true US20080162921A1 (en) 2008-07-03
US7865713B2 true US7865713B2 (en) 2011-01-04
ID=39585731
US11966912 Active 2029-07-19 US7865713B2 (en) 2006-12-28 2007-12-28 Application-aware wireless network system and method
US (1) US7865713B2 (en)
WO (1) WO2008083339A3 (en)
US4291401A (en) 1978-11-30 1981-09-22 Ebauches Bettlach S.A. Device for securing a watch dial to a watch-movement plate
US4760586A (en) 1984-12-29 1988-07-26 Kyocera Corporation Spread spectrum communication system
US4933953A (en) 1987-09-10 1990-06-12 Kabushiki Kaisha Kenwood Initial synchronization in spread spectrum receiver
US5008899A (en) 1989-07-03 1991-04-16 Futaba Denshi Kogyo Kabushiki Kaisha Receiver for spectrum spread communication
US5187575A (en) 1989-12-29 1993-02-16 Massachusetts Institute Of Technology Source adaptive television system
US5793303A (en) 1995-06-20 1998-08-11 Nec Corporation Radio pager with touch sensitive display panel inactive during message reception
US6005853A (en) 1995-10-13 1999-12-21 Gwcom, Inc. Wireless network access scheme
US6188649B1 (en) 1996-06-28 2001-02-13 Matsushita Electric Industrial Co., Ltd. Method for reading magnetic super resolution type magneto-optical recording medium
US6240078B1 (en) 1997-08-20 2001-05-29 Nec Usa, Inc. ATM switching architecture for a wireless telecommunications network
US6356758B1 (en) 1997-12-31 2002-03-12 Nortel Networks Limited Wireless tools for data manipulation and visualization
US20020052205A1 (en) 2000-01-26 2002-05-02 Vyyo, Ltd. Quality of service scheduling scheme for a broadband wireless access system
US6393290B1 (en) 1999-06-30 2002-05-21 Lucent Technologies Inc. Cost based model for wireless architecture
US20020095486A1 (en) 2001-01-12 2002-07-18 Paramvir Bahl Systems and methods for locating mobile computer users in a wireless network
US6496290B1 (en) 1998-01-31 2002-12-17 Lg Telecom, Inc. Optic repeater system for extending coverage
US20030018889A1 (en) 2001-07-20 2003-01-23 Burnett Keith L. Automated establishment of addressability of a network device for a target network enviroment
US6512916B1 (en) 2000-02-23 2003-01-28 America Connect, Inc. Method for selecting markets in which to deploy fixed wireless communication systems
US6661787B1 (en) 1998-05-21 2003-12-09 3Com Technologies Integrated data table in a network
US20040019857A1 (en) 2002-01-31 2004-01-29 Steven Teig Method and apparatus for specifying encoded sub-networks
US6687498B2 (en) 2000-08-14 2004-02-03 Vesuvius Inc. Communique system with noncontiguous communique coverage areas in cellular communication networks
US20040025044A1 (en) 2002-07-30 2004-02-05 Day Christopher W. Intrusion detection system
US20040047320A1 (en) 2002-09-09 2004-03-11 Siemens Canada Limited Wireless local area network with clients having extended freedom of movement
US20040064560A1 (en) 2002-09-26 2004-04-01 Cisco Technology, Inc., A California Corporation Per user per service traffic provisioning
US20040120370A1 (en) 2002-08-13 2004-06-24 Agilent Technologies, Inc. Mounting arrangement for high-frequency electro-optical components
WO2004095800A1 (en) 2003-04-17 2004-11-04 Cisco Technology, Inc 802.11 using a compressed reassociation exchange to facilitate fast handoff
US20040230370A1 (en) 2003-05-12 2004-11-18 Assimakis Tzamaloukas Enhanced mobile communication device with extended radio, and applications
US20050058132A1 (en) 2002-05-20 2005-03-17 Fujitsu Limited Network repeater apparatus, network repeater method and network repeater program
US20050128989A1 (en) 2003-12-08 2005-06-16 Airtight Networks, Inc Method and system for monitoring a selected region of an airspace associated with local area networks of computing devices
US20050180358A1 (en) 2004-02-13 2005-08-18 Trapeze Networks, Inc. Station mobility between access points
US20050276218A1 (en) 2002-07-05 2005-12-15 Alcatel Resource admission control in an access network
US20060045050A1 (en) 2004-08-27 2006-03-02 Andreas Floros Method and system for a quality of service mechanism for a wireless network
GB2429080A (en) * 2005-08-08 2007-02-14 Giga Byte Tech Co Ltd Dual-boot combined wireless adapter and access point
US20070086378A1 (en) 2005-10-13 2007-04-19 Matta Sudheer P C System and method for wireless network monitoring
US20080014916A1 (en) * 2006-07-11 2008-01-17 Wistron Neweb Corp. Wireless network connection method and mobile phone using the same
US20080117822A1 (en) 2006-06-09 2008-05-22 James Murphy Wireless routing selection system and method
US7788475B2 (en) * 2006-12-28 2010-08-31 Intel Corporation Booting utilizing electronic mail
DE102004028555A1 (en) * 2004-06-15 2006-02-16 Zf Friedrichshafen Ag Pedal arrangement for a motor vehicle
Acampora and Winters, IEEE Communications Magazine, 25(8):11-20 (1987).
Acampora and Winters, IEEE Journal on selected Areas in Communications. SAC-5:796-804 (1987).
Bing and Subramanian, IEEE, 1318-1322 (1997).
Co-pending U.S. Appl. No. 10/778,901, filed Feb. 13, 2004.
Co-pending U.S. Appl. No. 11/326,966, filed Jan. 5, 2006.
Co-pending U.S. Appl. No. 11/330,877, filed Jan. 11, 2006.
Co-pending U.S. Appl. No. 11/331,789, filed Jan. 14, 2006.
Co-pending U.S. Appl. No. 11/351,104, filed Feb. 8, 2006.
Co-pending U.S. Appl. No. 11/377,859, filed Mar. 15, 2006.
Co-pending U.S. Appl. No. 11/400,165, filed Apr. 5, 2006.
Co-pending U.S. Appl. No. 11/417,830, filed May 3, 2006.
Co-pending U.S. Appl. No. 11/445,750, filed Jun. 1, 2006.
Co-pending U.S. Appl. No. 11/487,722, filed Jul. 17, 2006.
Co-pending U.S. Appl. No. 11/592,891, filed Nov. 3, 2006.
Co-pending U.S. Appl. No. 11/595,119, filed Nov. 10, 2006.
Co-pending U.S. Appl. No. 11/604,075, filed Nov. 22, 2006.
Co-pending U.S. Appl. No. 11/643,329, filed Dec. 20, 2006.
Co-pending U.S. Appl. No. 11/784,307, filed Apr. 5, 2007.
Co-pending U.S. Appl. No. 11/975,134, filed Oct. 16, 2007.
Co-pending U.S. Appl. No. 12/131,028, filed May 3, 2008.
Co-pending U.S. Appl. No. 12/336,492, filed Dec. 16, 2008.
Co-pending U.S. Appl. No. 12/401,073, filed Mar. 10, 2009.
Co-pending U.S. Appl. No. 12/489,295, filed Jun. 22, 2009.
Co-pending U.S. Appl. No. 12/491,201, filed Jun. 24, 2009.
Co-pending U.S. Appl. No. 12/500,392, filed Jul. 9, 2009.
Durgin, et al., "Measurements and Models for Radio Path Loss and Penetration Loss in and Around Homes and Trees at 5.85 GHz", IEEE Transactions on Communications, vol. 46, No. 11, Nov. 1998.
Final Office Action Mailed Aug. 27, 2008 in Co-pending U.S. Appl. No. 11/377,859, filed Mar. 15, 2006.
Final Office Action Mailed Jan. 5, 2010 in Co-pending U.S. Appl. No. 11/595,119, filed Nov. 10, 2006.
Final Office Action Mailed Jul. 20, 2009 in Co-pending U.S. Appl. No. 11/592,891, filed Nov. 3, 2006.
Final Office Action Mailed Jun. 10, 2009 in Co-pending U.S. Appl. No. 11/351,104, filed Feb. 8, 2006.
Final Office Action Mailed Mar. 13, 2009 in Co-pending U.S. Appl. No. 11/330,877, filed Jan. 11, 2006.
Final Office Action Mailed May 28, 2009 in Co-pending U.S. Appl. No. 11/417,830, filed May 3, 2006.
Final Office Action Mailed Oct. 23, 2008 in Co-pending U.S. Appl. No. 11/331,789, filed Jan. 14, 2006.
Fortune et al., IEEE Computational Science and Engineering, "Wise Design of Indoor Wireless Systems: Practical Computation and Optimization", pp. 58-68 (1995).
Freret et al., Applications of Spread-Spectrum Radio to Wireless Terminal Communications, Conf. Record, Nat'l Telecom. Conf., Nov. 30-Dec. 4, 1980.
Freret et al., Applications of Spread-Spectrum Radio to Wireless Terminal Coummunications, Conf. Record. Nat'l Telecom. Conf., Nov. 30-Dec. 4, 1980.
Geier, Jim, Wireless Lans Implementing Interoperable Networks, Chapter 3 (pp. 89-125) Chapter 4 (pp. 129-157) Chapter 5 (pp. 159-189) and Chapter 6 (pp. 193-234), 1999, United States.
Ho et al., "Antenna Effects on Indoor Obstructed Wireless Channels and a Deterministic Image-Based Wide-Based Propagation Model for In-Building Personal Communications Systems", International Journal of Wireless Information Networks, vol. 1, No. 1, 1994.
Ho et al., "Antenna Effects on Indoor Obstructed Wireless Channels and a Deterministic Image-Based Wide-Based Propogation Model for In-Building Personal Communications Systems", International Journal of Wireless Information Networks, vol. 1, No. 1, 1994.
International Search Report PCT/US05/004702 dated Aug. 10, 2006, pp. 1-3.
International Search Report PCT/US06/09525 dated Sep. 13, 2007, pp. 1-2.
International Search Report PCT/US06/40498 dated Dec. 28, 2007, pp. 1-2.
International Search Report PCT/US07/089134 dated Apr. 10, 2008, pp. 1-3.
International Seartsh Report PCT/US07/14847 dated Apr. 1, 2008, pp. 1-4.
Kim at al., "Radio Propogation Measurements and Prediction Using Three-Dimensional Ray Tracing in Urban Environments at 908 MHz and 1.9 GHz", IEEE Transactions on Vehicular Technology, vol. 48, No. 3, May 1999.
Kim et al., "Radio Propagation Measurements and Prediction Using Three-Dimensional Ray Tracing in Urban Environments at 908 MHz and 1.9 GHz", IEEE Transactions on Vehicular Technology, vol. 48, No. 3, May 1999.
Kleinrock and Scholl, Conference record 1977 ICC vol. 2 of 3, June 12-15 Chicago Illinois "Packet Switching in radio Channels: New Conflict-Free Multiple Access Schemes for a Small Number of data Useres", (1977).
Kleinrock and Scholl, Conference record 1977 ICC vol. 2 of 3, June 12-15 Chicago Illinois "Packet Switching in radio Channels: New Conflict-Free Multiple Access Schemes for a Small Number of data Users", (1977).
LAN/MAN Standards Committee of the IEEE Computer Society, Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications: Higher Speed Physical Layer Extension in the 2.4 GHz Band, IEEE Std. 801.11b (1999).
LAN/MAN Standars Committee of the IEEE Computer Society, Part 11:Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications:Higher Speed Physical Layer Extension in the 2.4 GHz Band, IEEE Std. 802.11b (1999).
Non-Final Mailed Aug. 19, 2008 in Co-pending U.S. Appl. No. 11/400,165, filed Apr. 5, 2006.
Non-Final Office Action Mailed Aug. 5, 2009 in Co-pending U.S. Appl. No. 11/331,789, filed Jan. 14, 2006.
Non-Final Office Action Mailed Aug. 6, 2009 in Co-pending U.S. Appl. No. 11/330,877, filed Jan. 11, 2006.
Non-Final Office Action Mailed Aug. 7, 2009 in Co-pending U.S. Appl. No. 11/487,722, filed Jul. 17, 2006.
Non-Final Office Action Mailed Dec. 2, 2009 in Co-pending U.S. Appl. No. 11/351,104, filed Feb. 8, 2006.
Non-Final Office Action Mailed Feb. 17, 2009 in Co-pending U.S. Appl. No. 11/445,750, filed Jun. 1, 2006.
Non-Final Office Action Mailed Jan. 14, 2009 in Co-pending U.S. Appl. No. 11/592,891, filed Nov. 3, 2006.
Non-Final Office Action Mailed Jan. 8, 2008 in Co-pending U.S. Appl. No. 11/377,859, filed Mar. 15, 2006.
Non-Final Office Action Mailed Jul. 21, 2009 in Co-pending U.S. Appl. No. 11/595,119, filed Nov. 10, 2006.
Non-Final Office Action Mailed Jun. 13, 2008 in Co-pending U.S. Appl. No. 11/331,789, filed Jan. 14, 2006.
Non-Final Office Action Mailed Nov. 10, 2008 in Co-pending U.S. Appl. No. 11/326,966, filed Jan. 5, 2006.
Non-Final Office Action Mailed Nov. 14, 2008 in Co-pending U.S. Appl. No. 11/417,830, filed May 3, 2006.
Non-Final Office Action Mailed Oct. 28, 2008 in Co-pending U.S. Appl. No. 11/351,104, filed Feb. 8, 2006.
Non-Final Office Action Mailed Sep. 11, 2008 in Co-pending U.S. Appl. No. 11/330,877, filed Jan. 11, 2006.
Non-Final Office Action Mailed Sep. 22, 2009 in Co-pending U.S. Appl. No. 11/784,307, filed Apr. 5, 2007.
Notice of Allowance Mailed Apr. 23, 2009 in Co-pending U.S. Appl. No. 11/400,165, filed Apr. 5, 2006.
Notice of Allowance Mailed Feb. 23, 2010 in Co-pending U.S. Appl. No. 11/331,789, filed Jan. 14, 2006.
Notice of Allowance Mailed Feb. 26, 2007 in Co-pending U.S. Appl. No. 10/778,901, filed Feb. 13, 2004.
Notice of Allowance Mailed Feb. 27, 2009 in Co-pending U.S. Appl. No. 11/377,859, filed Mar. 15, 2006.
Notice of Allowance Mailed Jun. 11, 2009 in Co-pending U.S. Appl. No. 11/326,966, filed Jan. 5, 2006.
Notice of Allowance Mailed Jun. 16, 2009 in Co-pending U.S. Appl. No. 11/445,750, filed Jun. 1, 2006.
Notice of Allowance Mailed Mar. 19, 2010 in Co-pending U.S. Appl. No. 11/487,722, filed Jul. 17, 2006.
Okamoto and Xu, IEEE, Proceeding so of the 13th Annual Hawaii International Conference on System Sciences, pp. 54-63 (1997).
Okamoto and Xu, IEEE, Proceedings of the 13th Annual Hawaii International Conference on System Sciences, pp. 54-63 (1997).
Panjawani et al., "Interactive Computation of Coverage Regions for Wireless Communication in Multifloored Indoor Environments", IEEE Journal on Selected Areas in Communications, vol. 14, No. 3, Apr. 1996.
Panjwani et al., "Interactive Computation of Coverage Regions for Wireless Communication in Multifloored Indoor Environments", IEEE Journal on Selected Areas in Communications, vol. 14, No. 3, Apr. 1996.
Perram and Martinez, "Technology Developments for Low-Cost Residential Alarm Systems", Proceedings 1977 Carnahan Conference on Crime Countermeasures, April 6-8, pp. 45-50 (1977).
Piazzi et al., "Achievable Accuracy of Site-Specific Path-Loss Predictions in Residential Environments", IEEE Transactions on Vehicular Technology, vol. 48, No. 3, May 1999.
Puttini, R., Percher, J., Me, L., and de Sousa, R. 2004. A fully distributed IDS for MANET. In Proceedings of the Ninth international Symposium on Computers and Communications 2004 vol. 2 (Iscc''04)—vol. 02 (Jun. 28-Jul. 1, 2004). ISCC. IEEE Computer Society, Washington, DC, 331-338.
Puttini, R., Percher, J., Me, L., and De Sousa, R. 2004. A fully distributed IDS for MANET. In Proceedings of the Ninth international Symposium on Computers and Communications 2004 vol. 2 (Iscc''04)—vol. 02 (Jun. 28-Jul. 1, 2004). ISCC. IEEE Computer Society. Washington. DC. 331-338.
Seidel et al, "Site-Specific Propagation Prediction for Wireless In-Building Personal Communications System Design", IEEE Transactions on Vehicular Technology, vol. 43, No. 4, Nov. 1994.
Seidel et al., "Site-Specific Propagation Prediction for Wireless In-Building Personal Communications System Design", IEEE Transactions on Vehicular Technology, vol. 43, No. 4, Nov. 1994.
Skidmore et al., "Interactive Coverage Region and System Design Simulation for Wireless Communication Systems in Multi-floored Indoor Environments, SMT Plus" IEEE ICUPC '96 Proceedings (1996).
Skidmore et al., "Interactive Coverage Region and System Design Simulation for Wireless Communication Systems in Multi-floored Indoor Environments, SMT Plus", IEEE ICUPC '96 Proceedings (1996).
U.S. Appl. No. 11/326,966, filed Jan. 2006, Taylor.
U.S. Appl. No. 11/330,877, filed Jan. 2006, Matta.
U.S. Appl. No. 11/331,789, filed Jan. 2006, Matta et al.
U.S. Appl. No. 11/351,104, filed Feb. 2006, Tiwari.
U.S. Appl. No. 11/377,859, filed Mar. 2006, Harkins.
U.S. Appl. No. 11/400,165, filed Apr. 2006, Tiwari.
U.S. Appl. No. 11/417,830, filed May 2006, Morain.
U.S. Appl. No. 11/417,993, filed May 2006, Jar et al.
U.S. Appl. No. 11/437,387, filed May 2006, Zeldin et al.
U.S. Appl. No. 11/437,537, filed May 2006, Freund et al.
U.S. Appl. No. 11/437,538, filed May 2006, Zeldin.
U.S. Appl. No. 11/437,582, filed May 2006, Bugwadia et al.
U.S. Appl. No. 11/445,750, filed May 2006, Matta.
U.S. Appl. No. 11/451,704, filed Jun. 2006, Riley.
U.S. Appl. No. 11/487,722, filed Jul. 2006, Simons et al.
U.S. Appl. No. 11/592,891, filed Nov. 2006, Murphy, James.
U.S. Appl. No. 11/595,119, filed Nov. 2006, Murphy, James.
U.S. Appl. No. 11/604,075, filed Nov. 2006, Murphy et al.
U.S. Appl. No. 11/643,329, filed Dec. 2006, Towari, Manish.
U.S. Appl. No. 11/648,359, filed Dec. 2006, Gast et al.
U.S. Appl. No. 11/690,654, filed Mar. 2007, Keenly et al.
U.S. Appl. No. 11/801,964, filed May 2007, Simone et al.
U.S. Appl. No. 11/845,029, filed Aug. 2007, Gast, Mathew S.
U.S. Appl. No. 11/852,234, filed Sep. 2007, Gast et al.
U.S. Appl. No. 11/944,346, filed Nov. 2007, Gast, Mathew S.
U.S. Appl. No. 11/970,484, filed Jan. 2008, Gast, Mathew S.
U.S. Appl. No. 11/975,134, filed Oct. 2007, Aragon et al.
U.S. Appl. No. 12/077,051, filed Mar. 2008, Gast, Mathew S.
Ullmo et al., "Wireless Propogation in Buildings: A Statistic Scattering Approach", IEEE Transactions on Vehicular Technology, vol. 48, No. 3, May 1999.
Written opinion PCT/US05/004702 dated Aug. 10, 2006, pp. 1-5.
Written Opinion PCT/US06/40498 dated Dec. 28, 2007, pp. 1-5.
Written Opinion PCT/US07/089134 dated Apr. 10, 2008, pp. 1-4.
Written Opinion PCT/US07/14847 dated Apr. 1, 2008, pp. 1-4.
Written Opinlon PCT/US06/09525 dated Sep. 13, 2007, pp. 1-7.
WO2008083339A3 (en) 2008-10-09 application
US20080162921A1 (en) 2008-07-03 application
WO2008083339A2 (en) 2008-07-10 application
US7076655B2 (en) 2006-07-11 Multiple trusted computing environments with verifiable environment identities
US20080276295A1 (en) 2008-11-06 Network security scanner for enterprise protection
US20090271623A1 (en) 2009-10-29 Intersystem mobility security context handling between different radio access networks
EP1772988A1 (en) 2007-04-11 A method, system and apparatus for realizing the data service safety of the mobile communication system
US20060101515A1 (en) 2006-05-11 System and method for monitoring network traffic
US8391834B2 (en) 2013-03-05 Security techniques for device assisted services
US20110151836A1 (en) 2011-06-23 Secure subscriber identity module service
US20070124573A1 (en) 2007-05-31 Method for rapid startup of a computer system
US20130111592A1 (en) 2013-05-02 Mobile application security and management service
US20070043831A1 (en) 2007-02-22 Distribution of software based on scheduled time to deploy software dynamic resource state of systems involved in deployment of software and based upon environmental conditions
US20050216957A1 (en) 2005-09-29 Method and apparatus for protecting a remediated computer network from entry of a vulnerable computer system thereinto
US20140075556A1 (en) 2014-03-13 Threat Detection for Return Oriented Programming
US20120096537A1 (en) 2012-04-19 Basic architecture for secure internet computers
US20070126554A1 (en) 2007-06-07 Multiple RFID reader system and method for controlling multiple RFID readers in the same
US20060129808A1 (en) 2006-06-15 Method and system for distributing security policies
US20090070467A1 (en) 2009-03-12 Enabling access to remote entities in access controlled networks
US20110283138A1 (en) 2011-11-17 Change Tracking and Management in Distributed Applications
US20080189420A1 (en) 2008-08-07 Method and System for Mobilizing a Management Service Platform
US20090077632A1 (en) 2009-03-19 Proactive network attack demand management
US20160373474A1 (en) 2016-12-22 Technologies for secure personalization of a security monitoring virtual network function
US20130117842A1 (en) 2013-05-09 Optimizing performance information collection
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUGWADIA, JAMSHEED;FREUND, YUN;GAST, MATTHEW S.;AND OTHERS;REEL/FRAME:021927/0883;SIGNING DATES FROM 20080214 TO 20080308
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUGWADIA, JAMSHEED;FREUND, YUN;GAST, MATTHEW S.;AND OTHERS;SIGNING DATES FROM 20080214 TO 20080308;REEL/FRAME:021927/0883