SCEF Location Context API for Network Congestion Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current location tracking APIs in M2M systems do not provide location-based context information, such as available Radio Access Technologies (RATs) and congestion levels, which are essential for optimizing network resource utilization and service delivery.
Innovation Solution
The introduction of a new API and communication protocols between the Service Capability Exposure Function (SCEF) and core network entities like MME, SGSN, AAA Server, and PCRF, allowing the SCEF to inquire about and convey location-based context, including RAT availability and congestion levels, to Application Servers and Service Capability Servers.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If current location tracking APIs are used, then basic location information can be obtained, but location-based context information (RAT availability, congestion levels) is not provided
Solution Approach 1:
The SCEF acts as an intermediary between the core network entities (MME, SGSN, AAA Server, PCRF) and Application Servers. It receives location-based context information from core network entities via new communication protocols and exposes this information to Application Servers through a new API, thereby mediating the information flow without requiring direct complex interactions between all components
Solution Approach 2:
The solution segments the information delivery system into distinct functional components: the SCEF as an exposure function, separate core network entities (MME, SGSN, AAA Server, PCRF) that generate context information, and Application Servers that consume it. This segmentation allows each component to operate independently with standardized interfaces, reducing overall system complexity despite the added functionality
2Productivity
If detailed location context information is provided, then intelligent resource management and service optimization are enabled, but network infrastructure complexity increases
Solution Approach 1:
The SCEF is designed as a universal exposure function that can serve multiple Application Servers and multiple types of core network entities simultaneously. The new API provides a universal interface for accessing location-based context information regardless of the specific source entity, enabling multi-functional operation that improves resource management efficiency without proportionally increasing complexity
Solution Approach 2:
The SCEF mediates between diverse core network entities and various Application Servers, providing a standardized interface that simplifies interactions. This intermediary approach allows detailed context information to be collected from multiple sources and delivered to multiple consumers through a single unified mechanism, improving productivity while containing infrastructure complexity
3Adaptability or versatility
If new API and communication protocols are introduced, then location-based context can be inquired and conveyed, but system implementation complexity increases
Solution Approach 1:
The SCEF serves as an intermediary that handles the complexity of new communication protocols internally while presenting a simplified new API to Application Servers. It translates between the protocol requirements of core network entities and the needs of application-level users, thereby enabling context inquiry capability without requiring Application Servers to directly implement complex protocol stacks
Solution Approach 2:
The new communication protocols establish feedback mechanisms between the SCEF and core network entities (MME, SGSN, AAA Server, PCRF), allowing the SCEF to inquire about and receive location-based context information. This feedback-oriented design enables versatile context inquiry while managing implementation complexity through standardized request-response patterns
Data Source
Figure 1
Figure 2
Figure 3
AI summary
An enhanced 3GPP network architecture can enables a SCEF to interact with SCS/AS via APIs that provide location based context; GMLC to get the UE's location, available RATs, and congestion levels; HSS to get the UE's location, available RATs, and congestion levels; PCEF (via PCRF) to obtain the the congestion level at the P-GW; RCAF (via PCRF) to obtain the user plane congestion levels at the E-UTRAN, UTRAN, and WLAN; and serving nodes (MME, SGSN, 3GPP AAA Server) to get the available RATs and congestion levels.