Dedicated Bearer Routing Between Local and PDN Gateways
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing 3GPP networks lack a direct connection mechanism between local servers and application servers, leading to inefficiencies in sharing local context information and preference-based filtering of advertisements, especially when user equipment devices access local networks through small cells.
Innovation Solution
A method is introduced where user equipment devices or service capability servers initiate the creation of dedicated bearers between local gateways and packet data network gateways, utilizing Network Address Translation (NAT) and Traffic Flow Templates (TFT) to route traffic between local servers and application servers, enabling direct communication within the operator's EPC network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If a direct connection mechanism is implemented between local servers and application servers, then information sharing efficiency is improved, but device complexity increases
Solution Approach 1:
The patent introduces a Service Capability Exposure Function (SCEF) as an intermediary entity that manages and coordinates the direct bearer connections between local servers and application servers. The SCEF receives requests from AS/SCS, determines appropriate L-GWs, and orchestrates the bearer creation process through interaction with MME and S-GW, thereby enabling efficient information sharing while abstracting the complexity of direct peer-to-peer connection management
Solution Approach 2:
The patent segments the connection establishment process into distinct functional stages: (1) AS/SCS initiates bearer creation request to SCEF, (2) SCEF determines target L-GW and interacts with MME, (3) MME establishes dedicated bearer through S-GW to L-GW, and (4) local server communicates directly with AS/SCS over the established bearer. This segmentation allows each entity to handle only its specific function, reducing overall system complexity while enabling efficient information sharing
2Measurement precision
If traffic routing through NAT and TFT is implemented, then traffic routing precision is improved, but device complexity increases
Solution Approach 1:
The patent implements self-service routing where the local server and AS/SCS automatically perform Network Address Translation (NAT) and apply Traffic Flow Templates (TFT) to their own traffic without requiring manual configuration or external intervention. The routing rules are established through the bearer creation process, and the endpoints autonomously enforce the routing policies, achieving precise traffic routing while minimizing the operational complexity burden on network operators
3Reliability
If dedicated bearers are established between L-GW and P-GW, then connection reliability is improved, but device complexity increases
Solution Approach 1:
The patent leverages the existing multi-functional 3GPP Evolved Packet Core (EPC) network infrastructure to establish dedicated bearers. The same MME, S-GW, and L-GW entities that handle standard user equipment connections are reused to create and manage the dedicated bearers between local servers and application servers. This universal approach ensures reliable connections while avoiding the need for separate specialized infrastructure, thereby limiting the increase in device complexity
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A user equipment device (UE) initiates the creation of a dedicated bearer between a local gateway (L-GW) and a packet data network gateway (P-GW). A GTP tunnel is established to connect the L-GW, a serving gateway (S-GW), and the P-GW. The L-GW and P-GW apply Network Address Translation (NAT) and/or Traffic Flow Template (TFT) to route the traffic between the LS and a Service Capability Server / Application Server (SCS/AS). Alternatively, an SCS-initiates the bearer creation, and an SCEF manages the creation of the GTP tunnel connecting. The L-GW may be co-located with an Evolved UTRAN Node B (eNB) and/or connected to multiple eNBs which are not co-located with the L-GW.