Message Retargeting in M2M Service Layer Communications
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M service layer architectures restrict communication between two service layer entities unless they have a registration relationship, limiting information exchange between entities without established registration links.
Innovation Solution
Implementing retargeting tables and retargeting chain tables at service layer entities to facilitate message delivery between entities without registration relationships, allowing entities to look up and redirect messages to the intended destination through enhanced registration, de-registration, and update procedures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If service layer entities require registration relationships to communicate, then communication reliability is ensured, but communication flexibility and interoperability are limited
Solution Approach 1:
The patent applies preliminary action by pre-establishing retargeting tables and retargeting chain tables that contain forwarding information before communication is needed. When an entity needs to communicate with another entity without a direct registration relationship, the message includes retargeting information that enables automatic forwarding through intermediate entities. This allows flexible communication without requiring pre-established registration relationships, while maintaining reliable delivery through the predetermined retargeting structures.
2Adaptability or versatility
If retargeting tables and chain tables are implemented, then communication between entities without registration relationships is enabled, but system complexity increases
Solution Approach 1:
The patent uses intermediary structures (retargeting tables and retargeting chain tables) that act as mediators between entities without direct registration relationships. These tables store forwarding information and enable automatic message routing through intermediate entities. The complexity is managed by centralizing the retargeting logic in these tables rather than requiring complex peer-to-peer relationship management between all entities, thus enabling flexible communication while controlling system complexity through structured intermediaries.
3Loss of information
If message retargeting is implemented, then information exchange between entities is enhanced, but message processing overhead increases
Solution Approach 1:
The patent applies preliminary action by pre-populating retargeting tables and retargeting chain tables with forwarding information before messages need to be routed. When a message is sent, the retargeting information is already available in the tables, allowing for quick lookup and forwarding decisions without requiring complex real-time route discovery. This reduces message processing overhead and time while enabling comprehensive information exchange between entities that would otherwise lack direct communication paths.
Data Source
AI summary
Two methods are described to enable the communication between two service layer entities that do not have registration relations. In the first method, service layer entities employ a retargeting table that stores the service layer entity to retarget the message in order to deliver the message to the destination. In a second method, an infrastructure node in a service provider employs a retargeting chain table that stores a chain of entities that can retarget the message to the destination.