Patent 8144717

Prior art

Earlier patents, publications, and products that may anticipate or render the claims unpatentable.

Active provider: Google · gemini-2.5-flash

Prior art

Earlier patents, publications, and products that may anticipate or render the claims unpatentable.

✓ Generated

To identify the most relevant prior art for US Patent 8144717, I will examine the "References Cited" section of the patent itself. The USPTO's Patent Public Search tool and Google Patents provide this information.

Based on the provided patent text, here are the prior art references cited in US Patent 8144717:

US Patent Application No. 2003/0151513

  • Full Citation: US Patent Application No. 2003/0151513 (US 2003/0151513 A1)
  • Publication/Filing Date: The patent mentions its publication number, US 2003/0151513 A1, indicating it's a published application. No specific filing or publication date is given within the provided text, but the format suggests a publication date in 2003.
  • Brief Description: This patent application describes a wireless sensor station network where data is transmitted in multiple hops to a central panel. It details methods for dynamically forming network topology and routes from sensor stations to cluster head units using link discovery messages and route discovery packets. It also mentions that link discovery packets function to synchronize communication clocks. In one embodiment, sensor stations select routes based on the least number of hops, and then send route registration packets. In another embodiment, the association unit selects routes from received link registration messages and sends route definition messages.
  • Potential Anticipated Claims (35 U.S.C. § 102):
    • Claim 1, 11, 14 (Method of operating a wireless communication network, Wireless Communication Network, Station for wireless communication network): The core concept of establishing routes in a multi-hop wireless network with a central unit and stations that can forward messages is present in US 2003/0151513. The patent explicitly states that a "problem with these techniques is that they require transmission of information via sensor stations before the routing topology has been defined, i.e. when plural routes are still possible." This indicates that elements of network initialization, route definition, and stations participating in routing were known. The method of having stations in a "not-associated state" transmit requests, and subsequently defining routes, appears to have parallels.

"TBONE: A Mobile-Backbone Protocol for Ad Hoc Wireless Networks" by Izhak Rubin et al.

  • Full Citation: "TBONE: A Mobile-Backbone Protocol for Ad Hoc Wireless Networks" by Izhak Rubin et al., published in the IEEE Aerospace Conference proceedings 2002 (Piscataway N.J., Mar. 9-16, 2002) page 2727-2740.
  • Publication/Filing Date: March 9-16, 2002 (publication date of the proceedings).
  • Brief Description: This article describes a mobile communications protocol that uses two types of networks: a high-power backbone network (BNET) and multiple low-power networks (ANETs). Devices initially decide whether to operate as backbone nodes based on qualifications. Backbone nodes then receive join requests from other nodes to form ANETs. The article also mentions a scenario where an existing backbone node can command another backbone-capable device to become a backbone node to grant a join request that couldn't otherwise be accepted. It notes that "No provision is made for routing through successive previously established low power network (ANET) nodes and association for this form of routing."
  • Potential Anticipated Claims (35 U.S.C. § 102):
    • Claim 1, 11, 14 (Method of operating a wireless communication network, Wireless Communication Network, Station for wireless communication network): This reference discusses dynamic network formation, different types of nodes (backbone vs. low-power), and a process of nodes "joining" the network. The concept of a hierarchical network structure (BNET and ANETs) and nodes making decisions about their role in the network (e.g., becoming a backbone node) could be seen as broadly relevant to the initialization and association processes described in the claims. However, the patent explicitly distinguishes itself by stating that TBONE makes "No provision...for routing through successive previously established low power network (ANET) nodes and association for this form of routing," implying a difference in how routes are established and utilized for subsequent communication.

Generated 5/29/2026, 6:47:22 AM