Eliminating data traffic redirection in scalable clusters

US2018248805A1 · US · A1

Patent metadata
FieldValue
Publication numberUS-2018248805-A1
Application numberUS-201815967423-A
CountryUS
Kind codeA1
Filing dateApr 30, 2018
Priority dateApr 24, 2014
Publication dateAug 30, 2018
Grant date

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Provided are methods and systems for eliminating a redirection of data traffic in a cluster. An example method may include receiving, by one or more nodes of the cluster, a data packet associated with a service session. The method may include determining, by the node, that the data packet is directed to a further node in the cluster. The method may further include, in response to the determination, acquiring, by the node, a session context associated with the service session. Acquiring the session context may include sending, by the node, a request for the session context to the further node and receiving the session context from the further node. The method may further include processing, by the one or more nodes, the data packet based on the session context.

First claim

Opening claim text (preview).

What is claimed is: 1 . A system for eliminating a redirection of data traffic, the system comprising: a cluster comprising one or more nodes, the one or more nodes being configured to: receive a data packet associated with a service session; determine that the data packet is directed to a further node in the cluster; and in response to the determination: acquire a session context associated with the service session; and process the data packet based on the session context. 2 . The system of claim 1 , wherein a first time required to acquire the session context is less than a second time required to redirect the data packet to the further node. 3 . The system of claim 1 , wherein the one or more nodes are further configured to store the session context in a dedicated memory. 4 . The system of claim 3 , further comprising a control plane configured to acquire the session context from the one or more nodes to obtain a plurality of session contexts of service sessions. 5 . The system of claim 4 , wherein the one or more nodes are configured to acquire a further session context by sending a request for the further session context to the control plane. 6 . The system of claim 4 , wherein the control plane is configured to synchronize one or more session contexts from the plurality of session contexts with the session context stored in the one or more nodes in the cluster. 7 . The system of claim 6 , wherein prior to synchronizing the one or more session contexts, the control plane selects the one or more session contexts from the plurality of session contexts based on priorities of the service sessions. 8 . The system of claim 7 , wherein the priorities of the service sessions are based on latency requirements for the service sessions. 9 . The system of claim 1 , wherein the one or more nodes are further configured to: receive a further packet of a further service session; generate a further session context associated with the further service session; and send the further session context to one or more further nodes of the cluster. 10 . The system of claim 1 , wherein the one or more nodes are configured to: send a request for the session context to the further node; and receive the session context from the further node. 11 . A method for eliminating a redirection of data traffic in a cluster, the method comprising: receiving, by one or more nodes of the cluster, a data packet associated with a service session; determining, by the one or more nodes, that the data packet is directed to a further node in the cluster; and in response to the determination: acquiring, by the one or more nodes, a session context associated with the service session; and processing, by the one or more nodes, the data packet based on the session context. 12 . The method of claim 11 , wherein a first time required for acquiring the session context is less than a second time required to redirect the data packet to the further node. 13 . The method of claim 11 , further comprising storing, by the one or more nodes, the session context in a dedicated memory. 14 . The method of claim 13 , further comprising acquiring, by a control plane, the session context from the one or more nodes to obtain a plurality of session contexts of service sessions. 15 . The method of claim 14 , further comprising acquiring, by the one or more nodes, a further session context by sending a request for the further session context to the control plane. 16 . The method of claim 14 , further comprising: selecting, by the control plane, one or more session contexts from the plurality of session contexts based on priorities of the service sessions; and synchronizing, by the control plane, the one or more session contexts from the plurality of session contexts with the session context stored in the one or more nodes of the cluster. 17 . The system of claim 16 , wherein the priority of the one or more service sessions is based on latency requirements for the service sessions. 18 . The method of claim 11 , wherein the acquiring the session context includes: sending, by the one or more nodes, a request for the session context to the further node; and receiving, by the one or more nodes, the session context from the further node. 19 . The method of claim 11 , further comprising: receiving, by the one or more nodes, a further packet of a further service session; generating, by the one or more nodes, a further session context associated with the further service session; and sending, by the one or more nodes, the further session context to one or more further nodes of the cluster. 20 . A non-transitory computer-readable medium having embodied thereon a program, the program providing instructions for a method for eliminating a redirection of data traffic in a cluster, the method comprising: receiving, by one or more nodes of the cluster, a data packet associated with a service session; determining, by the one or more nodes, that the data packet is directed to a further node in the cluster; and in response to the determination: acquiring, by the one or more nodes, a session context associated with the service session; and processing, by the one or more nodes, the data packet based on the session context.

Assignees

Inventors

Classifications

  • Traffic policing · CPC title

  • H04L47/24Primary

    Traffic characterised by specific attributes, e.g. priority or QoS · CPC title

  • Real time traffic · CPC title

  • by balancing the load, e.g. traffic engineering · CPC title

  • QOS or priority aware · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US2018248805A1 cover?
Provided are methods and systems for eliminating a redirection of data traffic in a cluster. An example method may include receiving, by one or more nodes of the cluster, a data packet associated with a service session. The method may include determining, by the node, that the data packet is directed to a further node in the cluster. The method may further include, in response to the determinat…
Who is the assignee on this patent?
A10 Networks Inc
What technology area does this patent fall under?
Primary CPC classification H04L47/24. Mapped technology areas include Electricity.
When was this patent published?
Publication date Thu Aug 30 2018 00:00:00 GMT+0000 (Coordinated Universal Time) (A1). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 3 related publications on this page (citations in our corpus or others sharing the same primary CPC).