Node Availability Prediction Service for IoT Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Internet protocols lack support for 'sleepy' nodes in M2M/IoT networks, where devices frequently enter sleep mode for energy efficiency, leading to node unavailability issues, and existing service layers do not have the capability to estimate node availability proactively.

Innovation Solution

A Node Availability Estimation (NAE) service is implemented within the service layer to collect and process real-time data from various sources, using historical availability data to build estimators and provide node availability information, enabling proactive decision-making and resource management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Use of energy by moving object

If nodes enter sleep mode for energy efficiency, then energy consumption is reduced, but node availability deteriorates

Engineering Contradiction:
Improveenergy consumptionVSAvoidnode availability
Core Design Contradiction:
Use of energy by moving objectVSReliability

Solution Approach 1:

The service layer proactively collects historical availability data from multiple sources (direct observations, network logs, application layer information) and builds prediction models in advance. This preliminary action enables the system to predict when sleepy nodes will become available before actual connection attempts are made, allowing applications to schedule operations during predicted availability windows and avoid wasted connection attempts.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback mechanisms where actual node availability outcomes are continuously monitored and used to refine prediction models. The service layer aggregates feedback from various sources including successful/unsuccessful connection attempts, node status changes, and application layer observations. This feedback loop continuously improves prediction accuracy, enabling better energy-availability tradeoff decisions over time.

Inventive Principle:
Principle #23Feedback

2Measurement precision

If service layer collects and processes historical data to predict availability, then prediction accuracy is improved, but system complexity increases

Engineering Contradiction:
Improveprediction accuracyVSAvoidservice layer complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The availability prediction service is segmented into distinct functional components: data collection module, data processing module, model building module, and prediction provision module. Each component has a specific responsibility and can be independently implemented, configured, and maintained. This segmentation reduces overall system complexity by creating modular, manageable units with well-defined interfaces.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The service layer acts as an intermediary between the application layer and the sleepy nodes. Instead of applications directly managing complex availability prediction logic, the service layer provides a simplified API that applications can use to query predicted availability. This intermediary absorbs the complexity of data collection, processing, and model management, presenting a simple interface to applications while handling sophisticated prediction mechanisms in the background.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentEP3544238B1Network node availability prediction based on past history data
Publication Date: 2021.04.14 CONVIDA WIRELESS LLC
  • EP3544238B1 patent drawingFigure 1
  • EP3544238B1 patent drawingFigure 2
  • EP3544238B1 patent drawingFigure 3

AI summary

A node availability estimation service can be used at a service layer of an M2M/IoT network. Value-added services can leverage this node availability information to improve the operation intelligence, quality of service, communication overhead as well as energy efficiency for M2M/IoT systems. A Real-time Data Collection (DC) component can collect real-time data from input sources at service layer (e.g., other existing CSFs). A Data Processing for Estimating Node Availability component (DP) can execute data processing for estimating node availability based on the data collected by DC. A Node Availability Service Provisioning component (SP) can store the estimated node availability results from DP and expose them to service clients in terms of "node availability estimation services".