Transaction execution system interface and enterprise system architecture thereof

Description

BACKGROUND OF THE INVENTION

[0002] 1. Field of the Invention

[0003] The present invention relates to on-line transaction systems, and particularly to a transaction interface system for interfacing user interactive devices with a transaction execution system in a distributed network environment, and more particularly to a transaction interface system having an unified architecture which is compatible with existing transaction execution systems. The present invention also relates to the development of an enterprise system based on the unified architecture.

[0004] 2. Description of Related Art

[0005] The dramatic growth of the information highway and network-centric computing significantly altered the way people conduct business transactions. For example, on-line transactions are becoming ubiquitous. A user may use a personal computer to access a company's transaction execution system to request and carry out a desired transaction. With the explosion of the World Wide Web and Internet technologies, on-line transactions are made more widely accessible to users. The conveniences of on-line business transactions have driven companies from across a broad spectrum of businesses to provide customers with the option of conducting on-line transactions.

[0006] The demand and ubiquity of on-line transactions fueled the development of various sophisticated transaction execution systems and related transaction application systems. With the availability of increasingly more powerful processors, many applications are designed to run on smaller scale network computer systems generally referred to as client-server systems. However, in the past, the transaction execution applications and transaction applications had been designed as dedicated systems which did not offer the flexibility of allowing easy addition of new features, and compatibility and interoperability with other applications.

[0007] For example, when a company having an existing transaction execution system wished to provide for user access for transaction via the Internet, an entirely new protocol had to be provided to interface the Internet with the existing transaction execution application. This required developing a new application or making significant modifications to the existing transaction execution application, and integration of the Internet interface into such modified transaction execution application. When it comes time to add another feature to the modified transaction execution system, additional modifications and integration into the transaction execution application would be required. Moreover, the Internet based interface of one transaction execution system is not compatible with another transaction execution system.

[0008] There are several drawback associated with having to develop new applications or make modifications to existing applications. The direct costs for making the modifications or developing a new application can be relatively high, especially in the case when a company undertakes to make modifications to an antiquated legacy system. Further, significant time and resource must be spent on debugging the entire new or modified transaction execution application to confirm its integrity. There is always the risk of discovering additional bugs in the new or modified application after it has been put into active service. Such new bugs may cause significant downtime of the transaction system to allow for debugging and bug fixing. More critically, the bugs may create irreversible errors in the execution of the transactions, which may proceed undetected until significant damages have been caused. For example in the financial industry, and more particularly in the securities trading business, an error in executing an on-line trade could have ramifications that cannot be reversed when the error is eventually detected several hours or days later.

[0009] The reason for the lack of compatibility of current transaction applications is partly due to the lack of an infrastructure in the past to allow development and deployment of large-scale, interactive applications on distributed networks, such as Intranets, Extranets, and the Internet. Specifically, in current implementations of Internet systems, Web servers route discrete requests from multiple browsers to the requested applications and databases. These discrete requests are received by the system as a series of unconnected “hits”. This is due to a problem that generally exists in the Internet environment known as a lack of “application state”. Without an application state, a system cannot track a user's prior actions, and it loses track of which requests came from which user. Moreover, the numerous variables required by the application in each instance of the program cannot be efficiently maintained in the Internet environment. (For example, while a request for a stock quote requires a single query to a database of current share prices, the manipulation of sales information for a customized report may involve a large number of variables and multiple queries to the database.) These problems are exacerbated when one visualizes a Web site or Internet system with hundred or thousands of simultaneous users, whereby multiple instances of an application may run concurrently. Until now, the lack of an application state in the Internet environment has prevented the deployment of sophisticated applications, which require tracking a user's actions throughout the entire program in the Internet environment. This has also lead to development of a variety of convoluted methods for making applications written in existing languages or for legacy environments work in the Internet environment.

[0010] Further, in the past, some developments cannot be carried out using technology the developers already owned, programming languages they already knew, and programming techniques they already understood. As a result, the development and maintenance costs in prior systems are relatively high. For example, there is a large market of corporate developers that do not feel comfortable developing new Web-based applications because they do not have the right systems in place to help them to do so. However, companies are hard pressed to develop such systems because of the competitive pressures and general advantages of the technology. Companies that start developing the Web systems in the absence of programming talent in-house are faced with the choice of significant time delay because of retraining of their people, or a significant expense of hiring new personnel or outsourcing.

SUMMARY OF THE INVENTION

[0011] The present invention provides an add-on transaction system that interfaces a network of users with an existing on-line transaction execution system, without requiring significant modifications to the functionality and/or protocol of such transaction execution system. This is accomplished by providing a set of novel application programmer interfaces (“API”) which allows integration of specific transaction applications within the transaction system with virtually any existing transaction execution system on practically any platform. More specifically, two separate APIs are provided, a “transaction execution” API (“TE API”) and a “transaction alert” API (“TA API”). The TE API provides the functionality of delivering trade information and user requests to the execution system, and the TA API allows the execution system to deliver real-time information to the user. The cooperation of the two APIs with the transaction system's core functionality provides an extremely flexible and secure way to implement two-way communication without actually modifying the transaction application itself. In another aspect of the present invention, the transaction system is implemented to receive user transaction requests via networks which use IP network protocol (“IP network”) (e.g., the Internet, which uses “transmission control protocol/Internet protocol” (“TCP/IP”)). In a further aspect of the present invention, the transaction system is implemented to receive transaction requests via a wireless gateway, and more specifically via a digital packet-switched wireless gateway, which may be connected via an IP network to the transaction system. In a specific embodiment of the present invention, a novel financial trading system is disclosed.

[0012] According to yet another aspect of the present invention, an enterprise system having a novel unified architecture is disclosed which may be adopted for the IP network protocol based transaction system of the present invention. The enterprise system consists of one or more enterprise system managers, each managing a number of application servers. The system manager is connected to a Web server, and supports the Common Gateway Interface (“CGI”) as well as server APIs of all major general purpose Web servers and all major browser technologies. The application servers are capable of running applications on remote computers and present a highly reliable and scalable system for deployment. The system manager tracks and provides an “application state” in each instance of the application programs running on the distributed application servers, even though the necessary data is received as a series of unconnected “hits” in the IP network environment. The system manager unites the information and applications residing on the different application servers within the otherwise unstructured IP network environment, so the applications work together seamlessly and efficiently, even if the types of application servers and related databases in the system are not compatible. The system manager also routes the data from the Internet to one or more application servers that are operating in parallel in accordance with the demand and availability of the application servers. The unified architecture provides a novel development environment. This development environment enables programmers to write large-scale applications in any of the ways familiar to them without them having to learn unfamiliar and complex languages.

[0013] In another aspect of the enterprise system of the present invention, a set of APIs is used to provide developers of enterprise applications with a simple and flexible means of developing Web applications running on multiple platforms. For each platform that the enterprise system runs on, a version of such API is created. All these APIs maintain the same set of base functionality, which is expressed in terms of the target platform. This functionality allows the developers to extract data entered by the user in to the Web page, store this information in the program variables and as a persistent context, and present newly generated data and pages to the user. Unlike existing methods of development of Web applications that require knowledge of particulars of CGI and HTTP implementations for a specific Web server, the APIs in the enterprise system hides these complexities from the developer and allows development of the Web applications in a cross-platform fashion.

[0014] In the IP network version of the transaction system of the present invention, the transaction system consists of one or more transaction applications which provide specific transaction ability, one or more transaction application servers which accommodate a large number of simultaneous user requests, and a transaction system manager which coordinates the activities of the transaction application servers. The APIs in the transaction system are structured based on the principle of the APIs in the enterprise system.

[0015] In a further aspect of the enterprise system, a special screen definition language (“UNML”) has been developed to describe basic GUI elements such as text fields, images, input fields, command buttons, menus and tables. This is an embedded language that implements the “context free screen concept”, where every screen and every element of the screen is independent from other elements. Using the UNML, information can be transmitted to the users in a device independent fashion, so that transmitted information can be displayed on various wireless devices based on their unique browser.

[0016] According to yet another aspect of the invention, a new, high level programming language, the Report Query Language (“RQL”), is disclosed, which may be used to develop transaction applications and other applications including IP network applications. RQL provides a programming environment similar to C, C++ and PERL, but makes it more convenient for programmers to manipulate and format relational and non-relational data. RQL also includes extensions which allow developers to rapidly create state-of-the-art Internet applications for Intranets and Web sites. A run time engine, and various software development kits are also available for RQL. RQL therefore simplifies the development of complex system, databases and network administration applications, as well as database applications and enterprise wide reporting applications for “traditional” client/server and Internet/Intranet environments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0017]
FIG. 1 is a schematic system block diagram illustrating the integration of the transaction system of the present invention with the transaction execution system in a network environment.

[0018]
FIG. 2 is a schematic system block diagram illustrating the integration of an IP network-based transaction system with a transaction execution system, in accordance with one embodiment of the present invention.

[0019]
FIG. 3 is a functional block diagram of the unified architecture in an enterprise system in accordance with another aspect of the present invention.

[0020]
FIG. 4 is a functional block diagram of one embodiment of the IP network version of the transaction system of the present invention, as implement in accordance with the unified architecture.

[0021]
FIG. 5 is a chart of exemplary trade specific application functions.

[0022]
FIG. 6 and FIG. 7 show exemplary actual screen displays at a user interactive device, of information that is transmitted in accordance with the UNML screen definition of the present invention.

[0023]

FIGS. 8

a
-8g represents the various placeholders in HTML templates that are supported by UNML conversion in accordance with one embodiment of the present invention.

