Data Session Policies

Smartphones and tablets require constant data connectivity, even when on networks where roaming agreements aren't favorable. Data session policies determine when ItsOn-powered devices can establish data sessions. 

The basic purpose for a data session policy is to block a data session from occurring and define exceptions to that blocking. It is to avoid superfluous connections while a device is not being used, but allow the connections when it is in use to not degrade the user experience. For example, you can create a data session policy that blocks data sessions when the device is not in the home network and is not in use, as determined by the screen being off, no media being streamed and the download manager being idle.

How Data Session Policies Work

Data session policies are evaluated when a network transition event or a user-initiated event occurs with an ItsOn-powered device. Examples of network transition events include moving from WiFi to cellular, moving from 3G to 4G, or moving from the home network to a roaming network. User-initiated events include an Internet app being brought to the foreground, the device being unlocked, or the device screen being turned on.

The Default Policy Event lists up to 3 blocking exceptions: Downloading, Screen On, and Streaming Media.

When a network transition event or a defined user trigger occurs, data session policies are evaluated in 2 steps:

Data Session Policy Examples

A common scenario is what is called ZULU, or zero use, low use. It occurs when a device isn't actively being used, but it is transitioning between networks, often within short periods of time, and the device wants to start or maintain data sessions even when they are not necessary. A good example is when a device is in an area where a roaming network is stronger than a home network, and the device moves briefly into an area where the home network is lost and the roaming network is used, such as when a device user goes into an elevator or garage. If there's nothing actively being done by the user, there's no reason to allow a data session. You can create a data session policy that blocks data sessions when the device is not in the home network and is not streaming data or downloading. 

Similarly, a device's user might be listening to music from a streaming app. When that's happening, you don't want to degrade the user experience by blocking data sessions during these micro network changes. You might refine the above data session policy to make an exception to data session blocking when the device is streaming media.