Detecting Problematic Control-Plane Protocol Interactions in Mobile Networks
Detecting Problematic Control-Plane Protocol Interactions in Mobile Networks
复制标题
检测移动网络中有问题的控制平面协议交互
DOI：
10.1109/tnet.2015.2404336
复制
发表时间：
2016
期刊：
影响因子：
--
通讯作者：
Songwu Lu
中科院分区：
文献类型：
--
作者：
Guan;Yuanjie Li;Chunyi Peng;Chi;Songwu Lu
3G/4G 移动网络中的控制平面协议相互通信，并提供丰富的控制功能，例如无线资源控制、移动性支持、连接管理等。尽管其意义重大，但验证协议正确性的问题在很大程度上仍未得到解决。在本文中，我们研究了移动网络中的控制平面协议交互。我们提出了 CNetVerifier，一种两阶段信号诊断工具，用于检测设计和实践中存在问题的交互。 CNetVerifier 首先通过特定领域的模型检查基于 3GPP 标准进行协议筛选，然后在运营的 3G/4G 网络中进行基于手机的经验验证。通过 CNetVerifier，我们沿着跨（协议）层、跨（电路交换和数据包交换）域以及跨（3G 和 4G）系统三个维度发现了七种麻烦的交互。有些是由必要但有问题的合作引起的（即，需要协议交互，但它们行为不当），而另一些则是由于独立但不必要的耦合操作（即，不需要协议交互，但实际上是耦合的）。这些实例涵盖了 3GPP 标准中的设计缺陷以及运营商和供应商的操作失误。它们都会导致性能损失或功能错误。我们推断根本原因，提出实证结果，提出解决方案，并总结经验教训。
The control-plane protocols in 3G/4G mobile networks communicate with each other, and provide a rich set of control functions, such as radio resource control, mobility support, connectivity management, to name a few. Despite their significance, the problem of verifying protocol correctness remains largely unaddressed. In this paper, we examine control-plane protocol interactions in mobile networks. We propose CNetVerifier, a two-phase signaling diagnosis tool to detect problematic interactions in both design and practice. CNetVerifier first performs protocol screening based on 3GPP standards via domain-specific model checking, and then conducts phone-based empirical validation in operational 3G/4G networks. With CNetVerifier, we have uncovered seven types of troublesome interactions, along three dimensions of cross (protocol) layers, cross (circuit-switched and packet-switched) domains, and cross (3G and 4G) systems. Some are caused by necessary yet problematic cooperation (i.e., protocol interactions are needed but they misbehave), whereas others are due to independent yet unnecessary coupled operations (i.e., protocols interactions are not required but actually coupled). These instances span both design defects in 3GPP standards and operational slips by carriers and vendors. They all result in performance penalties or functional incorrectness. We deduce root causes, present empirical results, propose solutions, and summarize learned lessons.