DESCRIPTION OF THE ILLUSTRATED EMBODIMENTS

[0024] The following description is of the best presently contemplated mode of carrying out the invention. This description is made for the purpose of illustrating the general principles of the invention and should not be taken in a limiting sense. The scope of the invention is best determined by reference to the appended claims.

[0025] The inventive transaction system of the present invention will be described below in reference to the embodiment of a wireless financial instrument trading system. However, it is understood that the present invention may be adopted for other types of transaction systems without departing from the scope and spirit of the present invention. Similarly, the unified architecture aspect of the present invention will be described in reference to an IP network-based, and particularly an Internet-based, transaction application. It is equally understood that the unified architecture may be adopted for the development of other types of applications for Internet based, IP network-based, or other distributed network systems without departing from the scope and spirit of the present invention.

Transaction System Configuration

[0026]
FIG. 1 is a schematic block diagram that illustrates interfacing an add-on transaction system 10 of the present invention between a network 12 and an existing on-line transaction execution system 14. As will be discussed in greater details below using the example of a financial trade system, the transaction system 10 includes a set of APIs that allows flexible integration of the transaction system 10 with virtually any existing transaction execution system 14 on practically any platform, without the need to significantly modify the functionality, system configuration, protocol, system architecture, or characteristics of the existing transaction execution system 14. Specifically, there is no need to modify the existing trade execution system 22 at a system level, beyond making minor application specific setup and configuration changes, if required, that are typical of system integration. Typically, recompilation of the existing transaction execution system would not be required, unless the changes to the setup and configuration necessitate otherwise.

[0027] The transaction system 10 may have the following exemplary user/system interfacing functions: coordinating the interactions of the transaction execution system 14 and the transaction requests from users received through the network; delivering information from the transaction execution system to the users; authenticating the users; and identifying the user requests; and routing user requests to the appropriate transaction execution system 14. The transaction system 10 may also include modules which perform transaction specific add-on functions or shell functions that are not found in the transaction execution system 14 and are relevant to and compatible with the specific nature of the transaction execution system 14. In the example of a trade execution system described in connection with FIGS. 2 and 4 below. These specific applications may include the following function categories: user portfolio management, trade order placement, view orders, and trade alert notification functions. The transaction execution system 14 actually executes the requested trade, but leaves the user interfacing functions to the transaction system 10. (In other words, the transaction system 10 handles the user interfacing functions independent of the functions of the transaction execution system 14.) An example of a transaction execution system is the “TRIARCH” trading system developed by Reuter, Ltd. The network 12 may be a local area network (“LAN”), wide area network (“WAN”), the Internet, Intranet, Extranet, and the like, which may be based on any protocol, including without limitation the IP network protocol. The network may be accessed by a user (at 16) by using an interactive device that has an appropriate graphical user interface (such as a personal computer, personal digital assistant (“PDA”), two-way pager, cellular phone, and the like) via land lines 18 or a wireless gateway 19.

Trade System Configuration

[0028] Referring to FIG. 2, the present invention is illustrated in reference to an IP network based, and in particular an Internet based, financial instrument-trading environment. The transaction system in this embodiment is the trade system 20, which is connected to an existing trade execution system 22. In this particular embodiment, the trade system 20 is implemented to work with an IP network 25, such as the Internet that uses TCP/IP. The trade system 20 can be easily configured to work with other distributed networks, such as Intranet, Extranet and other LAN and WAN and the like, whether or not based on IP network protocols or other protocols, without departing from the scope and spirit of the present invention. At least one Web server 24 interfaces between the network 25 and the trade system 20. (Other types of servers may be used for other network systems depending on the network protocol, without departing from the scope and spirit of the present invention.) Traders can access the trade system 20 via the Internet by any conventional means, such as using any user interactive device that has an appropriate Web browser that is connected to a landline gateway 26 using a modem 28 or to a wireless gateway 30 using a wireless modem 32 (e.g., using a workstation 34 or a portable notebook computer 36). To enable a wider coverage for portable applications and added conveniences, a wireless gateway is provided for hand-held wireless interactive devices 40. The hand-held wireless devices may include Internet enabled cell phones (generally known as “smart phones”, e.g., the ALCATEL's “One Touch Pro”), two-way pagers (e.g., the Inter@ctive Pager™ developed by Research In Motion Ltd.), PDAs (e.g., the NOKIA's “9000i Communicator”, or 3COM's PalmPilot™), palmtop computers (e.g., HP's 320LX), etc. For cellular devices, a packet-switched network such as the Cellular Digital Packet Data (“CDPD”) wireless network is currently the preferred implementation, as it provides an efficient, low cost system, for both setup and usage. For example, the AT&T PocketNet™ Service, or the like, would be a suitable wireless platform.

[0029] The functionalities of the trade system 20 will be described, followed by a description of its architecture. The trade system 20 is designed to facilitate trading of all types of financial instruments (e.g., stocks, bonds, etc.). For example, the trading system creates a completely mobile trading environment where one can browse a stock quote portfolio, retrieve real-time stock prices and place market stop or limit orders on demand. The trade system 20 is a two-way system that handles user/system interfacing functions. This may include: coordinating the interactions of the trade execution system 22 and the transaction requests from users received through the network 25; delivering information from the trade execution system 22 to the users; authenticating the users; and identifying the user requests; and routing user requests to the appropriate trade execution system 22. The trade system 20 may also include modules which perform trade specific add-on functions or shell functions that are not found in the trade execution system 22, including the following function categories: user portfolio management, trade order placement, view orders, and trade alert notification functions. (FIG. 5 shows examples of the specific trade functions that are relevant to securities trading, which will be explained in greater detail below). The trade system 20 also include a module that can initiate communications to the traders to provide up to the minute price fluctuation alerts to the traders' interactive devices. This allows the traders to react immediately. By simply logging on to the trade system 20, a trader has the ability to check the trader's trade positions and execute any number of transactions. Immediately upon execution, each trade is confirmed by messaging directly to the trader's wireless interactive device 40 (e.g., a cellular phone). Confirmations can also be routed to email addresses and/or fax numbers designated by the trader. Such confirmation may be by way of a short message to trader's wireless device (e.g., cellular phone or pager) that the trade has been executed, with details of the trade being sent to a fax or email address designated by the trader. The trade system 20 allows flexibility for the trader to customize setup and configuration via the interactive device the desired options with respect to alerts, confirmation, access passwords, and other personal preferences for interfacing with the trade system 20. For those interactive devices 40 that are already IP network enabled, the traders' setups and configurations may be made via the trader's existing devices without requiring modifications to any physical configuration of the trader's existing interactive device 40. The trade system generates user screens in both “hand held device markup language” (“HDML”) and “hyper text markup language” (“HTML”) for wireless IP network devices as well as for networked computers. As will be discussed more fully, a special screen definition language (“UNML”) is introduce in one aspect of the present invention which permits screen information to be transmitted to various wireless devices in a device independent fashion so that the information may be displayed based on the unique browser of each device.

[0030] Transparent to the traders, the trade system consists of multiple application servers and a system manager (see also FIG. 4). The trade system is structured and configured such that it controls interaction with and input from the traders' device and coordinates each trader's session activities. As the trade system 20 is accessible by a large number of users, it is structured and configured to bring order and logic to busy IP network trading environments by binding together all system components and connecting unconnected “hits” from each trader into a single session. It also provides load balancing and high availability by distributing transactions to multiple application servers (see discussions below in connection with FIG. 4). Simultaneous trading activities of an unlimited number of traders is accommodate by managing instances of trading applications required for each. The trade system 20 is configured to be scalable, by adding additional application servers. The system has a set of APIs which are linkable to virtually any existing real-time price feed, proprietary database and trade execution system 22, Web site and Intranet, without the need to significantly modify the functionality, system configuration, protocol, system architecture, or characteristics of the existing trade execution system 22. Specifically, there is no need to modify the existing trade execution system 22 at a system level, beyond making minor application specific setup and configuration changes, if required, that are typical of system integration. Typically, recompilation of the existing trade execution system would not be required, unless the changes to the setup and configuration necessitate otherwise.

[0031] The trade system 20 works with either its own system database, or a proprietary database that is associated with the particular trade execution system 22. Each trader's transaction information is stored in either the system database or the proprietary database as each instance of the trade session is started following user authentication and login.

Enterprise System

[0032] Before describing the specific components of the trade system 20, it would be beneficial to discuss another aspect of the present invention, which involves the system architecture of an enterprise system that forms the basis of the trade system 20. FIG. 3 shows the novel enterprise system architecture. It is understood that the trade system 20 may also be configured based on other architectures to achieve the desired functions.

[0033] The enterprise system 50 has a novel unified system architecture that moves the IP networks to the next level by enabling deployment of large-scale applications in a cost effective manner. The enterprise system 50 infrastructure unites information and applications residing on different application servers, so systems work together seamlessly and efficiently, even if the types of servers and databases in the system are not compatible. The enterprise system 50 also has the following attributes: (a) the system provides familiar ways of programming using the tools already know to minimize the learning curve of personnel, regardless of their background; (b) the system has a flexible and powerful deployment environment to allow a developer to create a unified infrastructure for Web applications across operation system, programming tools and languages and database; and (c) the system includes ability to build both interactive and reporting applications, since both kinds are in equal wide use on the Web.

[0034] Referring specifically to FIG. 3, the enterprise system 50 is located between a Web server 52 and databases and applications 54. It accepts web requests from the Web server 52 and performs processing on those requests, passing them to the correct applications 54. The applications connect to databases, data feeds and other sources of data, collecting the results and returning them to the user.

