Abstract: Various exemplary embodiments relate to method performed by a router. The method may include: receiving a HTTP GET request from a user device; forwarding the HTTP GET request; receiving a response to the HTTP GET request; determining whether to intercept the response based on flow selection criteria; and replacing the response with a modified response. Various exemplary embodiments relate to a router including a plurality of line cards interconnected by a backplane, the plurality of line cards receiving communication packets; and an application assurance card connected to the backplane and configured to detect application traffic flows among the communication packets, identify a HTTP session including a HTTP GET request and a matching response from among the packets; determine whether the HTTP session meets selection criteria; and modify the response to include a command to execute a script located on a notification server responsive to the HTTP session meeting the criteria.

Abstract: Various exemplary embodiments comprise a method and related device and computer-readable medium including one or more of the following: receiving an uncompressed packet sent from the source node to the destination node during a compression negotiation stage; storing information extracted from the uncompressed packet, the stored information sufficient to uniquely identify flows; receiving a compressed packet sent from the source node to the destination node; associating the compressed packet with an active flow by accessing the stored information and information in the compressed packet; performing deep packet inspection (DPI) to identify an application associated with the active flow; and performing application-specific processing on at least one packet belonging to the active flow. In various exemplary embodiments, the information extracted from the uncompressed packet includes a context identifier used to establish a compression context between a compressor and a decompressor.

Abstract: Based on application information received from a DPI device, a downstream device, such as a Radio Network Controller (RNC), optimally implements a dormancy timer policy for short-lived applications, such as email and MMS. In particular, the RNC may initially use a large value for the dormancy timer for these applications. When the RNC receives an indication of the end of the application from the DPI device, the RNC may terminate the connection, thereby immediately freeing up resources. Alternatively, should the DPI device fail to recognize the end of the application, the initial dormancy timer serves as a fail-safe, such that the radio network resources are still released for allocation to another device in the radio network.

Abstract: Various exemplary embodiments relate to a method and related network element including: receiving a first plurality of packets transmitted between a peer-to-peer (P2P) client and a P2P central entity; performing deep packet inspection (DPI) to extract a key from one or more of the first plurality of packets, the key identifying a P2P content item; receiving a second plurality of packets; performing DPI to extract location information of at least one P2P peer from one or more of the second plurality of packets; detecting at least one subsequent IP flow between the P2P client and the at least one P2P peer using the extracted location information, the at least one subsequent IP flow relating to a transfer of the P2P content item; and performing a traffic management action on the at least one subsequent IP flow.

Abstract: Various exemplary embodiments relate to a method and related network element including one or more of the following: receiving a plurality of packets belonging to an IP flow, the packets received in a network element in the telecommunications network; performing deep packet inspection (DPI) to identify an application protocol associated with the flow; when the application protocol is a peer-to-peer (P2P) protocol, performing DPI to extract a key from one or more of the packets in the flow, the key uniquely identifying a P2P content item; querying a P2P content database using the key, the P2P content database maintaining a mapping between keys and corresponding traffic management actions; and when the key is located in the P2P content database, performing the traffic management action associated with the key in the P2P content database.

Abstract: Various exemplary embodiments relate to a method and related network element including: receiving a first plurality of packets transmitted between a peer-to-peer (P2P) client and a P2P central entity; performing deep packet inspection (DPI) to extract a key from one or more of the first plurality of packets, the key identifying a P2P content item; receiving a second plurality of packets; performing DPI to extract location information of at least one P2P peer from one or more of the second plurality of packets; detecting at least one subsequent IP flow between the P2P client and the at least one P2P peer using the extracted location information, the at least one subsequent IP flow relating to a transfer of the P2P content item; and performing a traffic management action on the at least one subsequent IP flow.

Abstract: Based on application information received from a DPI device, a downstream device, such as a Radio Network Controller (RNC), optimally implements a dormancy timer policy for short-lived applications, such as email and MMS. In particular, the RNC may initially use a large value for the dormancy timer for these applications. When the RNC receives an indication of the end of the application from the DPI device, the RNC may terminate the connection, thereby immediately freeing up resources. Alternatively, should the DPI device fail to recognize the end of the application, the initial dormancy timer serves as a fail-safe, such that the radio network resources are still released for allocation to another device in the radio network.

Abstract: Various exemplary embodiments comprise a method and related device and computer-readable medium including one or more of the following: receiving an uncompressed packet sent from the source node to the destination node during a compression negotiation stage; storing information extracted from the uncompressed packet, the stored information sufficient to uniquely identify flows; receiving a compressed packet sent from the source node to the destination node; associating the compressed packet with an active flow by accessing the stored information and information in the compressed packet; performing deep packet inspection (DPI) to identify an application associated with the active flow; and performing application-specific processing on at least one packet belonging to the active flow. In various exemplary embodiments, the information extracted from the uncompressed packet includes a context identifier used to establish a compression context between a compressor and a decompressor.

Abstract: Redundancy mechanisms are difficult to implement in a node holding connections spanning over a wide telecommunications network. Novel redundancy mechanisms to be implemented on a telecommunications node is described. In the mechanisms, an inactive device is maintained in hot standby with the active device so that a substantially hitless activity switch can be performed. The inactive device is kept in synchrony with the active device by updating the inactive device only when the status of connection has changed.