Source: http://www.patentgenius.com/patent/8238942.html
Timestamp: 2018-06-25 10:09:41
Document Index: 767891949

Matched Legal Cases: ['art 11', 'Application No. 2007800229623', 'Application No. 02770460', 'Application No. 02770460', 'Application No. 02770460', 'Application No. 02770460', 'Application No. 06006504', 'Application No. 2006', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300', 'art 300']

Wireless station location detection - Patent # 8238942 - PatentGenius
8238942 Wireless station location detection
Application: 11/944,346
Inventors: Gast; Matthew Stuart (San Francisco, CA)
U.S. Class: 455/457; 370/324; 370/331; 370/337; 370/519; 455/522; 455/67.14
Field Of Search: 455/457; 455/67.14; 455/522; 370/324; 370/331; 370/37; 370/519
Foreign Patent Documents: 0 992 921; 1 542 409; 2329801; 2429080; 2000-215169; 2003-234751; 2003274454; 2004-032525; WO 94/03986; WO 99/11003; WO 00/06271; WO 00/18148; WO-02089442; WO 03/085544; WO-2004013986; WO 2004/095192; WO 2004/095800
Other References: Co-pending U.S. Appl. No. 10/235,338, filed Sep. 5, 2002. cited by other.
Notice of Allowance Mailed Jul. 29, 2003 in Co-pending U.S. Appl. No. 10/235,338, filed Sep. 5, 2002. cited by other.
Non-Final Offce Action Mailed Jan. 8, 2003 in Co-pending U.S. Appl. No. 10/235,338, filed Sep. 5, 2002. cited by other.
Notice of Allowance Mailed Mar. 23, 2009 in Co-pending U.S. Appl. No. 11/094,987, filed Mar. 31, 2005. cited by other.
Non-Final Offce Action Mailed Oct. 21, 2008 in Co-pending U.S. Appl. No. 11/094,987, filed Mar. 31, 2005. cited by other.
Final Offce Action Mailed May 23, 2008 in Co-pending U.S. Appl. No. 11/094,987, filed Mar. 31, 2005. cited by other.
Non-Final Offce Action Mailed Dec. 27, 2007, 2009 in Co-pending U.S. Appl. No. 11/094,987, filed Mar. 31, 2005. cited by other.
Co-pending U.S. Appl. No. 12/474,020, filed May 28, 2009. cited by other.
Non-Final Offce Action Mailed Jun. 3, 2010 in Co-pending U.S. Appl. No. 12/474,020, filed May 28, 2009. cited by other.
Co-pending U.S. Appl. No. 09/866,474, filed May 29, 2001. cited by other.
Non-Final Office Action Mailed Jun. 10, 2005 in Co-pending U.S. Appl. No. 09/866,474, filed May 29, 2001. cited by other.
International Search Report of PCT/US2002/028090, Aug. 13, 2003, 3 pages. cited by other.
Bahl et al., "User Location and Tracking in an In-Building Radio Network", Microsoft Research, Feb. 1999. cited by other.
U.S. Appl. No. 11/326,966, filed Jan. 2006, Taylor. cited by other.
U.S. Appl. No. 11/330,877, filed Jan. 2006, Matta. cited by other.
U.S. Appl. No. 11/331,789, filed Jan. 2006, Matta, et al. cited by other.
U.S. Appl. No. 11/351,104, filed Feb. 2006, Tiwari. cited by other.
U.S. Appl. No. 11/377,859, filed Mar. 2006, Harkins. cited by other.
U.S. Appl. No. 11/400,165, filed Apr. 2006, Tiwari. cited by other.
U.S. Appl. No. 11/445,750, filed May 2006, Matta. cited by other.
U.S. Appl. No. 11/417,830, filed May 2006, Morain. cited by other.
U.S. Appl. No. 11/417,993, filed May 2006, Jar et al. cited by other.
U.S. Appl. No. 11/437,537, filed May 2006, Freund et al. cited by other.
U.S. Appl. No. 11/437,538, filed May 2006, Zeldin. cited by other.
U.S. Appl. No. 11/437,387, filed May 2006, Zeldin et al. cited by other.
U.S. Appl. No. 11/437,582, filed May 2006, Bugwadia et al. cited by other.
U.S. Appl. No. 11/451,704, filed Jun. 2006, Riley. cited by other.
U.S. Appl. No. 11/487,722, filed Jul. 2006, Simons et al. cited by other.
U.S. Appl. No. 11/592,891, filed Nov. 2006, Murphy, James. cited by other.
U.S. Appl. No. 11/595,119, filed Nov. 2006, Murphy, James. cited by other.
U.S. Appl. No. 11/604,075, filed Nov. 2006, Murphy et al. cited by other.
U.S. Appl. No. 11/643,329, filed Dec. 2006, Towari, Manish. cited by other.
U.S. Appl. No. 11/648,359, filed Dec. 2006, Gast et al. cited by other.
U.S. Appl. No. 11/690,654, filed Mar. 2007, Keenly et al. cited by other.
U.S. Appl. No. 11/801,964, filed May 2007, Simone et al. cited by other.
U.S. Appl. No. 11/845,029, filed Aug. 2007, Gast, Mathew S. cited by other.
U.S. Appl. No. 11/852,234, filed Sep. 2007, Gast et al. cited by other.
U.S. Appl. No. 11/966,912, filed Dec. 2007, Chesnutt et al. cited by other.
U.S. Appl. No. 11/970,484, filed Jan. 2008, Gast, Mathew S. cited by other.
U.S. Appl. No. 11/975,134, filed Oct. 2007, Aragon et al. cited by other.
U.S. Appl. No. 12/077,051, filed Mar. 2008, Gast, Matthew S. cited by other.
Acampora and Winters, IEEE Communications Magazine, 25(8):11-20 (1987). cited by other.
Acampora and Winters, IEEE Journal on selected Areas in Communications. SAC-5:796-804 (1987). cited by other.
Bing and Subramanian, IEEE, 1318-1322 (1997). cited by other.
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. cited by other.
Freret et al., Applications of Spread-Spectrum Radio to Wireless Terminal Communications, Conf. Record, Nat'l Telecom. Conf., Nov. 30- Dec. 4, 1980. cited by other.
Fortune et al., IEEE Computational Science and Engineering, "Wise Design of Indoor Wireless Systems: Practical Computation and Optimization", p. 58-68 (1995). cited by other.
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. cited by other.
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. cited by other.
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. cited by other.
Kleinrock and Scholl, Conference record 1977 ICC vol. 2 of 3, Jun. 12-15 Chicago Illinois "Packet Switching in radio Channels: New Conflict-Free Multiple Access Schemes for a Small Number of data Useres", (1977). cited by other.
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). cited by other.
Okamoto and Xu, IEEE, Proceeding so of the 13.sup.th Annual Hawaii International Conference on System Sciences, pp. 54-63 (1997). cited by other.
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. cited by other.
Perram and Martinez, "Technology Developments for Low-Cost Residential Alarm Systems", Proceedings 1977 Carnahan Conference on Crime Countermeasures, Apr. 6-8, 1977, pp. 45-50. cited by other.
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. cited by other.
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. cited by other.
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). cited by other.
Ullmo et al., "Wireless Propagation in Buildings: A Statistic Scattering Approach", IEEE Transactions on Vehicular Technology, vol. 48, No. 3, May 1999. cited by other.
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. IEEEComputer Society, Washington, DC, 331-338. cited by other.
U.S. Appl. No. 12/474,020, filed May 28, 2009, Peden, II et al. cited by other.
Radar: An In-Building RF-based User Location and Tracking System, P. Bahl et al., Microsoft Research, Mar. 2000. cited by other.
Evaluation of RSSI-Based Human Tracking, J. Latvala et al, Proceedings for the 2000 European Signal Processing Conference, Sep. 2000. cited by other.
User Location and Tracking in an In-Building Radio Network, P. Bahl et al., Microsoft Research, Feb. 1999. cited by other.
A Software System for Locating Mobile Users: Design, Evaluation, and Lessons, P. Bahl et al., Microsoft Research, Apr. 2000. cited by other.
Chen, et al., "Enabling Location-Based Services on Wireless LANs", 11.sup.th IEEE International Conference, Sep. 28-Oct. 1, 2003, pp. 567-572. cited by other.
Erten, Y. Murat, "A Layered Security Architecture for Corporate 802.11 Wireless Networks", Wireless Telecommunications Symposium, May 14-15, 2004, pp. 123-128. cited by other.
Kleine-Ostmann, T., et al., "A data fusion architecture for enhanced position estimation in wireless networks," IEEE Communications Letters , vol. 5(8), p. 343-345, Aug. 2001. cited by other.
Ultra wideband (UWB) Radios for Precision Location, Third IEEE Workshop on Wireless Local Area Networks, Sep. 27-28, 2001. cited by other.
Barber, S., Monitoring 802.1 Networks, IEEE 802.11, Sydney, NSW, May 13-17, 2002. cited by other.
Bahl, P. and V. Padmanabhan, Radar; An In-Building RF-based User Location and Tracking System, Microsoft Research, Mar. 2000. cited by other.
Latvala, J., J. Syrjarinne, S. Niemi and J. Niittylahti, Patient Tracking in a Hospital Environment Using Extended Kalman-filtering, Proceedings of the 1999 Middle East Conference on Networking, Nov. 1999. cited by other.
Myllymaki, P., T. Roos, H. Tirri, P. Misikangas and J. Sievanen, A Probabilistic Approach to WLAN User Location Estimation, Third IEEE Workshop on Wireless Local Area Networks, Sep. 27-28, 2001. cited by other.
P. Martinez, M. Brunner, J. Quittek, F. Straus, J. Schonwlder, S. Mertens, T. Klie "Using the Script MIB for Policy-based Configuration Management", Technical University Braunschweig, Braunschweig, Germany, 2002. cited by other.
Law, A., "New Service Discovery Protocol," Internet Citation [Online] XP002292473 Retrieved from the Internet: <URL: http://sern.uccalgary.ca.about.lawa/SENG60921/arch/SDP.htm> [retrieved Aug. 12, 2004] (15 pages). cited by other.
Potter, B., and Fleck, B., 802.11 Security, O'Reilly Media Inc., Dec. 2002, 14 pages. cited by other.
McCann, S., et al., "Emergency Services for 802," IEEE 802.11-07/0505r1, Mar. 2007, 27 pages. cited by other.
Di Sorte, D., et al., "On the Performance of Service Publishing in IEEE 802.11 Multi-Access Environment," IEEE Communications Letters, vol. 11, No. 4, Apr. 2007, 3 pages. cited by other.
Microsoft Computer Dictionary, Fifth Edition, Microsoft Corporation, 2002, 2 pages. cited by other.
Thomson, Allan, Cisco Systems, AP Power Down Notification, Power Point slide show; IEEE standards committee meeting Jul. 15, 2008; doc.: IEEE 802.11-08/0759r0, 14 pages. cited by other.
3COM, Wireless LAN Mobility System; Wireless LAN Switch and Controller Configuration Guide, 3COM, Revision A, Oct. 2004, 476 pages. cited by other.
3COM, Wireless LAN Switch Manager (3WXM), 3COM Revision C, Oct. 2004, 8 pages. cited by other.
3COM, Wireless LAN Switch and Controller; Quick Start Guide, 3COM, Revision B, Nov. 2004, 10 pages. cited by other.
3COM, Wireless LAN Mobility System; Wireless LAN Switch and Controller Installation and Basic Configuration Guide, Revision B, Apr. 2005, 496 pages. cited by other.
Johnson, David B, et al., "DSR the Dynamic Source Routing Protocol for Multi-Hop Wireless Ad Hoc Networks," Computer Science Department, Carnegie Mellon University, Nov. 3, 2005 (http://monarch.cs.rice.edu/monarch-papers/dsr-chapter00.pdf). cited byother.
Information Sciences Institute, RFC-791--Internet Protocol, DARPA, Sep. 1981. cited by other.
U.S. Appl. No. 12/603,391, filed Oct. 21, 2009. cited by other.
U.S. Appl. No. 12/763,057, filed Apr. 19, 2010. cited by other.
U.S. Appl. No. 13/006,950, filed Jan. 14, 2011. cited by other.
U.S. Appl. No. 13/017,801, filed Jan. 31, 2011. cited by other.
Office Action for U.S. Appl. No. 11/784,307, mailed Sep. 22, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/784,307, mailed Jun. 14, 2010. cited by other.
Non-Final Office Action for U.S. Appl. No. 11/377,859, mailed Jan. 8, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/377,859, mailed Aug. 27, 2008. cited by other.
Office Action for U.S. Appl. No. 12/401,073, mailed Aug. 23, 2010. cited by other.
Final Office Action for U.S. Appl. No. 12/401,073, mailed Apr. 1, 2011. cited by other.
Office Action for U.S. Appl. No. 12/401,073, mailed Sep. 20, 2011. cited by other.
Office Action for U.S. Appl. No. 11/326,966, mailed Nov. 14, 2008. cited by other.
Office Action for U.S. Appl. No. 12/500,392, mailed Jun. 20, 2011. cited by other.
Office Action for U.S. Appl. No. 11/400,165, mailed Aug. 19, 2008. cited by other.
Office Action for U.S. Appl. No. 12/489,295, mailed Apr. 27, 2011. cited by other.
Office Action for U.S. Appl. No. 11/330,877, mailed Sep. 11, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/330,877, mailed Mar. 13, 2009. cited by other.
Office Action for U.S. Appl. No. 11/330,877, mailed Aug. 6, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/330,877, mailed Apr. 22, 2010. cited by other.
Office Action for U.S. Appl. No. 11/330,877, mailed Jan. 13, 2011. cited by other.
Final Office Action for U.S. Appl. No. 11/330,877, mailed May 27, 2011. cited by other.
Office Action for U.S. Appl. No. 11/351,104, mailed Oct. 28, 2008. cited by other.
Office Action for U.S. Appl. No. 11/351,104, mailed Dec. 2, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/351,104, mailed Jun. 10, 2009. cited by other.
Office Action for U.S. Appl. No. 11/351,104, mailed May 26, 2010. cited by other.
Office Action for U.S. Appl. No. 11/351,104, mailed Nov. 29, 2010. cited by other.
Office Action for U.S. Appl. No. 11/351,104, mailed Jul. 26, 2011. cited by other.
Office Action for U.S. Appl. No. 11/437,537, mailed Dec. 23, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/437,537, mailed Jul. 16, 2009. cited by other.
Office Action for U.S. Appl. No. 11/331,789, mailed Jun. 13, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/331,789, mailed Oct. 23, 2008. cited by other.
Office Action for U.S. Appl. No. 11/331,789, mailed Aug. 5, 2009. cited by other.
Office Action for U.S. Appl. No. 12/785,362, mailed Apr. 22, 2011. cited by other.
Office Action for U.S. Appl. No. 11/417,830, mailed Nov. 14, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/417,830, mailed May 28, 2009. cited by other.
Office Action for U.S. Appl. No. 11/417,993, mailed Oct. 29, 2008. cited by other.
Office Action for U.S. Appl. No. 12/370,562, mailed Sep. 30, 2010. cited by other.
Office Action for U.S. Appl. No. 12/370,562, mailed Apr. 6, 2011. cited by other.
Office Action for U.S. Appl. No. 11/592,891, mailed Jan. 15, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/592,891, mailed Jul. 20, 2009. cited by other.
Office Action for U.S. Appl. No. 11/595,119, mailed Jul. 21, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/595,119, mailed Jan. 5, 2010. cited by other.
Office Action for U.S. Appl. No. 11/595,119, mailed Aug. 19, 2010. cited by other.
Final Office Action for U.S. Appl. No. 11/595,119, mailed Aug. 2, 2011. cited by other.
Office Action for U.S. Appl. No. 11/604,075, mailed May 3, 2010. cited by other.
Office Action for U.S. Appl. No. 11/845,029, mailed Jul. 9, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/845,029, mailed Jan. 25, 2010. cited by other.
Office Action for U.S. Appl. No. 11/845,029, mailed May 14, 2010. cited by other.
Final Office Action for U.S. Appl. No. 11/845,029, mailed Dec. 9, 2010. cited by other.
Office Action for U.S. Appl. No. 11/845,029, mailed Sep. 27, 2011. cited by other.
Office Action for U.S. Appl. No. 11/437,538, mailed Dec. 22, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/437,538, mailed Jun. 10, 2009. cited by other.
Office Action for U.S. Appl. No. 11/437,387, mailed Dec. 23, 2008. cited by other.
Final Office Action for U.S. Appl. No. 11/437,387, mailed Jul. 15, 2009. cited by other.
Office Action for U.S. Appl. No. 11/437,582, mailed Jan. 8, 2009. cited by other.
Final Office Action for U.S. Appl. No. 11/437,582, mailed Jul. 22, 2009. cited by other.
Office Action for U.S. Appl. No. 11/801,964, mailed Sep. 17, 2010. cited by other.
Final Office Action for U.S. Appl. No. 11/801,964, mailed May 11, 2011. cited by other.
Office Action for U.S. Appl. No. 12/304,100, mailed Jun. 17, 2011. cited by other.
Office Action for U.S. Appl. No. 11/487,722, mailed Aug. 7, 2009. cited by other.
Office Action for U.S. Appl. No. 11/643,329, mailed Jul. 9, 2010. cited by other.
Office Action for U.S. Appl. No. 11/648,359, mailed Nov. 19, 2009. cited by other.
Office Action for U.S. Appl. No. 12/077,051, mailed Dec. 28, 2010. cited by other.
Office Action for U.S. Appl. No. 12/113,535, mailed Apr. 21, 2011. cited by other.
Office Action for U.S. Appl. No. 11/852,234, mailed Jun. 29, 2009. cited by other.
Office Action for U.S. Appl. No. 11/852,234, mailed Jan. 21, 2010. cited by other.
Office Action for U.S. Appl. No. 11/852,234, mailed Aug. 9, 2010. cited by other.
Office Action for U.S. Appl. No. 11/852,234, mailed Apr. 27, 2011. cited by other.
Office Action for U.S. Appl. No. 11/970,484, mailed Nov. 24, 2010. cited by other.
Final Office Action for U.S. Appl. No. 11/970,484, mailed Jul. 22, 2011. cited by other.
Office Action for U.S. Appl. No. 12/172,195, mailed Jun. 1, 2010. cited by other.
Office Action for U.S. Appl. No. 12/172,195, mailed Nov. 12, 2010. cited by other.
Office Action for U.S. Appl. No. 12/336,492, mailed Sep. 15, 2011. cited by other.
Office Action for U.S. Appl. No. 12/210,917, mailed Nov. 15, 2010. cited by other.
Final Office Action for U.S. Appl. No. 12/210,917, mailed May 13, 2011. cited by other.
Office Action for U.S. Appl. No. 12/350,927, mailed Aug. 17, 2011. cited by other.
Office Action for U.S. Appl. No. 12/365,891, mailed Aug. 29, 2011. cited by other.
Final Office Action for U.S. Appl. No. 12/474,020, mailed Oct. 4, 2010. cited by other.
Office Action for U.S. Appl. No. 09/866,474, mailed Nov. 30, 2004. cited by other.
Office Action for U.S. Appl. No. 10/667,027, mailed Jul. 29, 2005. cited by other.
Final Office Action for U.S. Appl. No. 10/667,027, mailed Mar. 10, 2006. cited by other.
Office Action for U.S. Appl. No. 10/667,027, mailed May 5, 2006. cited by other.
Final Office Action for U.S. Appl. No. 10/667,027, mailed Feb. 26, 2007. cited by other.
Office Action for U.S. Appl. No. 10/666,848, mailed Mar. 22, 2007. cited by other.
Office Action for U.S. Appl. No. 10/667,136, mailed Jan. 25, 2006. cited by other.
Office Action for U.S. Appl. No. 10/667,136, mailed Aug. 28, 2006. cited by other.
Final Office Action for U.S. Appl. No. 10/667,136, mailed Mar. 9, 2007. cited by other.
International Search Report and Written Opinion for PCT/US05/004702, mailed Aug. 10, 2006. cited by other.
International Search Report and Written Opinion for PCT/US06/40500, mailed Aug. 17, 2007. cited by other.
International Search Report and Written Opinion for PCT/US06/40498, mailed Dec. 28, 2007. cited by other.
International Search Report and Written Opinion for PCT/US2007/012194 dated Feb. 4, 2008. cited by other.
International Search Report and Written Opinion for PCT/US06/40499, mailed Dec. 13, 2007. cited by other.
International Search Report and Written Opinion for PCT/US2007/19696, mailed Feb. 29, 2008. cited by other.
International Search Report and Written Opinion for PCT/US2007/12016, mailed Jan. 4, 2008. cited by other.
International Search Report and Written Opinion for PCT/US2007/012195, mailed Mar. 19, 2008. cited by other.
International Search Report and Written Opinion for PCT/US07/013758 mailed Apr. 3, 2008. cited by other.
First Office Action for Chinese Application No. 2007800229623.X , mailed Dec. 31, 2010. cited by other.
International Search Report and Written Opinion for PCT/US07/013757, mailed Jan. 22, 2008. cited by other.
International Search Report and Written Opinion for PCT/US07/14847, mailed Apr. 1, 2008. cited by other.
International Search Report and Written Opinion for PCT/US07/089134, mailed Apr. 10, 2008. cited by other.
International Search Report and Written Opinion for PCT/US2008/010708, mailed May 18, 2009. cited by other.
Supplementary Partial European Search Report for European Application No. 02770460, mailed Aug. 20, 2004. cited by other.
Supplementary Partial European Search Report for European Application No. 02770460, mailed Dec. 15, 2004. cited by other.
Examination Report for European Application No. 02770460, Mar. 18, 2005. cited by other.
Summons for Oral Hearing Proceedings for European Application No. 02770460, Jan. 31, 2006. cited by other.
International Search Report for PCT/US02/28090, mailed Aug. 13, 2003. cited by other.
International Preliminary Examination Report for PCT/US02/28090, mailed Oct. 29, 2003. cited by other.
Examination Report for European Application No. 06006504, mailed Oct. 10, 2006. cited by other.
English Translation of Office Action for Japanese Application No. 2006-088348, mailed Jan. 4, 2011. cited by other.
International Search Report and Written Opinion for PCT/US04/30769, mailed Oct. 4, 2005. cited by other.
International Search Report and Written Opinion for PCT/US04/30683, mailed Feb. 10, 2006. cited by other.
International Search Report and Written Opinion for PCT/US04/30684, mailed Feb. 10, 2006. cited by other.
Final Office Action for U.S. Appl. No. 12/489,295, mailed Jan. 18, 2012. cited by other.
Office Action for U.S. Appl. No. 11/351,104, mailed Feb. 15, 2012. cited by other.
Office Action for U.S. Appl. No. 12/370,562, mailed Jan. 17, 2012. cited by other.
Office Action for U.S. Appl. No. 12/683,281, mailed Jan. 20, 2012. cited by other.
Final Office Action for U.S. Appl. No. 12/304,100, mailed Feb. 2, 2012. cited by other.
Final Office Action for U.S. Appl. No. 11/852,234, mailed Jan. 20, 2012. cited by other.
Final Office Action for U.S. Appl. No. 12/350,927, mailed Jan. 18, 2012. cited by other.
Abstract: A technique for locating a device uses connectivity to find a distance between an access point (AP) and a device. The AP transmits a frame to a device and receives an acknowledgement frame from the device. The amount of time for a signal to pass between the AP and the device is estimated and multiplied by the speed of light to find the distance between the AP and the device.
1. A system, comprising: an access point (AP), wherein, in operation: the AP transmits a frame; stores a time of beginning of transmission, t.sub.0; if an acknowledgementframe is received the AP stores a time of completion of receiving, t.sub.1; and if the acknowledgement frame is not received after one or more frame transmissions, the AP denies future requests for access to a network from the station and sends aninstruction to a network management module (NMM) to broadcast an address of the station to other APs in the network to allow the other APs to deny the station access; and the NMM, coupled to the AP, including: memory having a value, t.sub.fixed, storedtherein, representing a known frame exchange component period of time, and a value, c, representing the speed of light; a distance calculation engine, in operation, the distance calculation engine determining a distance, d, using a formulad=[(t.sub.1-t.sub.0-t.sub.fixed)/2]c, d representing an estimated distance of the AP from the station; and a graphical display engine, wherein, in operation, the graphical display engine displays one or more predicted locations the distance, d, from theAP in a graphically rendered environment.
2. The system of claim 1 wherein, in operation, the AP transmits a plurality of frames, receives a responding acknowledgement paired to each frame transmitted; and wherein, in operation, the distance calculating engine calculates a pluralityof distance values for paired frames from the plurality of times for t.sub.0 and t.sub.1 and averages the plurality of distance values to find an estimated distance.
5. The system of claim 1 further comprising: a second AP, wherein, in operation, the second AP transmits a second frame; stores a second time of beginning of transmission, t.sub.0'; receives a second acknowledgement frame from the station; stores a second time of completion of receiving, t.sub.1'; wherein, in operation, the distance calculating engine calculates a second distance d' using a second formua d'=[(t.sub.1'-t.sub.0'-t.sub.fixed)/2]c and d' is used to reduce the one or morepredicted locations to two or fewer predicted locations; wherein the two or fewer predicted locations are displayed at intersecting points of two circles, a location of the AP being at a center of a first circle having a radius of length d, a secondlocation of the second AP being at a second center of the second circle having a radius of length d'.
6. The system of claim 5 further comprising: a third AP; wherein, in operation, the third AP transmits a third frame; stores a third time of beginning of transmission, t.sub.0'; receives a third acknowledgement frame from the station; stores a third time of completion of receiving, t.sub.1' wherein, in operation, the distance calculating engine is used to calculate a third distance d'' and the third distance d'' is used to reduce the one or more predicted locations to one location; the one location is at a point a distance d from the AP, a distance d' from the second AP, and a distance d'' from the third AP.
8. The system of claim 1 further comprising: a second AP, wherein, in operation, the second AP transmits a second frame; stores a second time of beginning of transmission, t.sub.0'; receives a second acknowledgement frame from the station; stores a second time of completion of receiving, t.sub.1'; a third AP a third AP; wherein, in operation, the third AP transmits a third frame; stores a third time of beginning of transmission, t.sub.0''; receives a third acknowledgement frame fromthe station; stores a second time of completion of receiving, t.sub.1''; a fourth AP a fourth AP; wherein, in operation, the fourth AP transmits a fourth frame; stores a fourth time of beginning of transmission, t.sub.0'''; receives a fourthacknowledgement frame from the station; stores a second time of completion of receiving, t.sub.1'''; wherein in operation, the second AP calculates a second distance d'=[(t.sub.1'-t.sub.0'-t.sub.fixed)/2]c, the third AP calculates a third distanced''=[(t.sub.1''-t.sub.0''-t.sub.fixed)/2]c, the fourth AP calculates a fourth distance d'''=[(t.sub.1'''-t.sub.0'''-t.sub.fixed)/2]c; wherein the distance d, the second distance d', the third distance d'', and the fourth distance d''' are used toidentify a single point on the graphically rendered environment as a location of a station; the one location is at a point a distance d from the AP, a distance d' from the second AP, a distance d'' from the third AP, and a distance d''' from the fourthAP.
10. A method, comprising: transmitting a first message from a first access point (AP); if a second message, associated with the first message, is not received from the station, (1) disabling future access to a network by a station and (2)broadcasting an address of the station to a second AP in the network to allow the second AP to deny the station access; and predicting a location of the station if the second message is received from the station, comprising: calculating a timedifference, .DELTA.t, between the start of transmission of the first message, t.sub.0 and receipt of the second message, t.sub.1, wherein .DELTA.t=t.sub.0-t.sub.1. calculating roundtrip propagation time by subtracting one or more fixed periods of timefrom .DELTA.t for one or more components of a frame exchange; determining a distance d by multiplying the speed of light by half the round trip propagation time; and predicting a location of the station based on d.
11. The method of claim 10 wherein the one or more fixed periods time subtracted from .DELTA.t include times used to prepare the first message for transmission and to prepare the second message for transmission.
12. The method of claim 10 wherein the one or more components of the frame exchange comprise: a transmission frame physical layer convergence procedure; a transmission frame mac header; a transmission frame check sequence; a shortinter-frame space; an acknowledge frame physical layer convergence procedure; an acknowledge frame mac header; an acknowledge frame check sequence.
15. A device, comprising: a radio; a propagation distance calculating engine; wherein, in operation: the radio sends a frame to a station, the propagation distance calculating engine records a time of start of transmission of the frame, whenthe radio does not receive an acknowledgement frame from the station, the device (1) denies future access to a network by the station through the device and (2) broadcasts an address of the station to other devices in the network to allow the otherdevices to deny access to the network by the station; and when the radio receives an acknowledgement frame from the station: the propagation distance calculating engine stores a time of completion of receiving the acknowledgement frame, and thepropagation distance calculating engine calculates a distance by d=[(.DELTA.t-t.sub.fixed)/2]c, c being the speed of light, .DELTA.t being the time of completion of receiving minus the time of start of transmission, and t.sub.fixed being a known frameexchange component period of time.
16. The device of claim 15 wherein, in operation, the radio sends a plurality of frames, the propagation distance calculating engine calculates a plurality of distance values, and the propagation distance calculating engine averages thedistance values to calculate an estimate of the distance d.
17. The device of claim 15 wherein t.sub.fixed includes time components for a transmission frame physical layer convergence procedure, a transmission frame mac header, a transmission frame check sequence, a short inter-frame space, anacknowledgement frame physical layer convergence procedure, an acknowledge frame mac header, an acknowledge frame check sequence.
Devices on a network may be considered client devices or rogue devices. Generally, clients have permission to use the network, and rogues do not. For rogues, elimination is desirable. It may be possible that an operator of the rogue devicemay attempt to frustrate efforts to find the rogue. A rogue device at an unknown location may be difficult to eliminate, requiring the use of strong countermeasures, e.g. suppression of service.
An existing approach uses a received signal strength indicator (RSSI) to locate devices. RSSI levels may be used to estimate a device distance. High RSSI is indicative of closer proximity than low RSSI. The RSSI approach may yield poorresults because client transmit power is usually unknown. Further, a precise model of a radio environment is generally unavailable.
Another existing approach uses time differences of arrival (TDOA). TDOA removes signal attenuation from the calculation. However, TDOA is similarly flawed in that nanosecond clocks are generally not synchronized and synchronizing them isdifficult. Further, in TDOA, paths to the location avoids obstacles in different ways. Varying path lengths from varying points may cause TDOA to suffer in quality when higher numbers of different points are used to find a location. This is counterintuitive because a greater number of measurements would seem to lead to a more accurate location.
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 upon a reading of the specification and a study of thedrawings.
The following examples and aspects thereof are described and illustrated in conjunction with systems, tools, and methods that are meant to be exemplary and illustrative, not limiting in scope. In various examples, one or more of theabove-described problems have been reduced or eliminated, while other examples are directed to other improvements.
A technique for locating a device may involve transmitting a frame to a device and receiving an acknowledgement frame from the device. The amount of time for a signal to pass between the AP and the device may be estimated and multiplied by thespeed of light to find the distance between the AP and the device. Many distances calculated from many APs may be used to determine a location of the device. Sometimes a single AP may be used to find possible locations of a device in two dimensions. In three dimensions, a number of APs may by used to locate a device, such in an outdoor network.
Consider, for the purposes of example only, a rogue device operated by a rogue operator that does not have permission to use a network. The rogue device is well hidden in a building. In some cases a network administrator may employcountermeasures, shutting down service to portions of the network that the rogue would use. However, using the technique disclosed herein, the rogue is located, security is dispatched, and the rogue computing device is quickly eliminated withoutinterrupting service. Users of the network may remain unaware that an intruding rogue was ever present.
FIG. 8 depicts a diagram of an example of two possible locations for a station at points at which the station is a distance d away from the first station and a distance d'' away from the second station.
In the following description, several specific details are presented to provide a thorough understanding. One skilled in the relevant art will recognize, however, that the concepts and techniques disclosed herein can be practiced without one ormore of the specific details, or in combination with other components, etc. In other instances, well-known implementations or operations are not shown or described in detail to avoid obscuring aspects of various examples disclosed herein.
FIG. 1 depicts a diagram 100 of an example of a system including a wireless access domain. The system 100 includes network 102, network management module 106, station 108, wireless exchange switch 110-1, wireless exchange switch 110-2, wirelessexchange switch 110-N (collectively wireless exchange switches 110), access point 114-1, access point 114-2, access point 114-N (collectively access points 114).
In the example of FIG. 1, the network 102 may be practically any type of communications network. By way of example but not limitation, the wireless access domain 104 may be referred to as, a Local Area Network (LAN), virtual LAN (VLAN), and/orwireless LAN (WLAN).
In the example of FIG. 1, the network management module 106 may be practically any type of component or device that is capable of communicating with a communications network, such as, by way of example but not limitation, a mainframe or aworkstation as well as a module coupled to or operating in software on a server, AP, wireless exchange switches or other network component.
In the example of FIG. 1, the station 108 may be any computing device, by way of example but not limitation, a laptop, a wireless telephone, or any device capable of communication on a wireless network. A station, as used herein, may bereferred to as a device with a media access control (MAC) address and a physical layer (PHY) interface to the wireless medium that comply with the IEEE 802.11 standard. As such, the access points 114 are typically also stations. In alternativeexamples, a station may comply with a different standard than IEEE 802.11, and may have different interfaces to a wireless or other medium. The station 108 may include a radio capable of generating signals compatible with communication on one or morenetworks. The station 108 may be in radio communication with one or more of the access points 114.
In the example of FIG. 1, wireless exchange switches 110 may swap topology data and client information that details each user's identity, location, authentication state, VLAN membership, permissions, roaming history, bandwidth consumption,and/or other attributes assigned by, by way of example but not limitation, an Authentication, Authorization, and Accounting (AAA) backend (not shown).
The wireless exchange switches 110 provide forwarding, queuing, tunneling, and/or some security services for the information the wireless exchange switches 110 receive from their associated access points 114. The wireless exchange switches 110coordinate, may provide power to, and/or manage the configuration of the associated access points 114. An implementation of a wireless exchange switches, provided by way of example but not limitation, includes a Trapeze Networks Mobility Exchange.RTM. switch. The Trapeze Networks Mobility Exchange.RTM. switches may, in another implementation, be coordinated by means of the Trapeze Access Point Access.TM. (TAPA.TM.) protocol.
In a non-limiting example, the access points 114 are hardware units that act as a communication hub by linking wireless mobile stations such as PCs to a wired backbone network. In an example the access points 114 connect users to other userswithin the network and, in another example, can serve as the point of interconnection between a WLAN and a fixed wire network. The number of users and size of a network help to determine how many access points are desirable for a given implementation. An implementation of an access point, provided by way of example but not limitation, includes a Trapeze Networks Mobility System.RTM. Mobility Point.RTM. (MP.RTM.) access point.
The access points 114 are stations that transmit and receive data (and may therefore be referred to as transceivers) using one or more radio transmitters. For example, an access point may have two associated radios, one which is configured forIEEE 802.11a standard transmissions, and the other which is configured for IEEE 802.11b standard transmissions. In a non-limiting example, an access point transmits and receives information as radio frequency (RF) signals to and from a wireless clientover a 10/100BASE-T Ethernet connection. The access points 114 transmit and receive information to and from their associated wireless exchange switches 110. Connection to a second wireless exchange switch provides redundancy.
FIG. 2 depicts a diagram 200 of an example of a system transmitting a frame, receiving an acknowledgement frame, calculating a distance to a station, and displaying results. In the example of FIG. 2, the diagram 200 includes station 202, accesspoint 204, network management module 206, display 208, frame transmission indicator 222, acknowledgement frame transmission indicator 224, location data communication indicator 226, and display of contents indicator 228.
Station 202 may be a device capable of radio communication with one or more access points. In a non-limiting example, the station 202 may be configured for communication using IEEE 802.11 standard communication, but any known or convenientstandard for communication may be used.
Access point 204 may be an access point as discussed in reference to FIG. 2, and may be capable of communication with one or more stations via IEEE 802.11 standard communications. Network management module 106 may be practically any type ofcomponent or device that is capable of communicating with a communications network, such as, by way of example but not limitation, a mainframe or a workstation as well as a module coupled to or operating in software on a server, AP, wireless exchange orother network component.
Network management module 206 may be practically any type of component or device that is capable of communicating with a communications network. A workstation as well as a module coupled to or operating in software on a server, AP, wirelessexchange or other network component could be used. Access point 204 may be coupled to, or contain network management module 206. AP 204 and network management module 206 may further be modules in another component such as a wireless exchange switch.
Display 208 may provide a view of a layout of a building, floorplan, or other known or convenient manner of visualizing an environment including APs and stations. AP 204 may be displayed on display 208. Station 202 may be displayed on display208. Display 208 may be connected to network management module 206 and display information provided by network management module 206.
In the example of FIG. 2, in operation, AP 204 transmits a frame to station 202. Frame transmission indicator 222 depicts the transmission of the frame from AP 204 to station 202. The frames may be null frames. Typically, null frames haveheaders, but not payload. AP 204 records a time of transmission of the frame.
Such frames may be referred to as "ping" frames. Because of variance in acknowledgement over time, a single ping frame may be insufficient to acquire an accurate estimate of a distance between an AP and a device. It may be advantageous to usemultiple ping frames and average a round trip time for transmitting a ping frame and receiving an acknowledgement frame. Averaging many values may lead to a more accurate estimate of the distance between the AP and the device. Multiple pings may becoordinated to occur during ActiveScan intervals to avoid interruptions in service.
A rogue device may encrypt data in transmission, and refuse to respond to frames that do not have proper encryption keys. However, by using a null frame, a rogue device may respond regardless of encryption. A rogue device may refuse totransmit an Acknowledgement frame. A system may respond by denying the rogue device use of system resources, and if necessary, completely suspending service to a portion of the network, or the entire network. This response may be automatic, or may bemanually initiated by an administrator.
It may be necessary to "spoof" or supply an inaccurate 802.11 frame control field sequence number to be accepted by a device, however, many 802.11i implementations do not validate an 802.11 frame sequence number. A device may check the TKIP(Temporal Key Integrity Protocol), or CCMP Packet No. (Counter Mode with Cyper Block Chaining Message Authentication Code Protocol) instead. A rogue device may accept the transmitted ping frame, and respond with an acknowledgement frame.
In the example of FIG. 2, AP 204 provides location data to network management module 206. Location data communication indicator 226 shows AP 204 communicating time of transmission of the frame and time of receipt of the acknowledgement frame tonetwork management module 206. Network management module 206 calculates a distance d between AP 204 and station 202.
In the example of FIG. 2, display of contents indicator 228 depicts network management module 206 providing location information to display 208. The location information may be based on the distance d between the AP and the station to display208 as indicated by display of contents indicator 228. Location information may be in the form of an identification of the location of the station, multiple possible locations for the station, or other information about the location of station 202.
FIG. 3 depicts a flowchart 300 of an example of a method of estimating a location of a station. The method is organized as a sequence of modules in the flowchart 300. However, it should be understood that these and modules associated withother methods described herein may be reordered for parallel execution or into different sequences of modules.
In the example of FIG. 3, the flowchart 300 starts at module 302 with transmitting a frame. At the beginning of transmission, a time t.sub.0 may be recorded indicating the beginning of transmission.
In the example of FIG. 3, the flowchart 300 continues to module 304 with receiving a second message from a station associated with the first message. Here, the acknowledgement frame is received at a time which is later than t.sub.0. This timemay be recorded as t.sub.1.
In the example of FIG. 3, the flowchart 300 continues to module 306 with calculating a time difference, .DELTA.t, between the start of transmission of the first message and receipt of the second message. t.sub.0 may be a time of beginning oftransmission of the first message. t.sub.1 may be a time of receipt of the second message. .DELTA.t may be calculated by subtracting to from t.sub.1: .DELTA.t=t.sub.0-t.sub.1.
In the example of FIG. 3, the flowchart 300 continues to module 308 with calculating roundtrip propagation time by subtracting fixed periods of time from .DELTA.t for components of the frame exchange. Fixed periods of time may include time tocomplete a physical layer convergence procedure (PLCP), a Media Access Control (MAC) Header, frame check sequence (FCS), short inter-frame space (SIFS), physical layer convergence procedure (PLCP), Media Access Control (MAC) Header, and frame checksequence (FCS). These fixed time periods are known so they may be stored. By subtracting fixed periods of time from .DELTA.t, the remaining time is equal to the amount of time that the transmitted frame, and the acknowledgement frame traveled betweenthe station and the AP, or the round trip propagation time.
In the example of FIG. 3, the flowchart 300 continues to module 310 with determining a distance d by multiplying the speed of light by half the round trip propagation time. It is necessary to divide the round trip propagation time by twobecause the round trip includes traveling the distance between the AP and the station and then traveling between the station and the AP. The speed of light is used because the signals which transmit the frame travel at approximately the speed of light.
In the example of FIG. 3, the flowchart 300 continues to module 312 with using d to estimate a location of the station. In two dimensions, knowing that the station is a distance d from the AP allows a location to be estimated in terms of pointson a circle a distance d away from the AP, as depicted in FIG. 7. If more than one AP is used, the intersection of circles may be used to find possible locations of a station as discussed relative to FIG. 8-9. For estimation in three dimensions, referto the discussions of FIG. 9 and FIG. 10. Having estimated the location of a station, the flowchart ends.
FIG. 4 depicts a diagram 400 of an example of a floor plan including APs for a wireless access domain. FIG. 4 includes floorplan 402, AP 414-1, AP 414-2, AP 414-3, AP 414-4 and AP 414-5 (Collectively, APs 414). In the example of FIG. 4,devices present in the offices depicted in floorplan 402 may connect to one or more of APs 414. APs 414 may be included as a part of a larger wireless access domain including wireless exchange switches and one or more network management modules. TheAPs may be coupled together via conventional network wiring.
In the example of FIG. 4, five APs may provide high quality service throughout all offices and hallways of the offices depicted in floorplan 402. Some APs may not be accessible from some locations on the floor plan. In a non-limiting example,AP 414-1 may not be accessible from office 54. Similarly parts of office 55 may receive no signal or only a weak signal from AP 414-5, and may receive no signal from AP 414-1. Weak signal strength or a low number of APs may negatively impact theability of a network of APs to locate a station. For installations in which only a single AP provides a strong signal to an office, a distance to a station may be calculated. However, such a predicted distance to the station may indicate an infinitenumber of locations on a circle a distance d away from the AP.
FIG. 5 depicts a diagram 500 of an example of a sequence of transmitting a frame and receiving an acknowledgement frame. Diagram 500 includes frame transmission indicator 502, and acknowledge frame transmission indicator 504. A first pingframe is sent as shown by frame transmission indicator 502. Next acknowledgement frame transmission indicator 504 shows the transmission of an acknowledgement frame. Time spent between receipt of the transmitted frame but before sending anacknowledgement frame is referred to as a short frame interface space.
FIG. 6 depicts a diagram 600 of fixed time components as a part of a sequence of transmitting a frame and receiving an acknowledgement frame. Diagram 600 includes frame transmission indicator 602, acknowledgement (ACK) frame transmissionindicator 604, distributed inter-frame space (DIFS) 606, physical layer convergence procedure (PLCP) 608, Media Access Control (MAC) Header 610, frame check sequence (FCS) 612, short inter-frame space (SIFS) 612, physical layer convergence procedure(PLCP) 616, Media Access Control (MAC) Header 618, and frame check sequence (FCS) 620.
In subtracting time components for PLCP 608, MAC Header 610, FCS 612, PLCP 616, MAC Header 618, and FCS 620 from .DELTA.t, the remaining time may be attributed to the travel a round trip between the station and the AP. Half this time may be theamount of time for one frame to travel between the station and the AP.
FIG. 7 depicts a diagram 700 of an example of a plurality of possible locations for a station a distance d away from an access point. Diagram 700 includes access point 706, station 708, and distance (d) 710. This diagram assumes a twodimensional layout, such as a floorplan of an office. In such a case, the station will be a distance d away from the AP at a location that lies approximately on a circle or are around the station with a radius equal to the distance. In order to locatea device with more specificity, it may be necessary to use more than one AP. However, where a floor plan is such that the AP may only identify a limited range of locations, such as in a corner of a building, fewer points than necessary to comprise awhole circle may be used. In such a case, the possible locations will lie on an arc instead of a circle.
FIG. 8 depicts a diagram 800 of an example of two possible locations for a station at points at which the station is a distance d away from the first station and a distance d'' away from the second station. Diagram 800 includes access point(AP) 804, access point (AP) 806, station 808, distance (d) 820, and second distance (d') 822. Where two APs are used to reduce the number of potential locations for a station, there will be two distances d 820 and d' 822. The two distances d 820 and d'822 will sweep circles around the APs. So long as the APs are not each at exactly the same location and have overlapping coverage areas, they will intersect at two points. Two possible locations are depicted.
FIG. 9 depicts a diagram 900 of an example of locating a device using three APs. Diagram 900 includes Access Point (AP) 902, Access Point (AP) 904, Access Point (AP) 906, station 908, distance (d) 920, second distance (d') 922, and thirddistance (d''') 924. Similarly to FIG. 8, in a two dimensional system, three APs located at different locations may locate a station in exactly one point. AP 902, AP 904, and AP 906 each estimate distances d, d', and d'' respectively. d, d', and d''sweep three circles around AP 902, AP 904, and AP 906.
FIG. 10 depicts a diagram 1000 of an example of locating a device in three dimensional space using an AP. The system 1000 includes AP 1004, station 1008, and distance (d) 1012. In this case, the AP is able to estimate a distance which can beused to sweep a sphere around the AP. Where AP 1004 is used, station 1008 can, without taking into account physical limitations, may be found at any point, a distance d away from the AP. The multiple locations displayed could be three of many differentpossible locations lying on the sphere surrounding the AP.
FIG. 11 depicts a diagram 1100 of an example of locating a device in three dimensional space using four APs. The system 1100 includes station 1102, AP 1104, AP 1106, AP 1108, AP 1110, distance (d) 1124, second distance (d') 1124, third distance(d''') 1126, fourth distance (d''') 1128.
In three dimensions, it may be necessary to use four APs to identify a single location for station 1102. This is because the intersection between two spheres representing distances d and d' away from APs 1106 and 1108 may be a circle. A circlemay intersect with the sphere representing the distance d'' away from AP 1108 in two points. Finally, a sphere representing the distance d''' away from AP 1110 may intersect with a single one of the two points. This may identify a single point in threedimensions for a location of station 1102.
FIG. 12 depicts a diagram of an example of locating a rogue device on a floor plan using a wireless access domain. The diagram 1200 includes network management module 1202, display 1204, rogue 1205, network 1206, and wireless access domain1207. A floorplan is an exemplary two dimensional model in which to locate a station however, many other two dimensional or three dimensional models could be used; this model is for purposes of example and not limitation. Herein, AP 1214-2, AP 1214-4,and AP 1214-5 (Collectively APs 1214) have, as a group, identified the location of a rouge station a distance d away from AP 1214-2, a distance d' away from AP 1214-5, and a distance d'' from AP 1214-4. Dashed circles and arcs represent distances awayfrom access points.
In the example of FIG. 12, wireless access domain 1207 contains wireless access areas 108-1 through 108-N, (collectively wireless access areas 1208). Wireless exchange switches 1210-1 to 1210-N (hereinafter collectively referred to as wirelessexchange switches 1210), access points 1212-1 to 1212-N (hereinafter collectively referred to as access points 1212), and networks 1214-1 to 1214-N (hereinafter collectively referred to as networks 1214).
In the example of FIG. 12, an operator of station 1220 has placed station 1220 in a hidden area, e.g. an air vent, and has opted to employ station 1220 for malicious purposes, e.g. theft of trade secrets from a system server. A systemadministrator here may be faced with the options of (1) terminating service on APs 1214, or alternatively (2) eliminating the rogue. Since the system administrator has been given the estimated location of the rogue, security may be dispatched, and therogue eliminated. This prevents the interruption of service.
Display 1204 may display not only warning messages, such as "Alert," but also may display an entire floor plan animated with information about the location of rogues, clients, APs and other relevant information. Where the rogue is moving, thedisplay may update the position of the rogue in real time.
FIG. 13 depicts a diagram 1300 of a system capable of calculating a distance to another device. The system 1300 may be a conventional computer system that can be used as a client computer system, such as a wireless client or a workstation, or aserver computer system. The computer system 1300 includes a device 1302, I/O devices 1304, radio 1324, and a display device 1306. The device 1302 includes a processor 1308, a communications interface 1310, memory 1312, display controller 1314,non-volatile storage 1316, I/O controller 1318, clock 1320, and distance calculation engine 1322. The device 1302 may be coupled to or include the I/O devices 1304, display device 1306, and radio 1324.
The device 1302 interfaces to external systems through the communications interface 1310, which may include a modem or network interface. It will be appreciated that the communications interface 1310 can be considered to be part of the system1300 or a part of the device 1302. The communications interface 1310 can be an analog modem, ISDN modem, cable modem, token ring interface, ethernet interface, wireless 802.11 interface, satellite transmission interface (e.g. "direct PC"), or otherinterfaces for coupling a computer system to other computer systems.
The processor 1308 may be, for example, a conventional microprocessor such as an Intel Pentium microprocessor or Motorola power PC microprocessor. The memory 1312 is coupled to the processor 1308 by a bus 1320. The memory 1312 can be DynamicRandom Access Memory (DRAM) and can also include Static RAM (SRAM). The bus 1320 couples the processor 1308 to the memory 1312, also to the non-volatile storage 1316, to the display controller 1314, and to the I/O controller 1318.
The I/O devices 1304 can include a keyboard, disk drives, printers, a scanner, and other input and output devices, including a mouse or other pointing device. The display controller 1314 may control in the conventional manner a display on thedisplay device 1306, which can be, for example, a cathode ray tube (CRT) or liquid crystal display (LCD). The display controller 1314 and the I/O controller 1318 can be implemented with conventional well known technology.
The non-volatile storage 1316 is often a magnetic hard disk, an optical disk, or another form of storage for large amounts of data. Some of this data is often written, by a direct memory access process, into memory 1312 during execution ofsoftware in the device 1302. One of skill in the art will immediately recognize that the terms "machine-readable medium" or "computer-readable medium" includes any type of storage device that is accessible by the processor 1308 and is intended toencompass a carrier wave that encodes a data signal to the extent that such a carrier wave is patentable.
Clock 1320 can be any kind of oscillating circuit creating an electrical signal with a precise frequency. In a non-limiting example, clock 1320 could be a crystal oscillator using the mechanical resonance of vibrating crystal to generate theelectrical signal.
Radio 1324 may be any combination of known or convenient electrical components including by way of example, but not limitation, transistors, capacitors, resistors, multiplexers, wiring, registers, diodes or any other electrical components knownor convenient.
The system 1300 is one example of many possible computer systems which have different architectures. For example, personal computers based on an Intel microprocessor often have multiple buses, one of which can be an I/O bus for the peripheralsand one that directly connects the processor 1308 and the memory 1312 (often referred to as a memory bus). The buses are connected together through bridge components that perform any necessary translation due to differing bus protocols.
Network computers are another type of computer system that can be used in conjunction with the teachings provided herein. Network computers do not usually include a hard disk or other mass storage, and the executable programs are loaded from anetwork connection into the memory 1312 for execution by the processor 1308. A Web TV system, which is known in the art, is also considered to be a computer system, but it may lack some of the features shown in FIG. 13, such as certain input or outputdevices. A typical computer system will usually include at least a processor, memory, and a bus coupling the memory to the processor.
In addition, the system 1300 is controlled by operating system software which includes a file management system, such as a disk operating system, which is part of the operating system software. One example of operating system software with itsassociated file management system software is the family of operating systems known as Windows.RTM. from Microsoft Corporation of Redmond, Wash., and their associated file management systems. Another example of operating system software with itsassociated file management system software is the Linux operating system and its associated file management system. The file management system is typically stored in the non-volatile storage 1316 and causes the processor 1308 to execute the various actsrequired by the operating system to input and output data and to store data in memory, including storing files on the non-volatile storage 1316.
The present example also relates to apparatus for performing the operations herein. This apparatus may be specially constructed for the required purposes, or it may comprise a general purpose computer selectively activated or reconfigured by acomputer program stored in the computer. Such a computer program may be stored in a computer readable storage medium, such as, but is not limited to, read-only memories (ROMs), random access memories (RAMs), EPROMs, EEPROMs, magnetic or optical cards,any type of disk including floppy disks, optical disks, CD-ROMs, and magnetic-optical disks, or any type of media suitable for storing electronic instructions, and each coupled to a computer system bus.
The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenientto construct more specialized apparatus to perform the required method steps. The required structure for a variety of these systems will appear from the description below. In addition, the present example is not described with reference to anyparticular programming language, and various examples may thus be implemented using a variety of programming languages.
Torque enhancing clamping nut
Process for preparing prilled porous ammonium nitrate
Hydrolysis process of fat or oil