[0035] Enterprise System Manager

[0036] Several important components make the heart of the enterprise system 50. First is the system manager 56. The system manager 56 adds a layer of management to an otherwise unstructured system, providing an application state for the IP network environment. The system manager 56 tracks and manages the actions of an unlimited number of users accessing the system at the same time, even though user requests are received as a series of unconnected “hits”. The system manager 56 also provides load balancing and high availability by routing each request to the most appropriate application server. The enterprise system 50 supports the Common Gateway Interface (“CGI”) as well as the server APIs of all major general purpose Web servers and all major browser technologies that are currently available.

[0037] The system manager 56 is connected to the Web server 52 through ‘Capture Clients’ (which is a software implementation). The Capture Client receives process request from the Web server and sends it to the system manager along with information required for the system manager to process the request. The Capture Client will send additional variables such as referring Web page URL, authenticated user, remote client name and other information that will be subsequently stored in the system to be available all throughout the application life cycle. To increase processing speed, all this information is not sent for application that is already running.

[0038] Several implementation of Capture Clients for different Web server API may be provided, along with a CGI-based Capture Client, which will work with any CGI-compatible Web server. The solution based on Web server API is much more robust, since it eliminates the need to start multiple CGI processes. The method of connection between the Web server and the system manager 56 is actually irrelevant to the applications, so it is possible to develop applications first with CGI and then move them to Web server API solution. It is also possible to switch Web servers without the need to recompile or modify any application code. The enterprise system manager 56 stores inside itself various tables of client and session information to match client requests with the running applications. The system manager 56 can run on the same computer as the Web server 52 or on a different one.

[0039] Application Server

[0040] The next important component of the enterprise system 50 is the application server. Typically, a number of application servers 58 are coupled to the system manager 56. The application servers 58 are software servers, which may be configured such that each application server 58 is installed in a separate hardware system, or two or more application servers 58 are installed in the same hardware system, or a combination of both configurations. The application servers may be configured to run in parallel or otherwise. By parallel, it means that each application servers 58 are configured to run independent of the other application servers 58, even though the application servers 58 are found in the same hardware system.

[0041] The application servers 58 are capable of running applications on remote computers and present a highly reliable and scalable system for deployment. Generally, the application servers 58 initiate, execute and manage each instance of an application 54 which physically resides on a particular application server hardware when multiple users “simultaneously’ access an application. And when a new hardware server or application is added to the network, an application server (software) installed on this new hardware server automatically notifies the system manager 56 to optimize the use of available resources in the network. As a user's network expands with the addition of new machines, additional application servers can be acquired to automatically incorporate the servers into the system.

[0042] Upon startup, the application servers 58 read their configuration files to determine the location of the system manager and register themselves with it. The configuration files also describe which applications 54 this particular application server is configured to run. This information allows the system manager 56 to direct new users to the least loaded application server 58 in the system. The application servers 58 may be configured to run on multiple platforms, even within the single system. This allows the enterprise system 50 to combine applications developed for incompatible platforms under the homogeneously managed solution, providing the unified infrastructure for deployment.

[0043] When an application server 58 receives a request from a user to start a new application 54, it consults its configuration file and starts the appropriate process that contains the application code. All application interactions with the user are done through the special channels opened by the application server 58. The application server 58 also provides reliable storage for user data, received from the browsers. This data can be replicated between application servers 58, so that an application 54 can be restarted on another application server 58 in the event of hardware failure of the computer it is currently run on.

[0044] Application API

[0045] In order to provide developers of enterprise applications 54 with a simple and flexible means of developing Web applications running on multiple platforms, a set of APIs 60 has been adopted in the enterprise system 50. For each platform that the enterprise system 50 runs on, a version of such APIs 60 is created. All these APIs 60 maintain the same set of base functionality, which is expressed in terms of the target platform. This functionality allows the developers to extract data entered by the user into the Web page, store this information in the program variables and as a persistent context, and present newly generated data and pages to the user. Unlike existing methods of development of Web applications that require knowledge of particulars of CGI and HTTP implementations for a specific Web server, the APIs 60 in the enterprise system 50 hides these complexities from the developer and allows development of the Web applications in a cross-platform fashion. The net result of the enterprise system APIs is that it is only necessary for the developer to code the application logic in the back-end once, and any front-end user can access the application using a “dumb” interface without requiring another application program. The basic functionality of the enterprise system APIs 60 and the underlying principles of its functions are set forth below.

[0046] The enterprise system APIs 60 provide the communications between the application 54 and the application server 58. To deploy an application on the enterprise system 50, the developer needs to call the API functions to communicate with the application server 58. These communications include retrieval of the user-entered information, presentation of the new screens to the user and storage and retrieval of the user-defined context of the application. Additionally, the APIs 60 provide a means to deliver dynamically generated Embedded Objects, such as images, charts and applets. The description of the main functions of the APIs 60 is presented later below.

[0047] A special version of enterprise system APIs 60 is developed for each platform that enterprise applications 54 run on. These versions utilize specific protocols of the underlying platform and the operating system, however the functionality exposed to the user remains the same. Thus, a simple recompilation of the application 54 on the target platform will allow the enterprise application to be migrated to this platform. No code changes or usage of a different API is required. Because the APIs 60 are developed (e.g., by Unistra Technologies LLC) for a variety of programming languages under a variety of hardware and operating systems, developers with various skills could develop applications to be deployed under the unified infrastructure of the enterprise system 50. The use of such APIs, which may be part of a development kit for each language and platform, greatly reduces the training required to become fluent with the system, since the methodology of software development with the API's is familiar to most developers.

[0048] The API calls can be inserted into existing code in order to Web-enable it. All the program logic that existed and functioned in the present environment will remain the same, but the application 54 will produce the Web output and take the Web input. Because the application context is stored in the application server 58, the enterprise system APIs 60 can be used to store application specific information between the screens for multi-page interaction with the user. The screens sent by the application 54 are processed by application server 58 and receive additional information that would be required to process it when the user sends in the input. Additionally, to support rapid GUI development, the enterprise system 50 supports specialized screen definitions that allow programmers to develop applications operating on higher level of abstraction, dealing with just generic interface objects, such as ‘button’ or ‘text box’. The application server 58 transparently handles substitution of correct markup language implementation of such objects and their values defined in previous interactions with the user. This may be accomplished by making use of the new screen definition language “UNML” described later below.

[0049] The major functionality of the enterprise system APIs are as follows:

[0050] Function: Char *AS_read

[0051] Parameters: char *block

[0052] Description: Returns the value of a user inputted variable.

[0053] Function: Int AS_back

[0054] Parameters: Int increment

[0055] Description: Indicates that the user has pressed a back button on the browser and return several screens back.

[0056] Function: char AS_pageid

[0057] Parameters: Void

[0058] Description: Returns the name of the current screen to identify the user location.

[0059] Function: int AS_write_begin

[0060] Parameters: Char *content_type; Char *page_id

[0061] Description: Sends a beginning of the new screen to the browser.

[0062] Function: Int AS_write

[0063] Parameters: Char *data; Int len

[0064] Description: Sends a screen portion to the browser.

[0065] Function: int AS_writeEmbed

[0066] Parameters: Int state; char *embed_name; char *data; int length

[0067] Description: Creates and initializes an embedded object.

[0068] Function: int AS_write_end

[0069] Parameters: Void

[0070] Description: Finishes the output and waits for the next user input.

[0071] Enterprise System Markup Language

[0072] A special screen definition language (Unistra Markup Language “UNML”) has been developed which may be used advantageously for enterprise systems.

[0073] (a) General

[0074] UNML is designed to describe basic GUI elements (widgets) to be used to present information on wireless user interactive devices, such as PDAs, cellular phones, pagers, and other wireless devices. The basic GUI elements include:

[0075] text fields;

[0076] images (pictures);

[0077] input fields;

[0078] command buttons;

[0079] menus;

[0080] tables.

[0081] UNML is designed to be used in the internet/intranet applications using the enterprise system manager 56 and application servers 58 and UNML browsers. Communication between the application server 58 and the UNML browser is performed using HTTP protocol. UNML implements the “context free screen” concept, when every screen and every element of the screen is independent from other elements. Using the UNML, information can be transmitted to the users in a device independent fashion, so that transmitted information can be displayed on various wireless devices based on their unique browser. If the selectable screen element such as Menu Item is selected or if the editable screen element such as Input Field is edited, the value of the variable, assigned to this element is set and the variable is sent to the server using HTTP protocol.

[0082] UNML language is an embedded language. To comply with the HTTP protocol requirements the UNML screen definition page should be wrapped between standard HTML header, for example, containing the URL of the server application and standard HTML footer, for example. UNML allows one to create proprietary GUI applications (browsers) which are independent from the server application logic and use HTTP protocol as a communication protocol, but unlike standard WEB browsers, are optimized to be used with interactive server applications. By using a set of conversion rules, UNML can be converted “on-the-fly” to various browser screen definition languages, such as markup languages including “plain” HTML or HDML, so the same server application can use not only UNML browser, but other browsers, such as standard HTML or HDML browser, as its interface as well.

[0083] UNML introduces the “screen layout templates” concept, when the screen layout information is excluded from the data sent from the server to the client with every screen. Screen layout information can be saved in a separate local file and UNML browser can read that information to render the screen. Using screen layout templates allows optimization of the client-server communication and reduction of the network traffic.

[0084] It is helpful to explain the terminology referred to herein:

[0085] (i) Layout: the type of screen presentation that has its own behavior and rules for its population. Layouts are device independent, but their look and feel are device dependent in that they adhere to design characteristics and patterns specific to each device. Layouts might also have parameters, undefined until a template is created. Each Layout has a unique ID known by client and server.

