Gateway SNI Header Reading for Secured Subscriber Information Transmission
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing solutions for transmitting subscriber information in mobile networks are limited to HTTP transactions and become obsolete with the transition to HTTPS, as they are hindered by Network Address Translators (NAT) and are less efficient due to multiple table lookups, especially in API-based solutions.
Innovation Solution
A method and system that allow mobile operators to transmit subscriber information from the core network's gateway to trusted partners via HTTPS, by reading the SNI header or destination IP address in HTTPS transactions and forwarding the information through a secured connection, enabling correlation and successful transaction acknowledgement.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If HTTP transactions are used for subscriber information transmission, then the transmission process is simple, but the solution becomes obsolete with HTTPS transition and is hindered by NAT nodes
Solution Approach 1:
The gateway acts as an intermediary between the UE and the server, establishing a separate HTTPS connection to transmit subscriber information. This mediator approach allows the system to maintain compatibility with HTTPS-encrypted traffic while enabling subscriber information transmission that would otherwise be blocked by NAT nodes and encryption protocols.
Solution Approach 2:
The transmission process is segmented into two independent channels: the original HTTPS transaction channel for data communication, and a separate gateway-initiated HTTPS channel for subscriber information transmission. This segmentation allows each channel to serve its specific purpose without interfering with the other, resolving the conflict between HTTPS encryption and subscriber information accessibility.
2Reliability
If API-based solutions are used for subscriber information transmission, then subscriber information can be shared with trusted partners, but the process becomes less efficient due to multiple table lookups
Solution Approach 1:
The gateway performs preliminary actions by establishing the HTTPS connection and preparing the subscriber information transmission before the actual data session occurs. By pre-configuring the transmission channel and having subscriber information ready at the gateway, the system eliminates the need for multiple table lookups during the actual transmission, thereby improving efficiency while maintaining reliability.
3Adaptability or versatility
If subscriber information is transmitted through NAT nodes, then coverage is extended to all data sessions, but the transmission becomes more complex and less reliable
Solution Approach 1:
The gateway serves as a trusted intermediary that operates outside the NAT translation process. By establishing its own HTTPS connection to the server and directly providing subscriber information, the gateway bypasses NAT-related reliability issues while maintaining extended coverage to all data sessions, including those that would otherwise be blocked by NAT nodes.
Data Source
AI summary
Systems and methods are provided for transmitting subscriber information via HTTPS. Upon a UE initiating an HTTPS transaction to a server, the gateway reads an SNI header of the HTTPS transaction or a destination IP address of the server. If the SNI header or the destination IP address in the HTTPS transaction matches a pre-configured SNI header or destination IP address that requires subscriber information, the gateway copies a portion of an HTTPS message corresponding to the HTTPS transaction. The gateway initiates a secured connection to the server via HTTPS and forwards the subscriber information to the server, including the portion of the HTTPS message used to correlate the subscriber information to the original HTTPS transaction. Upon successfully correlating the subscriber information to the original HTTPS transaction, an acknowledgement is received that the HTPPS transaction is successful.