IoT Service Expands Edge Device Address Space via ID Segmentation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The limited device address space in radio communication protocols, such as LoRaWAN, restricts the number of unique network addresses available for IoT edge devices, failing to meet the demand for managing a large number of client devices.
Innovation Solution
The implementation of an IoT service that generates unique internal IDs by combining client IDs with device IDs, expanding the address space while adhering to the radio communication protocol specifications, and dynamically assigning device IDs with non-roaming or roaming prefixes based on device capabilities.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If a limited number of bits are used for network addresses in radio communication protocol, then protocol compliance is maintained, but the number of available unique network addresses becomes insufficient
Solution Approach 1:
The patent segments the address identification into two parts: a network address (compliant with radio protocol bit limits) and a device identifier (additional unique identification). This segmentation allows the system to maintain protocol compliance while effectively expanding the addressable device capacity beyond protocol limitations.
Solution Approach 2:
The patent adds an additional dimension to address identification by introducing device identifiers alongside network addresses. Instead of relying solely on the limited network address bits, the system creates a two-dimensional identification space (network address × device identifier) that exponentially increases the number of uniquely addressable devices.
2Ease of operation
If device IDs are dynamically assigned with non-roaming or roaming prefixes, then device identification efficiency is improved, but the complexity of ID management increases
Solution Approach 1:
The system performs preliminary actions by pre-assigning device identifiers and determining roaming status before devices need to communicate. This allows the network server to have all necessary identification information ready in advance, enabling efficient device recognition and routing without complex real-time negotiations.
Solution Approach 2:
The network server acts as an intermediary that manages the complexity of dynamic ID assignment. It maintains the mapping between device identifiers, network addresses, and roaming status, shielding individual devices from the complexity of ID management while enabling efficient identification and routing.
Data Source
AI summary
An IoT service of a provider network may be used to increase the edge device address space while complying with a radio communication protocol. This may allow a service provider to manage a much larger number of client devices that use a particular radio communication protocol that specifies a limited address space (e.g., LoRaWAN). When the IoT service receives a join request via a private gateway of the client network, the service determines, based on the private gateway ID, the client ID of the client that owns the private gateway/client network. The service may generate a unique internal ID for the edge device by combining the client ID with an assigned device ID. The internal ID identifies the edge device as an activated device of the edge network.