Don’t let BYOD become BMNP (Bring Me New Problems)

The Bring Your Own Device (BYOD) trend presents enterprises with a number of significant challenges to go along with the potential benefits. Certainly there are positives associated with letting employees use their own computing devices to access enterprise resources, especially mobile technologies such as tablets and smart phones, including reduced costs and enhanced productivity.

 There are also some rather serious complications as well though, including security, manageability, and control. For the medical industry there are additional compliance issues to be aware of and enterprises must ensure that regulatory standards continue to be met. The medical community also has to contend with unique elements including compliance with insurance practices and acceptable levels of legal risk.

A successful BYOD implementation strategy will have to include a rigidly enforced acceptable use policy. Within regulated industries including medical I believe that in order to enforce a solid acceptable use policy enterprises must maintain complete management control of the device, enterprise data, and enterprise connectivity.

Enforcing enterprise standards on mobile devices generally begins using Mobile Device Management (MDM) and Mobile Application Management (MAM) systems. MDM/MAM systems enable the enterprise administrators to remotely configure and provision devices, install applications, troubleshoot, administer, and secure the device, and if required remotely wipe the device in accordance with established policies.

Additionally, MAM platforms enable the enterprise to implement version control, patch enforcement, and administrative access to the applications that are installed on the remote device. MDM and MAM are essential if mobile devices are going to be allowed to access and utilize enterprise systems and are an essential tool in enforcing acceptable use policies.

Because of the level of control needed to effectively implement an access control policy that satisfies the legal, regulatory, and best practices requirements of the medical community it may prove difficult to broadly implement BYOD with existing user devices. For this reason some organizations are adopting a hybrid model where the enterprise develops a list of acceptable devices and then offers them to employees at a discounted price in conjunction with the acceptable use policy.

One of the biggest, and most publicly known, challenge of BYOD is ensuring the security of data on the device and when transmitting to and from the enterprise. Effectively securing enterprise data includes encrypting data both at rest and in motion. Securing data at rest includes encrypting the data on the local storage medium so that if an unauthorized user attempts to read it there will be nothing useable. For mobile devices it is best to encrypt the entire device. Data at rest security must also incorporate user access controls including effective passwords and enforced logins to the device including screen timeouts and logouts for inactivity.

Securing data in motion includes the use of VPN connections to the enterprise and the use of access controls to ensure that only authorized users and applications are able to connect. Although most mobile devices support establishing VPNs, there are enterprise specific capabilities available that provide enhanced management and control of the connection and access. By enforcing secure connections and access control in conjunction with encrypting the data on the device, a strong level of overall data assurance can be provided.

BYOD can be a useful and effective element in an enterprise’s overall plan; there are a number of precautions that should be taken though to ensure successful implementation. Sound policies, effective enforcement, and good communication between enterprise administrators and end users will go a long way towards getting the most out of any BYOD effort.

MVO Optimization Daisy Chains

The concept of Daisy Chains as it relates to Circadence MVO technology involves the ability to connect to multiple destination networks from a single client and optimize the delivery of content from each of the connected networks individually.  The Daisy Chain allows the client to utilize the Circadence MVO optimized path between multiple MVO appliances across networks (or across subnets within a single network) until it reaches the nearest point of access.  This serves a dual purpose by extending the WAN optimization data path  as well as the Circadence Link Resilience capability as far as possible (or as far as is necessary).

One way to envision this concept is to have an organization with end users connecting to applications and retrieving content that are located at more than one location across the enterprise. Typically this could include content located in a branch office as well as a headquarters location and perhaps a datacenter. In typical WAN Optimization deployment the end user or client side implementation would have to have individual tunnels established from the end point to each head-end location separately.  With Daisy Chaining enabled in MVO there is a single head-end configured in the end user client or client-side endpoint, only the first link in the chain needs to be configured.

