Patent Application
20090043666
Embodiments of the subject matter described herein relate generally to a planning and management software application for use with wireless network architectures. More particularly, embodiments of the subject matter relate to the generation of a wireless network planning report that contains stock keeping unit (SKU) and price information for wireless network devices and accessories.
Wireless radio frequency (RF) network architectures, wireless local area networks (WLANs), and wireless network devices and accessories are becoming increasingly popular. WLANs can give mobile computing clients the ability to “roam” or physically move from place to place without being connected by wires. In the context of a WLAN, the term “roaming” describes the act of physically moving between wireless access devices, which may be stand-alone wireless access points or wireless access ports that cooperate with one or more wireless switches located in the WLAN. Many deployments of wireless computer infrastructure, such as WLANs, involve the use of multiple wireless switches serving a number of wireless access devices.
Some wireless network administrators utilize software-based tools for purposes of planning, managing, diagnosing, and monitoring WLANs. Planning features in software of this type can generate RF coverage maps in conjunction with the floor plan in which the WLAN will be deployed. Such planning features allow the network administrator to determine how best to provide for RF coverage in the floor plan. In addition, WLAN planning software typically includes a reporting feature that can be used to generate a listing of devices needed to deploy the proposed WLAN.
A more complete understanding of the subject matter may be derived by referring to the detailed description and claims when considered in conjunction with the following figures, wherein like reference numbers refer to similar elements throughout the figures.
The following detailed description is merely illustrative in nature and is not intended to limit the embodiments of the invention or the application and uses of such embodiments. Furthermore, there is no intention to be bound by any expressed or implied theory presented in the preceding technical field, background, brief summary or the following detailed description.
Techniques and technologies may be described herein in terms of functional and/or logical block components, and with reference to symbolic representations of operations, processing tasks, and functions that may be performed by various computing components or devices. Such operations, tasks, and functions are sometimes referred to as being computer-executed, computerized, software-implemented, or computer-implemented. In practice, one or more processor devices can carry out the described operations, tasks, and functions by manipulating electrical signals representing data bits at memory locations in the system memory, as well as other processing of signals. The memory locations where data bits are maintained are physical locations that have particular electrical, magnetic, optical, or organic properties corresponding to the data bits. It should be appreciated that the various block components shown in the figures may be realized by any number of hardware, software, and/or firmware components configured to perform the specified functions. For example, an embodiment of a system or a component may employ various integrated circuit components, e.g., memory elements, digital signal processing elements, logic elements, look-up tables, or the like, which may carry out a variety of functions under the control of one or more microprocessors or other control devices.
When implemented in software or firmware, various elements of the systems described herein are essentially the code segments or instructions that perform the various tasks. The program or code segments can be stored in a processor-readable medium or transmitted by a computer data signal embodied in a carrier wave over a transmission medium or communication path. The “processor-readable medium” or “machine-readable medium” may include any medium that can store or transfer information. Examples of the processor-readable medium include an electronic circuit, a semiconductor memory device, a ROM, a flash memory, an erasable ROM (EROM), a floppy diskette, a CD-ROM, an optical disk, a hard disk, a fiber optic medium, a radio frequency (RF) link, or the like. The computer data signal may include any signal that can propagate over a transmission medium such as electronic network channels, optical fibers, air, electromagnetic paths, or RF links. The code segments may be downloaded via computer networks such as the Internet, an intranet, a LAN, or the like.
The following description may refer to elements or nodes or features being “connected” or “coupled” together. As used herein, unless expressly stated otherwise, “connected” means that one element/node/feature is directly joined to (or directly communicates with) another element/node/feature, and not necessarily mechanically. Likewise, unless expressly stated otherwise, “coupled” means that one element/node/feature is directly or indirectly joined to (or directly or indirectly communicates with) another element/node/feature, and not necessarily mechanically.
For the sake of brevity, conventional techniques related to WLAN design, topologies, and operation, inventory control, computer science, computer programming, and other functional aspects of the systems (and the individual operating components of the systems) may not be described in detail herein. Furthermore, the connecting lines shown in the various figures contained herein are intended to represent example functional relationships and/or physical couplings between the various elements. It should be noted that many alternative or additional functional relationships or physical connections may be present in an embodiment of the subject matter.
In this example, the wireless access devices are realized as wireless access ports 104, which are “thin” devices that rely on the network intelligence and management functions provided by wireless switch 102. In contrast,
Referring again to
A WLAN management and planning system of the type described herein can generate RF coverage maps to display optimal device placement as an aid to planning, while other graphs indicate network health at a glance. Users can view the status and location of wireless infrastructure devices and clients, search for a specific piece of equipment, identify rogue access devices, troubleshoot network issues, generate reports, etc. Statistics such as RF coverage, load balancing, redundancy, security threat levels, and network utilization can be graphically displayed, allowing network administrators to instantly access network status. Moreover, the management and planning system provides a suitably formatted report that contains a parts list, SKU information, and/or pricing information that facilitates quick and easy ordering of products needed to support a planned WLAN deployment.
The WLAN management and planning system is a software-based application that provides users with the functionality to research and define the physical design and intended performance of their RF infrastructure. The system can output a set of component placement recommendations based on a user-provided floor plan. The floor plan is used to generate coverage areas to expose areas of RF interference that should be taken into consideration when making component placement recommendations. The system reduces the dependency on costly manual site surveys prior to installation of a WLAN. The system can conduct RF coverage calculations and equipment placement scenarios to optimize RF coverage in certain predefined areas. The system allows network administrators to design a WLAN before actually dispatching a technician and before actually purchasing a wireless switch, an antenna, or a wireless access device.
The system creates a coverage area template based upon an image of the desired floor plan. This template can be revised to include infrastructure devices, mobile units (MUs), and/or known RF barriers such as walls, obstructions, or large metal structures. The system can then be manipulated by the user to define new coverage areas, generate an updated floor plan, and display device locations and projected coverage zones. The system can leverage a library of attenuators for different building materials to ensure that the characteristics of the RF coverage area can be accurately modeled. This library can be utilized to ensure that the expected signal strength of a device is properly impacted by the RF attenuation associated with the actual building materials and obstacles.
The system can be suitably configured to support the product line of one or more vendors, manufacturers, resellers, etc. In certain embodiments, the system focuses on WLAN products offered by one manufacturer, for example, Motorola, Inc. In other embodiments, the system can be configured to recommend products from multiple sources. The system can be populated with (or have access to) the WLAN product line database, which may include products such as, without limitation: wireless switches; wireless access devices (i.e., wireless access points and wireless access ports); bridges; adapters; repeaters; mobile computing devices; RFID readers; antennas; power cables; interconnect cables; mounting devices; UWB sensors; time synchronization devices; ZigBee routers; and related accessories.
The subject matter described herein relates to the planning, reporting, and order facilitating features of a WLAN management and planning system. These features enable easy planning of WLAN installations, and allow a network administrator to quickly review a recommended product list that includes model numbers, SKU codes, and pricing information for the recommended infrastructure products.
As mentioned previously, the WLAN planning system described here can be realized as a computer-executed software application that resides at one or more computing devices. Depending upon the implementation, the application may be: a standalone application that is designed to run on a computing device having no network connectivity; a web browser based application hosted by one or more servers; a shared application; a standalone application that is designed to run on a computing device having network connectivity to an external database; or the like. In this regard,
Computing device 400 typically includes at least some form of computer readable media. Computer readable media can be any available media that can be accessed by computing device 400 and/or by applications executed by computing device 400. By way of example, and not limitation, computer readable media may include computer storage media and communication media. Computer storage media includes volatile, nonvolatile, removable, and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computing device 400. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
Computing device 400 generally includes a processing architecture 402 (e.g., one or more processors) having suitably configured processing logic 404, a suitable amount of memory 406, at least one communication module 408, user interface features 410, and a display element 412. These elements may be interconnected using a data/control bus 414 or any suitably configured interconnection architecture or arrangement.
Processing architecture 402 may be implemented or performed with a general purpose processor, a content addressable memory, a digital signal processor, an application specific integrated circuit, a field programmable gate array, any suitable programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described here. A processor may be realized as a microprocessor, a controller, a microcontroller, or a state machine. Moreover, a processor may be implemented as a combination of computing devices, e.g., a combination of a digital signal processor and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a digital signal processor core, or any other such configuration.
Memory 406 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or a combination thereof. In this regard, memory 406 can be coupled to processing architecture 402 such that processing architecture 402 can read information from, and write information to, memory 406. In the alternative, memory 406 may be integral to processing architecture 402. As an example, processing architecture 402 and memory 406 may reside in an ASIC. Computing device 400 may also have additional storage (removable and/or non-removable) including, but not limited to, magnetic or optical disks or tape. Memory 406, removable storage, and non-removable storage are all examples of computer storage media as defined above.
For the embodiments described here, processing architecture 402 cooperates with memory 406 to support a computer-readable medium having stored thereon computer-executable instructions for performing a method of planning a wireless network architecture for a desired site. Thus, memory 406 can be used to store a suitably configured software application that is executed by processing architecture 402 in a manner that supports the techniques, methodologies, and processing tasks described in more detail herein.
Communication module 408, which may utilize wired and/or wireless data communication interfaces and protocols, allows computing device 400 to communicate with other devices or elements, such as a printer 416, a data communication network 418, and/or a remote database 420. In embodiments described herein, communication module 408 may include, without limitation, suitably configured interfaces that allow computing device 400 to communicate with network 418 (e.g., the Internet), external databases such as remote database 420, external memory devices, and the like. Communication module 408 may be associated with the handling of communication media as defined above.
Computing device 400 may also include or communicate with user interface features 410 such as a keyboard, mouse or other pointing device, pen, voice input device, touch input device, etc. Computing device 400 may also include or communicate with output device(s) such as display element 412, speakers, printer 416, or the like. All of these components are well known in the art and need not be discussed at length here.
In this embodiment, remote database 420 contains data indicative of product identifier codes (e.g., SKUs, bar code numbers, universal price codes (UPCs), or the like), pricing data that represents the current prices for the wireless infrastructure components, and model identifier codes (e.g., model numbers, product names, or the like). Remote database 420 can be controlled and managed by any suitably configured database management system such that the data provided by remote database 420 to computing device 400 is formatted in an appropriate manner.
Alternatively (or additionally), memory 406 of computing device 400 serves as an embedded preloaded database for the WLAN planning system. In such an embodiment, some or all of the data mentioned above in the context of remote database 420 can be stored in the embedded database. Such an embedded database can be updated as needed using portable storage media (such as a CD-ROM), a programming device coupled to computing device 400, a downloading procedure that leverages the Internet or another network to which computing device 400 is coupled, or the like. Alternatively (or additionally), computing device 400 can be configured to access a database that resides on a portable storage media (such as a CD-ROM). Such on-demand access to a database stored on a disk may be desirable to ensure that confidential data does not remain in memory 406.
WLAN planning process 500 may begin by receiving floor plan data corresponding to the site of interest (task 502). As an example,
For this embodiment, task 508 recommends wireless infrastructure components along with their associated accessories (which may be optional or required). For example, task 508 can recommend a wireless access device and accessories for the wireless access device, such as, without limitation: adapter cables; compatible antennas; mounting hardware; power supplies; weather proofing kits; or the like. As another example, task 508 can recommend a wireless switch device and related accessories, including, without limitation: PoE switches; L2 hubs; and Ethernet switches. As yet another example, task 508 might recommend a radio antenna and its associated accessories, such as, without limitation: mounting hardware and fixtures; and interconnect cables/wires.
In a practical deployment, an embodiment of WLAN planning process 500 may also support a number of features and operations, many of which are conventional in nature. For example, process 500 might be suitably designed to support one or more of the following features, without limitation: WLAN management; troubleshooting; network monitoring; RF heat mapping; key performance indicator (KPI) graphing; identification of rogue access devices; and displaying network related statistics.
WLAN planning process 500 is suitably designed to obtain one or more of the following items: product identifier codes corresponding to the recommended wireless infrastructure components and accessories (task 510); pricing data for the recommended wireless infrastructure components and accessories (task 512); and model identifier codes for the recommended wireless infrastructure components and accessories (task 514). As described above, the computing device that executes process 500 can obtain this information from: an embedded local database; an attached local database; a remote database, which may be accessed via a network such as the Internet; a portable storage medium; or the like. Thereafter, process 500 can analyze, format, or otherwise process this information as needed.
Eventually, WLAN planning process 500 generates a report (task 516) that is suitably formatted for review by a user. The report may be rendered as a PDF file, a JPEG image file, a file compatible with a word processing application, a file compatible with a spreadsheet application, or the like. In certain embodiments, this report lists the product identifier codes (e.g., SKUs) for the recommended wireless infrastructure components and any identified accessories. This listing enables the user to easily place an order for the recommended components and accessories by referring to their SKUs. In certain embodiments, the report may also include quantity data for the respective wireless infrastructure components and any recommended accessories. For example, the wireless network architecture depicted in
The report generated during task 516 may be displayed, printed, and/or transmitted to a destination device (task 518). In practice, the report can be used as a convenient tool for initiating a purchase order. In certain embodiments, WLAN planning process 500 is suitably designed to generate one or more active ordering links that accommodate online purchasing of the wireless infrastructure components contained in the report (task 520). This optional task is desirable when the host computing device has network connectivity to an appropriate online or remote ordering system. As used here, an active ordering link is any graphically generated user interface control that supports user interaction. For example, active ordering links may be implemented as URL links to an online shopping cart. In certain embodiments, these active ordering links are rendered on the report itself, as depicted in
Product listing report 700 includes entries for the recommended wireless infrastructure devices and their recommended accessories (which may be optional). In contrast to device layout report 600, product listing report 700 may combine identical products together into one line item. For example, the first row 701 in product listing report 700 corresponds to three wireless access devices having the same model number and SKU. For this embodiment, product listing report 700 contains, without limitation: a Label field 702 for the device labels; a Model field 704 that lists the model identifier codes for the devices; an SKU field 706 that lists the SKU codes for the devices; a Description field 708 that provides a brief description of the products; a Price field 710 that lists the purchase price for the products; a Quantity Needed field 712 that indicates the number of units required for each SKU code; and an Order field 714 that contains active ordering links for purposes of online ordering. In practice, the active ordering links contained in Order field 714 allow the operator to launch an online purchase transaction for the listed products. The WLAN planning system described herein can leverage well known online shopping cart techniques and technologies that enable the user to adjust quantities, add and subtract items from the online shopping cart, save an order for purchase at a later time, place an order, etc. Of course, the actual content and format of product listing report 700 may vary from that depicted in
While at least one exemplary embodiment has been presented in the foregoing detailed description, it should be appreciated that a vast number of variations exist. It should also be appreciated that the example embodiment or embodiments described herein are not intended to limit the scope, applicability, or configuration of the claimed subject matter in any way. Rather, the foregoing detailed description will provide those skilled in the art with a convenient road map for implementing the described embodiment or embodiments. It should be understood that various changes can be made in the function and arrangement of elements without departing from the scope defined by the claims, which includes known equivalents and foreseeable equivalents at the time of filing this patent application.
