# US 2004/0205597 A1 · Network apparatus for switching based on content of application data

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0205597 A1
- Document ID: US20040205597A1
- Status: Published application
- Kind: A1
- Application number: 10/750,266
- Filed: 2003-12-31
- Published: 2004-10-14
- Earliest claimed: 2000-04-13
- Assignees: Intel Corporation
- Inventors: John B. Abjanic
- Web page: https://patentgrep.com/patent/US20040205597A1

## CPC

- H04L 47/125: by balancing the load, e.g. traffic engineering
- G06F 16/986: {Document structures and storage, e.g. HTML extensions}
- H04L 41/0266: using meta-data, objects or commands for formatting management information, e.g. using eXtensible markup language [XML]
- H04L 43/0876: Network utilisation, e.g. volume of load or congestion level
- H04L 47/28: in relation to timing considerations
- H04L 47/31: by tagging of packets, e.g. using discard eligibility [DE] bits
- H04L 47/33: using forward notification
- H04L 49/252: {Store and forward routing}
- H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload}
- H04L 63/0471: {applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding}
- H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP]
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L 67/101: based on network conditions
- H04L 67/56: Provisioning of proxy services (store-and-forward switching systems in data switching networks H04L12/54)
- H04L 67/562: Brokering proxy services
- H04L 67/563: Data redirection of data network streams
- H04L 67/63: Routing a service request depending on the request content or context
- H04L 69/22: Parsing or analysis of headers
- H04L 69/329: in the application layer [OSI layer 7]
- A61B 5/6852: {Catheters}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D)

## Abstract

A network apparatus is provided between a network and a plurality of processing nodes or servers. The network apparatus includes a content based message director (e.g., XML director) to route or direct messages received from the network to one of the processing nodes based upon the application data, including business transaction information

## Claims

### Claim 1

A network apparatus comprising:
an XML checker to determine if a received message includes XML information;
the network apparatus adapted to switch the message to an output port or to a selected processing node based upon business transaction information provided in XML in the message if the message includes XML information.

### Claim 2 (depends on 1)

The network apparatus of claim 1 wherein the network apparatus is adapted to switch or forward the message substantially without XML processing if the message does not include XML information.

### Claim 3 (depends on 1)

The network apparatus of claim 1 wherein the network apparatus comprises a traffic manager.

### Claim 4 (depends on 1)

The network apparatus of claim 1 wherein the network apparatus comprises a network processor.

### Claim 5 (depends on 1)

The network apparatus of claim 1 comprising a content based message director to switch messages to one of a plurality of output ports or one of a plurality of processing nodes based upon comparing business transaction information provided in XML to a configuration pattern.

### Claim 6 (depends on 1)

The network apparatus of claim 1 wherein the network apparatus comprises an XML parser to parse XML information in the received message.

### Claim 7

A method comprising:
receiving a message;
determining if the received message includes XML information; and
switching the message to an output port or to a selected processing node based upon business transaction information provided in XML in the message if the message includes XML information.

### Claim 8 (depends on 7)

The method of claim 7 and further comprising:
otherwise forwarding the message substantially without XML processing if the message does not include XML information.

### Claim 9 (depends on 7)

The method of claim 7 and further comprising parsing the received message.

### Claim 10 (depends on 7)

The method of claim 7 wherein the switching comprises:
comparing the business transaction information provided in XML in the message to a configuration pattern; and
switching the message to an output port or to a selected processing node based upon a match between the XML business transaction information and the configuration pattern.

### Claim 11 (depends on 10)

The method of claim 10 and further comprising performing one of the following on the message if there is no match between the XML business transaction information and the configuration pattern:
directing the message to a default location; and
blocking or not forwarding the message.

### Claim 12 (depends on 10)

The method of claim 10, wherein the configuration pattern may indicate one or more of the following:
a source or From entity of the message;
a destination or To entity of the message;
a type of transaction; and
a purchase amount.

### Claim 13 (depends on 7)

The method of claim 7 wherein the determining if the received message includes XML information comprises performing one of the following:
detecting a certain filename or type of filename in the message;
detecting a certain type of filename extension in the message;
examining header information in the message; and
examining one or more tags in the message.
