GTPC Private Extension for Non-Co-located Node Optimization
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current GTPC (S11 and S5 interface) optimization methods are limited to co-located core nodes, which restricts optimization when user equipment (UE) moves to a different Serving Gateway (SGW) or Packet Data Network (PDN) Gateway.
Innovation Solution
The proposed method involves using a Private Extension capability in the GTPC stack to send a feature name and socket information in a first message over the S11 or S5 interface, allowing peer nodes to confirm support for GTPC optimization. This enables the use of IPC (Inter-Process Communication) for subsequent messaging, reducing the load on S11 and S5/S8 interfaces.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If GTPC optimization is implemented using co-located core nodes, then processing load on interfaces is reduced, but optimization cannot be applied when UE moves to different SGW or PDN Gateway
Solution Approach 1:
The patent introduces a Private Extension capability as an intermediary mechanism that enables GTPC optimization to work across non-co-located nodes. This extension acts as a mediator that carries socket information and feature names between MME and peer nodes, allowing IPC-based optimization to function even when core nodes are distributed rather than co-located, thus resolving the contradiction between processing efficiency and mobility support.
Solution Approach 2:
The patent implements preliminary action by exchanging feature name and socket information in advance through the Private Extension capability. This pre-establishment of communication channels and capability confirmation allows the system to prepare for optimized IPC-based messaging before actual UE mobility events occur, enabling both co-located and non-co-located optimization scenarios to function efficiently.
2Adaptability or versatility
If traditional GTPC messaging is used over S11 and S5 interfaces, then node placement flexibility is maintained, but processing load on core nodes increases
Solution Approach 1:
The Private Extension capability serves as an intermediary that enables the system to switch between traditional GTPC messaging and optimized IPC-based messaging. When activated, it reduces processing load by using local IPC communication instead of full GTPC stack processing, while maintaining node placement flexibility through the socket information exchange mechanism that works for both co-located and non-co-located scenarios.
Solution Approach 2:
The patent implements dynamics by making the communication mechanism adaptable - the system can dynamically choose between traditional GTPC interface messaging and optimized IPC-based messaging based on whether the Private Extension capability is supported and activated. This dynamic switching allows the system to optimize processing load when conditions permit while maintaining flexibility when they don't.
3Productivity
If GTPC optimization is implemented, then control plane signaling is optimized, but requires additional feature negotiation and socket information exchange
Solution Approach 1:
The patent applies preliminary action by performing feature negotiation and socket information exchange once during initial setup through the Private Extension capability. This one-time preliminary configuration enables subsequent optimized IPC-based messaging without requiring repeated negotiation overhead, thus achieving control plane signaling optimization while limiting the additional complexity to an initial setup phase rather than continuous operation.
Data Source
AI summary
Systems and methods are disclosed for providing GPRS Tunneling Protocol Core (GTPC) optimization. In one embodiment a method includes sending a first message from a Mobility Management Entity (MME) to a peer node, the first message including a feature name and socket information in a private extension over an interface; wherein a message format includes a message type, a Tunnel Endpoint Identifier (TEID) and a bitmask; when the peer node supports GTPC optimization, then confirming, by the peer node, by encoding the docket information in a response message and sending the response message to the MME.