Patents by Inventor David Clear

David Clear has filed for patents to protect the following inventions. This listing includes patent applications that are pending as well as patents that have already been granted by the United States Patent and Trademark Office (USPTO).

  • Patent number: 11489773
    Abstract: Methods and devices for processing packets with reduced data stalls are provided. The method comprises: (a) receiving a packet comprising a header portion and a payload portion, wherein the header portion is used to generate a packet header vector; (b) producing a table result by performing packet match operations, wherein the table result is generated based at least in part on the packet header vector and data stored in a match table; (c) receiving, at a match processing unit, the table result and an address of a set of instructions associated with the match table; and (d) performing, by the match processing unit, one or more actions in response to the set of instructions until completion of the instructions, wherein the one or more actions comprise modifying the header portion, updating memory based data structure or initiating an event.
    Type: Grant
    Filed: November 5, 2018
    Date of Patent: November 1, 2022
    Assignee: Pensando Systems Inc.
    Inventors: Michael Brian Galles, David Clear
  • Publication number: 20200336425
    Abstract: Methods and devices for processing packets with reduced data stalls are provided. The method comprises: (a) receiving a packet comprising a header portion and a payload portion, wherein the header portion is used to generate a packet header vector; (b) producing a table result by performing packet match operations, wherein the table result is generated based at least in part on the packet header vector and data stored in a match table; (c) receiving, at a match processing unit, the table result and an address of a set of instructions associated with the match table; and (d) performing, by the match processing unit, one or more actions in response to the set of instructions until completion of the instructions, wherein the one or more actions comprise modifying the header portion, updating memory based data structure or initiating an event.
    Type: Application
    Filed: November 5, 2018
    Publication date: October 22, 2020
    Inventors: Michael Brian GALLES, David CLEAR
  • Publication number: 20160173600
    Abstract: A method is provided in one example embodiment and includes receiving at an interface controller associated with a host server and disposed between the host server and a network element a packet from a sender; processing the packet to identify a rewrite rule to be applied to the packet based on characteristics of the packet; applying the identified rewrite rule to the packet to generate a rewritten packet; and forwarding the rewritten packet toward a next hop. The processing may include classifying the packet, the classifying including identifying at least one of a type of traffic with which the packet is associated and an application with which the packet is associated. Additionally and/or alternatively, the processing may include performing a flow table lookup for the packet to identify a flow with which the packet is associated.
    Type: Application
    Filed: December 15, 2014
    Publication date: June 16, 2016
    Applicant: CISCO TECHNOLOGY, INC.
    Inventors: Michael B. Galles, David A. Clear
  • Publication number: 20020101868
    Abstract: A virtual local area network (VLAN) tunneling system includes an ingress edge switching node that adds VLAN encapsulation information to a packet even if the egress port is configured to act as an untagged 802.1Q port. The packet is tunneled via a label-switched path (LSP) according to a multiprotocol label switching (MPLS) protocol. Label values are used for identifying a next switching node in the LSP to which the packet is to be transmitted. At a penultimate switching node in the LSP, a current label value is replaced with a label value reserved for packets originating from a port associated with a VLAN. An egress switching node in the LSP receives the packet with the reserved label value and recognizes that VLAN information is embedded in the packet. The egress switching node extracts the embedded VLAN information as well as the original source and destination addresses, and processes the packet for transmitting to a final destination.
    Type: Application
    Filed: September 18, 2001
    Publication date: August 1, 2002
    Inventors: David Clear, Sudhir Cheruathur, Guy Erb
  • Publication number: 20020016856
    Abstract: A packet switching node has first and second forwarding engines interconnected over a first path dependent on an inspection engine and a second path independent of the inspection engine. The first forwarding engine identifies a first session in which an application port number is to be dynamically negotiated for a second session and directs the first session to the first path. The inspection engine monitors a dynamic application port number negotiation for the first session, determines a dynamic application port number for the second session, configures a service level for the second session on the forwarding engines and directs the second session to the second path. The first forwarding engine also identifies a third session in which an application port number is statically assigned and directs the third session to the second path.
    Type: Application
    Filed: May 18, 2001
    Publication date: February 7, 2002
    Inventors: Mathieu Tallegas, David Clear, Timothy S. Michels, Greg W. Davis
  • Publication number: 20010053150
    Abstract: A data communication switch includes a backplane and multiple packet switching controllers. At least one packet switching controller includes programmable application logic for generating application data for a packet. The application logic is contained in key builder and lookup table of an application engine. The key builder contains one or more schema programs for generating keys and key controls using classification information and header data of inbound packets. The schema programs can be loaded onto the key builder during fabrication of the packet switching controller or in field. The keys and key controls are used to lookup the application data from the lookup table.
    Type: Application
    Filed: January 8, 2001
    Publication date: December 20, 2001
    Inventors: David Clear, Greg Davis, Tim Michels, Sundara Ganesh, Mathieu Tallegas
  • Publication number: 20010048661
    Abstract: A router is capable of providing multi-protocol redundant router protocol support. The redundant router protocols supported by the router include Hot Standby Router Protocol (HSRP) and Virtual Router Redundancy Protocol (VRRP). The router is capable of supporting multiple groups of virtual routers for each of the redundant router protocols. The router receives a packet and checks for prefix matching of MAC address bits. If the prefix of MAC address matches predefined HSRP or VRRP pattern, the router formulates a key, and compares the key against VRRP/HSRP database. If the key matches, the router routes the packet using virtual router address.
    Type: Application
    Filed: March 23, 2001
    Publication date: December 6, 2001
    Inventors: David Clear, Tim Michels, Jim Cathey
  • Publication number: 20010046229
    Abstract: A switch includes one or more programmable packet switching controllers. The programmable packet switching controller has a real-time edit program construction engine. The edit program construction engine receives packet data, e.g., the header data, and disposition decisions generated by, for example, an application engine. The edit program construction engine uses the packet data and the disposition decisions to construct edit programs in real-time. The edit programs include a number of instructions for performing operations, such as COPY, DELETE, RECORD, PLAYBACK, INSERT and OVERWRITE, and are stored in an instruction RAM associated with an edit engine. The edit engine executes the instructions to modify inbound packets in order to transmit them as outbound packets.
    Type: Application
    Filed: January 8, 2001
    Publication date: November 29, 2001
    Inventors: David Clear, Greg Davis, Mike Helbling, Tim Michels, Mathieu Tallegas