Push Service Provisioning via On-Demand IP Allocation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Mobile network service providers face challenges in securing sufficient public IP addresses, leading to the use of NAT technology and private IP addresses, which result in continuous IP sessions that cause signaling overhead and resource waste, especially when maintaining connections with multiple mobile stations and application servers.
Innovation Solution
A method and apparatus that allow for the provision of a push service without continuous IP sessions by querying and allocating public IP addresses on demand through a location register and gateway, enabling efficient data transmission based on acquired public IP addresses.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If continuous IP sessions are maintained between mobile stations and application servers, then push service can be provided, but signaling overhead and wireless resource waste increase significantly
Solution Approach 1:
The patent implements periodic keep-alive messages transmitted at configurable intervals to maintain NAT table entries, replacing the need for continuous IP sessions. This periodic action allows the system to refresh network address translation mappings only when necessary, reducing signaling overhead while ensuring push service availability when data needs to be transmitted.
Solution Approach 2:
The system pre-establishes NAT table entries and maintains them through periodic refreshes before actual data transmission occurs. This preliminary action ensures that when push data arrives, the network path is already established, eliminating the need for continuous session maintenance while ensuring immediate data delivery capability.
2Reliability
If continuous IP sessions are maintained for M×N mobile stations and application servers, then push service is enabled, but the number of sessions and signaling burden increase
Solution Approach 1:
The patent merges multiple individual IP sessions into a single session between the mobile station and the application server. By using a unified NAT table entry that can handle multiple data transmissions, the system reduces the M×N session matrix into manageable individual sessions, significantly decreasing network complexity while preserving push service functionality.
Solution Approach 2:
The NAT table entry is designed to serve multiple functions: it maintains the IP session, handles data transmission, and supports push service delivery through periodic refreshes. This multi-functional approach allows a single session structure to replace multiple dedicated sessions, reducing overall system complexity.
3Reliability
If mobile stations transmit keep alive messages by periods to maintain continuous IP sessions, then push service can be provided, but power consumption increases
Solution Approach 1:
The patent implements periodic keep-alive message transmission at configurable intervals instead of continuous messaging. This approach maintains IP session continuity by refreshing NAT table entries only when necessary, significantly reducing the frequency of transmissions and thereby lowering power consumption while ensuring session reliability when needed.
4Quantity of substance
If NAT technology is used to allocate private IP addresses, then public IP address shortage is addressed, but external equipment cannot set IP sessions to mobile stations
Solution Approach 1:
The patent introduces a session management entity that acts as an intermediary between external application servers and mobile stations using private IP addresses. This intermediary maintains the NAT table, translates addresses, and manages session state, enabling external equipment to initiate push services to mobile stations with private IPs without requiring direct IP session establishment.
Data Source
AI summary
A method and a system are provided for a push service in a communication system. The method comprises: if there is data that is directed from an application server to an application of a terminal, transmitting, to a location register, a first message requesting location information of the terminal; if the location register receives the first message, transmitting, to a gateway, a second message requesting the location information of the terminal; transmitting, to the location register by the gateway, a third message including the location information of the terminal; transmitting, to the application server by the location register, a fourth message including the location information of the terminal; and transmitting, to the application of the terminal by the application server, the data using the location information of the terminal.


