Mesh Network Packet Segmentation and Reassembly

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Low-power mesh networks face challenges in transmitting larger data payloads due to size constraints, leading to increased power consumption, packet collisions, and reduced network capacity, with existing segmentation and reassembly methods being inefficient and burdensome for developers.

Innovation Solution

A system that segments an access protocol data unit into multiple segments, concatenates a segment transport header to each segment, and transmits them as segmented access messages, using a unique transaction identifier, segment offset, and total segment fields to enable efficient reassembly and acknowledgment, reducing unnecessary retransmissions and memory allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If larger data packets are transmitted in the mesh network, then the payload capacity is improved, but power consumption increases and packet collisions become more frequent

Engineering Contradiction:
Improvedata payload sizeVSAvoidpower consumption
Core Design Contradiction:
Quantity of substanceVSUse of energy by moving object

Solution Approach 1:

The patent divides large data payloads into multiple smaller segments that can be transmitted within the size constraints of single packets. Each segment is transmitted separately and then reassembled at the destination, allowing large data transfer without increasing individual packet size, thereby avoiding the power consumption and collision issues associated with large packets while maintaining high payload capacity

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If larger data packets are transmitted in the mesh network, then the payload capacity is improved, but the probability of packet collisions increases

Engineering Contradiction:
Improvedata payload sizeVSAvoidpacket collision probability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

By segmenting large payloads into smaller units, the patent reduces the size of individual packets transmitted over the network. Smaller packets occupy the medium for shorter durations and are less likely to collide with other traffic, thereby improving reliability while still enabling transmission of large total data volumes through multiple segments

Inventive Principle:
Principle #1Segmentation

3Adaptability or versatility

If each application performs custom segmentation and reassembly, then the data transport capability is improved, but the device complexity and development burden increase

Engineering Contradiction:
Improvedata transport capabilityVSAvoidsegmentation implementation complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal segmentation and reassembly mechanism at the network layer that serves all applications regardless of their specific data transport needs. This standardized approach eliminates the need for each application to implement its own custom segmentation logic, reducing device complexity and development burden while maintaining adaptability through the flexible segment header design that can accommodate various payload types and sizes

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS10849016B2Packet segmentation and reassembly for mesh networks
Publication Date: 2020.11.24 GOOGLE LLC
  • US10849016B2 patent drawing
  • US10849016B2 patent drawing
  • US10849016B2 patent drawing

AI summary

In aspects of packet segmentation and reassembly for mesh networks, a source node in a mesh network segments an access protocol data unit (PDU) into a set of segments that are concatenated with a segment transport header and transmitted over the mesh network in segmented access messages to a destination node. The destination node allocates memory to store the content of the access PDU based on a segment total field in the segment transport header, and stores each received segment at the appropriate offset in the allocated memory, based on a value of a segment offset filed in each segmented access message. The destination node transmits a segment acknowledgement message including a segment acknowledgement field indicating which of the multiple segments have been received by the destination node.