System, method and computer program product for a user agent for pattern replay

FIELD OF THE INVENTION

[0001] The present invention relates to computer-related transactions, and more particularly to automating computer-related transactions.

BACKGROUND OF THE INVENTION

[0002] The Internet is composed of content distributed in the World Wide Web and various intranets. While a large fraction of the content is static, the truly interesting content is the one that a user can interact with dynamically. This content is of various types including, but not limited to (i) the content stored in various databases, (ii) e-commerce web-pages, (iii) directories, (iv) intranet pages, (v) data warehouses, etc.

[0003] The interaction with this dynamic content is accomplished through (i) queries/submissions to databases, (ii) buying/selling/interacting through e-commerce, (iii) running queries and lookups in directories, (iv) accessing and interacting with content resident on intranet pages (including on individual computers), and/or (v) accessing, interacting with, adding, subtracting or modifying content resident in data warehouses.

[0004] The access to or interaction with this dynamic content is done in a variety of ways. For example, such interaction may be accomplished through direct access to the databases by running specific commands or through form submissions on the Internet that run specific queries or perform specific actions. This interaction requires the submission of necessary parameters or information to complete a query or interaction (addition, modification, subtraction) with the dynamic content. This information may need to be submitted in multiple steps. Once the submission of information is finished, the results of the interaction/query/e-commerce are sent back to the user.

[0005] Each time a user wishes to interact in the foregoing manner, the user is required to carry out each and every one of the steps associated with the submission of necessary parameters or information. If a same type of transaction is to be carried out in a repeated manner, this may be very time consuming and problematic.

[0006] Accordingly, accessing web content is more complicated than simply making individual HTTP requests. The prior art has yet to enable fetching of the same content as the user and rendering it the same way the user saw it. To do this, the appropriate content must first be fetched across the network. It must then be rendered correctly.

[0007] When fetching the content, the user may first be required to log in or run a search for a certain term. More generally, the content of interest could be generated by an arbitrary web transaction. Logging in and running a search are all examples of web transactions. Thus, fetching content requires support for various authentication and network protocols, management of client-side state information as well as support for the appropriate cipher strength.

[0008] It should be noted that fetching any interactive web content requires the ability to be able to execute web transactions. In the case of non-interactive content (e.g. the top headlines from a news site), no transaction is required to retrieve the content. One simply has to request the page from the remote server. However, if any interaction is required to access that content (e.g. weather report for a particular zip code), the transaction must be executed before the content can be retrieved.

[0009] Web transactions vary in their complexity. They may be as simple as entering a zip code to receive a customized weather report. On the other hand, they may be complex enough to involve logging in to a secure stock trading site, browsing to a particular page on the site, submitting a query and then browsing to a specific section in the report to obtain the current credit rating of a company.

[0010] Rendering the content is also a challenging problem. To start with, there is no well-defined standard for how web pages should display. Identical HTML is often rendered differently by competing browsers. Secondly, even apart from standards disputes and ambiguities, one can never be entirely sure that one has rendered a page as intended by the page designer. The designer may not have intended it for display on certain resolutions. Furthermore, not all browsers and clients are equally capable.

[0011] The aforementioned problems are compounded when attempting to access and navigate websites using wireless devices. Most websites are not wireless enabled. Nor can most wireless devices access and retrieve content from the websites directly.

[0012] There is therefore a need to allow wireless enablement of any website to allow output of desired content on a wireless device in a format amenable to display on the wireless device. There is also a need for a method to render active content into a format amenable to display on a device that does not support active content.

[0013] There is also a need for a way to retrieves such content as a user's electronic “agent.” More particularly, what is needed is an electronic user agent that attempts to make reasonable compromises so that it can fetch and render popular web content correctly and with acceptable performance.

[0014] What is a further need a way to replay patterns so that active content can be output on a wireless device without requiring that the entire web page be displayed. There is also a need for a way to complete transactions on behalf of a user using a pattern, regardless of which state the website is in at the time the request is initiated. In other words, there should be a mechanism to recognize when a user strays from the pattern and reinitiate the pattern at the new state.

SUMMARY OF THE INVENTION

[0015] The present invention provides a User Agent that simulates a user's actions (logging in to a web site, for example) and returns the results of those actions (i.e. the resulting web pages) for further processing. In generally, the User Agent mimics human user actions as closely as possible web pages so that web pages can be rendered such that they will display correctly.

[0016] Accordingly, a system, method and computer program product are provided for User Agent operation. A network site is accessed utilizing a network. This can be done by navigating to a particular web site using its URL, for example. User interaction is simulated for navigating the network site based on client specifications (i.e., directions). An example of such navigation is logging in to a b site. The client is a process that makes requests to and receives output from the Use r Agent. A web page is retrieved from the site. Such content can be part or all of a web page, for example, such as the resulting page that is accessible upon logging in to a web site. Identifiers are assigned to elements of the web page. For example, the third element on the page could be assigned the ID “3”. The web page is rendered for further processing, which can utilize the identifiers. The rendering can include converting the resulting page into XHTML for processing by another system component and/or output on a user device. Dynamic content of the web page such as scripting is rendered before the page is returned to the client. Note that the dynamic content can include JavaScript. The rendered web page is returned to the client in a markup language, such as XHTML or XML for example. As noted above, the rendered content can be output to a user device, such as a wireless device. The wireless device can include a wireless telephone, Personal Digital Assistant (PDA), handheld computer such as a handheld PC, a pager, a device connected to a wireless modem, or any type of device capable of receiving information where at least one of the communication links is wireless.

[0017] In one aspect of the present invention, navigation from the web page is performed. For example, navigating from the web page can include of clicking links on a web page, submitting forms, and/or firing scripting events (clicking a link being a specific kind of event).

[0018] In another aspect of the present invention, the client is informed of changed frames. The User Agent is able to inform the client which frame(s) have changed since the last event was executed. Navigating to a specified URL would be considered an event in this context. Typically, this would be used by the client to determine which frames have changed since the last event was executed and it would then request only the modified frames. In a further aspect, specified frames are sent to the client. The User Agent is ideally able to send any frames which are requested to the client. Often, a web page will comprise a single frame. However, if the page comprises multiple frames, the User Agent is able to send a selected single frame (or a specified subset of the frames) to the client.

[0019] In a further aspect, a network interface is provided. A runtime engine can use a network interface to make requests to the User Agent. It uses the network interface to navigate the User Agent and to request the web pages from it. As an option, a Component Object Model (COM) interface can be provided. In a preferred environment, the User Agent is embedded as a COM object. The embedding program can then interact with the User Agent's browser directly. The embedding program may then also request the XHTML representations of the current web page loaded in the browser.

BRIEF DESCRIPTION OF THE DRAWINGS

[0020]FIG. 1 illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment;

[0021]FIG. 2 illustrates a system for navigating a network, including conducting transactions, in accordance with one embodiment of the present invention;

[0022]FIG. 3 is a flowchart of a process for User Agent operation according to an embodiment of the present invention;

[0023]FIG. 4 illustrates a flow of User Agent operation at design-time;

[0024]FIG. 5 shows the flow of User Agent operation at runtime;

[0025]FIG. 6 is a flow chart that illustrates a method for recording a pattern using the User Agent according to one embodiment of the present invention;

[0026]FIG. 7 illustrates a recording interface according to one embodiment of the present invention;

[0027]FIG. 8 illustrates a mode selection screen of the interface of FIG. 7;

[0028]FIG. 9 shows a field selection screen of the interface of FIG. 7;

[0029]FIG. 10 depicts a filter screen of the interface of FIG. 7;

[0030]FIG. 11 illustrates a results screen of the interface of FIG. 7;

[0031]FIG. 12 illustrates an assign variable screen of the interface of FIG. 7;

[0032]FIG. 13 shows the grid screen of the interface of FIG. 7;

[0033]FIG. 14 shows the grid screen of FIG. 13 with additional objects added;

[0034]FIG. 15 illustrates a display specification screen of the interface of FIG. 7 from which the user can specify the manner in which variables are displayed on particular devices;

[0035]FIG. 16 gives a general overview of how the PRE interfaces with other major components of the system according to one embodiment of the present invention;

[0036]FIG. 17 is a flowchart of a process for replaying a pattern for transitioning from one state to another state, according to an embodiment of the present invention;

[0037]FIG. 18 depicts a process for replaying a pattern for transitioning from one state to another state in a remote application, according to another embodiment of the present invention;

[0038]FIG. 19 is a flowchart of a method for identifying a dynamic element and replaying a dynamic event according to an embodiment of the present invention;

[0039]FIG. 20 illustrates a Connector class hierarchy according to one embodiment of the present invention;

[0040]FIG. 21 depicts a State class hierarchy according to one embodiment of the present invention;

[0041]FIG. 22 is a diagram illustrating how different components of the present invention can interact to support Scripting;

[0042]FIG. 23 depicts a process for recognizing a state based on a current output, according to one embodiment of the present invention;

[0043]FIG. 24 is a flow diagram of a process for recognizing a remote state utilizing individual document recognition, according to another embodiment of the present invention;

[0044]FIG. 25 is a flow diagram that illustrates the interaction between the XML Connector Module (XCM) and the Pattern Replay Engine (PRE);

[0045]FIG. 26 is a flow diagram of the operation of the XML Connector;

[0046]FIG. 27 is a flow diagram of SRM and IDT interaction; and

[0047]FIG. 28 depicts a program flow of the Connector.

