Juniper Networks, Inc.

Andrzej Szyszko

Nitin Kumar

Apurva Mehta

Gopi Krishna

Scott Mackie

Kumar B Mehta

John Ernest Ziegler

Jagadish Grandhi

Murtuza S Attarwala

Surya Chandra Sekhar Nimmagadda

Timothy L Patrick

John Gibbons

Cristina Radulescu-Banu

Aditya Thakur

Nagaraj S Turaiyur

Abhay Mehta

Rohan Meegada

Jitendra Kumar Singh

Norm Strahle

Ravikumar Tulugu

Akhil S

Kumar Mehta

NAPT services are provided, preferably inline on the 'fast path' on bundled links. One of the member links is selected as “anchor.” When uplink traffic arrives on the any of the member links, the link's forwarding path looks to the NAPT binding entry in its forwarding path. If a binding entry is found, NAPT is performed in an inline manner (without requiring any other device), and the traffic is forwarded. If a binding entry is not found, the received traffic is forwarded to the anchor. The anchor allocates the port and creates a NAPT binding on all the member links. Downlink traffic performs lookup for reverse NAPT binding entry in the link's forwarding path. If a matching entry is found, the forwarding path of the link performs NAPT. If there is no matching binding entry, the downlink traffic is dropped. Stale binding entries are “aged out”, enabling dynamic NAPT.

Inline dynamic network address and port translation (NAPT)

In some implementations, a network device may receive an indication of a switchover for a subscriber group that contains subsets of subscriber sessions. The network device may transition each subset of the subscriber sessions to a state associated with traffic forwarding. The network device may selectively transition each subset of the subscriber sessions from the state associated with the traffic forwarding to a state associated with traffic services.

State transitions for redundancy groups

In some implementations, a redundant DBNG user plane device may maintain respective subscriber states of a plurality of primary DBNG user plane devices. The redundant DBNG user plane device may determine, based on maintaining the respective subscriber states of the plurality of primary DBNG user plane devices, that a particular primary DBNG user plane device, of the plurality of primary DBNG user plane devices, is not active. The redundant DBNG user plane device may identify, based on determining that the particular primary DBNG user plane device is not active, a subscriber state of the particular primary DBNG user plane device. The redundant DBNG user plane device may operate, using the subscriber state of the particular primary DBNG user plane device, as an active DBNG user plane device for traffic associated with the particular primary DBNG user plane device.

Distributed broadband network gateway stateful N+1 hot-redundancy

In some examples, a network device comprises a first application and a second application; a forwarding unit comprising an interface card to receive a packet; a packet processor; an internal forwarding path of the forwarding unit; a forwarding unit processor; a first interface; and a second interface. The first application is configured to configure, via the first interface, the internal forwarding path to include a sandbox that comprises a container for instructions to be configured inline within the internal forwarding path. The second application is configured to configure, via the second interface, the sandbox with second instructions that determine processing of packets within the sandbox. The packet processor is configured to process, in response to determining a packet received by the forwarding unit is associated with a packet flow controlled at least in part by the second application, the packet by executing the second instructions configured for the sandbox.

Network device data plane sandboxes for third-party controlled packet forwarding paths

In general, this disclosure describes techniques for applying, with a network device, subscriber-specific packet processing using an internal processing path that includes service objects that are commonly applied to multiple packet flows associated with multiple subscribers. In one example, a network device control plane creates subscriber records that include, for respective subscribers, one or more variable values that specify service objects as well as an identifier for a packet processing template. A forwarding plane of the network device receives and maps subscriber packets to an associated subscriber record and then processes the packet by executing the packet processing template specified by the subscriber record. When the forwarding plane reaches a variable while executing the specified packet processing template, the forwarding plane reads the associated variable value from the subscriber record to identify and then apply the subscriber-specific service object specified by the variable.

Variable-based forwarding path construction for packet processing within a network device

In general, techniques are described for scheduling traffic for delivery over an aggregated bundle of links. The techniques may be implemented by a network device comprising a control unit. The control unit configures a primary logical interface such that the primary logical interface is associated with a primary link of the aggregated bundle of links. The primary logical interface is associated with a primary scheduling module that schedules the traffic for delivery via the primary link. The control unit further, prior to detecting a failure associated with the primary scheduling module, configures a backup logical interface such that the backup logical interface is associated with a backup link of the aggregated bundle links. The backup logical interface is associated with a backup scheduling module that schedules, in response to detecting the failure associated with the primary scheduling module, the traffic for delivery downstream via the backup link.

Scheduling traffic over aggregated bundles of links

A network device may include a lawful interception module, a routing module, and a multicast distribution table. The lawful interception module may receive a lawful interception request for a subscriber, may inform the routing module about the subscriber, and may provide, to the routing module, a tap interface corresponding to the subscriber. The routing module may receive a multicast join request from the subscriber, and may insert, when the multicast join request is received, the tap interface in the multicast distribution table, as a forwarding interface.

Lawful interception of subscriber received multicast traffic

Growing community of inventors

Holden, MA, United States of America

Andrzej Szyszko