To illustrate the concept assume a user is connecting via laptop to their enterprise while on the road. The user has applications which connect to servers located within the enterprise and is requesting content that is located at multiple locations within the enterprise extranet. The user’s device has the MVO client installed and configured to connect to the MVO head-end installation located at their home office, which is a branch of the larger corporation. Further assume that the applications and content required are located at: the user’s brand office, at the company headquarters, at a company datacenter, and at a cloud hosted location. The configuration and workflow would be the following: 

We can make the following assumptions about the network connection:

1. The end user “A” is connecting to the public internet “B” via WiFi, Cellular Data, or wired Ethernet.
2. The end user “A” has/has not established a VPN connection to the Branch Office “C”.
3. The Branch Office “C” is connected by an IP network connection to Corp Headquarters “D”.
4. The Corp Headquarters “D” is connected by an IP network connection to a Corp Datacenter “W”. 
5. The Corp Datacenter is connected by an IP network connection to a private or public Cloud Service “E”.

The MVO client application installed on “A” is configured as a MVO Remote with a peer connection to the MVO Hub located at “C”. The Hub at “C” has a MVO Managed Traffic Definition “MTD” configured for applications and content located on network “C” (c.c.c.c). If “A” requests content located on the c.c.c.c network the MVO Remote client will divert the original IP request to the MVO process, which will then encode the original IP packets into the enhanced TMP and send the request via the TMP protocol to the MVO Hub located at “C”. The Hub at “C” will process the request from “A” and return the appropriate c.c.c.c content via the TMP connection from the MVO Hub process at “C” to the MVO Remote process at “A”. The MVO Remote process at “A” will then decode the TMP packets into the original IP and forward to the original requesting local client process.

The MVO instance located at “C” is configured as both a MVO Hub and a MVO Remote. The MVO Remote process is configured to connect to the MVO peer located at “D”. The Hub at “D” has a MVO Managed Traffic Definition “MTD” configured for applications and content located on network “D” (d.d.d.d). If “C” requests content located on the d.d.d.d network the MVO Remote process will divert the original IP request to the MVO process, which will then encode the original IP packets into the enhanced TMP and send the request via the TMP protocol to the MVO Hub located at “D”. The Hub at “D” will process the request from “C” and return the appropriate d.d.d.d content via the TMP connection from the MVO Hub process at “D” to the MVO Remote process at “C”. The MVO Remote process at “C” will then decode the TMP packets into the original IP and forward to the original requesting local client process.  Additionally, the MVO instance at “C” has been configured to support Daisy Chains. The Daisy Chain configuration allows the MVO Hub instance to internally forward IP packets destined for a network which has MTD rules applied at the same MVO instance’s Remote process from a distant MVO Hub. With Daisy Chains enabled, if “A” requests content located on the d.d.d.d network the MVO Remote client will divert the original IP request to the MVO process, which will then encode the original IP packets into the enhanced TMP and send the request via the TMP protocol to the MVO Hub located at “C”. The Hub at “C” will process the d.d.d.d request from “A” and forward the request for content from d.d.d.d to the MVO Remote process at “C”. The MVO Remote process at “C” will send the request via the TMP protocol to the MVO Hub located at “D”. The Hub at “D” will process the request from “A” and return the appropriate d.d.d.d content via the TMP connection from the MVO Hub process at “D” to the MVO Remote process at “C”. The Daisy Chain enabled MVO instance at “C” will then internally forward the d.d.d.d content from the “C” Remote process to the “C” Hub process for transport to “A”. The MVO Remote process at “A” will then decode the TMP packets into the original IP and forward to the original requesting local client process at “A”.

