Obviousness

A rigorous obviousness analysis under 35 U.S.C. § 103 requires specific prior art references that predate the patent's priority date of 2002-10-28. The provided "Prior art keywords" (node, parent node, parent, wireless, nodes) and "Prior art date" (2002-10-28) from the Google Patents page do not identify specific prior art documents (e.g., patents, publications) that can be combined. Without these explicit references, a definitive obviousness determination cannot be made.

However, based on the general technical field indicated by the keywords and the patent's detailed description, one can hypothesize how a Person Having Ordinary Skill in the Art (PHOSITA) in 2002 might have considered combining existing technologies to arrive at the invention of US7885243. The PHOSITA would be an individual with a bachelor's degree in electrical engineering or computer science, or equivalent experience, specializing in wireless networking and embedded systems.

The core of US7885243 describes an adaptive wireless network where "smart" Access Point (AP) nodes provide embedded intelligence and distributed control, while a centralized access server sets high-level parameters to "tune" the network's characteristics (e.g., latency vs. throughput) based on application needs. [cite: The present invention describes an adaptive software layer for a distributed set of wireless communication devices that communicate with each other in a wireless network., The software control layer addresses low latency requirements (for applications such as voice) and high throughput requirements (for applications involving data transfer)., An additional objective of this invention is to allow the characteristics of the network to be set by a centralized access server, which can thus “tune” the character of the network to be anything between the two extremes of low latency to high throughput, based on the needs of applications running in the enterprise.]

Hypothetical Combination of Prior Art References and Motivation:

Let's consider a hypothetical combination of three types of prior art that would likely have been available before the October 28, 2002 priority date:

1. Reference A: A document disclosing IEEE 802.11-based Wireless Mesh Networks (WMNs)

   • This reference would teach the fundamentals of wireless mesh networks, including multi-hop communication, the concept of nodes forming parent-child relationships, and basic routing algorithms to forward data towards a gateway or "root" node. [cite: The root node ( 20 ) acts as the interface between the wireless communication devices ( 30 ) and the Ethernet. All wireless devices ( 30 ) communicate to the Ethernet through a root node ( 20 ), which is has a radio interface and an Ethernet link.] Such networks would inherently provide some level of redundancy through alternate paths. [cite: In this implementation of the invention, redundancy is assured because of the mesh characteristic of the network.]

2. Reference B: A document disclosing Quality of Service (QoS) mechanisms in wireless networks

   • This reference would detail methods for differentiating and prioritizing various types of network traffic, such as voice (requiring low latency) and data (requiring high throughput and reliability), in a wireless environment. [cite: The software control layer addresses low latency requirements (for applications such as voice) and high throughput requirements (for applications involving data transfer).] It would explain how applications have varied latency and throughput requirements and how these can be managed, for instance, through queue servicing rates or priority schemes. [cite: The challenge lies in providing—within the same wireless network—the ability to address potentially conflicting latency and throughput needs of diverse applications., Changing the rate the queue is serviced can also be accomplished by specialized communications between wireless communication devices such as Access Point (AP) nodes and the access server to ensure that voice and data, for example, are serviced at different time intervals.]

3. Reference C: A document disclosing Centralized Network Management Systems for Distributed Network Devices

   • This reference would teach the use of a central server to manage and configure a plurality of distributed network devices (e.g., routers, switches, or early wireless access points). It would describe how a central entity can set policies or parameters that guide the behavior of the individual devices, rather than micro-managing each device's operations. [cite: An additional objective of this invention is to allow the characteristics of the network to be set by a centralized access server, which can thus “tune” the character of the network to be anything between the two extremes of low latency to high throughput, based on the needs of applications running in the enterprise., The Access Server does not change the characteristics of each node, it simply sets the parameters governing the characteristic of the network—and let the AP nodes reconfigure their relationships to meet the objectives set by the Access Server.]

Motivation to Combine References A, B, and C:

A PHOSITA in 2002 would be motivated to combine the teachings of these hypothetical references to address well-known challenges in wireless networking, particularly the growing demand for converged voice, video, and data services over wireless infrastructure.

• Motivation for improved application support in WMNs: The PHOSITA would recognize that basic WMNs (Ref A) often struggle to provide consistent performance for applications with diverse QoS requirements, especially time-sensitive traffic like Voice over IP (VoIP) or video streaming, alongside best-effort data traffic.
• Motivation for scalable and flexible QoS management: While QoS mechanisms (Ref B) were known, implementing them effectively and dynamically across a large, distributed wireless network was complex. Centralized management (Ref C) offered a way to set global policies without the scalability issues of micromanaging each node.
• Motivation for self-configuration and ease of deployment: Deploying and configuring large wireless networks, especially mesh networks, was often a labor-intensive process. A system that could largely self-configure based on high-level goals from a central server would be highly desirable to reduce operational costs and complexity. [cite: Installs out of the box. No site survey or installation involved, since system self configures.]

Therefore, a PHOSITA would be motivated to combine:

1. Distributed intelligence and self-configuration from Ref A and C: Equip the nodes of a wireless mesh network (Ref A) with embedded intelligence to execute distributed algorithms (as suggested by the "smart" AP nodes of US7885243 [cite: an objective of the present invention to develop an adaptive wireless network, based on “smart” communication devices such as Access Points (AP) that provide embedded intelligence at the edge of the network]) guided by overarching parameters set by a central management system (Ref C).
2. Application-aware QoS from Ref B and C: Integrate QoS awareness (Ref B) into the network by allowing the central server (Ref C) to define application profiles and translate them into network-wide latency/throughput constraints. The distributed intelligence at the AP nodes would then interpret these constraints to make local routing decisions. [cite: The objective of this invention is to allow the Access Server to set some latency/throughput constraints that causes each AP node to change their relationships to each other and consequently the character of the network., Control parameters, set by an access server can then tune the wireless network to provide a mix between the two extremes of max throughput and low latency.]
3. Adaptive routing for load balancing and redundancy from Ref A and B: Further, a PHOSITA would combine the mesh routing capabilities (Ref A) with QoS considerations (Ref B) to enable nodes to adaptively select parents (and thus routes) based on current load and desired latency/throughput. This would directly lead to concepts like automatic load balancing and failover, where congested nodes increase their "cost of connectivity" to encourage children to seek alternate paths. [cite: Described thus far is how the parent selection process takes into account latency/throughput criteria set by the access server. However, one must also take into account how the system behaves under load, when the load increases at one node, causing congestion., In FIG. 7 , the cost of connectivity is raised from 0 to 3, resulting in one node “leaving” in favor of a better route.]

The motivation would be to create a more robust, efficient, and easily manageable wireless network capable of seamlessly handling diverse application traffic, which was a significant market need at the time. The specific implementation details (e.g., secure key distribution, low-footprint OS) could be seen as routine engineering choices for embedded wireless devices, drawing upon general knowledge in cryptography and embedded systems development prevalent before the priority date.