MTC Triggering Authorization via Intermediary Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Machine-Type-Communication (MTC) systems, there is a need to prevent unauthorized MTC server triggering, manage network congestion, validate trigger freshness, and handle failures to ensure secure and efficient communication between MTC devices and servers, particularly when MTC devices are offline or outside the 3GPP network domain.
Innovation Solution
Implementing a Service Capability Server and MTC-IWF that authenticate and authorize MTC servers and devices, protect trigger messages with integrity and confidentiality checks, manage trigger lifetimes to prevent replay attacks, and allow retry mechanisms for failed deliveries, while also considering the status of MTC devices during offline periods.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MTC server sends triggering messages to MTC devices, then the MTC device can be activated or notified, but unauthorized MTC servers may overload the network and cause battery consumption and mis-behaviour
Solution Approach 1:
The network acts as an intermediary between the MTC server and MTC device, performing authorization of the MTC server and validation of triggering messages. The network verifies the MTC server's authorization to send triggers to specific devices, preventing rogue servers from overloading the network while maintaining reliable communication channels.
2Reliability
If MTC device responds to triggering messages, then communication can be established, but responding to unauthorized triggers causes battery consumption and potential mis-configuration
Solution Approach 1:
The MTC device performs preliminary validation of the triggering message before responding. The device checks whether it is authorized to receive triggers from the sending MTC server and validates the message integrity using security contexts established during attachment. This preliminary validation prevents battery consumption from responding to unauthorized triggers.
3Reliability
If the network resends triggering messages to handle failures, then delivery reliability improves, but replay attacks and network overload may occur
Solution Approach 1:
The triggering message includes a sequential counter that increments with each resend attempt. The MTC device validates this counter to ensure the message is a legitimate retry rather than a replay attack. This periodic action mechanism allows the network to resend messages for reliability while preventing harmful replay attacks through counter validation.
4Reliability
If trigger messages are sent frequently to ensure delivery, then communication reliability improves, but network traffic and congestion increase
Solution Approach 1:
The patent combines multiple validation functions into a single triggering message structure. The message includes authorization validation, sequential counter for replay prevention, and delivery status tracking all in one transmission. This merging reduces the number of separate messages needed, decreasing network traffic while maintaining reliable delivery assurance.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Upon receiving a triggering message from a MTC server (20), a network (10) verifies if the MTC server (20) is authorized to trigger a target MTC device (30) and also if the MTC device (30) is authorized to respond the triggering message, by comparing an MTC device ID and MTC server ID (and optionally information on subscription) which are include in the triggering message with authorized ones. Upon succeeding in the verification, the network (10) checks a trigger type included in the triggering message to verify if the triggering message is authorized to be sent to the MTC device (30). Upon succeeding in the check, the network (10) forwards the triggering message to the MTC device (30). The network (10) also validates a response from the MTC device (30), by checking whether the MTC device (30) is allowed to communicate with the addressed MTC server (20).