Resource Representation Common Part for LPWAN Message Size Reduction
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Low-Power Wide-Area Networks (LPWAN) face challenges in supporting large resource representations due to limited communication bandwidth and strict message size requirements, leading to inefficiencies in data exchange between Service Layer entities, especially when traditional compression algorithms incur computation costs that are not feasible for constrained IoT devices.
Innovation Solution
The introduction of a Resource Representation Common Part (RRCP) stored at the Service Layer, which reduces message sizes by allowing only the RRCP identifier to be transmitted, enabling efficient resource creation, update, and retrieval operations without the need for full resource representation, thus accommodating LPWAN constraints.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If traditional compression algorithms are used to reduce resource representation size, then message size is reduced, but computation cost increases which is not affordable for constrained IoT devices
Solution Approach 1:
The patent pre-processes and stores common resource representation parts (RRCP) at the service layer before they are needed for message transmission. By performing the compression and organization work in advance, the system avoids real-time computation during message exchange, thus reducing computation cost for constrained IoT devices while maintaining small message sizes.
Solution Approach 2:
The patent creates a simplified copy or reference (RRCP identifier) instead of transmitting the full resource representation. This copy contains only essential information needed to reconstruct or access the original data, significantly reducing message size without requiring complex compression algorithms during transmission, thereby minimizing computation cost.
2Loss of information
If full resource representation is transmitted between Service Layer entities, then data completeness is maintained, but message size exceeds LPWAN constraints
Solution Approach 1:
The patent segments the resource representation into two parts: a common part (RRCP) stored at the service layer and a specific part transmitted in messages. The RRCP contains shared attributes that remain constant, while only variable or device-specific attributes are transmitted. This segmentation maintains data completeness by ensuring the receiver can reconstruct the full resource representation using the transmitted specific part plus the stored common part, while keeping message size within LPWAN constraints.
Solution Approach 2:
The patent extracts and separates the common, reusable portion of resource representations (RRCP) from the full data structure. By taking out this common part and storing it independently at the service layer, the system only needs to transmit the remaining variable portions in messages, thus maintaining data completeness while reducing message size to fit LPWAN limitations.
3Quantity of substance
If resource representations are optimized for small message size, then LPWAN constraints are met, but resource management efficiency decreases
Solution Approach 1:
The patent creates a universal RRCP structure that serves multiple functions: it acts as a template for resource creation, a reference for resource updates, and a storage mechanism for common attributes. This multi-functional design allows the same RRCP to be reused across different resource management operations and multiple devices, thereby maintaining resource management efficiency while keeping message sizes small for LPWAN compliance.
Data Source
AI summary
Some underlying networks such as Low-Power Wide-Area Networks (LPWAN) have limited communication bandwidth and strict requirements on maximum message size. These requirements may pose a challenge for data or resource exchange between two service layer (SL) entities, for example, because resource representations to be exchanged may have too large a size to be supported by the underlying networks. In some cases, traditional data compression algorithms can be used to alleviate this problem to some degree, but it is recognized herein that there are associated computation costs due to compression and decompression that may not be affordable for constrained IoT devices. Various embodiments described herein address this problem, among others by defining a Resource Representation Common Part (RRCP) and storing it at the service layer. In some cases, the RRCP is not transmitted between SL entities, thereby reducing SL message sizes to cater to the constraints of underlying networks.