Service Layer Message Routing for IoT Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing oneM2M Service Layer message routing is sub-optimal due to its hop-by-hop approach based on registration relationships, which does not consider Service Layer specific information such as node sleeping schedules and service capabilities, leading to inefficient message deliveries across multiple hops.
Innovation Solution
The proposed Service Layer Message Routing Service maintains service layer neighbors, builds routing tables based on optimal performance metrics, and routes messages to achieve the best required performance, including shortest distance, lowest delay, and highest reliability, by associating messages with routing metrics and using components like Maintain Service Layer Neighbor, Build Service Layer Routing Table, and Route Service Layer Message.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If hop-by-hop routing based on registration relationships is used, then message routing is simple to implement, but message delivery efficiency deteriorates due to sub-optimal paths
Solution Approach 1:
The patent introduces a Service Layer Message Routing Service as an intermediary component between message sources and destinations. This routing service maintains service layer neighbors, builds routing tables based on optimal performance metrics, and intelligently determines message paths, thereby improving delivery efficiency without requiring complexity at individual network nodes
Solution Approach 2:
The routing service performs preliminary actions by pre-building and maintaining routing tables that contain optimal message paths based on service layer metrics. These routing tables are constructed in advance using information about service layer neighbors, node sleeping schedules, and service capabilities, enabling efficient message routing without real-time computation
2Reliability
If traditional routing without service layer information is used, then routing decisions are simple, but message delivery performance deteriorates due to ignoring node sleeping schedules and service capabilities
Solution Approach 1:
The patent changes the routing parameters from simple network layer addresses to service layer specific parameters including node sleeping schedules, service capabilities, and performance metrics. The routing service uses these parameters to dynamically determine optimal message paths, ensuring messages are routed to active nodes with appropriate service capabilities, thereby improving delivery reliability
Solution Approach 2:
The routing service implements feedback mechanisms by continuously monitoring service layer information such as node availability, sleeping schedules, and service capabilities. This feedback is used to update routing tables and adjust message paths in real-time, ensuring reliable delivery even when network conditions change
3Speed
If multi-hop message forwarding is implemented, then message can reach distant targets, but message delivery time increases due to multiple intermediate hops
Solution Approach 1:
The routing service performs preliminary path optimization by pre-calculating and storing optimal message paths in routing tables. These paths are determined based on service layer metrics including expected delivery time, node availability, and hop counts. When messages need to be forwarded, the routing service simply follows these pre-optimized paths, significantly reducing delivery time compared to ad-hoc routing decisions at each hop
Data Source
AI summary
A Service Layer Message Routing Service at the Service Layer entity is capable of routing service layer messages to reach the target with optimal performance, e.g. shortest service layer distance, shortest network layer distance, least end-to-end delay, highest reliability, etc. The service layer Message Routing Service may have the following example functions: Maintain Service Layer Neighbor can take charge of finding and updating the service layer Neighbors of the service layer entity due to registration or policy configuration; Build Service Layer Routing Table can take charge of building the Service Layer routing table, which routes a service layer message from a service layer entity to the other service layer entities with the optimal performance that is desired by the message originator; and Route Service Layer Message can take charge of routing/forwarding a service layer message by the service layer entity towards other service layer entities.