M2M Data License Management via RESTful Resource Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M systems lack effective mechanisms for managing data licenses, including adding data license information, checking proper usage, and exchanging license information between platforms, which hinders efficient data management and sharing.
Innovation Solution
Implementing a RESTful-based API in the M2M system to manage data licenses through resources like the resource, which includes attributes for license management, enabling operations like creation, retrieval, and deletion, and allowing devices to check and enforce license compliance during data operations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If data license management mechanisms are implemented in M2M systems, then data sharing security and compliance are improved, but system complexity increases
Solution Approach 1:
The patent introduces a license server as an intermediary component that centralizes license management functions. The license server stores license information, validates data access requests, and communicates licensing status between data providers and consumers. This mediator approach improves data license compliance reliability while containing system complexity by consolidating management logic in a dedicated component rather than distributing it across all M2M devices.
Solution Approach 2:
The patent segments the M2M system into distinct functional components: data storage units, license management units, and validation units. Each component has a specific responsibility - data storage holds the actual data, license management stores and retrieves license information, and validation checks compliance. This segmentation allows the system to handle license compliance reliably through specialized components while managing complexity by dividing the overall system into manageable, independent modules.
2Reliability
If license information is stored with data, then data access control is improved, but data management complexity increases
Solution Approach 1:
The patent implements a nested structure where license information is embedded within or associated with data containers. The data storage unit holds data, and the license management unit contains license information that is logically nested with the data it protects. This nesting allows access control to be enforced at the data level without requiring separate external verification systems, improving control reliability while managing complexity through hierarchical organization.
Solution Approach 2:
The patent creates a universal data container structure that simultaneously holds data, license information, and access control metadata. This multi-functional container serves multiple purposes: storing actual data, managing licensing, and enforcing access control policies. By making the data structure itself multi-functional rather than requiring separate systems for each function, the patent improves access control reliability while reducing overall data management complexity.
3Adaptability or versatility
If data is shared across multiple platforms, then data utility is improved, but license management complexity increases
Solution Approach 1:
The patent uses the license server as a mediator that enables cross-platform data sharing without requiring each platform to implement its own license management system. The license server receives data access requests from any platform, validates them against stored license information, and returns authorization decisions. This intermediary approach improves data sharing versatility across multiple platforms while containing license management complexity in the centralized server that handles all platforms uniformly.
Data Source
AI summary
The present disclosure related to managing a data license in a machine-to-machine (M2M) system, and a method for operating a first device may include generating a first resource including data and a second resource including information for managing a license of the data, receiving a message for requesting an operation for the data from a second device, determining, based on the information in the second resource, whether the operation is permitted, and transmitting a second message for performing the operation to the second device or a third device.