M2M Service Architecture with Segmented Control and Data Paths
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The conventional ETSI M2M architecture lacks direct communication paths between service capability layers, leading to potential delays and inefficiencies in control and data transmission, especially in scenarios involving multiple verticals and mobility, and does not separate control and data paths effectively.
Innovation Solution
Introduce new reference points (mIm, dId, dIa, and aIa) and a scalable M2M architecture (SMA) that splits M2M servers into control and data servers, allowing separate control and data paths with different transport protocols, enabling direct communication between service capability layers and optimizing interactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If the conventional ETSI M2M architecture is used with a single unified server structure, then the architecture is simpler to implement, but control and data transmission experience delays and inefficiencies
Solution Approach 1:
The patent segments the unified M2M server into separate control servers and data servers. Control servers handle signaling, registration, and control functions, while data servers handle actual data storage and transmission. This segmentation eliminates the bottleneck where control and data paths were mixed in the conventional architecture, thereby improving transmission efficiency without requiring complete architectural redesign.
Solution Approach 2:
The patent introduces a new dimensional separation by creating distinct control plane and user plane paths. The control plane handles signaling and management, while the user plane handles data transmission. This dimensional separation allows independent optimization of control and data flows, resolving the efficiency problem without proportionally increasing complexity.
2Loss of time
If direct communication paths between service capability layers are added, then communication efficiency improves, but the number of reference points and system complexity increases
Solution Approach 1:
The patent establishes direct reference points (mIc, dIc, aIc for control plane; mIu, dIu, aIu for user plane) between service capability layers in advance, allowing devices to communicate directly without routing through intermediate nodes. This preliminary establishment of communication paths eliminates unnecessary routing delays while the reference points are standardized and documented, preventing uncontrolled complexity growth.
3Reliability
If control and data paths are separated into different servers, then system reliability and scalability improve, but the difficulty of system management increases
Solution Approach 1:
By segmenting servers into control and data types with clearly defined responsibilities, the patent improves reliability through functional isolation - failures in data processing don't affect control functions. The standardized reference points and interfaces between segmented components provide clear management boundaries, actually simplifying rather than complicating system management.
Solution Approach 2:
The patent introduces standardized reference points and interface definitions as intermediaries between control and data servers. These standardized interfaces act as mediators that simplify management by providing consistent interaction patterns, reducing the complexity burden that would otherwise result from direct point-to-point management of separated components.
4Productivity
If multiple reference points are introduced for direct communication, then communication efficiency improves, but the architecture becomes more complex
Solution Approach 1:
The patent creates universal reference point patterns that can be applied across different service capability layers. The same reference point naming convention and interaction model (mIc/dIc/aIc for control, mIu/dIu/aIu for user plane) are used throughout the architecture, allowing efficient direct communication while reducing complexity through standardization and reusability rather than ad-hoc point-to-point connections.
Data Source
Figure 1
Figure 2A
Figure 2B
AI summary
A method implemented by a first service entity, comprising: receiving a request for service from a second service entity, the request message including requested service capability information; determining to grant the service based on the requested service capability information; and creating an entry of a resource for the granted service based on the requested service capability information.