Systems and methods for managing traffic within a peer-to-peer network
AssigneePanasonic Electric Works Co., Ltd.
InventorsDevon S. Sumner, W. Bryant Eastham
Life of this patent
Estimating the term…
Abstract
In a peer-to-peer network, one or more congestion events are defined that imply congestion on the network. In addition, one or more non-congestion events are defined that imply a lack of congestion on the network. When a node detects the occurrence of one or more of the defined congestion events, the node increases the spacing of connectionless protocol (e.g., UDP) packets that are sent by the node. When a node detects the occurrence of one or more of the defined non-congestion events, the node decreases the spacing of connectionless protocol packets that are sent by the node.
Claims19
A method for managing traffic within a peer-to-peer network, the method being implemented by a node within the peer-to-peer network, the method comprising:
- defining one or more congestion events that imply congestion on the peer-to-peer network, the one or more congestion events being defined to include either sending or receiving a multicast request;
- defining one or more non-congestion events that imply a lack of congestion on the peer-to-peer network, the one or more non-congestion events being defined to include either sending or receiving a multicast request;
- receiving a multicast request and a responder list that is associated with the multicast request, wherein the multicast request is a request for data or a request for a service;
- determining whether the node provides the data or the service;
- sending a response if the node provides the data or the service and if the node is not on the responder list and not sending a response if the node does not provide the data or the service or if the node is on the responder list;
- increasing spacing of connectionless protocol packets that are sent by the node in response to detecting one or more of the defined congestion events;
- and
- decreasing the spacing of connectionless protocol packets that are sent by the node in response to detecting one or more of the defined non-congestion events.
A node in a peer-to-peer network that is configured for managing traffic within the network, the node comprising:
- a processor;
- memory in electronic communication with the processor;
- instructions stored in the memory, the instructions being executable to:
- define one or more congestion events that imply congestion on the peer-to-peer network, the one or more congestion events being defined to include either sending or receiving a multicast request;
- define one or more non-congestion events that imply a lack of congestion on the peer-to-peer network, the one or more non-congestion events being defined to include either sending or receiving a multicast request;
- receive a multicast request and a responder list that is associated with the multicast request, wherein the multicast request is a request for data or a request for a service;
- determine whether the node provides the data or the service;
- send a response if the node provides the data or the service and if the node is not on the responder list and not send a response if the node does not provide the data or the service or if the node is on the responder list;
- increase spacing of packets that are sent by the node according to a connectionless protocol in response to detecting one or more of the defined congestion events;
- and
- decrease the spacing of packets that are sent by the node according to the connectionless protocol in response to detecting one or more of the defined non-congestion events.
A computer-readable medium comprising executable instructions for managing traffic within the network, the instructions being executable to:
- define one or more congestion events that imply congestion on the peer-to-peer network, the one or more congestion events being defined to include either sending or receiving a multicast request;
- define one or more non-congestion events that imply a lack of congestion on the peer-to-peer network, the one or more non-congestion events being defined to include either sending or receiving a multicast request;
- receiving a multicast request and a responder list that is associated with the multicast request, wherein the multicast request is a request for data or a request for a service;
- determining whether the node provides the data or the service;
- sending a response if the node provides the data or the service and if the node is not on the responder list and not sending a response if the node does not provide the data or the service or if the node is on the responder list;
- increase spacing of packets that are sent by the node according to a connectionless protocol in response to detecting one or more of the defined congestion events;
- and
- decrease the spacing of packets that are sent by the node according to the connectionless protocol in response to detecting one or more of the defined non-congestion events.
Dependencies are inferred from the claim text.