Common Capability Component Device State Synchronization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In IoT systems, existing methods for device state synchronization between a representation state and an actual state often lead to reduced system availability due to resource locking, inefficient processing, and inability to handle multiple update requests simultaneously, resulting in inconsistent states and resource wastage.
Innovation Solution
A device state synchronization method where a common capability component maintains multiple representation state instance resources, allowing sequential or latest state updates, and manages synchronization based on update modes (sequence, latest, moment, duration, or mixed) to improve processing efficiency and handle multiple requests effectively.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the CSE locks the resource when receiving a resource update request, then resource consistency is ensured, but system availability is reduced
Solution Approach 1:
The patent segments the resource update process into multiple independent stages: resource locking for consistency validation, asynchronous notification sending, and state update. By dividing the monolithic update operation into smaller granular steps, the system can lock resources only when necessary for consistency checks while allowing other operations to proceed asynchronously, thus maintaining both resource consistency and system availability.
Solution Approach 2:
The patent performs preliminary consistency validation and resource locking before the actual state update, then sends notifications asynchronously. This preliminary action ensures that resource consistency is verified upfront, allowing subsequent operations to proceed without holding locks, thereby improving system availability while maintaining consistency guarantees.
2Reliability
If the CSE rejects another request when a resource update request is being processed, then resource consistency is maintained, but processing efficiency is reduced
Solution Approach 1:
The patent implements dynamic request handling where the CSE can accept multiple update requests concurrently but processes them in a controlled manner. Instead of statically rejecting all requests during processing, the system dynamically manages request queues, prioritizes critical updates, and processes non-critical updates asynchronously, thereby maintaining resource consistency while improving overall processing efficiency.
Solution Approach 2:
The patent ensures continuous processing of update requests by implementing an asynchronous notification mechanism. While one request is being processed, other requests can be queued and prepared for processing. The notification system continues to send updates to devices even as new requests arrive, ensuring that useful actions (state updates and notifications) continue without interruption, thus improving processing efficiency while maintaining consistency.
3Reliability
If the CSE sends a notification to the device after resource update, then device state synchronization is achieved, but processing time is increased
Solution Approach 1:
The patent sends notifications in advance or in parallel with the actual state update process rather than waiting for complete synchronization. The CSE can pre-notify devices of upcoming state changes or send notifications asynchronously while the device state is being updated in the background, thereby achieving device state synchronization while minimizing additional processing time.
Solution Approach 2:
The notification sending process runs continuously and asynchronously alongside the state update operations. Instead of pausing the update process to send notifications, the system maintains continuous useful actions by performing state updates and sending notifications in parallel threads or asynchronous task queues, thus achieving synchronization without significant time loss.
Data Source
AI summary
This application discloses a device state synchronization method. The method performed by a common capability component, the method includes: receiving a first representation state instance resource creation request sent by an application, where the first representation state instance resource creation request includes a device state attribute; creating a first representation state instance resource based on the first representation state instance resource creation request and a created second representation state instance resource; sending a device state update request to a device, where the device state update request includes the device state attribute; receiving an actual state instance resource creation request sent by the device; creating an actual state instance resource based on the actual state instance resource creation request; and sending to the application, information indicating that an actual state resource is successfully created.