The MVO instance located at “D” is also configured as both a MVO Hub and a MVO Remote. The MVO Remote process is configured to connect to the MVO peer located at “W”. The Hub at “W” has MVO Managed Traffic Definition “MTD” configured for applications and content located on network “W” (w.w.w.w) and Cloud Service “E” (e.e.e.e). If “D” requests content located on the w.w.w.w or e.e.e.e network the MVO Remote process will divert the original IP request to the MVO process, which will then encode the original IP packets into the enhanced TMP and send the request via the TMP protocol to the MVO Hub located at “W”. (The process for content from either w.w.w.w or e.e.e.e is fundamentally similar so only w.w.w.w will be detailed) The Hub at “W” will process the request from “D” and return the appropriate w.w.w.w content via the TMP connection from the MVO Hub process at “W” to the MVO Remote process at “D”. The MVO Remote process at “D” will then decode the TMP packets into the original IP and forward to the original requesting local client process.  Additionally, the MVO instance at “D” and at “W” have been configured to support Daisy Chains. The Daisy Chain configuration allows the MVO Hub instance to internally forward IP packets destined for a network which has MTD rules applied at the same MVO instance’s Remote process from a distant MVO Hub. With Daisy Chains enabled, if “A” requests content located on the w.w.w.w network the MVO Remote client will divert the original IP request to the MVO process, which will then encode the original IP packets into the enhanced TMP and send the request via the TMP protocol to the MVO Hub located at “C”. The Hub at “C” will process the w.w.w.w request from “A” and forward the request for content from w.w.w.w to the MVO Remote process at “C”. The MVO Remote process at “C” will send the request via the TMP protocol to the MVO Hub located at “D”. The Hub at “D” will process the w.w.w.w request from “A” through “C” and forward the request for content from w.w.w.w to the MVO Remote process at “D”. The MVO Remote process at “D” will send the request via the TMP protocol to the MVO Hub located at “W”. The Hub at “W” will process the forwarded request from “A” and return the appropriate w.w.w.w content via the TMP connection from the MVO Hub process at “W” to the MVO Remote process at “D”. The Daisy Chain enabled MVO instance at “D” will then internally forward the w.w.w.w content from the “D” Remote process to the “D” Hub process for transport to “C”. The Daisy Chain enabled MVO instance at “C” will then internally forward the w.w.w.w content from the “C” Remote process to the “C” Hub process for transport to “A”. The MVO Remote process at “A” will then decode the TMP packets into the original IP and forward to the original requesting local client process at “A”.

Functionally the Daisy Chain process works as an inherent function of MVO being able to operate with both Frontend (Remote) and Backend (Hub) processes running simultaneously. In a network consisting of a MVO Remote “A”, first MVO Hub “B”, and second MVO Hub “C”: As traffic from a Frontend process at Remote “A” arrives at the Backend process of the Hub “B” if it does NOT meet a MTD rule being diverted by the “B” Hub’s Frontend process it is exited from the MVO application at that location. If the traffic from the Remote meets the definition of a MTD divert running on the Frontend process at the “B” Hub it is reprocessed and sent along to the upstream “C” Hub. The configuration is best approached in reverse, from the last link in the chain to the first remote client.

Imaging Economics Interview Q&A

What is it that WAN optimization products do?

WAN Optimization products such as Circadence’s MVO platform substantially increase the performance of applications which use the network. With Circadence MVO file transfers, including medical images, are much faster and their delivery is ensured. By implementing MVO WAN Optimization, it’s possible to increase transfer speeds by more than 300 percent. For example, using Circadence, one healthcare organization was able to reduce the time required to complete image transfers from almost four minutes down to 13 seconds.

MVO WAN optimization significantly prevents corrupt, incomplete or lost files transferred across the network. Increasing data integrity and reliability improves the quality of healthcare provided by medical imaging institutions and limits the number of resends that are typically required. Implementing optimization maximizes return on investment in bandwidth and decreases or eliminates the need for expensive infrastructure upgrades.

Can you give the bird’s eye view of Circadence MVO for Mobile in a health care setting?

Circadence MVO for Mobile provides full end-end optimization between applications and content. In the healthcare setting, this could include Hospitals; remote clinics; distributed call centers; remote offices; and, individual users on laptops, tablets and smartphones.  In healthcare, typical applications that MVO will be utilized for are EMR/EHR and image study transfers such as with PACS, where MVO facilitates fast and effective patient care and increases the provider’s capabilities. 

What sets Circadence MVO for Mobile apart from similar solutions?