[0086] Examples: Table, Chart, PopUp, Form, etc.

[0087] (ii) Template: implementation of a layout. Each template also has a unique ID that allows gluing together the logic. A template is implemented by defining a layout it is based on, parameters of this layout and the controls that populate it.

[0088] Examples: Order List, Quote, Order Executed Message

[0089] (iii) Control: an element of the template. Control definition includes type, name and value. Additionally, each control has a default action flag (show/hide) when assigned to a template.

[0090] Examples: Button, Table Row, Label

[0091] (iv) Screen: a template populated with data.

[0092] The logic of the UNML implementation is generally as follows:

[0093] Predefined layouts are embedded into the front end (i.e., the UNML browser). Templates are created for each screen in the application and stored on the server in form of UNML files. The front end caches templates once it had seen them. When the front end requests a screen, the data for the screen is sent to the front end, and the front end presents the screen based on the template. When a new screen needs to be added to the application, one has to choose the layout, create a template, add logic to server code and add invocation of the screen into one of the controls. No modification of the front end is necessary, as long as there is an appropriate layout. New layouts can be added in the future versions of the front end.

[0094] If certain control needs to be hidden (or shown, if controls default state is hidden) because of certain data, the server can send a modifier to alter the control's behavior.

[0095] In order to save bandwidth, keyed field values are included into a template. For example, ‘Trading’ and ‘Watchlist’ account can be coded values of a control ColumnValue2 in template ‘Account List’. Upon receipt of the first data element for this field, the front end will show ‘Trading’ in the cell.

[0096] It is also possible that a transition from one screen to another will happen entirely on the front end without request to the server. The server can request such transition, and the front end executes it if it has appropriate template cached.

[0097] Caching can be implemented either in a by session or a persistent basis, depending on the device's capabilities. In the by session caching the screens are only cached between logins. In the persistent caching, each cached template is assigned a timestamp and the templates, which were changed on the server, expire from cache at login time.

[0098] (b) Conversion

[0099] In order to convert a screen to a markup language such as HTML or HDML, the conversion rules replace the layout and each control in the template with appropriate statements in the target markup language. By implementing the set of conversion rules, each UNML GUI element or widget is converted into a tag or a set of tags in the target markup language and merged with a template in the target markup language to create a full screen, which is rendered by the browser that is compatible with the target markup language.

[0100] By way of example and not limitation, the conversion of UNML to HTML is possible by using HTML layout templates. They contain regular HTML tags and placeholders. The following describes the format of these placeholders:

{<Type>=<FormID>:<ControlID>[Options]}

[0101] 1. Currently the following types are supported:

[0102] DISPLAY—a plain text line

[0103] ENTRY—an entry field

[0104] MULTILINE—a multiline entry filed

[0105] CHOICE—an options list

[0106] RADIO—a radio button with horizontal representation if more than one choice available

[0107] VRADIO—a radio button with vertical representation if more than one choice available

[0108] DATABLE—a table's row, which can contain links.

[0109] TEXTTABLE—the same as above, w/o links

[0110] CELL—a table cell

[0111] BUTTON—command button

[0112] 2. FormID and ControlID describe the corresponding GUI element, which is defined in the UNML template. They are separated by ‘:’ (column). FormID is a number (ID of the form). ControlID is either a number (ID of the control itself) or a name the corresponding UNML control, which will contain the value when the form is submitted.

[0113] 3. The Options can contain additional attributes of the HTML tag. For example [VALUE=“Submit The Order”] option is used with “BUTTON” type and assigns a new label of the button control.

EXAMPLES

[0114] DISPLAY.

[0115] The following will display the text with ID=1, defined in form 220

[0116] {DISPLAY=220:1}

[0117] ENTRY:

[0118] Condition:{ENTRY=111:condition}

[0119] (See FIG. 8a for display.)

[0120] MULTILINE:

[0121] Comments: {MULTILINE=111:r_comments[COLS=30]}

[0122] (See FIG. 8b for display.)

[0123] CHOICE: Order Type:{CHOICE=112:order_type}

[0124] (See FIG. 8c for display.)

[0125] RADIO:

[0126] Order Type: {RADIO=110:order_type}

[0127] (See FIG. 8d for display.)

[0128] VRADIO: Order Type:{VRADIO=110:order_type}

[0129] (See FIG. 8e for display.)

[0130] DATABLE:

[0131] <TABLE BORDER=1>

[0132] <TR>

[0133] <TD>Name</TD>

[0134] <TD>Type</TD>

[0135] <TD>Value</TD>

[0136] <TD>Sec Value</TD>

[0137] <TD>Cash Value</TD>

[0138] <TD>Loan Rate</TD>

[0139] <TD>Buying Power</TD>

[0140] <TD>Money Market</TD>

[0141] <TD>Action</TD>

[0142] </TR>

[0143] {DATABLE=102:portfolio}

[0144] <TR>

