WO2014044689A1

WO2014044689A1 - A method for connecting programs and/or applications to network interfaces

Info

Publication number: WO2014044689A1
Application number: PCT/EP2013/069313
Authority: WO
Inventors: Juan Manuel CAMBEIRO CUNS; Roberto GUERRERO GONZÁLEZ
Original assignee: Telefonica, S.A.
Priority date: 2012-09-24
Filing date: 2013-09-17
Publication date: 2014-03-27

Abstract

A Method for connecting programs and/or applications to network interfaces The method comprising in order to assign priorities to specific programs or applications, so that they are granted maximum priority when accessing to the internet/intranet and enable the application of connectivity selection policies on a "per application or program" basis: (a) redirecting said computerized system administrator said request for connectivity of said at least one program and/or application to a virtual network adapter; (b) distinguishing said virtual network adapter said network data traffic belonging to said at least one program and/or application; (c) said virtual network adapter applying a routing policy identifying said at least one program and/or application; (d) obtaining for said routing policy a specific network adapter, and (e) dynamically connecting said computerized system administrator said at least one program and/or application to said at least one network interface through said specific network adapter.

Description

A method for connecting programs and/or applications to network interfaces

Field of the art

The present invention generally relates to Internet traffic control and/ or monitoring and routing tools, and more particularly to a method for connecting programs and/or applications to network interfaces.

Prior State of the Art

Existing technologies related with the present invention are the following:

GoS Networks: "GoS 360" is software, executing on a device, able to monitor and apply policies to the incoming and outgoing traffic to/from a device. So, on any specified type of traffic (identified basically by type of protocol, IP destination address, port, etc.), and on any specified link (WiFi, Ethernet, etc.), this product is able to enforce different priorities, delays, jitter, restrictions, etc. from within the device. The software also provides a DPI (deep packet inspection) module which in some cases may be used for traffic type differentiation. It has as well a "GoS Manager", a centralized manager which is able to push these policies from a central place into any given number of devices.

Netbalancer: This software, executing on a device, is able to apply policies and restrictions on certain types of traffic. In addition to GoS networks abilities, it is able to apply these policies on specific processes running on the device, and not just on types of traffic. This is: their addition is to apply policies depending on the process which is originating the traffic.

OS Connection Managers: current Operating Systems (be it Windows OS for PCs or Android and iOS for smartphones) have a functionality that decides which kind of connectivity is to be provided, whenever an application or service running on the device requires data access.

MAPCON (Multi Access PDN-Connectivity) and IFOM (IP Flow Mobility): Part of the Release 10 of the 3GPP specification (3GPP TR 23.861 and 23.261 ), which defines the ability for devices to have simultaneously two open connections, one over a

3GPP type of connections (e.g. 3G) and other over a non 3GPP connections (e.g.

WiFi). The policies about what should go on which connection, are based on type of

APN (Access Point Name) and IP flow class.

Problems with existing solutions The problem with GoS Networks technology (and all related ones) is that policies cannot be applied for specific programs or applications. All these technologies apply policies on type of traffic and other technical parameters like "IP address, HTTP protocol, port 80, etc.", or try to identify the traffic type using the DPI module. With this approach, one is not usually able to specify that "I want high priority for downloads made from Firefox" or "I want a bandwidth guarantee on Call of Duty" or "I don't want Adobe update program to get more than 2 Mbits of my bandwidth connection". There are some technical difficulties to this in that several different programs or applications generate the same type of traffic (hence, they are indistinguishable in order to apply differential traffic policies, even when they might be coming from different programs e.g.: HTTP traffic originated from/directed to Firefox, Internet Explorer or Chrome navigators, same with different Voice over IP programs).

Netbalancer technology goes one step further than the previous one in being able to apply policies to traffic depending on the process which is generating it, and not just on the type of traffic. But again, this is useless if you just want to apply policies to some programs or applications, since programs and applications are generally executed from very many different processes, and the common device user is not able to relate the programs he is using, with the processes supporting it. Other times different and unrelated applications generate traffic through the same OS-related process (i.e. svchost.exe in Microsoft Windows environment) making it impossible to distinguish their traffic with this mechanism.