Circadence MVO is currently the only WAN Optimization solution that supports MS Windows, Android, and Apple iPhone/iPads.  Circadence is the most innovative mobile optimization provider and offers the most deployment options available including cloud, hardware, software, VM, and 3^rd party integration with the MVO SDK. Circadence MVO also offers leading performance transferring all types of image studies and enables full optimization without caching or storing content or modifying it in any way.

Highlights:

- OEM integration with 3^rd party platforms and applications, such as PACS imaging systems;
- Broadest deployment capabilities, reducing infrastructure costs and accelerating ROI;
- Full support for all mobile platforms including Windows, Android, and Apple iOS;
- Optimizes all data dynamically in real-time, without caching or modifying;
- Circadence patented Link Resiliency maintains application session persistence;

In recent years, how has the emergence of mobile devices changed the health care environment, specifically the radiology department?
The emergence of mobile devices, specifically high performance tablets with high definition displays and strong graphics performance, has enabled radiology professionals to “untether” themselves from the imaging systems. Essentially, mobility enables practitioners to be closer to their patients, provide a higher level of care and greatly increase efficiency. As the capabilities of the mobile platform increase, the demands placed on the network infrastructure increase substantially. The size of image studies increase near exponentially as they increase in definition, making WAN Optimization essential for effective use. The capabilities mobility brings to radiology also are increasing rapidly and in many ways are creating positive changes in the dynamic between caregiver and patient. Mobile access to patient studies enables healthcare professionals to be closer to their patients, and to being the technology to the patient versus forcing the patient to come to the technology.

How can radiology practices utilize WAN optimization? What are some of the benefits?

WAN Optimization such as Circadence MVO is essential for delivering radiology studies across networks. The broad deployment options offered by Circadence enable radiology practices to implement optimization in ways that best suit their particular practices. Distributed radiology offices can use WAN Optimization to provide much higher performance transferring content between offices. Centralized radiology providers can dramatically increase the number of studies their radiologists are able to read, increasing revenue and decreasing costs. Mobile WAN Optimization enables practitioners to access even larger, high definition studies from wherever they happen to be, improving patient care and increasing access.  

Does the Circadence MVO for Mobile have to comply with HIPAA guidelines? If so, how is that achieved?

Circadence MVO can be a key component of an organization’s HIPAA compliance program. Under HIPAA, healthcare organizations must ensure that patients’ privacy is protected; this includes protecting confidential information. Unlike other WAN Optimization vendors, the Circadence MVO Optimization platform does not cache, store, or decrypt information sent across the network. Circadence MVO enables healthcare providers to implement the leading WAN Optimization platform across their organizations while maintaining compliance with current guidelines.

What are some of the difficulties when installing/utilizing the Circadence WAN optimization solution?

As with any fast changing landscape, there can be challenges as organizations adapt. The healthcare industry in particular is facing an extraordinary amount of change in the way that healthcare services are provided and accessed, with new capabilities being announced daily. For an industry as regulated as healthcare the challenges can be administrative and procedural as much, or more so, than technical. Additionally, the increasing focus on technology is forcing medical practitioners at all levels to become more familiar with systems, terminology, and practices that may be entirely new to them. As regulators, providers, and practitioners become more educated and comfortable with technology the pace of adoption is increasing and administrative barriers to adoption of emerging technologies are being removed. Circadence places an emphasis on making the MVO optimization platform as easy to implement and manage as possible, both technically and administratively, allowing providers to focus more on providing high quality services.

Mobile Usage

Mobile usage is rising dramatically, placing greater strain on networks and creating bandwidth and connectivity issues. Exacerbating this situation are the high demands mobile users place on networks.

With the increased popularity of smartphones, tablets and other mobile devices, the boundaries between work and personal are blurring. As a result, people are using mobile devices to check work email, review and work on documents and a host of other work-related functions.

 As more and more critical information is accessed outside of brick and mortar, wireless and broadband companies need to plot the best way to accommodate the spike in traffic. Enterprises must also be prepared to help their employees remain connected regardless of their location or device.

The rise of mobile

