Service Layer Interface Preference Binding for M2M Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Machine-to-machine (M2M) networks face challenges in managing multiple interfaces and providing consistent communication across diverse devices and applications due to the lack of explicit bindings between underlying networks, network interfaces, and service layers, leading to inconsistent behavior and connectivity issues.
Innovation Solution
A common service layer is introduced that provides interface preferences and explicit bindings between underlying networks and network interfaces, allowing devices to access and configure these preferences dynamically, enabling consistent behavior across devices and applications.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple network interfaces are used to support diverse devices and applications, then adaptability and coverage are improved, but interface management complexity and connectivity reliability deteriorate due to lack of explicit bindings
Solution Approach 1:
The service layer acts as an intermediary between the application layer and network interfaces, introducing interface preference objects that mediate the binding between applications and specific network interfaces. This mediator resolves the contradiction by providing structured preference information that guides reliable interface selection while maintaining support for multiple diverse interfaces.
Solution Approach 2:
The patent introduces interface preference parameters (such as interface type, priority, and binding rules) that can be dynamically configured and updated. By changing these parameters, the system can adapt to different devices and applications while maintaining reliable connectivity through structured preference management.
2Ease of operation
If interface preferences are dynamically configured, then ease of operation and adaptability are improved, but device complexity increases due to additional configuration management
Solution Approach 1:
The service layer provides universal interface preference management that can be applied across multiple devices and applications. The interface preference objects serve multiple functions: storing preferences, guiding interface selection, and enabling dynamic reconfiguration, thereby reducing overall system complexity through a unified management mechanism.
Solution Approach 2:
The system enables self-service configuration where interface preferences can be automatically updated and managed without requiring complex manual intervention. The service layer automatically processes preference information and applies it to interface selection, reducing operational complexity while maintaining dynamic configurability.
3Reliability
If explicit bindings between networks and interfaces are established, then connectivity reliability is improved, but device complexity increases due to additional binding management structures
Solution Approach 1:
The service layer with interface preference objects serves as an intermediary that manages explicit bindings between networks and interfaces. This mediator structure organizes binding information in a standardized format, improving connectivity reliability while containing complexity within the service layer rather than propagating it throughout the entire system.
4Adaptability or versatility
If service layer resources are used to store and access preference information, then adaptability and ease of operation are improved, but information access complexity increases
Solution Approach 1:
The service layer resources provide universal access to interface preference information for multiple applications and devices. By centralizing preference storage and access in the service layer, the system achieves high adaptability while managing information access complexity through a unified interface that can be reused across different contexts.
Data Source
AI summary
A set of point-of-contact information including a service level identifier, an address, a list of interfaces, and a set of interface selection preferences for each of several entities may be used to facilitate communications among the entities by selecting a preferred interface in accordance with the set. Interface preferences may also be derived from a set of policies. The preferred interface may be resolved in accordance with the preferences of multiple entities. Messages may include an interface type parameter to be used for forwarding of the message, and message forwarding may be resolved in accordance with the parameter and the messages.


