MTC-IWF Trigger Quota Enforcement via Subscriber Data Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems lack an efficient mechanism to enforce and maintain trigger quotas for services capability servers (SCS) in machine-type communication (MTC) data flow, requiring frequent queries to the Home Subscriber Server (HSS) and not allowing caching of subscriber data, leading to inefficiencies in trigger authorization and delivery.
Innovation Solution
Implementing an online charging system (OCS) interface between the MTC-IWF and the HSS to check trigger quotas, allowing caching of subscriber information and reducing HSS queries, and using a Txx interface to deliver triggers and small data packets over the user plane, enabling efficient quota management and backward compatibility with existing systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the HSS checks trigger quota for every trigger request, then trigger quota enforcement is ensured, but the number of HSS queries increases and system efficiency decreases
Solution Approach 1:
The MTC-IWF performs preliminary actions by caching subscriber data and pre-authorizing trigger requests locally before they reach the HSS. This allows the system to enforce trigger quotas while reducing the number of real-time HSS queries needed during actual trigger authorization operations.
Solution Approach 2:
The MTC-IWF acts as an intermediary between the SCS and HSS, maintaining local trigger quotas and caching subscriber information. This intermediary role allows the system to enforce quotas locally without requiring every trigger request to query the HSS, thereby improving authorization efficiency while maintaining reliability.
2Measurement precision
If the MTC-IWF queries HSS before every trigger request, then accurate subscriber information is obtained, but communication overhead and processing time increase
Solution Approach 1:
The MTC-IWF retrieves and caches subscriber information in advance from the HSS before actual trigger requests are processed. This preliminary action ensures accurate subscriber information is available locally, eliminating the need for time-consuming HSS queries during each trigger authorization event.
Solution Approach 2:
The MTC-IWF serves as an intermediary that maintains local caches of subscriber data, reducing the frequency of HSS queries. This approach preserves information accuracy by using cached data while significantly reducing the time loss associated with repeated HSS communications.
3Reliability
If trigger quotas are strictly enforced without caching, then quota compliance is maintained, but system complexity and query frequency increase
Solution Approach 1:
The MTC-IWF performs preliminary quota checks and caches the results locally. This allows the system to maintain strict quota compliance while reducing the operational complexity of repeatedly querying the HSS for every trigger request, as the cached quota information can be used for multiple authorizations.
Solution Approach 2:
The MTC-IWF acts as an intermediary that maintains local trigger quotas and subscriber data caches. This intermediary function enables the system to enforce quota compliance reliably while simplifying the overall system architecture by reducing dependencies on frequent HSS interactions.
Data Source
AI summary
Method and apparatus are described for delivering triggers and small data. In an embodiment, a receiver may be configured to receive a trigger or small data packet, and a transmitter may be configured to transmit a subscriber information request to see whether a subscriber is present. The receiver may be further configured to receive an identity of a second node on a condition that the subscriber is present. The transmitter may be further configured to transmit the trigger or small data packet to the second node over an interface, the second node configured to create an Internet Protocol (IP) packet with an IP address containing the trigger or small data packet and deliver the IP packet to a wireless transmit/receive unit (WTRU) using the IP address and a default or dedicated bearer of the WTRU.