Two-Way IP Channel for UICC Secure Access in LTE
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In fourth-generation telecommunications networks like LTE, the transition from SMS-based communication channels to IP packets poses a challenge for secure access to a UICC (Universal Integrated Circuit Card) from a remote server, as existing methods lack a mechanism for establishing a secure two-way IP communication channel using only the IP address of the terminal.
Innovation Solution
A method is introduced where the local server on the UICC transmits the IP address of the remote server and communication port number to the terminal, followed by a request to connect, enabling the establishment of a two-way IP communication channel by combining identifiers and IP addresses to facilitate secure access from the remote server to the local server through the terminal.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If SMS-based communication channels are used for remote server access to UICC, then secure access can be established, but this method is incompatible with fourth-generation IP-based networks like LTE where SMS channels no longer exist
Solution Approach 1:
The patent changes the communication parameter from SMS-based to IP-based, enabling the system to operate in LTE networks. The local server and remote server establish direct IP communication channels, replacing the SMS dependency while maintaining security through IP address verification and authenticated communication protocols
Solution Approach 2:
The terminal acts as an intermediary between the local server (in UICC) and the remote server. It receives IP addresses from both servers, establishes bidirectional IP communication channels, and forwards data packets, enabling secure access without direct SMS involvement
2Adaptability or versatility
If direct IP communication channels are established between remote server and terminal, then network compatibility with LTE is achieved, but the mechanism for secure access to UICC local server becomes complex and uncertain
Solution Approach 1:
The terminal performs preliminary actions by obtaining and storing both the local server's IP address (from UICC) and the remote server's IP address (from network configuration) before actual communication begins. This pre-establishment of address information simplifies the subsequent channel setup process
Solution Approach 2:
The communication establishment process is segmented into distinct phases: local server to terminal channel setup, terminal to remote server channel setup, and data forwarding operations. This segmentation makes the complex process manageable and implementable through separate protocol handlers
3Ease of operation
If the terminal forwards data between local and remote servers, then two-way communication is enabled, but security risks increase due to potential unauthorized access
Solution Approach 1:
The terminal implements feedback mechanisms by verifying IP addresses and communication requests against authorized lists. The local server provides authentication credentials, and the terminal uses these to validate incoming data packets, blocking unauthorized access attempts while allowing legitimate communication
Solution Approach 2:
The system applies preliminary anti-action by pre-configuring security filters and authentication rules before data exchange begins. The terminal and servers establish trusted relationships in advance, and any deviation from authorized communication patterns is immediately blocked
Data Source
AI summary
A method for establishing a communication channel between a local server and a remote server includes: i) transmitting, from the local server to a terminal, the IP address of the remote server and a communication port of the local server; ii) transmitting the IP address of the terminal from the terminal to the local server; iii) transmitting, from the local server to the terminal, a request to connect to the remote server, including the IP addresses of the remote server and the terminal, an identifier of the local server; and the communication port; iv) transmitting, from the local server to the remote server, the IP address of the terminal, an identifier of the local server, and the communication port; and v) combining, at the remote server, the identifier of the local server and the IP address of the terminal to ascertain an IP address of the local server.