[0145] <TD>{CELL#0=102:1“USER1”}</TD>

[0146] <TD>{CELL#1}</TD>

[0147] <TD>{CELL#2}</TD>

[0148] <TD>{CELL#5}</TD>

[0149] <TD>{CELL#8}</TD>

[0150] <TD>{CELL#11}</TD>

[0151] <TD>{CELL#14}</TD>

[0152] <TD>{CELL#17}</TD>

[0153] </TR>

[0154] {/DATABLE}

[0155] </TABLE>

[0156] (See FIG. 8f for display)

[0157] BUTTON: {BUTTON=102:1“USER2”[VALUE=“Add New Portfolio”]}

[0158] (See FIG. 8g for display.)

[0159] The foregoing illustrates the example of how UNML may be converted to HTML. Conversion of UNML to other markup languages may be implemented following a similar approach by one skilled in the art.

[0160] (c) UNML Language

[0161] Basic UNML language element is the GUI element definition triplet enclosed in the square brackets:

[0162] Triplet=:[{Type}:{Name}:{Value}]

[0163] where:

[0164] Type is UNML code defining the GUI element;

[0165] Name is any text or binary value to show on the screen;

[0166] Value—optional field, containing text or binary value and defining default value of the element or return code, if the element is selected.

[0167] Parts of the UNML triplets are separated by the ‘:’ (column) symbol. If Name or Value fields contains column symbols, these symbols should be “escaped” by the ‘\’ (backslash) symbol. The meaningful backslash symbols should be “escaped” too.

[0168] UNML Type is 8-digits numeric value, composed of the four 2-digits components:

[0169] Type =:{Main type}{Subtype}{Command}{Format}

[0170] Main types, currently supported by UNML:

[0171] Screen;

[0172] Text;

[0173] Numeric field;

[0174] Image;

[0175] Input field;

[0176] Command button;

[0177] Menu;

[0178] Delimited text.

[0179] Subtypes, currently supported by UNML:

[0180] Prompt (for the Main type of Text);

[0181] Entry format (for the Main type of Input field);

[0182] Menu Item Value (for the Main type of Menu);

[0183] Menu Item Index (for the Main type of Menu);

[0184] Menu Item (for the Main type of Menu);

[0185] Menu Command Item (for the Main type of Menu);

[0186] Integer Format (for the Main types of Input field and Numeric field);

[0187] Float Format (for the Main types of Input field and Numeric field);

[0188] Fractions Format (for the Main types of Input field and Numeric field);

[0189] 32-nd Fractions Format (for the Main types of Input field and Numeric field);

[0190] Table Column Names (for the Main type of Delimited text).

[0191] Formats, currently supported by UNML:

[0192] Line;

[0193] Wrap;

[0194] Left;

[0195] Center;

[0196] Right.

[0197] (d) Defining a Screen Using UNML

[0198] UNML screen definition usually contains:

[0199] HTML header with the server application URL;

[0200] optional screen identification triplet, which can be used by the UNML browser to define a screen title and load screen layout template;

[0201] set of GUI elements triplets;

[0202] HTML footer.

[0203] <HTML>

[0204] <A HREF=“Server Application URL”></A>

[0205] [Type13 screen:screen_name:screen_id]

[0206] [Type:Name:Value]

[0207] . . .

[0208] [Type:Name:Value]

[0209] </HTML>

[0210] (e) Defining GUI Element Using UNML

[0211] Defining different GUI elements require different number of UNML triplets. In addition, some GUI elements require Value component of a triplet and some—not.

[0212] i. Text Fields

[0213] Text field definition consists of one triplet. Text field triplet Type part allows specifying Subtype of Prompt and any of the supported Formats. Text field triplet does not require a Value part.

[0214] ii. Numeric Fields

[0215] Numeric field definition consists of one triplet. Numeric field triplet Type part allows specifying datatype Subtype (Integer, Float, Fraction or 32-nd Fraction) and any of the supported Formats. Numeric field triplet does not require a Value part.

[0216] iii. Image

[0217] Image definition consists of one triplet Image triplet Name part should contain the title of the image and Image field triplet Value part should contain the path to the image file on the server.

[0218] iv. Input Field

[0219] Input field definition consists of one triplet. Numeric field triplet Type part allows specifying data type Subtype (Integer, Float, Fraction or 32-nd Fraction) and any of the supported Formats. Input field triplet Name part should contain the name of the server variable in which the value will be stored. Input field triplet does not require a Value part, but if the Value part is supplied, it is used to set the initial value of the variable, specified by the Name part of the triplet.

[0220] v. Command Button

[0221] Command button definition consists of one triplet. Command button triplet Type part should contain Command component set to 01. Command button triplet Type Subtype and Format components are ignored. Command button triplet Name part should contain the name of the button. Command button triplet Value part should contain the action code (unique in the scope of the screen) which will be returned to the server, if the button is pressed.

[0222] vi. Menu

[0223] Menu definition consists of multiple triplets in the following order:

[0224] Menu Name Definition Triplet

[0225] Menu Item definition triplet

[0226] . . .

[0227] Menu Item definition triplet

[0228] vii. Menu Name

[0229] Menu Name definition triplet Type part allows specifying Subtype of Menu Item Index or Subtype of Menu Item Value. In case of specifying Subtype of Menu Item Index the sequential index (starting with 1) of the Menu Item will be returned, if the Item is selected. If the Subtype of Menu Item Value is specified, the Value part of the Menu Item triplet will be return, if the Item is selected. Menu Name definition triplet Name part should contain the name of the server variable in which the value will be stored. Menu Name definition triplet Value part is used to define the default Menu Item.

[0230] viii. Menu Item

[0231] Menu Item definition triplet Type part should have Main type of Menu and Subtype of Menu Item or Menu Command Item. Menu Item definition triplet Name part should contain the name of the Menu Item to be shown. Menu Item definition triplet Value part is optional, if Menu Name triplet Type part has a Subtype of Menu Item Index and is required, if Menu Name triplet Type part has a Subtype of Menu Item Value. In case of Subtype of Menu Item Value Menu Item triplet Value part should contain the value, which will be stored in the variable, specified by the Menu Name triplet Name part, if this item is selected.

[0232] ix. Delimited Text

[0233] Delimited text definition consists of one triplet. Delimited text triplet Name part should contain the text, delimited by “tab” and/or “new line” symbols. Delimited text triplet does not require a Value part.

[0234] An example of the UNML screen definition with UNML “wrapped” between HTML header and footer to comply with HTTP protocol is as follows:

[0235] <HTML>

[0236] <A HREF=“/cgi-bin/wrql/cc.dev/wtrade_cpp_html/0000000002302000W-trade/ID=5”></A>

[0237] [05040000:Menu:1] 

[0238] [05060000:Accounts:13] 

[0239] [05060000:Place order:14] 

[0240] [05060000:Get quote:15] 

[0241] [05060000:Order list:16] 

[0242] [05060000:Event list:17] 

[0243] [05060000:Notifications:18] 

[0244] [05060000:Alerts:19] 

[0245] [05060000:Look up:20] 

[0246] [01000011:1:Account\:098-05007] 

[0247] [05110000:Symbol Type Value $:] 

[0248] [05030000:security:MSFT|1] 

[0249] [05050000:MSFT Stock 86250.000 MSFT—MICROSOFT CORP

[0250] Quantity 1000

[0251] Total value $86250.000:MSFT|1] 

[0252] [05050000:NSCP Stock 18093.750 NSCP—NETSCAPE COMMUNICATIONS CORP

[0253] Quantity 750

[0254] Total value $18093.750:NSCP|1] 

[0255] [04000100:Get quote:3] 

[0256] [04000100:Allocation:4] 

[0257] [04000100:Place order:5] 

[0258] </HTML>

[0259]
FIG. 6 and FIG. 7 are actual screen displays for the “PalmPilot” PDA device (by U.S. Robotics) corresponding to the UNML screen definition given above.

[0260] Deployment Options

[0261] As previously mentioned, it is possible to deploy the enterprise system 50 in various combinations on multiple platforms. More specifically, some most common deployment options for various levels of system uses are as follows:

[0262] a) Entry-Level Configuration

[0263] This configuration runs all system components on the same computer. It is possible to use the same computer as the Web server 52 is running on, making initial hardware costs minimal. In this case only one application server 58 is running in the system.

[0264] b) Advanced option in Homogeneous System

[0265] This configuration is used when multiple application servers 58 are required because of increasing load. In such configuration each additional computer contains an application server 58 with its own configuration file, that determines which applications it is capable of running. This computer should also contain the application code that will be invoked by the application server 58.

[0266] c) Advanced Option in Heterogeneous System

[0267] This option should be used when inter-related applications on multiple platforms are deployed in the same architecture. For example, a Visual Basic application has been developed using the development kit for Visual Basic and another application has been developed under the C++ system. Both applications can be seamlessly integrated at the deployment stage under the same architecture.

[0268] d) Advanced Option Over the Firewall

[0269] The enterprise system 50 can be configured to run securely through a network system firewall, so that the Web server 52 which is running on an external network is accessing the system manager 56 running within the firewall as a specialized proxy. The application servers 58 in this configuration are running inside the firewall securely accessing the proprietary databases in a controlled environment. This way, there is no need to move data outside the firewall, thus eliminating possible costs of data synchronization.

[0270] In the Advanced configuration option, multiple application servers are running on multiple hardware servers connected to a network. The system manager distributes the load between these application servers. Each application server can run multiple instances of multiple applications. In addition, application servers can run on various hardware and software platforms simultaneously, including platforms that are incompatible with each other.

[0271] Application Development

[0272] The enterprise system's unified architecture provides a way to quickly and cost-effectively develop large scale IP network systems that can handle the most complex applications and any number of users. Unlike other software infrastructure products, the unified architecture offers a familiar application development environment where programmers can work with the languages and programming methodologies they already know. Rather than forcing programmers to learn unfamiliar and difficult proprietary languages, or limiting the user base to those familiar with object-oriented programming, the unified architecture's infrastructure enables programmers to develop large-scale IP network applications the way they have been developing other applications. This eliminates re-training and reduces both development and maintenance costs, while allowing rapid application deployment. Since the unified architecture provides enterprise-class application availability, performance, and scalability, companies can now leverage their existing business-applications and business knowledge to create the high-value, strategic Web Systems, Intranets, Extranets they need for rapid business growth. In addition, the unified architecture delivers lower deployment costs, reduced system administration expenses, and improved overall system performance.

[0273] To further facilitate development of new applications, or incorporation on previously developed application, written in any existing language, software development kits may be developed for C, C++, Java, PERL, COBOL, FORTRAN, and RPG, as well as visual tools.

Report Query Language (“RQL”)

[0274] A new programming language has been created to make it significantly easier to develop new applications, e.g., for use with the enterprise system 50 in an IP network environment.

[0275] The Internet has created a demand for new classes of tools that let programmers build many different types of applications which work with existing (legacy) systems and data—without having to learn complex, proprietary languages and without having to change they way they currently work. RQL is a high-level platform independent programming language specifically designed to address the challenges of creating complex system, database and network administration applications, as well as database applications and enterprise wide reporting applications for “traditional” client/server, IP network and Internet/Intranet environments. RQL also includes extensions that allow developers to rapidly create state-of-the-art IP network, such as Internet, applications for Intranets and Web sites. This includes corporate reports, on-line databases and catalogues, and content rich Web sites. A “run time engine” (“RTE”), and various “software development kits” (“SDK”s) are also available for RQL.

[0276] RQL Features

[0277] Unlike like many Internet-centric application development tools emerging today, RQL is a robust and flexible technology addresses application development issues equally well in both client/server and Internet/Intranet environments. This is because RQL is not an existing tool that has simply been adapted for use in the Internet/Internet environment, like many others. RQL uses a simple but flexible syntax based on familiar grammar (so the learning curve is minimal). However, it is also robust and flexible enough to allow programmers to implement the same, extensive functionality as they can now implement only by using other, more cumbersome general purpose languages.

[0278] Also unlike other application development tools, RQL provides programmers with straightforward ways to incorporate legacy code, custom libraries and additional programming in other languages into their web applications—quickly and easily. It is one of a small number of tools that are based on and integrate with industry standard languages, and the only one of its kind to utilize a C based API, and allow programmers to merge legacy code with product code, and vice versa.

[0279] In addition, RQL applications can be deployed with virtually all major database management systems including Oracle, Sybase, Informix, Computer Associates (Ingres), and Microsoft's SQL Server. RQL's cost-effectiveness is enhanced by Data Sources that enable access to data from all kinds of relational and non-relational databases. Data Sources are available for databases from Sybase, Oracle, Informix, and Microsoft, and other Data Sources to meet the particular needs of vertical markets (for example, Bloomberg and Telerate data feeds for the financial industry, and SABRE for the travel industry.)

[0280] RQL is designed to support all major proprietary web server interfaces such as Microsoft's ISAPI and Netscape's NSAPI, as well as the standard Common Gateway Interface, so it can be deployed with any web server. Various SDKs will allow programmers to build new applications or reuse legacy code written in virtually any standard programming language, including C, C++, PERL, Java, Visual Basic and others.

[0281] RQL Functions

[0282] RQL is a new, high-level programming language that allows programmers to rapidly create complex database applications and reports in the client/server environment—without having to code the extensive data manipulation logic necessary with other commonly used general purpose languages. RQL provides a programming environment similar to C, C++ and PERL. However, RQL extends these languages to enable the application developer to easily manipulate and format relational data that is accessed using standard SQL. At the same time, RQL is simpler to use because it incorporates only those constructs that are required for robust data access and data manipulation. RQL is an exceptional tool for creating sophisticated applications, data manipulation programs and complex, enterprise-wide reports.

[0283] Since RQL uses a simple but flexible syntax based on familiar grammar, the learning curve is minimal. Any database application developer can program in RQL from day one. Yet, RQL's robust features allow the developer to implement the same functionality as any other general purpose language. The language also provides the developer with compact and straightforward ways to implement tasks that incorporate legacy code, custom libraries and additional programming in other languages—quickly and easily.

[0284] RQL is based on the ANSI-89 version of SQL. ANSI-92 compliant version may be developed. RQL includes native drivers to most popular relational databases so developers can access multiple database engines in the same program. Since RQL is based on a common standard, it's easy to write platform-independent programs can be easily migrated from RDBMS to RDBMS (“relational database management system”).

[0285] RQL includes extensions that allows developers to rapidly create state-of-the-art Internet applications for Corporate Intranets and Web Sites—including corporate reports, on-line databases and catalogues, and content rich Web Sites. RQL works with any Web browser, and programs developed in RQL will run on virtually any industry-standard Web Server. Since RQL is self-contained, complete RQL applications can be packaged for distribution throughout an organization. Also, commercial developers can create vertical market applications for resale, if desired.

[0286] In addition, a significant advantage of RQL over other general purpose languages is that it eliminates the need for direct programming of CGI scripts and Web Server API's. RQL is designed to work with standard CGI and most major Web Server interfaces (for example, NSAPI, ISAPI).

[0287] With general purpose programming languages such as C or PERL, programmers have to work with particulars of a specific database API, including conversion of data types, handling NULL values and so forth. Even in more advanced object-oriented languages, such as Java, C++ or PERL, the class libraries designed to hide the complexities or the API's, do not actually simplify the processing and grouping of records that are present if every data processing application. RQL solves these problems in a consistent and transparent manner and provides programmers with a light and simple environment. Based on the fact that C is the most popular programming language in the client/server environment, RQL syntax is very similar to ideas found in C. As such RQL contains all required data flow statements like if, while and for, functions, variables and other elements typically found in a procedural language. Additionally, to improve text processing, RQL features standard-based pattern matching and string parsing operators that are similar to those found in PERL.

[0288] Unlike PERL and like strong-type programming languages, RQL does not allow operations on variables of incompatible types. This feature significantly simplifies run-time debugging of programs written in RQL. All of RQL data types have been designed and optimized to provide the programmer with powerful, yet easy to use tools for working with text and data. All database values are mapped to RQL types automatically and are accessible to the programmer immediately upon retrieval like other RQL variables. The NULL, or ‘undefined’, type is a native RQL type, allowing correct exchange of data between the database and the application.

[0289] Data Source and Data Iterator

[0290] To process data from external sources RQL introduces two very important concepts: Data Source and Data Iterator. Data Source is actually any external database or data feed. RQL communicates with Data Sources in a consistent manner through drivers (e.g., distributed by Unistra Technologies, LLC). From the program standpoint, the syntax to call a Sybase database will look the same as to open a flat file. However, unlike ODBC (Open Database Connectivity), RQL not only allows the programmer to use native language of the Data Source, but allows to access Data Sources that have no ODBC drivers.

[0291] RQL also allows access of extensions in the Data Sources that are not available through ODBC since all exchange is performed through native Data Source drivers. Currently, most relational databases, basic networking and some vertical market data feeds are supported as Data Sources. Driver may be developed for OLE, CORBA, SNMP and other distributed protocols to enable rapid development of light and easily understandable programs communicating with such Data Sources.

[0292] Another innovation of RQL is Data Iterator, which serves as the basis to processing of data received from any Data Source. Data Iterator contains components that handle processing of individual records and record groups, providing programmers with a combined declaratively-procedural interface to data processing. The foundation of this approach is that the programmer defines a block of RQL operators to process records and groups, as well as conditions, such as no records in the set or group, beginning or end of processing group, beginning or end of the data set. Everyone who had experience writing purely procedural reports in PERL or C knows that this is the most tedious and error-prone part of the job.

[0293] Additionally, RQL provides functionality that reduces the amount of code the programmers have to write while processing record groups, by allowing definition of aggregate statements. Those aggregate expressions are calculated automatically and allow incorporation of arbitrarily complex RQL code. The amount of code the programmer has to write is decreased significantly and the code becomes simpler and easier to maintain.

[0294] To output the result of the calculations RQL uses output templates. Those output templates allow any kind of information to be sent to standard output, including HTML, plain text and other markup and type-setting languages. RQL also uses the same output template to send data to Data Sources, but the rules of data formatting are different.

[0295] Output templates are generally defined to run over Data Sources, therefore by opening a connection to Sybase one can use Data Iterator to read data from the Data Source and output template to send data and command to it. RQL also contains Data Source Drivers specifically designed to data load into Data Sources, which makes it very useful for loading large amount of information that is collected from multiple sources.

[0296] In a single RQL programs, multiple connection to multiple Data Sources can be used simultaneously, so there can be an application that connects to Sybase and some financial data feed and produces an end-of-the day portfolio report with the latest data that is coming from the feed combined with the account information in the Sybase database.

[0297] Data Warehouse users can find RQL very useful in extracting and loading data. Support for multiple database and platforms makes development easy and does not require intermediate files and data conversion between programs. Native support for database types ability makes it more straightforward to move data from source database to the warehouse and group processing make summary calculations pretty straightforward.

[0298] RQL programs can also be developed on one platform and deployed on many others. RQL code is platform independent and can be either processed in text form by RQL interpreter or compiled into RQL object code to be processed by RQL run time engine.

[0299] RQL Run Time Engine (“RTE”)

[0300] The RQL RTE runs database applications and reports over Intranets and Web sites. The RTE takes the code of a precompiled RQL application and executes it in a multithreaded environment that facilitates database access—and provides high performance with excellent response times. Each RQL program runs in its own secure thread, so corporate data and commercial Internet transactions are protected.

[0301] For further details of the RQL, a copy of the “Request Query Language Reference Guide” for the RQL software product distributed by Unistra Technologies, LLC is attached as Appendix A, and documentations relating to various examples of Data Sources (including “RQL File Data Source”, “RQL ODBC Data Source”, “RQL Process Data Source”, “RQL Socket Data Source”, “RQL Sybase Data Source”, and “RQL Sybase BCP Data Source”) are attached as Appendix B. These Appendices are fully incorporated by reference herein.

IP Network Based Trade System

[0302] Referring now to FIG. 4, the IP network based trade system 20 described in connection with FIG. 2 may be implemented with the unified architecture of the enterprise system 50 above. The trade system 20 consists of a trade system manager 62, one or more trade application server 64, and one or more trade application 66. The trade system manager 62 corresponds to the system manager 56 in FIG. 3. The trade application servers 64 correspond to the application servers 58 in FIG. 3. The trade applications 66 correspond to the application 54 in FIG. 3. The trade system manager 62 and the trade application servers 64 have similar generic system characteristics and functions as those of the enterprise system manager 56 and application servers 58 discussed before (e.g., the trade system manager has the same Capture Client function), except that the specific information and transactions being handled by the trade system specifically relate to financial trading in this embodiment. A trading database 68 may be provided in addition to any proprietary databases 70 associated with the existing trade execution system 22. For systems with a trade alert function, an alert system 72 is provided in the trade system 20.

[0303] Trade System Manager; Trade Application Servers

[0304] The trade system manager 62 brings order and logic to busy Internet trading environments by binding together all system components and connecting unconnected “hits” from each trader into a single session. It also provides load balancing and high availability by routing traders to the least busy trade application server 64. The trade application servers 64 accommodate the simultaneous trading activities of an unlimited number of traders by managing instances of the trade application 66 as required for each. Any number of trade application server 64 can be transparently added, on the fly, for complete scalability. Each application server 64 may be provided with an API 65, which is used to couple to any existing trade applications without the need to modify the latter.

[0305] While FIG. 4 shows one trade system manager 62, more than one trade system managers may be provided, each coupled to a group of trade application servers 64.

[0306] Trade Applications

[0307] Each trade application 66 contains one or more specific functions that process the traders' requests received over the Internet. Referring to FIG. 5, these functions may include interfacing functions such as: trader setup and configuration (block 80), coordination of interactions of the trade execution system 22 and the transaction requests from users received through the network 25; information delivery from the trade execution system 22 to the traders; trader login (block 82) (which may include encryption, trader authentication, trader account verification, and other trader/account specific functions); identification of user requests; and routing of user requests to the appropriate trade execution system 22 (if there is more than one). The trade applications 66 also include trade modules which perform trade specific add-on functions or shell functions that are not found in the trade execution system 22, including the following function categories: management (block 84), place orders (86), order status (88). Within each category, there may a series of functions and sub-functions that are specific to trading, which are exemplified in FIG. 5. The trade applications 66 may be developed using the RQL discussed above.

[0308] Trade Alert

[0309] The trade alert system 72 is a dedicated trade application. Referring to FIG. 5, it may include both alert messaging (block 90) and order confirmation (block 92) functions.

[0310] Independent of any request on demand by the trader, the trade alert system 72 initiates a dial out to the cellular phone (or other types of interactive devices) of specific trader or traders to alert them to, for example, trading price fluctuations, or simply to report information and news which the traders subscribed to (i.e., information the trader requested the trade system 20 to provide on a regular basis or when available basis). Depending on the device, the alert system formats the alert information in UNML, HTML and/or HDML, and sends it via the Web server, the Internet, and the wireless gateway to the traders' wireless device (e.g., a cellular phone, pager, etc.). The alert is displayed on the screen of the trader's wireless device. The traders can react immediately to the alert by pressing one or more buttons, for example, to request a trade. For example, as the alert is displayed on the screen via the built-in browser of a trader's cellular phone, the browser also displays graphics or menu driven menu prompts for the trader to select an action in response to the alert. The available prompts may represent a buy-request, a sell-request, a clear-screen request, and other user-friendly prompts. The trader only needs to move a cursor and/or press the corresponding number button or softkey to activate the desired action associated with a desired prompt. There may be one or more additional levels of prompts before the trader's request is sent from the trader's cellular phone (e.g., a confirmation prompt for the trader to confirm a sell or buy request before such request is sent). The trade system is configured to interface with the trader's existing interactive device in a manner such interface may be fully configurable to meet the requirements of any trading system implementation. It is understood that similar or different configurations may be implemented on other types of wireless devices to accomplish the Trade Alert function and trader's response without departing from the scope and spirit of the present invention.

[0311] Trade Confirmation

[0312] A confirmation function for reporting the status of the trader's request may be built into the trade alert system 72 or in a separate system. Immediately upon completing execution of a trade request by the trade execution system 22, the trade is confirmed by the trade alert system 72 in a brief message via email, voice mail, code paging, or the like messaging to the trader's wireless device. Further, depending on the configuration initially set by the trader, a full report concerning the trade may be sent to the trader's designated email addresses and/or fax numbers, which may include a receipt, invoice, account statement, etc. The trader has the option to receive the full report on the spot using the wireless device if so desired.

[0313] Further, the trade system 20 may include the feature for allowing the trader to customize the browser format and functions to suit the trader's personal preference, including configuring user setup with respect to the desired access security level, alert subscription and preferences, confirmation preferences, and other preferences for interfacing with the trade system 20. Details of possible browser functions are omitted herein, as they can be easily devised without undue experimentation to suit ease and convenience of use of users.

[0314] Trade Application API

[0315] In order to facilitate quick and consistent integration of trade system 20 with the existing trade execution systems 22, well-defined APIs are used for coupling the trade application 74 to the trade execution system 22. These APIs avoids the need to modify the functionality of the trade execution system 22. At a system level, the manner of access to the trade execution system 22 (e.g., by wired or wireless network) is indistinguishable to the trade execution system 22. Such approach allows integration with virtually any existing trade execution system 22 on practically any platform. Specifically, two separate API systems are created: a trade execution API (“TE API”) 74 and a trade alert API (“TA API”) 76. The TE API 74 provides the functionality of delivering trade information and trader requests to the trade execution system 22 and the TA API 76 allows the trade execution system 22 to deliver real-time trade information to the trader. The cooperation of the two types of APIs with the trade system's core functionality provide an extremely flexible and secure way to implement two-way communication without actually modifying the trade application itself.

[0316] The TE API 74 allows delivery of trade information and trader requests from a trade application to a trade execution system 22 maintained by a company. It provides stubs, or hooks that are called at predefined moments in various steps in trade processing by a Core Trade Processing (CTP) module located in the trade application 66. These stubs have to filled with code that actually performs the interface with the trade execution system 22. The code is customer dependent and is implemented during the integration phase.

[0317] Such an architecture provides significant advantage because the CTP code does not have to be modified during the integration phase. The TE API 74 functions provide all the necessary information for the CTP to present to the user and to deliver information to the execution system. TE API 74 functions include Portfolio Management, Order Management, User Authentication, Quote Interface and Event Subscription subsystems. These subsystems can interact with different components in the Execution System and in conjunction with the TA API provide full two-way interaction between the user and the Execution System. Major functions and their descriptions are provided in the following table:

1SubsystemFunction NameDescriptionUserWTE_user_authVerifies validity ofAuthenticationuser/password combinationUserWTE_user_registerRegisters the user in theAuthenticationexecution systemUserWTE_change_passwordModifies user password in theAuthenticationexecution systemUserWTE_get_user_infoRetrieves information aboutAuthenticationuserPortfolioWTE_get_portfolio_listGet list of user's accountsManagementPortfolioWTE_get_default_portfolioRetrieves user's defaultManagementaccountPortfolioWTE_change_default_portChanges user's default accountManagementPortfolioWTE_get_security_listRetrieves list of securities inManagementthe accountPortfolioWTE_add_to_portfolioAdds a security to a watch listManagementQuote InterfaceWTE_get_market_infoRetrieves current informationabout the market conditionsQuote InterfaceWTE_is_market_timeChecks if the security iscurrently tradedQuote InterfaceWTE_get_quoteGet current market quote for asecurityQuote InterfaceWTE_security_lookupTicker lookup by companynameOrderWTE_post_orderSend an order to the executionManagementsystemOrderWTE_cancel_orderSend a cancellation request toManagementthe execution systemOrderWTE_get_orderRetrieve order informationManagementfrom the execution systemOrderWTE_get_user_pending_order_listRetrieve the list of pendingManagementorders for the userOrderWTE_get_user_hist_order_listRetrieve the list of transactionsManagementfor the userOrderWTE_gel_port_pending_order_listRetrieve the list of pendingManagementorders in the accountEvent SubscriptionWTE_get_event_listRetrieve list of eventsregistered for userEvent SubscriptionWTE_add_eventRegisters an eventEvent SubscriptionWTE_get_event_infoRetrieves information aboutthe eventEvent SubscriptionWTE_modify_eventUpdates modified event withnew information

[0318] The TA API 74 allows asynchronous delivery of real-time information to the user device from the Execution System. It is implemented as a library of functions that are called by an Alert Daemon located in the alert system 72 or the trade execution system 22 itself when a portion of information has to be delivered to the user. Since such information may be of different type, TA API 76 contains various subsystems for handling specific types of alerts. These subsystems include Trade Confirmation, and Custom Information subsystems. Major functions and their descriptions are provided in the following table:

2SubsystemFunction NameDescriptionTradeWTA_confirm_orderSends order confirmationConfirmationinformation to the userTradeWTA_reject_orderNotifies the user that the orderConfirmationwas rejected by the executionsystemTradeWTA_cancel_orderNotifies the user that the orderConfirmationwas cancelled by the executionsystemCustomWTA_send_alertSends a simple alert to the userInformation

[0319] An important feature of TA API 76 is its security, which is important since sensitive information is delivered asynchronously to a user device. For each alert, only the type and its title are actually delivered to the user, while the full content stored in the trading database and are only revealed to the user after his/her logging into the trade application. This prevents sensitive information from being revealed accidentally when the device is out of the owner's hands.

[0320] When the trade system 20 is being integrated with a particular trade execution system 22, the programmer will use a library of CTP and TA modules, and a file with TE function stubs. Those functions will be delivered may be found in a single file and will have no code in them. The programmer working on the integration will write the actual code for the integration with particular trade execution system 22. Additionally, a sample makefile is included in the package. This makefile can be modified with the additional parameters necessary for successful compilation of the integration code. The functions will be called at the appropriate time during trade processing, and the returned results will be used by CTP to notify the user about the status.

[0321] Since several popular trade execution systems 22 and platforms currently exist in the marketplace, a number of prepackaged implementations of TE and TA APIs may be developed and prepackaged, so that no coding will be required during the integration process. This follows the principles of the enterprise system and its APIs. For those using an execution system that a prepackaged implementation has been developed, they can simply install the implementation and configure it to match with parameters of the actual installation of the trade execution system. Such turnkey configuration will significantly decrease cost of entry and integration time for the customer.

[0322] An example of a trade system that has been implemented in accordance with the present invention is the w-Trade Wireless Internet Trading System distributed by w-Trade Technologies, LLC for use with digital cellular phones, for example, and other digital user interactive devices. A copy of the User Guide (V. 2.0) for the w-Trade system is attached hereto as Appendix C. This Appendix is fully incorporated by reference herein.

[0323] The systems of the present invention have been described above in terms of functional modules in block diagram format. It is understood that unless otherwise stated herein, one or more functions may be integrated in a single physical or software module in an actual implementation, or a function may be implemented in separate physical or software modules, without departing from the scope and spirit of the present invention.

[0324] Further, unless other stated herein, the actual implement of each functional module taken alone does not form part of the invention. It is appreciated that detail discussion of the actual implementation of each module is not necessary for an enabling understanding of the invention. The actual implementation is well within the routine skill of a programmer and system engineer, given the disclosure herein of the system attributes, functionality and inter-relationship of the various functional modules in the systems. A person in the art applying ordinary skill can practice the present invention without undue experimentation.

[0325] While the invention has been described with respect to the described embodiments in accordance therewith, it will be apparent to those skilled in the art that various modifications and improvements may be made without departing from the scope and spirit of the invention. For example, the inventive concepts herein may be applied to design a wired or wireless system, based on the Internet, IP network, or other network technologies, for financial or other transaction systems, without departing from the scope and spirit of the present invention. Accordingly, it is to be understood that the invention is not to be limited by the specific illustrated embodiments, but only by the scope of the appended claims.

Claims

1. A system for interfacing user interactive devices with a transaction execution system to execute transactions requested by users, comprising: a network communicating the user interactive devices to the transaction execution system; and application means coupled to the network for interfacing between the user interactive devices and the transaction execution system and coordinating interaction of the user interactive devices with the transaction execution system.
2. A system as in claim 1 wherein the application means comprises alert means for initiating and sending information relating to the transactions to the user interactive devices via the packet-switched wireless network independent of any request on demand from the user.
3. A system as in claim 2 wherein the transaction execution system is a system which handles financial transaction.
4. A system as in claim 3 wherein the transaction execution system is a system which handles trading of financial instruments.
5. A system as in claim 3 wherein the information relates to trading of the financial instruments.
6. A system as in claim 2 wherein the application means further comprises confirmation means for sending the users via the network a confirmation that the transactions requested by the respective users has been completed.
7. A system as in claim 6 wherein the confirmation means includes configuration means that allows each user to select specific conduit for sending the confirmation and related information of the completed transactions to the respective users.
8. A system as in claim 7 wherein the application means further comprises means for monitoring the transactions requested by the users and verifying integrity of the transactions and/or status of the accounts of the users.
9. A system as in claim 1 wherein the transaction execution system is an existing system without capability to interface with the user interactive devices, and wherein the application means is configured to couple to such existing system to add the functionality of interfacing with the user interactive devices substantially without modification of the functionality of the existing system.
10. A system as in claim 9 wherein the application means is configured such that the manner of user access to the transaction execution system is indistinguishable to the transaction execution system at a system level.
11. A system as in claim 1 wherein the application means includes at least one API for integrating the functions of the transaction system and the transaction execution system without requiring significant modification to the transaction execution system.
12. A system as in claim 11 wherein the application means contains first and second APIs, and wherein the first API is structured to deliver information relating to user transaction request to the transaction execution system, and the second API is structured to deliver to the user information relating to the transaction.
13. A system as in claim 1 wherein the application means comprises: a plurality of transaction application servers; at least one transaction application coupled to each transaction application server and to the transaction execution system; and a transaction manager coupled to the plurality of transaction application servers, wherein the transaction manager is structured and configured to provide load balancing and high availability by routing user transaction requests to the least busy transaction application server.
14. A system as in claim 1 where the network comprises an IP network, and the transaction manager is structured and configured to connect unconnected information from various users received over the IP network into a single session.
15. A system as in claim 1 wherein the network includes a wireless network.
16. A system as in claim 15 wherein the wireless network is a digital packet-switched network.
17. A system as in claim 1 wherein the network includes a distributed network which operates on the TCP/IP protocol.
18. A system as in claim 17 wherein the distributed network is an IP network.
19. A system as in claim 1 wherein the user interactive devices are based on different operating platforms.
20. A system as in claim 19 wherein the transaction execution system communicates with the user interactive devices in a device independent fashion.
21. A system for interfacing user interactive devices with a transaction execution system to execute transactions requested by users, comprising: a network providing access to the transaction execution system by the user interactive devices; application means coupled to the network for interfacing between the user interactive devices and the financial transaction execution system and coordinating interaction of the user interactive devices with the transaction execution system; wherein the financial transaction execution system is an existing system without capability to interface with the user interactive devices, and wherein the application means is configured to couple to such existing system to add the functionality of interfacing with wireless user interactive devices substantially without modification of the functionality of the existing system.
22. A system as in claim 21 wherein the application means is configured such that the manner of access to the transaction execution system by the user interactive devices is indistinguishable to the financial transaction execution system at a system level.
23. A system for interfacing user interactive devices with an executing transaction system to execute transactions requested by users, comprising: a network providing access to the transaction execution system by the user interactive devices; and an add-on transaction system coupled between the transaction execution system and the network, wherein the transaction system coordinates interaction of the user interactive devices with the transaction execution system.
24. A system as in claim 23 wherein the transaction system interacts with the user interactive devices independent of the functions of the financial transaction execution system.
25. A system for interfacing user interactive devices with an executing transaction system to execute transactions requested by users via an IP network, comprising: a network interfaced between the user interactive devices and the transaction execution system, said network including the IP network; and a transaction system between the transaction execution system and the network, wherein the transaction system coordinates interaction of the user interactive devices with the transaction execution system based on TCP/IP protocols.
26. A system as in claim 25 wherein the network also includes a wireless network between an IP network and the user interactive devices.
27. A method for executing transactions requested by users using user interactive devices, comprising the steps of: interfacing a network between the user interactive devices and the transaction execution system; interfacing a transaction system between the transaction execution system and the network; coordinating using the transaction system interaction of the user interactive devices with the transaction execution system.
28. A method as in claim 27 wherein the transaction system coordinates interaction with the user interactive devices independent of the functions of the financial transaction execution system.
29. A method for providing a transaction execution system with the functionality of interacting with user interactive devices via an IP network, comprising the steps of: interfacing a network between the user interactive devices and the transaction execution system; and interfacing a transaction system between the user interactive devices and the transaction execution system, wherein the transaction system coordinates interaction of the transaction execution system with the user interactive devices based on TCP/IP protocol.
30. An enterprise system for interfacing between an IP network and an existing system, comprising: a system manager coupled to a Web server; a plurality of application servers coupled to the system manager; and at least one application coupled to each application server and the existing system.
31. An enterprise system as in claim 30 wherein the applications each has an API for integrating the functions of the existing system and the respective applications without requiring significant modification of the existing system.
32. An enterprise system as in claim 31 wherein a first application has a first API and a second application has a second API, and wherein the first API is structured to deliver information received from the IP network to the existing system, and the second API is structured to deliver to the IP network information relating to the existing system.
33. An enterprise system as in claim 30 wherein the applications operates independent of the functions of the existing system.
34. An enterprise system as in claim 30 wherein the applications are coupled to the existing system with requiring significant modification to the existing system.
35. An enterprise system as in claim 30 wherein the applications are configured such that the coupling of the system manager to the IP network is indistinguishable to the existing system at a system level.
36. An enterprise system as in claim 30 wherein the system manager is structured and configured to connect unconnected information from various users received over the IP network into a single session.
37. An enterprise system as in claim 36 wherein the system manager provides an application state to information received from the IP network.
38. An enterprise system as in claim 30 wherein the existing system is a transaction execution system which executes transactions requested by user via the IP network, the system manager is a transaction system manager, the application servers are transaction application servers and the applications are transaction applications, wherein the applications interact with the users via the IP network independent of the functions of the transaction execution system.
39. An enterprise system as in claim 31 wherein the APIs maintain a same set of base functionality, which is expressed in terms of target operating platform.
40. An enterprise system as in claim 39, wherein the functionality are such that would allow a Web application developer to extract data entered by the user into the Web page and store this information in program variables and as a persistent context, and to present newly generated data and Web pages to the user, thereby allowing development of Web applications without requiring knowledge of particulars of interface implementations for a specific Web server.
41. A method as is claim 39, wherein a special set of APIs is developed for each operating platform on which the applications run on, and wherein each set utilizes specific protocols of the underlying operating platform while presenting the same functionality to the user for different operating platforms.
42. A method as in claim 41, wherein a simple compilation of the application on a particular operating platform with respect to the corresponding set of APIs would allow the application to be migrated to the operating platform without code changes or usage of a further API.
43. A method of interfacing between a client and an application server across a network, comprising the step of providing a browser to interface the client with the application server, wherein the browser is based on a screen definition language that allows every screen to be independent of other screens and every element of the screen to be independent from other elements.
44. A method as in claim 43, wherein the application server is structured and configured to convert the screen definition language to another set of screen definition language on-the-fly so that the application server may communicate with clients that use browsers that are compatible with said another set of screen definition language.
45. A method as in claim 44, wherein said another set of screen definition language is a markup language.
46. A method as in claim 45, wherein said markup language includes HTML or HDML.
47. A method as in claim 43, wherein screen layout information is stored at the client, wherein the browser renders the screen based on the data sent from the server and the stored screen layout information.
48. A method as in claim 47, wherein the application server includes one or more screen layout templates each based on a screen layout information, and wherein the scree layout templates are used to create screen data to be sent to the client.
49. A method as in claim 48, wherein the screen data sent from the server excludes screen layout information.
50. A method as in claim 43 further comprising the steps of: when an element in the browser is edited by the client, setting the value of the variable assigned to the edited element; and sending only the value of the variable to the server to represent the edited element.
51. A method as in claim 43 wherein the browser is device dependent and the variable sent from the server is device independent, which variable can be recognized by the device dependent browser.
52. A method of distributing screen information between a client and an application server across a network, comprising the steps of: providing a device dependent browser to interface the client with the application server, wherein the device dependent browser is associated with a screen layout; transmitting screen information from the server to the client in a device independent fashion, wherein the screen information is based on a screen layout template stored at the server; presenting the screen information at the client using the device dependent browser and based on the screen layout.
53. A method for programming an application for use in an IP network environment, comprising the steps of: creating program code for the application; providing a C-based API for the application; and merging, using the C-based API, existing program code that is based on one or more of C, C++, PERL, Java, Visual Basic programming languages.
54. A method as in claim 53, wherein the application created is platform independent.
55. A method for accessing and processing data from an external data source by an application in an IP network environment, comprising the steps of: creating the application using RQL programming language; accessing the external data source via a driver and based on native language of the external data source; and processing the data received from the external data source.
56. A method as in claim 55, wherein the external data source is accessed using syntax similar to opening a flat file.
57. A method as in claim 55, wherein the external data source is accessed without using ODBC drivers.
58. A method as in claim 55, wherein the processing step uses a data iterator which contains components that handle processing of individual records and record groups.
59. A method as in claim 55, further comprising the step of providing an output template to output the result of the processing step.
60. A method as in claim 55, wherein the step of processing uses a run time engine which processes the precompiled RQL application and executes it in a multi-threaded environment.
61. A method as in claim 55, wherein the application created using RQL programming language is platform independent.

Parent Case Info

[0001] This application is a continuation-in-part application of U.S. Provisional Application Serial No. 60/072,569, filed on Jan. 26, 1998, which is fully incorporated by reference herein.

Provisional Applications (1)

	Number	Date	Country
	60072569	Jan 1998	US

Continuations (1)

	Number	Date	Country
Parent	09229473	Jan 1999	US
Child	10455692	Jun 2003	US

Transaction execution system interface and enterprise system architecture thereof

Information

Publication Number

Date Filed

Date Published

Inventors

CPC

US Classifications

International Classifications

Abstract

Description

Claims

Parent Case Info

Provisional Applications (1)

Continuations (1)