Abstract M2M Entity Object for Resource Change Management

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In M2M networks, existing methods for accessing and managing resources, particularly when dealing with unknown devices, face challenges such as errors in message configuration due to strict protocol formats and difficulties in managing resource changes, including device connections and internal environment changes.

Innovation Solution

The solution involves creating an abstract M2M entity object associated with resource changes, which is then instantiated into an M2M entity object suitable for each application development environment, enabling message protocol translation and URI updates to facilitate efficient communication and resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If direct message configuration using strict protocol formats is used for accessing M2M devices, then message transmission can be achieved, but errors occur during message configuration and device access becomes complex

Engineering Contradiction:
Improvemessage transmission reliabilityVSAvoidmessage configuration ease
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent introduces an M2M platform as an intermediary between applications and M2M devices. The platform automatically generates and manages messages according to strict protocols, shielding developers from protocol complexity while ensuring reliable message transmission. The platform acts as a mediator that handles the complex message configuration tasks automatically.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The M2M platform performs self-service by automatically generating messages, managing URI configurations, and handling protocol compliance without requiring manual developer intervention. The system self-manages the complex message configuration processes, reducing errors and simplifying the developer experience.

Inventive Principle:
Principle #25Self-service

2Productivity

If manual URI management is used for resource access in M2M networks, then resource access is possible, but resource change management becomes difficult and time-consuming

Engineering Contradiction:
Improveresource access efficiencyVSAvoidresource change management time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements a feedback mechanism where the M2M platform continuously monitors resource changes in the network and automatically updates URI configurations. When resources change, the platform receives feedback about these changes and automatically adjusts message routing and URI management, eliminating manual intervention and reducing time loss.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The M2M platform performs preliminary actions by pre-configuring URI lists and message templates before resources are accessed. When resources change, the platform has already established the framework for quick adaptation, reducing the time required for resource change management.

Inventive Principle:
Principle #10Preliminary action

3Loss of information

If direct access to unknown M2M devices is attempted, then device functionality can be discovered, but the process becomes complex requiring multiple standardized communication steps

Engineering Contradiction:
Improvedevice information acquisitionVSAvoiddiscovery process complexity
Core Design Contradiction:
Loss of informationVSDevice complexity

Solution Approach 1:

The M2M platform serves as an intermediary that simplifies the discovery process. Instead of requiring applications to directly perform complex standardized communication sequences with unknown devices, the platform handles the discovery automatically, reducing process complexity while acquiring necessary device information.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates abstract M2M entity objects that represent actual M2M devices. These objects contain copied essential information and functionality interfaces, allowing applications to interact with simplified representations rather than dealing with the complexity of actual device discovery and communication protocols.

Inventive Principle:
Principle #26Copying

4Adaptability or versatility

If abstract M2M entity objects are automatically created and instantiated, then resource change management is simplified and compatibility is enhanced, but system architecture complexity increases

Engineering Contradiction:
Improveenvironmental change adaptabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent creates universal abstract M2M entity objects that can represent different types of M2M devices through a common interface. This universal approach enhances adaptability to environmental changes while managing architecture complexity by providing a standardized framework that works across diverse device types.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system architecture is segmented into distinct layers: abstract M2M entity objects, concrete device implementations, and application interfaces. This segmentation allows the system to handle complexity in manageable sections, where each layer has specific responsibilities, enhancing adaptability without overwhelming the overall system complexity.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS9832076B2Resource change management in machine to machine network
Publication Date: 2017.11.28 KT CORP
  • US9832076B2 patent drawing
  • US9832076B2 patent drawing
  • US9832076B2 patent drawing

AI summary

The disclosure is related to managing a resource change in a machine to machine (M2M) network. Managing the resource change in M2M network by creating an abstract M2M entity object associated with a resource change, and creating an M2M entity object instance by embodying the abstract M2M entity object according to each application development environment.