The number of mobile users has sharply increased in recent years. As of June 2011, according to CTIA, a non-profit organization supporting the wireless industry in the United States, there were 322.9 million wireless subscriber connections. This represents a 745 percent increase from five years ago, when there were 38.2 million wireless subscriber connections. There are seven billion connected devices worldwide and by 2025, it is predicted that number will have ballooned to 50 billion. 

Consumers rely on their phones and mobile devices for a wide variety of purposes such as listening to music, downloading apps, surfing the Internet and watching videos. More people are also using personal devices for work-related functions such as managing email and working on documents. Unlike texting or making a phone call, this usage places an incredible strain on networks, consuming large amounts of data.

The surge in data usage coupled with the rise in BYOD (Bring Your Own Device) threatens to overwhelm the infrastructure supporting mobile devices. As a result, some carriers have discontinued offering unlimited data usage offers. In the enterprise, companies are increasingly adopting WAN optimization to ensure they can quickly transmit and process information even in areas with low-quality or intermittent network connections.

Unfortunately, it is not feasible to physically expand the wireless infrastructure in the United States by for instance, building more cell phone towers. And the cost of doing so would be astronomical.

In this challenging environment, service providers want the ability to more efficiently utilize the bandwidth available. At the same time, consumers have grown accustomed to being able to use their phones for work and fun. The always-on worker armed with a laptop, tablet and phone is quickly becoming the norm. In response, enterprise organizations are also seeking a way to accommodate additional devices.

WAN optimization goes mobile

 WAN optimization, once reserved for military organizations looking to move critical information in the field, is gaining momentum in the enterprise and could play a critical role in helping alleviate mobile network overload. Loosely defined, WAN optimization is a collection of technologies and techniques used to maximize the efficiency of data flow across a wide area network. WAN optimization enables organizations to transmit information and gain access to critical applications faster.

 The enterprise is increasingly adopting WAN optimization as a method for transmitting information quickly and securely. For example, healthcare organizations using WAN optimization can quickly transmit images and patient data quickly regardless of network connections or bandwidth strength.

 For companies and organizations seeing an influx of mobile workers and personnel utilizing personal devices, mobile WAN optimization provides the same benefits as WAN optimization but to mobile devices. This enables organizations to embrace remote workers and mobile workers, confident that they connect regardless of their location. WAN optimization can also help alleviate pressure on existing networks. For example, carriers can provide the same level of service but use 1/6 of the infrastructure to deliver it.

Conclusion

As mobile devices continue to become more sophisticated and mobile device adoption continues to explode, pressures on the current networks will continue to mount. BYOD and the mobile worker are also creating issues for organizations and companies who want to ensure their employees are able to quickly and securely access the information they need to perform their duties regardless of their location.

In this atmosphere, it’s critical that carriers and organizations look for innovative ways to increase the effectiveness of their existing bandwidth.  If the current mobile adoption continues at the current pace, soon they’ll have no choice but to embrace new solutions to address the situation. By embracing new technologies and solutions such as mobile WAN optimization, organizations will able to ensure that the mobile workforce isn’t left out in the cold.

Cloud, Mobile, and why Network Optimization is essential

When discussing "Cloud Computing" and "Mobile Computing" it's starting to get difficult to have a discussion about one without in some way talking about the other. Also, I think they may turn out to be the endpoints of the same organism (we'll let the terminal equipment manufacturers and cloud providers sort out which is the head end and which is the...). Before getting too deep allow me to standardize on some definitions around the terms "Cloud" and "Mobile" for the purposes of this discussion, and take giant, complex, difficult concepts and boil them down to easily digested techno porridge:

"Cloud Computing" or just "Cloud": We'll go ahead and use the NIST definition here: Cloud computing is a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. -NIST.gov – Computer Security Division – Computer Security Resource Center". Csrc.nist.gov

"Mobile Computing":  Taking a computer and all necessary files and software out into the field. Definition courtesy of US Bureau of Land Management http://www.blm.gov/wo/st/en/prog/more/bea/Glossary.html#m