OS Connection Managers on the other hand, do not allow the possibility for the end user (or the service/application developer) to specify which connectivity is better for each application. On Windows PC platforms, when an application demands connectivity, the OS just gives the last connectivity that has been enabled, this is: it does not matter that the laptop might have an Ethernet port connected, WiFi enabled, and 3G; all the applications that require connectivity will go through the last connectivity that has been activated. This makes impossible for the end user to say "I want Windows Update to go only via Ethernet or WiFi, but not on 3G". On mobile handsets, applications just get connected to the connection that is enabled, this is: it is not possible to tell the handset that whenever I start application X, please switch to 3G data and abandon WiFi. In some cases user may change the OS routing tables, either through OS commands (i.e. "route" command in Microsoft Windows), or with the use of dedicated applications; in any case, routing is done based on IP addresses schema, and not on which application is requesting connectivity. And it is usually a complex process, not suitable at all for the average user.

Finally, MAPCON and IFOM standards go one step further in solving the problem mentioned in the previous point with the current connection managers. However, as was the case with GoS technologies and NetBalancer, these policies for traffic routing (assigning this traffic to that connectivity) are based again on type of traffic, and not per program or application. Again, based on these standards, it cannot be said "I want Windows Update to work only over Ethernet" or "I want Firefox to connect always via 3G".

Summary of the Invention

To address the above-discussed deficiencies of the prior state of the art, the present invention provides a method for connecting programs and/or applications to network interfaces.

As commonly used in the field, the method of the invention comprises:

receiving a computerized system administrator a request by at least one program and/or application running in a computer device with computing capacity and connectivity to at least one network interface;

receiving said computerized system administrator, network data traffic from said at least one program and/or application regarding said requested connectivity, and applying said computerized system administrator routing policies to said network data traffic or deciding which kind of connectivity is to be provided depending on the kind of program or application when said at least one program and/or application makes said request.

On contrary to the known proposals, the method of the invention in order to provide a particular kind of connectivity or prioritization granting access to said at least one program and/or application to said at least one network interface comprises in a characteristic manner, performing following steps:

(a) redirecting said computerized system administrator said request for connectivity of said at least one program and/or application to a virtual network adapter;

(b) distinguishing said virtual network adapter said network data traffic belonging to said at least one program and/or application;

(c) said virtual network adapter applying a Quality of Services (QoS) routing policy identifying said at least one program and/or application; (d) obtaining for said QoS routing policy a specific network adapter, and

(e) dynamically connecting said computerized system administrator said at least one program and/or application to said at least one network interface through said specific network adapter.

In an embodiment, the virtual network adapter maps the network data traffic with the at least one application originating it in order to perform said step b). Several mechanisms such as a file directory where said at least one application resides, registry information and/or installed application lists can be used for performing the mapping.

In another embodiment, step b) is performed by marking a plurality of IP frames and/or by using RAM heaps shared between processes.

The system administrator can select the QoS routing policy by identifying said at least one program and/or application through a graphic user interface (GUI). Then, the system administrator is able to establish per application policies such as priority, minimum bandwidth required for said at least one application and preferred network interfaces, among others.

Finally, in yet another embodiment step (e) is performed only when said at least one application is associated with an active connection. Brief Description of the Drawings

The previous and other advantages and features will be more fully understood from the following detailed description of embodiments, with reference to the attached, which must be considered in an illustrative and non-limiting manner, in which:

Figure 1 illustrates a block diagram representing the structure followed by the method of the present invention, according to an embodiment.

Detailed Description of Several Embodiments

Embodiments of the present invention propose a technical solution for Internet traffic control and/or a monitoring tool that is able to provide the ability to:

· Assign priorities to specific programs or applications, so that they are granted maximum priority when accessing to the Internet/Intranet.

• Enable the application of connectivity selection policies on a "per application or program" basis. Example: "Windows Update runs only over Ethernet" or "Firefox goes over 3G preferably". The final user devices which the invention is able to control may be any device with computing capacity and connectivity to at least one network interface: such as PCs, laptops, mobile devices, including mobile phones and tablets.

Control of how priority is assigned or connectivity selected is done by a system administrator. There are several possible scenarios:

• Individual PC scenario: the invention just controls one PC. The final user of this PC is the system administrator.

• Residential scenario: the invention is used to control all the PCs in a home network. One member of the family gets the role of system administrator, and is able to assign priorities and connectivity usage of all the rest of PCs at home.

• Business scenario: by the use of the invention, the PCs of a company are controlled. The systems and networks responsible in the organization is the system administrator.

Figure 1 show in an embodiment the detail technical description of the present invention, where related functionalities are enclosed within the dashed line box.

• Virtual Network Adapter: This virtual network interface acts as an umbrella for all the existing connectivity.

o When an application requires connectivity (e.g. access to the Internet), they will be redirected to this virtual network adapter, instead of letting the Operating System assign any direct interface (e.g. WiFi interface).

Several mechanisms have been tested for mapping traffic to the originating applications: process originating the traffic, file directory where the executable resides, registry information, installed applications lists, etc.

o When traffic goes through this virtual network adapter, it is marked so that it is clear which application or program is originating the traffic. Several mechanisms for marking have been tested: marking the IP frames, using RAM heaps shared between processes, etc. o Once the traffic has been identified, the appropriate routing policies are applied, and the traffic is redirected to the selected real network adapter.

For example, if Google Chrome traffic is to be sent through WiFi, when the Virtual Network Adapter identifies traffic coming from that application, it routes it to the WiFi network adapter.

• Application of per application QoS policies: thanks to the traffic marking, QoS enforcement software is now able to identify the application originating the traffic, and apply "per application" QoS policies. Example: if via configuration the system administrator has said that Firefox traffic is the most important, when traffic with the "Firefox" marking gets here, is treated with maximum priority, even if the rest of the traffic has to be pushed to the background, or even blocked.

• Configuration of per application policies: Through a proper Graphic User Interface (GUI), the system administrator will be able to establish per application policies, meaning: priority (high, medium, low and none), minimum bandwidth required, and preferred network interfaces. This preferences and policies will be translated into the proper traffic QoS and traffic routing policies that will be applied in the Virtual Network Adapter and the Application of per application QoS policies module.

In an embodiment of the present invention, a real prototype has been developed, in software for Windows 7 platform, in a laptop computer.

A list (non exhaustive) of the use cases supported by this prototype are as follows:

Use case 1 : different traffic priorities per originating application.

• Context: Two file downloads are started from different web browsers.

One of them (Firefox) is configured low priority (best effort) and the other browser (Google Chrome) is configured as high priority. Both browsers are configured to go through the same link (Ethernet).

• Use Case Flow: Download is started from Firefox (low priority). As there is no other download going on in the laptop, the download gets nearly all the available bandwidth. From Google Chrome another file download is started. As Chrome has been configured as high priority, this download gets nearly all available bandwidth, whilst the former download started from Firefox, is left with minimum or no bandwidth at all. When Google Chrome Download finishes, Firefox Download recovers again and uses the available bandwidth.

Use case 2: traffic routing policies per originating application.

• Context: From the configuration tool, Internet Explorer has been assigned to use exclusively to Ethernet link, Firefox to WiFi, and Chrome to 3G.

• Use Case Flow: By plugging and unplugging the different connectivities, it can be observed that only those web browsers associated with active connectivities have Access to the internet, while the others simply can't work. Example: The moment the USB 3G dongle is unplugged; Google Chrome is not able to have Access to the Internet, while the other browsers work properly (provided that Ethernet and WiFi are connected).

Case 3: simultaneous downloads an all available laptop links.

• Context: The same configuration was used as in use case 2, while all the connectivity in the laptop was kept enabled: Ethernet, WiFi and 3G.

• Use case Flow: It starts file downloads from the three different web browsers (Internet Explorer, Firefox and Chrome). Via network monitoring tools, it can be seen that the laptop is effectively downloading information on the three available links (Ethernet, WiFi and 3G), thus, using all available connectivity simultaneously.

Case 4: Improvement of user experience on an application (Skype).

• Context: Laptop A connected only to Ethernet link. Ethernet link is then limited to just 500 Kbit of download. Web browsers and Skype are configured with no special priority at all (best effort). Another common laptop (laptop B) participates in the use case, with Skype application installed, but no invention related software running on it.