[0048]<tables id="TABLE-US-00001" num="1"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="center" /><thead><row><entry /></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row><row><entry>DESCRIPTION OF THE PREFERRED EMBODIMENTS</entry></row><row><entry>Glossary </entry></row><row><entry namest="1" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="42PT" align="left" /><colspec colname="2" colwidth="175PT" align="left" /><tbody valign="top"><row><entry>action</entry><entry>An event which can be executed by the user or by script to</entry></row><row><entry /><entry>change the state of the remote application (thus changing</entry></row><row><entry /><entry>the state of the local application). For example, clicking a</entry></row><row><entry /><entry>link.</entry></row><row><entry>content</entry><entry>Any content. Also includes a sub-tree of a full DOM tree.</entry></row><row><entry>client</entry><entry>A process which makes requests to and, presumably, gets</entry></row><row><entry /><entry>web pages from the User Agent.</entry></row><row><entry>connector</entry><entry>An internal module of the platform, which can execute a</entry></row><row><entry /><entry>state in a pattern recorded by the IDT.</entry></row><row><entry>CRM</entry><entry>Content Retrieval Module, a component of the platform.</entry></row><row><entry>custom</entry><entry>An application created utilizing the platform</entry></row><row><entry>(local)</entry></row><row><entry>application</entry></row><row><entry>DOM</entry><entry>Document Object Model, a W3C standard for describing</entry></row><row><entry /><entry>XML documents in an object-oriented fashion.</entry></row><row><entry>DTD</entry><entry>Document Type Definition, a document used to define an</entry></row><row><entry /><entry>XML markup language. It contains the rules by which an</entry></row><row><entry /><entry>XML Document of the corresponding markup language is</entry></row><row><entry /><entry>constructed/validated.</entry></row><row><entry>element</entry><entry>An XML element. Everything from &lt;tag&gt; to &lt;/ tag&gt;</entry></row><row><entry>HTML</entry><entry>A component of the platform. Also called the XML</entry></row><row><entry>connector</entry><entry>connector. This component calls the User Agent directly.</entry></row><row><entry>IDT</entry><entry>Interactive Design Tool, the design tool of the platform.</entry></row><row><entry /><entry>Allows a user to create patterns and custom application</entry></row><row><entry /><entry>layouts.</entry></row><row><entry>pattern</entry><entry>A collection of states grouped together by a platform user to</entry></row><row><entry /><entry>be used as one functional element in the custom application.</entry></row><row><entry>platform</entry><entry>The platform of the system.</entry></row><row><entry>PRE</entry><entry>Pattern Replay Engine, a component of the platform that</entry></row><row><entry /><entry>replays patterns recorded by the IDT.</entry></row><row><entry>remote</entry><entry>An application, which exists on some remote site and has</entry></row><row><entry>application</entry><entry>some functionality of interest that the user of the platform</entry></row><row><entry /><entry>desires to extract from it. (For, example Yahoo Mail is a</entry></row><row><entry /><entry>remote web application).</entry></row><row><entry>remote state</entry><entry>Corresponds to a stable output from a remote application at</entry></row><row><entry>(remote</entry><entry>some point in time. (In case of Yahoo Mail, the login page</entry></row><row><entry>output)</entry><entry>is one state and the page, which displays the Inbox, is</entry></row><row><entry /><entry>another state.)</entry></row><row><entry>Session-</entry><entry>A class responsible for keeping track of active sessions and</entry></row><row><entry>Manager</entry><entry>associated data such as Patterns and Variables.</entry></row><row><entry>SRM</entry><entry>State Recognition Module, a component of the platform.</entry></row><row><entry /><entry>Provides state recognition and content retrieval</entry></row><row><entry /><entry>functionality.</entry></row><row><entry>state</entry><entry>State of the remote application as defined by the user of the</entry></row><row><entry /><entry>platform (the designer). (This will usually correspond to a</entry></row><row><entry /><entry>given remote state; however, since not all parameters of the</entry></row><row><entry /><entry>remote system are known, the local state cannot have all of</entry></row><row><entry /><entry>the information that is available to the remote state.) States</entry></row><row><entry /><entry>are contained within a Pattern (see definition).</entry></row><row><entry>step</entry><entry>A Step is part of a larger sequence of mappings to States.</entry></row><row><entry /><entry>The list of Steps serves as a history of the States traversed</entry></row><row><entry /><entry>by the PRE. The reason for using Steps is the user may go</entry></row><row><entry /><entry>“Back” to a previous State in the Pattern and initiate an</entry></row><row><entry /><entry>Action from that particular point in the traversal history.</entry></row><row><entry>UA</entry><entry>The User Agent, a component of the platform. Used to</entry></row><row><entry /><entry>fetch the output from a remote application and execute any</entry></row><row><entry /><entry>user actions on that output.</entry></row><row><entry>variable</entry><entry>Represents a value which the designer's scripting code can</entry></row><row><entry /><entry>manipulate. Variables can be one of the following three</entry></row><row><entry /><entry>scope types: User, Session, or Application. And the</entry></row><row><entry /><entry>Variable's underlying value can be one of three value types:</entry></row><row><entry /><entry>(1) Primitive (not strongly-typed) (e.g. int, string, boolean),</entry></row><row><entry /><entry>(2) Record (which is like a struct), and (3) Table (a list of</entry></row><row><entry /><entry>records).</entry></row><row><entry>web content</entry><entry>See content.</entry></row><row><entry>XHTML</entry><entry>Extensible HyperText Markup Language, an</entry></row><row><entry /><entry>XML-compliant version of HTML. XHTML is viewable on</entry></row><row><entry /><entry>major browsers.</entry></row><row><entry>XML</entry><entry>Extensible Markup Language, a syntax for creating SGML-</entry></row><row><entry /><entry>compliant markup documents. The rules by which a</entry></row><row><entry /><entry>document is constructed/validated can be specified via a</entry></row><row><entry /><entry>DTD or XML Schema. XHTML is an example of an XML</entry></row><row><entry /><entry>compliant markup language. XML documents may also be</entry></row><row><entry /><entry>created which do not correspond to an explicitly defined</entry></row><row><entry /><entry>schema. Such documents arc said to be well-formed if they</entry></row><row><entry /><entry>conform to the syntactical rules of XML, but their overall</entry></row><row><entry /><entry>structure can be arbitrary.</entry></row><row><entry>XML</entry><entry>An internal module of the platform, which can execute an</entry></row><row><entry>connector</entry><entry>Extensible Markup Language (XML) state in a pattern</entry></row><row><entry /><entry>recorded by the IDT. Also called the HTML connector.</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0049] Illustrative System Architecture

[0050]FIG. 1 illustrates a typical hardware configuration of a workstation in accordance with a preferred embodiment having a central processing unit <b>110</b>, such as a microprocessor, and a number of other units interconnected via a system bus <b>112</b>.

[0051] The workstation shown in FIG. 1 includes a Random Access Memory (RAM) <b>114</b>, Read Only Memory (ROM) <b>116</b>, an I/O adapter <b>118</b> for connecting peripheral devices such as disk storage units <b>120</b> to the bus <b>112</b>, a user interface adapter <b>122</b> for connecting a keyboard <b>124</b>, a mouse <b>126</b>, a speaker <b>328</b>, a microphone <b>132</b>, and/or other user interface devices such as a touch screen (not shown) to the bus <b>112</b>, communication adapter <b>134</b> for connecting the workstation to a communication network <b>135</b> (e.g., a data processing network) and a display adapter <b>136</b> for connecting the bus <b>112</b> to a display device <b>138</b>.

[0052] The workstation typically has resident thereon an operating system such as the Microsoft Windows NT or Windows Operating System (OS), the IBM OS/2 operating system, the MAC OS, or UNIX operating system. Those skilled in the art may appreciate that the present invention may also be implemented on platforms and operating systems other than those mentioned.

[0053]FIG. 2 illustrates a system <b>200</b> for navigating a network <b>202</b>, including conducting transactions, in accordance with one embodiment of the present invention.

[0054] A Request Handler (RH) <b>204</b> communicates with a user device <b>205</b>. The RH manages requests from the user device, routing them to the appropriate system component. When a user requests a transaction, the request is sent to a Pattern Replay Engine (PRE) <b>206</b>, which replays a pattern for conducting a transaction on behalf of a user. More information about the PRE is set forth below.

[0055] The State Recognition Module (SRM) <b>208</b> determines which state a website is in based on its current output, such as a structure of the current output. The SRM may communicate with a Content Recognition Module <b>210</b>, which recognizes individual documents that can comprise a state. A Connector <b>212</b> is in communication with the SRM. The Connector executes a state in the pattern. The SRM, Content Recognition Module, and connector are described in detail below. More information about operation and functionality of the Content Retrieval Module is found in US patent application entitled SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FOR RETRIEVING ARBITRARY CONTENT FROM A REMOTE DATA SITE FOR OUTPUT TO A DEVICE IN A FORMAT SUITABLE FOR THAT DEVICE, filed concurrently herewith and assigned to common assignee Clickmarks, Inc., and which is herein incorporated by reference.

[0056] The User Agent <b>214</b> is used by other components of the system to provide the actual interaction with a remote website. For example, when replaying a pattern, the SRM communicates with the User Agent via the Connector to provide instructions to the User Agent. The other system components have intelligence built into them that instructs them how to utilize the User Agent. For example, when a user clicks on a button on a page, other components instruct the User Agent to navigate to the desired web page and perform some action, such as filling in a form. The User Agent retrieves the resulting page and returns it to the other components.

[0057] By default, the User Agent is not running. A listener (not shown) listens for requests. When the listener receives a request, it creates a new User Agent process on the server and returns an identifier that identifies the User Agent process. Subsequently, client processes use the identifier, go to the specific User Agent and instruct it to perform some action. The User Agent performs the action according to the instructions and returns the results of the action.

[0058] A Transcoding Page Rending Engine (TRE) <b>216</b> renders content for display on the user device. Preferably, the TRE is able to render content on any display environment. More information about operation and functionality of the TRE is found in US patent application entitled SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FOR PAGE RENDERING UTILIIZING TRANSCODING, filed concurrently herewith and assigned to common assignee Clickmarks, Inc., and which is herein incorporated by reference.

[0059] In the present invention, a transaction preferably refers to communicating (i) information and/or actions required to conduct the transaction, and/or (ii) information and/or actions sent back or desired by the user, respectively.

[0060] For example, a transaction, in one embodiment, may refer to: information submitted by the user, actions taken by the user, actions taken by a system enabling the access of the user to the data, actions taken by the data to retrieve/modify content, results sent back to the user, and/or any combination or portion of the foregoing entities.

[0061] User Agent

