IoT API Authentication via Network TCP Flow Logging

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Internet of Things (IoT) space is fragmented, leading to 'information silos' where data from different devices is not accessible, and there is a challenge in securing application programming interface (API) calls due to the lack of standardized security measures.

Innovation Solution

An IoT application framework that logs Transmission Control Protocol (TCP) flow data for registered devices, compares packet information with logged data to authenticate API calls, and sends responses to accept or reject calls based on matches, providing reliable security measures for IoT API calls.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If standardized security measures are implemented for API calls, then security reliability is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity reliabilityVSAvoiddevice complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary authentication mechanism that mediates between IoT devices and the cloud platform. The system captures TCP flow data, extracts packet information, and validates API calls through an intermediate authentication process rather than implementing complex security measures directly in each device. This intermediary layer handles the security complexity centrally while keeping individual devices simpler.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent creates a copy of the TCP flow data and packet information for validation purposes. Instead of modifying the actual API call flow or implementing complex security protocols in devices, the system captures and validates copies of the communication data. This allows security verification without adding complexity to the original device operations.

Inventive Principle:
Principle #26Copying

2Reliability

If TCP flow data logging and validation is implemented, then API call security is improved, but processing time increases

Engineering Contradiction:
ImproveAPI call securityVSAvoidprocessing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary actions by capturing and logging TCP flow data as it naturally occurs during device communication. The system prepares the validation data in advance by monitoring the TCP stream, so when API calls need validation, the necessary packet information is already captured and ready for comparison. This preliminary data capture reduces the time needed for actual validation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces complex mechanical security verification systems with a lighter-weight validation approach. Instead of implementing heavy cryptographic protocols or multi-step authentication mechanisms, the system substitutes a simpler validation method that compares packet information against captured TCP flow data. This substitution reduces processing time while maintaining security effectiveness.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Measurement precision

If packet information comparison is performed for each API call, then authentication accuracy is improved, but computational load increases

Engineering Contradiction:
Improveauthentication accuracyVSAvoidcomputational load
Core Design Contradiction:
Measurement precisionVSPower

Solution Approach 1:

The patent applies local quality by performing packet information comparison only at specific critical points in the communication flow, rather than continuously analyzing all data. The system validates API calls by comparing packet information against captured TCP flow data at authentication decision points, rather than processing every single packet. This localized validation approach maintains authentication accuracy while reducing overall computational load.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10970380B2Internet-of-Things partner integration
Publication Date: 2021.04.06 VERIZON PATENT & LICENSING INC
  • US10970380B2 patent drawing
  • US10970380B2 patent drawing
  • US10970380B2 patent drawing

AI summary

A network device logs transmission control protocol (TCP) flow data for connections between registered devices that are registered for use of secure Internet of Things (IoT) application programming interfaces (APIs). The logging generates logged flow data. The network device receives, from a first registered device, a call validation request for an IoT API call directed to the first registered device from a second registered device. The call validation request includes packet information of the IoT API call. The network device compares the packet information with the logged TCP flow data. When the comparing indicates a match of the packet information and the logged TCP flow data, the network device sends a response to the first registered device to accept the IoT API call. Otherwise, the network device sends a response to the first registered device to reject the IoT API call.