M2M Service-to-Management Interface for Cross-Protocol Group Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current device management protocols lack standardized interfaces for communication between M2M servers and DM servers, requiring custom developments for each service provider, limiting efficiency and interoperability, and do not support enhanced group management operations in an end-to-end architecture.
Innovation Solution
Introduce new message formats and resource attributes for group management procedures to standardize the interface between the service layer and management layer, enabling group-on-group operations and interoperability among different device management protocols.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If custom API interfaces are developed for each service provider to support different device management protocols, then interoperability between systems is limited, but the ability to communicate with specific device protocols is achieved
Solution Approach 1:
The patent introduces a universal service layer interface that can handle multiple device management protocols (OMA DM, OMA LWM2M, BBF CWMP) through a single standardized API. The service layer acts as a protocol-agnostic intermediary that translates between the standardized interface and protocol-specific implementations, eliminating the need for separate custom interfaces for each protocol while maintaining full protocol compatibility
Solution Approach 2:
The service layer serves as an intermediary component between the application layer and the device management protocols. It provides a standardized interface that mediates all communications, translating generic service layer commands into protocol-specific operations. This mediator approach allows the system to work with multiple protocols without requiring custom interfaces for each one
2Adaptability or versatility
If individual device management is used following traditional DM protocols, then existing protocols can be maintained, but group management operations are not supported
Solution Approach 1:
The patent merges individual device management capabilities with group management functionality into a unified framework. The service layer enables batch operations that can simultaneously manage multiple devices by combining their individual management operations into single group-level commands. This allows existing protocol mechanisms to be leveraged while adding efficient group management capabilities
Solution Approach 2:
The patent adds a group management dimension to the traditional individual device management model. By introducing group-level abstractions in the service layer, the system can operate at both individual device level and group level, enabling efficient bulk operations without sacrificing individual device control capabilities. This dimensional extension allows simultaneous management of multiple devices through group operations
3Adaptability or versatility
If standardized interfaces are introduced between service layer and management layer, then interoperability is enhanced, but development complexity increases
Solution Approach 1:
The patent segments the system into distinct layers with clear responsibilities: the service layer provides standardized interfaces, while protocol-specific implementations are separated into independent modules. This segmentation allows the standardized interface to be developed once and reused across multiple protocols, reducing overall implementation complexity despite the added standardization layer
Data Source
Figure 1A
Figure 1B
Figure 1C
AI summary
The present application is directed to a computer-implemented device and method for performing group-on-group operations over the M2M interface. The device and method includes the step of receiving a request to initiate the group-on-group operation from a device owner including commands of a group resource defined in a uniform resource indicator. The device and method includes the step of processing the request and also a step for sending a group management request API to a management server to execute the commands on the devices. Further, there is a step of receiving a response from the management server indicating execution status of the commands by the device. The application also is directed to a computer-implemented method for establishing group-on-group operation over the M2M interface.