Patent Application
20070258368
Typically, messages sent within data packets traverse the communications network 100 by hopping from one network device to another network device until the data packets reach their destination. Usually these data packets jump between adjacent network devices, called neighbors e.g., neighboring network devices 102 and 104, network devices 108 and 110, et cetera. Generally, data network topologies provide for a generous number of interconnections among neighboring network devices throughout the network 100.
Each network device in the communications network 100 computes a source tree (or routing table) that defines the paths to all neighboring network devices within its reach. These neighbors communicate with one another efficiently using special messages that propagate the data network. Changes in the data network are reported regularly to make the end-to-end configuration dynamic.
Link metrics may be used to maximize performance as traffic moves edge-to-edge through the data network. These metrics can be based on measuring signal strength, stability, transfer rate, bit error rate, latency, number of hops, or other ‘per link’ parameters. Each link therefore carries a ‘cost’ and the overall load can be balanced efficiently by whatever path presents the least cost.
The communications between network devices 102-114 may have self-management, self-configuring, self-tuning, self-healing and self-monitoring capabilities. A management console (e.g., running on laptop 124) may be used to provide a visualization of actual interconnections between nodes 102-114, and may also provide a means to monitor the communication network's 100 status from edge-to-edge, and provide performance and activity statistics. The console may also provide some form of command and control over the communications network 100, including network device updates, software upgrades, and reconfigurations.
Security is a major concern for data networks. Traffic within communications network 100 preferably should be secured and outside devices, including data sources and those that use the data network's Ethernet services, should be prohibited from accessing internal data network traffic. Features like digital signatures can be used to ensure that only authorized systems participate in the wireless network. User traffic between nodes can also be encrypted to prevent eavesdropping, for instance, by using 128-bit and 256-bit AES encryption, WEP, or the like. The communications network 100 may also support other security standards available on other Ethernet-based and wireless networks. Compatibility with any end-to-end security provisions, such as virtual private networks (VPNs), may also be implemented for securing over-the-air communications between network devices.
In setting up a communications network with known network devices, each network device of the network needs to be communicated with and the parameters configured individually. In addition, it is not unusual for an address or encryption code to be incorrectly assigned, thus rendering a network device completely inaccessible from the network. Correction of these types of errors are often difficult and laborious. Since many potential users of a communications network may not have a strong understanding of data networks for the setup of network devices, it is desirable to have a simple setup process catering for such users.
Accordingly, user interface 200 provides users of network devices with an exemplary interface that configures network parameters based on user selection of virtual “channels”. Accordingly, user interface 200 includes a channel selector 202, a channel indicator 204, a node selector 206, a node indicator 208. Channel selector 202 and node selector 206 may be push button, toggle, or rotatable switches that are used to select the channel and node respectively. Channel and node selection may also or alternatively be performed via a remote device, e.g., RF or infrared remote control, or over the communications network via a client or browser-based interface (not shown). Channel indicator 204 represents a communications “channel,” and node indicator 208 represents the node address of the network device 102, which may be displayed on a digital display e.g., using mechanical digits, liquid crystal digits, LED, LCD/TFT panel displays, et cetera.
In an embodiment of a wireless network device, in selecting a channel via channel selector 202, the wireless network device with which the user interface 200 is associated may select a combination of a particular frequency channel and, in some instances, one of several predetermined encryption keys, and a Service Set Identifier (SSID). The node indicator 408 shows a number that is associated with a network address of the network device according to a predetermined mapping. Table 1 provides an exemplary mapping of selected “channels” to map to frequencies, encryption keys, SSIDs (not shown) and network (most likely Internet Protocol) addresses. Note that other mapping schemes are possible and likely to be used for different implementations of the network device.
In the below example, for a wireless node, communication channels may map to 802.11 frequency channels, SSIDs and pre-configured encryption keys. The following list illustrates an exemplary mapping of channel numbers:
Node identifiers map to IP addresses. Node identifier number is an offset to be added to pre-configured base IP address. It should be noted that this exemplary mapping is shown for IEEE 802.11b/g US product. The mapping may be different for other countries or standards.
The set of predetermined encryption keys and the base IP address may be configurable via an embedded web-server interface that can be accessed across the network from a computer with a web browser.
With this type of user interface 200, a user that is unfamiliar with network device configuration can simply select the desired virtual communications “channel” and the node identifier to which the associated video input is assigned. Each node on the same channel should have a unique node identifier.
A similar user interface 200 may be represented on a remote computer-based graphical control panel (i.e., a client, web browser, et cetera). The net result is that the rather esoteric frequency channels, encryption keys and IP addresses can be assigned automatically for the user without the necessity of understanding the technical aspects of these parameters. Consequently, the non-technical user may now find the configuration and use of the data network to be much more accessible and less intimidating than was previously the case with conventional network devices. In addition, the probability of an error rendering a network device inaccessible is less likely and easily corrected if it does happen.
As one of ordinary skill in the art will appreciate, the term “operably coupled”, as may be used herein, includes direct coupling and indirect coupling via another component, element, circuit, unit, or module where, for indirect coupling, the intervening component, element, circuit, unit, or module does not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As one of ordinary skill in the art will also appreciate, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two elements in the same manner as “operably coupled”.
Having described several embodiments, it will be recognized by those of ordinary skill in the art that various modifications, alternative constructions, and equivalents may be used without departing from the spirit of the disclosed embodiments. Accordingly, the presently disclosed embodiments are therefore considered in all respects to be illustrative and not restrictive. The scope of the invention is indicated by the appended claims rather than the foregoing description, and all changes that come within the meaning and ranges of equivalents thereof are intended to be embraced therein.
Additionally, the section headings herein are provided for consistency with the suggestions under 37 C.F.R. § 1.77 or otherwise to provide organizational cues. These headings shall not limit or characterize the invention(s) set out in any claims that may issue from this disclosure. Specifically and by way of example, although the headings refer to a “Technical Field,” the claims should not be limited by the language chosen under this heading to describe the so-called technical field. Further, a description of a technology in the “Background of the Invention” is not to be construed as an admission that technology is prior art to any invention(s) in this disclosure. Neither is the “Brief Summary of the Invention” to be considered as a characterization of the invention(s) set forth in the claims found herein. Furthermore, any reference in this disclosure to “invention” in the singular should not be used to argue that there is only a single point of novelty claimed in this disclosure. Multiple inventions may be set forth according to the limitations of the multiple claims associated with this disclosure, and the claims accordingly define the invention(s), and their equivalents, that are protected thereby. In all instances, the scope of the claims shall be considered on their own merits in light of the specification, but should not be constrained by the headings set forth herein.
This application claims the benefit of U.S. Provisional Application Ser. No. 60/746,577, filed on May 5, 2006, and entitled “Network device user control interface,” which is commonly assigned with the present application and incorporated herein by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60746577 | May 2006 | US |