[0062] The User Agent is able to fetch web pages of interest and render them correctly. The operation of the User Agent can be likened to remote controlling navigation of a browser on a remote server. For example, the User Agent acts as an intermediary on a remote server that can be commanded to go online and retrieve content, and then send it for rendering for output on a wireless device. The system component that renders the content for output on the wireless device is the Transcoding Page Rendering Engine (TRE).

[0063] The User Agent can be used both via a network interface and Interprocessor Communication (IPC). Furthermore, it has performance and scalability befitting a server application.

[0064]FIG. 3 is a flowchart of a process <b>300</b> for User Agent operation. In operation <b>302</b>, a network site is accessed utilizing a network. This can be done by navigating to a particular web site using its URL, for example. In operation <b>304</b>, a user interaction is simulated for navigating the network site based on client specifications (i.e., directions). An example of such navigation is logging in to a web site. The client is a process that makes requests to and receives output from the Use r Agent. A web page is retrieved from the site in operation <b>306</b>. Such content can be part or all of a web page, for example, such as the resulting page that is accessible upon logging in to a web site. In operation <b>308</b>, identifiers are assigned to elements of the web page. For example, the third element on the page could be assigned the ID “3”. The web page is rendered for further processing utilizing the identifiers in operation <b>310</b>. The rendering can include converting the resulting page into XHTML for processing by another system component and/or output on a user device. Note that XHTML is used herein by way of example; any other XML compliant format may be used; that is, if the page loaded by the User Agent is an XML page, as opposed to an HTML page, it is not converted to XHTML, but rather is passed on to the client in its original XML format. In operation <b>312</b>, dynamic content of the web page such as scripting is rendered utilizing the identifiers. The rendered web page is returned to the client in operation <b>314</b>. As noted above, the rendered content can be output to a user device, such as a wireless device. The wireless device can include a wireless telephone, Personal Digital Assistant (PDA), handheld computer such as a handheld PC, a pager, a device connected to a wireless modem, or any type of device capable of receiving information where at least one of the communication links is wireless.

[0065] In one aspect of the present invention, navigation from the web page is performed. For example, navigating from the web page can include of clicking links on a web page, submitting forms, and/or firing scripting events (clicking a link being a specific kind of event).

[0066] In another aspect of the present invention, the client is informed of changed frames. The User Agent is able to inform the client which frame(s) have changed since the last event was executed. Navigating to a specified URL would be considered an event in this context. Typically, this would be used by the client to determine which frames have changed since the last event was executed and it would then request only the modified frames. In a further aspect, specified frames are sent to the client. The User Agent is ideally able to send any frames which are requested to the client. Often, a web page will comprise a single frame. However, if the page comprises multiple frames, the User Agent is able to send a selected single frame (or a specified subset of the frames) to the client.

[0067] In a further aspect, a network interface is provided. A runtime engine can use a network interface to make requests to the User Agent. It uses the network interface to navigate the User Agent and to request the web pages from it. As an option, a Component Object Model (COM) interface can be provided. In a preferred environment, the User Agent is embedded as a COM object. The embedding application can then interact with the User Agent's browser component directly. It may then also request the XHTML representations of the current web page. Again, XHTML is used herein by way of example, and any other XML compliant format can be used.

[0068] Module Dependencies

[0069] The User Agent module is not required to use other modules from the platform. It is used by the HTML connector and the IDT.

[0070] Technologies Used

[0071] The User Agent is preferably a Windows application. It can use COM and standard Microsoft browser libraries (i.e. MSHTML.DLL). In addition, it can use standard libraries for common functionality (e.g. HTTP communication).

[0072] Functionality

[0073] The User Agent is able to fetch the web pages and render them “correctly”. While there is no universally agreed upon definition of “correct”, the User Agent attempts to conform to de facto standards. The User Agent acts, to the degree possible, like a web browser running on a desktop machine and operated by a single user. Broadly speaking, a preferred embodiment of the User Agent:

[0074] satisfies all protocol requirements (e.g. HTTP, FTP, SSL and TLS),

[0075] supports all technologies of interest (e.g. JavaScript, VBScript),

[0076] renders pages in a generally accepted manner

[0077] shares no state information with any other User Agent instance.

[0078] Remote web sites should not be able to determine whether they are interacting with a human user on a dedicated machine or the User Agent. For example, two different User Agents running on the same server should be able to simultaneously log-in to Hotmail using two different user names (and get two different pages).

[0079] Constraints

[0080] The User Agent as described herein is designed for use at design-time and runtime. The two usage scenarios impose different constraints.

[0081] Design-Time Usage

[0082] At design-time, the User Agent is run locally on the designer's machine (embedded directly in the Development Tool (DT) used by the designer). It exposes the browser interface directly to the DT. See also FIG. 4 and the related discussion below for more information.

[0083] Runtime Usage

[0084] At runtime, the User Agent is run remotely on a dedicated server. A network interface is exposed so that remote clients can interact with the UA. HTTP can be used to provide this interface. As it is a very widely used protocol, it allows for a very flexible system design (as many diverse clients can speak HTTP) and there are a plethora of standard tools (e.g. performance auditing, load balancing, security tracking) available for it. See also FIG. 5 and the related discussion below for more information.

[0085] Two Interface Methods: HTTP and COM

[0086] The User Agent can support a COM interface so that it can be embedded into the DT at runtime. It can also support an HTTP interface so that it can be used by remote clients at runtime.

[0087] Performance and Scalability

[0088] The User Agent can be used primarily as a server-side application which services client requests. Each User Agent server is able to support several hundred simultaneous users with acceptable response time. In addition, it is possible to increase the number of users which can be reasonably supported by adding more hardware to the server set-up.

[0089] Functionality

[0090] Abstraction

[0091] The User Agent is able to navigate to a desired web page (rendering any dynamic content) and then send an XHTML representation of the rendered web page (which may comprise several frames) to the client. It also allows for the client to be able to direct it to a specified URL, click links, submit forms and fire scripting events on the page. Preferably, it is able to: Note that XHTML is used herein by way of example, and any XML compliant format can be used.

[0092] 1. Navigate to a specified URL and retrieve the associated page over the network. This is the process of actually making network requests and receiving responses. It involves handling all required network protocols, including protocol requirements such as maintaining client-side state information (e.g. HTTP cookies) and having appropriate security certificates.

[0093] 2. Render those pages, tag them and convert them to XHTML. Once the page has been fetched, any dynamic elements (e.g. scripting) are rendered in XHTML for output on the device. While JavaScript is the scripting language of choice, any common scripting language (such as VBScript) could be used. The User Agent also generates and assigns unique IDs to each element on the page. It can use the integer indices of the elements on the page for the IDs (starting from one). For example, the third element on the page would be assigned the ID “3”. It then converts the resulting page into XHTML if it is an HTML page. To render a page, the UA executes any scripting which is to be executed upon the page loading (prior to any user actions). Any scripting which is run as a result of a user action (for example, onMouseOver) is not executed at this point.

