Abstract: A system and method for modifying services provided by one or more network devices. A processor of a first network device identifies defined events in each of a plurality of applications, including a first defined event associated with a first application. The processor assigns a signal-route to each defined event. The processor then executes the first application and, when the processor detects occurrence of the first defined event during execution of the first application, the processor modifies services provided by a second network device by adding the first signal-route to or removing the first signal-route from a routing information base (RIB) on the first network device and advertising, to the second network device, the change in the RIB.

Abstract: A stateful application gateway redundancy system and method. Configuration information defines a service processing unit on a service gateway and associates a first redundancy set and a second redundancy set with the service processing unit, wherein the first and the second redundancy sets include a master redundancy state, a standby redundancy state and one or more redundancy policies, including at least one redundancy policy defining actions to be taken on occurrence of a redundancy event associated with the respective redundancy set. In response to detecting a critical event for the first redundancy set, the service gateway transitions the first redundancy set from the standby redundancy state to the master redundancy state, adds a first signal-route associated with the first redundancy set to a Routing Information Base (RIB) and advertises the first signal-route to routing protocol peer network devices.

Abstract: A stateful application gateway redundancy system and method. Configuration information defines a service processing unit on a service gateway and associates a first redundancy set and a second redundancy set with the service processing unit, wherein the first and the second redundancy sets include a master redundancy state, a standby redundancy state and one or more redundancy policies, including at least one redundancy policy defining actions to be taken on occurrence of a redundancy event associated with the respective redundancy set. In response to detecting a critical event for the first redundancy set, the service gateway transitions the first redundancy set from the standby redundancy state to the master redundancy state, adds a first signal-route associated with the first redundancy set to a Routing Information Base (RIB) and advertises the first signal-route to routing protocol peer network devices.

Abstract: A system and method for handling critical events in service gateways. Configuration information is received in a service gateway, the configuration information defining a redundancy set having a master redundancy state and a standby redundancy state, the configuration information including one or more redundancy policies associated with the redundancy set, a service redundancy policy defining changes to be made in a service when a transition occurs in the state of the redundancy set. The service gateway receives further configuration information defining events that cause a transition between the master and standby redundancy states in the redundancy set. In response to detecting a redundancy event in the service gateway, the service gateway transitions the redundancy set, within the service gateway, from the master redundancy state to the standby redundancy state, modifies a first signal-route state associated with the redundancy set and modifies the service based on the service redundancy policy.

Abstract: In general, the invention is directed to techniques for offloading per-subscriber traffic management from an access gateway to one or more upstream service nodes within a service provider network. For example, as described herein, an upstream service node receives a new packet flow for a subscriber and sends packet flow information, such as a network address, to a session and resource controller (SRC). The SRC maintains a table of subscriber attachment sessions and maps the packet flow information to a subscriber attachment session in the table to obtain a subscriber identifier for a subscriber. The SRC then determines subscriber-specific services to be applied to subscriber data traffic, transforms the services to a set of one or more enforcement policies, and returns the enforcement policies to the service node. In turn, the service node applies the enforcement policies for the subscriber-specific services to the subscriber data traffic in the packet flow.

Abstract: Multiple subscriber devices are connected to a network device via one or more network switches. The network device transmits multicast traffic to the subscriber devices. In particular, the network device may receive membership requests for a multicast group from the subscriber devices via the network switch on a first interface, i.e., a mapping interface. The network device sends a multicast stream associated with the multicast group to the network switch on a second interface, i.e. an outgoing interface (OIF). Upon receiving a membership request, the network device maps the membership request to an OIF dedicated to the multicast group. In this way, when multiple subscriber devices connected to the same switch request the same multicast stream, each membership request will map to the same OIF. The network device sends one copy of the multicast stream to the network switch on the dedicated OIF.