Abstract: Congestion control by adding a congestion signal tag header to each of one or more transmission packets prior to transmission of the transmission packets by the first node to a second node, the congestion signal tag header specifying one or more congestion signal types and, for each of the congestion signal types, specifying a congestion signal value by providing an initial congestion signal value for the congestion signal value; receiving one or more return packets generated by the second node in response to receipt of the transmission packets, the return packets including a congestion signal reflection header having one or more return congestion signal values, and the return congestion signal values corresponding respectively to the congestion signal types; and determining whether transmission rate control is necessary based on the return congestion signal values.

Abstract: A system includes a first processor configured to analyze packets received over a communication protocol system and determine one or more congestion indicators from the analysis of the data packets, the one or more congestion indicators being indicative of network congestion for data packets transmitted over a reliable transport protocol layer of the communication protocol system. The system also includes a rate update engine separate from the packet datapath and configured to operate a second processor to receive the determined one or more congestion indicators, determine one or more congestion control parameters for controlling transmission of data packets based on the received one or more congestion indicators, and output a congestion control result based on the determined one or more congestion control parameters.

Abstract: A system includes a first processor configured to analyze packets received over a communication protocol system and determine one or more congestion indicators from the analysis of the data packets, the one or more congestion indicators being indicative of network congestion for data packets transmitted over a reliable transport protocol layer of the communication protocol system. The system also includes a rate update engine separate from the packet datapath and configured to operate a second processor to receive the determined one or more congestion indicators, determine one or more congestion control parameters for controlling transmission of data packets based on the received one or more congestion indicators, and output a congestion control result based on the determined one or more congestion control parameters.

Abstract: A system includes a first processor configured to analyze packets received over a communication protocol system and determine one or more congestion indicators from the analysis of the data packets, the one or more congestion indicators being indicative of network congestion for data packets transmitted over a reliable transport protocol layer of the communication protocol system. The system also includes a rate update engine separate from the packet datapath and configured to operate a second processor to receive the determined one or more congestion indicators, determine one or more congestion control parameters for controlling transmission of data packets based on the received one or more congestion indicators, and output a congestion control result based on the determined one or more congestion control parameters.

Abstract: A system includes a first processor configured to analyze packets received over a communication protocol system and determine one or more congestion indicators from the analysis of the data packets, the one or more congestion indicators being indicative of network congestion for data packets transmitted over a reliable transport protocol layer of the communication protocol system. The system also includes a rate update engine separate from the packet datapath and configured to operate a second processor to receive the determined one or more congestion indicators, determine one or more congestion control parameters for controlling transmission of data packets based on the received one or more congestion indicators, and output a congestion control result based on the determined one or more congestion control parameters.

Abstract: Techniques for cross referencing data are presented. A first database object and a second database object are linked together. The linkage is automatically cross referenced to a third database object. Access to any of the database objects can be achieved via any of the remaining database objects and vice versa. Additionally, the link and cross reference can be visualized and visually manipulated and modified.

Abstract: Techniques for data integration are provided. Source attributes for source data are interactively mapped to target attributes for target data. Rules define how records from the source data are merged, selected, and for duplication detection. The mappings and rules are recorded as a profile for the source data and processed against the source data to transform the source attributes to the target attributes.

Abstract: Techniques for managing data relationships are presented. A database element from a first database table is linked with a database element of a second database table via a Graphical User Interface as directed by a user. The link establishes a data relationship having attributes and properties. The relationship along with the attributes and properties are graphically presented to the user for inspection and analysis.

Abstract: A packet gateway (PGW) receives a plurality of IP packet fragments from a network. The IP packet fragments comprise a head fragment and one or more trailing fragments, and are associated with a first IP packet. As the fragments are received, a controller at the PGW classifies the fragments. The controller applies a same selected service treatment to the head fragment and to each of the trailing fragments based on the classification of the head fragment. The PGW then sends each treated packet fragment to an end user device.