I'm intentionally using broad definitions of both Cloud and Mobile because that is exactly what our customers and partners are doing. What specifically a person means by either "Cloud" or "Mobile" is going to depend on a wide variety of factors including location, application, public or private sector, industry, role, etc. The above definitions do an admirable job of rolling the multitude of variants up into an easy generalization that captures the essence of each. They are also at a high enough level that the intrinsic tie between Cloud and Mobile should be readily apparent. We can highlight the synergy by reducing the definitions one step further:

"Cloud" : Easy, on-demand access to applications and content hosted somewhere else.
"Mobile": Everything you need to run applications and look at content wherever you are.

A match made in heaven. And a headache in the making if ever there was one. Although it's easy to see where Cloud Computing and Mobile are closely aligned, some may miss the remarkably important piece that's missing. If the apps and content are hosted somewhere else, and you're accessing them from wherever you are....HOW are you accessing them? Via a network of course. But, which network? Does it have enough bandwidth for your needs, is it all yours or shared, is it safe and secure, do you know anything about it at all? The network is an essential element for both Cloud and Mobile, neither will work without one, but is a little difficult to define well here. We'll call it the "network", now giving us:

"Cloud" : Easy, on-demand applications and content hosted somewhere else.
"Mobile": Using applications and looking at content wherever you are.
"Network": How Mobile things connect to Clouds.

The fantastic opportunities that Cloud and Mobile have to offer are only accessible if there is a network connecting them. The network must be sufficient to carry the content users are requesting, consistent enough for transactions to be completed, and assured enough for reliable connectivity and data delivery. Because we've already defined Cloud as being "somewhere else" but haven't said where, and we've defined Mobile as being "wherever you are" but not where or how, the actual characteristics of the network remain unknown. This are exactly the conditions that users face every day from wherever they are. The vast majority of users connecting to applications or content do not have a detailed knowledge of the network they are using to connect themselves to the computing platforms and content storage they are accessing. If those users are connecting from anywhere other than their workplace, they may know their connection only by the marketing brand delivering it: Verizon Wireless, WiFi by AT&T, Boingo, T-Mobile Hotspot. Clearly the network is the critical bridge and if the user can't provide actionable information related to the character and capabilities of the connection we must rely on platforms, applications, or content to provide it without user input. This is the principle reason why WAN Optimization technology is essential for Cloud Computing and Mobile, both require network connectivity in order to function and neither can rely on user input or single-sided configurations to ensure successful and efficient operation.

Circadence WAN Optimization for Mobile http://bit.ly/fjXYt4 and Cloud http://bit.ly/i7O0Oy

Some pictures of the new Circadence MVO WAN Optimization Client for Android

20x Gain in Application Througput with MVO for Android

Network characterizations and performance benchmarks running the Circadence MVO WAN Optimization Client for Android on the Motorola Xoom, using WiFi and Verizon 3G.
Summary:
Motorola Xoom Tablet on the Verizon network
WiFi Performance
Without MVO installed: 4.8Mb/s
With MVO Installed: 81.5Mb/s
3G Performance
Without MVO installed: 750Kb/s
With MVO Installed: 31.1Mb/s

Testing to: iPerf Server running on Windows 2003 hosted in commercial datacenter
Test Device Model: Xoom
Android Version: 3.0.1
Tested using iPerf v2.0.5 pthreads

WiFi:
The following data describe the link characteristics for the WiFi portion of the testing. This was tested with iperf using UDP streams sent at configured bandwidth levels:

Reported MSS/MTU, MSS Size 1292 bytes, MTU 1332 bytes
Link tested at 10Mb/s Bandwidth
WiFi is 802.11n