[0094]  Preferably, no scripting is removed or modified from the page. Thus, if a naïve client loads the page into a script-capable browser, it will then execute any automatic events twice. In addition, if an event is fired, whatever script would have been originally called is executed. If the client wishes to modify these events (so that, for example, onClick calls a script of the client's choice instead of the original script), the client modifies the script.

[0095] 3. Navigate from the current web page as specified by other Platform components. This includes clicking links on a web page, submitting forms and firing scripting events. This comprises two parts: filling in forms and firing events (clicking a link being a specific kind of event). Given a specified event (complete with all the parameters needed to execute that event, including the element on which the event is to be fired), the User Agent executes the event on the web page. Typical events include onClick and onSubmit.

[0096] 4. Inform the client of changed frames—The User Agent, upon request, informs the client which frame(s) have changed since the last event was executed. Navigating to a specified URL can be considered an event in this context. Typically, this would be used by the client to determine which frames have changed since the last event was executed and it would then fetch only the modified frames.

[0097] 5. Send specified frames to client—The User Agent can be able to send any frames which are requested to the client. Often, a web page will comprise a single frame. However, if the page comprises multiple frames, the User Agent is able to send only a single frame (or a specified subset of the frames) to the client.

[0098] 6. Provide a network interface. The runtime engine uses a network interface to make requests to the User Agent. It uses the network interface to navigate the User Agent and to request the web pages from it.

[0099] 7. Provide a COM interface. The design-time environment can embed the User Agent as a COM object. It is then able to interact with the browser directly. It may then also request the XHTML representations of the current web page.

[0100] 8. Support scaling easily to multiple server configurations. It is possible to add servers to a UA server farm easily, quickly and without any of interruption of service.

[0101] The following sections detail the HTTP interface and the COM interface.

[0102] HTTP Interface

[0103] When running in server mode, the User Agent exposes an HTTP interface. Clients can create new sessions, control existing sessions, retrieve the content of various web pages and terminate sessions via the HTTP interface.

[0104] Session Creation

[0105] Clients make HTTP POST requests to a well-known URL (e.g. http://user_agent:80) to spawn new UA instances. A new UA instance is spawned and assigned a port number. The body of the response contains the server name and this newly assigned port number. The concatenation of the protocol used, the server name and the port number are called the assigned URL. Clients can then make future requests to the assigned URL.

[0106] Clients may specify a timeout period (in seconds) in the body of the response. If the UA instance does not receive any requests in the specified period, it self-terminates. If no timeout period is specified, the UA instance times out after a pre-configured maximum wait period.

[0107] Session Termination

[0108] To terminate a UA session, the client sends a termination request to the specific UA instance it wishes to terminate. After that instance has been terminated, the client should no longer communicate with the specified server and port. The port number may be recycled for future UA sessions.

[0109] Session Control

[0110] To interact with the User Agent, a client makes HTTP POST requests to the assigned URL. The body of the request contains the method it wishes to invoke, along with any parameters required for that method. Available methods are listed below in Table 1. <tables id="TABLE-US-00002" num="2"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="49PT" align="left" /><colspec colname="2" colwidth="168PT" align="left" /><thead><row><entry namest="1" nameend="2" align="center">TABLE 1</entry></row><row><entry /></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Method</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>goToURL</entry><entry>Parameters: The absolute URL which the User Agent</entry></row><row><entry /><entry>goes to.</entry></row><row><entry /><entry>Actions: The User Agent goes to the URL specified. This</entry></row><row><entry /><entry>method returns immediately. It does not wait until</entry></row><row><entry /><entry>successfully fetching and rendering the page until it</entry></row><row><entry /><entry>returns. This is to improve performance (the client does</entry></row><row><entry /><entry>not get blocked an HTTP POST request while</entry></row><row><entry /><entry>waiting for the User Agent to finish getting the page).</entry></row><row><entry /><entry>Returns: Success or failure code</entry></row><row><entry>navigate</entry><entry>Parameters: XML encoding of a series of valid</entry></row><row><entry /><entry>navigation-related actions. There are two types of actions</entry></row><row><entry /><entry>that may be performed: filling form fields and firing</entry></row><row><entry /><entry>events (see below for details). There are two</entry></row><row><entry /><entry>“sub-methods” for navigate.</entry></row><row><entry /><entry>fillFormField [field locations and values]—Fills out the</entry></row><row><entry /><entry>specified fields with the specified data. The client</entry></row><row><entry /><entry>specifies the location of the field and the value to assign</entry></row><row><entry /><entry>to that field. The location comprises the frame in which</entry></row><row><entry /><entry>the target form resides and the element ID of the field in</entry></row><row><entry /><entry>the frame. The client may specify multiple fields in</entry></row><row><entry /><entry>multiple forms in multiple frames in a single request.</entry></row><row><entry /><entry>fireEvent element_ID event [event parameters]—Fires</entry></row><row><entry /><entry>the specified event on the specified element with the</entry></row><row><entry /><entry>specified parameters. Note: Clicking a link is also an</entry></row><row><entry /><entry>event.</entry></row><row><entry /><entry>Actions: The User Agent executes the actions specified.</entry></row><row><entry /><entry>The client may specify zero or more of either type of</entry></row><row><entry /><entry>action in the sequence of their choice. However, the UA</entry></row><row><entry /><entry>only guarantees execution up to an event which causes a</entry></row><row><entry /><entry>page transition. So, for example, if the client tells the UA</entry></row><row><entry /><entry>to click the “Search” button on Google and,</entry></row><row><entry /><entry>subsequently, tells it to enter some string in the text field,</entry></row><row><entry /><entry>the UA will click the “Search” button, detect a page</entry></row><row><entry /><entry>change and ignore the rest of the input. Thus, the client</entry></row><row><entry /><entry>should specify actions in the order in which they are</entry></row><row><entry /><entry>intended to be taken.</entry></row><row><entry /><entry>Returns: Success or failure code</entry></row><row><entry>changedFrames</entry><entry>Parameters: None</entry></row><row><entry /><entry>Actions: None</entry></row><row><entry /><entry>Returns: Indicates if all frames changed or only some</entry></row><row><entry /><entry>frames changed. Returns the IDs of the frames which</entry></row><row><entry /><entry>changed since the last request in the latter case and all</entry></row><row><entry /><entry>frame IDs in the former case.</entry></row><row><entry>getOrigHTML</entry><entry>Parameters: The ID of the frame of interest</entry></row><row><entry /><entry>Actions: None</entry></row><row><entry /><entry>Returns: The original, un-rendered HTML of the</entry></row><row><entry /><entry>specified frame</entry></row><row><entry>getXHTML</entry><entry>Parameters: The ID of the frame of interest</entry></row><row><entry /><entry>Actions: None</entry></row><row><entry /><entry>Returns: The XHTML representation (with element ID's</entry></row><row><entry /><entry>inserted in each tag) of the rendered HTML of the</entry></row><row><entry /><entry>specified frame. Separate frames are requested in</entry></row><row><entry /><entry>separate requests.</entry></row><row><entry>terminate</entry><entry>Terminates the UA instance</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0111] COM Interface

[0112] The COM interface exposes two methods: getXHTML and getIBrowser. These are described in Table 2. <tables id="TABLE-US-00003" num="3"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="1" colwidth="42PT" align="left" /><colspec colname="2" colwidth="175PT" align="left" /><thead><row><entry namest="1" nameend="2" align="center">TABLE 2</entry></row><row><entry /></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row><row><entry>Method</entry><entry>Description</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry>getIBrowser</entry><entry>Parameters: None</entry></row><row><entry /><entry>Actions: None</entry></row><row><entry /><entry>Returns: A handle to the COM browser interface IBrowser</entry></row><row><entry>getXHTML</entry><entry>Parameters: The ID of the frame of interest</entry></row><row><entry /><entry>Actions: None</entry></row><row><entry /><entry>Returns: The XHTML representation (with element ID's</entry></row><row><entry /><entry>inserted in each tag) of the rendered HTML of the specified</entry></row><row><entry /><entry>frame. Separate frames are requested in separate requests.</entry></row><row><entry namest="1" nameend="2" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0113] Design

[0114] Component Overview

[0115] A complete UA server setup involves several components. Namely, the load balancer, the instance manager and the User Agent itself. Not all of these components are necessarily used at both design-time and runtime. The components are first enumerated and described individually. Subsequent sections describe how they are used at design-time and runtime.

[0116] Installer

[0117] The installer program should install all code necessary for the correct functioning of the User Agent. In addition, it should do any configuration necessary for the correct and efficient functioning of the User Agent. This includes, but is not necessarily limited to, the following:

[0118] Changing the Internet Explorer settings so that images are not loaded by default.

[0119] Setting the number of network handles and other server resources which may be required to optimize performance.

[0120] The Load Balancer

[0121] The load balancer is a standard web server hardware load balancer. It acts invisibly as a relay between clients and individual UA servers. It receives HTTP requests from clients and routes those requests to the server with the least load and routes the responses back to the client. It determines load by the number of active HTTP connections each server has. Servers with more active connections are considered to have a heavier load.

[0122] This entire process is completely invisible to the client. The load balancer operates on OSI layer <b>3</b>. Neither the client nor the server need have any knowledge of its existence. The domain portion of the URL to which the client makes requests will point to the load balancer. The load balancer then acts as an intermediary for that HTTP transaction, sending the response from the server back to the client. This is the only request for that session which will be serviced by the load balancer. From this point on, clients will communicate directly with the User Agent instance assigned to them on the server which ended up servicing their rerouted request.

[0123] The Instance Manager

[0124] The instance manager is a daemon (“service” in Windows terminology) which spawns new UA instances when it receives an HTTP POST request to do so. It then informs the newly spawned UA instance and the client of the port which they should subsequently use to communicate with each other. It may choose any available port for this purpose.

[0125] It also passes the body of the HTTP request to the new UA instance. Any parameters which are to be passed to the UA are contained in this body.

[0126] This is the only request for that session which will be serviced by the instance manager. From this point on, clients will communicate with the UA instance directly via the assigned port. Once the instance terminates, the instance manager may recycle the port for use by another instance.

[0127] When it receives a request, the Instance Manager should check to see that sufficient server resources are free to service the request without severely degrading server performance (in extreme cases, causing thrashing or crashing the server). Memory is the most obvious resource in question. However, if any other resources turn out to be severe bottlenecks, they should also be checked. If sufficient resources are not free, the request should be denied and the client should be sent an informative message indicating why the request was denied.

[0128] The User Agent

[0129] The User Agent is the actual application that does the majority of the work. It does not run by default. The instance manager spawns new UA instances in response to requests. The high-level functionality and interface of the UA has been discussed above. To summarize briefly, the UA's main purpose is to fetch and render web pages and return their XHTML or XML representation to the client.

[0130] Design-Time Operation

[0131]FIG. 4 illustrates a flow <b>400</b> of User Agent <b>402</b> operation at design-time. Design-time operation is relatively simple from a User Agent point of view. As shown, the IDT <b>404</b> simply instantiates the COM object UserAgent. The COM interface <b>406</b> exposes two methods (discussed earlier). getXHTML returns the XHTML representation of the current page. getIBrowser returns a handle to the IBrowser object. The HTTP interface <b>408</b> is shown in dotted lines because it is unused at design-time.

[0132] In effect, the UA acts like a normal browser embedded in the IDT with the sole exception that it offers a method to get the XHTML representation of the page (with element IDs inserted in each tag). It is the responsibility of the IDT to use the browser object to achieve its desired functionality. In particular, it can trap any and all events in browser (including user events such as a right-clicking). It can also access the DOM tree of the current page either for inspection or modification.

[0133] Runtime Operation

[0134]FIG. 5 shows the flow <b>500</b> of User Agent operation at runtime. Runtime operation involves nearly all of the components used at design-time (although the COM interface of the UA is not used). The load balancer receives client requests and routes them to quickest server <b>502</b>. The instance manager <b>504</b> runs as a daemon on the UA servers. Upon receiving a request, they spawn a new UA instance. Clients <b>506</b> then communicate directly with the this new UA instance. The COM interface is shown in dotted lines because it is not used at runtime.

[0135] Pattern Recording and Replay

[0136] The Platform gives its users the ability to create (record) functional elements called patterns and use those elements (replay) in their custom applications. A pattern consists of a collection of states (see Glossary) and states can be of different types. For example, an action that requires accessing the World Wide Web can be represented by an XML (or other type) state and an action that would require sending e-mail can be a part of an SMTP state. Each type of state has a dedicated connector, which is used to create the state definitions and operate on those states. Thus, an XML Connector Module (XCM) is the connector that aids in recording and replaying of XML states. A database connector is used to store and retrieve data from a database, but may not point to a next state. An XML Connector points to a next table. For example, the XML Connector in state A would instruct the UA to execute action X to access state C. Note that the PRE deals with any state, such as a database state (e.g., Yahoo inbox stored in a database).

[0137]FIG. 6 is a flow chart <b>600</b> that illustrates a method for recording a pattern using the User Agent. In particular, the user performs the desired navigation and associated input, which are recorded. In operation <b>602</b>, the user is sent a request for a URL. Upon receiving the URL from the user, the URL is sent to the User Agent in operation <b>604</b>. The User Agent parses the request in operation <b>606</b> to determine a meaning of the request. In operation <b>608</b>, the User Agent retrieves the web page associated with the URL and sends it back to the user. This (and other) web pages are represented in the pattern as States. In operation <b>610</b>, actions are received from the user. Such actions can include selection of links, input of data in fields, etc. The User Agent receives the user input in operation <b>612</b>, and in operation <b>614</b>, executes the actions on the remote website. The actions are recorded in operation <b>616</b>. The resulting web page is shown the to the user in operation <b>618</b>. The user then identifies the parts of the page he or she is interested in, which is received in operation <b>620</b>. The identified parts are recorded in operation <b>622</b>.

[0138] The system now knows how to retrieve desired information using the pattern. Accordingly, all users using the system can obtain that content. The next (or same) user that wants to perform a similar action enters the URL and the pattern is replayed with the User Agent executing the actions received of operation <b>614</b>. The parts of the web page that were identified by the user and stored in operation <b>620</b> are returned to the user. The user can also define a default area to access in the event that a state is not recognized. See also the description below regarding state identification based on content and probability.

[0139] The information stored in a pattern may involve (i) the web or non-web interfaces presented to the user, (ii) the actions performed by the user or the system in the submission of the information, (iii) the parameters required to complete the transaction and submitted by the user, (iv) the automatic or manual navigation of the user within the transaction process, and/or (v) the content or results returned by the system or selected by the user.

[0140] A transaction pattern for any transaction need only be recorded once by anyone with sufficient system access privilege. Once recorded, any user may conduct that transaction, any number of times, by the invocation of the recorded transaction, or “transaction macro.”

[0141] Since a transaction macro can be stored in any fashion and invoked, directly or indirectly, by any agent (human or automated), it enables the completion of the transaction it describes in any fashion from any device.

[0142] As an example of use, suppose the user goes to Amazon.com and wants to search for books about Java. A User Agent performs a search for the books and a predetermined number of results are output. The Buy and Buy Later buttons are output along with the results. The user is allowed to select one of the books. The User Agent retrieves additional information about the book (by following a link, for example). If the user clicks on the Buy button, the User Agent follows a pattern to purchase the book automatically by filling in the appropriate information, including pre-stored user address information and credit card information. A Purchase Completed page is shown to the user stating that the book has been purchased.

[0143] Exemplary Pattern Recording Interface

[0144] According to a preferred embodiment of the present invention, pattern recording is done through an intuitive interface that allows the user to quickly and easily record patterns. More particularly, the interface allows creation of an application for retrieving a variable from a database as well as creation of an interface for displaying the variable on a particular type and/or model of device.

[0145]FIG. 7 illustrates a recording interface <b>700</b>. As shown, a grid screen <b>702</b> is provided. It is here that the graphical representation of an application for retrieving data from a data site is displayed. An Object Bar <b>704</b> allows insertion of connectors and shapes into the grid screen. A Catalog Bar <b>706</b> displays several types of specialized connectors and components. One specialized connector is the database connector <b>708</b> representing a connection to a database. Selection of the tabs on the Catalog Bar displays different connectors and components. The items in these bars can be dragged and dropped into the grid screen and connected with connectors from the Object Bar. The Project Bar <b>710</b> shows the names and types of variables being manipulated. Variables can be added by using a wizard, which starts upon selection of the wizard button <b>712</b>.

[0146] The following example illustrates creation of an application for retrieving a customer identifier (ID) from a database and creating an interface for displaying the customer ID on a particular type and/or model of device. As will be discussed in the example, the recording interface allows creation of different interfaces for different devices based on the capabilities of each.

[0147] Referring again to FIG. 7, a start screen <b>714</b> is displayed upon selection of the wizard button. The database server is selected from the drop down menu <b>716</b> and the Next button is selected. A database selection screen (not shown) is presented, which allows the user to select the desired database from which the desired data is to be retrieved.

[0148]FIG. 8 illustrates a mode selection screen <b>800</b>. Here, the user is allowed to select step by step mode or advanced mode. The desired mode is chosen and the Next button is selected. In this example, the step by step mode is shown.

[0149]FIG. 9 shows a field selection screen <b>900</b>. The tables of the selected database are presented in the drop down menu <b>902</b>. The user is allowed to select which table to view. The fields of the selected table are presented in the fields display portion <b>904</b>. The user is allowed to select one or more fields from the field display portion. Note, multiple fields can be chosen using CTRL+R-click. The Next button is selected.

[0150]FIG. 10 depicts a filter screen <b>1000</b>, which allows entry of filtering elements used to restrict the variables retrieved from the database. As shown, the field chosen in the field selection screen is displayed in the Field column <b>1002</b>. Operands can be entered into the Operator column <b>1004</b> (or chosen from a drop down menu). Illustrative operands include &gt;, &lt;, ≧, ≦, and =. The Value column <b>1006</b> receives comparison values, to which the variables associated with the field are compared using the operand. The Next button is selected.

[0151]FIG. 11 illustrates a results screen <b>1100</b> displaying the results of the query in a results portion <b>1102</b>. The query is also displayed in a query portion <b>1104</b>. The query may be edited in the query portion to change the results returned. The Execute button <b>1106</b> is selected to re-execute the query and retrieve results of the edited query. The Next button is selected.

[0152]FIG. 12 illustrates an assign variable screen <b>1200</b>. Here, the results are assigned to a variable and saved for later use. The name of the variable is entered in the Variable Name field <b>1202</b>. In this example, the variable is named “customer.” The Next button is selected.

[0153]FIG. 13 shows the grid screen <b>700</b>. The new variable “customer” now appears in the Project Bar <b>710</b>. A Database Connector <b>1302</b> is dragged from the Catalog Bar, as is a Select Query object <b>1304</b>. A connector <b>1306</b> is dragged and dropped from the Object Bar to the grid screen and used to connect the Database Connector and the Select Query object.

[0154]FIG. 14 shows the grid screen with additional objects added. Here, a Start Process object <b>1402</b>, an Output object <b>1404</b>, an End Process object <b>1406</b>, and connectors have been added.

[0155]FIG. 15 illustrates a display specification screen <b>1500</b> from which the user can specify the manner in which variables are displayed on particular devices. As shown, various devices are shown in a tree structure. A type of device is selected, here the Palm V version of the PDA. A representation <b>1502</b> of the PDA is displayed. The identifier “customer” <b>1504</b> is added to the simulated display <b>1506</b> of the PDA. The variable field <b>1508</b> is also added to the display. During runtime, the actual result of the query is displayed in place of the identifier and variable field. Text may also be added for output in this screen. Here, the words “Customer ID:” <b>1510</b> have been added.

[0156] For example, a website may have a table having an output with five columns. On a PDA, perhaps only four columns can be displayed on the display. The output can be set to only show four variables. Similarly, if only two columns of the table can be displayed on a phone, the output van be set to show only two variables.

[0157] Pattern Replay Engine

[0158] The Pattern Replay Engine (PRE) is the component of the platform that is responsible for replaying a pattern from one particular state to another during runtime.

[0159]FIG. 16 gives a general overview of how the PRE <b>1602</b> interfaces with other major components including the Input Handler <b>1604</b>, session manager <b>1606</b>, connector b<b>0008</b> (discussed in detail below), and TRE <b>1610</b>.

[0160] The PRE is a request-driven component. The PRE takes the request to make a transition from a particular State. Transitions from one State to another are made by executing Actions. The PRE communicates with the appropriate Connector (of the current State) to execute the current Action in the request and get the new resulting State. Next, all Script associated with the State, except for OnDestroy( ), is evaluated.

[0161] The PRE then calls the Transcoding Page Rendering Engine (TRE) to “flush” its output to the device. This means that any Content, which has been queued for display in the TRE (while processing the request), is sent to the device. Every state can potentially generate output to be displayed on the device, including internal states. This is a desirable feature as it means the designer can send a status message to the device, e.g. “Please wait while processing.” etc. The TRE may have to be reset every time, i.e. after a “flush” which flushes any queued output to the device, the TRE has to be ready to start building up a whole new display.

[0162] Finally, the State's OnDestroy( ) script is called, which can initiate further State transitions from this script method if necessary.

[0163]FIG. 17 is a flowchart of a process <b>1700</b> for replaying a pattern for transitioning from one state to another state, according to an embodiment of the present invention. A request to transition from a current state in a pattern to a new state is received in operation <b>1702</b>. A state can be defined as the state of a remote application as defined by the user. A pattern is a collection of states to be used as one functional element in an application. In operation <b>1704</b>, information about transitioning between the states from the current state to the new state is retrieved from the pattern. Scripting code of the current state is evaluated in operation <b>1706</b> to determine what action or actions are to be performed/executed in order to effect the transition to the new state. In operation <b>1708</b>, an action (or actions) is executed using the scripting code for effecting the transition from the current state to the new state. An example of an action is clicking on a link. The new state is rendered and output to a user device in operation <b>1710</b> and <b>1712</b>, respectively.

[0164] Preferably, the action is executed by communicating with a connector in communication with the appropriate state for executing the action. Also preferably, each type of state has a dedicated connector.

[0165] In another aspect of the present invention, each of the states generates output for display on the user device.

[0166] In a further aspect of the present invention, a further state transition is initiated and the process is repeated. Preferably, a history of states in the pattern that been traversed is maintained. Ideally, a state traversed out of sequence is detected. If it is determined that the incoming request is “out of Step”, then a determination is made as to what point in the history the request is coming from. Then a special Back event is sent to the appropriate Connectors in order to “back up” to that State. For example, Step 1 could represent the login page for Yahoo mail. The user then proceeds to the Inbox page (Step 2), and subsequently to a specific mail message (Step 3). If the user clicks “Back” twice on their device browser, the browser could simply render the cached pages for Step 2 and Step 1. Then the user could initiate another login from Step 1. The present invention would detect that the user has gone back in sequence (since the Step ID is part of the request) and would respond as described above.

[0167] In one embodiment of the present invention, the transaction pattern may include a record of: information submitted by a user, actions taken by the user, actions taken by a system to generate results, and results sent to the user. As an option, the transaction pattern may include a record of actions taken by the system which enable access of the user to data, and actions enabled by the data to retrieve content. Storage may take any form with sufficient identification and description of any required step in the transaction process.

[0168]FIG. 18 depicts a process <b>1800</b> for replaying a pattern for transitioning from one state to another state in a remote application, according to another embodiment of the present invention. In operation <b>1802</b>, a request to transition from a current state in a pattern to a new state is received. The states correspond to current and new states of a remote application. In operation <b>1804</b>, an action is executed for effecting the transition from the current state in the remote application to the new state in the remote application utilizing the pattern. An example of an action is clicking on a link. Note that the action can be executed by a user or by script. An output from the new state is generated and output to a user device in operations <b>1806</b> and <b>1808</b>.

[0169] In one aspect of the present invention, the action is executed by communicating with a connector associated with the state for executing the action. Preferably, each type of state has a dedicated connector. Also preferably, each of the states generates output for display on the user device.

[0170] A further state transition can be initiated. Likewise, a history of states in the pattern that been traversed can be maintained. Preferably, a state traversed out of sequence is detected.

[0171] During use of the present invention, such transaction pattern may be retrieved from memory when desired. Thereafter, the transaction pattern is executed to carry out the transaction in an automated manner. An execution, or playback may include the invocation of a stored transaction pattern.

[0172] The various operations that may occur during execution of a transaction pattern may involve: (i) a direct or indirect retrieval of the transaction pattern by an automated and/or programmable agent, i.e. a computer server/client, an active or dormant program, a human being, etc. (ii) an automatic or user prompted submission of the required parameters in every step of the transaction process, (iii) the automatic navigation within the transaction process, (iv) a retrieval of the content returned by the system or specified by the user, and/or (v) the relaying of the content back to the user.

[0173]FIG. 19 is a flowchart of a method <b>1900</b> for identifying a dynamic element and replaying a dynamic event according to an embodiment of the present invention: This method is preferably carried out by the User Agent in conjunction with the Pattern Replay Engine and State Recognition Module. A web browser is hosted in operation <b>1902</b>. In operation <b>1904</b>, a web page of a network site is rendered using the web browser so that it is in the form the user would see it. This allows the User Agent to identify dynamic elements based on its visual properties, including text labels, positioning, etc. A dynamic element with pre-specified properties is identified on the rendered web page in operation <b>1906</b>. Such an element could be a “Buy” button on the web page. In operation <b>1908</b>, the identified element is executed based on a prerecorded pattern. A web page resulting from execution of the element is output in operation <b>1910</b>. This method overcomes the disadvantages of attempting to understand the source (e.g., HTML) of the content. Rather, particular elements can be identified by their properties, even though the elements have changed form. For example, the “Buy” button may have changed to a different type of icon or even an animated graphic. Regardless, the present invention is able to identify the element and execute it.

[0174] More information regarding pattern recording and replay is provided in co-pending Provisional U.S. patent application entitled SYSTEM, METHOD AND COMPUTER PROGRAM PRODUCT FOR THE RECORDING AND PLAYBACK OF TRANSACTION MACROS, filed Apr. 12, 2001 under serial No. 60/283,781 and assigned to common assignee, Clickmarks, Inc., and which is incorporated herein by reference

[0175] Connector Plugin Support

[0176]FIG. 20 illustrates a Connector class hierarchy <b>2000</b>. The Platform uses Connectors to provide specific functionality for interacting with a remote application. See State Recognition Module and Connector below. A standard interface <b>2002</b> is defined for the Connector and its associated classes <b>2004</b>, <b>2006</b> such as Connector-specific State information classes.

[0177]FIG. 21 depicts a State class hierarchy <b>2100</b>. In the XML description of the Pattern, all possible States are defined, including State information which is generic and State information which is specific to the Connector.

[0178] An interface <b>2100</b> is defined. A public StateImpl (implementation object) <b>2102</b> is provided to subclass from. All Connectors have a “createState( )” method which creates a State object which is specific to the Connector. This makes the design clean so that the PRE does not need to instantiate Connector-specific State objects (e.g. HTMLStateImpl <b>2104</b>) itself.

[0179] Scripting

[0180] The PRE evaluates scripting code associated with each State. The user's script can be written in JavaScript (which is specified by the designer using the IDT). The script has access to the Platform's Scripting API.

[0181] Script Event Methods

[0182] There are five preferred Scripting methods which are called when a State is entered:

[0183] OnInit( . . . ): method called when the PRE first enters the State. Used to perform any initial processing.

[0184] OnData&lt;contentID&gt;( ): group of methods called to extract and manipulate the content Data retrieved by the Connector as it becomes available. There is a separate ‘OnData’ function for each content data item of interest. Each JavaScript function name is distinguished by a suffix consisting of the content ID. Using the Scripting API, the Data can be stored in Variables and/or in Content UI objects for rendering on the device.

[0185] OnDataComplete( ): single method called when all the data content retrieval has been completed.

[0186] OnDestroy( ): last script method called. Typically used for cleanup and to explicitly execute one or more Actions and/or to initiate a State transition (using the Scripting API). See the Executing Actions Via Script section for more details.

[0187] OnError( ): method called when PRE is unable to normally process the State for any particular reason. (It does not get called when an Action-execution results in a new State—in this case, the ‘catch’ code within the script gets called.)

[0188] Invoking the Transcoding Page Rendering Engine (TRE)

[0189] The TRE's ‘flush’ method is called to output to the device any content that has been rendered. This method is called every time a State transition occurs. Specifically, it is called after the OnDataComplete( ) method but before the OnDestroy( ) method.

[0190] Executing Actions via Script

[0191] In the OnDestroy method, the user can explicitly execute an Action.

[0192] Exposed Scripting Functionality

[0193] In addition to having the core JavaScript language available, the Scripting code can take advantage of powerful functionality via the Scripting API and by importing and calling methods on special Scripting objects provided by the PRE.

[0194] Scripting API

[0195] Variable Access

[0196] variable retrieval—reading in User, Session, and Application variables

[0197] variable storage—writing out User, Session, and Application variables

[0198] Pattern Flow Control Methods

[0199] Action execution—executing any Action within the current State

[0200] State transition—jumping to any State within the current Pattern

[0201] Importable Java Objects

[0202] Data Retrieval: (class: DataRetrieval)

[0203] provides access to the Data of interest associated with the current State.

[0204] Content Object

[0205] allows script to put data into a Content Object, which in turn has a render method which can be called to output the Content Object to the device.

[0206] Variable Management

[0207] The PRE handles requests to read and write out Variables. These requests occur from within the scripting code (See Scripting API). The requests can be for any of the three different types of Variables: User, Session, and Application. Variable read/write requests are initiated from the scripting code. The scripting code gains access to these variables through the ScriptingAPI's “Variable Access” methods. (See Scripting API section.)

[0208] Pattern Replay Engine Tasks

[0209] Accepting the Request

[0210] The PRE accepts requests from the Input Handler (e.g. HTTP Input Handler). The PRE receives the Pattern ID, Step Number, Event ID, and the data parameters to successfully process the request. The data parameters are passed in a Java Hashtable object containing name-value pairs.

[0211] Determining Corresponding State from Step Number

[0212] The PRE maintains a history of the States in the Pattern that have been traversed as a monotonically increasing sequence of Steps. The PRE maintains a mapping between each Step and its corresponding State.

[0213] Detecting a Step Number Out of Sequence

[0214] Since the request given to the PRE contains the Step Number of the originating State, the PRE determines whether the user is traversing the States in a linear fashion, or if the user has gone “back” in the history of Steps, by comparing the request Step Number with the Step Number of the last-traversed State. If the user has gone “Back” in the sequence, this is a special case. See the Going Back in Sequence section.

[0215] Retrieving the Session

[0216] The PRE communicates with the SessionManager to obtain the Session object for a request. This Session object contains a PatternContext in particular, which is discussed below.

[0217] Maintaining the PatternContext

[0218] The PatternContext object is contained within the Session object. It represents the runtime information associated with a particular Pattern and Session, including the current Step number, the mapping between Steps and States, the collection of Connector objects, and the Session variables. The PRE keeps the PatternContext up-to-date and stores it persistently (via the SessionManager) by storing the Session object that contains it.

[0219] Retrieving the Pattern, State, and Script

[0220] The Pattern object contains all of its State objects. The PRE requests the specified State from Pattern object by passing it a State ID.

[0221] The State object contains a Script object, which represents the scripting code that is associated with the State. (There is only one Script object per State object.) The PRE requests the Script object from the State object.

[0222] Instantiating the Connector

[0223] Each State can only be handled by one particular type of Connector. Each Connector is instantiated only as needed since a Pattern may never branch to a particular Connector.

[0224] The PRE asks the State object what type of Connector to use. The PRE first tries to retrieve the Connector from the PatternContext object if it already exists. If the Connector has not yet been instantiated, the PRE calls a createConnector method, passing it the type value and Pattern reference to associate with the Connector. The createConnector function creates the appropriate Connector subclass instance which corresponds to the specified type and returns it to the caller (the PRE).

[0225] Extracting Connector-Specific Data

[0226] The XML definition of each State within a Pattern contains information that is Connector-specific. The PRE does not need to be able to interpret this Connector-specific information; it simply needs to pass this information (for each State) to the Connector when an Action is to be performed. (See Invoking the Connector.)

[0227] Invoking the Connector

[0228] The PRE invokes the Connector (determined above) by calling its executeAction( . . . ) method. This method takes the Action and a Hashtable of data parameters as name-value pairs. The Connector has access to the Pattern using a reference passed during the Connector's construction. The Connector only has access to the Connector-specific Pattern information pertinent to this particular Connector subclass instance. For example, the XML Connector stores State-property information within the Pattern which is specific to the XML Connector only. The Connector returns an ActionResult object which has methods to get the resulting State ID and retrieve all of the content data items of interest. If any errors occur (such as not being able to process the Back event), an exception is thrown within the executeAction method.

[0229] Predetermined Transitions Between States

[0230] At design time, the user can specify a State transition that should be performed after a State's script code has finished evaluating, called a predetermined State transition. The IDT specifies this in the Pattern XML. The PRE recognizes such a predetermined State transition in the XML and performs the transition after all other script code (not including OnError) has been evaluated for this particular State. And unlike State transitions which are specified in the script code, predetermined State transitions are preferably implemented directly from the PRE's own Java code, not JavaScript.

[0231] Evaluating Script

[0232] Assuming no error occurred while performing the transition, the PRE evaluates script associated with the new resulting State. See the separate Scripting section for details.

[0233] Going Back in Sequence

[0234] If the PRE has detected that the incoming request is “out of Step”, then it finds at what point in the history the request is coming from. Then it sends a special Back event to the appropriate Connectors in order to “back up” to that State. For example, Step 1 could represent the login page for Yahoo mail. The user then proceeds to the Inbox page (Step 2), and subsequently to a specific mail message (Step 3). If the user clicks “Back” twice on their device browser, the browser could simply render the cached pages for Step 2 and Step 1. Then the user could initiate another login from Step 1. The PRE would detect that the user has gone back in sequence (since the Step ID is part of the request) and would respond as described above.

[0235] Scripting

[0236] The user can specify script to be evaluated when a State is encountered. (This script is specified using the IDT.) Using script (which is specifically JavaScript), the user has access to the Platform's Scripting API and Scripting Java objects. The Functionality section describes the functionality that is exposed.

[0237] Scripting Implementation

[0238]FIG. 22 is a diagram <b>2200</b> illustrating how different components interact to support Scripting. PRE preferably supports JavaScript scripting using an open-source platform <b>2202</b> from Mozilla called Rhino. Rhino is Mozilla's Java implementation of the core JavaScript language. Using Rhino, the PRE <b>2204</b> can evaluate JavaScript from within Java objects. In addition to the core language, Rhino has implemented JavaAdapters, which allow JavaScript to implement any Java interface or extend any Java class with a JavaScript object.

[0239] The Scripting Engine <b>2206</b> receives a request to evaluate a particular script inside a Script object. The Scripting Engine receives a reference to the content DOM tree so that the JavaScript can manipulate it. The Scripting Engine communicates with the Session Manager <b>2208</b> to fulfill any Variable read/write requests that it made available via the Scripting API.

[0240] State Recognition Module and Connector

[0241] The XML Connector is a ‘state-keeping’ connector. That is, it is always in some specific state. That state corresponds to some state of the remote application (see Glossary). A transition from one XML state to another cannot usually be made, unless it is done by using an “action” that will change the state of the remote application and thus change the state of the connector accordingly.

[0242] The XML Connector identifies a remote state by the output provided by the remote application in that state. In fact, the remote application may have much more information about its current state then what it displays to its users. Thus, a distinction can be made between a local state (“state”)—which will refer to the state assigned by the user to the remote application state—and the actual remote state. The transition from one remote state to another is a function of the user input and the state of the remote application. Since the XML Connector does not have all information about the remote state, it cannot accurately know what the next state of the remote application will be, until the remote application provides output corresponding to that state. Moreover, if at one time certain user action in state A caused the remote application to transition to state B, it does not follow that the same transition will occur the next time the same user action is executed in state A. In light of the above discussion, the replaying mechanism preferably recognizes the state by its current output, not by the previous state and transition. This is done with the help of the State Recognition Module (SRM).

[0243] The SRM creates a state's “output structure” description for a state and then uses that description during replay to recognize a state. The term “output structure” refers to the window and frame structure of the output from the remote application. The output structure description contains the information about how many windows were presented to the user at a given state in remote application and how many frames were in each window and the nesting structure of those frames. (SRM uses the CRM to recognize individual documents in a document structure.)

[0244] Functionality

[0245]FIG. 23 depicts a process <b>2300</b> for recognizing a state based on a current output, according to one embodiment of the present invention. In operation <b>2302</b>, current output is retrieved from a remote application utilizing a network, the current output corresponding to a state of the remote application. An output structure description of the remote state is generated in operation <b>2304</b>. The output structure description is preferably of a window and frame structure of the output. The output structure definition is compare to a pre-defined state definition of a recorded state (called a state description) in operation <b>2306</b>. In operation <b>2308</b>, a determination is made as to whether the remote state corresponds to the recorded state. Note that the recorded state definition is created during recording of the pattern.

[0246] As an option, predefined information (e.g. a StateData Object) about the remote state can be returned if the remote state corresponds to the recorded state. The predefined information can then be used to extract data from the remote application.

[0247] In one aspect of the present invention, the output structure definition includes a number of windows presented in the remote state, a number of frames in each window, a nesting structure of the windows, and/or a nesting structure of the frames. Preferably, the recorded state is part of a pattern pre-recorded by a user. In yet another aspect of the present invention, content of the remote output is recognized based on recorded content properties and used to help recognize the state. Preferably, the recognized content is utilized for recognizing the state based at least in part on a weighted average of content recognition and content importance. Note that the content can be one or more documents, one or more content items in a document(s), etc.

[0248]FIG. 24 is a flow diagram of a process <b>2400</b> for recognizing a remote state utilizing individual document recognition, according to another embodiment of the present invention. This embodiment identifies the state of a site or page by the content of its content (such as documents) instead of (or in addition to) the layout structure of these documents. In operation <b>2402</b>, a plurality of documents are received. An attempt to recognize each of the documents as being associated with a predetermined state is made in operation <b>2404</b>. In operation <b>2406</b>, a state is identified based on the recognition of the documents.

[0249] A Content Recognition Module (CRM) can be used to recognize states. Basically the state consists of a bunch of documents, each one of which is first recognized by the CRM. If the state consists of documents A, B and C, then if the CRM recognizes all of A,B and C from the documents given it by the SRM, the state is recognized. Otherwise, if the CRM recognizes a different set of documents, then the state is recognized as the state containing that set of documents, or no state is recognized if no state corresponds to that set of documents, the pattern is placed in an error state.

[0250]FIG. 25 is a flow diagram <b>2500</b> that illustrates the interaction between the XML Connector Module (XCM) <b>2502</b> and the Pattern Replay Engine (PRE) <b>2504</b>. As discussed above, the PRE performs the task of replaying (executing) a pattern at run-time. It goes through each state of the pattern, and depending on the type of the state invokes the appropriate connector. The XML Connector Module (XCM) is invoked to execute XML states. Its input is the request parameters (DataParams) and definitions for all possible XML states in the current pattern, and it outputs a StateData object, which can be used to obtain information about the next state and the desired data elements.

[0251]FIG. 26 is a flow diagram <b>2600</b> of the operation of the XML Connector <b>2602</b>. The request parameters contain the action to be executed and other element changes caused by the end user (such as filling out a form field). This information is sent to the User Agent Module <b>2604</b>, so that it fetches the output of the resulting remote state. That output is then sent to the SRM <b>2606</b> so that the current remote output can be matched to a state definition created during design time. The SRM accepts the output of the remote state and the properties of all possible local states to which this remote state can correspond. If the remote output is recognized as one of the recorded states, a StateData object is returned which contains the information about the recognized state and can be used to extract the desired content and other information stored during recording.

[0252] At design-time, the XML connector is not used, because the task of fetching the output of the remote application is performed directly by the Interactive Design Tool (IDT), which is the user interface for the pattern recording. However, the IDT may still use the SRM to create state definitions for pattern states. These state definitions contain the information that is used later during replay to identify remote states and match them to local states (which are defined by these state definitions).

[0253]FIG. 27 is a flow diagram <b>2700</b> of SRM and IDT interaction (requests executed from top to bottom). During design time, the IDT <b>2702</b> sends requests to the SRM <b>2704</b> to calculate state properties for some remote output. That request contains the remote output XML, the element id's for XML elements of interest in that output and the document and content descriptions created by the user to aid in identifying documents and content elements. After analyzing the state structure, the documents and the content elements, SRM returns to the IDT the properties, which are used during run-time to identify the state. If a state with the same structure and document properties already exists, this information is returned to IDT to fetch more information from the user on differentiating the state from the other similar state (if that is desired).

[0254] Besides calculating the state properties, the SRM is also able to identify if the new XHTML output matches any of the existing state properties for a previously defined state. This allows identification of any identical states in the pattern, which may be difficult to differentiate at run-time. It will also aid the designer if a state is to be edited after being recorded initially. That is, if the designer points the IDT browser to a remote state that was already identified, the system will recognize that this is an already existing state and will let the designer modify content and actions at that state.

[0255] In one embodiment of the present invention, the interaction between the IDT and the SRM proceeds as follows. Once the designer loads the XHTML output for a given remote state into the IDT browser, that XHTML is sent to the SRM to compare against the properties of the states that already exists in the pattern (unless no states exists). If the XHTML matches one of the state properties, the state id for that state is returned.

[0256] Once the user has identified all the content of interest in a state and has executed an action that causes a state transition (DOM modifying action or page transition action), the element ids are sent to the SRM to create content properties.

[0257] The following is a sample interaction between the SRM and IDT: <tables id="TABLE-US-00004" num="4"><table frame="none" colsep="0" rowsep="0" pgwide="1"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="252PT" align="left" /><thead><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>IDT:</entry></row><row><entry /><entry>Add A State (check existence):</entry></row><row><entry /><entry>&lt;SRM:STATE id=”2”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="84PT" align="left" /><colspec colname="1" colwidth="210PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”21” type=”window” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="112PT" align="left" /><colspec colname="1" colwidth="182PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”211” type=”frame” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="126PT" align="left" /><colspec colname="1" colwidth="168PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”2111” type=”frame” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="140PT" align="left" /><colspec colname="1" colwidth="154PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;HTML&gt;...&lt;/HTML&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="126PT" align="left" /><colspec colname="1" colwidth="168PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;SRM:DOC id=”2112” type=”frame” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="140PT" align="left" /><colspec colname="1" colwidth="154PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”21121” type=”iframe”</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="126PT" align="left" /><colspec colname="1" colwidth="168PT" align="left" /><tbody valign="top"><row><entry /><entry>rank=”ignore”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="154PT" align="left" /><colspec colname="1" colwidth="140PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;HTML&gt;...&lt;/HTML&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="140PT" align="left" /><colspec colname="1" colwidth="154PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;HTML&gt;...&lt;/HTML&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="126PT" align="left" /><colspec colname="1" colwidth="168PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;HTML&gt;...&lt;/HTML&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="112PT" align="left" /><colspec colname="1" colwidth="182PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;HTML&gt;...&lt;/HTML&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="224PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="266PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:STATE&gt;</entry></row><row><entry /><entry>CRM:</entry></row><row><entry /><entry>&lt;CRM:RESP status=”ok”&gt;&lt;/CRM:RESP&gt;</entry></row><row><entry /><entry>IDT:</entry></row><row><entry /><entry>Add content to state.</entry></row><row><entry /><entry>&lt;CRM:DESCR docid=”2111” markup=”markup.crm”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="238PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;CRM:EL id=”e42” rank=”high”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="98PT" align="left" /><colspec colname="1" colwidth="196PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;CRM:PROP class=”???” rank=”normal” border=”0”/&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="84PT" align="left" /><colspec colname="1" colwidth="210PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/CRM:EL&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="238PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/CRM:DESCR&gt;</entry></row><row><entry /><entry>CRM:</entry></row><row><entry /><entry>&lt;CRM:RESP status=”ok”&gt;&lt;/CRM:RESP&gt; SRM:</entry></row><row><entry /><entry>&lt;SRM:RESP status=”ok”&gt;&lt;/SRM:RESP&gt;</entry></row><row><entry /><entry>IDT:</entry></row><row><entry /><entry>Add content to state.</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="294PT" align="left" /><tbody valign="top"><row><entry>&lt;SRM:STATE id=”2” status=”new”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="266PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;DOCUMENT id=”21” url=”http://www.yahoo.com”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="224PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;CONTENT id=”23” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="98PT" align="left" /><colspec colname="1" colwidth="196PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;PROPERTY class=”ATTR_DEF” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="112PT" align="left" /><colspec colname="1" colwidth="182PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;PARAM name=”href” value=”http://mail.yahoo.com”&gt;</entry></row><row><entry /><entry>&lt;/PARAM&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="98PT" align="left" /><colspec colname="1" colwidth="196PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/PROPERTY&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="224PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/CONTENT&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="252PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/DOCUMENT&gt;</entry></row><row><entry /><entry>&lt;EVENTSTREAM&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="35PT" align="left" /><colspec colname="1" colwidth="259PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;EVENT id=“1”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="238PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;ACTION&gt;ONCLICK&lt;/ACTION&gt;</entry></row><row><entry /><entry>&lt;CONTENTID&gt;23&lt;/CONTENTID&gt;</entry></row><row><entry /><entry>&lt;DOCUMENTID&gt;21&lt;/DOCUMENTID&gt;</entry></row><row><entry /><entry>&lt;EVENTHANDLER&gt;on_submit_page&lt;/EVENTHANDLER&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="252PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/EVENT&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="280PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/EVENTSTREAM&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="294PT" align="left" /><tbody valign="top"><row><entry>&lt;/SRM:STATE&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="238PT" align="left" /><tbody valign="top"><row><entry /><entry>SRM:</entry></row><row><entry /><entry>&lt;SRM:RESP status=”ok”&gt;&lt;/SRM:RESP&gt;</entry></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0258] If the SRM informs the IDT that the state already exists, the IDT may ask some document description details from the user (for example, the user may specify that this document should be identified by a certain text which is not present in the documents in the other state which is similar to this one). The SRM will try to reanalyze the state output given the additional user input and if the additional information helps to differentiate the states, the state will be added as a new state.

[0259] XML Applications

[0260] Most common XML applications are HTML web-based applications and this connector supports these applications. There are two distinct issues that the connector has to deal with in supporting XML applications. These are data representation (state recognition and content retrieval) and transition actions. State recognition and content retrieval are supported on any XML document or set of documents (multiple documents are possible in one state only through the use of HTML windows and frames). The transition actions supported are an arbitrary user event (as represented by the event object) and GET and POST requests to an arbitrary URL.

[0261] The XML Connector interoperates between the Pattern Replay Engine, the User Agent and the State Recognition Module.

[0262]FIG. 28 depicts a program flow <b>2800</b> of the Connector. As shown, a request to execute an event or go to an initial state is received from the PRE in operation <b>2802</b>. In operation <b>2804</b>, the event is sent to the User Agent. A response is received from the User Agent in operation <b>2806</b>. If an error is found, the error is returned to the PRE. If no error is found, the current output and state definitions are sent to the SRM in operation <b>2808</b>. In operation <b>2810</b>, a new state id is received from the SRM. If an error is found in the state id, it is send to the PRE. If no error is found, the new state id and content retrieval object are sent to the PRE in operation <b>2812</b>.

[0263] Additional Embodiment of the SRM

[0264] While sophisticated techniques can be used to recognize a remote state by its output structure, an embodiment of the present invention identifies a state by the content of its documents rather than by the layout structure of these documents. So if on day a site navigation menu is in the left frame and the contents of the site is in the right frame and the next day it is the opposite, that does not have any impact on the functionality of the site at that state. In light of the above, while the SRM has the information about the exact structure of the state's output, state recognition occurs based only upon whether the required documents are present in the unordered list of the documents output at the current state. So, state recognition most heavily relies upon individual document recognition (performed by the CRM).

[0265] The SRM works according to this algorithm:

[0266] Send all documents from the current output to the CRM for document recognition

[0267] Compare the list of document ids in the definition of each state in the pattern (of the proper type) with the list of document ids in the current output.

[0268] If a match is found, state is identified. (See below on how matching is done.)

[0269] If more then one match is found, then output structures are compared for the matched states.

[0270] There are two additional features in the SRM, which provide some more intelligence for state recognition. One is the Transition Probability List (TPL). This list provides an ordered array of state ids (which have higher probability than others to match the current output) where the first state id corresponds to the state that will be the most probable to match the current output, the second state id corresponds to state which is the second most probable state to match the current output and so on. The Pattern Replay Engine can create this vector by keeping a history of which states resulted from a certain action being executed in a certain state. So if during last replay (or record) action x executed in state A resulted in state B, then during current replay when x is executed in A, B will be the most probable resulting state, more so than any other state in the pattern. During each replay the resulting state id can be saved for any state-action combination and that information can be used later to create the transition probability list.

[0271] The transition probability list is used by the SRM to generate hints for document recognition, which are sent to the CRM. The hints are provided in an ordered list of document ids where the position of document ids implies their probability. Thus, the first document id is the most probable to match the current document, the next one has second highest probability and so on (similar to the transition probability list). The output structure is used to generate hints. Each state id in the transition probability list points to state properties. The structure of the each state's output, as given by the properties, is compared with the current output structure being analyzed, and if a document's tree position matches the position of a document element in state properties, the id of that document element is sent as the most probable to match that document. The next most probable ids are the ids of documents on the same level of the tree and the next are all document ids given by the state property. If tree positions do not match, then the list of all document ids in the more probable states will be sent as more probable to match each document in the current output.

EXAMPLE

[0272] If pattern contains two state properties as follows: <tables id="TABLE-US-00005" num="5"><table frame="none" colsep="0" rowsep="0"><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><thead><row><entry /><entry /></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></thead><tbody valign="top"><row><entry /><entry>&lt;SRM:STATE id=”1”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”11” type=”window” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”111” type=”frame” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”1111” type=”frame”</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row><entry /><entry>rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;SRM:DOC id=”1112” type=”frame”</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row><entry /><entry>rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;SRM:DOC id=”1113” type=”frame”</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row><entry /><entry>rank=”ignore”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="1"><colspec colname="1" colwidth="217PT" align="left" /><tbody valign="top"><row><entry>&lt;/SRM:STATE&gt;</entry></row><row><entry>&lt;SRM:STATE id=”2”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”21” type=”window” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”211” type=”frame” rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”2111” type=”frame”</entry></row><row><entry /><entry>rank=”necessary”&gt;</entry></row><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row><row><entry /><entry>&lt;SRM:DOC id=”2112” type=”frame”</entry></row><row><entry /><entry>rank=”necessary”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;SRM:DOC id=”21121” type=”iframe”</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row><entry /><entry>rank=”ignore”&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="70PT" align="left" /><colspec colname="1" colwidth="147PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="56PT" align="left" /><colspec colname="1" colwidth="161PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="42PT" align="left" /><colspec colname="1" colwidth="175PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="28PT" align="left" /><colspec colname="1" colwidth="189PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:DOC&gt;</entry></row></tbody></tgroup><tgroup align="left" colsep="0" rowsep="0" cols="2"><colspec colname="OFFSET" colwidth="14PT" align="left" /><colspec colname="1" colwidth="203PT" align="left" /><tbody valign="top"><row><entry /><entry>&lt;/SRM:STATE&gt;</entry></row><row><entry /><entry namest="OFFSET" nameend="1" align="center" rowsep="1" /></row></tbody></tgroup></table></tables>

[0273] The transition probability list is: TPL=“2,1”.

[0274] If current step output received has a window with two frames inside, the hints list for the first frame will be an ordered list “2111, 2112, 211, 21, 21121, 1111, 1112, 1113, 111, 11”.

[0275] Another feature is the document importance ranking. This enables the designer to provide a rank to each document signifying how important its presence is to identifying the state. The ranking is specified on the scale from 1 through 5, where 1 means that the document must be present for the state to be recognized and 5 means that the presence of the document has no bearing on state recognition (2, 3 and 4 are for additional flexibility and can be used for more sophisticated state recognition). The IDT provides the designer an ability to provide importance ranking for each document in a state as part of document description. If such ranking is not provided, all documents with any identified content elements are given a ranking of 1, otherwise a document is ranked with a 5.

[0276] While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, for example, the Connector described above should not be understood to only execute XML, but should be understood to also execute Hypertext Markup Language (HTML) and Standard Generalized Markup Language (SGML).

[0277] Therefore, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.