Juniper Networks, Inc.

Mark Bryers

Nazar A Zaidi

Abbas Rashid

Elango Ganesan

Michael Freed

Ramesh Panwar

Robert G Hathaway

Frederick R Gruner

Fred Gruner

Yen C Lee

Sankar Ramanoorthi

John Phillips

Yuhong Zhou

Gregory G Spurrier

David T Hass

Ricardo Ramirez

Mark Vilas

Chau Anh Ngoc Nguyen

Chau Ahn Ngoc Nguyen

A network content service apparatus includes a set of compute elements adapted to perform a set of network services; and a switching fabric coupling compute elements in said set of compute elements. The set of network services includes firewall protection, Network Address Translation, Internet Protocol forwarding, bandwidth management, Secure Sockets Layer operations, Web caching, Web switching, and virtual private networking. Code operable on the compute elements enables the network services, and the compute elements are provided on blades which further include at least one input/output port.

Content service aggregation system

A cross-bar switch includes a set of input ports to accept data packets and a set of sink ports in communication with the input ports to forward the data packets. Each sink port includes a communications link interface with a Retry input. When a signal is asserted on the Retry input, the sink port aborts transmission of a data packet and waits a predetermined period of time to retransmit the data packet.

Cross-bar switch incorporating a sink port with retry capability

A cross-bar switch includes a set of input ports for receiving data packets and a set of sink ports for transmitting the received packets to identified targets. A set of data rings couples the input ports to the sink ports. Each sink port utilizes the set of data rings to simultaneously accept multiple data packets targeted to the same destination&#x2014;creating a non-blocking cross-bar switch. Sink ports are also each capable of supporting multiple targets&#x2014;providing the cross-bar switch with implicit multicast capability.

Cross-bar switch having bandwidth allocation

An architecture for controlling a multiprocessing system to provide at least one network service to subscriber data packets transmitted in the system using a plurality of compute elements, comprising a management compute element including service set-up information for at least one service and at least one processing compute element applying said at least one network service to said data packets and communicating service set-up information with the management compute element in order to perform service specific operations on data packets. In a further embodiment, a method of controlling a processing system including a plurality of processors is disclosed. The method comprises the steps of operating at least one of said processors as a control authority providing service provisioning information for a subscriber; and operating a set of processors as a service specific compute element responsive to the control authority, receiving provisioning information from the subscriber and performing service specific instructions on data packets to provide IP content services.

Content service aggregation device for a data center

Each sink port in a cross-bar switch provides for allocating bandwidth among data packets. Packets are assigned priority levels, and the cross-bar switch regulates bandwidth allocation for each priority level. A sink port records traffic volume for packet data of each priority level. The sink port calculates a weighted average bandwidth for each different priority level and determines whether to reject packet data for the priority level. When the packet data collected by a sink port exceeds a threshold, the sink port rejects data packets with priority levels having excessive weighted average bandwidths.

Cross-bar switch with bandwidth allocation

A cross-bar switch includes a set of input ports for receiving data packets and a set of sink ports for transmitting the received packets to identified targets. A set of data rings couples the input ports to the sink ports. Each sink port utilizes the set of data rings to accept data packets targeted to destinations supported by the sink port. The cross-bar switch includes a multi-sink port for supporting explicit multicast addressing. The multi-sink port is coupled to each data ring and each sink port. The multi-sink port snoops multicast packets on the cross-bar switch's rings and transfers each packet to a set of sink ports that support the packet's targeted destinations.

Cross-bar switch with explicit multicast support

A cross-bar switch includes a set of input ports to receive data packets and a set of sink ports in communication with the input ports to receive the data packets and forward them onto a communications link. Each sink port is adapted to concurrently receive multiple data packets targeted to the same destination or multiple destinations. For example, one sink port receives a first data packet and a second data packet. The one sink port receives at least a portion of the second data packet during a time period in which the one sink port is receiving the first data packet.

Cross-bar switch with sink port accepting multiple packets

Cross-bar switch

A cross-bar switch includes a set of input ports and a set of sink ports in communication with the input ports. The input ports receive packets, which are snooped by the sink ports. The cross-bar switch also includes a set of port address tables. Each port address table is adapted to store data identifying a plurality of destinations supported by a sink port. For example, a first port address table is adapted to identify a plurality of destinations supported by a first sink port in the set of sink ports. When determining whether to accept a packet, a sink port considers whether the packet's destination is identified in the sink port's port address table. By supporting multiple destinations, a port address table implicitly facilitates a sink port's multicast operation.

Cross-bar switch supporting implicit multicast addressing

A compute engine allocates data path bandwidth among different classes of packets. The compute engine identifies a packet's class and determines whether to transmit the packet based on the class' available bandwidth. If the class has available bandwidth, the compute engine grants the packet access to the data path. Otherwise, the compute engine only grants the packet access to the data path if none of the other packets waiting for data path access have a class with available bandwidth. After a packet is provided to the data path, the compute engine decrements a bandwidth allocation count for the packet's class. Once the bandwidth count for each class is exhausted, the compute engine sets each count to a respective starting value&#x2014;reflecting the amount of bandwidth available to a class relative to the other classes. A compute engine employing the above-described bandwidth allocation can be employed to perform different networking services, including but not limited to: 1) virtual private networking; 2) secure sockets layer processing; 3) web caching; 4) hypertext mark-up language compression; 5) virus checking; 6) firewall support; and 7) web switching.

Growing community of inventors

Granite Bay, CA, United States of America

Mark Bryers