Trace ID Partitioning for Secure TCE Routing in 3GPP Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current methods for Minimization of Drive Tests (MDT) in 3GPP networks face challenges in efficiently providing Trace Collection Entity (TCE) IP addresses to network elements without revealing them to mobile equipment or end users, and cause overhead on the radio link, especially when UEs are in idle mode.
Innovation Solution
The method involves partitioning the Trace ID space, encoding a partition ID within the Trace ID, and mapping it to a specific TCE, allowing efficient TCE IP address provision across network elements without additional signaling over the air, ensuring backward compatibility and security.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If TCE IP address is transmitted to UE at configuration time, then the network knows about the destination TCE of the UE, but the IP address of the network nodes in the core network is disclosed to mobile equipments or end users which is a security issue
Solution Approach 1:
The patent introduces an intermediary mapping mechanism where the TCE IP address is not directly transmitted to the UE. Instead, a TCE ID is sent to the UE, which is then mapped to the actual TCE IP address through a mapping table maintained by network elements (eNB or MME). This intermediary TCE ID acts as a proxy that preserves security while enabling correct routing of trace data.
Solution Approach 2:
The patent extracts the TCE IP address information from the direct configuration message to the UE. Only a simplified TCE ID is transmitted to the UE, while the complete TCE IP address mapping information is retained and managed by the network infrastructure. This separation allows the UE to identify the correct TCE without exposing internal network addressing schemes.
2Object-affected harmful factors
If TCE ID is sent to the UE instead of IP address, then security is improved, but this ID is sent over the radio interface which is considered as a precious transmitting channel and a bottleneck in network signaling
Solution Approach 1:
The patent merges the TCE ID transmission with existing signaling messages that are already exchanged between the UE and the network. Specifically, the TCE ID is included in the measurement report message that the UE sends to the network anyway. This integration eliminates additional signaling overhead on the radio interface while maintaining the security benefits of not transmitting the actual IP address.
3Adaptability or versatility
If multiple TCEs exist in the same network, then TCE usage optimization and load balancing are enabled, but the network node receiving the measurements might not be the same as the one who activated MDT on that UE, creating routing challenges
Solution Approach 1:
The patent applies preliminary action by pre-configuring the mapping between TCE IDs and TCE IP addresses in mapping tables maintained by network elements before trace data needs to be routed. When a UE sends measurements, the receiving network element can immediately look up the TCE ID in its local mapping table to determine the correct destination TCE, without needing complex real-time routing decisions or knowledge of which node activated the MDT.
Data Source
AI summary
A method of managing trace sessions in a network, wherein each trace session is assigned a Trace ID and a specific trace collection entity TCE (5) from a plurality of TCEs (5) disposed inside the network for storing the related measurements of the trace session, is characterized in the steps of partitioning the space of the Trace ID such that each partition is associated to one or more of the plurality of TCEs (5), encoding a partition ID inside the Trace ID, and mapping the partition ID to a specific TCE (5) from the plurality of TCEs (5). Furthermore, a corresponding trace session management system is described.