Service Layer Cache Management for IoT Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Machine-to-Machine (M2M)/Internet of Things (IoT) Service Layer implementations lack capabilities to manage cached resources effectively, leading to synchronization issues between original resources and cached copies, inadequate access control, and a lack of statistics for resource management.
Innovation Solution
Implementing caching mechanisms at the Service Layer that allow a Caching Entity to create, refresh, update, and delete cached resources, while the Original Hosting Entity maintains a registry and sets cache parameters, enabling complete access control and subscription features, and obtaining statistics for resource management.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If caching mechanisms are implemented at the Service Layer, then latency is reduced and throughput is improved, but device complexity increases due to the need for cache management capabilities
Solution Approach 1:
The patent introduces a Service Layer as an intermediary between the Application Layer and Network Service Layer. This Service Layer contains a cache management component that acts as a mediator, intercepting resource access requests, managing cached copies, and coordinating with both the original resource hosting entity and accessing entities. This intermediary approach reduces latency by serving cached resources locally while maintaining standardized interfaces that hide the complexity of cache management from end applications.
Solution Approach 2:
The patent implements a copying mechanism where cached resources are created as copies of original resources and stored in the Service Layer cache. These cached copies are maintained with references to their original resources, allowing the system to serve fast copies while preserving the ability to update from originals. This copying strategy reduces latency for resource access while the standardized copy management protocols prevent complexity from propagating to application entities.
2Reliability
If cached resources are managed with complete access control and subscription features, then security and resource management are improved, but device complexity increases due to additional management functions
Solution Approach 1:
The patent merges multiple functions including cache management, access control, and subscription services into a unified Service Layer architecture. The Service Layer consolidates these previously separate functions into a single coordination point, managing cached resources with integrated access control policies and subscription capabilities. This merging improves reliability by ensuring consistent security enforcement while reducing overall system complexity by eliminating the need for distributed implementation of these functions across multiple entities.
Solution Approach 2:
The Service Layer is designed as a universal component that performs multiple functions: caching resources, controlling access to cached resources, managing subscriptions to resource updates, and coordinating with original resource hosts. This multi-functional design improves reliability by providing comprehensive resource management in a single layer while preventing complexity multiplication through standardized interfaces that handle all these functions centrally.
3Stability of the object's composition
If the Original Hosting Entity maintains a registry of cached resources, then synchronization and resource tracking are improved, but device complexity increases due to registry management overhead
Solution Approach 1:
The patent implements a registry mechanism where the Original Hosting Entity pre-registers cached resource copies before they are created or when they are first cached. This preliminary registration establishes the relationship between original resources and their cached copies, enabling automatic synchronization tracking. The registry is maintained with minimal overhead by only recording essential metadata (resource identifiers, cache location, expiration information) rather than full resource states, thus improving synchronization while limiting complexity increase.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A caching entity may store a cached copy of a service layer resource. An original hosting entity may maintain a registry of the corresponding cached resources. Optionally, the original hosting entity may set cache parameters to govern the lifetime of the cache on a caching entity. The caching entity may keep storing the cached copy of the resource and the original hosting entity may obtain statistics about the cached resource. By knowing the statistics, e.g. how many times a resource is retrieved on each caching entity, the original hosting entity may better manage the resource.