Juniper Networks, Inc.

Gopi Krishna

Apurva Mehta

Jagadish Grandhi

Ananda Sathyanarayana

Dinesh Bakiaraj

Krishna Sankaran

Sanjay Agrawal

Srinivasa Chaganti

Murtuza S Attarwala

Harsha Srinath

Bobby Vandalore

Sankar Ramamoorthi

Kumar B Mehta

Venkatesh Ramachandra

Shauli Gal

Tong Jiang

Prasad Chigurupati

Rohini Kasturi

Ramasamy Ramanathan

Bin William Hong

Roopa Bayar

Andrzej Szyszko

Roshan Joyce

Santosh Gupta

Sandesh Kumar Sodhi

Gazal Sahai

Balamurugan Ramaraj

Nikhil G Shetty

Chitrak K Ojha

Ananya Basu

Vijay S Rajaram

Pankaj Gupta

Ina Minei

Suresh Kumar Vinapamula Venkata

Ramanarayanan Ramakrishnan

Sanjiv Doshi

Shiva Shenoy

Prabhakaran Ganesan

Li Fang

Abbas Y Sakarwala

Vignesh Chinnakkannu

Rama Ramakrishnan

Jwala Dinesh Gupta Chakka

Arun Balasubramanian

Juan-Antonio Bernal Van Der Ven

Kumar Mehta

Amanda Sathyanarayana

A system and method for communicating between applications using a routing process. A set of one or more signal-routes are defined on a network device, including a first signal-route. Each signal-route is associated with a state of an application to be executed on the network device, wherein the first signal-route is associated with a first application state of the application. The network device detects, within the application executing within an application layer of the network device, a change in the first application state and notifies other applications of the change in the first application state. Notifying includes modifying the first signal-route, wherein modifying includes adding the first signal-route to or removing the first signal-route from a Routing Information Base (RIB) and advertising the change in the RIB.

Inter-application communication via signal-routes

Techniques are described for dynamically adapting virtualized network functions (VNFs) to different target environments. A controller stores device profiles that include configuration data and workflows for resolving configuration parameters for instantiating and deploying a VNF package to form a network service. To support the resolution of VNF configuration parameters, a VNF descriptor for the VNF is extended to include a device family parameter that indicates a shared architecture and configuration parameters. The controller, when instantiating the VNF, may identify a device profile usable for resolving the configuration parameters for the VNF and obtain configuration data from the device profile for creating and configuring a VNF instance for the VNF descriptor. Extending the VNF descriptor to specify a device family allows the VNF to be flexibly adapted for different target environments and may avoid the use of numerous pre-defined VNF descriptors.

Virtualized network function descriptors for virtualized network function configuration

A redundant service delivery gateway system and method. Configuration information defining roles for redundant service delivery gateways is received via a user interface defined for each of a plurality of redundant service delivery gateways. Configuration information defining one or more redundancy events, a redundancy policy associated with each redundancy event and two or more redundancy sets is also received via a user interface. Each redundancy set is associated with one or more of the redundancy events and each redundancy set includes a master redundancy state and a standby redundancy state. A first redundancy event detected in a first service delivery gateway leads to a transition, in the first service delivery gateway, from a master redundancy state to a standby redundancy state in the redundancy set associated with the first redundancy event.

Application aware inter-chassis redundancy

A system and method for handling critical events in service delivery gateways. Events are defined that cause a transition from a master redundancy state to a standby redundancy state in service delivery gateways and a plurality of signal-routes are stored. Each signal-route is associated with one or more of the defined events. A first defined event is detected in the first service delivery gateway and causes a transition from the first master redundancy state to the first standby redundancy state in the first service delivery gateway and a change in a first signal-route from the plurality of signal-routes in the first service delivery gateway. The change in the first signal-route is advertised and a second service delivery gateway transitions from the first standby redundancy state to the first master redundancy state.

Route signalling based resilient application overlay network

In general, techniques are described for programming a set of one or more pre-defined rules within the forwarding plane of a packet gateway of a mobile service provider network and caching, within control plane, a group identifier that identifies the set of programmed, pre-defined rules. The control plane may match quality of service (QoS) information of incoming subscriber service requests with the group identifier and respective subsets of the set of programmed, pre-defined rules to rapidly associate service requests with already-programmed PCC rules and thereafter install, to the forwarding plane, subscriber service-specific actions for the PCC rules.

Policy and charging control rule programming and lookup in connectivity access networks

In general, techniques are described for offloading data transfer statistics from a mobile access gateway. The mobile access gateway comprises a forwarding unit. The forwarding unit comprises a packet forwarding engine (PFE). When the PFE receives a packet, the PFE updates a data transfer statistic based on a quantity of data in the packet. The data transfer statistic is initially stored in a memory of the PFE. The PFE is configured to push the data transfer statistic from the memory of the PFE to a memory of the forwarding unit.

Offload of data transfer statistics from a mobile access gateway

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 aggregating, within a network device, internal forwarding routes for multiple control protocols and allocating next hops for the routes among individual service units of a decentralized control plane for the network device. The techniques may also include aggregating internal forwarding routes for data protocols and allocating next hops for the routes among individual forwarding units of a decentralized data plane for the network device. In one example, a mobile gateway includes a plurality of subscriber management service units that present a uniform interface to nodes within a mobile service provider network. An allocation manager apportions a control protocol session identifier namespace into a plurality of contiguous, non-overlapping protocol session identifier ranges and allocates the ranges among the service units. The service units execute the control protocol by utilizing respective allocated ranges, which the aggregate internal forwarding routes use to identify the associated service units.

Mobile gateway having reduced forwarding state for anchoring mobile subscribers

In one example, an intermediate network device sends packets that advertise a transmission control protocol (TCP) window size of zero bytes to a client device and a server device. The device, after sending the packets, receives a first zero-window probe packet from the client device including data representing a first current sequence number for a client-to-server packet flow of an established network session, and a second zero-window probe packet from the server device including data representing a second current sequence number for a server-to-client packet flow of the network session. The device also initializes a TCP state based on the first and second current sequence numbers, and acts as a TCP proxy for packets following the first zero-window probe packet of the client-to-server packet flow based on the TCP state and packets following the second zero-window probe packet of the server-to-client packet flow based on the TCP state.

TCP proxying of network sessions mid-flow

In general, techniques are described for load balancing, with a service node, packet flows using stateless load balancing that adapts to server failure to provide flow affinity to initially selected servers for the duration of respective flows. In one example, service node device applies stateless load balancing to packet flows to distribute the flows among a plurality of servers. The service node determines a failure of a failed server and then receives an initial packet of a packet flow from the packet flows and forwards the initial packet to an active server. The service node generates a mapping of the packet flow to the active server, determines a recovery of the failed server, receives a subsequent packet of the packet flow, and forwards the subsequent packet of the packet flow to the active server based at least on the mapping of the packet flow to the active server.

Adaptive stateless load balancing

Techniques are described for performing inline NAT functions in a forwarding element of a mobile gateway router or other device in which subscriber sessions of a mobile access network are distributed across a plurality of session management cards. The session management cards pre-allocate a public network address and port range for subscribers at the time a network connection is established in response to connection request prior to receiving any data traffic associated with the subscriber. NAT profiles are programmed into hardware forwarding elements of the mobile gateway router for inline NAT when routing subscriber traffic for the mobile access network.

Inline network address translation within a mobile gateway router

Policy and charging control rule programming and lookup in wireless connectivity access networks

Growing community of inventors

Tracy, CA, United States of America

Gopi Krishna