Edge Network Server Segmentation for LoRaWAN Latency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current LoRa-based IoT networks face challenges with latency and security due to centralized network architecture, which can lead to delays in critical message transmission and vulnerability to attacks, especially when handling a large number of end devices.

Innovation Solution

Implementing an edge network server collocated with gateways or closer to them, allowing for the selection of optimal gateways based on application type and policy, enabling direct data paths to application servers without traversing the central network server, and incorporating fog computing for localized data processing and validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a centralized network server architecture is used, then network management and control are simplified, but transmission latency increases and security vulnerabilities arise

Engineering Contradiction:
Improvenetwork management complexityVSAvoidtransmission latency
Core Design Contradiction:
Device complexityVSLoss of time

Solution Approach 1:

The patent segments the centralized network server into distributed edge network servers deployed at multiple gateways. Each edge server handles local data processing and validation, reducing the distance data must travel and eliminating the single point of latency associated with centralized architecture. This segmentation maintains management simplicity through coordinated control while dramatically reducing transmission latency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a spatial dimension to network architecture by deploying edge servers at distributed gateway locations rather than consolidating all processing at a central location. This dimensional change from centralized to distributed architecture reduces the physical distance data must traverse, thereby reducing latency while maintaining architectural simplicity through standardized edge server implementations.

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

2Device complexity

If a centralized network server architecture is used, then network control is centralized, but security vulnerabilities and attack risks increase

Engineering Contradiction:
Improvenetwork control structureVSAvoidsecurity vulnerability
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the centralized control function into distributed edge network servers at multiple gateways. This segmentation eliminates the single point of failure and security vulnerability associated with centralized architecture. Each edge server independently validates messages and processes data locally, reducing the attack surface and improving overall network security while maintaining coordinated control through standardized protocols.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces edge network servers as intermediaries between end devices and the central network server. These intermediaries perform local validation and filtering of messages, preventing potentially malicious data from reaching the central server and reducing the security burden on centralized control. This intermediary layer maintains control structure simplicity while significantly improving security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Device complexity

If all data is routed through the central network server, then centralized processing is simplified, but network capacity becomes a bottleneck

Engineering Contradiction:
Improveprocessing architectureVSAvoidnetwork capacity
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The patent segments the centralized processing function into distributed edge network servers at multiple gateways. Each edge server independently processes and validates data locally, eliminating the bottleneck effect of centralized processing. This segmentation maintains architectural simplicity through standardized edge server implementations while dramatically increasing overall network capacity through parallel distributed processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent enables edge network servers to autonomously validate messages, filter data, and process information locally without requiring constant central server intervention. This self-service capability at the edge reduces the processing burden on the central server, maintaining simplified centralized control architecture while significantly increasing network capacity through distributed autonomous processing.

Inventive Principle:
Principle #25Self-service

4Reliability

If centralized validation is performed, then security control is centralized, but message transmission latency increases

Engineering Contradiction:
Improvevalidation securityVSAvoidmessage transmission time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the centralized validation function into distributed validation capabilities at edge network servers. Each edge server performs local validation of messages and data before they reach the central server, reducing the distance validation must traverse and eliminating the sequential bottleneck of centralized validation. This segmentation maintains security through coordinated validation rules while dramatically reducing message transmission time.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP3542557B1Application based intelligent edge computing in a low power wide area network environment
Publication Date: 2021.02.17 CISCO TECHNOLOGY INC
  • EP3542557B1 patent drawingFigure 1
  • EP3542557B1 patent drawingFigure 2
  • EP3542557B1 patent drawingFigure 3

AI summary

Embodiments include technologies for receiving two or more requests to join a network from an end device via two or more gateways, respectively, and selecting one of the two or more gateways for the end device. Embodiments further include sending, to the selected gateway, a response to a request to join the network received via the selected gateway, where the response includes an indication to the selected gateway to forward the request to join the network to an edge network server associated with the selected gateway. In more specific embodiments, an application is identified based on information included in the request to join the network, and a determination is made regarding whether to allocate an edge network server to the end device based, at least in part, on a type of the application. Specific embodiments can include the gateway being selected based, at least in part, on a policy.