Packet Gateway Session Identifier Injection for Mobile Private Network Routing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current solutions for enabling business VPN services in mobile networks are tied to the evolved packet core (EPC) and lack stickiness with EPC elements, making it difficult to leverage LTE service authorization and policy elements effectively, which limits the flexibility and efficiency of service management.
Innovation Solution
The solution involves a method where a packet gateway intercepts and modifies proxy binding update messages to include session identifiers, constructing a vendor-specific mobility option field, and sending this information to a local mobility anchor, allowing for session identifier extraction and caching, which enables tunnel setup and traffic forwarding between mobile access gateways and servers, thereby decoupling service logic from the EPC.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If service logic is tied to the evolved packet core (EPC), then service management is simplified, but flexibility and adaptability to move services outside EPC are reduced
Solution Approach 1:
The patent segments service logic into two parts: EPC-based service management functions remain in the core network, while service delivery functions are extracted and deployed in access network elements. This segmentation allows simplified EPC operation while enabling flexible service deployment in the access network.
Solution Approach 2:
Service logic is extracted from the EPC and relocated to access network elements such as base stations or access controllers. This extraction maintains EPC simplicity while enabling flexible service deployment in the access network, resolving the contradiction between ease of operation and adaptability.
2Adaptability or versatility
If service logic is moved outside the EPC to service nodes, then flexibility and adaptability are improved, but stickiness with EPC elements and ability to leverage LTE service authorization deteriorates
Solution Approach 1:
The patent introduces reference to LTE service authorization mechanisms as an intermediary between EPC and external service nodes. Service nodes outside EPC can leverage LTE service authorization through standardized interfaces, maintaining reliability and trust while enabling flexible deployment.
Solution Approach 2:
The service logic is designed with universal interfaces that can interact with both EPC elements and external service nodes. This multi-functionality allows service logic to maintain stickiness with EPC elements while being deployable outside EPC, resolving the contradiction between adaptability and reliability.
3Adaptability or versatility
If service logic is decoupled from EPC and deployed in access network elements, then service deployment flexibility is improved, but complexity of maintaining stickiness with EPC elements increases
Solution Approach 1:
The patent applies local quality by implementing service logic with different functional characteristics in different locations: EPC-side functions focus on authorization and management, while access network functions focus on service delivery. This localized functional differentiation reduces integration complexity while maintaining deployment flexibility.
Solution Approach 2:
Service logic is pre-configured with standardized interfaces and authorization mechanisms before deployment. This preliminary preparation reduces the complexity of maintaining stickiness with EPC elements, as the integration requirements are established in advance rather than configured dynamically.
Data Source
AI summary
A method provided in one embodiment includes receiving, at a packet gateway, a first binding update message from a mobile access gateway. The first binding update message has a destination address associated with a local mobility anchor. The method further includes extracting at least one session identifier associated with the mobile access gateway from the first binding update message, constructing an option field including the at least one session identifier, and appending the option field to the first binding update message to form a second binding update message. The method further includes sending the second binding update message to the local mobility anchor.