• Use Case Flow:

o On laptop A a big size file download is started.

o An Skype Video Call is started from laptop A to laptop B

o It can be seen that the quality of the videocall is bad, with many frames lost, image freezing, and eventually the Skype software recommends performing a "voice only" call. Login to Skype account and videocall setup is perceived as very slow. o From the configuration tool in laptop A, Skype is set to maximum priority.

o A new Skype Video Cal is started from laptop A to laptop B. In this case, the experience is significantly improved: login and videocall setup are fast, the video is smooth, there are no image freezing, and the videocall goes on without interruptions or recommendation from Skype to go to a voice only call. In parallel, it can be seen that the download on laptop A, classified a low priority, has been almost "starved" to zero bandwidth. Advantages of the Invention:

The system administrator is able to specify how applications connect to Internet. For instance:

- he can say that Windows Update (or any other software update) should work only via Ethernet or WiFi, and not via 3G, in order not to get the 3G flat rate quota to be wasted on software updates.

- Another example: an end user can specify that, as he uses Firefox to connect to important places (banking services, corporate services, etc.), he wants Firefox to connect always via 3G, as it is considered more secure.

- In a corporate network, the administrator may decide to assign high bandwidth to corporate applications and just best effort for the other ones, improving business affectivity.

- In a residential environment, parents may decide to block or limit traffic from certain applications running in son's PC, in order they do not to fill completely their FTTH access.

The system administrator is able to specify which applications are important, and hence make sure that connectivity resources are dedicated to these applications, improving hence the final user experience (as shown in use case 4, section 3.2). As it is now, and without this invention, laptops and mobile devices generate a lot of "background traffic" originated in applications that the end user is not directly using, which is competing in equal priority with the traffic generated by the applications that the end user is really using, worsening his experience.

The end user can use simultaneously all the connectivity available on the laptop by the redirection of different applications to different links. This is a way to aggregate all the connectivity capacities available on the same device.

A person skilled in the art could introduce changes and modifications in the embodiments described without departing from the scope of the invention as it is defined in the attached claims. ACRONYMS

ADSL Asymmetric Digital Subscriber Line

UMTS Universal Mobile Telecommunication System

DPI Deep Packet Inspection

Claims

1. - A method for connecting programs and/or applications to network interfaces, comprising:

receiving a computerized system administrator a request by at least one program and/or application running in a computer device with computing capacity a connectivity to at least one network interface;

receiving said computerized system administrator, network data traffic from said at least one program and/or application regarding said requested connectivity, and applying said computerized system administrator routing policies to said network data traffic or deciding which kind of connectivity is to be provided depending on the kind of program or application when said at least one program and/or application makes said request,

said method being characterized in that it comprises in order to provide a particular kind of connectivity or prioritization granting access to said at least one program and/or application to said at least one network interface, performing following steps:

(c) said virtual network adapter applying a Quality of service (QoS) routing policy identifying said at least one program and/or application;

(d) obtaining for said QoS routing policy a specific network adapter, and

2. - A method according to claim 1 , characterized in that it comprises said virtual network adapter mapping the network data traffic with the at least one program and/or application originating it in order to perform said step b).

3.- A method according to claim 2, comprising performing said mapping by processing the originated network data traffic, a file directory where said at least one application resides, registry information and/or installed application lists.

4.- A method according to claim 1 , comprising performing said step b) by marking a plurality of IP frames and/or by using RAM heaps shared between processes.

5. - A method according to claim 1 , comprising said computerized system administrator selecting said QoS routing policy identifying said at least one application through a graphic user interface (GUI).

6. - A method according to claim 5, characterized in that it comprises selecting said QoS routing policy depending on a level of priority for said at least one application.

7. - A method according to claim 5, characterized in that it comprises selecting said QoS routing policy depending on a minimum bandwidth required for said at least one application.

8. - A method according to claim 5, characterized in that it comprises selecting said QoS routing policy depending on a preferred network interface for said at least one application.

9. - A method according to claim 1 , characterized in that it comprises performing said step (e) only when said at least one application is associated with an active connection.