Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device; establishing a routing decision context object in response to receiving the Diameter message, wherein the routing decision context object is associated with a destination device chosen to receive a previous message; evaluating a rule that includes a context object reference, wherein the evaluation includes accessing the routing decision context object based on the context object reference; and transmitting a message based on the evaluation of the rule.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a Diameter message at the DRA from an origin device, wherein the Diameter message includes a first destination address; establishing a context object based on receiving the Diameter message, wherein the context object is associated with a copy of the Diameter message; evaluating at least one rule, comprising modifying, based on a first reference to the context object, the copy to include a second destination address, and transmitting the copy to another device based on the second destination address.

Abstract: Various exemplary embodiments relate to a method performed by a policy and charging rules node (PCRN), the method comprising: receiving an event trigger from a policy and charging enforcement node (PCEN) indicating that a subscriber is out of credit; installing temporary PCC rules to handle the out of credit status of the subscriber; receiving an indication that the subscriber has completed a reallocation of credit action; uninstalling the temporary PCC rules and restoring the original PCC rules after receiving an indication of reallocation of credit.

Abstract: Various exemplary embodiments relate to a method performed by a policy and charging rules node (PCRN) device. The method may include: establishing a first service data flow for an application function having a first Policy and Control Charging (PCC) rule including a first parameter within a session; receiving a request to upgrade the first parameter of the service data flow; generating a second PCC rule including an upgraded parameter; storing the first PCC rule in a cache; sending the second PCC rule to a Policy and Charging Enforcement Node (PCEN); receiving acknowledgement that the second PCC rule has been installed at the PCEN; receiving an indication that the second PCC rule failed at a downstream node; and sending the first PCC rule stored in the cache to the PCEN.

Abstract: A method of sending hypertext transfer protocol (HTTP) adaptive streaming (HAS) content from a content source to a client over a transmission control protocol (TCP) connection between the content source and the client may include receiving a request for one or more first HAS data chunks from the client; sending the one or more first HAS data chunks to the client; generating idle delay values indicating an amount of delay in the TCP connection during an idle time period, the idle time period being a time period over which no HAS data chunks are being sent from the content source to the client; receiving a request for a second HAS data chunk from the client; setting the size of a starting TCP congestion window based on the idle delay values; and sending the second HAS chunk to the client using the starting TCP congestion window.

Abstract: Embodiments of the invention are directed to a TCAM for longest prefix matching in a routing system. The TCAM comprises a plurality of records of which a portion are configured into one or more address clusters each such cluster corresponding to a respective IP address prefix length and another portion of which are configured into a free cluster not corresponding to any IP address prefix length.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: displaying, by the network management system, a first representation of a synchronization topology, wherein the synchronization topology includes a set of network elements and a set of peers; identifying a set of peers to be monitored; receiving an indication that a network path associated with a peer of the set of peers to be monitored has changed; and displaying an alarm indication.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: displaying, by the network management system, a first representation of a synchronization topology, wherein the synchronization topology includes a set of network elements and a set of peers; receiving a selection of at least one selected network element of the set of network elements; identifying at least one identified peer of the set of peers associated with the at least one selected network element; adding the at least one identified peer of the set of peers to a first synchronization group; and displaying a second representation of the synchronization topology, wherein the second representation includes a representation of the first synchronization group.

Abstract: Embodiments of the invention provide an improved major release negotiation mechanism between an initiating node and a receiving node during Diameter session establishment in a 3GPP network.

Abstract: A low profile standoff with tool stop is disclosed for attaching surfaces in fixed proximity to each other. The low profile standoff with tool stop includes a main body having a threaded bore, a threaded stem for threading a nut, and an intermediate section of narrower cross section than the main body that admits a portion of the threaded bore. The intermediate section extends within the thickness of the mounting surface while the main body stays on one side and the threaded stem extends wholly through to the opposite side of the surface. Some embodiments further comprise a tool stop on the exterior of the main body. Other embodiments dispense with the threaded stem. The low profile standoff with tool stop is particularly useful for overcoming the strength disadvantages of reduced height standoffs known in the art, and of minimizing tool head damage to the mounting surface.

