SCEF Reachability Coordination for IoT Data Delivery

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

IoT devices in low-power wide-area networks often enter power-saving modes or extended discontinuous reception periods, making them unreachable, leading to wasted computing and networking resources as application servers attempt to transmit data, resulting in potential packet data network session timeouts and data delivery issues.

Innovation Solution

A service capability exposure function (SCEF) facilitates data transmission by requesting and providing reachability data for IoT devices, allowing the application server to determine when the device is reachable, thereby conserving resources and preventing session timeouts by coordinating data transmission during reachable times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If IoT devices enter power-saving mode or extended discontinuous reception periods, then battery life is extended, but device reachability deteriorates

Engineering Contradiction:
Improvebattery lifeVSAvoiddevice reachability
Core Design Contradiction:
Duration of action of moving objectVSReliability

Solution Approach 1:

The system performs preliminary actions by establishing a subscription with the SCEF before the IoT device becomes unreachable. The application server subscribes to reachability notifications in advance, so when the device enters power-saving mode, the server is already prepared to receive and act on reachability updates without attempting futile data transmissions

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The SCEF provides feedback to the application server about the IoT device's reachability status. When the device becomes reachable again after being in power-saving mode, the SCEF sends a notification to the application server, enabling the server to know when data transmission is appropriate without continuously polling or attempting transmissions during unreachable periods

Inventive Principle:
Principle #23Feedback

2Reliability

If application servers continuously attempt data transmission to unreachable IoT devices, then data delivery is maintained, but computing and networking resources are wasted

Engineering Contradiction:
Improvedata deliveryVSAvoidcomputing and networking resources
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The application server performs a preliminary subscription action with the SCEF before needing to transmit data. This advance preparation establishes a mechanism where the server will be notified when the IoT device becomes reachable, eliminating the need for continuous transmission attempts and reducing wasted computing and networking resources

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The SCEF provides feedback notifications to the application server when the IoT device transitions from unreachable to reachable state. This feedback mechanism allows the application server to optimize its data transmission strategy by only attempting transmissions when the device is known to be reachable, thereby conserving computing and networking resources while maintaining reliable data delivery

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11588788B2Systems and methods for facilitating data transmission to internet of things devices
Publication Date: 2023.02.21 VERIZON PATENT & LICENSING INC
  • US11588788B2 patent drawing
  • US11588788B2 patent drawing
  • US11588788B2 patent drawing

AI summary

A device may receive provisioning data identifying an application server and a user equipment. The device may provide a request for reachability data associated with the user equipment and may receive the reachability data. The device may cause a trigger for a packet and data identifying the application server to be provided to the user equipment. The device may receive, from the user equipment, the packet that includes a network address and a port identifier of a port of the user equipment. The device may provide, to a firewall associated with the application server, an identifier, the network address, and the port identifier. The device may cause, via the firewall, the reachability data, the network address, and the port identifier to be provided to the application server to enable the application server to provide data to the user equipment.