oneM2M Common Service Layer Resource Discovery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current M2M solutions lack a unified platform for integrating data exchange and sharing across different industry sectors, leading to inefficiencies and limitations in resource discovery and CRUD operations.
Innovation Solution
The oneM2M architecture introduces a distributed software layer with a common service layer that enables inter-sector data exchange, using Common Service Functions (CSFs) like Application and Service Layer Management, Discovery, Registration, and Security to facilitate communication between machines and devices from various sectors.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If separate M2M solutions are used for different industry sectors, then each sector can have specialized functionality, but integration and data sharing across sectors becomes inefficient and complex
Solution Approach 1:
The patent implements a universal service layer architecture that provides common data exchange, device management, and communication services across multiple industry sectors. This service layer acts as a standardized interface that enables different sectors (healthcare, energy, automotive, etc.) to leverage the same infrastructure, eliminating the need for separate specialized solutions while maintaining sector-specific application capabilities through configurable service instances.
2Loss of information
If multiple separate requests are sent for resource discovery and CRUD operations, then comprehensive data can be retrieved, but messaging efficiency and operational time increase
Solution Approach 1:
The patent combines resource discovery and CRUD operations into a single integrated request message. The service layer processes multiple operations (discovery, create, read, update, delete) within one messaging transaction, allowing comprehensive data retrieval and manipulation while significantly reducing the number of separate messages exchanged. This merging eliminates redundant communication overhead and reduces total operational time while maintaining complete data access capabilities.
Data Source
AI summary
A batch of CRUD operations can be coupled with the resource discovery operation and directly conducted on the matched resources, without initiating new CRUD requests. New functionality at the Originator and Receiver can differentiate the resources for which criteria matching is applied from the resources included in the discovery/filtering results. Enhanced functionality at the Originator and Receiver can combine discovery with RESTful operations targeting a resource set different than but related the discovered resources. Other enhancements may be used to request discovery of resources in a specified relationship to those matching a filter, or to request group formation based on the result.