M2M Resource Deletion via Confirmation-Based Operation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current M2M systems lack a robust mechanism for discreet data deletion based on data importance, leading to potential errors and user experience issues, as existing deletion methods do not account for the characteristics of the data or resources being deleted.

Innovation Solution

A confirmation-based operation method is introduced in M2M systems, where deletion of resources is performed only after obtaining confirmation from the originator, with optional attributes like time-window and operation ID management to ensure accurate and user-verified data removal.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If automatic deletion without confirmation is implemented, then productivity is improved, but reliability deteriorates due to potential errors in deleting critical data

Engineering Contradiction:

Improvedeletion operation speedVSAvoiddata deletion accuracy

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The system performs preliminary identification of the resource type before deletion. When a resource is identified as having type 'CONFIRMED_BASED_OPERATION', the system proactively requests confirmation from the originator before proceeding with deletion. This preliminary check prevents accidental deletion of critical data while maintaining efficient automatic deletion for non-critical resources.

Inventive Principle:

Principle #10Preliminary action

2Reliability

If confirmation request mechanism is added, then reliability is improved, but device complexity increases

Engineering Contradiction:

Improvedata deletion accuracyVSAvoidoperation control mechanism

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The confirmation mechanism is applied selectively based on resource type rather than universally. The system checks the resource type attribute and only triggers confirmation requests for resources marked as 'CONFIRMED_BASED_OPERATION'. This localized application of the confirmation mechanism reduces overall system complexity compared to a universal confirmation approach, while still providing reliable protection for critical resources.

Inventive Principle:

Principle #3Local quality

3Adaptability or versatility

If resource type attribute is used to differentiate operations, then adaptability is improved, but difficulty of detecting and measuring increases

Engineering Contradiction:

Improvedeletion operation flexibilityVSAvoidresource characteristic identification

Core Design Contradiction:

Adaptability or versatilityVSDifficulty of detecting and measuring

Solution Approach 1:

The system uses resource type attributes as categorical identifiers (analogous to color coding) to differentiate between confirmed-based operations and other operations. Resources are tagged with specific type values ('CONFIRMED_BASED_OPERATION' vs. other types), making them easily identifiable and measurable by the system. This categorical approach simplifies detection compared to analyzing continuous or complex resource characteristics.

Inventive Principle:

Principle #32Color changes

Data Source

PatentUS11659619B2Method and apparatus for performing confirmed-based operation in machine to machine system

Publication Date: 2023.05.23 HYUNDAI MOTOR CO LTD

AI summary

An operation method is provided for deleting a resource in an M2M system. The operation method includes receiving a first deletion request message requesting deletion of a resource from a counterpart M2M apparatus and transmitting a first deletion response message for the first deletion request message to the counterpart M2M apparatus. A second deletion request message is received that requests deletion of the resource from the counterpart M2M apparatus and the resource is deleted.