M2M Device Triggering Port Allocation and Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing M2M architectures face challenges in device triggering, including the lack of standardized port number for listening, insecure transmission of device identities, inefficient long polling, and undefined trigger payload formats, which affect communication efficiency and security.
Innovation Solution
Implementing a method where devices or gateways indicate their trigger port numbers to the M2M server during registration, using triggers for secure bootstrapping with temporary identifiers, and defining a trigger payload format to enhance communication efficiency by minimizing data plane connection time.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If devices use non-standardized port numbers for trigger listening, then devices can avoid conflicts with existing services, but it becomes difficult to standardize device triggering and manage port allocation
Solution Approach 1:
The patent changes the port number parameter from a fixed, pre-assigned value to a dynamically allocated value. The M2M server assigns port numbers to devices on-demand, transforming the static port allocation into a dynamic parameter that adapts to system needs while maintaining standardization through centralized control
Solution Approach 2:
The M2M server acts as an intermediary between devices and the trigger mechanism. It manages the port number allocation, receives trigger requests, and routes them to the appropriate devices, thereby centralizing port management complexity in the server rather than distributing it across all devices
2Productivity
If device identities are transmitted in clear text during bootstrapping, then the bootstrapping process is simple and fast, but security is compromised as device identities can be intercepted
Solution Approach 1:
The patent applies preliminary action by establishing a secure channel and exchanging cryptographic materials (certificates, keys) before any sensitive device identity information is transmitted. This preliminary security setup ensures that subsequent identity transmissions are protected without significantly delaying the bootstrapping process
Solution Approach 2:
The patent replaces the simple, unencrypted text transmission mechanism with a cryptographic security mechanism. Instead of directly sending device identities in clear text, the system uses digital certificates, public-key infrastructure, and encrypted channels to protect identity information while maintaining efficient communication
3Loss of time
If devices maintain continuous data plane connections for long polling, then real-time notifications can be received, but network resources are wasted due to keep-alive messages and connection maintenance
Solution Approach 1:
The patent replaces continuous connection maintenance with periodic action. Instead of maintaining constant data plane connections with periodic keep-alive messages, the system uses event-triggered notifications where devices only activate connections when actual data or events need to be transmitted, eliminating unnecessary periodic traffic
Solution Approach 2:
The patent extracts the notification functionality from the continuous data plane connection. By separating the control plane (for signaling and notifications) from the user plane (for data transfer), the system allows devices to receive notifications through control plane signaling without maintaining persistent user plane connections, thereby reducing network resource consumption
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Service layer and application triggering may be used in a machine-to-machine environment. In an embodiment, an existing service layer procedure, such as registration, may allow a device or gateway service layer or application to indicate to a machine-to-machine server what port is listened to for triggers. In another embodiment, triggering may be used to provide bootstrapping instructions, including temporary bootstrapping identifiers, in trigger requests. In another embodiment, triggering may be used to assist with event notification. Service layer or application instructions may be embedded inside of trigger payloads. A trigger payload format is defined.