M2M Capability Model Segmentation for Query Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing M2M systems experience long query latency and wastage of hardware resources due to the need for massive data queries when retrieving capability information from the M2M service platform.

Innovation Solution

A capability model is introduced that categorizes capabilities into communication, control, and measurement types, with each type divided into subentries, allowing for efficient querying without massive data queries by using a filled capability model and an overall capability model updated in a type division manner.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If capability information of all M2M devices is stored in a centralized database, then complete capability data is available for querying, but query latency increases and hardware resources are wasted due to massive data queries

Engineering Contradiction:
Improvecompleteness of capability dataVSAvoidquery latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the centralized capability database into distributed capability information storage units located at edge nodes or local servers. Each segment stores capability data for a specific region or device group, allowing queries to be directed to relevant segments rather than scanning the entire database. This segmentation reduces query latency while maintaining data completeness through distributed replication.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a hierarchical dimension to the data storage architecture, organizing capability information across multiple levels (central cloud platform, edge nodes, local servers). This multi-dimensional structure allows queries to be resolved at the closest appropriate level, reducing the need for massive data queries across the entire system while maintaining comprehensive capability data availability.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

2Reliability

If capability information of all M2M devices is stored in a centralized database, then complete capability data is available for querying, but hardware resources of the M2M service platform are wasted

Engineering Contradiction:
Improvecompleteness of capability dataVSAvoidhardware resource wastage
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent divides the centralized database into distributed storage units across multiple edge nodes and local servers. Each node stores a subset of capability information locally, eliminating the need for a single massive centralized database. This distribution reduces hardware resource consumption at any single location while collectively maintaining complete capability data across the distributed system.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables edge nodes and local servers to independently store and serve capability information for their respective regions or device groups. This self-service capability allows local queries to be resolved without accessing centralized resources, reducing overall hardware resource wastage while maintaining data availability through distributed replication and local caching mechanisms.

Inventive Principle:
Principle #25Self-service

3Reliability

If capability information is queried sequentially from a database, then all capability data can be accessed, but query efficiency decreases due to massive data queries

Engineering Contradiction:
Improvecompleteness of capability data accessVSAvoidquery efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the monolithic database into distributed capability information storage units organized by region, device group, or capability type. This segmentation enables targeted queries to specific segments rather than sequential scanning of entire database, dramatically improving query efficiency while maintaining access to complete capability data through distributed architecture.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements preliminary actions by pre-processing and organizing capability information into structured segments at edge nodes and local servers during device registration and capability updates. This preliminary organization enables efficient query resolution through local indexing and filtering, reducing the need for massive data queries while ensuring complete capability data can be accessed when needed.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3247088B1M2m data processing methods and devices
Publication Date: 2020.12.30 HUAWEI TECH CO LTD
  • EP3247088B1 patent drawingFigure 1~2
  • EP3247088B1 patent drawingFigure 3A
  • EP3247088B1 patent drawingFigure 3B

AI summary

The present invention provides an M2M data processing method, device, and system, and relates to the field of communications. The method includes: receiving a registration request sent by an M2M device; obtaining a filled capability model according to a capability model and capability information of the M2M device after authentication on the registration request succeeds, where the capability model includes three types of capabilities: a communication capability, a control capability, and a measurement capability, each capability is divided into multiple subentries, and the filled capability model describes at least one subentry corresponding to three types of capabilities of the M2M device; updating an overall capability model according to the filled capability model, where capability information of all registered M2M devices managed by an M2M service platform is recorded in the overall capability model in a type division manner of the capability model. The present invention can resolve a problem of a relatively long query latency and waste of hardware resources of the M2M service platform. Therefore, the query latency and the waste of hardware resources of the M2M service platform are reduced. The present invention is applicable to M2M system communications.