Multicast forwarding methods and apparatuses across autonomous systems
US-2024275714-A1 · Aug 15, 2024 · US
US11848866B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11848866-B2 |
| Application number | US-202217725604-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 21, 2022 |
| Priority date | May 28, 2014 |
| Publication date | Dec 19, 2023 |
| Grant date | Dec 19, 2023 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods are described for effectively managing and maintaining a communication network by monitoring communications to detect a loop condition, and effectively route the communication to one or more destinations known to reduce or eliminate the occurrence of a looping condition.
Opening claim text (preview).
The invention claimed is: 1. A method comprising: receiving, by a computing device, information indicating that a pair of an originating address and a destination address is associated with a prior communication that resulted in a looping condition; receiving, by the computing device, a new communication request associated with the pair; and causing, by the computing device and based on the information indicating that the pair is associated with the prior communication that resulted in the looping condition, suppression of the new communication request or subsequent communication requests associated with the pair. 2. The method of claim 1 , further comprising storing information indicating a type of looping condition between a first address and a geographic region, and using the stored information to process a different communication request involving the first address and an address in the geographic region. 3. The method of claim 1 , wherein the causing comprises causing suppression of a first subset of future communication requests involving the pair, and permitting a second subset of the future communication requests involving the pair. 4. The method of claim 1 , further comprising; changing a timer limit, or a counter limit, associated with a rule defining a first type of looping condition; and using the changed timer limit or counter limit to process a future communication request. 5. The method of claim 1 , wherein the causing suppression of the new communication request comprises: modifying a header of the new communication request to include a data field comprising a looping identifier indicating that the new communication request was sent by a looping customer; and routing, based on the looping identifier, the new communication request. 6. The method of claim 1 , wherein the causing suppression of the new communication request comprises rejecting the new communication request. 7. The method of claim 1 , further comprising determining that the originating address is associated with one or more looping customers, wherein the causing suppression of the new communication request comprises determining a route to the destination address via another computing device not associated with the one or more looping customers. 8. A method comprising: receiving, by a computing device and via a network, a communication request addressed to a destination address; determining, by the computing device, that a quantity of instances the communication request was routed through a node on the network satisfies a threshold; after the determining that the quantity of instances satisfies the threshold: causing suppression of the received communication request; and adding the destination address to a list of addresses associated with looping conditions; and using the list of addresses to process one or more subsequent communication requests. 9. The method of claim 8 , wherein the causing suppression is further based on a determination that the received communication request was received as a result of a looping condition. 10. The method of claim 8 , wherein the causing suppression is further based on a determination that an originating address, associated with the received communication request, is associated with one or more looping customers. 11. The method of claim 8 , wherein the causing suppression is further based on a determination that a frequency of communication requests, originating from an originating address associated with the received communication request and addressed for the destination address, satisfies a threshold. 12. The method of claim 8 , wherein the causing suppression of the received communication request comprises: modifying a header of the received communication request to include a data field comprising a looping identifier indicating that the received communication request was sent by a looping customer; and routing, based on the looping identifier, the received communication request. 13. The method of claim 8 , wherein the causing suppression of the received communication request comprises rejecting the received communication request. 14. The method of claim 8 , wherein the causing suppression is further based on a determination that an originating address, associated with the received communication request, is associated with one or more looping customers, and wherein the causing suppression of the received communication request comprises determining a route to the destination address via another computing device not associated with the one or more looping customers. 15. A method comprising: receiving, by a computing device and via a network, a communication request from an originating address; determining, by the computing device, that a quantity of instances the communication request was routed through a node on the network satisfies a threshold; after the determining that the quantity of instances satisfies the threshold: causing suppression of the received communication request; and adding the originating address to a list of addresses associated with looping conditions; and using the list of addresses to process one or more subsequent communication requests. 16. The method of claim 15 , wherein the causing suppression is further based on a determinization that the received communication request was received as a result of a looping condition. 17. The method of claim 15 , wherein the causing suppression is further based on a determination that the originating address is associated with one or more looping customers. 18. The method of claim 15 , wherein the causing suppression is further based on a determination that a frequency of communication requests, originating from the originating address, satisfies a threshold. 19. The method of claim 15 , wherein the causing suppression of the received communication request comprises: modifying a header of the received communication request to include a data field comprising a looping identifier indicating that the received communication request was sent by a looping customer; and routing, based on the looping identifier, the received communication request. 20. The method of claim 15 , wherein the causing suppression of the received communication request comprises rejecting the received communication request.
Address table lookup; Address filtering · CPC title
Loop-free operations · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.