[ ID]   Interval           Transfer               Bandwidth     Jitter                Lost/Total Datagrams
[1900]  0.0- 5.0 sec       5.80 MBytes       9.74 Mbits/sec  2.481 ms              1547322226/ 4195 (3.7e+007%)
[1900]  5.0-10.0 sec       5.73 MBytes       9.61 Mbits/sec  2.652 ms               222/ 4309 (5.2%)
[1900]  10.0-15.0 sec      5.85 MBytes       9.82 Mbits/sec  1.999 ms               81/ 4255 (1.9%)
[1900]   15.0-20.0 sec     5.88 MBytes       9.86 Mbits/sec  1.525 ms               6/ 4199 (0.14%)
[1900]   20.0-25.0 sec     5.95 MBytes       9.99 Mbits/sec  2.361 ms               3/ 4250 (0.071%)
[1900]   25.0-30.0 sec     5.04 MBytes       10.1 Mbits/sec  1.753 ms               7/ 4316 (0.16%)
[1900]   30.0-35.0 sec     5.94 MBytes       9.97 Mbits/sec  2.220 ms               7/ 4247 (0.16%)
[1900]   35.0-40.0 sec     5.76 MBytes       9.66 Mbits/sec  1.495 ms               95/ 4203 (2.3%)
[1900]   40.0-45.0 sec     5.97 MBytes       10.0 Mbits/sec  1.852 ms               47/ 4302 (1.1%)
[1900]   45.0-50.0 sec     5.95 MBytes       9.98 Mbits/sec   1.531 ms               5/ 4249 (0.12%)
[1900]   50.0-55.0 sec     5.83 MBytes       9.79 Mbits/sec   1.925 ms               33/ 4194 (0.79%)
[1900]  0.0-60.0 sec       70.7 MBytes       9.88 Mbits/sec   2.003 ms               597/51003 (1.2%)


WiFi Performance Test Results

iperf test results over WiFi-WithOUT MVO installed:
[ ID] Interval       Transfer     Bandwidth
[1828]  0.0- 5.0 sec  1.18 MBytes  1.98 Mbits/sec
[1828]  5.0-10.0 sec  2.62 MBytes  4.39 Mbits/sec
[1828] 10.0-15.0 sec  3.33 MBytes  5.58 Mbits/sec
[1828] 15.0-20.0 sec  3.36 MBytes  5.64 Mbits/sec
[1828] 20.0-25.0 sec  3.38 MBytes  5.68 Mbits/sec
[1828] 25.0-30.0 sec  3.30 MBytes  5.53 Mbits/sec
[1828] 30.0-35.0 sec  3.22 MBytes  5.41 Mbits/sec
[1828] 35.0-40.0 sec  2.43 MBytes  4.08 Mbits/sec
[1828] 40.0-45.0 sec  2.50 MBytes  4.20 Mbits/sec
[1828] 45.0-50.0 sec  2.72 MBytes  4.56 Mbits/sec
[1828] 50.0-55.0 sec  3.12 MBytes  5.24 Mbits/sec
[1828] 55.0-60.0 sec  3.41 MBytes  5.72 Mbits/sec
[1828]  0.0-60.1 sec  34.6 MBytes  4.84 Mbits/sec

iperf test results over WiFi-With MVO installed and running, default configurations:
[ ID] Interval       Transfer     Bandwidth
[1832]  0.0- 5.0 sec  45.0 MBytes  75.6 Mbits/sec
[1832]  5.0-10.0 sec  54.6 MBytes  91.6 Mbits/sec
[1832] 10.0-15.0 sec  45.8 MBytes  76.9 Mbits/sec
[1832] 15.0-20.0 sec  42.4 MBytes  71.2 Mbits/sec
[1832] 20.0-25.0 sec  54.9 MBytes  92.2 Mbits/sec
[1832] 25.0-30.0 sec  44.0 MBytes  73.8 Mbits/sec
[1832] 30.0-35.0 sec  42.1 MBytes  70.6 Mbits/sec
[1832] 35.0-40.0 sec  55.9 MBytes  93.8 Mbits/sec
[1832] 40.0-45.0 sec  50.1 MBytes  84.0 Mbits/sec
[1832] 45.0-50.0 sec  47.3 MBytes  79.3 Mbits/sec
[1832] 50.0-55.0 sec  51.0 MBytes  85.5 Mbits/sec
[1832] 55.0-60.0 sec  51.4 MBytes  86.3 Mbits/sec
[1832]  0.0-60.1 sec   585 MBytes  81.5 Mbits/sec


3G:
The following data describe the link characteristics for the 3G portion of the testing. This was tested with iperf using UDP streams sent at configured bandwidth levels:

