Today, there exist hundreds of thousands of mobile data applications for mobile devices
[2] and
[3]. Many of these applications utilize the mobile broadband connections to provide various types of communications to the users. While some of these applications focus on more
"traditional" use cases such as web browsing or email reading, other emerging applications such as social networking applications help the users to
"stay connected" with their friends on the go. Below is a short list of different categories of mobile data applications:
-
Web browsing
-
Email
-
Weather/News updates
-
VoIP (Skype, etc.)
-
Social Networking (Facebook)
-
Geo services (Google places/location-targeted ads)
-
Online games
-
Messaging (SMS and instant messaging)
-
etc.
A recent study
[4] noted that the way social networking applications on mobile devices transmit and receive status update messages can cause significant signalling congestions in 3G networks. There are other operational characteristics of the mobile data applications, such as small data transmission and frequent start or stop of services that can cause adverse impacts to the mobile network.
So as more and more mobile data traffic is handled by the network, the signalling traffic associated with various non-mtc mobile data applications can cause high signalling burden on the network and lead to poor user experience. Also, some of these applications have
"keep alive" messages that can generate large amount of signalling traffic.
As shown in Figure 1, it can be observed that, there is a many-to-many mapping between the mobile data apps and their operational characteristics/potential problems. Such mapping implies that:
-
One application can potentially cause multiple problems to the network.
-
Different applications can contribute to the same problem to the network, thereby aggravating the problems observed in the EPC and RAN.