Initiating peer-to-peer tunnels
View Patent ↗Initiating peer-to-peer tunnels between clients in a mobility domain. When initiated by the controller, the access nodes establish a peer-to-peer tunnel for suitable client traffic so as to bypass “slow” tunnels through the controller. Traffic through this “fast” tunnel may be initiated once established or traffic may be temporarily queued. This queue and release process may be bidirectional or unidirectional depending on the traffic. Completion of slow tunnel traffic may be sensed in a number of ways. Slow tunnel traffic may be timed out, and queued traffic released after a preset time since the last packet was sent through the slow tunnel. The identity of the last packet sent through the slow tunnel may be retained, and queued traffic released when an acknowledgement for that packet is received. A special packet may be sent through the slow tunnel and queued traffic released when an acknowledgement for that packet is received.
1. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel, comprising:
determining by a controller as to whether the first client and the second client are within the same mobility domain, the first client adapted to exchange digital traffic with the second client;
evaluating whether the digital traffic is eligible for peer-to-peer forwarding if the first client and the second client are in the same mobility domain;
sending traffic from the first client to the second client through the controller-terminated tunnel until the peer-to-peer tunnel is established upon determining by the controller that the digital traffic is eligible for peer-to-peer forwarding;
identifying traffic from the first client to the second client;
holding selected traffic for the second client in a queue;
determining when traffic from the first client to the second client through the controller-terminated tunnel has completed comprises signaling completion when a predetermined period of time has passed; and
releasing the queued traffic through the peer-to-peer tunnel when the completion is signaled.
2. The method of claim 1 where traffic from the first client to the second client not selected to be held in the queue is sent to the second client.
3. The method of claim 2 where traffic from the first client to the second client not selected to be held in the queue is sent to the second client through the peer-to-peer tunnel.
4. The method of claim 1 where the operations of identifying, holding in a queue, and releasing traffic are practiced by both first and second access nodes.
5. The method of claim 1 where the predetermined period of time is marked from the time the operation of determining when traffic through the controller-terminated tunnel has completed is called.
6. The method of claim 1 where the predetermined period of time is marked from the time a last packet was sent from the first client to the second client through the controller-terminated tunnel.
7. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel, comprising:
determining by a controller as to whether the first client and the second client are within the same mobility domain, the first client adapted to exchange digital traffic with the second client;
evaluating whether the digital traffic is eligible for peer-to-peer forwarding if the first client and the second client are in the same mobility domain;
sending traffic from the first client to the second client through the controller-terminated tunnel until the peer-to-peer tunnel is established upon determining by the controller that the digital traffic is eligible for peer-to-peer forwarding;
identifying traffic from the first client to the second client;
holding selected traffic for the second client in a queue;
determining when traffic from the first client to the second client through the controller-terminated tunnel has completed comprises:
sending a marked packet from the first client to the second client through the controller-terminated tunnel, and
signaling completion when an acknowledgement of the marked packet's arrival is received from the second client; and
releasing the queued traffic through the peer-to-peer tunnel when the completion is signaled.
8. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel, comprising:
determining by a controller as to whether the first client and the second client are within the same mobility domain, the first client adapted to exchange digital traffic with the second client;
evaluating whether the digital traffic is eligible for peer-to-peer forwarding if the first client and the second client are in the same mobility domain;
sending traffic from the first client to the second client through the controller-terminated tunnel until the peer-to-peer tunnel is established upon determining by the controller that the digital traffic is eligible for peer-to-peer forwarding;
identifying traffic from the first client to the second client;
holding selected traffic for the second client in a queue;
determining when traffic from the first client to the second client through the controller-terminated tunnel has completed comprises:
storing the identity of a last packet sent from the first client to the second client through the controller-terminated tunnel, and
signaling completion when an acknowledgement of the last packet's arrival is received from the second client; and
releasing the queued traffic through the peer-to-peer tunnel when the completion is signaled.
9. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel comprising:
determining by a controller if the peer-to-peer tunnel is to be established based on whether the first client and the second client are within the same mobility domain and whether the digital traffic is eligible for peer-to-peer forwarding;
deciding if the transition to the peer-to-peer tunnel should be delayed until traffic through the controller-terminated tunnel is complete;
sending traffic from the first client to the second client through the controller-terminated tunnel until the peer-to-peer tunnel is established;
if traffic need not be delayed until controller terminated tunnel traffic is complete, sending traffic through the peer-to-peer tunnel, otherwise:
identifying traffic from the first client to the second client, and
holding selected traffic for the second client in a queue,
determining when traffic from the first client to the second client through the controller-terminated tunnel has completed by signaling completion when a predetermined period of time has passed; and
releasing the queued traffic through the peer-to-peer tunnel when the completion is signaled.
10. The method of claim 9 where the predetermined period of time is marked from the time the operation of determining when traffic through the controller-terminated tunnel has completed is called.
11. The method of claim 9 where the predetermined period of time is marked from the time a last packet was sent from the first client to the second client through the controller-terminated tunnel.
12. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel comprising:
determining by a controller if the peer-to-peer tunnel is to be established based on whether the first client and the second client are within the same mobility domain and whether the digital traffic is eligible for peer-to-peer forwarding;
deciding if the transition to the peer-to-peer tunnel should be delayed until traffic through the controller-terminated tunnel is complete;
sending traffic from the first client to the second client through the controller-terminated tunnel until the peer-to-peer tunnel is established;
if traffic need not be delayed until controller terminated tunnel traffic is complete, sending traffic through the peer-to-peer tunnel, otherwise:
identifying traffic from the first client to the second client, and
holding selected traffic for the second client in a queue,
determining when traffic from the first client to the second client through the controller-terminated tunnel has completed comprises:
sending a marked packet from the first client to the second client through the controller-terminated tunnel, and
signaling completion when an acknowledgement of the marked packet's arrival is received from the second client;
releasing the queued traffic through the peer-to-peer tunnel when the completion is signaled.
13. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel comprising:
determining by a controller if the peer-to-peer tunnel is to be established based on whether the first client and the second client are within the same mobility domain and whether the digital traffic is eligible for peer-to-peer forwarding;
deciding if the transition to the peer-to-peer tunnel should be delayed until traffic through the controller-terminated tunnel is complete;
sending traffic from the first client to the second client through the controller-terminated tunnel until the peer-to-peer tunnel is established;
if traffic need not be delayed until controller terminated tunnel traffic is complete, sending traffic through the peer-to-peer tunnel, otherwise:
identifying traffic from the first client to the second client, and
holding selected traffic for the second client in a queue,
determining when traffic from the first client to the second client through the controller-terminated tunnel has completed, comprises:
storing the identity of a last packet sent from the first client to the second client through the controller-terminated tunnel, and
signaling completion when an acknowledgement of the last packet's arrival is received from the second client; and
releasing the queued traffic through the peer-to-peer tunnel when the completion is signaled.
14. A method of transitioning digital traffic from a first client in communication with a first access node to a second client in communication with a second access node from a controller-terminated tunnel to a peer-to-peer tunnel, comprising:
determining by a controller if the peer-to-peer tunnel is to be established based on whether the first client and the second client are within the same mobility domain and whether the digital traffic is eligible for peer-to-peer forwarding;
establishing the peer-to-peer tunnel if the first client and the second client are from the same mobility domain and the digital traffic is eligible for peer-to-peer forwarding;
determining if the transition to the peer-to-peer tunnel should be delayed until an event has occurred, the event being one of (i) expiration of a predetermined period of time, or (ii) receiving an acknowledgement signal for a specific packet sent through the controller-terminated tunnel;
storing selected traffic for the second client in a queue if the transition to the peer-to-peer tunnel is to be delayed and releasing the queued traffic through the peer-to-peer tunnel after occurrence of the event.
15. The method of claim 14 where the event indicates completion of the controller-terminated tunnel.