The PacketZoom Mobile Expresslane is a software-defined solution customized for each end user. By removing roadblocks in the mobile last mile, PacketZoom is able to significantly accelerate the performance by 2x to 3x, rescue up to 80% of the sessions from TCP connection drop and reduce CDN costs . PacketZoom’s Mobile Expresslane includes five key features
Throughput Optimization makes better transport layer decisions compared to how Web protocols operating over mobile networks work by default. We factor in mobile specific parameters such as network type, connection latency, throughput, packet loss and signal strength when transporting data and content.
Smart Cache PacketZoom includes in-app and edge-server caches that reduce the round trips to the CDN and origin servers and deliver content to the device faster. Both caches are fully controlled by your DevOps team and cache size as well as state can be adjusted in real time from anywhere. What’s more, because we focus just on mobile data, we are the perfect complement to your Web CDN.
Session Assurance controls both ends of the wireless communication, from the device to the first hop on the internet. This enables us to better handle session interruption and provide higher session assurance by minimizing disruption due to disconnects. Session Assurance provides uninterrupted mobile sessions for your mobile users on the same network or while traversing between access points and even different between networks.
Global Network Knowledge Engine stores last mile information about the performance of global mobile networks. With this advance knowledge mobile apps save time they would otherwise spend on network discovery. We are able to reduce or eliminate slow starts and requests for reconnects and retransmits. With PacketZoom intelligence mobile apps can maximize throughput on any mobile network.
Fail Forward PacketZoom Fail Forward design offers a robust layer of protection for customer data and user experience. The multicast session initialization process must be successful before the client stack starts handling any user requests. That means that if anything goes wrong user requests keep using the original network configuration (whether customer's servers or CDN).