Abstract: A method implementing dynamic next-hop routing at a network device is disclosed. The network device contains a routing information base (RIB) and a forwarding information base (FIB). The method starts with receiving a request to create a dynamic next-hop type using a next-hop schema. The dynamic next-hop type is for a prefix associated with an application. The next-hop schema includes a set of functions and a set of fields associated with the set of functions. The dynamic next-hop type is created using the next-hop schema at the RIB, where the set of fields associated with the set of functions of the dynamic next-hop type is processed. The created dynamic next-hop type is then downloaded to the FIB, where the set of functions of the dynamic next-hop type is processed. Afterward, an identifier associated with the dynamic next-hop type for the prefix associated with the application is returned.

Abstract: A method implementing dynamic next-hop routing at a network device is disclosed. The network device contains a routing information base (RIB) and a forwarding information base (FIB). The method starts with receiving a request to create a dynamic next-hop type using a next-hop schema. The dynamic next-hop type is for a prefix associated with an application. The next-hop schema includes a set of functions and a set of fields associated with the set of functions. The dynamic next-hop type is created using the next-hop schema at the RIB, where the set of fields associated with the set of functions of the dynamic next-hop type is processed. The created dynamic next-hop type is then downloaded to the FIB, where the set of functions of the dynamic next-hop type is processed. Afterward, an identifier associated with the dynamic next-hop type for the prefix associated with the application is returned.

Abstract: Techniques for data integration are provided. Source attributes for source data are interactively mapped to target attributes for target data. Rules define how records from the source data are merged, selected, and for duplication detection. The mappings and rules are recorded as a profile for the source data and processed against the source data to transform the source attributes to the target attributes.

Abstract: A packet gateway (PGW) receives a plurality of IP packet fragments from a network. The IP packet fragments comprise a head fragment and one or more trailing fragments, and are associated with a first IP packet. As the fragments are received, a controller at the PGW classifies the fragments. The controller applies a same selected service treatment to the head fragment and to each of the trailing fragments based on the classification of the head fragment. The PGW then sends each treated packet fragment to an end user device.

Abstract: Transferring a mobile node from one ASN-GW (anchor access service network gateway) to another ASN-GW is referred to as a hand-over. To facilitate transfer of data for the hand-over, a GRE (generic routing encapsulation) tunnel is established between the two ASN-GWs. Traffic through the GRE tunnel arriving at a line card of an ASN-GW is redirected from the arrival line card to the one line card that contains information for the mobile node. The redirection is based on traversal of one or more tables on the line cards. These tables are indexed according to GRE keys corresponding to the mobile nodes. Therefore, the appropriate line card for the traffic can be identified quickly and efficiently using a distributed forwarding plane with minimal provisioning overhead, resulting in lower latency during the hand-over.

Abstract: Techniques for cross referencing data are presented. A first database object and a second database object are linked together. The linkage is automatically cross referenced to a third database object. Access to any of the database objects can be achieved via any of the remaining database objects and vice versa. Additionally, the link and cross reference can be visualized and visually manipulated and modified.

Abstract: Techniques for managing data relationships are presented. A database element from a first database table is linked with a database element of a second database table via a Graphical User Interface as directed by a user. The link establishes a data relationship having attributes and properties. The relationship along with the attributes and properties are graphically presented to the user for inspection and analysis.

Abstract: Transferring a mobile node from one ASN-GW (anchor access service network gateway) to another ASN-GW is referred to as a hand-over. To facilitate transfer of data for the hand-over, a GRE (generic routing encapsulation) tunnel is established between the two ASN-GWs. Traffic through the GRE tunnel arriving at a line card of an ASN-GW is redirected from the arrival line card to the one line card that contains information for the mobile node. The redirection is based on traversal of one or more tables on the line cards. These tables are indexed according to GRE keys corresponding to the mobile nodes. Therefore, the appropriate line card for the traffic can be identified quickly and efficiently using a distributed forwarding plane with minimal provisioning overhead, resulting in lower latency during the hand-over.

Abstract: An apparatus, method, and article of manufacture provide the ability to publish information to an external source as part of an integrated workflow in a computer system. The computer system executes a relational database management system (RDBMS). A publication services processing engine utilizes the RDBMS to publish the information based on a publication node. A publication object defines a collection of information that is published to the external source. A publication action defines a specification of a manner in which the information in the publication object is to be published to the external source. The publication node defines a workflow data process that specifies the publication object and the publication action.