LWM2M Remote Script Execution for IoT Constrained Devices
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
There is currently no standardized method for enabling remote scripting on constrained devices in IoT applications using CoAP and LWM2M, leading to scalability issues and changes in scripting methods when devices switch between management servers.
Innovation Solution
A standardized method for enabling remote script execution on constrained devices is provided through the Lightweight Machine-to-Machine (LWM2M) protocol, where a LWM2M protocol server transmits a message with script access information to the client, including resource indicators and execution rules, allowing automatic script execution based on device attributes and output handling.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If proprietary methods are used to upload and execute scripts on constrained devices, then scripting functionality can be achieved on individual devices, but scalability is limited and methods change when devices switch between management servers
Solution Approach 1:
The patent applies universality by creating a standardized script management interface that works across multiple device management servers and constrained devices. The LWM2M protocol defines universal objects (Script Sandbox, Script Trigger, Script Output Recipient) that can be used by any server to manage scripts on any compliant device, eliminating the need for proprietary methods specific to each server or device type.
Solution Approach 2:
The patent uses parameter changes by defining specific LWM2M object parameters such as Script URI, Script Sandbox ID, Trigger resource paths, and Output recipient configurations. These parameters allow the same standardized interface to adapt to different scripting scenarios and device types without changing the fundamental management approach, enabling scalability while maintaining consistency.
2Productivity
If scripts are executed on constrained devices with limited memory and power, then remote functionality can be extended, but device resource consumption increases
Solution Approach 1:
The patent applies self-service by enabling constrained devices to execute scripts locally using their own processing power and memory resources. The device autonomously interprets and runs script code received from the management server, performing computations and data processing tasks that would otherwise require continuous server communication, thereby extending remote functionality while managing device resources efficiently.
Solution Approach 2:
The patent uses periodic action through Script Trigger objects that can schedule script execution based on time intervals, resource changes, or external events. This allows scripts to execute only when needed rather than continuously, optimizing the use of limited device power and memory resources while maintaining the ability to perform remote scripting tasks on demand.
3Adaptability or versatility
If standardized protocol messages are used for script management, then interoperability between different servers is improved, but message format complexity increases
Solution Approach 1:
The patent applies segmentation by dividing script management functionality into separate LWM2M objects: Script Sandbox (for storing and managing script code), Script Trigger (for defining execution conditions), and Script Output Recipient (for handling script results). This modular approach allows each object to be managed independently through standardized LWM2M operations, improving interoperability while keeping individual message formats manageable and well-defined.
Data Source
AI summary
A standardised method is provided for enabling remote script execution on a constrained device. The method comprises transmitting a first Lightweight Machine-to-Machine, LWM2M, protocol message from a LWM2M protocol server to a LWM2M protocol client on the constrained device. A content of the first LWM2M message is such that the LWM2M protocol client has access to a script. The method also comprises transmitting information about execution of the script from the LWM2M protocol server to the LWM2M protocol client in a LWM2M protocol message.