Multicast Acknowledgment Frame for LoRaWAN Terminal Groups
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for acknowledging frames from multiple terminals in LoRa networks are inefficient, as they require individual acknowledgments that monopolize network resources and are tedious to implement.
Innovation Solution
A method that uses a single multicast frame to acknowledge multiple frames, containing fields for time setting, next wake-up date, group identifier, and frame acknowledgment status, transmitted by the centralizing server, allowing terminals to efficiently check their acknowledgment status and adjust their sleep schedules accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If individual acknowledgments are sent to each terminal, then each terminal receives reliable confirmation of its frame transmission, but network resources are monopolized and the acknowledgment process becomes cumbersome
Solution Approach 1:
The patent merges multiple individual acknowledgments into a single multicast acknowledgment frame that can confirm receipt of frames from multiple terminals simultaneously. This consolidation approach maintains reliable acknowledgment for each terminal while dramatically improving network resource efficiency by reducing the number of separate acknowledgment transmissions required.
Solution Approach 2:
The acknowledgment frame is designed with universal applicability to serve multiple terminals at once. By incorporating multiple terminal identifiers and corresponding acknowledgment bits within a single frame structure, the system achieves multi-functionality where one frame performs the work of many individual frames, resolving the contradiction between reliability and productivity.
2Reliability
If multiple individual acknowledgment frames are transmitted, then each terminal's frame status is confirmed, but the acknowledgment process becomes tedious and complex to implement
Solution Approach 1:
The patent combines multiple acknowledgment operations into a single unified multicast frame transmission. This merging eliminates the need for complex coordination of multiple separate acknowledgment processes, significantly simplifying the overall implementation while maintaining complete frame status confirmation for all terminals.
Solution Approach 2:
The acknowledgment frame structure incorporates variable parameters including multiple terminal identifiers, acknowledgment status bits for each terminal, and optional retransmission request flags. This parameter-based design allows the single frame to adaptively handle different acknowledgment scenarios for multiple terminals, reducing complexity compared to fixed individual acknowledgment protocols.
3Loss of information
If terminals continuously monitor for acknowledgments, then they can detect frame transmission status, but energy consumption increases
Solution Approach 1:
The patent implements periodic acknowledgment transmission where the network sends multicast acknowledgment frames at scheduled intervals rather than requiring continuous terminal monitoring. Terminals wake up at predetermined times to receive acknowledgments and then return to sleep mode, dramatically reducing energy consumption while ensuring terminals detect their frame transmission status through these periodic checks.
Data Source
Figure 1~2A
Figure 2B
Figure 2C~6
AI summary
A method enabling an application server to acknowledge, with a single acknowledgment frame, a set of frames transmitted by terminals within a group of terminals destined for said application server. Each terminal in the group communicates with the application server via a gateway and a central server. The application server is connected to the central server via a primary communication network. The central server is connected to each gateway via a secondary communication network. The group of terminals and each gateway form a LoRa network, with each communication between a terminal in the group and a gateway using the LoRaWAN protocol.