Reported MSS/MTU, MSS Size 1424 bytes, MTU 1500 bytes
Link tested at 5Mb/s Bandwidth
Verizon 3G
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams
[1900]  0.0- 5.0 sec   445 KBytes   729 Kbits/sec  32.780 ms 1510/ 1820 (83%)
[1900]  5.0-10.0 sec   422 KBytes   691 Kbits/sec  25.222 ms 1739/ 2033 (86%)
[1900]  0.0-11.0 sec   937 KBytes   696 Kbits/sec  34.851 ms 3600/ 4253 (85%)

Link tested at 1Mb/s Bandwidth
Verizon 3G
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams
[1900]  0.0- 5.0 sec   393 KBytes   644 Kbits/sec  15.512 ms  131/  405 (32%)
[1900]  5.0-10.0 sec   451 KBytes   739 Kbits/sec  13.384 ms  104/  418 (25%)
[1900]  0.0-10.4 sec   874 KBytes   690 Kbits/sec  13.179 ms  243/  852 (29%)

Link tested at 250Kb/s Bandwidth
3G is Verizon
[ ID] Interval       Transfer     Bandwidth       Jitter   Lost/Total Datagrams
[1900]  0.0- 5.0 sec   184 KBytes   301 Kbits/sec  20.309 ms    0/  128 (0%)
[1900]  0.0- 9.0 sec   307 KBytes   279 Kbits/sec  22.648 ms    0/  214 (0%)

3G Performance Test Results 

iperf test results over 3G-WithOUT MVO installed:
[ ID] Interval       Transfer     Bandwidth
[1852]  0.0- 5.0 sec   399 KBytes   654 Kbits/sec
[1852]  5.0-10.0 sec   455 KBytes   746 Kbits/sec
[1852] 10.0-15.0 sec   469 KBytes   768 Kbits/sec
[1852] 15.0-20.0 sec   407 KBytes   668 Kbits/sec
[1852] 20.0-25.0 sec   439 KBytes   720 Kbits/sec
[1852] 25.0-30.0 sec   508 KBytes   832 Kbits/sec
[1852] 30.0-35.0 sec   425 KBytes   696 Kbits/sec
[1852] 35.0-40.0 sec   502 KBytes   823 Kbits/sec
[1852] 40.0-45.0 sec   499 KBytes   818 Kbits/sec
[1852] 45.0-50.0 sec   465 KBytes   761 Kbits/sec
[1852] 50.0-55.0 sec   465 KBytes   761 Kbits/sec
[1852] 55.0-60.0 sec   449 KBytes   736 Kbits/sec
[1852]  0.0-61.5 sec  5.50 MBytes   750 Kbits/sec


iperf test results over 3G-With MVO installed and running, default configurations::
[ ID] Interval       Transfer     Bandwidth
[1860]  0.0- 5.0 sec  33.6 MBytes  56.4 Mbits/sec
[1860]  5.0-10.0 sec  3.41 MBytes  5.73 Mbits/sec
[1860] 10.0-15.0 sec  20.6 MBytes  34.5 Mbits/sec
[1860] 15.0-20.0 sec  22.1 MBytes  37.1 Mbits/sec
[1860] 20.0-25.0 sec  13.1 MBytes  22.1 Mbits/sec
[1860] 25.0-30.0 sec  25.3 MBytes  42.5 Mbits/sec
[1860] 30.0-35.0 sec  24.0 MBytes  40.3 Mbits/sec
[1860] 35.0-40.0 sec  12.5 MBytes  20.9 Mbits/sec
[1860] 40.0-45.0 sec  15.7 MBytes  26.4 Mbits/sec
[1860] 45.0-50.0 sec  16.2 MBytes  27.2 Mbits/sec
[1860] 50.0-55.0 sec  15.7 MBytes  26.3 Mbits/sec
[1860] 55.0-60.0 sec  14.9 MBytes  25.1 Mbits/sec
[1860]  0.0-61.6 sec   229 MBytes  31.1 Mbits/sec