Case Studies
Overview
When it comes to regulatory compliance, you can’t afford not to have complete network visibility. You need to know what is, and what is not, happening on your network at any given time. A large wireless voice and data carrier with 15 million subscribers worldwide had this exact problem — they had blind spots that they knew were causing problems but couldn’t see a solution.
Customer Challenges
The wireless communications carrier needed a solution to address the following four pain points:
• Identify calls that were bypassing the Lawful Intercept Mirror IMS State Function (LMISF) network functionality.
• Correlate the signaling and data streams for those calls for packet capture file (PCAP) creation.
• Analyze the information to determine if the scenario was created by a malicious entity or if it was some sort of misconfiguration error.
• Finally, mitigate the problem by either fixing the configuration error or sending the malicious information to the legally authorized enforcement agency.
Specifically, the carrier needed to capture specific pieces of voice and data packets on their network and then be able to forward a copy of that data to legally authorized government collection points. While lawful intercept of voice and data isn’t a new concept, a problem has been created by an increase in encrypted data and VoLTE roaming calls due to the discontinuance of 3G network equipment. Some calls were believed to be bypassing the LMISF unit. Exacerbating the problem is that fact that multi-roaming calls are routed through a disaggregated network, meaning that logs produced by individual elements are not sufficiently detailed for root cause analysis of the problem.
In this case, the European wireless service provider turned to Keysight Technologies — the only network visibility vendor that is part of the ETSI standards group. Keysight has a long history of understanding visibility solutions for service providers, which was clearly evident by the solution that was provided.
Keysight’s Solution
Keysight was able to solve the customer’s problem by deploying a solution with the following components:
• Vision X packet broker that has a backbone capacity of full-duplex, non-blocking, and line rate traffic at 12.8 Tbps.
• A variety of fiber interfaces for the Vision X that can support 10GE, 25GE, 40GE, 50GE and up to 100GE wire speeds.
• The MobileStack feature package which supports data correlation and packet capturing and filtering for wireless carrier networks.
• The AppStack feature package which supports application filtering and the collection and correlation of metadata.
• 100 GE Flex taps and CloudLens virtual taps that enable user traffic to be collected using physical taps and the control plane traffic to be captured using virtual taps.
One of the most important features that the customer was looking for was QCI-based bearer identification. In this case, QCI stands for QoS Class Identifier, as described in the 3GPP TS 23.203/ ETSI TS 123 203 standards. User traffic bearers are assigned a QCI number between 1 and 9. As an example, a QCI of 1 is used for real-time voice (best quality), a QCI of 5 is used for call signaling (e.g. call setup and call tear down), and a QCI of 9 is the low priority level which is used for standard internet traffic. In certain situations, like when an inbound roamer from another carrier, completes a call into the roaming network, this can present challenges, especially when encryption is used. While calls are normally encrypted, which is good for privacy, it causes a problem for lawful interception obligations. This is because the encryption keys are managed by the whole network of the roaming subscriber. To resolve this issue, carriers agree to turn off encryption for roaming voice calls. If encryption is accidentally or maliciously turned on, the LMISF unit does not get activated.
Even though the wireless carrier has a LMISF unit to implement lawful interception of calls, delivering a copy of those calls to law enforcement when activated for targeted users was a challenge because the unit only looks at calls with a quality with a QCI of 1 or 5. Everything else is ignored. So, some use cases, like misconfigured settings or deliberate obfuscation by the user, can trigger a bypass of the LMISF unit. This is where Keysight’s Lawful intercept solution is able to fill the gap. Keysight’s MobileStack product supports the QCI function, as described in 3GPP TS 23.203/ ETSI TS 123 203. The product filters user plane traffic matching a specified QCI value, enabling the monitoring of specific services. Once engaged, MobileStack sends the live correlated control plane information, along with the user plane traffic that matches the filtering criteria, to a configured egress destination where the traffic can be captured and stored in a PCAP file by another device. If the filtering criteria is the user id (e.g IMSI, MSISDN), the result will be that the live correlated traffic for those users will be sent towards the configured egress ports where capture can occur.
What are you looking for?