SCEF Node Consolidates MTC Device Connections to Multiple Application Servers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current wireless access networks face challenges in efficiently managing multiple connections for Machine-Type Communication (MTC) devices, leading to increased data traffic and resource consumption, particularly when devices need to communicate with multiple application servers, which complicates provisioning and increases storage requirements.
Innovation Solution
Implementing a Service Capability Exposure Function (SCEF) node that allows MTC devices to communicate with multiple application servers via a single Access Point Name (APN), using a single connection and specifying which servers receive uplink data through identifiers in messages, reducing the need for multiple SCEF configurations and conserving network resources.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If MTC devices establish multiple separate connections to communicate with multiple application servers, then communication capability is improved, but device complexity and resource consumption increase
Solution Approach 1:
The patent combines multiple application server connections into a single connection through the SCEF node. The SCEF acts as a consolidation point where multiple AS connections are merged, allowing the MTC device to communicate with multiple AS through one unified connection rather than maintaining separate connections to each AS.
Solution Approach 2:
The SCEF node performs multiple functions including connection management, message routing, and data forwarding for multiple application servers through a single interface. This multi-functional approach allows one connection to serve multiple communication purposes with different AS.
2Adaptability or versatility
If MTC devices maintain multiple connections to multiple application servers, then communication versatility is improved, but memory requirements and battery consumption increase
Solution Approach 1:
Multiple connection management tasks are merged into the SCEF node, which handles authentication, session management, and data routing for multiple AS through a single connection. This consolidation reduces the computational burden and energy consumption on the MTC device.
Solution Approach 2:
The SCEF acts as an intermediary between the MTC device and multiple application servers, handling the complexity of multiple connections on the network side rather than requiring the device to manage each connection individually. This mediator approach reduces device energy consumption.
3Adaptability or versatility
If multiple SCEF configurations are created for different application servers, then service coverage is improved, but network complexity and provisioning difficulty increase
Solution Approach 1:
A single SCEF configuration is designed to handle multiple application servers through universal interfaces and standardized protocols. The SCEF can dynamically route messages to different AS based on message content rather than requiring separate dedicated configurations for each server.
Solution Approach 2:
The system segments the functionality into the MTC device, SCEF node, and multiple application servers, with the SCEF handling the complexity of multi-server management. This functional segmentation allows a single simplified configuration at the device level while maintaining comprehensive service coverage.
Data Source
AI summary
A computing device may include a memory configured to store instructions and a processor configured to execute the instructions to receive a message from a user equipment (UE) device via a Mobility Management Entity (MME), wherein the computing device is configured as a Service Capability Exposure Function (SCEF) device. The processor may be further configured to identify an application server associated with the message based on one or more application server identifiers included in the received message; map uplink data, included in the received message and associated with the identified application server, to an application programming interface (API) associated with the identified application server; and send the mapped uplink data to the identified application server using the API associated with the identified application server.