Abstract: Various exemplary embodiments relate to a method performed by a policy and charging rules node of provisioning event triggers. The method may include: receiving, from a requesting node, a request to provision a set of event triggers on a primary gateway; forwarding, to the primary gateway, the set of event triggers; storing the set of event triggers in association with a session; detecting a handover of the session; determining a new primary gateway; and forwarding, to the new primary gateway, the set of event triggers. The method may further include: receiving a message; determining whether the message includes the same set of event triggers; if the message includes the same set of event triggers, refraining from sending the set of event triggers to the primary gateway; and if the message includes a different set of event triggers, forwarding the different set of event triggers to the primary gateway.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: performing an active gateway election to determine whether the provider edge device will be an active gateway for a connection; if the provider edge device will be the active gateway for the connection, indicating to a customer edge device that no fault is currently associated with a link between the customer edge device and the provider edge device; and if the provider edge device will not be the active gateway for the connection, indicating to the customer edge device that a fault is currently associated with the link between the customer edge device and the provider edge device.

Abstract: Various exemplary embodiments relate to a method of protecting against resource overload. The method may include: setting a resource critical threshold level of usage for a monitored resource; setting an overload rejection level for a plurality of operations; measuring a level of usage; determining an overload usage state based on the level of usage; shedding an operation if the overload usage state equals or exceeds the overload rejection level for the operation; determining whether the level of usage exceeds the resource critical threshold level; and if the level of usage exceeds the resource critical threshold level: changing the overload usage state to a resource critical overload usage state, and shedding an operation unless the overload rejection level indicates that the operation should never be shed. Various exemplary embodiments relate to a network element including: a monitored resource; a rejection level mapping; a status monitor; and an overload manager.

Abstract: In one embodiment, the apparatus for embedding links includes a reproducing unit configured to receive a data stream and display at least one object of the data stream on a display screen of a device. The apparatus further includes a processing unit configured to activate a link associated with a displayed object based on linking information. The linking information includes activation information and destination information. The activation information indicates a period of time when the link is activated. The destination information includes at least one of address information that points to additional information on a remote server and launch information that specifies an application to be launched on the device. The processing unit is configured to display the additional information on the display screen or launch the application upon user selection of the activated link.

Abstract: Various exemplary embodiments relate to a method performed by a policy and charging rules node (PCRN) of generating a notification message. The method may include: defining a notification server profile; defining a notification template including a message body and a variable; defining an action rule including a condition; evaluating the condition of the action rule; determining a result set including an attribute; placing the attribute in the variable to form a notification message; and sending the notification message to the notification server. Various exemplary embodiments relate to a PCRN. The PCRN may include: a context information module; a notification server profile storage; a notification template including a message body and a variable; a rules engine configured to evaluate rules using context information; and an action manager configured to: connect to a server, generate a notification message by placing an attribute in the variable, and send the notification message to the server.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving a message at the network device; constructing a route key based on the message, wherein the route key comprises at least one value carried by the message; determining whether the network device stores a previous route record associated with the route key; and if the network device does not store a previous route record associated with the route key, generating a new route record based on the route key, and provisioning a new route based on the new route record into a routing table of the network device.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving the set of PCC rules at the network device from a partner device; determining that the set of PCC rules includes an unauthorized PCC rule, wherein the unauthorized PCC rule fails an authorization; determining that the set of PCC rules includes an authorized PCC rule, wherein the authorized PCC rule passes the authorization; generating an unauthorized rules list including an indication of the unauthorized PCC rule; generating an authorized rules list including an indication of the authorized PCC rule; transmitting the unauthorized rules list and the authorized rules list to the partner device.

Abstract: A method and system for enforcing metered data usage is disclosed for automatically providing top-ups to a cumulative user data quota. The method for enforcing metered data includes determining cumulative data usage associated to a customer, comparing the cumulated data usage to a quota threshold, and in the event that the cumulated data usage exceeds the threshold, to automatically apply a quota top-up if one is provided for in an associated customer plan. This allows the customer data transfers to continue without requiring manual intervention on the part of the service provider in the event that quota is exceeded. The method and system for enforcing metered data usage also provides for expressing cumulative data usage in terms of a percentage of base quota, thereby facilitating determination if an increase in base quota should be arranged.

Abstract: Various exemplary embodiments relate to a method and related network node including one or more of the following: receiving, at the network device from an entity, a request for a serving device assigned to a subscriber; attempting to locate an assignment record associated with the subscriber; in response to locating the assignment record associated with the subscriber, identifying an assigned serving device of the multiple serving devices indicated by the assignment record as being assigned to the subscriber; and transmitting a response to the entity, wherein the response identifies the assigned serving device.

Abstract: Various exemplary embodiments relate to a method of matching a user roaming request with the users home network, the method comprising: receiving a user request that includes an international mobile subscriber identification (IMSI); extracting mobile country code (MCC) from the IMSI; extracting the next M digits from the IMSI as the mobile network code (MNC); searching a MCC-MNC database for the extracted MCC-MNC; if the extracted MCC-MNC is found in the MCC-MNC database, then associate the user request with an identified roaming partner.