|Publication number||US6874025 B2|
|Application number||US 09/746,932|
|Publication date||Mar 29, 2005|
|Filing date||Dec 22, 2000|
|Priority date||Dec 22, 2000|
|Also published as||US20020083171|
|Publication number||09746932, 746932, US 6874025 B2, US 6874025B2, US-B2-6874025, US6874025 B2, US6874025B2|
|Inventors||Peter J. Hoogenboom, Richard G. Ireland, Douglas P. Bogia|
|Original Assignee||Intel Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (19), Non-Patent Citations (7), Referenced by (31), Classifications (11), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The subject matter of this disclosure relates to data networks. In particular, this disclosure relates to systems and methods of receiving inputs to an application process through a communication network.
Services are typically provided over the Internet at a server platform by receiving inputs for server based applications from client processes. For the inputs to be valid, the inputs typically must conform to constraints. For example, an application receiving text based inputs typically require that the inputs conform to a particular alphanumeric format. This is particularly common in applications which receive inputs from a network browser through a hypertext transfer protocol (HTTP) server.
An HTTP server typically transmits hypertext markup language (HTML) pages to a network browser hosted on a client device for receiving inputs to a server application. The HTML pages may provide an entry form which is generated on a graphical user interface (GUI) of the client device for prompting a user to provide textual inputs to be transmitted back to the HTTP server. Upon receipt of the inputs, the HTTP server may execute logic to determine whether the received inputs are valid. The HTTP server may provide validated inputs to the server application and respond to invalid inputs by transmitting an error message back to the network browser.
Repeated transmission of invalid inputs to the HTTP server and corresponding error messages back to the network browser is a time consuming activity which uses communication resources. To reduce the need to transmit data between the HTTP server and the network browser in the process of providing valid inputs to the server application, the HTML page transmitted to the network browser may include an encoded script to validate the inputs at the network browser prior to sending any inputs to the HTTP server. This ensures that only valid inputs are received at the HTTP server.
A server application may be adapted to receive user inputs from external processes through other communication interfaces in addition to an HTTP server. Like inputs provided through the HTTP server, the inputs provided through the other communication interfaces are typically validated before being provided to the application. Accordingly, there is a need for a system and method of validating inputs to the server application according to consistent validation criteria regardless of the method of providing the inputs to the server application.
Non-limiting and non-exhaustive embodiments of the present invention will be described with reference to the following figures, wherein like reference numerals refer to like parts throughout the various figures unless otherwise specified.
Reference throughout this specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrase “in one embodiment” or “an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in one or more embodiments.
An “application process” as referred to herein relates to one or more processes for providing a result or initiating action in response to inputs. For example, an application process may provide a service to an end user such as, for example, a communication service, commercial transaction, games, spreadsheet, word processing or database retrieval. However, embodiments of the present invention are not limited in this respect and an application process may be directed to providing other results or services.
In some embodiments, an application process may respond to input data to provide the result. For example, an application may receive inputs specifying a commercial transaction to be initiated by the application process. “Validation criteria” as referred to herein relates to criteria to be applied in determining whether inputs to an application process are acceptable by the application process to provide a result or initiate an action. However, embodiments of the present invention are not limited in this respect. A “validation engine” as referred to herein refers to a process for providing or applying validation criteria for inputs to an application.
A “client process” as referred to herein relates to processes for receiving user inputs to be forwarded to an application process. Such a client process may be adapted to forward the user inputs according to a communication protocol. However, embodiments of the present invention are not limited in this respect. A “client device” as referred to herein relates to a device for hosting a client process such as, for example, a personal computer system, mobile telephone, personal digital assistant. However, these are merely examples and embodiments of the invention are not limited in this respect.
A “communication interface” as referred to herein relates to a process for receiving inputs to an application process from a source and forwarding the inputs to the application process. A communication interface may receive the inputs from the source according to a communication protocol. In an example embodiment, a plurality of communication interfaces may be adapted to receive inputs to an application process from a plurality of sources. However, embodiments of the present invention are not limited in this respect.
A “server” as referred to herein relates to one or more processes for communicating with a client process according to a communication protocol. Such a server may be adapted to receive inputs to an application process from the client process. However, embodiments of the present invention are not limited in this respect.
Embodiments of the present invention relate to a system and method of validating inputs to an application process received at any one of a plurality of communication interfaces. A validation engine determines validation criteria for inputs to the application process received at any one of the communication interfaces. One of the communication interfaces may be a communication server (e.g., a hypertext transfer protocol (HTTP) server, see, e.g., Internet Official Protocol Standards RFC 2616, June 1999) adapted to receive inputs to the application process from a client process (e.g., a network browser) hosted on a client device. In response to a query from the communication server, the validation engine provides validation data representative of the validation criteria to the communication server. The communication server may then transmit an encoded script to the client process for executing a validation procedure at the client device.
The IP server 14 may provide a plurality of communication interfaces for receiving inputs to the application process 10 from the external processes. These communication interfaces may comprise an HTTP server 18, an SNMP manager 20, an electronic mail process 22 (see, e.g., Simple Mail Transfer Protocol, Internet Official Protocol Standards, RFC 821) and a VoIP process 24. However, embodiments of the present invention are not limited in this respect and the IP server 14 may comprise other communication interfaces.
In addition to IP based communication interfaces, a telephony server 34 coupled to a public switched telephone network (PSTN) 23 may provide a communication interface for receiving inputs to the application process 10 from an external telephony device 21. The telephony server 34 may include one or more telephone modems coupled to the PSTN 23 through telephone lines and sufficient CPU and memory resources to host a telephony applications programming interface (TAPI). Call handling routines hosted on the telephony server 34 may process calls received to provide inputs to the application process 10 via a network interface. Such call handling routines may include a procedure to validate inputs to the application process 10. However, this is merely a sample embodiment of the telephony server 34 and does not limited embodiments of the present invention.
The application process 10 may be any one of several processes for responding to external inputs such as, for example, an electronic commerce application which receives inputs as orders for goods or services from the external processes. However, this is merely an example of application process and other application processes may be used. The application process 10 may be hosted on a processing platform as part of an enterprise resource planning (ERP) system. However, embodiments of the present invention are not limited in this respect.
The validation engine 16 determines validation criteria for the inputs to the application process 10 from all communication interfaces. The validation criteria determined at the validation engine 16 is used to execute procedures at either the external processes or the communication interfaces to validate inputs to the application process 10. A single validation engine 16 enables modification to the input validation criteria without modification to the communication interfaces. Also, consistent validation criteria may be applied to inputs of the application process 10 regardless of whether a validation process occurs at an external processes or at a communication interface (for providing the inputs to the application 10).
The validation engine 16 may determine the validation criteria 37 dynamically based upon aspects of the application process 10 and events detected at the validation server. For example, the validation criteria 37 may define input constraints for data types, completeness, date and time or other format related requirements. However, these are merely examples of validation criteria and embodiments of the present invention are not limited in these respects.
The server 50 may comprise any of the communication interfaces other than the HTTP server 18 such as the SNMP manager 20, electronic mail process 22 or VoIP process 24 on the IP server 14, or the telephony server 34. However, the server 50 may comprise other communication interfaces and embodiments of the present invention are not limited in this respect. The telephony server 34 and the VoIP process 24 may receive inputs to the application process 10 in the form of dual tone multi-frequency (DTMF) tones or voice data provided by the user at the telephony device 21. However, the telephony server 34 may receive inputs according to a different format and embodiments of the present invention are limited in this respect. The SNMP manager 20 may receive inputs to the application process 10 in the form of an SNMP message (e.g., an SNMP response to a GET or SET command) from the SNMP agent 32. The electronic mail process 22 may receive inputs to the application process 10 in the form of data provided in specific fields of an electronic mail message. However, the electronic mail process 22 may receive inputs according to a different format and embodiments of the present invention are not limited in this respect.
If the validation engine 16 determines that the system input 66 does not meet the validation criteria, the server 50 may modify the system input 66 to conform with the validation criteria (and may re-submit the modified system input 66 to the validation engine 16 for validation) before forwarding the system input 66 to the application process 10. Alternatively, the server 50 may transmit a message to the external process indicating that the input is invalid and may be resubmitted. For example, if the server 50 is the telephony server 34 or the VoIP process 24, the server 50 may transmit a prerecorded voice message back to the caller/user indicating that the received inputs are invalid. If the server 50 is the electronic mail process 22, the server 50 can transmit an electronic mail message to an address associated with the external process providing the system input 66. However, this merely illustrates examples of a validation engine and embodiments of the present invention are not limited in this respect.
In alternative embodiments, the validation engine 16 may communicate directly with the application process 10 to pass validated inputs directly to the application process 10 without any further interaction with the server 50. In handling system inputs 66 which do not meet the validation criteria, the validation engine 16 may selectively modify invalid inputs to comply with the validation criteria and forward the modified inputs to the application process 10, or return a message to the server 50 indicating that the system input does not meet the validation criteria. Again, this is merely a sample embodiment of a validation engine and embodiments of the present invention are not limited in this respect.
While there has been illustrated and described what are presently considered to be the preferred embodiments of the present invention, it will be understood by those skilled in the art that various other modifications may be made, and equivalents may be substituted, without departing from the true scope of the invention. Additionally, many modifications may be made to adapt a particular situation to the teachings of the present invention without departing from the central inventive concept described herein. Therefore, it is intended that the present invention not be limited to the particular embodiments disclosed, but that the invention include all embodiments falling within the scope of the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5287403 *||Jul 22, 1992||Feb 15, 1994||At&T Bell Laboratories||Method and apparatus for processing telephone calls charged to credit cards|
|US5572640 *||Dec 1, 1994||Nov 5, 1996||Hewlett-Packard Company||Batch transfer system and method for high performance graphic display of network topology|
|US5907680 *||Jun 24, 1996||May 25, 1999||Sun Microsystems, Inc.||Client-side, server-side and collaborative spell check of URL's|
|US5930258 *||Nov 29, 1996||Jul 27, 1999||Telefonica De Espana, S.A.||Structure for an electronic data system|
|US5964891 *||Aug 27, 1997||Oct 12, 1999||Hewlett-Packard Company||Diagnostic system for a distributed data access networked system|
|US6041324 *||Nov 17, 1997||Mar 21, 2000||International Business Machines Corporation||System and method for identifying valid portion of computer resource identifier|
|US6247171 *||Dec 6, 1999||Jun 12, 2001||Sun Microsystems, Inc.||Bytecode program interpreter apparatus and method with pre-verification of a data type restrictions and object initialization|
|US6304905 *||Sep 16, 1998||Oct 16, 2001||Cisco Technology, Inc.||Detecting an active network node using an invalid protocol option|
|US6393468 *||Jan 9, 1998||May 21, 2002||British Telecommunications Public Limited Company||Data access control|
|US6507857 *||Mar 10, 2000||Jan 14, 2003||Sun Microsystems, Inc.||Extending the capabilities of an XSL style sheet to include components for content transformation|
|US6519228 *||Dec 22, 1999||Feb 11, 2003||International Business Machines Corp.||System and method of operation for verifying and validating public switch telephone networks (PSTN) to (IP) network services|
|US6615258 *||Sep 24, 1998||Sep 2, 2003||Worldcom, Inc.||Integrated customer interface for web based data management|
|US6629098 *||Jan 16, 2001||Sep 30, 2003||Hewlett-Packard Development Company, L.P.||Method and system for validating data submitted to a database application|
|US20020007409 *||Jan 6, 2001||Jan 17, 2002||Rode Christian Stig||Methods and apparatus for sharing computational resources|
|US20020065689 *||Nov 26, 2001||May 30, 2002||Getthere Inc.||Meeting site selection based on all-inclusive meeting cost|
|US20020069365 *||Sep 10, 1999||Jun 6, 2002||Christopher J. Howard||Limited-use browser and security system|
|US20020082857 *||Sep 6, 2001||Jun 27, 2002||Val Skordin||Method and apparatus for providing an online document and input form creation and storage system|
|US20020163535 *||Dec 11, 2000||Nov 7, 2002||Mitchell Kathryn L.||System and method for generating a graphical user interface from a template|
|US20030046361 *||Jul 3, 2002||Mar 6, 2003||Infoseek Corporation||Method and apparatus for redirection of server external hyper-link references|
|1||*||Devanbu et al, "Research directions for automated software verification Using trusted hardware", IEEE, 1997, pp. 274-279.*|
|2||*||Drummond et al, "Intelligent Browsing for Multimedia Applications", IEEE, 1996, p. 386-389.*|
|3||*||Feigin et al, "Hardware-fitted Modeling and Simulation of VoIP over a Wireless LAN", IEEE, 2000, p. 1431-1438.*|
|4||*||Hailpern, "Modular Verification of Computer communication Protocols", IEEE, 1993, pp. 56-68.|
|5||*||Heidemann,et al, "Modeling the Performance of HTTP Over Several Transport Protocols", IEEE/ACM Transactions on Networking, vol.5, No. 5, Oct. 1997, p. 616-630.*|
|6||*||Merlin, "Specification and Validation Protocol", IEEE Transactions on communication, vol. COM-27 , No. 11, Nov. 1979, pp. 1671-1680.*|
|7||*||Zafiropulo, "Protocol Validation by Duologue-Matrix Analysis", IEEE, 1978, pp. 1187-1194.*|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7236910 *||Feb 1, 2005||Jun 26, 2007||Wood Group Esp, Inc.||Equipment identification, tracking and failure analysis process|
|US7519905 *||Aug 27, 2003||Apr 14, 2009||Webmd Corp.||Automatic formatting and validating of text for a markup language graphical user interface|
|US7542957 *||Jul 22, 2005||Jun 2, 2009||International Business Machines Corporation||Rich Web application input validation|
|US7769807 *||Jul 18, 2008||Aug 3, 2010||International Business Machines Corporation||Policy based auditing of workflows|
|US8230042||Apr 19, 2005||Jul 24, 2012||International Business Machines Corporation||Policy based auditing of workflows|
|US8433283||Jan 27, 2009||Apr 30, 2013||Ymax Communications Corp.||Computer-related devices and techniques for facilitating an emergency call via a cellular or data network using remote communication device identifying information|
|US8527860||Dec 2, 2008||Sep 3, 2013||Appcelerator, Inc.||System and method for exposing the dynamic web server-side|
|US8650247 *||Apr 5, 2010||Feb 11, 2014||Microsoft Corporation||Four tier architecture for implementing thin clients|
|US8719451||Nov 22, 2008||May 6, 2014||Appcelerator, Inc.||System and method for on-the-fly, post-processing document object model manipulation|
|US8756579 *||Nov 30, 2008||Jun 17, 2014||Appcelerator, Inc.||Client-side and server-side unified validation|
|US8806431||Dec 2, 2008||Aug 12, 2014||Appecelerator, Inc.||Aspect oriented programming|
|US8914774||Nov 14, 2008||Dec 16, 2014||Appcelerator, Inc.||System and method for tagging code to determine where the code runs|
|US8954553||Sep 20, 2009||Feb 10, 2015||Appcelerator, Inc.||System and method for developing, deploying, managing and monitoring a web application in a single environment|
|US9178705||Apr 13, 2007||Nov 3, 2015||International Business Machines Corporation||Method and system for stateless validation|
|US9444786||May 23, 2012||Sep 13, 2016||Servicenow, Inc.||Policy based auditing of workflows|
|US20020198975 *||Jun 26, 2001||Dec 26, 2002||Bogia Douglas P.||Method for managing an appliance|
|US20040024842 *||Jul 31, 2002||Feb 5, 2004||Sap Aktiengesellschaft||Validation framework for validating markup page input on a client computer|
|US20040039993 *||Aug 27, 2003||Feb 26, 2004||Panagiotis Kougiouris||Automatic formatting and validating of text for a markup language graphical user interface|
|US20060235964 *||Apr 19, 2005||Oct 19, 2006||Childress Rhonda L||Policy based auditing of workflows|
|US20070016960 *||Jul 17, 2006||Jan 18, 2007||Nt Objectives, Inc.||NTO input validation technique|
|US20070022119 *||Jul 22, 2005||Jan 25, 2007||Patrick Roy||Rich Web application input validation|
|US20070189270 *||Feb 15, 2006||Aug 16, 2007||Borislow Daniel M||Network adapter|
|US20080247531 *||Apr 2, 2008||Oct 9, 2008||Borislow Daniel M||Techniques for Populating a Contact List|
|US20080256612 *||Apr 13, 2007||Oct 16, 2008||Cognos Incorporated||Method and system for stateless validation|
|US20090019123 *||Jul 18, 2008||Jan 15, 2009||Rhonda L Childress||Session Management Enhancements for Instant Messaging Applications|
|US20090209224 *||Feb 20, 2008||Aug 20, 2009||Borislow Daniel M||Computer-Related Devices and Techniques for Facilitating an Emergency Call Via a Cellular or Data Network|
|US20100190466 *||Jan 27, 2009||Jul 29, 2010||Borislow Daniel M||Computer-Related Devices and Techniques for Facilitating an Emergency Call Via a Cellular or Data Network Using Remote Communication Device Identifying Information|
|US20110246559 *||Apr 5, 2010||Oct 6, 2011||Microsoft Corporation||Four tier architecture for implementing thin clients|
|US20120253894 *||Apr 22, 2011||Oct 4, 2012||Nokia Corporation||Method and apparatus for providing tag-based content installation|
|U.S. Classification||709/225, 709/203|
|International Classification||G06F9/44, H04L29/08, H04L29/06|
|Cooperative Classification||H04L67/02, G06F9/4443, H04L29/06|
|European Classification||G06F9/44W, H04L29/08N1, H04L29/06|
|Apr 19, 2001||AS||Assignment|
Owner name: INTEL CORPORATION, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HOOGENBOOM, PETER J.;IRELAND, RICHARD G.;BOGIA, DOUGLAS P.;REEL/FRAME:011730/0103;SIGNING DATES FROM 20010412 TO 20010415
|Sep 22, 2008||FPAY||Fee payment|
Year of fee payment: 4
|Sep 26, 2012||FPAY||Fee payment|
Year of fee payment: 8
|Nov 4, 2016||REMI||Maintenance fee reminder mailed|