Distributed M2M/IoT Service Layer Registration for Gateway Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional M2M/IoT systems face service interruptions and lack of continuity when a gateway becomes non-functional, leading to disrupted service and loss of context for registered devices and backend applications, as they require new registrations and re-establishment of service layer contexts, which is burdensome for constrained devices and inefficient.
Innovation Solution
An enhanced registration procedure allows for one active and multiple inactive service layer registrations, enabling the active registrar entity to synchronize context with inactive entities, and triggering an inactive entity to become active when the primary entity fails, ensuring continuous service without significant overhead.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional M2M/IoT systems use a single active gateway for service registration, then service management is simple, but service continuity is lost when the gateway becomes non-functional
Solution Approach 1:
The patent applies preliminary action by establishing multiple inactive service layer registrations in advance at different gateway entities before any failure occurs. When the active gateway becomes non-functional, one of the pre-established inactive registrations can immediately take over, ensuring service continuity without requiring devices to perform complex service discovery or re-registration procedures at the time of failure.
2Reliability
If multiple inactive service layer registrations are established for constrained devices, then service continuity is improved, but overhead and complexity increase
Solution Approach 1:
The service layer acts as an intermediary that manages multiple gateway registrations on behalf of constrained devices. Instead of requiring devices to directly manage multiple connections and perform complex failover logic, the service layer abstraction handles the complexity of maintaining multiple inactive registrations and triggering active transitions, thereby protecting constrained devices from overhead while ensuring service availability.
3Loss of information
If single gateway registration is used, then context synchronization is simple, but context loss occurs when gateway fails
Solution Approach 1:
The patent merges the service layer context management across multiple gateway entities by establishing synchronized inactive registrations at each gateway. This ensures that service layer context information is maintained and synchronized across multiple gateways, so when one gateway fails, the context is already available at the standby gateways, preventing context loss without requiring complex real-time synchronization protocols.
4Reliability
If re-registration is required when gateway fails, then system simplicity is maintained, but service interruption and time loss occur
Solution Approach 1:
The system performs preliminary action by pre-establishing inactive service layer registrations at multiple gateway entities before any failure occurs. These pre-configured registrations include all necessary context information and are ready to immediately transition to active status, eliminating the time-consuming re-registration process that would otherwise be required when a gateway fails.
Data Source
AI summary
A registration procedure may allow one active and multiple inactive SL registrations to be created at different service layer entities for an application entity without adding significant overhead and burden to an application entity.