Service Element Segmentation for Multi-Element IoT Services
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The conventional oneM2M service layer lacks the functionality to support services composed of multiple service elements, failing to manage and maintain information about such services, which hinders their discovery and utilization.
Innovation Solution
The introduction of service elements and service element hosts allows the service layer to manage and maintain records of services composed of multiple elements, enabling their discovery and use by clients, with mechanisms for reporting, updating, and deleting these services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the oneM2M service layer follows conventional architecture, then the service layer structure remains simple, but it cannot support services composed of multiple service elements
Solution Approach 1:
The patent segments a service into multiple service elements (SE), where each SE represents a functional component provided by a service element host (SEH). This segmentation allows the service layer to manage complex services by breaking them down into manageable, independently addressable units while maintaining the overall service functionality.
Solution Approach 2:
The patent introduces a new dimensional structure to the service layer by adding service element-specific attributes (such as SE ID, SE type, SE parameters) to the existing resource structure. This dimensional extension enables the service layer to handle multi-element services without fundamentally altering the core oneM2M architecture.
2Loss of information
If the service layer manages multiple service elements, then service discovery capability is enhanced, but information management complexity increases
Solution Approach 1:
The patent creates a universal service element structure that can represent different types of service elements through a common framework. The service element resource template includes generic attributes (ID, type, parameters) that can accommodate various service types, enabling unified management while preserving service-specific information.
Solution Approach 2:
The patent uses resource templates and instances to manage service element information. Instead of creating entirely new data structures for each service element, the system uses copies of the service element resource template, instantiated with specific values for each SE, thereby simplifying information management through template-based replication.
3Measurement precision
If service elements are introduced with unique identification, then service element distinguishability is improved, but resource structure complexity increases
Solution Approach 1:
The patent implements a nested resource structure where service elements are nested within services, and service elements can further contain parameters and attributes. This hierarchical nesting provides precise identification and differentiation of service elements while organizing the resource structure in a manageable, layered fashion.
Data Source
Figure 1
Figure 2~3
Figure 4
AI summary
A service, such as an internet of things service, may have multiple service elements. Each service element may be provided by multiple devices or virtual devices (service element hosts). A service/service element can be managed as a resource at the service layer. Service with multiple service elements is supported.