M2M Data Querying via Infrastructure Node CSE

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current M2M data invoking solutions face inefficiencies due to increased byte overheads and time requirements in signaling exchanges between application nodes and middle nodes, particularly when service nodes are offline, leading to reduced data querying and invoking efficiency.

Innovation Solution

A querying and invoking method that includes a device configured to send a data invoking request to an infrastructure node with an identifier and data demand, allowing for efficient data retrieval by querying prestored data and forwarding requests when necessary, thereby reducing the need for multiple command requests and improving efficiency.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data invoking is performed through infrastructure node CSE by checking online state, then data can be invoked when service node is online, but data invoking fails and requires multiple command requests when service node is offline, increasing byte overheads and time consumption

Engineering Contradiction:
Improvedata invoking reliabilityVSAvoiddata querying and invoking time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The infrastructure node CSE performs preliminary actions by checking whether the service node CSE is online before data invoking. When offline, it proactively retrieves data from the DMR and stores it locally, so that when data requests arrive, the data can be immediately provided without waiting for service node responses, thus reducing time loss and improving reliability

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The infrastructure node CSE acts as an intermediary between the data requestor and the service node CSE. It maintains a local copy of data from the DMR and can directly respond to data requests without needing to forward requests to the offline service node, thereby reducing byte overheads and invocation time while improving reliability

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If multiple command requests are sent between application node and middle node for data invoking, then data can be retrieved, but byte overheads increase and data querying efficiency decreases

Engineering Contradiction:
Improvedata invoking reliabilityVSAvoiddata querying efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent merges multiple command requests into a single data retrieval operation. The infrastructure node CSE retrieves data once from the DMR and stores it locally, then serves multiple data requests from this cached copy, eliminating the need for repeated requests to the service node and thereby improving data querying efficiency while maintaining reliability

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The infrastructure node CSE performs preliminary data retrieval from the DMR and stores it in local memory before data requests arrive. This preliminary action eliminates the need for multiple command requests during data invoking, reducing byte overheads and improving data querying efficiency while ensuring reliable data delivery

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3054625B1M2m data query and scheduling method, query and scheduling device and system
Publication Date: 2021.09.01 HUAWEI TECH CO LTD
  • EP3054625B1 patent drawingFigure 1~2
  • EP3054625B1 patent drawingFigure 3
  • EP3054625B1 patent drawingFigure 4

AI summary

The present invention provides M2M data querying and invoking methods, querying and invoking devices, and a system. The querying method includes: sending a data invoking request to an infrastructure node common services entity infrastructure node CSE, where the data invoking request includes an identifier AE/CSE ID of an application entity/a common services entity that provides to-be-invoked data and a data demand of the to-be-invoked data, where the data demand includes a data type demand, a time demand, or a combination thereof; and receiving data meeting the data demand and returned by the infrastructure node CSE. According to the present invention, a case of excessive command requests between an application node and a middle node is avoided, thereby reducing byte overheads of signaling exchange between the application node and the middle node, reducing a time taken for data querying and a time taken for data invoking, and improving data querying efficiency and data invoking efficiency.