Patent Grant
7672879
The present invention is in the field of Internet navigation including various communication means and connection technologies. The present invention pertains more particularly to an interactive software interface suite for enabling management and transactional control of personal data including account data maintained on behalf of users by an entity providing data compilation, aggregation, and summary services.
The information network known as the World Wide Web (WWW), which is a subset of the well-known Internet, is arguably the most complete source of publicly accessible information available. Anyone with a suitable Internet appliance such as a personal computer with a standard Internet connection may access (go on-line) and navigate to information pages (termed web pages) stored on Internet-connected servers for the purpose of garnering information and initiating transactions with hosts of such servers and pages.
Many companies offer various subscription services accessible via the Internet. For example, many people now do their banking, stock trading, shopping, and so forth from the comfort of their own homes via Internet access. Typically, a user, through subscription, has access to personalized and secure WEB pages for such functions. By typing in a user name and a password or other personal identification code, a user may obtain information, initiate transactions, buy stock, and accomplish a myriad of other tasks.
One problem that is encountered by an individual who has several or many such subscriptions to Internet-brokered services is that there are invariably many passwords and/or log-in codes to be used. Often a same password or code cannot be used for every service, as the password or code may already be taken by another user. A user may not wish to supply a code unique to the user such as perhaps a social security number because of security issues, including quality of security that may vary from service to service. Additionally, many users at their own volition may choose different passwords for different sites so as to have increased security, which in fact also increases the number of passwords a user may have.
Another issue that can plague a user who has many passworded subscriptions is the fact that they must bookmark many WEB pages in a computer cache so that they may quickly find and access the various services. For example, in order to reserve and pay for airline travel, a user must connect to the Internet, go to his/her book-marks file and select an airline page. The user then has to enter a user name and password, and follow on-screen instructions once the page is delivered. If the user wishes to purchase tickets from the WEB site, and wishes to transfer funds from an on-line banking service, the user must also look for and select the personal bank or account page to initiate a funds transfer for the tickets. Different user names and passwords may be required to access these other pages, and things get quite complicated.
Although this preceding example is merely exemplary, it is generally known that much work related to finding WEB pages, logging in with passwords, and the like is required to successfully do business on the WEB.
A service known to the inventor and described in patent application Ser. No. 09/208,740 entitled “Method and Apparatus for Providing and Maintaining a User-Interactive Portal System Accessible via Internet or other Switched-Packet-Network”, provides a WEB service that allows a user to store all of his password protected pages in one location such that browsing and garnering information from them is much simplified. A feature of the above service allows a user to program certain tasks into the system such that requested tasks are executed by an agent (software) based on user instruction. The service stores user password and log-in information and uses the information to log-in to the user's sites, thus enabling the user to navigate without having to manually input log-in or password codes to gain access to the links.
The above-described service uses a server to present a user-personalized application that may be displayed as an interactive home page that contains all of his listed sites (hyperlinks) for easy navigation. The application lists the user's URL's in the form of hyperlinks such that a user may click on a hyperlink and navigate to the page wherein login, if required, is automatic, and transparent to the user.
The application described above also includes a software agent that may be programmed to perform scheduled tasks for the user including returning specific summaries and updates about user-account pages. A search function is provided and adapted to cooperate with the software agent to search user-entered URL's for specific content if such pages are cached somewhere in their presentable form such as at the portal server, or on the client's machine.
In addition to the features described above, patent application Ser. No. 09/523,598 entitled “Method and Apparatus for Obtaining and Presenting WEB Summaries to Users” describes a software agent used in conjunction with a search function that is enabled to navigate to any URL or group of URL's, provided as input by a user or otherwise deemed appropriate by the service provider, for the purpose of providing summary information regarding updated content for each URL, which may be presented as an HTML information-page to the user.
The above described service uses known site logic for navigating to specific “chunks” of data contained in Web pages at the site. Logic scripts are prepared by knowledge workers operating on behalf of users. With such scripts, gatherer agents may navigate directly to data portions that users are interested in.
Users who subscribe to many on-line services generally do all of their banking, investing, travel arranging, shopping, and so on while on-line with the Internet. Having all of his or her services available at one portal provides a convenience to a user in not having to remember a plurality of passwords, or to be required to physically log-on to each site. Similarly, the ability to obtain summary data associated with selected sites through one interface allows a user to greatly speed any decision making process related to his or her on-line activity. However, summary information may not help a user with certain other concerns. For example, obtaining accurate financial information concerning his entire portfolio of banking and investments would require much user calculation depending on the exact nature of the result desired. Similarly compiling a trend that reflects a user's on-line activity at a plurality of shopping services may also require considerable calculation to be performed by a user. Summary data presented in the above methods is general in nature and reflects such as updates, status of orders, and the like.
An Internet-connected portal system, known to the inventor, has a data repository, a data-gathering system, a request processor, a plurality of report algorithms, and a report processor. The request processor receives a request from a user and matches the request to an individual one of the report algorithms. The data-gathering subsystem accesses plural Internet sites associated with the user and extracts raw data therefrom according to needs of the report algorithm. The report processor processes the raw data according to the report algorithm into meta-summarized information defined by the report algorithm, and the portal system transmits the meta-summarized information as a report to a destination associated with the report request. In some cases there is an aggregated-data database in the data repository storing aggregated data retrieved for specific users periodically, and the request processor checks the aggregated-data database for needed data before requiring the data-gathering system to retrieve data from the associated Internet sites. In the instance that the needed data is stored in the aggregated-data database, the report is prepared from the aggregated data. Reports may be presented in a form such as to include text and graphic formats.
In view of various functional enhancements including the ability to provide calculative and solution-oriented reporting, it has occurred to the inventor that a single interface, through which summary and detailed data may be viewed and manipulated must be provided that is user-friendly, compact and interlinked in terms of request-to-result functionality wherein access and request actions may be performed by working within any category or department of data that may be available to be viewed through the interface. Current and prior-art interactive interface software used with typical data presentation services lacks the flexibility of providing multiple points of intractability within the interface as well as enabling cross-solution implementation across multiple categories of data viewable through the interface.
The above challenges exist with prior-art services in part because they lack much of the interactive capability required in order to enable a fully functional data interface, especially one that interfaces a user with a wide range of disparate data categories.
What is clearly needed is a single, interactive software interface for viewing pluralities of data categories and enabling action requests to be performed from within any one of the multiple data categories. A software interface such as this would greatly convenience users who must interact with a plurality of on-line services in order to effect and propagate on-line business activity related to their financial, employment, travel, recreational, and social activities and engagements.
In a preferred embodiment of the present invention, a software suite is provided for enabling viewing and manipulation of multiple categories of aggregated data compiled from a plurality of data sources and accessible through a single interface operated on a data-packet-network, the data sources available for direct network-access through multiple access points provided within the interface.
The software suite comprises, a calendar module having at least one display interface for enabling viewing and manipulation of time and date-sensitive calendar data, a transaction module having at least one display interface for enabling viewing and manipulation of financially oriented account data, a portfolio tracking module having at least one display interface for enabling viewing and manipulation of investment oriented account data, a net-worth reporting module having at least one display interface for displaying a solution-oriented net-worth report compiled from the aggregated data, a bill-payment module having at least one display interface for enabling viewing and initiation of payment action regarding current billing data and an account-alert module having at least one display interface for reporting time and event sensitive account alerts related to changes in account data due to occurring events or pre-configured time parameters.
In a preferred embodiment, the software suite is implemented on the Internet network. In this aspect, the plurality of data sources comprise service-access points maintained by service-hosting entities offering services accessible through the Internet. Also in a preferred aspect, the single interface (suite) is of the form of an HTML Web page served from a user-access point and downloaded by an accessing user into a Web browser. In one aspect, a personal computer is operated as a user-access device for accessing the interface. In another aspect, a handheld computer is operated as a user access-device for accessing the interface. Computational functions of the modules are, in a preferred embodiment, enabled by a database reporting software communicating with the various modules through application-program-interface implementation. In all aspects, the multiple-access points are URLs embedded within the at least one interface associated with each of the plurality of modules.
In one aspect, the software suite further comprises, a communications module having at least one interface for reporting existence of new communications events, an account-bookmarks module having at least one interface for listing URLs of the plurality of data sources and a travel-planning module having at least one interface for enabling configuration and initiation of travel plans. In preferred implementation, the modules are selectively cross-linked with each other for purpose of enabling the modules to share reporting aspects of the aggregated data and for enabling the user navigation between the modules.
In another aspect of the present invention, a network-based control system for controlling display, manipulation, and transaction parameters of aggregated data compiled from a plurality of data sources, the control capability extended through a single interface operated on a data-packet-network is provided. The control system comprises, a portal server operating on the network for enabling user-access to the system through the single interface, the single interface having a plurality of control and report modules for controlling categorization, viewing, reporting and manipulation aspects of the aggregated data, a mass data repository for storing the aggregated data, a database reporting software for accepting input from the software interface through individual ones of the control and report modules and for performing calculations, manipulations, and ordering transactions based on the received input and, a user-access device connected to the network for accessing the portal server and receiving the single interface.
In a preferred embodiment, the control system is implemented on the Internet network. The network-based control system further comprises multiple points of direct network-access to the plurality of data sources embedded into interfaces invoked by individual ones of the control and report modules. In preferred aspects, the aggregated data is personalized to an accessing user and limited to display in a personalized interface. Also in a preferred aspect, the multiple points of direct network access comprise embedded URLs. In all aspects, the control and report modules available through the single interface are capable of initiating service of at least one additional interface associated with an invoked module, the additional interface providing a more detailed accounting of the categorized data associated with the invoked module.
In one embodiment, the control and report modules are selectively cross-linked with each other for the purpose of sharing reporting aspects of the aggregated data and for enabling user navigation between the modules. In one embodiment, the user-access device is a personal computer. In another embodiment, the user access-device is a handheld computer.
In another aspect of the present invention, a method for enabling single-point control over various display, reporting, computation, and transactional aspects of data aggregated on behalf of a user from a plurality of data sources operating on a data-packet-network is provided. The method comprising the steps of, (a) providing a network-interface vehicle having a plurality of control and report modules embedded therein, the interface serving as the single-point control apparatus, (b) connecting the plurality of control and report modules to a database reporting software through application-program-interface implementation, (c) providing additional display interfaces launch-able from individual ones of the plurality of control and report modules, the display interfaces containing interactive links to utilities for configuring the aspects of data display and for ordering transactions through the modules and (d) rendering the network-interface vehicle accessible to the user operating a remote data-access device connected to the network.
In a preferred embodiment, the method is practiced on the Internet network. In one aspect of the method in step (a), the network-interface vehicle is of the form of an HTML Web page served from a user-access point and downloaded by the accessing user to a Web browser. In one aspect, in step (d), the data-access device is a personal computer. In another aspect, in step (d), the data-access device is a handheld computer. In a preferred aspect of the method in step (b), the computational functions of the modules are enabled and performed by the database reporting software. In preferred aspects in step (c), the additional display interfaces are linked to the individual control modules through hyper-linking. In this aspect in step (c), the modules are selectively cross-linked with each other for purpose of enabling the modules to share reporting aspects of the aggregated data and for enabling the user navigation between the modules.
Now, for the first time a single interactive software interface for viewing pluralities of data categories and enabling action requests to be performed from within any one of the multiple data categories is provided. A software interface such as this greatly services users who must interact with a plurality of on-line services in order to effect and propagate on-line business activity related to their financial, employment, travel, recreational, and social activities and engagements.
According to a preferred embodiment of the present invention, a unique Internet portal is provided and adapted to provide unique services to users who have obtained access via an Internet or other network connection from an Internet-capable appliance. Such an interface provides users with a method for storing many personal WEB pages and further provides search function and certain task-performing functions. The methods and apparatus of the present invention are taught in enabling detail below.
Internet 13 is representative of a preferred use of the present invention, but should not be considered limiting, as the invention could apply in other networks and combinations of networks.
ISP 15 in this embodiment comprises a server 31, a modem bank 33, represented here by a single modem, and a mass storage repository 29 for storing digital data. The modem bank is a convenience, as connection to the server could be by another type of network link. ISP 15, as is typical in the art, provides Internet access services for individual subscribers. In addition to well-known Internet access services, ISP 15 also provides a unique subscription service as an Internet portal for the purpose of storing many WEB pages or destinations along with any passwords and or personal codes associated with those pages, in a manner described in more detail below. This unique portal service is provided by execution of Portal Software 35, which is termed by the inventors the Password-All suite. The software of the invention is referred to herein both as the Portal Software, and as the Password-all software suite. Also, in much of the description below, the apparatus of the invention is referred to by the Password-All terminology, such as the Password-All Server or Pass-word All Portal.
ISP 15 is connected to Internet 13 as shown. Other equipment known in the art to be present and connected to a network such as Internet 13, for example, IP data routers, data switches, gateway routers, and the like, are not illustrated here but may be assumed to be present. Access to ISP 15 is through a connection-oriented telephone system as is known in the art, or through any other Internet/WEB access connection, such as through a cable modem, special network connection (e.g. T1), ISDN, and so forth. Such connection is illustrated via access line 19 from Internet appliance 17 through modem bank 33.
In a preferred embodiment a user has access to Internet Password-All Portal services by a user name and password as is well known in the art, which provides an individualized WEB page to the subscriber. In another embodiment wherein a user has other individuals that use his or her Internet account, then an additional password or code unique to the user may be required before access to portal 31 is granted. Such personalized Portal WEB pages may be stored in repository 29, which may be any convenient form of mass storage.
Three Internet servers 23, 25, and 27, are shown in Internet 13, and represent Internet servers hosted by various enterprises and subscribed to by a user operating appliance 17. For example, server 23 may be a bank server wherein interactive on-line banking and account managing may be performed. Server 25 may be an investment server wherein investment accounts may be created and managed. Server 27 may be an airline or travel server wherein flights may be booked, tickets may be purchased, and so on. In this example, all three servers are secure servers requiring user ID and password for access, but the invention is not necessarily limited to just secure services.
In a preferred embodiment of the present invention, a subscribing user operating an Internet-capable appliance, such as appliance 17, connects to Password-All Portal system 11 hosted by ISP 15, and thereby gains access to a personalized, interactive WEB page, which in turn provides access to any one of a number of servers on Internet 13 such as servers 23, 25, and 27, without being required to enter additional passwords or codes. In a preferred embodiment the software that enables this service is termed Password-All by the inventors. Password-Ai may be considered to be a software suite executing on the unique server, and in some instances also on the user's station (client). Additional interactivity provided by portal software 35 allows a connected user to search his listed pages for information associated with keywords, text strings, or the like, and allows a user to program user-defined tasks involving access and interaction with one or more Internet-connected servers such as servers 23, 25, and 27 according to a pre-defined time schedule. These functions are taught in enabling detail below.
Items listed in list 34 in this example may be considered destinations on such as servers 23, 25, and 27 of
In some embodiments one page 33 may be shared by more than one user, such as a husband and wife sharing a common account and subscription. An instance of this is illustrated herein with respect to the server labeled Mortgage.com wherein both a John and a Jane Doe are listed together under the column labeled user name. In another embodiment, a network of individuals, perhaps business owners, authorized co-workers, investment parties, or the like may share one application. In this way, system 11 may be adapted for private individuals as well as business uses.
After gaining access to application 33 which is served via Internet portal server 31 of
In another aspect of the invention new listings for a user's profile, such as a new passthrough to a bank or other enterprise page, may be added semi-automatically as follows: Typically, when a user opens a new account with an enterprise through interaction with a WEB page hosted by the enterprise, the user is required to provide certain information, which will typically include such as the user's ID, address, e-mail account, and so forth, and typically a new user name and password to access the account. In this process the user will be interacting with the enterprise's page from his/her browser. A Password-All plug-in is provided wherein, after entering the required information for the new enterprise, the user may activate a pre-determined signal (right click, key stroke, etc.), and the Password-All suite will then enter a new passthrough in the user's Password. All profile at the Password-All Portal server.
In a related method for new entries, the enterprise hosting the Password-All Portal may, by agreement with other enterprises, provide log-in and sign-up services at the Password-All Portal, with most action transparent to the user. For example, there may be, at the Password-All Portal, a selectable browser list of cooperating enterprises, such as banks, security services, and the like, and a user having a Password-All Portal subscription and profile may select among such cooperating enterprises and open new accounts, which will simultaneously and automatically be added to the Password-All Portal page for the user and to the server hosted by the cooperating enterprise. There may be some interactivity required for different accounts, but in the main, much information from the user's profile may be used directly without being re-entered.
The inventors have anticipated that many potential users may well be suspicious of providing passwords and user names to an enterprise hosting a Password-All Portal Server executing a service like Password-All according to embodiments of the present invention. To accommodate this problem, in preferred embodiments, it is not necessary that the user provide the cleartext password to Password. All. Instead, an encrypted version of each password is provided. When a user links to his passthrough page in Password-All at the Password-All Portal server, when he/she invokes a hyperlink, the encrypted password is returned to the user's system, which then, by virtue of the kept encryption key or master password, invokes the true and necessary password for connection to the selected destination. It is thus not necessary that cleartext passwords be stored at the Password-All Portal server, where they may be vulnerable to attack from outside sources, or to perceived misuse in other ways as well.
In a related safety measure, in a preferred embodiment of the invention, a user's complete profile is never stored on a single server, but is distributed over two or more, preferably more, servers, so any problem with any one server will minimize the overall effect for any particular user.
Password-All, as described above, allows a user to access a complete list of the user's usual cyberspace destinations, complete with necessary log-on data, stored in an encrypted fashion, so a user may simply select a destination (a hyperlink) in the Password-All list, and the user's browser then invokes the URL for the selected destination. In an added feature, Password-All may display banner ads and other types of advertisement during the navigation time between a hyperlink being invoked and the time the destination WEB page is displayed.
In yet another embodiment of the invention, a user/subscriber need not access the Password-All page to enjoy the advantages of the unique features provided. In this variation, a Plug-In is provided for the subscriber's WEB browser. If the subscriber navigates by use of the local browser to a WEB page requiring a secure log-in, such as his/her on-line banking destination, when the subscriber is presented with an input window for ID and Password, the plug in may be activated by a predetermined user input, such as a hot key or right click of the mouse device. The plug-in then accesses, transparently, the Password-All page (which may be cached at the client), and automatically accesses and provides the needed data for log-on.
In yet another aspect of the invention a search option 37 allows a user to search list 34 for specific URL's based on typed input such as keywords or the like. In some cases, the number of URL's stored in list 34 can be extensive making a search function such as function 37 an attractive option. A criteria dialog box 51 illustrated as logically separated from and below list 34 is provided and adapted to accept input for search option 37 as is known in the art. In one embodiment, search option 37 may bring up a second window wherein a dialog box such as box 51 could be located.
In another aspect of the invention the search function may also be configured in a window invoked from window 33, and caused to search all or selected ones of listed destinations, and to return results in a manner that may be, at least to some extent, configured by a user. For example, a dialog box may be presented wherein a user may enter a search criteria, and select among all of the listed destinations. The search will then be access each of the selected destinations in turn, and the result may be presented to the user as each instance of the criteria is found, or results may be listed in a manner to be accessed after the search.
Preferably the search function is a part of the Password-All Portal software, available for all users, and may be accessed by hyperlinks in user's personal pages. In some embodiments users may create highly individualized search functions that may be stored in a manner to be usable only by the user who creates such a function.
In many aspects of the present invention, knowledge of specific WEB pages, and certain types of WEB pages, is highly desirable. In many embodiments characteristics of destination WEB pages are researched by persons (facilitators) maintaining and enhancing Password-All Portal software 35, and many characteristics may be provided in configuration modules for users to accomplish specific tasks. In most cases these characteristics are invoked and incorporated transparent to the user.
In yet another aspect of the present invention, the Password-All suite is structured to provide periodic reports to a user, in a manner to be structured and timed by the user, through the user's profile. For example, reports of changes in account balances in bank accounts, stock purchases, stock values, total airline travel purchases, frequent-flier miles, and the like may be summarized and provided to the users in many different ways. Because the Password-All Portal server with the Password-All software site handles a broad variety of transactional traffic for a user, there is an opportunity to summarize and collect and process statistics in many useful ways. In preferred embodiments of the invention such reports may be furnished and implemented in a number of different ways, including being displayed on the user's secure personal WEB page on the Password-All Portal.
In addition to the ability of performing tasks as described above, task results including reports, and hard documents such as airline tickets may be sent over the Internet or other data packet-networks to user-defined destinations such as fax machines, connected computer nodes, e-mail servers, and other Internet-connected appliances. All tasks may be set-up and caused to run according to user-defined schedules while the user is doing something else or is otherwise not engaged with the scheduled task.
In another embodiment of the present invention, recognizing the increasing use of the Internet for fiscal transactions, such as purchasing goods and services, a facility is provided in a user's profile to automatically track transactions made at various destinations, and to authorize payment either on a transaction-by-transaction basis, or after a session, using access to the user's bank accounts, all of which may be pre-programmed and authorized by the user.
Other functions or options illustrated as part of application 35 include a last URL option 41, an update function 43, and an add function 45. Function 41 allows a user to immediately navigate to a last visited URL. Update function 43 provides a means of updating URL's for content and new address. An add function enables a user to add additional URL's to list 34. Similarly, function 45 may also provide a means to delete entries. Other ways to add accounts are described above. It should be noted that the services provided by the unique Password-All Portal in embodiments of the present invention, and by the Password-All software suite are not limited to destinations requiring passwords and user names. The Password-All Portal and software in many embodiments may also be used to manage all of a user's bookmarks, including editing of bookmarks and the like. In this aspect, bookmarks will typically be presented in indexed, grouped, and hierarchical ways.
There are editing features provided with Password-All for adding, acquiring, deleting, and otherwise managing bookmarks. As a convenience, in many embodiments of the invention, bookmarks may be downloaded from a user's Password-All site, and loaded onto the same user's local browser. In this manner, additions and improvements in the bookmark set for a user may be used without the necessity of going to Password-All. Further, bookmarks may be uploaded from a user's local PC to his/her home page on the Password-All site by use of one or more Password-All plug-ins.
It will be apparent to the skilled artisan, given the teaching herein, that the functionality provided in various embodiments of the invention is especially applicable to Internet-capable appliances that may be limited in input capability. For example, a set-top box in a WEB TV application may well be without a keyboard for entering IDs and Passwords and the like. In practice of the present invention keyboard entry is minimized or eliminated. The same comments apply to many other sorts of Internet appliances.
In preferred embodiments of the invention, once a subscriber-user is in Password-All, only an ability to point-and-click is needed for all navigation. To get into the Password-All site, using a limited apparatus, such as an appliance without a keyboard or keypad, a Smartcard or embedded password may be used, or some other type of authentication.
It will be apparent to one with skill in the art that an interactive application such as application 33 may be provided in a form other than a WEB page without departing from the spirit and scope of the present invention. For example, an application such as application 33 may be provided as a downloadable module or program that may be set-up and configured off-line and made operational when on-line.
At step 55, a user enters a user-name and password, which, in one embodiment, may simply be his ISP user name and password. In another embodiment, a second password or code would be required to access an Internet portal such as portal server 31 of
In step 58 a user will, minimally, select a URL from his or her bookmarked destinations, and as is known by hyperlink technology, the transparent URL will be invoked, and the user will navigate to that destination for the purpose of normal user interaction. In this action, the Password-All Portal software transparently logs the user on to the destination page, if such log-on is needed.
At step 60 the user invokes a search engine by clicking on an option such as described option 37 of
In another embodiment wherein WEB pages are cached in their presentable form, information extracted in step 64 may include any information contained in any of the stored pages such as text, pictures, interactive content, or the like. In this case, one displayed result page may provide generated links to search results that include the URL associated with the results. Perhaps by clicking on a text or graphic result, the associated WEB page will be displayed for the user with the result highlighted and in view with regards to the display window.
In another aspect of the present invention, a software agent, termed a gatherer by the inventors, is adapted to gather and return summary information about URL's according to user request or enterprise discretion. This is accomplished in embodiments of the present invention by a unique scripting and language parsing method provided by the inventor wherein human knowledge workers associated with the service provide written scripts to such a gatherer according to subscriber or enterprise directives. Such a software gatherer, and capabilities thereof, is described in enabling detail below.
Referring now to
The main purpose of portal software 35 as described above with reference to
Referring again to
It is described in the above disclosure that agent 39 may, in some embodiments, search for and return certain summary information contained on user-subscribed WEB pages, such as account summaries, order tracking information and certain other information according to user-defined parameters. This feature may be programmed by a user to work on a periodic time schedule, or on demand.
In the following disclosure, enhancements are provided to agent 39. Such enhancements, described in detail below, may be integrated into agent 39 of portal software 35 (
In this exemplary embodiment gatherer 67 is a multi-featured software application having a variety of sub-modules and interface modules incorporated therein to provide enhanced function. Gatherer 67 has a client/service interface layer 69 adapted to enable directive input from both a client (user) and a knowledge worker or workers associated with the service. A browser interface 77 is provided in layer 69, and adapted to provide access to application 67 from a browser running on a client's PC or other Internet or network appliance. Interface 77 facilitates bi-directional communication with a user's browser application (not shown) for the purpose of allowing the user to input summary requests into gatherer 67 and receive summary results. Interface 77 supports all existing network communication protocols such as may be known in the art, and may be adapted to support future protocols.
Layer 69 also comprises a unique input scripting module 79 that is adapted to allow a human knowledge worker to create and supply directive scripts containing the site logic needed by gatherer 67 to find and retrieve data from a WEB site. In this case, gatherer 67 executes and runs on a network server such as server 31 of
It is assumed in this example that gatherer 67 is part of the portal software suite 35 running on server 31 of
Interface layer 69 facilitates exchange of information from both a client and a knowledge worker. A client operating a WEB browser with an appropriate plug-in is enabled to communicate and interact with gatherer 67. For example, a user may enter a request to return a summary of pricing for all apartments renting for under $1000.00 per month located in a given area (defined by the user) from apartments.com (one of user's registered WEB sites). The just mentioned request would be categorized as either a periodic request, or a one time (on demand) request. The communicated request initiates a service action wherein a knowledge worker associated with the service uses module 79 to set-up gatherer 67 to perform it's function. Module 79 is typically executed from a network-connected PC operated by the knowledge worker.
According to an embodiment of the present invention, a unique scripting method facilitated by module 79 is provided to enable gatherer 67 to obtain the goal information requested by a user. For example, the above mentioned example of WEB-site apartments.com has a specific HTML (hyper-text-markup-language) logic that it uses to create its site and post its information. Such site logic is relatively standard fare for a majority of different sites hosted by different entities. Using this knowledge, a knowledge worker creates a site-specific script or template for gatherer 67 to follow. Such a template contains descriptions and locations of the appropriate fields used, for example, at apartments.com. Apartment description, location, deposit information, rental information, agent contact information, and other related fields are matched in terms of location and label description on the template created with module 79. Completed templates are stored in a database contained in a storage facility such as, perhaps, repository 29 of
In one embodiment, one script may contain site logics for a plurality of WEB pages, and instructions for specific navigational instruction and password or login information may be contained therein and executed serially, such as one site at a time. It is important to note that the knowledge worker or workers may perform much of their scripting via automatic controls such as by object linking and embedding (OLE) and a minor portion of scripting may be performed manually in an appropriate computer language, many of which are known in the art).
Gatherer 67 also has a process layer 71 adapted for internal information gathering and parameter configuration. An optional portal server interface 81 is provided and adapted to allow gather 67 to provide updated information to a user's list of hyperlinks and also to obtain data from portal server 31 if required. For example, required hyperlinks may be mirrored from a user's home page to a scripting template for navigational purposes. In an embodiment wherein gatherer 67 is part of a standalone service, a convention for providing user login information may be supplied at the client's end when a request is made. For example, an encrypted password may be supplied by a client plug-in and gatherer 67 may temporarily borrow the user's encryption key when auto login is performed.
An appliance configuration module 83 is provided and adapted to allow a user to define and configure an Internet appliance to communicate with the service and receive summary information. Such appliances may include but are not limited to palm top PC's, lap top PC's, cellular telephones, WEB TV's, and so on. Typically, a user will be presented a configuration WEB page from a network server that displays in his browser window on his desktop PC. The page contains an interface for communicating device parameters and communication protocol types to module 83. In this way, a user may configure a preferred device for receipt of summary information. Device parameters and communication protocols inherent to such a device are incorporated into the scripting of the site template and are used as instructions for WEB summary delivery.
A navigation layer 73 is provided and adapted to perform the function of external site navigation and data gathering for gatherer 67. To this end, a communication interface/browser control module 85 is provided and adapted to function as a WEB browser to access WEB sites containing WEB data. Control 85 receives it's instruction from the scripted template created by the knowledge worker.
A parsing engine 87 is provided and adapted to parse individual WEB sites according to a template created via scripting module 79. Parsing engine 87 may be a Pearl engine, an IE HTML engine, or any other or combination of known parsing engines. The template (not shown) tells control 85 and parsing engine 87 where to go and what fields at the destination site to look for to access desired data. Once the data fields are located, parsing engine 87 gathers current data in the appropriate field, and returns that data to the service for further processing such as data conversion, compression and storage, and the like.
Because WEB sites use tools that use consistent logic in setting up their sites, this logic may be used by the summarization service to instruct control 83 and parsing engine 87. The inventor provides herein an exemplary script logic for navigating to and garnishing data from Amazon™.com. The hyperlinks and/or actual URLs required for navigation are not shown, but may be assumed to be included in the template script. In this example, a company name Yodlee (known to the inventors) is used in the script for naming object holders and object containers, which are in this case Active X™ conventions. In another embodiment, Java™ script or another object linking control may be used. The scripted template logic example is as follows:
# Site amazon.orders.x—shows status of orders from Amazon
login(7);
get(“/exec/obidos/order-list/”);
my @tables=get_tables_containing_text(“Orders:”);
my $order_list=new Yodlee::ObjectHolder(‘orders’);
$order_list→source(‘amazon’);
$order_list→link_info(get_link_info( ));
my @href_list;
my @container_list;
foreach my $table (@tables) {
my @rows=get_table_rows( );
foreach my $i (0 . . . $#rows) {
select_row($i);
my $text=get_text($rows[$i]);
next if $text=/Orders:|Status/;
my @items=get_row_items( );
next unless @items>=4;
my($order_num, $date, $status);
select_cell(1);
$order_num=get_cell_text( );
my $href=get_url_of_first_href(get_cell( ));
select_cell(2);
$date=get_cell_text( );
select_cell(3);
$status=get_cell_text( );
next unless defined $order_num and defined $date and defined $status;
my $order=new Yodlee::Container(‘orders’);
$order→order_number($order_num);
$order→date($date);
$order→status($status);
$order_list→push_object($order);
if(defined $href) {
get($href_list[$i]);
(@tables=get_tables_containing_text(“Items Ordered:”);
foreach my $table (@tables) {
my @rows=get_table_rows( );
foreach my $j (0 . . . $#rows) {
select_row($j);
my $href=get_url_of_first_href(get_row( ));
next unless defined $href;
my @child_list=get_children(get_row( ), ‘a’);
next unless defined $child_list[0];
my $text=get_text($child_list[0]);
$container_list[$i]→description($text);
}
}
}
result($order_list);
The above example is a script that instructs control 85 and parser 87 to navigate to and obtain data from Amazon™.com, specifically that data that reflects the user's current order status. Scripts may also be written to obtain virtually any type of text information available from any site. For example, a user may wish to obtain the New York Times headlines, the top ten performing stocks, a comparative list of flights from San Francisco to New York, etc. In one embodiment, metadata may be associated with and used in-place of the actual scripted language for the purpose of reducing complication in the case of many scripts on one template.
A data processing layer 75 is provided and adapted to store, process, and present returned data to users according to enterprise rules and client direction. A database interface module 89 is provided and adapted to provide access for gatherer 67 to a mass repository such as repository 29 of
A summarization page module 91 is provided and adapted to organize and serve a WEB summary page to a user. Module 91, in some embodiments, may immediately push a WEB summary to a user, or module 91 may store such summarized pages for a user to access via a pull method, in which case a notification may be sent to the user alerting him of the summary page availability. Summarization module 91 includes an HTML renderer that is able to format data into HTML format for WEB page display. In this way, e-mail messages and the like may be presented as HTML text on a user's summarization page. Moreover, any summary data from any site may include an embedded hyperlink to that site. In this way, a user looking at an e-mail text in HTML may click on it and launch the appropriate e-mail program. Other sites will, by default, be linked through the summary page.
Many users will access their summary data through a WEB page as described above, however, this is not required in order to practice the present invention. In some embodiments, users will want their summary information formatted and delivered to one of a variety of Internet-capable appliances such as a palm top or, perhaps a cell phone. To this end, the renderer is capable of formatting and presenting the summary data into a number of formats specific to alternative devices. Examples of different known formats include, but are not limited to XML, plain text, VoxML, HDML, audio, video, and so on.
In a preferred embodiment of the present invention, gather 67 is flexible in such a way as it may act according to enterprise rules, client directives, or a combination of the two. For example, if a user makes a request for summary data about a user/subscribed WEB page to be periodically executed and presented in the form of a HTML document, then gather 67 would automatically access and analyze the required internal information and user provided information to formulate a directive. Using scripting module 79, a knowledge worker provides a template (if one is not already created for that site) that contains the “where to go” and “what to get” information according to site logic, user input, and known information.
Alternatively, if a user requests a summary about data on one of his sites such as, perhaps, current interest rates and re-finance costs at his mortgage site, the service may at it's own discretion provide an additional unsolicited summary from an alternate mortgage site for comparison. This type of summarization would be designed to enhance a user's position based on his profile information. In this case, updated data about latest interest rates, stock performances, car prices, airline ticket discounts, and so on would be stored by the service for comparative purposes. If a user request for a summary can be equaled or bettered in terms of any advantage to the user, such summary data may be included.
In many cases, created templates may be re-used unless a WEB site changes it's site logic parameters, in which case, the new logic must be accessed and any existing templates must be updated, or a new template may be created for the site. The templates contain site-specific script obtained from the site and stored by the knowledge workers. In one embodiment, companies hosting WEB pages automatically provide their site logics and any logic updates to the service by virtue of an agreement between the service and the WEB hosts.
In an alternative embodiment gatherer 67 may be implemented as a client application installed on a user's PC. In this embodiment, a user would not be required to supply log-in or password codes. Summarization scripts may be sent to the client software and templates may be automatically created with the appropriate scripts using log-in and password information encrypted and stored locally on the user's machine.
In addition to providing WEB summary information, gatherer 67 may also be used to provide such as automatic registration to new sites, and for updating old registration information to existing sites. For example, if a user whishes to subscribe, or register at a new site, only the identification of the site is required from the user as long as his pertinate information has not changed. If a new password or the like is required, gatherer 67 through control module 73 may present login or password codes from a list of alternative codes provided by a user. In another embodiment, a database (not shown) containing a wealth of password options may be accessed by gatherer 67 for the purpose of trying different passwords until one is accepted by the site. Once a password or log-in code is accepted, it may be sent to a user and stored in his password list and at the network level.
It will be apparent to one with skill in the art that a software application such as gatherer 67 may be implemented in many separate locations connected in a data network. For example, a plurality of gatherer applications may be distributed over many separate servers linked to one or more mass repositories. Client applications include but are not limited to a WEB-browser plug-in for communicating to the service. Plug-in extensions may also be afforded to proxy servers so that auto-login and data access may still be performed transparent to a user.
In another embodiment, plug-ins enabling communication with gatherer 67 may be provided and configured to run on other network devices for the purpose of enabling such a device to initiate a request and get a response without the need for a desktop computer.
In most embodiments a user operating a desktop PC will order a one time or periodic summary related to some or all of his subscribed WEB sites. A logical flow of an exemplary request/response interaction is provided below.
In step 97 a knowledge worker accesses particular site logic associated with the request URLs. For example, if the request involves a plurality of URLs, then all site logics for those URLs are accessed. Logic may be available in a repository such as repository 29 of
In step 99, the knowledge worker creates a template by virtue of scripting module 79 (
In step 101 the template is stored and associated with the requesting user. The stored template may now be retrieved at a scheduled time for performing the summary gathering. At step 103, a browser control such as module 85 of
In step 105, automatic log-in is performed, if required, to gain access to each specified URL. In step 107, a specified WEB-page is navigated to and parsed for requested data according to the logic on the template. If there are a plurality of WEB-pages to parse, then this step is repeated for the number of pages. A variety of parsing engines may be used for this process such as an IE™ parser, or a Pearl™ parser. Only the requested data is kept in step 107.
A request may be an on-demand request requiring immediate return, or a scheduled request wherein data may be posted. At step 109, such logic is confirmed. If the data is to be presented according to a periodic schedule, then summary data parsed in step 107 is stored for latter use in step 111. In step 113, the summary data is rendered as HTML if not already formatted, and displayed in the form of a summary WEB-page in step 115. The summary page may be posted for access by a user at a time convenient to the user (pull), or may be pushed as a WEB-page to the user and be made to automatically display on the user's PC. Notification of summary page availability may also be sent to a user to alert him of completion of order.
If the summary data is from a one-time on-demand request and required immediately by a user, then a network appliance and data delivery method (configured by the user) is confirmed, and the data is rendered in the appropriate format for delivery and display in step 117. In step 119, the summary data is delivered according to protocol to a user's designated appliance. In step 121 a user receives requested information in the appropriate format.
It will be apparent to one with skill in the art that there may be more or fewer logical steps as well as added sub-steps than are illustrated in this example. For example, step 105 may in other embodiments include sub-steps such as getting an encryption key from a user. In still another embodiment, part of a request may be rendered as HTML as in step 113 while certain other portions of the same request data might be rendered in another format and delivered via alternative methods. There are many possibilities.
The method and apparatus of the present invention may be used to present summaries to users without user input. Process logic such as this is detailed below.
In step 119, a database containing user information and parameters is accessed and reviewed. Certain information specific to a user may be required to initiate an enterprise-sponsored summary report. At step 121, the knowledge worker accesses the site logic specific to the specified target site or sites for summarization. In step 123, the knowledge worker modifies an existing user template, or creates a new one if necessary. At step 125 the template is stored in a repository such as repository 29 and associated with the user.
As described in
In step 131, all sites are parsed for summary data and stored in canonical fashion in step 133. At step 135, the data is compiled and rendered as HTML for presentation on a summary page. In step 137, a WEB summary containing all of the data is made available to a user and the user is notified of it's existence.
Providing certain information not requested by a user may aid in enhancing a user's organization of is current business on the WEB. Moreover, unsolicited WEB summaries may provide better opportunities than the current options in the user's profile. Of course, assisting a user in this manner will require that the enterprise (service) have access to the user's profile and existing account and service information with various WEB sites on the user's list. A user may forbid use of a user's personal information, in which case, no enterprise-initiated summaries would be performed unless they are conducted strictly in an offer mode instead of a comparative mode.
The method and apparatus also may be practiced in a language and platform independent manner, and be implemented over a variety of scalable server architectures.
In another aspect of the present invention, a method is provided largely through unique software wherein summary reports may be ordered and presented to users, the reports reflecting calculated and solution-orientated results. This type of summarizing is termed meta-summarization by the inventors, because it is a summarization over a plurality of data sources. Such a method is described in enabling detail below.
In this embodiment, a portal station 151 is provided and adapted by virtue of software and hardware, to perform WEB-summary and presentation services according to embodiments described in the co-patent applications listed above. Station 151 may be an ISP, a main Internet server, or other network connected server or interface station. In this example, portal station 151 is continuously connected to a source network, which is in this embodiment, the Internet network represented by Internet cloud 139. The above-described network connection is afforded by an Internet-connection line 149 from station 151 to an Internet backbone 147. Internet backbone 147 represents all lines and connections, including sub-nets that make up a global Internet 139.
Portal station 151 has a means provided therein for maintaining a portal interface 153. Portal interface 153 is a file-server interface in this example, however in other embodiments, differing types of network-interface hardware may be substituted therefor. Interface 153 provides hyper-text-transfer protocol (HTTP) pages over an Internet-connection such as path 161 to subscribing users operating such as an illustrated network-adapted PC 163. A user operating PC 163 may go on-line, in this case by such as a dial-up connection, and communicate with portal interface 153 over connection path 161. Connection path 161 may be a normal telephone line, an ISDN line, or another known type of Internet-connection link including wireless connection. A dial-up connection is illustrated herein only as a more common connection method.
A data repository 157 is provided within station 151 and adapted to warehouse aggregated data on behalf of and about a user. Data repository 157 may be part of the same hardware supporting portal interface 153 or it may be a separate hardware implementation connected by a data link. Repository 157 may be of the form of optical storage, or any other known implementation used for storing large amounts of digital data. Repository 157 may be assumed to support varied database programs as may be required to manipulate and organize data or metadata stored therein.
A data gathering sub-system GSS 159 is provided within station 151 and is adapted as a software and hardware implementation capable of navigating data-packet networks, such as Internet 139, upon instruction. GSS 159 represents automated browser control/navigation as described in co-pending patent application Ser. No. 09/523,598. GSS 159 is analogous to navigation layer 73 described in
A plurality of network-connected data sources represented herein by file/data servers 141-145 are illustrated in Internet 139. Servers 141-145 are user-subscribed servers known to portal station 151. For example, servers 141-145 may represent one user's collective WEB-services for banking and investment. Such options include banking, stock trading, retirement account servers, insurance servers, and so on. It is noted here that servers 141-145 are assumed to represent separate WEB-based services subscribed to by one user and are not affiliated with one another. For example, a user operating such as PC 163 would do all of his on-line banking, trading, and investing using servers 141-145 in this example.
In another embodiment, servers 141-145 may represent all of a user's frequented on-line shopping services. The fact that all of servers 141-145 are topically related but not affiliated with one another in this example serves only to aid in explanation of the present invention as will be seen below.
It is taught in the co-pending patent application entitled “Method and Apparatus for Obtaining and Presenting WEB Summaries to Users” that site navigation, parsing data, and returning data to users or storage is enabled, in part, by site-logic templates provided typically by knowledge workers. This aspect is represented herein by a PC 167 adapted for a knowledge worker (KW). A KW working from a station such as PC 167 provides site-logic scripts for navigation to data requested by a user and stored in any one of or all of servers 141-145. Such scripts are provided to GSS 159 over a data link 165. Summary data stored in such as repository 157 is stored for user access. In some cases wherein a user requests immediate data return, data is sent directly to such as portal interface 153 where a user may then access the data immediately.
According to an embodiment of the present invention, a novel database-reporting engine DBRE 155 is provided and adapted to perform formulative processes to aggregated data on behalf of a user. DBRE 155 is in itself a database utility and is in a preferred embodiment a part of the software environment of repository 157. In another embodiment DBRE 155 may be part of the software environment of portal interface 153.
In this embodiment, DBRE 155 acts as a first “gathering agent” and checks repository 157 first for user requested data upon request. User-history records of all user transactions at all of his registered WEB-based services are preferably maintained in repository 157 and are accessible to DBRE 155. In some cases, services such as those represented by servers 141-145 may provided complete transaction histories that may be obtained and stored in repository 157 and updated periodically. In some cases however, such services may not retain history records for users. In this case, a user accessing such services through his or her portal interface 153 may track each transaction over a normal course of time resulting in a history record for transactions at that service that is maintained in repository 157.
In the case of servers 141-145, each contains some form of financial portfolio data connected to one user. For example, server 141 may represent a banking service where a user has a savings account. Server 142 may represent a banking service where the user has a checking account. Server 143 may represent an on-line investment company maintaining a fast-changing portfolio of investments and losses for the particular user. Server 144 may represent a banking company where the user has an individual retirement account (IRA). Server 145 may represent a mortgage company holding data about the users property portfolios. Each site presumably holds current account-status information and a financial history of transactions performed by a particular user.
To illustrate, assume that all financial data particular to one user is provided by or obtained from servers 141-145, aggregated in data repository 157, and updated periodically. A user operating PC 163 may access portal interface 153 by way of Internet connection 161 and request a specific result that involves some or all of the data across multiple servers 141-145. One example would be a user-initiated command “calculate my current net-worth”. The resulting meta-summarized report would inform a user of his or her calculated net-worth with all financial data from all financial data-sources (servers 141-145) analyzed in the process of answering the user query.
In this case DBRE 155 utilizes only data that is already aggregated in repository 157. Therefore, it is not specifically required that GSS 159 navigate on behalf of the user in a case where data held in aggregation is current and sufficient to satisfy a user request. However, if a user's particular request, such as the one stated in the above example, requires navigation to one or more of servers 141-145, GSS 159, using site logic provided by KW 167, would navigate to each required site and retrieve the required data. After the required data is aggregated in repository 157, DBRE 155 may analyze the aggregated data and generate an accurate report from the aggregated data based on a user's request.
It will be apparent to one with skill in the art that providing a unique engine such as DBRE 155 on a user-side of repository 157 saves precious bandwidth resource required by individual site navigation and return of data ordered by a user. Added storage space is required in repository 157 for the purpose of storing complete activity histories from multiple WEB services on behalf of users. However, adding such resource and saving bandwidth represents an intelligent implementation in light of the many techniques known in the art for compressing and archiving data. More detail about the function of DBRE 155 is presented below.
Options database 173 may be part of DBRE 155 as illustrated herein, or part of repository 157 and made accessible to DBRE 155. In the case of DBRE 155 maintaining its own databases such as options database 173, and a previously described database containing user histories across multiple accounts, then DBRE 155 would be resident in a machine having enough storage memory to hold all required data. Such a machine could be a processor/server. In another embodiment, all stored data is held in repository 157.
DBRE 155 also has a runtime engine 177, which performs data analyzing and calculation in order to form specific data results or solutions for users based on user request. Engine 177 has access to all of the mathematical tools and system knowledge required to perform its objectives which can vary considerably. A knowledge base (not shown) may be used as a source of intelligence for engine 177 as is generally known in the art of configuration models.
Engine 177 performs a wide variety of mathematical functions including such as statistical analysis, summing, averaging, and so on. In one embodiment, algebraic, geometric, and trigonometric functions are also provided for performing more complex calculations. In most cases however, user requests will be geared more toward averaging, summing, predicting probabilities, deriving percentages, and so on. For example, summing multiple bank balances would be a common task. Analyzing on-line spending trends across multiple on-line shopping services would be another example of a common task. A more complicated report might compare shopping trends with income potential and produce a ratio figure along with recommended ways to improve on the ratio without sacrificing needed goods. There are many possibilities.
A graphics user interface (GUI) module 181 is provided within DBRE 155 and adapted to prepare data according to requested format and a requesting display type. GUI module 181 has knowledge of which presentation option was selected from options database 173, and knowledge of the parameters (hardware and software platform) of a particular device or station that will receive a report. It is not required that a report be directed back to an originating device. In some embodiments, a user may direct a meta-summary report to alternative receiving devices over different mediums. This assumes, of course, that the receiving devices and data networks are known to the system.
In practice of the present invention, a user initiates a request illustrated herein as an arrow labeled input to a pre-configured request 169 from such as his or her browser interface. Request 169 is parsed for meaning in control-logic module 171. If there is an error detected in the original request 169, such as missing information or an option selection that is not available, then an error report is immediately sent back to that user as illustrated by the arrow labeled error report. Control-logic module 171 may check options database 173 to determine if an unavailable option was selected and present an alternative available option back with the error report.
Once module 171 has confirmed a request and confirmed a presentation option, it accesses a guard (GI) 175 resident on the client side of such as repository 157 of
All of the data required to return a requested report is funneled into runtime engine 177. All of the appropriate calculations are performed and the resulting data illustrated herein as raw data-results 177 is passed into GUI module 181. GUI module 181 then prepares the result data for presentation to a user illustrated herein as an arrow labeled output.
As described above, a report may be very simple or quite complex, including text and graphical elements as well. In one embodiment, all of the process steps performed on included data may be broken down and reported to a user along with a final result. Presentation options may include spreadsheets, graphs, text reports, pie charts, and so on.
In the example presented above, DBRE 155 is a multi-functional module that may be broken down into cooperating sub-modules. However, this is not required to practice the present invention. One with skill in the art will recognize that there are other orders of modules and distribution paths that may be utilized to accomplish the same function. For example, DBRE 155 (
At step 185, control logic registers and confirms feasibility of the original request. This step includes parsing the request, confirming a presentation option, confirming presentation delivery parameters (software, hardware, medium) and so on. Once a request is approved for action, a data gatherer at step 187 accesses the database, such as in repository 157 (
At step 189 it is determined whether or not there is sufficient data available in aggregation to complete the request. If the decision is yes, then the required data is extracted from the database (DB) in step 191. At step 193 the extracted data is processed according to tools that accomplish the user's request, which is a solution-orientated result. Text records of processing may also be forwarded to a user if requested. In this way a user might review several steps taken to arrive at a solution-oriented result.
At step 193, the raw result data is prepared according to user-requested presentation options in such as GUI module 181 of
If in step 189 it is determined that there is not enough data or the right kind of data already in aggregation to complete a request, then the request is passed over to a GSS, such as GSS 159 of
At step 203, a GSS such as GSS 159 of
It will be apparent to one with skill in the art that the process steps described above represent a mostly automated or completely automated process. Moreover, there may be other sub-routines added without departing from the spirit and scope of the present invention such as adding a user notification step in the event that in step 189, data is insufficient.
It will also be apparent to one with skill in the art that a process routine such as the one described herein may be altered according to an alternate operating environment without departing from the spirit and scope of the present invention. For example, if a user is interfacing from a wireless device through such as a data center network interface, then added steps may be required to convert data to a format understood on a different network. There are many diverse applications.
Summary report 209 consists of individual bank, investment and account listings complete with the names of the institutions. Summaries of the individually reported information for both bank accounts and stock accounts are found beneath each group listing. Report 209 is a rather simplified example of many graphical possibilities and presentation methods. Depending on the complexity of a request, a meta-summarized report may contain virtually any type of presentation mediums. Some examples include, but the invention is not limited to limited to, Gant charts, time graphs, pie charts, flow charts, text summaries, and so on. In another embodiment, a summarized report may contain interactive options for looking at the same data in different ways, or even calculating further results from the results presented. A user has many options when accomplishing interface with the system of the present invention through a fully functional browser application installed on a powerful PC. Interface through other devices such as personal digital assistant's, cellular telephones, and the like will obviously limit presentation options, however, the use of such devices for interface is possible and may, in some situations, be preferred. Such situations may be business meetings, interviews, and other situations wherein a user may need to access some summary data, but does not have access to his personal computer station. Moreover, such data may be previously ordered and sent to a place other than at his or her personal computer. With appropriate interface to telephony networks, such information may, if directed by a user, be faxed to a meeting place, e-mailed to an associate's e-mail address, and so on. There are many diverse applications, many of which have already been stated.
Multiple Point-of-Access Summary Interface
According to a preferred embodiment of the present invention, an interactive software interface suite is provided and packaged to enable multi-point access to deeper levels of summary data as well as transaction and direct account access capabilities.
Referring now to
Referring now to
In this example, interface 211 is made up of 9 sub-modules each module providing a different class of functionality. An Account Alerts module 213 is provided within interface 211 and adapted to display various types of user-configured alerts that may be applied to a wide range of user account types. A Net Worth module 215 is provided within interface 211 and adapted to report a user's net worth information as determined through calculation related to data associated with all of the user's financially related accounts, assets, and financial activities. Module 215 is illustrated in this example as presenting dynamic graphics in the form of pie charts describing a user's current assets and liabilities.
A bill Payment module 217 is provided within interface 211 and adapted for user configuration to report parameters related to bill payment. A Calendar module 219 is provided with interface 211 and adapted to hold all of a user's pending data-sensitive information. A Transaction Center module 221 is provided within interface 211 and adapted to list and summarize all of a user's online and manually input transactions. A Communications module 223 is provided within interface 211 and adapted to report parameters associated with a user's online communications applications.
An Account Bookmarks module 225 is provided within interface 211 and adapted to list all of a user's Web services in the form of hyperlinks, which are enhanced with automatic login functionality (known to inventor). A Portfolio Tracker module 227 is provided within interface 211 and adapted to follow and report parameters related to the user's favorite stocks and other investment vehicles. A Travel Planning module 229 is provided within interface 211 and adapted to enable a user to initiate, create, and manage travel itineraries including all parameters related to ticket purchase, hotel accommodations, car rentals, and other related tasks.
All of sub-modules 213-229 are interactive in the sense that a user invokes each module in order to obtain more detailed information regarding the types and classes of dynamic data handled by the invoked module. Therefore, data visible on the “face” of each module represents initial summarized updates that are exploitable for further details.
In one embodiment, further interactive enhancement is included in sub-modules 213-229 that list service providers maintaining accounts for users. From within these modules, the actual login service pages of those entities are accessible through provision of the appropriate hyperlinks to those pages. In addition to providing direct access to a user's service-providing entities through modules 213-229, hyperlinks to one or more configuration utilities associated with one or more modules servicing a particular class or type of data may also be provided. Another enhancement provided by interface 211 is that various sub-modules exemplified herein are interlinked with each other through database reporting engine 155 of
Referring now back to
Referring now back to
Net Worth module 215 uses the calculative and logic functions provided by database reporting engine 155 of
Bill Payment module 217 informs a user, in this example, that he or she currently has 8 bills due within the next 15 days. By clicking on the provided navigation arrow, a more detailed account listing each bill by entity and account number and due date may be presented in a secondary interface associated with module 217. In this aspect, it is noted that the payment module 217 is interlinked with Calendar module 219 and may share overlapping data.
Calendar module 219 provides first, a summary of items to occur on the day accessed and items related to calendar events within the current running week. By clicking on the navigation arrow provided, a secondary interface is served containing a more detailed calendar display. More detail about Calendar module 219 will be provided later in this specification.
Transaction Center module 221 informs a user of new transactions occurring since the last time of access. In this case there are twelve new transactions noted. A maximum activity item is displayed on the face of Transaction Center module 221 and related to a particular account, in this case, a MasterCard™ account that has seen the most transaction activity during a pre-configured timeframe, or since the last time of access. Also shown on the face of Transaction Center module 221, is a section listing last transactions. In this action, there are two transactions listed. A debit transaction is listed including an account provider and account number, the amount of the transaction, and the date of the transaction. A credit transaction is listed that includes the same account, amount, and date parameters of the debit transaction. By clicking on the navigation arrow provided on the face of Transaction Center module 221, a user may navigate to a secondary interface providing additional detail. More detail about Transaction Center module 221 will be provided later in this specification.
Communications module 223 alerts a user, in this case, of a quantity of new e-mails. In this case, there are fifteen new e-mails listed. In one embodiment the fifteen e-mails listed may be generic to one e-mail account.
In another embodiment, the fifteen e-mails listed may source from various accounts. By clicking on the navigation arrow on Communications module 223, a secondary interface will appear containing listed accounts. By clicking on one of the accounts listed, a user may invoke that particular e-mail interface and receive any associated e-mails through that interface. If only one e-mail account is configured to Communications module 223, then clicking on the navigation arrow will simply bring up that account software.
Account Bookmarks module 225 provides a list of URLs to a user's registered accounts along with a date listing the last time each account was accessed. By clicking on the navigation arrow provided on the face of Account Bookmarks module 225, a user may invoke the secondary interface containing a more detailed rendering of account data.
Portfolio Tracker module 227 provides a summary view of the latest activity regarding a user's chosen stock symbols. Module 227 also provides a current summary regarding the top five stocks, in this example, contained in a user's stock portfolio. By clicking on the navigation arrow provided on the face of Tracker module 227, a user may invoke the secondary interface rendering much more detail. Similarly, clicking on any of the listed stock symbols may invoke the secondary interface dedicated to that particular symbol, the interface containing much more information.
Travel Planner module 229 provides a tool for a user to invoke when it is desired to create travel plans. By clicking on the navigation arrow provided on the face of the interface, a user may invoke a secondary interface containing a configuration utility for ordering and submitting tasks related to purchasing airline tickets, booking a hotel room, arranging a car rental, and any other travel related tasks. It is noted herein, that secondary interfaces associated with the above-described modules are, in many embodiments, utilities wherein a user may create and submit requests for task performance related to the class of data covered by a particular module. In a preferred embodiment, such utility tools enable proxy performance of online tasks. Still, hyperlinks to actual web sites may also be provided such that a user may navigate to and manually perform a task at the actual site invoked.
It will be apparent to one with skill in the art that interface 211 and associated modules 213-229 may be provided of a different look and feel as well as of differing content and data classification without departing from the spirit and scope of the present invention. The unique capability loaded into interface 211 of enabling performance of various proxy tasks, integrating solution-oriented data between more than one module of interface 211, and providing site-access to associated sites through multiple points of entry represents a level of novelty not known in current-art or prior-art interfaces. Furthermore, the unique proxy capabilities performed by the data compilation, aggregation, and summary system, known to the inventor, are fully accessible through interface 211 providing a level of user-friendliness heretofore not known in the art.
A resolution toolbar 235 is provided within interface 231 and adapted to enable a user to view various calendar resolutions of day, week, month, and year. In this example, interface 231 is displaying data associated with a particular calendar week (Jul. 18-24, 2000) as indicated.
A time-sensitive calendar bookmark window 237 is provided within interface 231 and adapted to show the current day of the current month of the current year. An interactive ad button 239 is provided within interface 231 and adapted to enable a user to enter a new calendar item such as an appointment, task, or other pending item. By invoking ad button 239, an interactive utility (not shown) for making calendar additions appears. Such utility contains all of the required fields and dialog options necessary for making correct calendar additions for later display within interface 231.
A show-item option window 241 is provided within interface 231 and adapted to enable a user to select specific categories of calendar entries to view within interface 231. In this example, the categories auctions, shopping, travel, bills, banking, credit cards, and investments are listed within window 241. The only category not selected for view is the category of banking. Therefore, existing calendar entries for the remaining categories, which are selected, appear as visible within interface 231. It is noted herein that calendar items pertaining to all selected categories within window 241 are restricted to items pending within the week of Jul. 18-24, 2000 has ordered by the options selected in resolution toolbar 235.
A summary view section 233 is provided within interface 231 and details actual pending calendar items existing within the time frame of Jul. 18-24, 2000 as ordered by window 241 and toolbar 235. In this example, the summary view lists the time and day of each pending item along with a summary description of each item. It is noted herein that titles of entities associated to each pending item listed in section 233 are interactive in that by clicking on them, further detail about the pending item is displayed.
Calendar interface 231, in a preferred embodiment, is cross-linked with other modules such that data incorporated therein may be affected by actions performed in other modules. For example, if a user pays a bill through the payment module 217 of
It is noted herein that interface 243 is provided in the form of an HTML interface. In this example, all of the described interfaces are displayed as HTML interfaces. However, this is not specifically required in order to practice the present invention. Interface 211 of
Referring now back to
A scroll-down menu 247 is provided within secondary interface 243 and adapted to list all of the user's registered accounts in an interactive fashion such that selecting one of the items contained in menu 247 invokes a transaction history report exemplified herein by a history window 249. Therefore, in this example there are five transactions associated with the selected account (Chase™ Visa™ Credit). In this example, the five detailed account transactions listed in window 249 by the five new transactions reported for the same account in window 245. It will be apparent to one with skill in the art that there may be more registered accounts listed in menu 247 than are shown in summary window 245 without departing from the spirit and scope of the present invention. In this example, window 249 simply details new transactions reported in window 245.
The above-described detail of the new transactions listed in window 249 includes date, description, amount of transaction, and category. A user using a scroll-down category menu containing a list of category options may assign category detail associated with any transaction. In this way, transactions may be uniformly categorized for tax and other organizational purposes. Action items are also reported within history window 249 such as for deleting a transaction and for notification that an e-mail regarding a specific transaction was sent to a certified-public-accountant (CPA) for tax or other accounting purposes.
Other interactive options provided within secondary interface 243 include a manual delete option for manually deleting a transaction, and an archive access option for accessing archived transaction lists. Still another options include CPA-notification option 251, a view-history option 253, and a bill-payment option 255. Bill payment option 255 interlinks with bill-payment module 217 of
It will be apparent to one with skill in the art that interface 243 may be provided of a different look, feel and function than that which is illustrated herein without departing from the spirit and scope of the present invention. For example, Summary window 245 may be adapted simply to provide a pre-configured amount of latest transactions without regard to system update or user access. Similarly, Summary window 245 may list all of a user's registered accounts and quantities of latest transactions instead of just those having new transactions discovered since a last update. Moreover, transactional histories may be organized and accessible according to account, transaction category, and the like.
Net Worth interface 257 is a unique reporting vehicle that is able to provide a user with up-to-date renditions of that user's current net worth. Such a tool enables a user to modify his or her transactional behavior so as to benefit his or her total Net Worth. An interactive History button 265 is provided within interface 257 and adapted to enable a user to view net worth history over a span of time. Such a history report may be presented in the form of a graph indicating value on one axis and time on the other axis.
An interactive Financial Advice button 267 is provided within interface 257 and adapted to enable a user to obtain financial advice in the form of system recommendations and/or advice from a live financial consultant having access to the user's portfolio and transactional data. An interactive Transfer Funds button 269 is provided within interface 257 and adapted as a utility in enabling the user to engage in funds transfer activity associated with registered accounts. It is noted herein that funds transfer activities initiated from invocation of button 269 are assumed to be tasks that are performed by proxy. Although it is not illustrated in this example, invocation of Transfer Funds button 269 provides an additional interface (not shown) that will contain all of the necessary dialogue fields for facilitating transfer of monies from one account to another. In one embodiment of the present invention invocation of Transfer Funds button 269 provides a list of accounts in the form of URLs. By clicking on these, a user may access those sites and perform manual transfer activities if so desired.
In one embodiment of the present invention, Net Worth module 215 of
An individual-holdings window 275 is provided within interface 271 and adapted to enable a user to view individual stock or investment holdings and also to navigate to actual sites maintaining the accounts as illustrated by the plurality of go buttons representing URLs. An options window 279 is provided within interface 271 and adapted to enable a user to choose only the data that he or she desires to track and view.
It will be apparent to one with skill in the art that interface 211 as illustrated and described in this specification provides all of the mechanisms for ordering, viewing, and manipulating all aspects of online, and some cases off-line user data through a single user interface accessible from an Internet-capable appliance. Data accessible through interface 211 is, in one embodiment, updated each time a user of the interface logs in. In another embodiment, data accessible through interface 211 is updated, in addition, by request termed a refresh action in the art. In still other embodiments, portions of the data accessible through interface 211 are updated by demand while other portions may be updated periodically. Still other portions of data accessible through interface 211 are continually updated in real-time. There are many possibilities.
It will also be apparent to one with skill in the art that interface 211 and functional modules provided therein or accessed thereby may be interfaced to a database reporting engine such as engine 155 of
The method and apparatus of the present invention may be practiced via private individuals on the Internet, businesses operating on a WAN connected to the Internet, businesses operating via private WAN, and so on. There are many customizable situations. The present invention as taught herein and above should be afforded the broadest of scope. The spirit and scope of the present invention is limited only by the claims that follow.
The present invention is a continuation in part (CIP) to patent application Ser. No. 09/425,626 entitled “Method and Apparatus for Providing Calculated and Solution-Oriented Personalized Summary-Reports to a User through a Single User-Interface” filed on Oct. 22, 1999 now U.S. Pat. No. 6,802,042, which is a CIP to a patent application Ser. No. 09/323,598 entitled “Method and Apparatus for Obtaining and Presenting WEB Summaries to Users” filed on Jun. 1, 1999 now U.S. Pat. No. 6,199,077, which is a CIP to patent application Ser. No. 09/208,740 entitled “Method and Apparatus for Providing and Maintaining a User-Interactive Portal System Accessible via Internet or other Switched-Packet-Network” filed on Dec. 8, 1998, disclosures of which are incorporated herein in their entirety by inclusion and reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4727243 | Savar | Feb 1988 | A |
| 4987538 | Johnson et al. | Jan 1991 | A |
| 5220501 | Lawlor et al. | Jun 1993 | A |
| 5237499 | Garback | Aug 1993 | A |
| 5318007 | Afshar | Jun 1994 | A |
| 5340537 | Barrett | Aug 1994 | A |
| 5347632 | Filepp et al. | Sep 1994 | A |
| 5423033 | Yuen | Jun 1995 | A |
| 5446891 | Kaplan et al. | Aug 1995 | A |
| 5459306 | Stein et al. | Oct 1995 | A |
| 5481672 | Okuno et al. | Jan 1996 | A |
| 5483445 | Pickering | Jan 1996 | A |
| 5537314 | Kanter | Jul 1996 | A |
| 5590196 | Moreau | Dec 1996 | A |
| 5611048 | Jacobs et al. | Mar 1997 | A |
| 5613012 | Hoffman et al. | Mar 1997 | A |
| 5619648 | Canale et al. | Apr 1997 | A |
| 5619716 | Nonaka et al. | Apr 1997 | A |
| 5634127 | Cloud et al. | May 1997 | A |
| 5640577 | Scharmer | Jun 1997 | A |
| 5644576 | Bauchot et al. | Jul 1997 | A |
| 5649118 | Carlisle et al. | Jul 1997 | A |
| 5649186 | Ferguson | Jul 1997 | A |
| 5655089 | Bucci | Aug 1997 | A |
| 5696965 | Dedrick | Dec 1997 | A |
| 5699528 | Hogan | Dec 1997 | A |
| 5701451 | Rogers et al. | Dec 1997 | A |
| 5706442 | Anderson et al. | Jan 1998 | A |
| 5708825 | Sotomayor | Jan 1998 | A |
| 5710887 | Chellish et al. | Jan 1998 | A |
| 5710918 | Lagarde et al. | Jan 1998 | A |
| 5712979 | Graber et al. | Jan 1998 | A |
| 5717923 | Dedrick | Feb 1998 | A |
| 5721908 | Lagarde et al. | Feb 1998 | A |
| 5724567 | Rose et al. | Mar 1998 | A |
| 5724595 | Gentner | Mar 1998 | A |
| 5727156 | Herr-Hoyman et al. | Mar 1998 | A |
| 5732074 | Spaur et al. | Mar 1998 | A |
| 5740365 | Pfeiffer et al. | Apr 1998 | A |
| 5740549 | Reilly et al. | Apr 1998 | A |
| 5745754 | Lagarde et al. | Apr 1998 | A |
| 5745884 | Carnegie et al. | Apr 1998 | A |
| 5752246 | Rogers et al. | May 1998 | A |
| 5758577 | Kleewin et al. | Jun 1998 | A |
| 5768521 | Dedrick | Jun 1998 | A |
| 5778367 | Wesinger, Jr. et al. | Jul 1998 | A |
| 5778368 | Hogan et al. | Jul 1998 | A |
| 5787425 | Bigus | Jul 1998 | A |
| 5790789 | Suarez | Aug 1998 | A |
| 5790793 | Higley | Aug 1998 | A |
| 5793964 | Rogers et al. | Aug 1998 | A |
| 5793966 | Amstein et al. | Aug 1998 | A |
| 5794233 | Rubinstein | Aug 1998 | A |
| 5796945 | Tarabella | Aug 1998 | A |
| 5799151 | Hoffer | Aug 1998 | A |
| 5805719 | Pare, Jr. et al. | Sep 1998 | A |
| 5812769 | Graber et al. | Sep 1998 | A |
| 5813007 | Nielsen | Sep 1998 | A |
| 5815665 | Teper et al. | Sep 1998 | A |
| 5818935 | Maa | Oct 1998 | A |
| 5819284 | Farber et al. | Oct 1998 | A |
| 5825884 | Zdepski et al. | Oct 1998 | A |
| 5828839 | Moncreiff | Oct 1998 | A |
| 5832474 | Lopresti et al. | Nov 1998 | A |
| 5832494 | Egger et al. | Nov 1998 | A |
| 5835724 | Smith | Nov 1998 | A |
| 5838910 | Domenikos et al. | Nov 1998 | A |
| 5838916 | Domenikos et al. | Nov 1998 | A |
| 5838918 | Prager et al. | Nov 1998 | A |
| 5842185 | Chancey et al. | Nov 1998 | A |
| 5845073 | Carlin et al. | Dec 1998 | A |
| 5848396 | Gerace | Dec 1998 | A |
| 5854897 | Radziewicz et al. | Dec 1998 | A |
| 5855015 | Shoham | Dec 1998 | A |
| 5855020 | Kirsch | Dec 1998 | A |
| 5860068 | Cook | Jan 1999 | A |
| 5860073 | Ferrel et al. | Jan 1999 | A |
| 5862325 | Reed et al. | Jan 1999 | A |
| 5870546 | Kirsch | Feb 1999 | A |
| 5870552 | Dozier et al. | Feb 1999 | A |
| 5875296 | Shi et al. | Feb 1999 | A |
| 5875437 | Atkins | Feb 1999 | A |
| 5878215 | Kling et al. | Mar 1999 | A |
| 5878219 | Vance, Jr. et al. | Mar 1999 | A |
| 5878408 | Van Huben et al. | Mar 1999 | A |
| 5884033 | Duvall et al. | Mar 1999 | A |
| 5884035 | Butman et al. | Mar 1999 | A |
| 5884045 | Kurihara | Mar 1999 | A |
| 5887133 | Brown et al. | Mar 1999 | A |
| 5890140 | Clark et al. | Mar 1999 | A |
| 5890152 | Rapaport et al. | Mar 1999 | A |
| 5892900 | Ginter et al. | Apr 1999 | A |
| 5892909 | Grasso et al. | Apr 1999 | A |
| 5893075 | Plainfield et al. | Apr 1999 | A |
| 5893091 | Hunt et al. | Apr 1999 | A |
| 5893128 | Nauckhoff | Apr 1999 | A |
| 5894554 | Lowery et al. | Apr 1999 | A |
| 5895468 | Whitmyer, Jr. | Apr 1999 | A |
| 5895838 | Harjunmaa et al. | Apr 1999 | A |
| 5897620 | Walker et al. | Apr 1999 | A |
| 5897622 | Blinn et al. | Apr 1999 | A |
| 5898836 | Freivald et al. | Apr 1999 | A |
| 5901287 | Bull et al. | May 1999 | A |
| 5903881 | Schrader et al. | May 1999 | A |
| 5905736 | Ronen et al. | May 1999 | A |
| 5905865 | Palmer et al. | May 1999 | A |
| 5907837 | Ferrel et al. | May 1999 | A |
| 5907838 | Miyasaka et al. | May 1999 | A |
| 5908469 | Botz et al. | Jun 1999 | A |
| 5913202 | Motoyama | Jun 1999 | A |
| 5918019 | Valencia | Jun 1999 | A |
| 5918214 | Perkowski | Jun 1999 | A |
| 5920848 | Schutzer et al. | Jul 1999 | A |
| 5923736 | Shachar | Jul 1999 | A |
| 5924090 | Krellenstein | Jul 1999 | A |
| 5926798 | Carter | Jul 1999 | A |
| 5930777 | Barber | Jul 1999 | A |
| 5931907 | Davies et al. | Aug 1999 | A |
| 5931947 | Burns et al. | Aug 1999 | A |
| 5933604 | Inakoshi | Aug 1999 | A |
| 5933811 | Angles et al. | Aug 1999 | A |
| 5933816 | Zeanah et al. | Aug 1999 | A |
| 5937168 | Anderson et al. | Aug 1999 | A |
| 5937392 | Alberts | Aug 1999 | A |
| 5943424 | Berger et al. | Aug 1999 | A |
| 5948040 | DeLorme et al. | Sep 1999 | A |
| 5949326 | Wicks et al. | Sep 1999 | A |
| 5951637 | Kuzma | Sep 1999 | A |
| 5951642 | Onoe et al. | Sep 1999 | A |
| 5956709 | Xue | Sep 1999 | A |
| 5958008 | Pogrebisky et al. | Sep 1999 | A |
| 5961593 | Gabber et al. | Oct 1999 | A |
| 5961601 | Iyengar | Oct 1999 | A |
| 5963915 | Kirsch | Oct 1999 | A |
| 5963924 | Williams et al. | Oct 1999 | A |
| 5963925 | Kolling et al. | Oct 1999 | A |
| 5963949 | Gupta et al. | Oct 1999 | A |
| 5963952 | Smith | Oct 1999 | A |
| 5963964 | Nielsen | Oct 1999 | A |
| 5963967 | Umen et al. | Oct 1999 | A |
| 5966441 | Calamera | Oct 1999 | A |
| 5966697 | Fergerson et al. | Oct 1999 | A |
| 5974406 | Bisdikian et al. | Oct 1999 | A |
| 5974430 | Mutschler et al. | Oct 1999 | A |
| 5978766 | Luciw | Nov 1999 | A |
| 5978779 | Stein et al. | Nov 1999 | A |
| 5978780 | Watson | Nov 1999 | A |
| 5978828 | Greer et al. | Nov 1999 | A |
| 5978842 | Noble et al. | Nov 1999 | A |
| 5982891 | Ginter et al. | Nov 1999 | A |
| 5983170 | Goodman | Nov 1999 | A |
| 5983200 | Slotznick | Nov 1999 | A |
| 5983214 | Lang et al. | Nov 1999 | A |
| 5983227 | Nazem et al. | Nov 1999 | A |
| 5983268 | Freivald et al. | Nov 1999 | A |
| 5987440 | O'Neil et al. | Nov 1999 | A |
| 5987454 | Hobbs | Nov 1999 | A |
| 5987466 | Greer et al. | Nov 1999 | A |
| 5987498 | Athing et al. | Nov 1999 | A |
| 5987611 | Freund | Nov 1999 | A |
| 5990887 | Redpath et al. | Nov 1999 | A |
| 5991735 | Gerace | Nov 1999 | A |
| 5991756 | Wu | Nov 1999 | A |
| 5995756 | Hermann | Nov 1999 | A |
| 5995943 | Bull et al. | Nov 1999 | A |
| 5995965 | Experton | Nov 1999 | A |
| 5996010 | Leong et al. | Nov 1999 | A |
| 5999179 | Kekic et al. | Dec 1999 | A |
| 5999940 | Ranger | Dec 1999 | A |
| 5999975 | Kittaka et al. | Dec 1999 | A |
| 6000033 | Kelly et al. | Dec 1999 | A |
| 6000832 | Franklin et al. | Dec 1999 | A |
| 6003077 | Bawden et al. | Dec 1999 | A |
| 6006227 | Freeman et al. | Dec 1999 | A |
| 6006333 | Nielsen | Dec 1999 | A |
| 6009408 | Buchanan | Dec 1999 | A |
| 6009429 | Greer et al. | Dec 1999 | A |
| 6012087 | Freivald et al. | Jan 2000 | A |
| 6014429 | LaPorta et al. | Jan 2000 | A |
| 6014502 | Moraes | Jan 2000 | A |
| 6018724 | Arent | Jan 2000 | A |
| 6023684 | Pearson | Feb 2000 | A |
| 6023698 | Lavey | Feb 2000 | A |
| 6029175 | Chow et al. | Feb 2000 | A |
| 6029180 | Murata et al. | Feb 2000 | A |
| 6029182 | Nehab et al. | Feb 2000 | A |
| 6029195 | Herz | Feb 2000 | A |
| 6029207 | Heninger | Feb 2000 | A |
| 6031354 | Wiley et al. | Feb 2000 | A |
| 6032162 | Burke | Feb 2000 | A |
| 6038601 | Lambert et al. | Mar 2000 | A |
| 6038603 | Joseph | Mar 2000 | A |
| 6038668 | Chipman et al. | Mar 2000 | A |
| 6041307 | Ahuja et al. | Mar 2000 | A |
| 6041326 | Amro et al. | Mar 2000 | A |
| 6044372 | Rothfus et al. | Mar 2000 | A |
| 6044465 | Dutcher et al. | Mar 2000 | A |
| 6055236 | Nessett et al. | Apr 2000 | A |
| 6055570 | Nielsen | Apr 2000 | A |
| 6058250 | Harwood et al. | May 2000 | A |
| 6058417 | Hess et al. | May 2000 | A |
| 6061700 | Brobst et al. | May 2000 | A |
| 6061716 | Moncreiff | May 2000 | A |
| 6064985 | Anderson | May 2000 | A |
| 6065120 | Laursen et al. | May 2000 | A |
| 6070150 | Remington et al. | May 2000 | A |
| 6073173 | Bittinger et al. | Jun 2000 | A |
| 6078907 | Lamm | Jun 2000 | A |
| 6078924 | Ainsbury et al. | Jun 2000 | A |
| 6078929 | Rao | Jun 2000 | A |
| 6081830 | Schindler | Jun 2000 | A |
| 6084585 | Kraft et al. | Jul 2000 | A |
| 6085186 | Christianson et al. | Jul 2000 | A |
| 6085188 | Bachmann et al. | Jul 2000 | A |
| 6085229 | Newman et al. | Jul 2000 | A |
| 6085238 | Yuasa et al. | Jul 2000 | A |
| 6088700 | Larsen et al. | Jul 2000 | A |
| 6088711 | Fein et al. | Jul 2000 | A |
| 6088722 | Herz et al. | Jul 2000 | A |
| 6101500 | Lau | Aug 2000 | A |
| 6108686 | Williams, Jr. | Aug 2000 | A |
| 6108691 | Lee et al. | Aug 2000 | A |
| 6112212 | Heitler | Aug 2000 | A |
| 6119079 | Wang et al. | Sep 2000 | A |
| 6119098 | Guyot et al. | Sep 2000 | A |
| 6119101 | Peckover | Sep 2000 | A |
| 6119229 | Martinez et al. | Sep 2000 | A |
| 6122673 | Basak et al. | Sep 2000 | A |
| 6125186 | Saito et al. | Sep 2000 | A |
| 6125352 | Franklin et al. | Sep 2000 | A |
| 6128602 | Northington et al. | Oct 2000 | A |
| 6128603 | Dent et al. | Oct 2000 | A |
| 6128624 | Papierniak et al. | Oct 2000 | A |
| 6128655 | Fields et al. | Oct 2000 | A |
| 6131115 | Anderson et al. | Oct 2000 | A |
| 6134532 | Lazarus et al. | Oct 2000 | A |
| 6134534 | Walker et al. | Oct 2000 | A |
| 6134548 | Gottsman et al. | Oct 2000 | A |
| 6134658 | Multerer et al. | Oct 2000 | A |
| 6138155 | Davis et al. | Oct 2000 | A |
| 6138158 | Boyle | Oct 2000 | A |
| 6141333 | Chavez, Jr. | Oct 2000 | A |
| 6141651 | Riley et al. | Oct 2000 | A |
| 6147975 | Bowman-Amuah | Nov 2000 | A |
| 6148402 | Campbell | Nov 2000 | A |
| 6157924 | Austin | Dec 2000 | A |
| 6167448 | Hemphill et al. | Dec 2000 | A |
| 6169992 | Beall et al. | Jan 2001 | B1 |
| 6172677 | Stautner et al. | Jan 2001 | B1 |
| 6175864 | Addison et al. | Jan 2001 | B1 |
| 6181786 | Detampel et al. | Jan 2001 | B1 |
| 6182085 | Eichstaedt | Jan 2001 | B1 |
| 6182142 | Win | Jan 2001 | B1 |
| 6182229 | Nielsen | Jan 2001 | B1 |
| 6185601 | Wolff | Feb 2001 | B1 |
| 6192380 | Light et al. | Feb 2001 | B1 |
| 6192407 | Smith et al. | Feb 2001 | B1 |
| 6195651 | Handel et al. | Feb 2001 | B1 |
| 6199077 | Inala et al. | Mar 2001 | B1 |
| 6199079 | Gupta et al. | Mar 2001 | B1 |
| 6199082 | Ferrel et al. | Mar 2001 | B1 |
| 6199099 | Gershman et al. | Mar 2001 | B1 |
| 6199113 | Alegre et al. | Mar 2001 | B1 |
| 6202062 | Cameron et al. | Mar 2001 | B1 |
| 6202210 | Ludtke | Mar 2001 | B1 |
| 6205433 | Boesch | Mar 2001 | B1 |
| 6205456 | Nakao | Mar 2001 | B1 |
| 6205473 | Thomasson et al. | Mar 2001 | B1 |
| 6208975 | Bull et al. | Mar 2001 | B1 |
| 6212548 | DeSimone et al. | Apr 2001 | B1 |
| 6219705 | Steinberger et al. | Apr 2001 | B1 |
| 6223292 | Dean et al. | Apr 2001 | B1 |
| 6226648 | Appleman et al. | May 2001 | B1 |
| 6226750 | Trieger | May 2001 | B1 |
| 6233592 | Schnelle et al. | May 2001 | B1 |
| 6233608 | Laursen et al. | May 2001 | B1 |
| 6236991 | Frauenhofer et al. | May 2001 | B1 |
| 6236994 | Swartz et al. | May 2001 | B1 |
| 6237096 | Bisbee et al. | May 2001 | B1 |
| 6240443 | Suzuki et al. | May 2001 | B1 |
| 6243755 | Takagi et al. | Jun 2001 | B1 |
| 6252544 | Hoffberg | Jun 2001 | B1 |
| 6253188 | Witek et al. | Jun 2001 | B1 |
| 6253208 | Wittgreffe et al. | Jun 2001 | B1 |
| 6253326 | Lincke et al. | Jun 2001 | B1 |
| 6260039 | Schneck et al. | Jul 2001 | B1 |
| 6263501 | Schein et al. | Jul 2001 | B1 |
| 6266615 | Jin | Jul 2001 | B1 |
| 6266774 | Sampath et al. | Jul 2001 | B1 |
| 6271840 | Finseth et al. | Aug 2001 | B1 |
| 6278993 | Kumar et al. | Aug 2001 | B1 |
| 6279037 | Tams et al. | Aug 2001 | B1 |
| 6282278 | Doganata et al. | Aug 2001 | B1 |
| 6286029 | Delph | Sep 2001 | B1 |
| 6286043 | Cuomo et al. | Sep 2001 | B1 |
| 6289346 | Milewski et al. | Sep 2001 | B1 |
| 6289389 | Kikinis | Sep 2001 | B1 |
| 6292787 | Scott et al. | Sep 2001 | B1 |
| 6301584 | Ranger | Oct 2001 | B1 |
| 6301621 | Haverstock et al. | Oct 2001 | B1 |
| 6304860 | Martin, Jr. et al. | Oct 2001 | B1 |
| 6317718 | Fano | Nov 2001 | B1 |
| 6317783 | Freishtat | Nov 2001 | B1 |
| 6324538 | Wesinger, Jr. et al. | Nov 2001 | B1 |
| 6324569 | Ogilvie et al. | Nov 2001 | B1 |
| 6330321 | Detampel, Jr. et al. | Dec 2001 | B2 |
| 6330561 | Cohen et al. | Dec 2001 | B1 |
| 6330592 | Makuch et al. | Dec 2001 | B1 |
| 6334132 | Weeks | Dec 2001 | B1 |
| 6339761 | Cottingham | Jan 2002 | B1 |
| 6341353 | Herman et al. | Jan 2002 | B1 |
| 6345300 | Bakshi et al. | Feb 2002 | B1 |
| 6347398 | Parthasarathy et al. | Feb 2002 | B1 |
| 6349257 | Liu et al. | Feb 2002 | B1 |
| 6349307 | Chen | Feb 2002 | B1 |
| 6351464 | Galvin et al. | Feb 2002 | B1 |
| 6356834 | Hancock et al. | Mar 2002 | B2 |
| 6356899 | Chakrabarti et al. | Mar 2002 | B1 |
| 6356905 | Gershman et al. | Mar 2002 | B1 |
| 6360205 | Iyengar et al. | Mar 2002 | B1 |
| 6360332 | Weinberg et al. | Mar 2002 | B1 |
| 6366923 | Lenk et al. | Apr 2002 | B1 |
| 6377567 | Leonard | Apr 2002 | B1 |
| 6377993 | Brandt et al. | Apr 2002 | B1 |
| 6380890 | Smith et al. | Apr 2002 | B1 |
| 6381592 | Reuning | Apr 2002 | B1 |
| 6385595 | Kolling et al. | May 2002 | B1 |
| 6385655 | Smith et al. | May 2002 | B1 |
| 6397212 | Biffar | May 2002 | B1 |
| 6405245 | Burson et al. | Jun 2002 | B1 |
| 6408292 | Bakalash et al. | Jun 2002 | B1 |
| 6412073 | Rangan | Jun 2002 | B1 |
| 6421693 | Nishiyama et al. | Jul 2002 | B1 |
| 6424979 | Livingston et al. | Jul 2002 | B1 |
| 6430542 | Moran | Aug 2002 | B1 |
| 6438580 | Mears et al. | Aug 2002 | B1 |
| 6442590 | Inala et al. | Aug 2002 | B1 |
| 6442607 | Korn et al. | Aug 2002 | B1 |
| 6453339 | Schultz et al. | Sep 2002 | B1 |
| 6470383 | Leshem et al. | Oct 2002 | B1 |
| 6473740 | Cockrill et al. | Oct 2002 | B2 |
| 6484155 | Kiss | Nov 2002 | B1 |
| 6490601 | Markus et al. | Dec 2002 | B1 |
| 6499036 | Gurevich | Dec 2002 | B1 |
| 6499042 | Markus | Dec 2002 | B1 |
| 6516303 | Wallman | Feb 2003 | B1 |
| 6517587 | Satyavolu et al. | Feb 2003 | B2 |
| 6538673 | Maslov | Mar 2003 | B1 |
| 6544295 | Bodnar | Apr 2003 | B1 |
| 6546393 | Khan | Apr 2003 | B1 |
| 6553359 | Schwenkreis | Apr 2003 | B1 |
| 6560639 | Dan et al. | May 2003 | B1 |
| 6567814 | Bankier et al. | May 2003 | B1 |
| 6567850 | Freishtat | May 2003 | B1 |
| 6572662 | Manohar et al. | Jun 2003 | B2 |
| 6594766 | Rangan et al. | Jul 2003 | B2 |
| 6601066 | Davis-Hall et al. | Jul 2003 | B1 |
| 6605120 | Fields et al. | Aug 2003 | B1 |
| 6606606 | Starr | Aug 2003 | B2 |
| 6609128 | Underwood | Aug 2003 | B1 |
| 6609200 | Anderson | Aug 2003 | B2 |
| 6625581 | Perkowski | Sep 2003 | B1 |
| 6631402 | Devine et al. | Oct 2003 | B1 |
| 6631496 | Li et al. | Oct 2003 | B1 |
| 6633910 | Rajan et al. | Oct 2003 | B1 |
| 6643652 | Helgeson et al. | Nov 2003 | B2 |
| 6694546 | Kasem | Feb 2004 | B1 |
| 6697860 | Kung | Feb 2004 | B1 |
| 6717376 | Lys et al. | Apr 2004 | B2 |
| 6718365 | Dutta | Apr 2004 | B1 |
| 6725425 | Rajan et al. | Apr 2004 | B1 |
| 6732102 | Khandekar | May 2004 | B1 |
| 6745229 | Gobin et al. | Jun 2004 | B1 |
| 6754833 | Black et al. | Jun 2004 | B1 |
| 6792082 | Levine | Sep 2004 | B1 |
| 6792422 | Stride et al. | Sep 2004 | B1 |
| 6801929 | Donoho et al. | Oct 2004 | B1 |
| 6802042 | Rangan | Oct 2004 | B2 |
| 6807558 | Hassett et al. | Oct 2004 | B1 |
| 6810414 | Brittain | Oct 2004 | B1 |
| 6826553 | DaCosta et al. | Nov 2004 | B1 |
| 6847988 | Toyouchi et al. | Jan 2005 | B2 |
| 6856415 | Simchik et al. | Feb 2005 | B1 |
| 6901394 | Chauhan et al. | May 2005 | B2 |
| 6915336 | Hankejh et al. | Jul 2005 | B1 |
| 6915482 | Jellum et al. | Jul 2005 | B2 |
| 6920609 | Manber et al. | Jul 2005 | B1 |
| 6944660 | Eshghi et al. | Sep 2005 | B2 |
| 7006993 | Cheong et al. | Feb 2006 | B1 |
| 7013310 | Messing et al. | Mar 2006 | B2 |
| 7085994 | Gvily | Aug 2006 | B2 |
| 7085997 | Wu et al. | Aug 2006 | B1 |
| 7178096 | Rangan et al. | Feb 2007 | B2 |
| 7225249 | Barry et al. | May 2007 | B1 |
| 7249315 | Moetteli | Jul 2007 | B2 |
| 7313813 | Rangan et al. | Dec 2007 | B2 |
| 20010000537 | Inala et al. | Apr 2001 | A1 |
| 20010011341 | Hayes Jr. et al. | Aug 2001 | A1 |
| 20010016034 | Singh et al. | Aug 2001 | A1 |
| 20010020237 | Yarnall et al. | Sep 2001 | A1 |
| 20010020242 | Gupta et al. | Sep 2001 | A1 |
| 20010023414 | Kumar et al. | Sep 2001 | A1 |
| 20010032182 | Kumar et al. | Oct 2001 | A1 |
| 20010037294 | Freishtat et al. | Nov 2001 | A1 |
| 20010051907 | Kumar et al. | Dec 2001 | A1 |
| 20020002536 | Braco | Jan 2002 | A1 |
| 20020007330 | Kumar et al. | Jan 2002 | A1 |
| 20020015480 | Daswani et al. | Feb 2002 | A1 |
| 20020019810 | Kumar et al. | Feb 2002 | A1 |
| 20020023104 | Satyavolu et al. | Feb 2002 | A1 |
| 20020023108 | Daswani et al. | Feb 2002 | A1 |
| 20020032782 | Rangan et al. | Mar 2002 | A1 |
| 20020059369 | Kern et al. | May 2002 | A1 |
| 20020078079 | Rangan et al. | Jun 2002 | A1 |
| 20020082990 | Jones | Jun 2002 | A1 |
| 20020095651 | Kumar et al. | Jul 2002 | A1 |
| 20020174006 | Rugge et al. | Nov 2002 | A1 |
| 20030120774 | Satyavolu et al. | Jun 2003 | A1 |
| 20030126134 | Messing et al. | Jul 2003 | A1 |
| 20030191661 | Doyle et al. | Oct 2003 | A1 |
| 20030204485 | Triggs | Oct 2003 | A1 |
| 20040031030 | Kidder et al. | Feb 2004 | A1 |
| 20040078282 | Robinson | Apr 2004 | A1 |
| 20040158524 | Anderson et al. | Aug 2004 | A1 |
| 20040162778 | Kramer et al. | Aug 2004 | A1 |
| 20040236696 | Aoki et al. | Nov 2004 | A1 |
| 20050034055 | Rangan et al. | Feb 2005 | A1 |
| 20050165651 | Mohan | Jul 2005 | A1 |
| 20050210297 | Wu et al. | Sep 2005 | A1 |
| 20060116949 | Wehunt et al. | Jun 2006 | A1 |
| 20060253463 | Wu et al. | Nov 2006 | A1 |
| 20060253742 | Elenburg et al. | Nov 2006 | A1 |
| Number | Date | Country |
|---|---|---|
| 0747843 | Dec 1996 | EP |
| 0786728 | Jul 1997 | EP |
| 0848338 | Jun 1998 | EP |
| 7074817 | Mar 1995 | JP |
| 9716796 | May 1997 | WO |
| 9737314 | Oct 1997 | WO |
| 9828698 | Jul 1998 | WO |
| 0133759 | May 2001 | WO |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 09425626 | Oct 1999 | US |
| Child | 09698708 | US | |
| Parent | 09323598 | Jun 1999 | US |
| Child | 09425626 | US | |
| Parent | 09208740 | Dec 1998 | US |
| Child | 09323598 | US |
