Network interface routing using computational context

• US 7,821,985 B2
• Filed: 03/13/2006
• Issued: 10/26/2010
• Est. Priority Date: 03/13/2006
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Manousek, Wolfgang, Salmre, Ivo W., Van Megen, Friedrich
• Primary Examiner(s): Jagannathan; Melanie
• Application Number:
  US11/373,954
• Publication Number:
  US 20070211690A1
• Time in Patent Office: 1,688 Days
• Field of Search: 370/351, 709/107, 709/102, 709/100, 709/5, 709/10
• US Class Current: 370/328
• CPC Class Codes: H04L 12/5692 Selection among different networks
• CPC Class Codes: H04W 28/18 Negotiating wireless communication parameters

Abstract

Knowledge of the computational context of a computer operating environment, for example, awareness of process threads, is used to route IP traffic in the presence of multiple active network connections. An additional protocol may be added to the network layer of an operating system in order to map certain computational contexts to particular network interfaces. Any process with identification parameters associated with a mapped computational context requesting data transfer via a communication network is bound to the network interface previously associated with the computational context rather than an alternate network interface that otherwise might be the default. Further, process threads created by a parent process thread may be caused to inherit the computational context of the parent thread in order to assign traffic to the same network interface. This routing framework may have particular application with respect to multihomed host devices, for example, mobile computing devices.

Claims

1. A method for routing data to a physical communication network interface comprising:

receiving a request to transmit data from an application executing a programmatic thread on a computing device having a plurality of physical communication network interfaces for transmitting the data over different communication networks, wherein the request is received at a network layer of the computing device that supports explicit socket bindings to specific physical communication network interfaces;

monitoring the request at one or more layered protocol drivers implemented by the networking layer for an explicit socket binding to a specific physical communication network interface;

upon determining that the request is without an explicit socket binding to a specific physical communication network interface, identifying a computational context that is associated with the data and relevant for subsequent network operations based on the executing programmatic thread;

registering the computational context with a routing interface of the network layer exposed by the one or more layered protocol drivers, the computational context registered by the programmatic thread using a thread identification parameter of the programmatic thread;

associating the computational context registered by the programmatic thread with a particular physical communication network interface in a mapping table of the routing interface;

receiving the data to transmit from the programmatic thread; and

routing the data to the particular physical communication network interface of the computing device for transmission over a communication network based upon the computational context registered by the programmatic thread with the routing interface.

2. The method of claim 1, further comprising transmitting the data via the particular physical communication network interface.

3. The method of claim 1, wherein the routing operation further comprises mapping the computational context to the particular network interface.

4. The method of claim 1, further comprising:

instantiating a communication socket;

associating the communication socket with the computational context; and

binding the communication socket to the particular physical communication network interface.

5. The method of claim 1, wherein the computational context comprises an extensible set of computational contexts.

6. A computer-readable storage medium having computer-executable instructions performing a computer process implementing the method of claim 1.

20. The method of claim 1 further comprising

receiving subsequent data associated with the computational context;

and

routing the subsequent data to the particular physical communication network interface based upon the computational context registered by the programmatic thread with the routing interface.

7. A method for routing data in a computing device having a plurality of physical communication network interfaces for transmitting the data over different communication networks, the method comprising:

registering computational contexts relevant for subsequent network operations with a routing interface of a network layer of the computing device, wherein;

the network layer supports explicit socket bindings to specific physical communication network interfaces,

the routing interface is exposed by one or more layered protocol drivers implemented by the network layer, and

the computational contexts are identified based on programmatic threads executed by the computing device and registered by the programmatic threads using thread identification parameters;

associating particular computational contexts registered by the programmatic threads with particular physical communication network interfaces in a mapping table of the routing interface;

receiving a request to transmit data from a process thread executing on the computing device;

monitoring the request at the one or more layered protocol drivers implemented by the networking layer for an explicit socket binding to a specific physical communication network interface;

upon determining that the request is without an explicit socket binding to a specific physical communication network interface, identifying a computational context associated with the data based on the executing process thread; and

making a routing decision for transmission of the data through one of the plurality of physical communication network interfaces of the computing device based upon the computational context associated with the data and the computational contexts registered by the one or more programmatic threads with the routing interface.

8. The method of claim 7 further comprising:

accessing the mapping table of the routing interface to determine the one of the plurality of physical communication network interfaces of the computing device for routing the transmission of the data.

9. The method of claim 7, wherein the computational context associated with the data comprises one or more of process thread identification, transaction identification, fiber identification, a time stamp, present processor load, and network cost difference.

10. The method of claim 7, wherein the process thread further creates a child process thread, and the method further comprises:

associating the computational context of the process thread with the child process thread; and

making a routing decision for transmission of additional data generated by the child process thread through the one of the plurality of physical communication network interfaces based upon the computational context of the process thread.

11. The method of claim 7, wherein the computational context comprises an extensible set of computational contexts.

12. A computer-readable storage medium having computer-executable instructions performing a computer process implementing the method of claim 7.

13. A method of making network interface routing decisions in a computing device having multiple physical communication network interfaces for transmitting data over different communication networks, the method comprising:

receiving a request to transmit data from an application process executing on the computing device at a network layer of the computing device, the network layer supporting explicit socket bindings to specific physical communication network interfaces;

monitoring the request at one or more layered protocol drivers implemented by the networking layer for an explicit socket binding to a specific physical communication network interface;

upon determining that the request is without an explicit socket binding to a specific physical communication network interface, identifying a computational context that is associated with the data and relevant for subsequent network operations based on a parameter presented to the networking layer as part of the application process;

mapping the parameter to a particular physical communication network interface in a routing interface exposed by one or more layered protocol drivers implemented by the networking layer to create a mapped relationship;

registering the mapped relationship with the routing interface of the network layer by the application process using a thread identifier of the application process;

storing the mapped relationship in a mapping table of the routing interface for associating the computational context with the particular physical communication network interface;

associating the parameter with data sent from the application process for transmission;

comparing the parameter associated with the data to the mapped relationship registered by the programmatic thread with the routing interface; and

routing the data to the particular physical communication network interface to which the parameter is mapped.

14. The method of claim 13 further comprising:

creating a communication socket;

associating the communication socket with the computational context; and

binding the communication socket to the particular physical communication network interface.

15. The method of claim 13, further comprising;

bypassing an existing default routing table;

accessing the mapped relationship from the mapping table of the routing interface to determine whether the computational context identified by the parameter is valid;

returning binding information from the routing interface for sending the data associated with the parameter through the particular physical communication network interface when the computational context identified by the parameter is valid; and

performing a routing table lookup through the existing default routing table when the computational context identified by the parameter is not valid.

16. The method of claim 13, wherein the computational context comprises one or more of process thread identification, transaction identification, fiber identification, a time stamp, present processor load, and network cost difference.

17. The method of claim 13, wherein the parameter comprises an extensible set of computational contexts.

18. The method of claim 13 further comprising

creating a child application process from the application process;

and

inheriting the mapped relationship to the child application process, wherein

the parameter is further associated with additional data sent from the child application process.

19. A computer-readable storage medium having computer-executable instructions performing a computer process implementing the method of claim 13.