|Publication number||US7146422 B1|
|Application number||US 09/562,104|
|Publication date||Dec 5, 2006|
|Filing date||May 1, 2000|
|Priority date||May 1, 2000|
|Also published as||CN1439132A, CN100407194C, DE60127247D1, DE60127247T2, EP1279115A1, EP1279115B1, WO2001084358A1|
|Publication number||09562104, 562104, US 7146422 B1, US 7146422B1, US-B1-7146422, US7146422 B1, US7146422B1|
|Inventors||David A. Marlatt, John B. Abjanic|
|Original Assignee||Intel Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (69), Non-Patent Citations (4), Referenced by (58), Classifications (16), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The invention generally relates to computers and computer networks and in particular to a network apparatus for validating documents.
While increasingly more successful in their roles as store and forward data systems, computer networks such as the Internet are experiencing tremendous growth as transaction-based, mission critical business applications, Web site owners, and business servers are overwhelmed by explosive traffic growth. Application servers and other processing nodes can be overwhelmed with the responsibility to perform a variety of functions, including establishing connections with remote servers or clients, encrypting and decrypting transmitted information, processing the received data or transaction information (e.g., purchase orders, requests for web pages, etc.), formatting information for display or processing etc. To account for the high volume of traffic and the increasingly complex number of tasks required of application servers, the traditional solution has been to buy more servers and more network bandwidth, which can be cost prohibitive. XML, or extensible Markup Language v. 1.0 was adopted by the World Wide Web Consortium (W3C) on Feb. 10, 1998. XML provides a structured syntax for data exchange. XML is a markup language, like Hyper-Text Markup Language (HTML). In XML, the actual data is separated from the presentation of the data, in contrast with HTML which combines these two items. Most markup languages, like HTML, are fixed markup languages. That is, the fixed markup languages (including HTML) include a set of fixed tags for crafting a document. On the other hand, XML does not define a fixed set of tags, but rather, only defines a syntax or structured format through which users can define their own set of tags. There presently are a number of XML based languages (e.g., WML, CXML, CBL) which define their own set of XML tags using the XML syntax.
The XML standard only requires that a received document be checked to confirm that it meets the basic syntax and format of XML (i.e., determine whether the document is “well formed”). In addition, the XML standard also allows a document to be validated, which is a more rigorous check to determine if the structure or grammar of the XML document complies with structure required by the particular XML based language. Although not required by the XML specification, many application servers or other processing nodes that process XML documents include a validating XML processor (or a validating XML parser) to check the XML application data for validity against a validation template. Validation is important because it can ensure that the application data (e.g., transaction information) in the XML document is provided in the correct format and should be correctly interpreted by the application server.
Current XML processing usually involves an XML application server receiving an XML document from a source application and then fully processing the document and optionally providing a response to the source application. An XML document is typically processed through three steps.
1) A check to determine if the document is “well formed”.
2) An optional validation check to guarantee the syntax and grammar match a particular validation template.
3) Traditional parsing of the content for meaning and application to the problem domain (e.g., processing the application data or transaction data).
The second step, validation, can be computationally very expensive from both a processor and elapsed time point of view. In order to validate a document, an XML application must either retrieve a validation template from somewhere on the network or must parse (or identify) the validation template out of the XML document itself (if the validation template is provided within the XML document). Once the application server has the validation template it then must parse the application data and check that it matches the validation template rules. As a result, the burden of performing document validation can significantly decrease the number of documents or transactions that can be processed by the application server or processing node.
The foregoing and a better understanding of the present invention will become apparent from the following detailed description of exemplary embodiments and the claims when read in connection with the accompanying drawings, all forming a part of the disclosure of this invention. While the foregoing and following written and illustrated disclosure focuses on disclosing example embodiments of the invention, it should be clearly understood that the same is by way of illustration and example only and is not limited thereto. The spirit and scope of the present invention is limited only by the terms of the appended claims.
For example, some of the techniques of the invention will be illustrated and described with reference to an XML message and XML processing. The use of an XML message and XML processing are used only to explain and describe the techniques of the invention. However, the invention is not limited to XML or similar languages, but is applicable to messages provided in a wide variety of structured formats or languages.
The following represents brief descriptions of the drawings, wherein:
According to an example embodiment, a network apparatus is provided between a network and a plurality of processing nodes (e.g. web servers, application servers, XML servers, routers, switches or other devices). The network apparatus includes a validation accelerator to pre-validate documents.
According to an embodiment, a message is received including validation instructions and application data. A validation template may be provided either inline (e.g., internal to the document as part of the validation instructions) or as an external validation template. If the validation document is external, the template can be retrieved from a network (or remote server) and can be locally cached for future use to improve validation speed. The document is then validated based on the template, and the validation instructions are then removed from the document. The pre-validated document is then sent to a processing node or application server.
Because the validation instructions (including an internal validation template and/or a pointer to an external template) have been removed from the document, the application server will not validate the document and will presume that the document is valid. In this manner, the expensive task of document validation can be off-loaded from the application server to a network apparatus, such as a validation accelerator.
According to another embodiment, the network apparatus may include other functions or blocks, such as a security accelerator, a content based message director and/or a load balancer.
Referring to the Figures in which like numerals indicate like elements,
The data center 135 is provided for sending, receiving, processing and fulfilling a wide variety of messages and requests, such as business transactions, purchase orders, stock quotes or stock trades, and other information. The data center 135 includes several processing nodes (e.g., servers), including server 150, server 160 and server 170 for handling the various orders, business transactions and other requests.
According to an example embodiment, the clients and the entities of data center 135 exchange messages that include application data to be processed by an application program (such as an XML processor). The application data in the message may include business transaction information which may describe or relate to one or more transactions. According to an embodiment, the application data provided in a message may advantageously be provided as XML data (e.g., as a XML document) or in another structured format or other markup language to facilitate data exchange. The XML data in the messages preferably complies with the format or syntax required by the XML standard. A document that uses tag formats (e.g., start tags, end tags) and other syntax (e.g., to markup data) that complies with the XML standard is considered to be a “well-formed” XML document.
Referring to the clients again in
As a another example, web browser 122 may request web pages, business information or other information from a remote server (e.g., located at data center 135). Web browser 122, may also send or post purchase orders, business transactions or other business information to a remote server, which may be located at data center 135. Wireless device 132 may receive information or data related to purchase orders, business transactions, web pages, stock quotes, game scores and the like from one or more remote servers (such as servers located at data center 135).
According to an embodiment, the server 110, computer 120 and wireless device 132 each may communicate or interchange data with one or more remote servers (e.g., servers 150, 160 and 170) by sending and receiving XML data (i.e., application data or business transaction information that is encoded or formatted according to the XML standard or according to one or more XML based languages).
According to an advantageous embodiment, the data center 135 also includes a validation accelerator 142 to pre-validate received messages before the messages are sent to one of the application servers or processing nodes. According to an example embodiment, the validation accelerator 142 is provided as a network apparatus. In other words, according to an example embodiment, the validation accelerator 142 can be coupled between a network 130 and a plurality of processing nodes or application servers (e.g., servers 150, 160 and 170). Providing the validation accelerator 142 as a network apparatus (i.e., separate from the application servers) allows the computationally expensive task of document validation to be off-loaded from the application servers to the validation accelerator 142. Alternatively, a plurality of validation accelerators 142 may be provided, with one validation accelerator 142 being provided for one or more application servers or other processing nodes.
As noted above, an XML document must be checked to ensure it meets the basic syntax and format of XML (i.e., determine whether the document is “well formed”). In addition, the XML standard also optionally allows a document to be validated, which is a more rigorous check to determine if the structure or grammar of the XML document complies with structure or grammar required by the particular XML based language. XML allows a document to be validated against a validation template. A validation template defines the grammar and structure of the XML document (including required elements or tags, etc.).
There can be many types of validation templates such as a document type definition (DTD) in XML or a schema, as examples. These two validation templates are used as examples to explain some features according to example embodiments. Many other types of validation templates are possible as well. A schema is similar to a DTD because it defines the grammar and structure which the document must conform to be valid. However, a schema can be more specific than a DTD because it also includes the ability to define data types (e.g., characters, numbers, integers, floating point, or custom data types). In addition, unlike a DTD (under present standards), a schema may be required to be well formed. Thus, both the application data and the schema can both be parsed and checked for basic syntax (or well-formedness). Therefore, at least for some applications, it is expected that schemas will possibly become more common than DTDs in the future.
As noted above, validating a received document against a validation template is optional according to the XML standard. If a document is to be validated against a particular validation template, the XML document will include validation instructions (or validation code) at the beginning of the document. One example of validation instructions can be a document type declaration, as commonly known in XML. Another example is a schema (or a reference to an external schema). According to current XML, the validation instructions (e.g., document type declaration or schema, etc.) is an optional area of the document that declares the structure, element types, attributes, etc. of the validation template. To be a valid document, the structure and grammar of the application data in the document must match the structure and grammar defined by the validation template (if validation instructions are included in the document). The validation template can be provided internal to (or within) the document and/or external to the document.
The application data 220 is the application data that will be processed by an application server. The application data 220 may include, for example, business transaction information, such as a list items to be purchased, prices, quantities or other specific details of a transaction or a request for information (e.g., request for stock quote, transaction details).
According to an embodiment, the presence of one or more validation instructions 215 indicates that the document can (or should) be validated before processing the application data 220 based on a validation template provided within and/or identified by the validation instructions 215. In other words, according to an embodiment, the presence of validation instructions may indicate that the application data should be pre-validated at a network apparatus (such as validation accelerator 142) before passing the data to an application server for further processing. To indicate to the application server that the document (or the application data) has been validated, the validation instructions may be removed from the document and/or an indication (such as a comment or instruction in the data or a field set in the message) may be provided to indicate that the application data or message has been validated (i.e., pre-validated). According to current XML, document validation is optional (e.g., by the application server), even when validation instructions 215 are present. However, it is possible that in the future, validation (in XML or other languages) may be required.
If the document should be associated with a validation template (document type definition, schema, etc.) for document validation (i.e., to allow document validation), the document will typically include one or more validation instructions 215. The validation instructions 215 provide or identify the validation template (or document type definition) which defines the document structure and grammar (e.g., elements, attributes) to which the application data 220 of document 210 must conform. The validation template can include an internal component and/or an external component.
In this example shown (e.g., for XML), the validation instructions 215 (or validation template) are provided as a document type declaration. The validation instructions 215 begin with the DOCTYPE statement “<DOCTYPE hogsforsale . . . ” which indicates that there is a validation template, which may be provided within the document (i.e., as internal component 219) or provided external to the document (i.e., an external component identified as “hogs.dtd”). Therefore, in this example, the validation instructions 215 provide an internal component 219 of a validation template and an external component identifier 217 identifying an external component. The internal component 219 and the external component (not shown) together form the validation template for this document (i.e., for validating the application data 220 for document 210). According to an embodiment, if validation is being performed, the presence of the DOCTYPE statement (or other validation instructions) typically will cause an application or application server to validate the application data 220 in the message against the validation template.
The internal component 219 of the validation template defines that a valid hosgsforsale document must include the following elements: type, avg wt, quantity and price/hog, etc. This is just an example.
In this example, the identifier “hogs.dtd” identifies an external entity or file which is an external component of the validation template. The external component can be located on a remote server or other location based on the external component identifier 217. The external component of the validation template (identified as “hogs.dtd”) may include additional requirements on the structure or grammar of the application data 220 of the document 210. The external component identifier 217 may be provided as the complete address, or as a relative address or pointer (e.g., relative to the address or location of the source or originating node of the message). For example, the “hogs.dtd” identifier listed in the validation instructions 215 may actually reference the “hogs.dtd” external component 217 which may be found at (for example): oasis.xml.org/farming/livestock/hogs.dtd. As noted above, examples of validation templates include a Document Type Definition (e.g., for XML), a schema, etc.
At block 315, a validation template is obtained by the validation accelerator 142 for validating the document or message (e.g., for validating the application data 220 in the document 210). This may include first determining if validation instructions are present in the document or message. If no validation instructions are present, then validation will not be performed. If validation instructions are present, the validation accelerator 142 then determines whether the validation template for the document is provided as an internal component and/or an external component based upon the syntax of or one or more statements in the validation instructions 215.
If the validation template is provided within the document (i.e., as an internal component), the validation template is parsed from or separated from the remainder of the document. If the validation instructions 215 provide a external component identifier 217, then the validation accelerator 142 then retrieves or obtains the external component (e.g., from a remote server or node).
At block 320 of
At block 325, if the document or message is valid, the validation accelerator 142 then removes the (preferably all of the) validation instructions, including any statements that might cause the document to be validated (e.g., a DOCTYPE statement), any internal component(s) of the validation template and any references or identifiers to external components of the validation template.
At block 330, the validated document (with the validation instructions removed) is then sent to an application server or other processing node for processing.
By validating the document and then removing the validation instructions (including the validation template or identifiers thereto), any application program or application server receiving the document will only check whether the document is “well formed” (or meets the basic syntax of XML). Due to the absence of the validation instructions, the application server cannot validate the document, and will assume that the document or application data is valid. In this manner, the burden of performing document validation can be shifted from the application server to the validation accelerator 142.
If validation instructions are present in the document 402, next the validation accelerator 142 determines whether the validation template is internal (or inline) to the document, diamond 406. If so, then the document is validated based on the internal validation template at block 414.
If the validation template is not internal (or inline) to the document (this indicates that the template should be found as an external component), the validation accelerator 142 then determines whether the validation template (e.g., an external component) is stored in the cache, diamond 408. The validation accelerator 142 includes a high speed memory or local template cache 420 where copies of one or more validation templates (e.g., such as the file “hogs.dtd”) can be stored, and then later retrieved. If the validation template is present in the cache 420, the validation template is then retrieved, block 418 and used to validate the document, block 414.
If the validation template is not present in the template cache 420, the validation accelerator 142 then retrieves the validation template from the network (e.g., from a remote server), blocks 410 and 405. The retrieved validation template is then added to (or stored in) the template cache 420, block 412. The document is then validated at block 414.
After the document (or message) is validated at block 414, the validation instructions (including any internal validation template or external template identifier) are stripped or removed from the document, block 422. The validation accelerator 142 then outputs the pre-validated document or message to one of the application servers or processing nodes (e.g., to one of the servers at the data center 135) for processing.
Alternatively (or in addition to removing the validating instructions), an indication can be added to the message indicating to the application server that the application data or message has already been validated (i.e., pre-validated). This pre-validation indication can be provided, for example, as a field in the message, as an instruction or comment in the application data itself, or using another technique. For example, In the XML specification, besides element tags, and data, there is something known as a processing instruction tag which provides an “escape hatch” to allow information specific to an application to be embedded in an XML document. Processing instructions are not considered to be part of the character data content of an XML document, but they are always passed on to the XML application by the parser. The format is <? . . . ?> for the processing instruction tag. Thus, according to one embodiment, after the validation instructions (or the DTD or schema or reference thereto) has been removed, the following comment or instruction tag could be added near the beginning of the document (or other location): <? validated by intel ?>.
By pre-validating the document and then removing the validation instructions from the document (and/or adding a pre-validation indication to the document or message), the expensive step of validation is off-loaded from the application server to a network apparatus, network appliance or other system (which may be referred to, for example, as the validation accelerator 142).
In addition, a local cache 420 is provided to dynamically cache the most recently used (or most common) set of validation templates. Thus, each document that requires validation will typically include a validation template inline (or internal to the document) or will include a reference or pointer (e.g., a Universal Resource Identifier or URI) to identify an external template. The local cache is queried or consulted to determine if the required template is locally stored. If not, then the template is retrieved from the network and then locally cached for future use. This allows validation accelerator 142 to significantly reduce the time or latency to validate a document because a template must be retrieved from the network only once. Thereafter, the template will be provided internal or inline or can be retrieved from local cache.
According to an example embodiment, the cache can be implemented as a fixed size, usage-based stack such that validation templates that are accessed more frequently automatically push lesser-used templates out of the stack when it overflows. According to an embodiment, a least recently used (LRU) algorithm can be used to maintain the most recently used validation templates in the local cache, and to discard (or move to other memory, such as RAM or hard disk drive) the less frequently used templates. In this manner, the time to retrieve or obtain an external component of the validation template (or an external validation template) can be greatly reduced.
As described above, a pre-validation indication can be added to a document or message after the message or data has been validated. This pre-validation indication can be in an implicit form of missing (or removed) validation instructions (i.e., where the absence of the validation instructions indicates that the document is valid or has been validated). Alternatively, the pre-validation indication can be in the form of an explicit statement or indication (e.g., a statement, instruction or comment added to the message or document) indicating that the message or application data has been validated.
While the validation accelerator 142 has been described above as performing validation using a validation template, in another embodiment, validation accelerator 142 may merely parse the document and determine whether the application data in the document is well formed (i.e., meets the basic syntax and format requirements for the language). A pre-validation indication may then be added to indicate to the application server that the message or document is well formed (e.g., meets the required syntax).
The security accelerator 515 is provided for encrypting outgoing messages and/or decrypting incoming messages received from the network 130. According to an embodiment, the security accelerator 515 is a Secure Sockets Layer (SSL) accelerator, available from Intel Corporation. The security accelerator 515 allows the security related tasks such as encryption and/or decryption to be off-loaded from the application servers to the security accelerator 515.
The content based message director 545 (e.g., a XML director) is provided to route or direct received messages to one of the processing nodes or application servers based upon the content of the application data in the message, including business transaction information. The application data (including business transaction information) may advantageously be provided as a XML based language.
The load balancer 550 is provided to balance or adjust the traffic or messages among one or more of servers or processing nodes within the data center 135, based on one or more load balancing algorithms, such as round robin or other algorithm.
According to an embodiment, when the load balancer 550 and the message director 545 are used together, the message director 545 may make a switching decision based on the content of the application data (including business transaction information). The load balancer 550 may then switch or route the message to a server or node based (in part) on the switching decision. Alternatively, the message director 545 may make a switching decision and then just route or direct the message to a specific server or node.
Several embodiments of the present invention are specifically illustrated and/or described herein. However, it will be appreciated that modifications and variations of the present invention are covered by the above teachings and within the purview of the appended claims without departing from the spirit and intended scope of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US4216462||Mar 6, 1978||Aug 5, 1980||General Electric Company||Patient monitoring and data processing system|
|US5396613||Nov 5, 1992||Mar 7, 1995||University Of Utah Research Foundation||Method and system for error recovery for cascaded servers|
|US5473691||Nov 5, 1993||Dec 5, 1995||Microsoft Corporation||System and method for computer data transmission|
|US5550984||Dec 7, 1994||Aug 27, 1996||Matsushita Electric Corporation Of America||Security system for preventing unauthorized communications between networks by translating communications received in ip protocol to non-ip protocol to remove address and routing services information|
|US5634010||Oct 21, 1994||May 27, 1997||Modulus Technologies, Inc.||Managing and distributing data objects of different types between computers connected to a network|
|US5678010||Jun 7, 1995||Oct 14, 1997||Compuserve Incorporated||Automated routing of messages over a network|
|US5862328||Sep 6, 1996||Jan 19, 1999||International Business Machines Corporation||Bridge for a client-server environment|
|US5862344||Aug 28, 1995||Jan 19, 1999||Ncr Corporation||Apparatus and methods for routing data packets through a processing system network|
|US5870605||Jan 18, 1996||Feb 9, 1999||Sun Microsystems, Inc.||Middleware for enterprise information distribution|
|US5875242||Jul 26, 1996||Feb 23, 1999||Glaser; Lawrence F.||Telecommunications installation and management system and method|
|US5896379||Aug 26, 1996||Apr 20, 1999||Motorola, Inc.||Network node for packet switching with selective data processing and method therefor|
|US5931917||Sep 26, 1996||Aug 3, 1999||Verifone, Inc.||System, method and article of manufacture for a gateway system architecture with system administration information accessible from a browser|
|US5937165||Sep 10, 1996||Aug 10, 1999||Ganymede Software, Inc||Systems, methods and computer program products for applications traffic based communications network performance testing|
|US5943426||Sep 22, 1997||Aug 24, 1999||Motorola, Inc.||Method and apparatus for relaying digitally signed messages|
|US5951650||Jan 31, 1997||Sep 14, 1999||International Business Machines Corporation||Session traffic splitting using virtual internet protocol addresses associated with distinct categories of application programs irrespective of destination IP address|
|US5956339||Apr 10, 1997||Sep 21, 1999||Fujitsu Limited||Apparatus for selecting a route in a packet-switched communications network|
|US5987132||Jun 17, 1996||Nov 16, 1999||Verifone, Inc.||System, method and article of manufacture for conditionally accepting a payment method utilizing an extensible, flexible architecture|
|US5987232 *||Sep 9, 1997||Nov 16, 1999||Cadix Inc.||Verification server for use in authentication on networks|
|US5987500||Jun 20, 1997||Nov 16, 1999||Pi-Net International, Inc.||Value-added network system for enabling real-time, by-directional transactions on a network|
|US5995625||Mar 24, 1997||Nov 30, 1999||Certco, Llc||Electronic cryptographic packing|
|US6002767||Jun 17, 1996||Dec 14, 1999||Verifone, Inc.||System, method and article of manufacture for a modular gateway server architecture|
|US6006264||Mar 30, 1998||Dec 21, 1999||Arrowpoint Communications, Inc.||Method and system for directing a flow between a client and a server|
|US6011910||Apr 8, 1997||Jan 4, 2000||3Com Corporation||Supporting authentication across multiple network access servers|
|US6012098||Feb 23, 1998||Jan 4, 2000||International Business Machines Corp.||Servlet pairing for isolation of the retrieval and rendering of data|
|US6018721||May 19, 1997||Jan 25, 2000||Citibank, N.A.||Method and system for improved collateral monitoring and control|
|US6018801||Feb 23, 1998||Jan 25, 2000||Palage; Michael D.||Method for authenticating electronic documents on a computer network|
|US6026379||Jun 17, 1996||Feb 15, 2000||Verifone, Inc.||System, method and article of manufacture for managing transactions in a high availability system|
|US6032190||Oct 3, 1997||Feb 29, 2000||Ascend Communications, Inc.||System and method for processing data packets|
|US6038488 *||Jan 12, 1998||Mar 14, 2000||Bertec Corporation||Catheter simulation device|
|US6061734 *||Sep 24, 1997||May 9, 2000||At&T Corp||System and method for determining if a message identifier could be equivalent to one of a set of predetermined indentifiers|
|US6067354||Oct 9, 1998||May 23, 2000||Mci Communications Corporation||Method and system for processing data records from a telephone data repository to a receiving system|
|US6076107||Jan 10, 1997||Jun 13, 2000||International Business Machines Corporation||Method for reducing SNMP instrumentation message flows|
|US6091724||Nov 20, 1997||Jul 18, 2000||International Business Machines Corporation||Routing messages within a network using the data content of the message|
|US6105008||Apr 30, 1998||Aug 15, 2000||Visa International Service Association||Internet loading system using smart card|
|US6167438||May 22, 1997||Dec 26, 2000||Trustees Of Boston University||Method and system for distributed caching, prefetching and replication|
|US6167448||Jun 11, 1998||Dec 26, 2000||Compaq Computer Corporation||Management event notification system using event notification messages written using a markup language|
|US6167523 *||May 5, 1997||Dec 26, 2000||Intel Corporation||Method and apparatus for forms data validation and processing control|
|US6219691||Nov 19, 1997||Apr 17, 2001||At&T Corporation||Communication circulation system and method for communication in a network|
|US6226675||Oct 16, 1998||May 1, 2001||Commerce One, Inc.||Participant server which process documents for commerce in trading partner networks|
|US6256676 *||Oct 5, 1999||Jul 3, 2001||Saga Software, Inc.||Agent-adapter architecture for use in enterprise application integration systems|
|US6266335||Dec 19, 1997||Jul 24, 2001||Cyberiq Systems||Cross-platform server clustering using a network flow switch|
|US6343738||Apr 18, 2000||Feb 5, 2002||John W. L. Ogilvie||Automatic broker tools and techniques|
|US6366663 *||Jul 21, 1997||Apr 2, 2002||Mci Communications Corporation||System for achieving local number portability|
|US6375469||Sep 13, 1999||Apr 23, 2002||Health Hero Network, Inc.||Online system and method for providing composite entertainment and health information|
|US6400381 *||Jun 11, 1999||Jun 4, 2002||International Business Machines Corporation||Web places|
|US6408311||Jun 30, 1999||Jun 18, 2002||Unisys Corp.||Method for identifying UML objects in a repository with objects in XML content|
|US6415318||Apr 5, 1999||Jul 2, 2002||Microsoft Corporation||Inter-enterprise messaging system using bridgehead servers|
|US6442588||Aug 20, 1998||Aug 27, 2002||At&T Corp.||Method of administering a dynamic filtering firewall|
|US6477646||Feb 23, 2000||Nov 5, 2002||Broadcom Corporation||Security chip architecture and implementations for cryptography acceleration|
|US6480860||Feb 11, 1999||Nov 12, 2002||International Business Machines Corporation||Tagged markup language interface with document type definition to access data in object oriented database|
|US6480865||Oct 5, 1998||Nov 12, 2002||International Business Machines Corporation||Facility for adding dynamism to an extensible markup language|
|US6507856||Jan 5, 1999||Jan 14, 2003||International Business Machines Corporation||Dynamic business process automation system using XML documents|
|US6507857||Mar 10, 2000||Jan 14, 2003||Sun Microsystems, Inc.||Extending the capabilities of an XSL style sheet to include components for content transformation|
|US6512824 *||Aug 3, 1999||Jan 28, 2003||Adc Services Fulfillment, Inc.||Proxy database for element management system of telephone switching network|
|US6519617 *||Apr 8, 1999||Feb 11, 2003||International Business Machines Corporation||Automated creation of an XML dialect and dynamic generation of a corresponding DTD|
|US6567853 *||Dec 8, 1997||May 20, 2003||International Business Machines Corporation||Scalable I/O system for the efficient transfer of storage device data by a non-server reconnection|
|US6571279 *||May 19, 1999||May 27, 2003||Pinpoint Incorporated||Location enhanced information delivery system|
|US6584459||Jun 2, 1999||Jun 24, 2003||International Business Machines Corporation||Database extender for storing, querying, and retrieving structured documents|
|US6591260 *||Jan 28, 2000||Jul 8, 2003||Commerce One Operations, Inc.||Method of retrieving schemas for interpreting documents in an electronic commerce system|
|US6600683||Sep 17, 2001||Jul 29, 2003||Matsushita Electric Industrial Co., Ltd.||Semiconductor integrated circuit|
|US6621505||Sep 30, 1998||Sep 16, 2003||Journee Software Corp.||Dynamic process-based enterprise computing system and method|
|US6629146 *||May 16, 2000||Sep 30, 2003||Fujitsu Limited||Selection intermediary apparatus, transmission apparatus, selection intermediary program storage medium and transmission program storage medium|
|US6631497 *||Jul 19, 1999||Oct 7, 2003||International Business Machines Corporation||Binding data from data source to cells in a spreadsheet|
|US6654914||May 28, 1999||Nov 25, 2003||Teradyne, Inc.||Network fault isolation|
|US6658260||Nov 1, 2001||Dec 2, 2003||Telecommunication Systems, Inc.||Inter-carrier short messaging service providing phone number only experience|
|US6675219 *||Nov 1, 1999||Jan 6, 2004||Nokia Corporation||Technique for improving throughput of a gateway interface|
|US6766305 *||Mar 12, 1999||Jul 20, 2004||Curl Corporation||Licensing system and method for freely distributed information|
|US6925631||Dec 8, 2000||Aug 2, 2005||Hewlett-Packard Development Company, L.P.||Method, computer system and computer program product for processing extensible markup language streams|
|US20020099734||Nov 29, 2000||Jul 25, 2002||Philips Electronics North America Corp.||Scalable parser for extensible mark-up language|
|1||"The Advantages of F5's HTTP Header Load Balancing Over Single-Point URL Parsing Solutions", F5 Networks, Inc., pp. 1-2.|
|2||Aaron Skonnard, "Soap: The Simple Object Access Protocol", Microsoft Corporation, pp. 1-10, Retrieved from the www on Mar. 16, 2005 at: <microsoft.com/mind/0100/soap/soap>.|
|3||*||Bray et al.; Extensible Markup Language (XML) 1.0; Feb. 10, 1998; http://www.w3.org/TR/1998/REC-xml-19980210.pdf.|
|4||Retrieved from the www on Mar. 16, 2005 at: <f5.com/solutions/archives/whitepapers>.|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7356532||Feb 16, 2005||Apr 8, 2008||Bea Systems, Inc.||Systems and methods for maintaining transactional persistence|
|US7451211 *||Jan 23, 2004||Nov 11, 2008||Microsoft Corporation||Message exchange pattern tracking to avoid invalid message exchange|
|US7472413 *||Aug 11, 2004||Dec 30, 2008||F5 Networks, Inc.||Security for WAP servers|
|US7475093 *||Jul 20, 2005||Jan 6, 2009||Microsoft Corporation||Memory cache management in XML/relational data mapping|
|US7555708 *||Sep 17, 2004||Jun 30, 2009||Microsoft Corporation||Mechanism for converting text output into objects|
|US7584474||Feb 24, 2004||Sep 1, 2009||Bea Systems, Inc.||Systems and methods for transaction chaining|
|US7650276||Feb 17, 2004||Jan 19, 2010||Bea Systems, Inc.||System and method for dynamic data binding in distributed applications|
|US7650592||Feb 23, 2004||Jan 19, 2010||Bea Systems, Inc.||Systems and methods for multi-view debugging environment|
|US7657832 *||Sep 18, 2003||Feb 2, 2010||Adobe Systems Incorporated||Correcting validation errors in structured documents|
|US7665074 *||Nov 29, 2004||Feb 16, 2010||Microsoft Corporation||Mechanism for converting text output into objects|
|US7676538||Mar 28, 2003||Mar 9, 2010||Bea Systems, Inc.||Systems and methods for application view transactions|
|US7707564||Feb 23, 2004||Apr 27, 2010||Bea Systems, Inc.||Systems and methods for creating network-based software services using source code annotations|
|US7711755 *||May 16, 2007||May 4, 2010||Topcoder, Inc.||Dynamic XSD enumeration|
|US7721193 *||Oct 15, 2002||May 18, 2010||Bea Systems, Inc.||System and method for implementing a schema object model in application integration|
|US7752599||Feb 23, 2004||Jul 6, 2010||Bea Systems Inc.||Systems and methods extending an existing programming language with constructs|
|US7774697||Feb 17, 2004||Aug 10, 2010||Bea Systems, Inc.||System and method for structuring distributed applications|
|US7774831 *||Dec 22, 2003||Aug 10, 2010||International Business Machines Corporation||Methods and apparatus for processing markup language messages in a network|
|US7831655||Oct 15, 2002||Nov 9, 2010||Bea Systems, Inc.||System and method for implementing a service adapter|
|US7840611||Mar 12, 2007||Nov 23, 2010||Oracle International Corporation||High availability for event forwarding|
|US7844636||Oct 31, 2007||Nov 30, 2010||Oracle International Corporation||Systems and methods for client-side filtering of subscribed messages|
|US7953787||Mar 2, 2009||May 31, 2011||Oracle International Corporation||System and method for providing highly available processing of asynchronous requests using distributed request and response queues and a service processor|
|US8015572||Apr 11, 2007||Sep 6, 2011||Oracle International Corporation||Systems and methods for an extensible software proxy|
|US8032860||Feb 24, 2004||Oct 4, 2011||Oracle International Corporation||Methods for type-independent source code editing|
|US8135772||Apr 1, 2003||Mar 13, 2012||Oracle International Corporation||Single servlets for B2B message routing|
|US8266519||May 15, 2008||Sep 11, 2012||Accenture Global Services Limited||Document analysis, commenting, and reporting system|
|US8266630||Sep 3, 2007||Sep 11, 2012||International Business Machines Corporation||High-performance XML processing in a common event infrastructure|
|US8271870||Sep 11, 2009||Sep 18, 2012||Accenture Global Services Limited||Document analysis, commenting, and reporting system|
|US8412516 *||Nov 27, 2007||Apr 2, 2013||Accenture Global Services Limited||Document analysis, commenting, and reporting system|
|US8442985||Feb 17, 2011||May 14, 2013||Accenture Global Services Limited||System for requirement identification and analysis based on capability mode structure|
|US8484664||Aug 1, 2011||Jul 9, 2013||Oracle International Corporation||Systems and methods for an extensible software proxy|
|US8566731||Jul 6, 2010||Oct 22, 2013||Accenture Global Services Limited||Requirement statement manipulation system|
|US8572673 *||Jun 10, 2005||Oct 29, 2013||Dominic Gavan Duffy||Data processing apparatus and method|
|US8671101||Apr 30, 2013||Mar 11, 2014||Accenture Global Services Limited||System for requirement identification and analysis based on capability model structure|
|US8843819||Jul 29, 2010||Sep 23, 2014||Accenture Global Services Limited||System for document analysis, commenting, and reporting with state machines|
|US8935654||Jan 9, 2012||Jan 13, 2015||Accenture Global Services Limited||Analysis system for test artifact generation|
|US9003509||Dec 10, 2008||Apr 7, 2015||F5 Networks, Inc.||Security for WAP servers|
|US9183194||Aug 6, 2012||Nov 10, 2015||Accenture Global Services Limited||Document analysis, commenting, and reporting system|
|US20030093470 *||Oct 15, 2002||May 15, 2003||Mitch Upton||System and method for implementing a service adapter|
|US20030182452 *||Oct 15, 2002||Sep 25, 2003||Mitch Upton||System and method for implementing a schema object model in application integration|
|US20040167915 *||Feb 23, 2004||Aug 26, 2004||Bea Systems, Inc.||Systems and methods for declaratively transforming data objects between disparate representations|
|US20040220815 *||Aug 20, 2001||Nov 4, 2004||Johanne Belanger||Apparatus and method for the compilation, assembly, and distribution of product documentation and associated information|
|US20050114148 *||Nov 20, 2003||May 26, 2005||International Business Machines Corporation||System, apparatus and method of automatically verifying conformance of documents to standardized specifications|
|US20050149371 *||Aug 29, 2004||Jul 7, 2005||Jenny Wang||Electronic form system and method thereof|
|US20050198148 *||Jan 23, 2004||Sep 8, 2005||Cabrera Luis F.||Message exchange pattern tracking to avoid invalid message exchange|
|US20060064668 *||Nov 29, 2004||Mar 23, 2006||Microsoft Corporation||Mechanism for converting text output into objects|
|US20060064672 *||Sep 17, 2004||Mar 23, 2006||Microsoft Corporation||Mechanism for converting text output into objects|
|US20060085451 *||Jul 12, 2005||Apr 20, 2006||Microsoft Corporation||Mapping of schema data into data structures|
|US20060085489 *||Jul 20, 2005||Apr 20, 2006||Microsoft Corporation||Memory cache management in XML/relational data mapping|
|US20060265689 *||Dec 22, 2003||Nov 23, 2006||Eugene Kuznetsov||Methods and apparatus for processing markup language messages in a network|
|US20070156922 *||Mar 8, 2007||Jul 5, 2007||Bea Systems, Inc.||High availability for event forwarding|
|US20070239749 *||Mar 30, 2006||Oct 11, 2007||International Business Machines Corporation||Automated interactive visual mapping utility and method for validation and storage of XML data|
|US20070294282 *||May 16, 2007||Dec 20, 2007||Donald Cruver||Dynamic xsd enumeration|
|US20090064185 *||Sep 3, 2007||Mar 5, 2009||International Business Machines Corporation||High-Performance XML Processing in a Common Event Infrastructure|
|US20090138257 *||Nov 27, 2007||May 28, 2009||Kunal Verma||Document analysis, commenting, and reporting system|
|US20090138793 *||May 15, 2008||May 28, 2009||Accenture Global Services Gmbh||Document Analysis, Commenting, and Reporting System|
|US20100005386 *||Sep 11, 2009||Jan 7, 2010||Accenture Global Services Gmbh||Document analysis, commenting, and reporting system|
|US20110022902 *||Jan 27, 2011||Accenture Global Services Gmbh||Document analysis, commenting, and reporting system|
|US20140281925 *||Mar 15, 2013||Sep 18, 2014||Alexander Falk||Automatic fix for extensible markup language errors|
|U.S. Classification||709/227, 709/246, 707/E17.032, 709/238, 709/225, 709/202|
|International Classification||H04L29/08, G06F15/16, G06F15/173, G06F17/30|
|Cooperative Classification||H04L67/02, G06F17/2725, G06F17/2247|
|European Classification||G06F17/30W7S, H04L29/08N1, G06F17/30N|
|Aug 4, 2000||AS||Assignment|
Owner name: INTEL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MARLATT, DAVID A.;ABJANIC, JOHN B.;REEL/FRAME:013478/0211
Effective date: 20000717
|Feb 27, 2007||CC||Certificate of correction|
|Jun 3, 2010||FPAY||Fee payment|
Year of fee payment: 4
|May 21, 2014||FPAY||Fee payment|
Year of fee payment: 8