Bluetooth Mesh Routing with Subnets for Low Power
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mesh networking technologies face challenges in efficiently directing messages between peripherals in a network with multiple subnets, particularly in terms of battery life and message latency.
Innovation Solution
The method involves organizing peripherals into multiple subnets and using a hop count and subnet identifier to determine the desired stream direction and subnet for message transmission, allowing peripherals to connect and send messages directly without the need for powered intermediate routing nodes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If powered intermediate routing nodes are used to direct messages between peripherals in multiple subnets, then message routing reliability is improved, but energy consumption increases and battery life decreases
Solution Approach 1:
Peripherals perform self-routing by autonomously determining the desired stream direction (upstream or downstream) and selecting the appropriate subnet based on the destination peripheral's location. Each peripheral uses its own resources (processor, memory, advertising mechanism) to make routing decisions without requiring powered intermediate routing nodes, thereby eliminating the energy consumption associated with maintaining powered routing infrastructure while preserving reliable message delivery through peer-to-peer routing.
Solution Approach 2:
The patent extracts the routing function from dedicated powered intermediate routing nodes and distributes it to all peripherals. By removing the dependency on powered routing infrastructure and enabling any peripheral to perform routing decisions based on subnet identifiers and hop counts, the system eliminates the energy drain of maintaining powered nodes while preserving routing reliability through decentralized peer-to-peer communication.
2Use of energy by moving object
If direct communication between peripherals is enabled without intermediate routing nodes, then battery life is improved, but message latency may increase due to direct connection requirements
Solution Approach 1:
The mesh network is segmented into multiple subnets with distinct identifiers, allowing peripherals to organize communication in structured groups. This segmentation enables efficient routing by confining messages within appropriate subnets rather than requiring network-wide broadcasting, thereby reducing the search space for destination peripherals and minimizing latency while maintaining direct communication benefits.
Solution Approach 2:
Peripherals perform preliminary actions by advertising their presence, subnet identifier, and hop count before actual message transmission. This advance information exchange allows receiving peripherals to pre-determine the desired stream direction and select the optimal routing path, reducing the time required for message delivery while maintaining direct peer-to-peer communication that conserves battery life.
3Reliability
If peripherals advertise continuously to maintain network awareness, then network reliability is improved, but energy consumption increases
Solution Approach 1:
Peripherals engage in periodic advertising rather than continuous transmission, broadcasting their presence, subnet identifier, and hop count at scheduled intervals. This periodic action maintains network awareness and enables reliable message routing while significantly reducing energy consumption compared to continuous advertising, as peripherals can enter low-power states between advertising cycles.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method for communicating amongst a plurality of peripherals within a mesh network including a first subnet and a second subnet including: receiving an advertisement from one or more peripherals of the plurality of peripherals, the adv ertisement including a hop count, a subnet identifier, and a unique subnet device identifier, the subnet identifier indicating the first subnet or the second subnet and the unique subnet device identifier indicating a specific peripheral of the plurality of peripherals within the mesh network; triggering a message send event; determining a desired stream direction within the mesh network; determining a desired subnet of the mesh network; determining a destination peripheral of the one or more peripherals within the desired subnet and in the desired stream direction in response to the hop count, the subnet identifier, and the unique subnet device identifier; connecting to the destination peripheral; and sending the message to the destination peripheral.