Ethernovia Inc.

Cisco Technology, Inc.

Broadcom Corporation

Greenfield Networks, Inc.

Brian Arnold Petersen

Roy Thomas Myers, Jr

James P Rivers

Joseph Andonieh

Tom Quoc Wellbaum

Harish Ramamurthy Devanagondi

Poon-Kuen Leung

Hossein Sedarat

Ramin Shirani

Darren S Engelkemier

Stewart Findlater

David H Yen

Mark A Ross

Bernard N Daines

David Talaski

Harish P Belur

Richard John Heaton

Max Klaus Turner

Atul Prakash Agarwal

James R Rivers

Majid Torabi

Various embodiments described herein support or provide for rapid program launch, such as receiving a notification from a hardware unit; causing the hardware unit to load one or more working registers associated with the processor with the one or more parameters; launching the program that handles the notification based on the one or more parameters; generating one or more result values based on a launching of the program; and exporting the one or more result values to the hardware unit for processing.

Data management using rapid program launch

Various embodiments provide for reliable multicast network communication using network connections. According to some embodiments, a source network node sends data to a plurality of destination network nodes (e.g., members of a multicast group of network nodes) over a communications network by one or more multicast data units, where the multicast data units include a sequence number and are sent using (e.g., transported over) one or more network connections.

Reliable multicast network communication

Disclosed are systems, methods, and non-transitory computer-readable media for protocol independent data unit forwarding. A packet forwarding system receives a data unit comprising a header byte string via an input port. The packet forwarding system parses the data unit based on a header type determined based on the input port, yielding a parsing output describing the header byte string of the data unit. The packet forwarding system updates a metadata item associated with the data unit based on the parsing output and determines a packet forwarding instruction for forwarding the data unit to a destination based on the metadata item associated with the data unit. The packet forwarding system forwards the data unit to the destination based on the packet forwarding instruction and the metadata item associated with the data unit.

Protocol independent data unit forwarding

Various embodiments described herein support or provide for data communication using hardware serialization and deserialization functions, such as receiving one or more data packets from a device over a network; and using the data communication hardware to perform operations including: decapsulating the one or more data packets to retrieve a serialized byte string, deserializing the serialized byte string including converting the serialized byte string into one or more data structures, and storing the one or more data structures in a memory of the device.

Data processing and transmission using hardware serialization and deserialization functions

Various embodiments provide for cut-through data unit forwarding with early ingress processing of a data unit in a communications network, such as an Ethernet-based network. According to some embodiments, cut-through data unit forwarding is performed such that data unit processing is initiated by a receiving network device while the data unit is still underway from a transmitting network device.

Cut-through data forwarding with early ingress processing

Various embodiments described herein support or provide for data communication using hardware serialization and deserialization functions, such as identifying definition data that defines structured data for transmission from a first electronic device to a second electronic device; generating a description file based on the definition data and using a compiler to generate, based on the description file, a plurality of hardware parameters and to generate source code defining a class that incorporates the structured data.

Various embodiments described herein support or provide for data processing and data transmission using hardware serialization and hardware deserialization functions, such as receiving structured data from a software application, using the data communication hardware to perform operations including: serializing the structured data to generate a serialized byte string based on the one or more hardware parameters; generate one or more data packets based on the serialized byte string; appending one or more headers to the one or more data packets; and transmitting the one or more data packets to a device based on a plurality of network parameters.

Various embodiments described herein support or provide for reactive code execution, such as receiving a byte string that includes a data structure; determining that processing the byte string requires a routine that is handled by a processor capable of operating in a proactive mode or a reactive mode; determining that the value corresponds to a type of value; executing, by the processor operating in the reactive mode, an instruction that causes the processor to remain in the reactive mode of operation; and processing the element by the processor operating in the reactive mode.

Data management using reactive code execution

Various embodiments provide for a ring network, such as an Ethernet-based ring network, for communicating specified data types, such audio data types. A ring network of some embodiments can be used in such applications as data network communications between sensors (e.g., cameras, motion, radar, etc.) and computing equipment within vehicles (e.g., smart and autonomous cars).

Ring network for specified data type

Various embodiments described herein support or provide for data processing and transmission using hardware serialization and hardware deserialization functions, such as receiving a data packet from a second electronic device over a network; determining, by a data communication hardware, that the header indicates the payload data includes serialized data; deserializing, by the data communication hardware, the serialized data; and storing, by the data communication hardware, deserialized data in a memory of the first electronic device for further processing by a processor of the first electronic device.

Various embodiments described herein support or provide for low latency protection switching, such as detecting a failure in a network associated with a network topology; determining a node that is affected by the failure; identifying a recovery scenario that is preconfigured for the node in an event of the detected failure; setting a value for a protection mode identifier associated with the node; and determining an alternate data transmission path for each node in the group of nodes based on the protection mode identifier.

Low latency protection switching

According to one general aspect, a method may include receiving at least a portion of a packet of data by an ingress device. The method may include determining an egress device to receive the packet. In some embodiments, the method may include dividing the received portion of the packet into a plurality of segments. The method may include editing, for each segment, a header to include an address field that indicates the address of the egress device, wherein the header is associated with a current segment. The method may include, for each segment, editing the header to include a next link field that indicates a link that will be used to transmit the next segment of the packet. The method may also include transmitting the current segment and header to the egress device via the link indicated in the next link field of the header of a preceding segment.

Efficient switch fabric bandwidth distribution

According to an example embodiment, a method may include receiving a message, appending a header set to the message, and transmitting the message from an ingress port to an egress port of the network switching system based on the header set. In an example embodiment, the header set may include a variable number of headers, wherein one or more of the headers in the header set includes a next header field to identify a type of header following a current header in the header set. In an example embodiment, the packet may be segmented and transmitted across the switching system as a plurality of cells, where a cell destination address may be a portion (e.g., subset of bits) of the packet destination address.

Growing community of inventors

San Francisco, CA, United States of America

Brian Arnold Petersen