SCEF Device Triggering for Non-IP Data Delivery
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current deployments of Machine-Type Communication-Interworking Function (MTC-IWF) for Non-IP Data Delivery in mobile communication networks are costly and inefficient, particularly due to the need for extensive infrastructure to handle error conditions and EPS bearer context management.
Innovation Solution
The proposed solution involves enhancing the Service Capability Exposure Function (SCEF) to facilitate device triggering for Non-IP Data Delivery without relying on MTC-IWF, using Mobile Terminated (MT) device triggering and SMS device triggering procedures, which allow the SCEF to manage EPS bearer contexts and initiate device triggering through existing network components like MME and MSC.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If MTC-IWF is deployed to handle device triggering for Non-IP Data Delivery, then device triggering functionality is provided, but deployment and operational costs increase significantly
Solution Approach 1:
The patent combines the device triggering functionality with the existing SCEF infrastructure. The SCEF is enhanced to perform both service capability exposure and device triggering functions that were previously handled by separate MTC-IWF components, thereby reducing overall infrastructure complexity while maintaining reliability
Solution Approach 2:
The SCEF is designed to perform multiple functions including service capability exposure, device triggering for Non-IP data delivery, and EPS bearer context management. This multi-functional approach eliminates the need for dedicated MTC-IWF components, reducing deployment costs while providing comprehensive device triggering functionality
2Reliability
If MTC-IWF is used for Non-IP Data Delivery triggering, then error conditions are handled, but operational costs increase
Solution Approach 1:
The enhanced SCEF performs device triggering and error handling autonomously using existing network components like MME and MSC. The system leverages self-service mechanisms where the SCEF manages its own triggering operations and error conditions without requiring additional MTC-IWF operational infrastructure, thereby reducing operational costs while maintaining reliable error handling
3Reliability
If extensive infrastructure is deployed for MTC-IWF, then EPS bearer context management is improved, but capital costs increase
Solution Approach 1:
The patent extracts the EPS bearer context management functionality from the proposed extensive MTC-IWF infrastructure and integrates it into the existing SCEF. This extraction approach allows the system to maintain reliable EPS bearer context management while avoiding the capital costs associated with deploying separate extensive infrastructure
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method is provided in one example embodiment and may include receiving, by a Service Capability Exposure Function (SCEF), a request to send data to a user equipment (UE), wherein a context for the UE is not available at the SCEF when the request is received; querying a subscriber database to determine whether the context for the UE is available at the subscriber database; and sending the data for the UE to a Mobility Management Entity (MME) by the SCEF using an interface directly interconnecting the MME and the SCEF based on a determination that the context for the UE is available at the subscriber database.