IoT Service Layer QoS Management Across Heterogeneous Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current IoT SL technologies lack the capability to manage end-to-end quality of service (QoS) requirements such as schedule, latency, jitter, throughput, error rate, and security across multiple underlying network technologies and operators, leading to mismatches in reachability schedules and suboptimal network resource utilization.
Innovation Solution
The implementation of a system that enables end-to-end QoS management through service layer sessions, allowing applications to specify QoS preferences and interact with underlying networks to configure and influence network settings, while coordinating QoS across multiple hops and operators, using Service Layer Connection Manager (SLCM), Application Connection Manager (ACM), and Underlying Network Connection Manager (UNCM) functions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If M2M/IoT devices integrate into deployments with multiple network technologies and operators, then connectivity and service coverage are improved, but QoS management complexity increases due to lack of end-to-end coordination
Solution Approach 1:
The patent introduces a Service Layer (SL) as an intermediary between applications and underlying networks. The SL session management functionality coordinates QoS parameters across multiple network technologies and operators, acting as a mediator that translates application QoS requirements into network-specific configurations without requiring applications to directly manage complex multi-network QoS coordination.
Solution Approach 2:
The patent segments QoS management into distinct functional components: application layer QoS specification, Service Layer session management, and network layer QoS configuration. This segmentation allows each layer to handle QoS aspects independently, reducing overall complexity while maintaining end-to-end QoS coordination across heterogeneous networks.
2Ease of operation
If applications directly manage communication sessions, then session control flexibility is improved, but application overhead and complexity increase
Solution Approach 1:
The Service Layer acts as an intermediary that handles session management tasks for applications. The SL session management functionality provides applications with session control capabilities while abstracting away the complexity of direct session management, including configuration, establishment, and teardown of communication sessions across multiple networks.
Solution Approach 2:
The Service Layer provides self-service session management capabilities, automatically handling session configuration, establishment, and teardown based on application requirements. This allows applications to obtain session control flexibility without directly managing the complex overhead of multi-network session coordination.
3Reliability
If end-to-end QoS management is implemented across multiple hops, then communication reliability is improved, but coordination overhead and system complexity increase
Solution Approach 1:
The Service Layer session management functionality serves as a central intermediary that coordinates QoS parameters across all hops in the communication path. It maintains end-to-end QoS requirements and translates them into hop-by-hop QoS configurations, ensuring communication reliability while centralizing coordination logic to reduce distributed system complexity.
Solution Approach 2:
The system performs preliminary QoS configuration and session establishment through the Service Layer before actual data communication begins. This preliminary action includes negotiating QoS parameters, configuring network resources, and establishing session contexts in advance, which simplifies real-time communication while maintaining end-to-end QoS guarantees across multiple hops.
Data Source
AI summary
Methods, system, and apparatuses may support end-to-end (E2E) quality of service (QoS) through the use of service layer (SL) sessions. For example, an application can communicate with a targeted device based on application specified schedule, latency, jitter, error rate, throughput, level of security, and cost requirements.