CoAP Request Status Resource for Low-Battery Client Polling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Constrained Application Protocol (CoAP) networks face inefficiencies due to clients waiting for responses from servers, leading to battery drain and resource waste, especially in scenarios where processing times exceed the default ACK_TIMEOUT, and continuous pinging is required to check resource status.
Innovation Solution
The server creates a second resource indicating the status of a confirmable request, allowing clients to sleep or disconnect, and sends a response with a path to the second resource, including a time 'tind' to ping for updates, reducing unnecessary message exchanges and battery consumption.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the server responds with an empty ACK message when not able to respond immediately, then the client can stop retransmitting the request, but the client suffers by waiting for the response or retransmitting the request leading to battery drain
Solution Approach 1:
The server performs preliminary actions by creating a second resource representing the confirmable request and sending a response with a path to this resource and a ping time indicator. This allows the client to know in advance when to query for the request status without continuously pinging or waiting, thereby reducing battery consumption while maintaining reliable request tracking.
2Loss of information
If the client continuously pings the server to check resource status, then the client can obtain timely updates, but unnecessary message exchanges increase overhead and resource consumption
Solution Approach 1:
The server provides feedback by sending a response that includes a path to a second resource representing the confirmable request and a ping time indicator. This feedback mechanism informs the client exactly when to query for status updates, eliminating the need for continuous pinging and reducing unnecessary network message exchanges while ensuring the client receives timely status information.
3Reliability
If the client waits for the response from the server within the ACK_TIMEOUT period, then the client can maintain protocol compliance, but processing time is wasted when server processing exceeds the timeout
Solution Approach 1:
The server performs preliminary actions by creating a second resource to represent the confirmable request and sending a response containing the path to this resource along with a ping time indicator. This preliminary setup allows the client to comply with the protocol by querying the second resource at the specified ping time rather than continuously waiting or retransmitting, thereby reducing wasted waiting time while maintaining protocol compliance.
Data Source
AI summary
A network (200), a client (210), a server (220), a method, a computer program and a computer program product for providing and receiving information about a first resource hosted at the server is disclosed. The network comprises the client and the server. The network receives at the server from the client, a first CoAP message comprising a confirmable request relating to the first resource, creates a second resource at the server, wherein the second resource indicates a status of the confirmable request, sends to the client from the server, a second CoAP message comprising a response including a path of the second resource, sends to the server from the client, the first CoAP message and receives from the server at the client, the second CoAP message.