MTC-IWF Trigger Delivery via Dynamic Path Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
MTC device triggering issues arise due to unprotected NAS or user plane messages, leading to discarded triggers, network overload, and MTC device battery consumption, with current mechanisms lacking optimization for delivery route selection.
Innovation Solution
Implementing a system where MTC-IWF or GGSN/P-GW holds and forwards trigger messages via alternative paths after security checks, using a priority list for optimal route selection based on UE capabilities and serving node information, and directly forwarding SMS triggers to MSC if the MTC device does not support IMS.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MTC device trigger is sent in unprotected NAS messages, then delivery flexibility is improved, but security reliability deteriorates causing trigger discard and battery consumption
Solution Approach 1:
MTC-IWF is introduced as an intermediary function between the trigger source and the MTC device. It receives triggers from external sources, performs security validation, and forwards them through appropriate network nodes (MME, SGSN, or MSC) based on device capabilities and network conditions, thereby ensuring both flexibility and reliability in trigger delivery
2Reliability
If MTC device trigger is sent via multiple paths, then delivery reliability is improved, but network load increases causing overload
Solution Approach 1:
The trigger delivery path is made dynamic rather than static. MTC-IWF selects the optimal path (control plane via MME, control plane via SGSN, or user plane via S-GW/P-GW) based on real-time factors including MTC device capabilities, network conditions, and trigger characteristics, thereby achieving reliable delivery without unnecessary network load
3Reliability
If trigger is resent after discard, then delivery reliability is improved, but battery consumption increases
Solution Approach 1:
A feedback mechanism is implemented where MTC device sends rejection messages with cause codes to MTC-IWF when triggers are discarded. MTC-IWF uses this feedback to adjust its behavior, selecting alternative delivery paths or modifying trigger characteristics to prevent future rejections, thereby avoiding repeated resends and reducing battery consumption
4Adaptability or versatility
If MTC-IWF forwards trigger through MME, then delivery compatibility is improved, but delivery efficiency deteriorates for non-IMS devices
Solution Approach 1:
The trigger delivery process is segmented into capability-based paths. MTC-IWF first determines MTC device capabilities (IMS support or not), then directs triggers through appropriate paths: non-IMS devices receive triggers directly via MSC, while IMS-capable devices go through MME, eliminating unnecessary routing steps for each device type
Data Source
AI summary
A network node (21), which is placed within a core network, stores a list of network elements (24) capable of forwarding a trigger message to a MTC device (10). The network node (21) receives the trigger message from a transmission source (30, 40) placed outside the core network, and then selects, based on the list, one of the network elements to forward the trigger message to the MTC device (10). The MTC device (10) validates the received trigger message, and then transmits, when the trigger message is not validated, to the network node (21) a reject message indicating that the trigger message is not accepted by the MTC device (10). Upon receiving the reject message, the network node (21) forwards the trigger message through a different one of the network elements, or forwards the reject message to transmission source (30, 40) to send the trigger message through user plane.