CA2306083A1 - Apparatus and method for automated aggregation and delivery of electronic personal information or data - Google Patents
Apparatus and method for automated aggregation and delivery of electronic personal information or data Download PDFInfo
- Publication number
- CA2306083A1 CA2306083A1 CA002306083A CA2306083A CA2306083A1 CA 2306083 A1 CA2306083 A1 CA 2306083A1 CA 002306083 A CA002306083 A CA 002306083A CA 2306083 A CA2306083 A CA 2306083A CA 2306083 A1 CA2306083 A1 CA 2306083A1
- Authority
- CA
- Canada
- Prior art keywords
- end user
- personal information
- information
- provider
- computer
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/953—Querying, e.g. by the use of web search engines
- G06F16/9535—Search customisation based on user profiles and personalisation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/954—Navigation, e.g. using categorised browsing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q30/00—Commerce
- G06Q30/04—Billing or invoicing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/102—Entity profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
- H04L67/306—User profiles
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/53—Network services using third party service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/54—Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/564—Enhancement of application control based on intercepted application data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/567—Integrating service provisioning from a plurality of service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
- H04L2463/102—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00 applying security measure for e-commerce
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/563—Data redirection of data network streams
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/565—Conversion or adaptation of application format or content
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
- H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
- H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
- H04L69/329—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]
Abstract
A system for delivering personal information according to the present invention includes a user store (360) including end user data, a provider store (310) including information provider data, a personal information store (280) including personal information (375) and a processor that communicates with these data stores. The processor selects an end user for personal information aggregation. The processor connects with one or more information providers. The processor then proceeds to retrieve personal information for the selected end user from the connected information providers. This retrieval is based on end user data associated with the selected end user and provider data associated with the connected information providers. The retrieved personal information (375) is stored in the personal information store (280).
Description
APPARATUS AND METHOD FOR AUTOMATED AGGREGATION AND DELIVERY OF
ELECTRONIC PERSONAL INFORMATION OR DATA
CROSS-REFERENCE TO RELATED PATENT APPLICATION
This application claims the benefit, pursuant to 35 U.S.C. ~ 119(e), of applicants' provisional U.S. Patent Application Serial No. 60/105,917, filed October 28, 1998, entitled "Apparatus and Method for Automated Aggregation and Delivery of and Transactions Involving Electronic Personal Information or Data" and of applicants' 1o provisional U.S. Patent Application Serial No. 60/134,395, filed May 17, 1999, entitled "Apparatus and Method for Automated Aggregation and Delivery of and Transactions Involving Electronic Personal Information or Data".
BACKGROUND OF INVENTION
Field of Invention 15 The invention relates to an apparatus and process for automated aggregation and delivery of electronic personal information or data (PI). The invention further relates to the automation of transactions involving electronic PI.
ELECTRONIC PERSONAL INFORMATION OR DATA
CROSS-REFERENCE TO RELATED PATENT APPLICATION
This application claims the benefit, pursuant to 35 U.S.C. ~ 119(e), of applicants' provisional U.S. Patent Application Serial No. 60/105,917, filed October 28, 1998, entitled "Apparatus and Method for Automated Aggregation and Delivery of and Transactions Involving Electronic Personal Information or Data" and of applicants' 1o provisional U.S. Patent Application Serial No. 60/134,395, filed May 17, 1999, entitled "Apparatus and Method for Automated Aggregation and Delivery of and Transactions Involving Electronic Personal Information or Data".
BACKGROUND OF INVENTION
Field of Invention 15 The invention relates to an apparatus and process for automated aggregation and delivery of electronic personal information or data (PI). The invention further relates to the automation of transactions involving electronic PI.
2. Description of Related Art Looking back over the last five years, it is apparent that as the Internet gained 2o momentum, consumers demanded applications or services that make their online experience simpler, easier to use, and more satisfying. The development of successful Internet Sites has corresponded with a number of themes which have developed over the last few years. When carefully analyzed this evolution is a logical development of the emerging digital economy.
25 Prior to 1994, the Internet was not a mass media, in part, because the existing technologies (FTP, Archie, Usenet, and Gopher) were not user friendly and required the end user to do all of the work (e.g., the end user had to learn of an existing data source, find the address, navigate to the destination, and download the information).
As more consumers began accessing the Internet, Search Engines were created to solve this usability issue. With the advent of the commercial Search Engine, additional content could be easily added to the Internet and the end user had a means of finding and accessing this information. Consumers required better tools than Search Engines for organizing and accessing this wealth of generic content. Push technologies were explored, and eventually, the portal strategy was successfully adopted as an efficient way for consumers to easily access a variety of content sources in a single, easy to use format. As the volume of available online content continues to grow exponentially, portals are now confronted with the need to make different types of content available to different consumers based upon their particular preferences and tastes.
The phenomenal success of Internet portals and destination sites has demonstrated the importance of creatively and intelligently aggregating, organizing and presenting the mass of information available on the Web. Search engines, portals and destination sites have Internet strategies based on the frequency, duration and quality of end user visits to their sites. For this reason, destination sites and portals are constantly seeking content and/or technologies which drive quality traffic to their site and keep it there. Recent trends indicate that Internet users are up to 25 times more likely to come back to a site when this information is organized according to personal preferences.
FIG. 1 displays the current process of acquiring online PI 100. The end user 2o first selects an information provider site in step 110. The end user proceeds to step 120 by locating and entering the Internet address of the selected information provider. This step may be accomplished in several manners with varying levels of complexity.
A
simple means for accomplishing this step is the utilization of a bookmark or favorite whereas locating an information provider for the first time might involve significant time and effort performing online searches. In step 130, the end users logs into the selected information provider's Web site utilizing the site's specific logon protocol.
This protocol usually involves verifying the identity of the end user using a user name and password or other means of verification, acquiring the verification data from cookies residing on the end user's system or a combination of requested data and cookie data. The end user continues in step 140 by navigating through Web pages on the information provider's Web site until the desired information is located.
During this process, the end user is often required to visit Web pages of little or no use to the end user whose goals is to simply acquire the particular PI residing on the Web site.
Ultimately in step 150, the end user is presented with the desired PI. The entire process 100 is repeated for each individual piece of PI desired by the end user. Under this PI
access model, the end user must visit each separate information provider, track potentially different identity verification data for each, utilize a different user interface at each site and possibly wade through a significant number of filler Web pages.
FIG. 4 pictorial illustrates the architecture of this current access process.
The end user 210 utilizes the client computer 220 to access each PI Web site 250 across the Internet 230. This current model suffers from several significant deficiencies. The end user must login to each site separately. Each separate site has its own graphical user 2o interface. Each site wants the end user to stay and return; each visited site wants to retain end user focus for as long as possible. No true aggregation of PI
exists; multiple accesses simply allow sequential access to particular pieces of PI.
One partial solution to these problems has recently evolved in the form of portal sites. Generic portal sites aggregate resources into categories and provide links to sites covering topics within those categories. Yahoo and Excite are examples of generic portal sites. These sites facilitate horizontal aggregation of generic content; horizontal aggregation refers to aggregation of PI access within a particular information provider category such as banks or utility companies. Some portal site allows individual end . users a limited capability to select and configure disparate generic PI.
Generic PI refers to PI of interest to the particular end user that does not require specific identity verification to obtain. For example, an end user might be interested in the weather 1o forecast for his local area. This information could be integrated into a portal page without requiring identity verification of the particular end user receiving this PI. The individualized portal page provides a significant benefit to users seeking to aggregate generic PI. However, current portal pages do not generally provide PI
requiring identity verification such as an end user's stock portfolio or bank balance.
Further, these pages do not facilitate transactions utilizing PI.
Under current technology, aggregating PI available over the Internet requires a significant burden in terms of time, effort and learning curve. An end user wishing to access his PI needs to individually visit a variety of information provider sites each with its own requirements, graphical user interface and login protocol.
2o SUMMARY OF THE INVENTION
In the present invention, a networked computer is used to facilitate end user access of, manipulation of and transactions involving electronic PI associated with the particular end user such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data. According to the present invention, the PI relevant to the particular end user is aggregated on the networked computer. This information or data is delivered to the end user in a unified manner by a variety of selectable delivery platforms such as facsimile, client computer, telephone, conventional mail, electronic mail, pager, other wireless device, Web page or channel or other delivery vehicle. The present invention further facilitates a variety of electronic transactions involving PI such as stock trading, retail purchases, bill payment, bank account fund transfers or other transactions.
A system for delivering personal information according to the present invention 1o includes a user store including end user data, a provider store including information provider data, a personal information store including personal information and a processor that communicates with these data stores. The processor supports the aggregation of personal information. The processor selects an end user for personal information aggregation. Once the end user is selected, the processor connects with one or more information providers. The processor then proceeds to retrieve personal information for the selected end user from the connected information providers. This retrieval is based on end user data associated with the selected end user and provider data associated with the connected information providers. The retrieved personal information is stored in the personal information store.
In the one aspect of the present invention, the network computer, alternatively referred to as the host computer, is used to distribute, store and retrieve electronic information associated with the particular end user. In a particular embodiment, the information is personal information such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data.
According to this aspect, the PI relevant to the particular end user is aggregated on the host computer.
The host computer transmits the aggregated data to a client computer associated with the particular end user for whom the PI was aggregated. Preferably, the aggregated data is transmitted to the client computer as cookie data and stored as such by the client computer. In some embodiments, the aggregated data is encrypted prior to transmission. The host computer receives a request concerning the aggregated data.
The source of the request is preferably the client computer, however other suitable device sources are contemplated within the scope of the present invention. The host computer receives the aggregated data from the client computer, preferably as cookie data. If encrypted, the aggregated data is decrypted. The host computer proceeds to service the request to generate a request result. The request result may be delivered to a variety of platforms, preferably a Web page. Alternatively, the result could be delivered to a telephone, an electronic mail destination, a facsimile or other print device, directly to a Web browser, a third computer, a wireless device or other suitable delivery platform.
In another embodiment of this aspect, specialize software may exist on the client computer by which requests concerning the aggregated data transmitted by the host computer may be serviced on the client computer. Such specialized software would include any decryption software if appropriate.
In another aspect of the present invention, electronic information from potentially disparate sources is dynamically combined with style preferences determined from potentially disparate sources to generate a compliant electronic document. In one embodiment of this aspect, electronic PI associated with the particular end user such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data is combined with distributor and provider content to yield the content for the generated document. Stylistic information is accumulated from end user preferences and distributor and provider style information. An adaptably compliant electronic document is generated by applying the combined style information to the combined content. This generated document may be delivered to the end user in a unified manner by a variety of selectable delivery platforms such as facsimile, client computer, wireless device, personal organizer, to telephone, pager, Web page or channel or other delivery vehicle.
A system for dynamically generating adaptably compliant electronic documents according to this aspect of the present invention includes a style merger unit, a content merger unit and a processor, which may be included in the network computer of the present invention. The style merger unit accumulates style information from one or more style providers and dynamically merges the accumulated style information.
The content merger unit accumulates content information from one or more content providers and dynamically merges the accumulated content information. The processor receives the merged style and content information and generates an adaptably compliant electronic document by dynamically applying the received style information 2o to the received content information. The generated page may be outputted to a variety of delivery platforms.
In another aspect, a host computer schedules the harvesting of information associated with one or more end users from one or more information providers.
The host computer is in communication with a user data store for storing data associated with users and an information provider store for storing data associated with information providers and includes a processor.
For each end user, a profile of past access times, login times, is maintained in the user data store. For each information provider, a profile of update times and criteria are maintained in the information provider store. The update times and criteria may be stored with respect to all information provided by each information provider, or update times and criteria may be stored with respect to each piece of information provided by each information provider.
For a selected information provider, the host computer processor determines an update time for information stored by the selected information provider and a set of end users whose information could be modified by an update at that update time.
The host computer processor generates a predicted login time for each end user in the determined set of end users and each generated login time back a predetermined time interval. The host computer processor sorts the determined set of end users according to the predicted login time or shifted login time and assigns a harvesting time for each end user based on each end user's shifted or predicted login time. The host computer processor, in one embodiment of this aspect, may further harvest the information for each end user in the determined set from the selected information provider at the 2o harvesting time assigned to each end user.
In another embodiment of this aspect, the host computer processor determines the set of end users whose information could be modified by an update at the determined update time by first selecting end users configured to receive information form the selected information provider and eliminating those end users not configured to receive information subject to update at the determined update time. The host computer processor may further eliminate end users from the set who do not meet update criteria or conditions for update associated with the information provider or the information subject to update at the determined update time.
The host computer processor may generate a predicted login time for each end user in the determined set based on login time profiles stored in the user store. For each end user in the determined set, a determination is made as to whether the end user's login time profile meets a predetermined confidence threshold. If the profile meets this threshold, a predicted login time is assigned based on the profile. If the profile does not meet this threshold, a predicted login time is assigned corresponding to the present day and time.
A harvesting time is assigned by the host computer processor for each end user based on his predicted login time. In one embodiment of this apsect, the assigned harvesting time for each end user corresponds to his generated predicted login time shift back a predetermined time interval.
In a further embodiment of this aspect, the host computer processor assigns harvesring times for each end user based on not only his predicted login time but also on expected network activity. The host computer processor first performs a distribution 2o fit across time to generate a polynomial function that allows determination of the number of end users subject to harvesting over a specified time period. Next, it determines a network activity curve of network activity associated with it and the selected information provider. An inverse of the determined network activity curve is generated. Then, it performs an integral matching algorithm utilizing the generated polynomial function and the generated inverse of the network activity curve.
Finally, it assigns harvesting times for each end user to redistribute peak harvesting time towards time zero to flatten the distribution fit across time.
In a further aspect of the present invention, electronic actions involving personal information (PI) associated with an end user are automatically performed for the end user. An end user will have a variety of electronic PI associated with him such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data. In an embodiment of this aspect, an end user store contains end to user data associated an end user and records correlating trigger events with responses associated with the end user. A host computer processor accesses the records associated with the end user. For each accessed record, the host computer determines whether the trigger event in the record has occurred, and if so, executes the response correlated to the trigger event determined to occur.
The execution of the response may involve the delivery of a notification of the occun ence of the trigger event to a specified delivery platform such as a wireless device, a facsimile, a telephone, a printing device, a pager, a Web page residing on a Web server, an electronic mail system or other suitable delivery vehicle.
Instead of, or in addition, to such a notification, the host computer may automatically execute a 2o transaction involving the personal information associated with the end user.
In a further embodiment of this aspect, the automated execution of such a transaction will involve the host computer accessing records associated with an information provider based on the response indicated in the accessed end user record in which the trigger event was determined to occur. The host computer connects with an information provider computer indicated by the accessed data associated with the information provider. The host computer then executes a transaction script on the connected information provider computer based on the accessed data associated with the information provider, the response indicated in the accessed end user record in which the trigger event was determined to occur and the end user data from the end user store.
In another aspect of the present invention, a host computer monitors interactions between end users and personal information providers via an intermediary computer.
Interactions will generally fall into two categories: requests for delivery of personal information and requests for transactions involving personal information. The host computer communicates with a personal information store for storing personal information associated with end users and an accounting store for storing accounting data associated with the intermediary computer. The host computer includes a processor.
The host computer processor receives requests concerning personal information associated with an end user from the intermediary computer and services the request based on personal information associated with the end user in the personal information store. The host computer processor updates the accounting data associated with the 2o intermediary computer. The host computer processor may update the accounting data in a variety of ways. First, the host computer processor may increment a user count for each new user of the intermediary computer over a selected period of time.
Next, the host computer processor may count the interactions performed through the intermediary computer. Third, the host computer processor may, where the service request is a request to perform a transaction, increment a commission total an amount based on the serviced request. Finally, the host computer processor may use any combination of these ways to update the accounting data associated with the intermediary computer.
The host computer processor generates invoices to the intermediary computer based on the updated accounting data. The host computer processor may generate such invoices on a periodic basis. In a further embodiment of this aspect, the host computer processor may deliver the generated invoices to a selected destination such as an electronic mail destination, a print device, a Web page residing on a Web server, an Internet client, a telephone, and a facsimile.
In yet another embodiment of this aspect, the intermediary computer has an account associated with it. The host computer processor may debit this account prior to generating an invoice so that the generated invoice only reflects additional revenue beyond the amount indicated by the intermediary computer account. The amount 1s debited may be based upon the updated accounting data associated with the intermediary computer using any of the aforementioned update types.
Another aspect of the present invention is a system and method for automated access to personal information associated with an end user, wherein the personal information is stored on a personal information provider. A representation of the 2o personal information and a link corresponding to the personal information stored on the personal information are presented to the end user via a client computer. Upon activation of the link, the client computer is automatically driven to the personal information provider presenting to the user via the client computer a page on the personal information provider.
In one embodiment of this aspect, an application is downloaded to the client.
The downloaded application initiates a connection between the client computer and the personal information provider. The application navigates through pages on the personal information provider until arriving at the personal information.
Finally, the application presents the personal information to the user on the client computer. The application may be either generated with any necessary data associated with the end user and associated with the personal information or such data may be transmitted to to the application. The data associated with the personal information provider may include a navigation script for guiding the application to the personal information. The data associated with the end user may include any data necessary to effectuate the navigation via the navigation script.
In a further embodiment of this aspect, a message including any necessary user data and personal information provider data is transmitted to the client computer causing the client computer to automatically log the end user into the personal information provider, thereby leaving the end user at a post login page. In a preferred embodiment of this aspect, the message comprises a page containing a form, which includes login information that upon opening by software on the client computer 2o redirects the client computer to a post login page.
In yet a further embodiment of this aspect, the client computer is driven to the personal information by connecting to the personal information provider, navigating to the personal information on the personal information provider. presenting the personal information to the end user via the client computer and proxying subsequent interactions between the client computer and the personal information provider for a given session with the personal information provider.
The above and other objects and advantages of the present invention will become more readily apparent when reference is made to the following description, taken in conjunction with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FTG. 1 is a process diagram of the current process that end users perform to access Internet available PI.
to FIG. 2 is a block diagram of the components that could be used to implement present invention.
FIG. 3 is a block diagram of the components of the PI engine.
FIG. 4 is a diagram of the current PI access architecture.
FIG. 5 is a diagram of an architecture supporting PI access utilizing an 15 intermediary Web site.
FIG. 6 is a diagram of the cookie/client cache architecture.
FIG. 7 is a flowchart for accessing pages underlying particular PI via the traditional process of FIG. 1 and via springboard technology.
FIG. 8 depicts the integration model for the dynamic generation of HTML
2o pages.
FIG. 9 displays the run-time process for dynamic generation of HTML page.
FIG. 10 illustrates a process for automated applet interaction utilizing a modified Java virtual machine.
FIG. 11 is a flowchart exemplifying an intermediary Web site transaction structure.
DETAILED DESCRIPTION OF THE INVENTION
A preferred embodiment of the invention is now described in detail. Refernng 5 to the drawings, like numbers indicate like parts throughout the views. As used in the description herein and throughout the claims that follow, the meaning of "a,"
"an," and "the" includes plural reference unless the context clearly dictates otherwise.
Also, as used in the description herein and throughout the claims that follow, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise.
1o In no time, end users will have to log into a large number of different Web Sites, each with separate passwords, security, rules, software and "look and feel" - just to get the information currently obtained by checking one place - the mailbox at the end of the driveway. The Internet will fundamentally change the way in which end users will access Personal Information (PI) and will make e-commerce as familiar as 15 using an ATM. "Personal Information" is all of the data that companies, information providers, have that is specific or unique to each person such as monthly bills, bank account balances, investments information, health care benefits, email, voice and fax messages, 401(k) holdings or potentially any other information pertinent to a particular end user.
2o The present invention alleviates several of the problems with the current PI
acquisition methods by automatically aggregating PI, not only generic PI as aggregated by portals but also PI specific to the end user requiring identity verification for access.
In one embodiment, the invention automates the PI acquisition and delivery process.
FIG. 2 provides a block diagram of components that could be used to implement the present invention. The end user 210 accesses a client computer 220 running client software 270 which in a particular embodiment could be a general Web browser such as Navigator or Communicator (Netscape). The client computer 220 utilizes the Internet 230 to access a PI engine 240 running on a PI host 290. The PI engine examines stored PI 280 for freshness. Any stale PI items are refreshed by directly reacquiring the PI from the particular information provider's Web site 250 running on the provider's computer system 260 accessed across the Internet 230. The PI
engine 240 stores the fresh PI in its store 280 and delivers the PI to a selected destination, in this instance across the Internet 230 to the client computer 220 which displays the to information to the end user 210 using the client software 270. The PI
engine 240 refreshes all stale PI in a like manner prior to forwarding the aggregated PI
to both the store 280 and the delivery destination, the client computer 220 in this instance. The PI
engine 240 may refresh the PI sequentially or in parallel. For example, the end user's checking account balance would be updated through his bank's Web site, his email from his particular email site, his portfolio information from his broker's site and his electricity bill from his electricity company's site.
FIG. 3 displays a block diagram of the components of the PI engine 240. The PI engine 240 is composed of both storage and processing components. The three primary storage components are the PI store 280, the PI Provider store 310 and the user 2o store 360. The first storage component of the PI engine 240 is the PI store 280. The PI
store 280 contains each individual's PI record 375; the PI associated with a particular end user is segregated from the PI of all other end users. The PI engine also utilizes a provider store 310 that maintains general parameters associated with particular PI
providers. The general parameters of a PI provider define the types of verification data necessary and the procedures to be followed to gain access to the particular PI provider.
Each PI provider record also contains the types of PI provided by the PI
provider and the types of transactions supported by the provider. Along with the type of PI
or transaction, the record also contains the additional types of data and procedures necessary to access the PI or execute the transaction. A user store 360 is also necessary to maintain configuration and verification information concerning particular end users.
For each end user, the user selected PI providers, PI and transactions are registered along with the verification data necessary to acquire the PI or execute the transaction 1 o from the PI provider.
The PI store 280 may be implemented in a variety of ways. Referring to FIG. 2, the PI store 280 may comprise a database residing on the PI Host 290. Under this approach, the PI for each individual end user 210 is stored as a separate record or object 375 in the database. In yet another embodiment, the PI for each end user 210 could be stored in a separate file 375, thus performing the task of segregating PI of different users at the file level.
In addition, or as an alternative, the PI associated with each end user 210 may reside on his/her client computer 220 using cookie technology as specified in D. Kristol and L. Montulli, "HTTP State Management Mechanism", Request For Comments (RFC) 2109, February, 1997 (available at http:Ilwww.ietf.orglrfc/rfc2109.txt), which is expressly incorporated herein in its entirety. The PI associate with the end user 210 would be stored as PI cookies 375. This implementation mechanism provides inherent support for segregating PI associated with one end user 375 from PI associated with all other end users. Utilizing this method as a substitute for a centralized store provides a layer of security against unauthorized access. As a further measure, PI data stored in cookies could be stored in an encrypted format.
FIG. 6 provides a diagram of a typical implementation of the PI store 280 using cookie technology; references in the foregoing description are also made to FIG. 3 with respect to the internal workings of the PI engine 240. When an attempt is made to access PI by an end user 210 directly, or through an intermediary Web server, the PI
access/transact component 340 of the PI engine 240 would retrieve stored PI
375 from the PI store 280. Under this approach, this stored PI 375 would be received directly l0 from cookies sent by the client computer 220 of the end user 210. The PI
accessltransact component 340 would perform any decryption if necessary. Any updates required would be obtained by direct access of PI providers 250. The PI
deliver component 350 would provide the mechanism for both updating the PI
store 280 as well as transmitting the requested PI to the end user 2I0, directly or through an intermediary Web site. The PI deliver component 350 would place the updated PI
in the PI store 280 by replacing the outdated PI cookies 375 stored on the client computer 220. The PI deliver component 350 would also handle any encryption if necessary.
The PI deliver component 350 would also be responsible for transmitting requested PI.
In a preferred embodiment, the PI store 280 would be implemented using this cookie-2o based architecture.
The user store 360 may be implemented in a variety of ways. Referring to FIG.
2, the user store 360 may comprise a database residing on the PI Host 290.
Under this approach, the personal configuration data for each individual end user 210 is stored as a separate record or object in the database. In addition, or as an alternative, the end user data could be distributed in a manner similar to the cooIcie/cache architecture describe above with respect to the PI store 280.
In a preferred embodiment, the user store 360 could be implemented through personal information configuration (PIC) files. PIC files store a personal profile such as name, address, and social security number in secure, encrypted fashion for each end user. PIC files facilitate automatic registration of end users with information Providers via the end user configuration component 330. This component will read the PIC
file and, using retrieved personal information, pre-populate registration templates for to selected Providers. Then, it will prompt the user to enter required information that is missing from profile, if necessary. If the information is complete, the registration is automatically completed. Next, the end user configure component 330 completes any Provider registration forms, gets responses and updates the end user's PIC.
The four primary processing components access and manipulate the data in the three stores. The processing components may execute on a single processor, such as a file server computer system based on a Pentium class (MMX, PRO, II, III, etc.) central processing unit or an equivalent, or multiple processors. These four processing components are the Baseline configure component 320, the end user configure component 330, the PI accessltransact component 340 and the PI delivery component 3~0 as seen in FIG. 3. The Baseline configure component 320 provides the interface by which new user selectable PI providers are added to the system. This component might be implemented in a variety of ways including trial and error followed by manual entry of configuration information, semi-automated trial and error (automated location of Hypertext Markup Language (HTML) <FORM> elements, Javascript functions and Java applets) followed by manual entry of configuration information or, preferably, configuration by example (executing the protocol in a simulated Web client where the simulated Web client automatically generates a list of required data and a list of steps in 5 the access process). These processes would be utilized at two levels: the first level being the set of data and steps required for.general access to the particular PI provider and the second level being the set of additional data and steps required for accessing each particular piece of PI on the PI provider's site. The baseline configuration component 320 may be triggered independently when a new PI provider is added to the 10 system, or it might be triggered as a result of a failure of the PI
access/transact component 340 potentially indicating a change in access requirements for the failed access. This latter warning would more likely result where the PI
access/transact component 340 has made a comparison between requirements supplied by the Provider store 310, both general to the PI provider and specific to the PI or transaction, and the 15 end user data supplied by the user store 360 after seeking end user verification via a request of the end user to confirm the previously entered required access data via the end user configure component 330 and found an inconsistency. When an inconsistency is determined, updates to the Provider store 320 are made to bring the Provider data into conformance with current access/transaction requirements.
2o The end user configure component 330 allows an end user to select and configure PI and transactions of interest to the specific user. This configuration information is maintained in the user store 360. When an end user initially subscribes to the system according to the present invention, the system allows the user to select the WO 00125227 PCTIUS99l25181 types and sources of PI and/or transactions desired. First, the system requests permission from the end user to act on his behalf to obtain any selected PI
and to execute any authorized transactions. Next, the system provides the user with a list of known information suppliers and the types of PI supplied from and transactions supported by the particular PI provider from the Provider store 320. The system requests the verification data necessary for accessing each selected PI
provider and the additional data required by the particular PIs and/or transactions desired from that PI
provider. Assuming the end user is already a registered user with the selected PI
provider or the particular PI provider does not require prior registration, the data 1o supplied by the end user is placed in the user store 360.
One method of obtaining any cookie data would be for the end user to access each previously accessed PI utilizing the PI engine 240 as a proxy server. The PI
engine 240 would pass the cookie data to the PI provider site with the appropriate Web page requests to obtain the PI or execute the transaction and with the end user's permission retain a copy of the cookie data in the his record in the user store 360. An alternate means of obtaining the cookie data would be a direct upload of the cookie information from the end user's computer. In a preferred embodiment, no cookie data is necessary where a user is already registered with a provider. All that is necessary is the verification data for login.
2o If the end user does not have the requisite information because he is not a registered user of a selected PI provider, the user configure component 330 prompts the user for the information necessary to register the end user with the PI
provider and performs the registration procedure required by the PI provider. A simulated Web client could perform this process automatically supplying the access data as required and sending any necessary cookie data. The manner in which such a simulated client registers the end user depends significantly upon the interaction method used on the PI
provider Web site. If the Web site uses HTML forms and common gateway interface (CGI) applications, the end user configure component 330 can formulate a uniform resource locator (URL) to replicate the effect of actual form usage and submit this URL
to the simulated Web client. The use of a URL to mimic an HTML form is equivalent to manually entering the data into the Web <FORM> element. See Kerven, Foust, Zakour, HTML 3.2 Plus How-To, Waite Group Press, 1997, pp. 559-569. If the Web site uses a mixture of HTML forms and Javascript functions, a simulated Web client with a modified Javascript interpreter could effectively register the user by following the end user registration process for the particular PI provider. The registration process to follow would be obtained from the record of the particular PI provider in the Provider store 320. The Javascript interpreter in the simulated Web client would follow ~5 this procedure and supply the data supplied by the end user. A similar process could be used if the registration process on the PI provider Web site utilizes a Java applet. A
Web client with a modified Java bytecode interpreter could effectively register the user by following the end user registration process stored for the particular PI
provider in the Provider store 320. The bytecode interpreter would supply the data previously entered 2o by the end user rather than requiring interactive input from the end user.
If the PI
provider Web site utilizes a combination of forms, scripts and applets, the individual procedures above could be used in combination to accomplish the desired registration.
With reference to FIG. 2 and FIG. 3, a modification of the Java virtual machine (VM) could allow for automated interaction between the various functional components of the PI Engine 240 and Java applet available through provider Web servers 250.
Templates for interacting with particular applets could reside in the Provider store 310.
The specific input data utilized by such templates could be stored in the User store 360.
When a functional component such as the end user configure 330 or the access/transact 340 components requires automated communication with a Java applet on a provider Web server 250, the modified Java VM would facilitate this interaction.
FIG. 10 illustrates one process utilizing such a modified Java VM to achieve 1o such automated interaction. The functional component requiring interaction identifies the provider and the particular applet on that provider with which the component needs to interact in step 1010. In step 1020, the component accesses the necessary template for interacting with the applet from the Provider store 310. Proceeding to step 1030, the component accesses the User store 360 to obtain the data required by the template.
The modified Java VM interprets the applet in step 1040 and, rather than requiring interactive input from a user as in a normal Java applet execution, awaits input from or output to the interacting functional component of the PI engine. In step 1050, the functional component supplies input data to the modified Java VM according to the accessed template and retrieved data and receives output data according to the accessed 2o template. Steps 1040 and 1050 repeat so long as additional input to or output from the applet continues. Upon termination of the applet, the functional component continues with its own processing in step 1060.
A successful registration could result in displaying the registration information to the end user for future reference. Further, the end user configure component 330 stores the requisite access verification data for the PI provider and the additional data required to access the selected PI or transaction in the user store 360.
In a preferred embodiment of such automated registration, any necessary cookie data would be accepted and stored as needed by the end user configure component 330.
In many cases, cookie data is session specific and, therefore, of little long term utility.
Cookies generated during the registration process are used solely during the registration process then discarded once registration is complete.
1o A failed registration could result from several situations. First, the end user attempting to register with the PI provider does not qualify for registration;
for example, an end user attempting to register with a bank with whom the end user does not maintain an account and where the bank only allows access to account holders.
Next, the end user may have supplied improper or incorrect information. For example, 15 a bank registration process might require a social security number, a password, a bank account number and the maiden name of the end user's mother; if the user entered an incorrect social security number, the registration process would fail.
Finally, the PI
provider may have altered the registration procedure for its Web site. In this situation, following the process supplied from the Provider store 320 would yield a failed 2o registration. In the instance of any registration failure, the end user could be presented with the data initially supplied to the system for registration. The system could then ask the end user to double check the correctness of the information provided and to correct and resubmit the data if an error is found. A second failure resulting from the submission of identical requisite data might generate an error message presented to the end user stating that either the end user is ineligible to access the selected PI from the selected PI provider or that alteration by the PI provider may have caused an error in registration. This second failure could also trigger a warning suggesting the need to 5 potentially reconfigure the record for the PI provider in the Provider store 320.
Ultimately, the user store 360 would contain a record for each end user. This record as previous described could be a database entry, one or more cookies or a file such as a PIC file. Each record would identify the selected PI providers along with the general access verification data needed and also under each PI provider would be a list of PI supplied and transactions supported by the particular PI provider of interest to the end user along with the additional data, if any, necessary to access that PI
or execute that transaction. Specifically, duplicative information such as an end user's name would be centrally stored in the record once.
The end user configure component 330 also allows the end user to select one or 15 more delivery destinations. One destination might be the end user's computer as exemplified by the client computer 220 running client software 270 in FIG. 2;
however, a computer is not the only destination contemplated by the present invention.
The destination for PI delivery could include facsimile, electronic mail, telephone, conventional mail, pager, other wireless device such as a Palm Pilot (3 Com), Web 2o page or channel, Web browser or other delivery mechanism. The present invention also contemplates indirect access of PI by the end user utilizing a Web site as an intermediary; however, such indirect access would not require the end user to specify a delivery destination unless additional delivery options were desired.
Further, access to the end user configure component 330 may occur through direct access to the PI engine via the Internet as contemplated by the client computer 220 running client software 270 in FIG. 2; however, alternative methods of access are equally feasible. For example, the user might indirectly access the PI engine through the use of an intermediary Web site. A telephone interface to allow access to the end user configure component is another alternative.
With reference to FIG. 3, the PI access/transact component 340 supports the update, acquisition and transaction functionality of the PI engine 240. The PI
access/transact component 340 is responsible for accessing and storing user PI
and executing transactions authorized by the end user. When access or update is needed for a selected end user, the PI access/transact component 340 combines information from the Provider store 320 and the user store 360 to update end user PI in the PI
store 280.
For each piece of PI requiring access or update, the PI access/transact component 340 looks up the access procedure and information needed for the particular PI in the Provider store 320. The verification and access data is found in the user store 360. The PI access/transact component 340 utilizes this information to connect to the PI
provider's Web site across the Internet and to access the PI. Where multiple pieces of PI require updating or access, the accesses may occur in series or parallel.
Requested transactions would be similarly supported. For each transaction, the PI access/transact component 340 combines information from the Provider store and the user store 360 to perform the requested transaction. The PI
access/transact component 340 looks up the transaction procedure and information needed for the particular transaction in the Provider store 320. The verification and access data is found in the user store 360. The PI access/transact component 340 utilizes this information to perform the transaction across the Internet from the PI
provider's Web site A simulated Web client could perform access or transaction processes automatically supplying access and verification data as necessary. The manner in which such a simulated client access PI or.execute transactions depends significantly upon the interaction method used on the PI provider Web site. If the Web site uses HTML forms and common gateway interface (CGI) applications, the PI
access/transact component 340 can formulate a uniform resource locator (URL) to replicate the effect of actual form usage and submit this URL to the simulated Web client. The use of a URL to mimic an HTML form is equivalent to manually entering the data into the Web <FORM> element. See Kerven, Foust, Zakour, HTML 3.2 Plus How-To, Waite Group Press, 1997, pp. 559-569. If the Web site uses a mixture of HTML forms and Javascript functions, a simulated Web client with a modified Javascript interpreter could effectively access the PI or perform the transaction by following the PI
accessltransact process for the particular PI or transaction respectively. The access or transaction process to follow would be obtained from the record of the particular PI or transaction in the Provider store 320. The Javascript interpreter in the simulated Web client would follow this procedure and supply the data found in the user store 360. A
similar process could be used if the PI provider Web site utilizes a Java applet. A Web client with a modified Java bytecode interpreter could effectively access PI
or perform transactions by following process stored for the particular PI or transaction in the Provider store 320. The bytecode interpreter would supply the data from the user store 360 rather than requiring interactive input from the end user. If the PI
provider Web site utilizes a combination of forms, scripts and applets, the individual procedures above could be used in combination to accomplish the desired access.
In a preferred embodiment of such automated accesses or transactions, any s necessary cookie data would be accepted and stored as needed by the PI
access/transact component 340. In many cases, cookie data is session specific and, therefore, of little long term utility. Cookies generated are used solely during these functions then discarded once the mining or transaction operation is complete.
In order to provide personal information to an end-user quickly after login, it is 1o necessary for the Pi access/transact component 340 to select an end user for data harvesting prior to the login of the end user. One approach to this solution is to update all of an end user's PI whenever the end user, directly or through an intermediary Web site, requests access to his/her PI. Another approach would be to update all of an end user's PI supplied by a particular provider whenever PI from that supplier is requested.
15 Thus, the act of logging into the system by an end user effectively selects that end user for immediate PI update. However, this approach may result in the inefficient use of the PI Engine 240 resources.
Given the large number of potential users and providers, and the goal of providing the freshest data possible, another embodiment includes an algorithm 2o developed to optimize the schedule in which end users are selected for data harvesting from a provider. This algorithm factors in the provider's update policy, the user's login habits, and the user-provider account characteristics. The proper application of the wo oon522~ PCTNS99n5181 algorithm should ensure that PI is harvested as infrequently as possible for a given user, thus minimizing system resource consumption.
If the next provider update time and the next expected user login can be accurately predicted, a model can be created that will allow for smarter harvesting.
s Rather than harvesting data for all users of a provider at once when the provider updates its site, the harvesting can be spread out over time based on expected login times of users and network activity profiles. For example, if Provider A
updates its site on Friday night and a large number of users of that provider are not expected to login again until Monday morning, the harvesting load can be distributed across multiple to days. This has the advantage of minimizing both the peak loading of the PI
Engine 240 as well as consumption of the provider's bandwidth by the PI Engine 240. To gain this optimization, the PI Engine 240 must maintain and refine models of each provider and user. Such data can be maintained in the provider store 310 and the user store respectively.
15 Each time a user utilizes the PI Engine 240, the time and date may be captured.
Once a sufficient number of login times are accumulated, they may be analyzed with respect to day of month, day of week, and time of day. These are used in a model to predict the next expected user login. The model is then tested and refined with subsequent logins until a measurable degree of confidence is established. Once high 2o confidence is determined, the user model is incorporated into the adaptive harvesting scheduler. Until a high confidence level is reached for a particular end user one of the aforementioned harvesting approaches may be used.
Each provider updates its site based on policy driven by their unique resources and business model. For any adaptive scheduler to work, the policy for each provider must be modeled. In some cases, the policy is self-evident. In others, it must be determined empirically. A provider's policy will most likely fall into one of the 5 following categories:
~ Type I. Updated periodically for all users ~ Type II. Updated periodically relative to each user ~ Type III. Updated in a pseudo-random manner The following three approaches may be used based upon provider type.
1o Type I Provider Policy Scheduling Algorithm 1. Assume users with a "no confidence" model have an immediate login time.
2. Order the users chronologically based on their predicted login time.
3. Shift the expected login time for all users back one hour.
25 Prior to 1994, the Internet was not a mass media, in part, because the existing technologies (FTP, Archie, Usenet, and Gopher) were not user friendly and required the end user to do all of the work (e.g., the end user had to learn of an existing data source, find the address, navigate to the destination, and download the information).
As more consumers began accessing the Internet, Search Engines were created to solve this usability issue. With the advent of the commercial Search Engine, additional content could be easily added to the Internet and the end user had a means of finding and accessing this information. Consumers required better tools than Search Engines for organizing and accessing this wealth of generic content. Push technologies were explored, and eventually, the portal strategy was successfully adopted as an efficient way for consumers to easily access a variety of content sources in a single, easy to use format. As the volume of available online content continues to grow exponentially, portals are now confronted with the need to make different types of content available to different consumers based upon their particular preferences and tastes.
The phenomenal success of Internet portals and destination sites has demonstrated the importance of creatively and intelligently aggregating, organizing and presenting the mass of information available on the Web. Search engines, portals and destination sites have Internet strategies based on the frequency, duration and quality of end user visits to their sites. For this reason, destination sites and portals are constantly seeking content and/or technologies which drive quality traffic to their site and keep it there. Recent trends indicate that Internet users are up to 25 times more likely to come back to a site when this information is organized according to personal preferences.
FIG. 1 displays the current process of acquiring online PI 100. The end user 2o first selects an information provider site in step 110. The end user proceeds to step 120 by locating and entering the Internet address of the selected information provider. This step may be accomplished in several manners with varying levels of complexity.
A
simple means for accomplishing this step is the utilization of a bookmark or favorite whereas locating an information provider for the first time might involve significant time and effort performing online searches. In step 130, the end users logs into the selected information provider's Web site utilizing the site's specific logon protocol.
This protocol usually involves verifying the identity of the end user using a user name and password or other means of verification, acquiring the verification data from cookies residing on the end user's system or a combination of requested data and cookie data. The end user continues in step 140 by navigating through Web pages on the information provider's Web site until the desired information is located.
During this process, the end user is often required to visit Web pages of little or no use to the end user whose goals is to simply acquire the particular PI residing on the Web site.
Ultimately in step 150, the end user is presented with the desired PI. The entire process 100 is repeated for each individual piece of PI desired by the end user. Under this PI
access model, the end user must visit each separate information provider, track potentially different identity verification data for each, utilize a different user interface at each site and possibly wade through a significant number of filler Web pages.
FIG. 4 pictorial illustrates the architecture of this current access process.
The end user 210 utilizes the client computer 220 to access each PI Web site 250 across the Internet 230. This current model suffers from several significant deficiencies. The end user must login to each site separately. Each separate site has its own graphical user 2o interface. Each site wants the end user to stay and return; each visited site wants to retain end user focus for as long as possible. No true aggregation of PI
exists; multiple accesses simply allow sequential access to particular pieces of PI.
One partial solution to these problems has recently evolved in the form of portal sites. Generic portal sites aggregate resources into categories and provide links to sites covering topics within those categories. Yahoo and Excite are examples of generic portal sites. These sites facilitate horizontal aggregation of generic content; horizontal aggregation refers to aggregation of PI access within a particular information provider category such as banks or utility companies. Some portal site allows individual end . users a limited capability to select and configure disparate generic PI.
Generic PI refers to PI of interest to the particular end user that does not require specific identity verification to obtain. For example, an end user might be interested in the weather 1o forecast for his local area. This information could be integrated into a portal page without requiring identity verification of the particular end user receiving this PI. The individualized portal page provides a significant benefit to users seeking to aggregate generic PI. However, current portal pages do not generally provide PI
requiring identity verification such as an end user's stock portfolio or bank balance.
Further, these pages do not facilitate transactions utilizing PI.
Under current technology, aggregating PI available over the Internet requires a significant burden in terms of time, effort and learning curve. An end user wishing to access his PI needs to individually visit a variety of information provider sites each with its own requirements, graphical user interface and login protocol.
2o SUMMARY OF THE INVENTION
In the present invention, a networked computer is used to facilitate end user access of, manipulation of and transactions involving electronic PI associated with the particular end user such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data. According to the present invention, the PI relevant to the particular end user is aggregated on the networked computer. This information or data is delivered to the end user in a unified manner by a variety of selectable delivery platforms such as facsimile, client computer, telephone, conventional mail, electronic mail, pager, other wireless device, Web page or channel or other delivery vehicle. The present invention further facilitates a variety of electronic transactions involving PI such as stock trading, retail purchases, bill payment, bank account fund transfers or other transactions.
A system for delivering personal information according to the present invention 1o includes a user store including end user data, a provider store including information provider data, a personal information store including personal information and a processor that communicates with these data stores. The processor supports the aggregation of personal information. The processor selects an end user for personal information aggregation. Once the end user is selected, the processor connects with one or more information providers. The processor then proceeds to retrieve personal information for the selected end user from the connected information providers. This retrieval is based on end user data associated with the selected end user and provider data associated with the connected information providers. The retrieved personal information is stored in the personal information store.
In the one aspect of the present invention, the network computer, alternatively referred to as the host computer, is used to distribute, store and retrieve electronic information associated with the particular end user. In a particular embodiment, the information is personal information such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data.
According to this aspect, the PI relevant to the particular end user is aggregated on the host computer.
The host computer transmits the aggregated data to a client computer associated with the particular end user for whom the PI was aggregated. Preferably, the aggregated data is transmitted to the client computer as cookie data and stored as such by the client computer. In some embodiments, the aggregated data is encrypted prior to transmission. The host computer receives a request concerning the aggregated data.
The source of the request is preferably the client computer, however other suitable device sources are contemplated within the scope of the present invention. The host computer receives the aggregated data from the client computer, preferably as cookie data. If encrypted, the aggregated data is decrypted. The host computer proceeds to service the request to generate a request result. The request result may be delivered to a variety of platforms, preferably a Web page. Alternatively, the result could be delivered to a telephone, an electronic mail destination, a facsimile or other print device, directly to a Web browser, a third computer, a wireless device or other suitable delivery platform.
In another embodiment of this aspect, specialize software may exist on the client computer by which requests concerning the aggregated data transmitted by the host computer may be serviced on the client computer. Such specialized software would include any decryption software if appropriate.
In another aspect of the present invention, electronic information from potentially disparate sources is dynamically combined with style preferences determined from potentially disparate sources to generate a compliant electronic document. In one embodiment of this aspect, electronic PI associated with the particular end user such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data is combined with distributor and provider content to yield the content for the generated document. Stylistic information is accumulated from end user preferences and distributor and provider style information. An adaptably compliant electronic document is generated by applying the combined style information to the combined content. This generated document may be delivered to the end user in a unified manner by a variety of selectable delivery platforms such as facsimile, client computer, wireless device, personal organizer, to telephone, pager, Web page or channel or other delivery vehicle.
A system for dynamically generating adaptably compliant electronic documents according to this aspect of the present invention includes a style merger unit, a content merger unit and a processor, which may be included in the network computer of the present invention. The style merger unit accumulates style information from one or more style providers and dynamically merges the accumulated style information.
The content merger unit accumulates content information from one or more content providers and dynamically merges the accumulated content information. The processor receives the merged style and content information and generates an adaptably compliant electronic document by dynamically applying the received style information 2o to the received content information. The generated page may be outputted to a variety of delivery platforms.
In another aspect, a host computer schedules the harvesting of information associated with one or more end users from one or more information providers.
The host computer is in communication with a user data store for storing data associated with users and an information provider store for storing data associated with information providers and includes a processor.
For each end user, a profile of past access times, login times, is maintained in the user data store. For each information provider, a profile of update times and criteria are maintained in the information provider store. The update times and criteria may be stored with respect to all information provided by each information provider, or update times and criteria may be stored with respect to each piece of information provided by each information provider.
For a selected information provider, the host computer processor determines an update time for information stored by the selected information provider and a set of end users whose information could be modified by an update at that update time.
The host computer processor generates a predicted login time for each end user in the determined set of end users and each generated login time back a predetermined time interval. The host computer processor sorts the determined set of end users according to the predicted login time or shifted login time and assigns a harvesting time for each end user based on each end user's shifted or predicted login time. The host computer processor, in one embodiment of this aspect, may further harvest the information for each end user in the determined set from the selected information provider at the 2o harvesting time assigned to each end user.
In another embodiment of this aspect, the host computer processor determines the set of end users whose information could be modified by an update at the determined update time by first selecting end users configured to receive information form the selected information provider and eliminating those end users not configured to receive information subject to update at the determined update time. The host computer processor may further eliminate end users from the set who do not meet update criteria or conditions for update associated with the information provider or the information subject to update at the determined update time.
The host computer processor may generate a predicted login time for each end user in the determined set based on login time profiles stored in the user store. For each end user in the determined set, a determination is made as to whether the end user's login time profile meets a predetermined confidence threshold. If the profile meets this threshold, a predicted login time is assigned based on the profile. If the profile does not meet this threshold, a predicted login time is assigned corresponding to the present day and time.
A harvesting time is assigned by the host computer processor for each end user based on his predicted login time. In one embodiment of this apsect, the assigned harvesting time for each end user corresponds to his generated predicted login time shift back a predetermined time interval.
In a further embodiment of this aspect, the host computer processor assigns harvesring times for each end user based on not only his predicted login time but also on expected network activity. The host computer processor first performs a distribution 2o fit across time to generate a polynomial function that allows determination of the number of end users subject to harvesting over a specified time period. Next, it determines a network activity curve of network activity associated with it and the selected information provider. An inverse of the determined network activity curve is generated. Then, it performs an integral matching algorithm utilizing the generated polynomial function and the generated inverse of the network activity curve.
Finally, it assigns harvesting times for each end user to redistribute peak harvesting time towards time zero to flatten the distribution fit across time.
In a further aspect of the present invention, electronic actions involving personal information (PI) associated with an end user are automatically performed for the end user. An end user will have a variety of electronic PI associated with him such as stock portfolio, local weather, sports scores, bank account balances or other pertinent information or data. In an embodiment of this aspect, an end user store contains end to user data associated an end user and records correlating trigger events with responses associated with the end user. A host computer processor accesses the records associated with the end user. For each accessed record, the host computer determines whether the trigger event in the record has occurred, and if so, executes the response correlated to the trigger event determined to occur.
The execution of the response may involve the delivery of a notification of the occun ence of the trigger event to a specified delivery platform such as a wireless device, a facsimile, a telephone, a printing device, a pager, a Web page residing on a Web server, an electronic mail system or other suitable delivery vehicle.
Instead of, or in addition, to such a notification, the host computer may automatically execute a 2o transaction involving the personal information associated with the end user.
In a further embodiment of this aspect, the automated execution of such a transaction will involve the host computer accessing records associated with an information provider based on the response indicated in the accessed end user record in which the trigger event was determined to occur. The host computer connects with an information provider computer indicated by the accessed data associated with the information provider. The host computer then executes a transaction script on the connected information provider computer based on the accessed data associated with the information provider, the response indicated in the accessed end user record in which the trigger event was determined to occur and the end user data from the end user store.
In another aspect of the present invention, a host computer monitors interactions between end users and personal information providers via an intermediary computer.
Interactions will generally fall into two categories: requests for delivery of personal information and requests for transactions involving personal information. The host computer communicates with a personal information store for storing personal information associated with end users and an accounting store for storing accounting data associated with the intermediary computer. The host computer includes a processor.
The host computer processor receives requests concerning personal information associated with an end user from the intermediary computer and services the request based on personal information associated with the end user in the personal information store. The host computer processor updates the accounting data associated with the 2o intermediary computer. The host computer processor may update the accounting data in a variety of ways. First, the host computer processor may increment a user count for each new user of the intermediary computer over a selected period of time.
Next, the host computer processor may count the interactions performed through the intermediary computer. Third, the host computer processor may, where the service request is a request to perform a transaction, increment a commission total an amount based on the serviced request. Finally, the host computer processor may use any combination of these ways to update the accounting data associated with the intermediary computer.
The host computer processor generates invoices to the intermediary computer based on the updated accounting data. The host computer processor may generate such invoices on a periodic basis. In a further embodiment of this aspect, the host computer processor may deliver the generated invoices to a selected destination such as an electronic mail destination, a print device, a Web page residing on a Web server, an Internet client, a telephone, and a facsimile.
In yet another embodiment of this aspect, the intermediary computer has an account associated with it. The host computer processor may debit this account prior to generating an invoice so that the generated invoice only reflects additional revenue beyond the amount indicated by the intermediary computer account. The amount 1s debited may be based upon the updated accounting data associated with the intermediary computer using any of the aforementioned update types.
Another aspect of the present invention is a system and method for automated access to personal information associated with an end user, wherein the personal information is stored on a personal information provider. A representation of the 2o personal information and a link corresponding to the personal information stored on the personal information are presented to the end user via a client computer. Upon activation of the link, the client computer is automatically driven to the personal information provider presenting to the user via the client computer a page on the personal information provider.
In one embodiment of this aspect, an application is downloaded to the client.
The downloaded application initiates a connection between the client computer and the personal information provider. The application navigates through pages on the personal information provider until arriving at the personal information.
Finally, the application presents the personal information to the user on the client computer. The application may be either generated with any necessary data associated with the end user and associated with the personal information or such data may be transmitted to to the application. The data associated with the personal information provider may include a navigation script for guiding the application to the personal information. The data associated with the end user may include any data necessary to effectuate the navigation via the navigation script.
In a further embodiment of this aspect, a message including any necessary user data and personal information provider data is transmitted to the client computer causing the client computer to automatically log the end user into the personal information provider, thereby leaving the end user at a post login page. In a preferred embodiment of this aspect, the message comprises a page containing a form, which includes login information that upon opening by software on the client computer 2o redirects the client computer to a post login page.
In yet a further embodiment of this aspect, the client computer is driven to the personal information by connecting to the personal information provider, navigating to the personal information on the personal information provider. presenting the personal information to the end user via the client computer and proxying subsequent interactions between the client computer and the personal information provider for a given session with the personal information provider.
The above and other objects and advantages of the present invention will become more readily apparent when reference is made to the following description, taken in conjunction with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
FTG. 1 is a process diagram of the current process that end users perform to access Internet available PI.
to FIG. 2 is a block diagram of the components that could be used to implement present invention.
FIG. 3 is a block diagram of the components of the PI engine.
FIG. 4 is a diagram of the current PI access architecture.
FIG. 5 is a diagram of an architecture supporting PI access utilizing an 15 intermediary Web site.
FIG. 6 is a diagram of the cookie/client cache architecture.
FIG. 7 is a flowchart for accessing pages underlying particular PI via the traditional process of FIG. 1 and via springboard technology.
FIG. 8 depicts the integration model for the dynamic generation of HTML
2o pages.
FIG. 9 displays the run-time process for dynamic generation of HTML page.
FIG. 10 illustrates a process for automated applet interaction utilizing a modified Java virtual machine.
FIG. 11 is a flowchart exemplifying an intermediary Web site transaction structure.
DETAILED DESCRIPTION OF THE INVENTION
A preferred embodiment of the invention is now described in detail. Refernng 5 to the drawings, like numbers indicate like parts throughout the views. As used in the description herein and throughout the claims that follow, the meaning of "a,"
"an," and "the" includes plural reference unless the context clearly dictates otherwise.
Also, as used in the description herein and throughout the claims that follow, the meaning of "in" includes "in" and "on" unless the context clearly dictates otherwise.
1o In no time, end users will have to log into a large number of different Web Sites, each with separate passwords, security, rules, software and "look and feel" - just to get the information currently obtained by checking one place - the mailbox at the end of the driveway. The Internet will fundamentally change the way in which end users will access Personal Information (PI) and will make e-commerce as familiar as 15 using an ATM. "Personal Information" is all of the data that companies, information providers, have that is specific or unique to each person such as monthly bills, bank account balances, investments information, health care benefits, email, voice and fax messages, 401(k) holdings or potentially any other information pertinent to a particular end user.
2o The present invention alleviates several of the problems with the current PI
acquisition methods by automatically aggregating PI, not only generic PI as aggregated by portals but also PI specific to the end user requiring identity verification for access.
In one embodiment, the invention automates the PI acquisition and delivery process.
FIG. 2 provides a block diagram of components that could be used to implement the present invention. The end user 210 accesses a client computer 220 running client software 270 which in a particular embodiment could be a general Web browser such as Navigator or Communicator (Netscape). The client computer 220 utilizes the Internet 230 to access a PI engine 240 running on a PI host 290. The PI engine examines stored PI 280 for freshness. Any stale PI items are refreshed by directly reacquiring the PI from the particular information provider's Web site 250 running on the provider's computer system 260 accessed across the Internet 230. The PI
engine 240 stores the fresh PI in its store 280 and delivers the PI to a selected destination, in this instance across the Internet 230 to the client computer 220 which displays the to information to the end user 210 using the client software 270. The PI
engine 240 refreshes all stale PI in a like manner prior to forwarding the aggregated PI
to both the store 280 and the delivery destination, the client computer 220 in this instance. The PI
engine 240 may refresh the PI sequentially or in parallel. For example, the end user's checking account balance would be updated through his bank's Web site, his email from his particular email site, his portfolio information from his broker's site and his electricity bill from his electricity company's site.
FIG. 3 displays a block diagram of the components of the PI engine 240. The PI engine 240 is composed of both storage and processing components. The three primary storage components are the PI store 280, the PI Provider store 310 and the user 2o store 360. The first storage component of the PI engine 240 is the PI store 280. The PI
store 280 contains each individual's PI record 375; the PI associated with a particular end user is segregated from the PI of all other end users. The PI engine also utilizes a provider store 310 that maintains general parameters associated with particular PI
providers. The general parameters of a PI provider define the types of verification data necessary and the procedures to be followed to gain access to the particular PI provider.
Each PI provider record also contains the types of PI provided by the PI
provider and the types of transactions supported by the provider. Along with the type of PI
or transaction, the record also contains the additional types of data and procedures necessary to access the PI or execute the transaction. A user store 360 is also necessary to maintain configuration and verification information concerning particular end users.
For each end user, the user selected PI providers, PI and transactions are registered along with the verification data necessary to acquire the PI or execute the transaction 1 o from the PI provider.
The PI store 280 may be implemented in a variety of ways. Referring to FIG. 2, the PI store 280 may comprise a database residing on the PI Host 290. Under this approach, the PI for each individual end user 210 is stored as a separate record or object 375 in the database. In yet another embodiment, the PI for each end user 210 could be stored in a separate file 375, thus performing the task of segregating PI of different users at the file level.
In addition, or as an alternative, the PI associated with each end user 210 may reside on his/her client computer 220 using cookie technology as specified in D. Kristol and L. Montulli, "HTTP State Management Mechanism", Request For Comments (RFC) 2109, February, 1997 (available at http:Ilwww.ietf.orglrfc/rfc2109.txt), which is expressly incorporated herein in its entirety. The PI associate with the end user 210 would be stored as PI cookies 375. This implementation mechanism provides inherent support for segregating PI associated with one end user 375 from PI associated with all other end users. Utilizing this method as a substitute for a centralized store provides a layer of security against unauthorized access. As a further measure, PI data stored in cookies could be stored in an encrypted format.
FIG. 6 provides a diagram of a typical implementation of the PI store 280 using cookie technology; references in the foregoing description are also made to FIG. 3 with respect to the internal workings of the PI engine 240. When an attempt is made to access PI by an end user 210 directly, or through an intermediary Web server, the PI
access/transact component 340 of the PI engine 240 would retrieve stored PI
375 from the PI store 280. Under this approach, this stored PI 375 would be received directly l0 from cookies sent by the client computer 220 of the end user 210. The PI
accessltransact component 340 would perform any decryption if necessary. Any updates required would be obtained by direct access of PI providers 250. The PI
deliver component 350 would provide the mechanism for both updating the PI
store 280 as well as transmitting the requested PI to the end user 2I0, directly or through an intermediary Web site. The PI deliver component 350 would place the updated PI
in the PI store 280 by replacing the outdated PI cookies 375 stored on the client computer 220. The PI deliver component 350 would also handle any encryption if necessary.
The PI deliver component 350 would also be responsible for transmitting requested PI.
In a preferred embodiment, the PI store 280 would be implemented using this cookie-2o based architecture.
The user store 360 may be implemented in a variety of ways. Referring to FIG.
2, the user store 360 may comprise a database residing on the PI Host 290.
Under this approach, the personal configuration data for each individual end user 210 is stored as a separate record or object in the database. In addition, or as an alternative, the end user data could be distributed in a manner similar to the cooIcie/cache architecture describe above with respect to the PI store 280.
In a preferred embodiment, the user store 360 could be implemented through personal information configuration (PIC) files. PIC files store a personal profile such as name, address, and social security number in secure, encrypted fashion for each end user. PIC files facilitate automatic registration of end users with information Providers via the end user configuration component 330. This component will read the PIC
file and, using retrieved personal information, pre-populate registration templates for to selected Providers. Then, it will prompt the user to enter required information that is missing from profile, if necessary. If the information is complete, the registration is automatically completed. Next, the end user configure component 330 completes any Provider registration forms, gets responses and updates the end user's PIC.
The four primary processing components access and manipulate the data in the three stores. The processing components may execute on a single processor, such as a file server computer system based on a Pentium class (MMX, PRO, II, III, etc.) central processing unit or an equivalent, or multiple processors. These four processing components are the Baseline configure component 320, the end user configure component 330, the PI accessltransact component 340 and the PI delivery component 3~0 as seen in FIG. 3. The Baseline configure component 320 provides the interface by which new user selectable PI providers are added to the system. This component might be implemented in a variety of ways including trial and error followed by manual entry of configuration information, semi-automated trial and error (automated location of Hypertext Markup Language (HTML) <FORM> elements, Javascript functions and Java applets) followed by manual entry of configuration information or, preferably, configuration by example (executing the protocol in a simulated Web client where the simulated Web client automatically generates a list of required data and a list of steps in 5 the access process). These processes would be utilized at two levels: the first level being the set of data and steps required for.general access to the particular PI provider and the second level being the set of additional data and steps required for accessing each particular piece of PI on the PI provider's site. The baseline configuration component 320 may be triggered independently when a new PI provider is added to the 10 system, or it might be triggered as a result of a failure of the PI
access/transact component 340 potentially indicating a change in access requirements for the failed access. This latter warning would more likely result where the PI
access/transact component 340 has made a comparison between requirements supplied by the Provider store 310, both general to the PI provider and specific to the PI or transaction, and the 15 end user data supplied by the user store 360 after seeking end user verification via a request of the end user to confirm the previously entered required access data via the end user configure component 330 and found an inconsistency. When an inconsistency is determined, updates to the Provider store 320 are made to bring the Provider data into conformance with current access/transaction requirements.
2o The end user configure component 330 allows an end user to select and configure PI and transactions of interest to the specific user. This configuration information is maintained in the user store 360. When an end user initially subscribes to the system according to the present invention, the system allows the user to select the WO 00125227 PCTIUS99l25181 types and sources of PI and/or transactions desired. First, the system requests permission from the end user to act on his behalf to obtain any selected PI
and to execute any authorized transactions. Next, the system provides the user with a list of known information suppliers and the types of PI supplied from and transactions supported by the particular PI provider from the Provider store 320. The system requests the verification data necessary for accessing each selected PI
provider and the additional data required by the particular PIs and/or transactions desired from that PI
provider. Assuming the end user is already a registered user with the selected PI
provider or the particular PI provider does not require prior registration, the data 1o supplied by the end user is placed in the user store 360.
One method of obtaining any cookie data would be for the end user to access each previously accessed PI utilizing the PI engine 240 as a proxy server. The PI
engine 240 would pass the cookie data to the PI provider site with the appropriate Web page requests to obtain the PI or execute the transaction and with the end user's permission retain a copy of the cookie data in the his record in the user store 360. An alternate means of obtaining the cookie data would be a direct upload of the cookie information from the end user's computer. In a preferred embodiment, no cookie data is necessary where a user is already registered with a provider. All that is necessary is the verification data for login.
2o If the end user does not have the requisite information because he is not a registered user of a selected PI provider, the user configure component 330 prompts the user for the information necessary to register the end user with the PI
provider and performs the registration procedure required by the PI provider. A simulated Web client could perform this process automatically supplying the access data as required and sending any necessary cookie data. The manner in which such a simulated client registers the end user depends significantly upon the interaction method used on the PI
provider Web site. If the Web site uses HTML forms and common gateway interface (CGI) applications, the end user configure component 330 can formulate a uniform resource locator (URL) to replicate the effect of actual form usage and submit this URL
to the simulated Web client. The use of a URL to mimic an HTML form is equivalent to manually entering the data into the Web <FORM> element. See Kerven, Foust, Zakour, HTML 3.2 Plus How-To, Waite Group Press, 1997, pp. 559-569. If the Web site uses a mixture of HTML forms and Javascript functions, a simulated Web client with a modified Javascript interpreter could effectively register the user by following the end user registration process for the particular PI provider. The registration process to follow would be obtained from the record of the particular PI provider in the Provider store 320. The Javascript interpreter in the simulated Web client would follow ~5 this procedure and supply the data supplied by the end user. A similar process could be used if the registration process on the PI provider Web site utilizes a Java applet. A
Web client with a modified Java bytecode interpreter could effectively register the user by following the end user registration process stored for the particular PI
provider in the Provider store 320. The bytecode interpreter would supply the data previously entered 2o by the end user rather than requiring interactive input from the end user.
If the PI
provider Web site utilizes a combination of forms, scripts and applets, the individual procedures above could be used in combination to accomplish the desired registration.
With reference to FIG. 2 and FIG. 3, a modification of the Java virtual machine (VM) could allow for automated interaction between the various functional components of the PI Engine 240 and Java applet available through provider Web servers 250.
Templates for interacting with particular applets could reside in the Provider store 310.
The specific input data utilized by such templates could be stored in the User store 360.
When a functional component such as the end user configure 330 or the access/transact 340 components requires automated communication with a Java applet on a provider Web server 250, the modified Java VM would facilitate this interaction.
FIG. 10 illustrates one process utilizing such a modified Java VM to achieve 1o such automated interaction. The functional component requiring interaction identifies the provider and the particular applet on that provider with which the component needs to interact in step 1010. In step 1020, the component accesses the necessary template for interacting with the applet from the Provider store 310. Proceeding to step 1030, the component accesses the User store 360 to obtain the data required by the template.
The modified Java VM interprets the applet in step 1040 and, rather than requiring interactive input from a user as in a normal Java applet execution, awaits input from or output to the interacting functional component of the PI engine. In step 1050, the functional component supplies input data to the modified Java VM according to the accessed template and retrieved data and receives output data according to the accessed 2o template. Steps 1040 and 1050 repeat so long as additional input to or output from the applet continues. Upon termination of the applet, the functional component continues with its own processing in step 1060.
A successful registration could result in displaying the registration information to the end user for future reference. Further, the end user configure component 330 stores the requisite access verification data for the PI provider and the additional data required to access the selected PI or transaction in the user store 360.
In a preferred embodiment of such automated registration, any necessary cookie data would be accepted and stored as needed by the end user configure component 330.
In many cases, cookie data is session specific and, therefore, of little long term utility.
Cookies generated during the registration process are used solely during the registration process then discarded once registration is complete.
1o A failed registration could result from several situations. First, the end user attempting to register with the PI provider does not qualify for registration;
for example, an end user attempting to register with a bank with whom the end user does not maintain an account and where the bank only allows access to account holders.
Next, the end user may have supplied improper or incorrect information. For example, 15 a bank registration process might require a social security number, a password, a bank account number and the maiden name of the end user's mother; if the user entered an incorrect social security number, the registration process would fail.
Finally, the PI
provider may have altered the registration procedure for its Web site. In this situation, following the process supplied from the Provider store 320 would yield a failed 2o registration. In the instance of any registration failure, the end user could be presented with the data initially supplied to the system for registration. The system could then ask the end user to double check the correctness of the information provided and to correct and resubmit the data if an error is found. A second failure resulting from the submission of identical requisite data might generate an error message presented to the end user stating that either the end user is ineligible to access the selected PI from the selected PI provider or that alteration by the PI provider may have caused an error in registration. This second failure could also trigger a warning suggesting the need to 5 potentially reconfigure the record for the PI provider in the Provider store 320.
Ultimately, the user store 360 would contain a record for each end user. This record as previous described could be a database entry, one or more cookies or a file such as a PIC file. Each record would identify the selected PI providers along with the general access verification data needed and also under each PI provider would be a list of PI supplied and transactions supported by the particular PI provider of interest to the end user along with the additional data, if any, necessary to access that PI
or execute that transaction. Specifically, duplicative information such as an end user's name would be centrally stored in the record once.
The end user configure component 330 also allows the end user to select one or 15 more delivery destinations. One destination might be the end user's computer as exemplified by the client computer 220 running client software 270 in FIG. 2;
however, a computer is not the only destination contemplated by the present invention.
The destination for PI delivery could include facsimile, electronic mail, telephone, conventional mail, pager, other wireless device such as a Palm Pilot (3 Com), Web 2o page or channel, Web browser or other delivery mechanism. The present invention also contemplates indirect access of PI by the end user utilizing a Web site as an intermediary; however, such indirect access would not require the end user to specify a delivery destination unless additional delivery options were desired.
Further, access to the end user configure component 330 may occur through direct access to the PI engine via the Internet as contemplated by the client computer 220 running client software 270 in FIG. 2; however, alternative methods of access are equally feasible. For example, the user might indirectly access the PI engine through the use of an intermediary Web site. A telephone interface to allow access to the end user configure component is another alternative.
With reference to FIG. 3, the PI access/transact component 340 supports the update, acquisition and transaction functionality of the PI engine 240. The PI
access/transact component 340 is responsible for accessing and storing user PI
and executing transactions authorized by the end user. When access or update is needed for a selected end user, the PI access/transact component 340 combines information from the Provider store 320 and the user store 360 to update end user PI in the PI
store 280.
For each piece of PI requiring access or update, the PI access/transact component 340 looks up the access procedure and information needed for the particular PI in the Provider store 320. The verification and access data is found in the user store 360. The PI access/transact component 340 utilizes this information to connect to the PI
provider's Web site across the Internet and to access the PI. Where multiple pieces of PI require updating or access, the accesses may occur in series or parallel.
Requested transactions would be similarly supported. For each transaction, the PI access/transact component 340 combines information from the Provider store and the user store 360 to perform the requested transaction. The PI
access/transact component 340 looks up the transaction procedure and information needed for the particular transaction in the Provider store 320. The verification and access data is found in the user store 360. The PI access/transact component 340 utilizes this information to perform the transaction across the Internet from the PI
provider's Web site A simulated Web client could perform access or transaction processes automatically supplying access and verification data as necessary. The manner in which such a simulated client access PI or.execute transactions depends significantly upon the interaction method used on the PI provider Web site. If the Web site uses HTML forms and common gateway interface (CGI) applications, the PI
access/transact component 340 can formulate a uniform resource locator (URL) to replicate the effect of actual form usage and submit this URL to the simulated Web client. The use of a URL to mimic an HTML form is equivalent to manually entering the data into the Web <FORM> element. See Kerven, Foust, Zakour, HTML 3.2 Plus How-To, Waite Group Press, 1997, pp. 559-569. If the Web site uses a mixture of HTML forms and Javascript functions, a simulated Web client with a modified Javascript interpreter could effectively access the PI or perform the transaction by following the PI
accessltransact process for the particular PI or transaction respectively. The access or transaction process to follow would be obtained from the record of the particular PI or transaction in the Provider store 320. The Javascript interpreter in the simulated Web client would follow this procedure and supply the data found in the user store 360. A
similar process could be used if the PI provider Web site utilizes a Java applet. A Web client with a modified Java bytecode interpreter could effectively access PI
or perform transactions by following process stored for the particular PI or transaction in the Provider store 320. The bytecode interpreter would supply the data from the user store 360 rather than requiring interactive input from the end user. If the PI
provider Web site utilizes a combination of forms, scripts and applets, the individual procedures above could be used in combination to accomplish the desired access.
In a preferred embodiment of such automated accesses or transactions, any s necessary cookie data would be accepted and stored as needed by the PI
access/transact component 340. In many cases, cookie data is session specific and, therefore, of little long term utility. Cookies generated are used solely during these functions then discarded once the mining or transaction operation is complete.
In order to provide personal information to an end-user quickly after login, it is 1o necessary for the Pi access/transact component 340 to select an end user for data harvesting prior to the login of the end user. One approach to this solution is to update all of an end user's PI whenever the end user, directly or through an intermediary Web site, requests access to his/her PI. Another approach would be to update all of an end user's PI supplied by a particular provider whenever PI from that supplier is requested.
15 Thus, the act of logging into the system by an end user effectively selects that end user for immediate PI update. However, this approach may result in the inefficient use of the PI Engine 240 resources.
Given the large number of potential users and providers, and the goal of providing the freshest data possible, another embodiment includes an algorithm 2o developed to optimize the schedule in which end users are selected for data harvesting from a provider. This algorithm factors in the provider's update policy, the user's login habits, and the user-provider account characteristics. The proper application of the wo oon522~ PCTNS99n5181 algorithm should ensure that PI is harvested as infrequently as possible for a given user, thus minimizing system resource consumption.
If the next provider update time and the next expected user login can be accurately predicted, a model can be created that will allow for smarter harvesting.
s Rather than harvesting data for all users of a provider at once when the provider updates its site, the harvesting can be spread out over time based on expected login times of users and network activity profiles. For example, if Provider A
updates its site on Friday night and a large number of users of that provider are not expected to login again until Monday morning, the harvesting load can be distributed across multiple to days. This has the advantage of minimizing both the peak loading of the PI
Engine 240 as well as consumption of the provider's bandwidth by the PI Engine 240. To gain this optimization, the PI Engine 240 must maintain and refine models of each provider and user. Such data can be maintained in the provider store 310 and the user store respectively.
15 Each time a user utilizes the PI Engine 240, the time and date may be captured.
Once a sufficient number of login times are accumulated, they may be analyzed with respect to day of month, day of week, and time of day. These are used in a model to predict the next expected user login. The model is then tested and refined with subsequent logins until a measurable degree of confidence is established. Once high 2o confidence is determined, the user model is incorporated into the adaptive harvesting scheduler. Until a high confidence level is reached for a particular end user one of the aforementioned harvesting approaches may be used.
Each provider updates its site based on policy driven by their unique resources and business model. For any adaptive scheduler to work, the policy for each provider must be modeled. In some cases, the policy is self-evident. In others, it must be determined empirically. A provider's policy will most likely fall into one of the 5 following categories:
~ Type I. Updated periodically for all users ~ Type II. Updated periodically relative to each user ~ Type III. Updated in a pseudo-random manner The following three approaches may be used based upon provider type.
1o Type I Provider Policy Scheduling Algorithm 1. Assume users with a "no confidence" model have an immediate login time.
2. Order the users chronologically based on their predicted login time.
3. Shift the expected login time for all users back one hour.
4. Perform a density curve fit along temporal boundaries to get a polynomial function 15 that can be used to determine the number of user accounts to harvest for a given epoch.
5. Perform an integral matching algorithm with the inverse of the network activity curve for the time period in question to adjust the distribution curve.
6. If possible, re-distribute peak harvesting time toward time zero to flatten the distribution curve.
20 7. Assign harvesting times to the sorted users according to the distribution curve.
8. Monitor time and harvest the user account when appropriate.
WO 00/2522'7 PCTNS99125181 Type II Provider Policy Scheduling Algorithm For each provider that falls into this category, an attribute of the user must be identified that determines when the personal information is updated. In some cases, the user may need to be queried for the information. In others, it can be determined from the harvested information. If the attribute cannot be established for a user via either of these means, the provider site may be monitored daily for changes in personal information until a pattern is established.
Since there is a natural, even distribution of accounts updated by a provider for a given day, a user's account can be harvested an hour before his expected login time.
to As in the Type I algorithm, users with a "no confidence" model should be immediately harvested.
Type III Provider Policy Scheduling Algorithm This type of policy is the most difficult of all. Since the provider updates a user's account in a non-deterministic manner, a decision must be made for each 15 provider as to the criticality of the information relative to the user. For those highly critical providers, each user account should be harvested daily, perhaps even more frequently. For those less critical providers, user accounts should be harvested less frequently and possible when overall system activity is low.
The PI deliver component 350 is responsible for formatting and delivering the 2o Pl to the end user. Usually delivery will only occur subsequent to updating all stale PI.
The PI will be delivered to one or more destinations (e.g. facsimile, telephone, pager, Web browser, e-mail, etc.) as specified in the user store 360 except where the PI is accessed via an intermediary Web site. Where the destination is not an intermediary Web site, the PI deliver component 350 performs all formatting necessary to deliver the PI to the appropriate destinations. For example, where the destination is a Web browser, the PI would be formatted as an HTMI. document, or where the destination is a telephone, the PI would be submitted for voice synthesis and transmission.
In the case of an intermediary Web site, the PI is delivered in a format configurable by the intermediary Web site. FIG. 5 pictorial illustrates a possible embodiment of the current invention utilizing an intermediary Web site. An end user 210 utilizes a client computer 220 to access an intermediary Web site 510 across the Internet 230. The end user 210 logs into the intermediary Web site 510. The 1o intermediary Web site 510 contacts the PI engine 240 across the Internet 230 and directly receives the end user's PI updated as required from the PI provider Web sites 250. The intermediary Web site 510 receives the PI, incorporates it into pages according to its particular formatting style and graphical user interface and delivers these pages to the end user 210. The use of the PI engine 240 is transparent to the end user 210. Further, an intermediary Web site 510 serving aggregate PI to an end user 210 may, and most likely will, simultaneously serve as a PI provider.
In another embodiment, this formatting occurs via a dynamic HTML generation system combining stylistic and layout information from a variety of sources.
The PI
deliver component 350 generates custom HTML pages dynamically. These pages are 2o customized based on a number of stylistic factors (such as background color, foreground color, font size, color and style, page layout, etc) from a variety of sources and content from a variety of sources. Information providers, distributors, the end user, the PI deliver component 350 or any combination of these sources, or other relevant WO OOI25227 PCT/US99/25i81 sources, may provide customization factors used in the page generation.
Finally, each HTML page must be filled in with data. The data used in such pages may originate from such sources as information providers, distributors, the end user, the PI
deliver component 350 or any combination of these sources, or other relevant sources.
The required solution is a system representing a generic algorithm for performing such HTML generation at run-time. The style and content may be provided in any suitable format such as the Extensible Stylesheet Language {XSL), as specified by W3C
in http://www.w3.or~TRIWD-xsl/, which is expressly incorporated herein by reference in its entirety, and/or the Extensible Markup Language (XML) as specified by W3C
in 1o http://www.w3.org/TR/REC-xml, which is expressly incorporated herein by reference in its entirety, or other suitable formatting standard. The key requirements for such a system are complete encapsulation of the problem domain and run-time efficiency.
In preferred embodiments, the solution is based on the following basic model as depicted in FIG. 8:
1. Six sets of customization factors are identified: distributor content 810, provider content 820, distributor style specification 830, provider style specification 840, user-specific content 850 and user-specific style 860.
2. Each set of customization factors 810-860 is considered a separate, independent and required input to the run-time system 870 that performs dynamic page generation.
3. Each input 810-860 will be in form of an XML stream.
4. Output 880 will be in form of an HTML stream.
wo oons2z~ Pc~rms99nsisl 5. The dynamic page generation system 870 will produce valid output 880 for each set of six valid inputs 810-860.
FIG. 9 illustrates an actual run-time sequence of input processing by such a system 870:
1. Distributor content 810 is combined with provider content 820 and with user-specific content 850 to produce a complete content specification 930 by the content merger unit 910.
2. Distributor style 830 is combined with provider style 840 and with user-specific style 860 to produce a complete style specification 940 by the style merger unit 920.
3. The style specification 940 is applied by the style applicator 950 to content specification 930 in order to produce the resulting page 880.
In order to completely encapsulate the problem domain, the following requirements must be placed on the system 870:
1. Each XML input 810-860 is a valid XML stream.
2. All content specifications 810, 820 and 850 are valid with respect to the same Document Type Definition.
3. All style specifications 830, 840 and 860 are valid with respect to the same Document Type Definition (such as the XSL DTD standard).
4. The merging units 910 and 920 whose task is to take two or more XML, streams and produce a combined XML output must be able to produce such output for any set of valid XML inputs.
Another method of performing this task would be to format PI as HTML
elements with predefined CLASS attributes. The intermediary Web site receiving these elements could dynamically include them in page forwarded to the end user of the PI.
The pages incorporating such elements could include different style information 5 associated with the predefined CLASS set. Level I cascading style sheet convention could be used to implement such configurability. See Kerven, Foust, Zakour, HTML
3.2 Plus How-To, Waite Group Press, 1997, pp. 651-693; Walsh, "An Introduction to Cascading Style Sheets," World Wide Web Journal, Winter 1997, pp. 147-156.
This option requires minimal programmatic support by the intermediary Web site but 10 restricts to some degree the intermediary Web sites flexibility in presenting the PI to the end user.
Alternatively, an intermediary Web site could develop an application utilizing a standardized application programming interface (API) to directly access the PI
data. In this instance, the PI deliver component 350 could either be bypassed or potentially used 15 as the component responsible for servicing API requests far data. Under this model, the intermediary Web site would be responsible for all formatting decisions with respect to the raw PI data. This implementation option requires additional programmatic support by the intermediary Web site but allows for greater flexibility in the use of the raw PI.
2o The ability to utilize an intermediate Web site to deliver PI is of significant utility. This capability allows an end user already familiar with an existing PI provider to access not only the PI associated with the particular PI provider but also all PI from other PI providers in the comfort of a familiar user interface, namely the existing PI
provider Web site. In this situation, the request for PI would directly originate with the intermediary PI provider Web site and indirectly from the end user. Security measures would restrict access to authorized intermediate Web site access. These measure might include verification of the end user and the intermediate Web site. Further, verification of the association between the end user and the particular intermediate Web site might also be required for additional security.
In addition, the use of an intermediary Web site also supports a novel transaction model. In this transaction model, the intermediary site subsidizes, or fully compensates, the PI engine administrator for services provided to the end user. These transactions are facilitated via the auditing and tracking capabilities of the PI engine.
These capabilities allow the calculation of per user fees, per transaction fees, per access fees or some combination thereof to be assessed. The assessed values could be directly charged to the intermediary Web site. Alternatively, such values could be debited from a minimum monthly fee charged to the intermediary Web site with any fees beyond the 15 minimum charged directly to the intermediary Web site.
FIG. 11 depicts a flowchart of a typical process according to the described model. The intermediary Web site pays a minimum monthly fee in step 1110. In step 1120, the PI engine audits and tracks end user usage via the intermediary Web site.
The audited usage is used to assess a fee on a per user, per access, per transaction or 20 combination basis. In step 1130, this audited amount is debited from the fee paid in step 1110. In step 1140, the intermediary Web site is charged for any fees in excess of the minimum fee paid.
Often an end user may require access to the underlying Web page generated by the provider of a particular piece of PI. The delivery component may deliver not only the PI but also an access point directly to the provider's page supplying that PI. The access point may take the form of a link, a form button or some other interactive access mechanism.
Such an access point significantly improves the efficiency of accessing the underlying page by the end user as exhibited by FIG. 7. In the traditional process 100 for accessing PI, the end user must proceed through numerous intermediary pages requiring a variety of often tedious interactions before reaching the desired page.
1o The end user must first identify the Provider 110. Next, the end user must locate the Provider's Web address 120. Then, the user the requests the Provider's login page 130. If the end user does not remember the requisite information, this information must be found, or the desired information will remain inaccessible via the Web. The end user then navigates the Provider's Web site 140. This often entails visiting the ~5 Provider's main page 710 followed by viewing a variety of intermediate pages on the Provider's site 720. The end user may have to backtrack several times to the main page 710 or accidentally leave the system entirely forcing a second login 140 before finally locating the desired information 150.
Utilizing springboard technology, the entire process 750 is streamlined into the 2o single click of an access point. The delivery component of the PI Engine delivers an access point to the Provider's underlying page along with the PI. As a consequence, the end user need only perform a single interaction with the PI presentation page 7b0.
This interaction immediately performs the requisite interactions with the Provider's Web site to bring the user to the desired underlying Web page 150.
In one embodiment, this springboard technology could be implemented utilizing a Java applet. With respect to FIG. 2, the applet would be downloaded from the PI
Host 290 by the end user's client software 270, usually a Web browser, and executed locally by the end user's computer 220. The applet would drive the client software 270 to the desired page. Such an applet could retrieve procedures and data for driving the client software from the Provider store 310 and the User store360.
In a further embodiment, the PI engine 240 could act as a proxy server directly 1o accessing the Provider store 310 and the User store 360 as required. When the PI
engine 240 receives the request to jump to the source of a particular piece of PI, the engine performs the necessary actions to navigate to the desire page and forwards the desired page to the end user's computer 220. Further interactions with the page might require additional proxying by the PI engine 240 as accumulated cookie data may reside on the PI Host 290. This embodiment is limited to use in handling standard HTTP traffic rather than secure HTTP traffic.
In a preferred embodiment, the springboard provides the end user with automated login into the PI Provider site 250 and allows the end user 210 to navigate via the client software 270. This automated login could be accomplished through the 2o utilization of a hypertext transfer protocol (HTTP) redirect. Upon receiving the a springboard access request from the end user 210 via the client software 270, the PI
Host 290 requests the login page from the PI Provider site 250 targeted by the springboard access. The PI engine 240 running on the PI Host 290 receives this login page and constructs a login request by accessing the proper data in the Provider store 310 and the User store 360. The login request is embedded in the HTTP redirect which is forward to the client software 270. The client software 270 is redirected to the targeted PI Provider site 250, and the end user 210 is automatically logged into this site.
Alternatively, this functionality could be implemented via a Java applet as described above. In addition, the PI engine 240 could generate a Javascript page containing the pertinent login request rather than an HT'TP redirect. The Javascript page could be returned to the client software 270. This page would then be executed by the client software 270 to accomplish the automated login.
1o The PI engine 240 of FIG. 3 may also include a site monitor 370 processing component. This component would systematically monitor supported PI provider Web sites for changes. This component enhances the ability of the system to identify alterations in PI provider Web site procedures, data requirements and cookies requirements. This component increases system efficiency by supplementing or IS supplanting alteration identification via feedback from the PI
access/transact component 340.
A further embodiment of the present invention might support the localize manipulation of PI. This could be accomplished where the client software 270 running on the client computer 220 in FIG. 2 is a specialized Web client rather than a general 2o Web client such as Netscape. This specialized client might utilize Web channel technology to automate the local PI download and update processes. Where the PI
store is implemented via the aforementioned cookie architecture, this specialized client may provide direct local access to stored PI.
In another embodiment, the PI engine 240 of FIG. 3 might support both system supported PI providers as well as PI providers specific to particular end users. In this embodiment, an end user is not limited to PI available from PI providers present in the Provider store 310: For an end user to add PI provided by a non-supported PI
provider, the end user would access the Baseline configure component 320 and create a configuration for the non-supported PI provider. The PI provider and PI
configuration along with the verification and access data would be stored along with the user's record in the user store 360.
A further embodiment of the present invention supports the inclusion of PI
1o transaction procedures and access requirements in the Provider store 310 of FIG. 3.
The end user specific information necessary to realize such a transaction would reside with the user record in the user store 360. The functionality of the PI
access/transact component 340 would expand to support the performance of transactions. This additional functionality could be supported in a manner similar to the procedure 15 described above with respect to performance of access utilizing a simulated Web client.
A further feature of this embodiment would include automated or semi-automated account management by providing trigger events to automatically initiate a transaction.
For instance, with reference to FIG. 2 an end user 210 would be able to maintain his/her accounts online through the PI Engine 240. If an information provider 2o has the capability of receiving payments online, the PI Engine 240 could support complete or partial automation of such transactions. If there is a billing due date for a certain information provider, PI Engine 240 could flag that information and send email to the end user 210 notifying him/her of the bill due. Thus, the user will not have to WO 00/25227 PC'T/US99/25181 check each of his/her providers individually for due date information. The PI
Engine 240 could also automated payments on a limited range of billing amount for providers who allow payments over their Web servers 260, then send an email to the user with the notification of payment.
Due date acquisition could be accomplished utilizing the PI access/transact component 340 seen in FIG. 3. The due date information would be available to the end user via any delivery means~supported by the PI deliver component 350. The PI
access/transact component 340 would use standard e-commerce bill-paying methods to pay the user's bills to the provider if he/she chooses. Once the bill is paid, then an to email notification will be sent to the user with the provider information and payment information. The user can specify the range of amount stored in the user store 360 that will be paid automatically. If the bill exceeds the amount specified by the user, then PI
engine will simply send out an email notification to the user instead of paying the bill automatically.
15 The embodiments described above are given as illustrative examples only. It will be readily appreciated that many deviations may be made from the specific embodiment disclosed in this specification without departing from the invention.
Accordingly, the scope of the invention is to be determined by the claims below rather than being limited to the specifically described embodiments above.
20 7. Assign harvesting times to the sorted users according to the distribution curve.
8. Monitor time and harvest the user account when appropriate.
WO 00/2522'7 PCTNS99125181 Type II Provider Policy Scheduling Algorithm For each provider that falls into this category, an attribute of the user must be identified that determines when the personal information is updated. In some cases, the user may need to be queried for the information. In others, it can be determined from the harvested information. If the attribute cannot be established for a user via either of these means, the provider site may be monitored daily for changes in personal information until a pattern is established.
Since there is a natural, even distribution of accounts updated by a provider for a given day, a user's account can be harvested an hour before his expected login time.
to As in the Type I algorithm, users with a "no confidence" model should be immediately harvested.
Type III Provider Policy Scheduling Algorithm This type of policy is the most difficult of all. Since the provider updates a user's account in a non-deterministic manner, a decision must be made for each 15 provider as to the criticality of the information relative to the user. For those highly critical providers, each user account should be harvested daily, perhaps even more frequently. For those less critical providers, user accounts should be harvested less frequently and possible when overall system activity is low.
The PI deliver component 350 is responsible for formatting and delivering the 2o Pl to the end user. Usually delivery will only occur subsequent to updating all stale PI.
The PI will be delivered to one or more destinations (e.g. facsimile, telephone, pager, Web browser, e-mail, etc.) as specified in the user store 360 except where the PI is accessed via an intermediary Web site. Where the destination is not an intermediary Web site, the PI deliver component 350 performs all formatting necessary to deliver the PI to the appropriate destinations. For example, where the destination is a Web browser, the PI would be formatted as an HTMI. document, or where the destination is a telephone, the PI would be submitted for voice synthesis and transmission.
In the case of an intermediary Web site, the PI is delivered in a format configurable by the intermediary Web site. FIG. 5 pictorial illustrates a possible embodiment of the current invention utilizing an intermediary Web site. An end user 210 utilizes a client computer 220 to access an intermediary Web site 510 across the Internet 230. The end user 210 logs into the intermediary Web site 510. The 1o intermediary Web site 510 contacts the PI engine 240 across the Internet 230 and directly receives the end user's PI updated as required from the PI provider Web sites 250. The intermediary Web site 510 receives the PI, incorporates it into pages according to its particular formatting style and graphical user interface and delivers these pages to the end user 210. The use of the PI engine 240 is transparent to the end user 210. Further, an intermediary Web site 510 serving aggregate PI to an end user 210 may, and most likely will, simultaneously serve as a PI provider.
In another embodiment, this formatting occurs via a dynamic HTML generation system combining stylistic and layout information from a variety of sources.
The PI
deliver component 350 generates custom HTML pages dynamically. These pages are 2o customized based on a number of stylistic factors (such as background color, foreground color, font size, color and style, page layout, etc) from a variety of sources and content from a variety of sources. Information providers, distributors, the end user, the PI deliver component 350 or any combination of these sources, or other relevant WO OOI25227 PCT/US99/25i81 sources, may provide customization factors used in the page generation.
Finally, each HTML page must be filled in with data. The data used in such pages may originate from such sources as information providers, distributors, the end user, the PI
deliver component 350 or any combination of these sources, or other relevant sources.
The required solution is a system representing a generic algorithm for performing such HTML generation at run-time. The style and content may be provided in any suitable format such as the Extensible Stylesheet Language {XSL), as specified by W3C
in http://www.w3.or~TRIWD-xsl/, which is expressly incorporated herein by reference in its entirety, and/or the Extensible Markup Language (XML) as specified by W3C
in 1o http://www.w3.org/TR/REC-xml, which is expressly incorporated herein by reference in its entirety, or other suitable formatting standard. The key requirements for such a system are complete encapsulation of the problem domain and run-time efficiency.
In preferred embodiments, the solution is based on the following basic model as depicted in FIG. 8:
1. Six sets of customization factors are identified: distributor content 810, provider content 820, distributor style specification 830, provider style specification 840, user-specific content 850 and user-specific style 860.
2. Each set of customization factors 810-860 is considered a separate, independent and required input to the run-time system 870 that performs dynamic page generation.
3. Each input 810-860 will be in form of an XML stream.
4. Output 880 will be in form of an HTML stream.
wo oons2z~ Pc~rms99nsisl 5. The dynamic page generation system 870 will produce valid output 880 for each set of six valid inputs 810-860.
FIG. 9 illustrates an actual run-time sequence of input processing by such a system 870:
1. Distributor content 810 is combined with provider content 820 and with user-specific content 850 to produce a complete content specification 930 by the content merger unit 910.
2. Distributor style 830 is combined with provider style 840 and with user-specific style 860 to produce a complete style specification 940 by the style merger unit 920.
3. The style specification 940 is applied by the style applicator 950 to content specification 930 in order to produce the resulting page 880.
In order to completely encapsulate the problem domain, the following requirements must be placed on the system 870:
1. Each XML input 810-860 is a valid XML stream.
2. All content specifications 810, 820 and 850 are valid with respect to the same Document Type Definition.
3. All style specifications 830, 840 and 860 are valid with respect to the same Document Type Definition (such as the XSL DTD standard).
4. The merging units 910 and 920 whose task is to take two or more XML, streams and produce a combined XML output must be able to produce such output for any set of valid XML inputs.
Another method of performing this task would be to format PI as HTML
elements with predefined CLASS attributes. The intermediary Web site receiving these elements could dynamically include them in page forwarded to the end user of the PI.
The pages incorporating such elements could include different style information 5 associated with the predefined CLASS set. Level I cascading style sheet convention could be used to implement such configurability. See Kerven, Foust, Zakour, HTML
3.2 Plus How-To, Waite Group Press, 1997, pp. 651-693; Walsh, "An Introduction to Cascading Style Sheets," World Wide Web Journal, Winter 1997, pp. 147-156.
This option requires minimal programmatic support by the intermediary Web site but 10 restricts to some degree the intermediary Web sites flexibility in presenting the PI to the end user.
Alternatively, an intermediary Web site could develop an application utilizing a standardized application programming interface (API) to directly access the PI
data. In this instance, the PI deliver component 350 could either be bypassed or potentially used 15 as the component responsible for servicing API requests far data. Under this model, the intermediary Web site would be responsible for all formatting decisions with respect to the raw PI data. This implementation option requires additional programmatic support by the intermediary Web site but allows for greater flexibility in the use of the raw PI.
2o The ability to utilize an intermediate Web site to deliver PI is of significant utility. This capability allows an end user already familiar with an existing PI provider to access not only the PI associated with the particular PI provider but also all PI from other PI providers in the comfort of a familiar user interface, namely the existing PI
provider Web site. In this situation, the request for PI would directly originate with the intermediary PI provider Web site and indirectly from the end user. Security measures would restrict access to authorized intermediate Web site access. These measure might include verification of the end user and the intermediate Web site. Further, verification of the association between the end user and the particular intermediate Web site might also be required for additional security.
In addition, the use of an intermediary Web site also supports a novel transaction model. In this transaction model, the intermediary site subsidizes, or fully compensates, the PI engine administrator for services provided to the end user. These transactions are facilitated via the auditing and tracking capabilities of the PI engine.
These capabilities allow the calculation of per user fees, per transaction fees, per access fees or some combination thereof to be assessed. The assessed values could be directly charged to the intermediary Web site. Alternatively, such values could be debited from a minimum monthly fee charged to the intermediary Web site with any fees beyond the 15 minimum charged directly to the intermediary Web site.
FIG. 11 depicts a flowchart of a typical process according to the described model. The intermediary Web site pays a minimum monthly fee in step 1110. In step 1120, the PI engine audits and tracks end user usage via the intermediary Web site.
The audited usage is used to assess a fee on a per user, per access, per transaction or 20 combination basis. In step 1130, this audited amount is debited from the fee paid in step 1110. In step 1140, the intermediary Web site is charged for any fees in excess of the minimum fee paid.
Often an end user may require access to the underlying Web page generated by the provider of a particular piece of PI. The delivery component may deliver not only the PI but also an access point directly to the provider's page supplying that PI. The access point may take the form of a link, a form button or some other interactive access mechanism.
Such an access point significantly improves the efficiency of accessing the underlying page by the end user as exhibited by FIG. 7. In the traditional process 100 for accessing PI, the end user must proceed through numerous intermediary pages requiring a variety of often tedious interactions before reaching the desired page.
1o The end user must first identify the Provider 110. Next, the end user must locate the Provider's Web address 120. Then, the user the requests the Provider's login page 130. If the end user does not remember the requisite information, this information must be found, or the desired information will remain inaccessible via the Web. The end user then navigates the Provider's Web site 140. This often entails visiting the ~5 Provider's main page 710 followed by viewing a variety of intermediate pages on the Provider's site 720. The end user may have to backtrack several times to the main page 710 or accidentally leave the system entirely forcing a second login 140 before finally locating the desired information 150.
Utilizing springboard technology, the entire process 750 is streamlined into the 2o single click of an access point. The delivery component of the PI Engine delivers an access point to the Provider's underlying page along with the PI. As a consequence, the end user need only perform a single interaction with the PI presentation page 7b0.
This interaction immediately performs the requisite interactions with the Provider's Web site to bring the user to the desired underlying Web page 150.
In one embodiment, this springboard technology could be implemented utilizing a Java applet. With respect to FIG. 2, the applet would be downloaded from the PI
Host 290 by the end user's client software 270, usually a Web browser, and executed locally by the end user's computer 220. The applet would drive the client software 270 to the desired page. Such an applet could retrieve procedures and data for driving the client software from the Provider store 310 and the User store360.
In a further embodiment, the PI engine 240 could act as a proxy server directly 1o accessing the Provider store 310 and the User store 360 as required. When the PI
engine 240 receives the request to jump to the source of a particular piece of PI, the engine performs the necessary actions to navigate to the desire page and forwards the desired page to the end user's computer 220. Further interactions with the page might require additional proxying by the PI engine 240 as accumulated cookie data may reside on the PI Host 290. This embodiment is limited to use in handling standard HTTP traffic rather than secure HTTP traffic.
In a preferred embodiment, the springboard provides the end user with automated login into the PI Provider site 250 and allows the end user 210 to navigate via the client software 270. This automated login could be accomplished through the 2o utilization of a hypertext transfer protocol (HTTP) redirect. Upon receiving the a springboard access request from the end user 210 via the client software 270, the PI
Host 290 requests the login page from the PI Provider site 250 targeted by the springboard access. The PI engine 240 running on the PI Host 290 receives this login page and constructs a login request by accessing the proper data in the Provider store 310 and the User store 360. The login request is embedded in the HTTP redirect which is forward to the client software 270. The client software 270 is redirected to the targeted PI Provider site 250, and the end user 210 is automatically logged into this site.
Alternatively, this functionality could be implemented via a Java applet as described above. In addition, the PI engine 240 could generate a Javascript page containing the pertinent login request rather than an HT'TP redirect. The Javascript page could be returned to the client software 270. This page would then be executed by the client software 270 to accomplish the automated login.
1o The PI engine 240 of FIG. 3 may also include a site monitor 370 processing component. This component would systematically monitor supported PI provider Web sites for changes. This component enhances the ability of the system to identify alterations in PI provider Web site procedures, data requirements and cookies requirements. This component increases system efficiency by supplementing or IS supplanting alteration identification via feedback from the PI
access/transact component 340.
A further embodiment of the present invention might support the localize manipulation of PI. This could be accomplished where the client software 270 running on the client computer 220 in FIG. 2 is a specialized Web client rather than a general 2o Web client such as Netscape. This specialized client might utilize Web channel technology to automate the local PI download and update processes. Where the PI
store is implemented via the aforementioned cookie architecture, this specialized client may provide direct local access to stored PI.
In another embodiment, the PI engine 240 of FIG. 3 might support both system supported PI providers as well as PI providers specific to particular end users. In this embodiment, an end user is not limited to PI available from PI providers present in the Provider store 310: For an end user to add PI provided by a non-supported PI
provider, the end user would access the Baseline configure component 320 and create a configuration for the non-supported PI provider. The PI provider and PI
configuration along with the verification and access data would be stored along with the user's record in the user store 360.
A further embodiment of the present invention supports the inclusion of PI
1o transaction procedures and access requirements in the Provider store 310 of FIG. 3.
The end user specific information necessary to realize such a transaction would reside with the user record in the user store 360. The functionality of the PI
access/transact component 340 would expand to support the performance of transactions. This additional functionality could be supported in a manner similar to the procedure 15 described above with respect to performance of access utilizing a simulated Web client.
A further feature of this embodiment would include automated or semi-automated account management by providing trigger events to automatically initiate a transaction.
For instance, with reference to FIG. 2 an end user 210 would be able to maintain his/her accounts online through the PI Engine 240. If an information provider 2o has the capability of receiving payments online, the PI Engine 240 could support complete or partial automation of such transactions. If there is a billing due date for a certain information provider, PI Engine 240 could flag that information and send email to the end user 210 notifying him/her of the bill due. Thus, the user will not have to WO 00/25227 PC'T/US99/25181 check each of his/her providers individually for due date information. The PI
Engine 240 could also automated payments on a limited range of billing amount for providers who allow payments over their Web servers 260, then send an email to the user with the notification of payment.
Due date acquisition could be accomplished utilizing the PI access/transact component 340 seen in FIG. 3. The due date information would be available to the end user via any delivery means~supported by the PI deliver component 350. The PI
access/transact component 340 would use standard e-commerce bill-paying methods to pay the user's bills to the provider if he/she chooses. Once the bill is paid, then an to email notification will be sent to the user with the provider information and payment information. The user can specify the range of amount stored in the user store 360 that will be paid automatically. If the bill exceeds the amount specified by the user, then PI
engine will simply send out an email notification to the user instead of paying the bill automatically.
15 The embodiments described above are given as illustrative examples only. It will be readily appreciated that many deviations may be made from the specific embodiment disclosed in this specification without departing from the invention.
Accordingly, the scope of the invention is to be determined by the claims below rather than being limited to the specifically described embodiments above.
Claims (93)
1. A system for delivering personal information from at least one information provider to at least one end user comprising:
(a) a user store for storing end user data associated with each end user;
(b) a provider store for storing information provider data associated with each information provider;
(c) a personal information store for storing personal information associated with each end user;
(d) a processor in communication with the user store, the provider store and the personal information store, for performing the steps of:
(i) connecting with at least one information provider;
(ii) for a selected end user, retrieving personal information for the selected end user from the connected at least one information provider based on end user data associated with the selected end user and information provider data associated with the connected one or more information providers; and (iii) storing the retrieved personal information in the personal information store.
(a) a user store for storing end user data associated with each end user;
(b) a provider store for storing information provider data associated with each information provider;
(c) a personal information store for storing personal information associated with each end user;
(d) a processor in communication with the user store, the provider store and the personal information store, for performing the steps of:
(i) connecting with at least one information provider;
(ii) for a selected end user, retrieving personal information for the selected end user from the connected at least one information provider based on end user data associated with the selected end user and information provider data associated with the connected one or more information providers; and (iii) storing the retrieved personal information in the personal information store.
2. The system of claim 1, wherein the processor performs the additional step of monitoring information providers for changes.
3. The system of claim 1, wherein the processor performs the additional step of updating the provider store to conform with requirements of the information provider.
4. The system of claim 1, wherein the processor performs the additional step of executing a transaction for the selected end user with a selected information provider based on the end user data associated with the selected end user and the information provider data associated with the selected information provider.
5. The system of claim 4, wherein the processor automatically performs the transaction execution step according to end user data in the user store.
6. The system of claim 1, wherein the processor performs the additional step of outputting the personal information associated with the selected end user from the personal information store.
7. The system of claim 6, wherein the outputting step performed by the processor outputs the personal information to a delivery platform specified in the end user data associated with the selected end user.
8. The system of claim 7, wherein the specified delivery platform is selected from the group consisting of electronic mail, facsimile, pager, telephone, wireless device, ftp server, Web server, gopher server and Web client.
9. The system of claim 6, wherein the outputting step of the processor outputs the personal information via a world wide web site.
10. The system of claim 1, wherein the connecting step of the processor performs the following substeps:
(A) accessing the end user data associated with the selected end user;
(B) identifying information providers specified in the accessed end user data; and (C) establishing a communication link with each of the identified information providers.
(A) accessing the end user data associated with the selected end user;
(B) identifying information providers specified in the accessed end user data; and (C) establishing a communication link with each of the identified information providers.
11. A method for delivering personal information to at least one end user from at least one information provider comprising the steps of:
(a) connecting with at least one information provider;
(b) for a selected end user, retrieving personal information for the selected end user from the connected at least one information provider based on end user data associated with the selected end user and information provider data associated with the connected one or more information providers; and (c) storing the retrieved personal information in a personal information store.
(a) connecting with at least one information provider;
(b) for a selected end user, retrieving personal information for the selected end user from the connected at least one information provider based on end user data associated with the selected end user and information provider data associated with the connected one or more information providers; and (c) storing the retrieved personal information in a personal information store.
12. The method of claim 11, further comprising the step of monitoring information providers for changes.
13. The method of claim 11, further comprising the step of updating the provider store to conform with requirements of the information provider.
14. The method of claim 11, further comprising the step of executing a transaction for the selected end user with a selected information provider based on the accessed end user and the accessed information provider data associated with the selected information provider.
15. The method of claim 14, wherein the execution step is triggered according to the accessed end user data.
16. The method of claim 11, further comprising the step of outputting the personal information associated with the selected end user from the personal information store.
17. The method of claim 16, wherein the outputting step outputs the personal information to a delivery platform specified in the accessed end user data.
18. The method of claim 17, wherein the specified delivery platform is selected from the group consisting of electronic mail, facsimile, pager, telephone, wireless device, ftp server, Web server, gopher server and Web client.
19. The method of claim 16, wherein the outputting step outputs the personal information via a world wide web site.
20. The method of claim 11, wherein the connecting step comprises the substeps of:
(i) accessing the end user data associated with the selected end user;
(ii) identifying information providers specified in the accessed end user data; and (iii) establishing a communication link with each of the identified information providers.
(i) accessing the end user data associated with the selected end user;
(ii) identifying information providers specified in the accessed end user data; and (iii) establishing a communication link with each of the identified information providers.
21. A computer-readable, digital storage device storing executable instructions which cause a processor to deliver personal information by performing the steps comprising of:
(a) connecting with at least one information provider;
(b) for a selected end user, retrieving personal information for the selected end user from the connected at least one information provider based on end user data associated with the selected end user and information provider data associated with the connected one or more information providers; and (c) storing the retrieved personal information in a personal information store.
(a) connecting with at least one information provider;
(b) for a selected end user, retrieving personal information for the selected end user from the connected at least one information provider based on end user data associated with the selected end user and information provider data associated with the connected one or more information providers; and (c) storing the retrieved personal information in a personal information store.
22. The storage device of claim 21, further storing executable instructions to perform the connecting step by performing substeps comprising of:
(i) accessing the end user data associated with the selected end user;
(ii) identifying information providers specified in the accessed end user data; and (iii) establishing a communication link with each of the identified information providers.
(i) accessing the end user data associated with the selected end user;
(ii) identifying information providers specified in the accessed end user data; and (iii) establishing a communication link with each of the identified information providers.
23. A method for distributing, storing and retrieving data associated with an end user aggregated from one or more information providers between a host computer and a client computer associated with the end user, comprising the steps of:
(a) aggregating data associated with the end user by the host computer from one or more information providers;
(b) transmitting the aggregated data from the host computer to the client computer;
(c) receiving at the client computer the aggregated data from the host computer;
(d) storing the received aggregated data at the client computer;
(e) receiving by the host computer a request concerning the aggregated data;
(f) receiving by the host computer the stored aggregated data from the client computer; and (g) servicing by the host computer the received request based on the received, stored aggregated data to generate a request result.
(a) aggregating data associated with the end user by the host computer from one or more information providers;
(b) transmitting the aggregated data from the host computer to the client computer;
(c) receiving at the client computer the aggregated data from the host computer;
(d) storing the received aggregated data at the client computer;
(e) receiving by the host computer a request concerning the aggregated data;
(f) receiving by the host computer the stored aggregated data from the client computer; and (g) servicing by the host computer the received request based on the received, stored aggregated data to generate a request result.
24. The method of claim 23, and further comprising the step of outputting the request result to a designated delivery platform.
25. The method of claim 23, and further comprising the step of encrypting the aggregated data by the host computer prior to transmission to the client computer and wherein the step of servicing the received request by the host computer comprises decrypting the received aggregated data by the host computer.
26. The method of claim 23, wherein the step of storing the received aggregated data at the client computer comprises storing the aggregated data as cookie data.
27. The method of claim 23, wherein the step of transmitting the aggregated data from the host computer to the client computer comprises formatting the aggregated data as cookie data.
28. A system for distributing, storing and retrieving data associated with an end user aggregated from one or more information providers between a host computer and a client computer associated with the end user, comprising a host computer in communication the client computer, the host computer comprising a processor for performing the steps of:
(a) aggregating data associated with the end user from one or more information providers;
(b) transmitting the aggregated data to the client computer;
(c) receiving a request concerning the aggregated data;
(d) receiving stored aggregated data from the client computer; and (e) servicing the received request based on the received, stored aggregated data to generate a request result.
(a) aggregating data associated with the end user from one or more information providers;
(b) transmitting the aggregated data to the client computer;
(c) receiving a request concerning the aggregated data;
(d) receiving stored aggregated data from the client computer; and (e) servicing the received request based on the received, stored aggregated data to generate a request result.
29. The system of claim 28, and the processor further performing the step of formatting the aggregated data as cookie data prior to transmission.
30. A digital, computer-readable storage device storing instructions that when executed on a processor distribute, store and retrieve data associated with an end user aggregated from one or more information providers between a host computer and a client computer associated with the end user, by performing the steps comprising of:
(a) aggregating data associated with the end user from one or more information providers;
(b) transmitting the aggregated data to the client computer;
(c) receiving a request concerning the aggregated data;
(d) receiving stored aggregated data from the client computer; and (e) servicing the received request based on the received, stored aggregated data to generate a request result.
(a) aggregating data associated with the end user from one or more information providers;
(b) transmitting the aggregated data to the client computer;
(c) receiving a request concerning the aggregated data;
(d) receiving stored aggregated data from the client computer; and (e) servicing the received request based on the received, stored aggregated data to generate a request result.
31. A system for generating adaptably compliant electronic documents, comprising:
(a) a style merger unit in communication with at least one style source, the style merger unit for performing the steps of:
(i) accumulating style information from the at least one style source;
and (ii) dynamically merging style information from each style source;
and (b) a content merger unit in communication with at least one content source, the content merger unit for.performing the steps of:
(i) accumulating content information from each content source; and (ii) dynamically merging content information from each content source; and (c) a processor in communication with the style merger unit and with the content information merger unit, the processor for performing the steps of:
(i) receiving the merged style information;
(ii) receiving the merged content information; and (iii) applying the received style information to the received content information to dynamically generate a compliant document.
(a) a style merger unit in communication with at least one style source, the style merger unit for performing the steps of:
(i) accumulating style information from the at least one style source;
and (ii) dynamically merging style information from each style source;
and (b) a content merger unit in communication with at least one content source, the content merger unit for.performing the steps of:
(i) accumulating content information from each content source; and (ii) dynamically merging content information from each content source; and (c) a processor in communication with the style merger unit and with the content information merger unit, the processor for performing the steps of:
(i) receiving the merged style information;
(ii) receiving the merged content information; and (iii) applying the received style information to the received content information to dynamically generate a compliant document.
32. The system of claim 31, wherein the at least one style provider comprises a style source selected from the group consisting of an information provider server, a distributor server, a user terminal, a personal information deliver component, and combinations thereof.
33. The system of claim 31, wherein the style merger unit is a process running on the processor.
34. The system of claim 31, wherein the style information comprises an XML
stream.
stream.
35. The system of claim 31, wherein the content information comprises an XML
stream.
stream.
36. The system of claim 31, wherein the content merger unit is a process running on the processor.
37. The system of claim 36, wherein the style merger unit is a process running on the processor.
38. The system of claim 31, wherein the processor performs the further step of outputting the compliant document.
39. A method of producing an adaptably compliant electronic document, comprising the steps of:
(a) accumulating style information from at least one style provider;
(b) dynamically merging the accumulated style information;
(c) retrieving content information comprises accumulating content information from at least one content provider;
(d) dynamically merging the accumulated content information; and (e) dynamically applying the retrieved style information to the retrieved content information to generate a compliant document.
(a) accumulating style information from at least one style provider;
(b) dynamically merging the accumulated style information;
(c) retrieving content information comprises accumulating content information from at least one content provider;
(d) dynamically merging the accumulated content information; and (e) dynamically applying the retrieved style information to the retrieved content information to generate a compliant document.
40. The method of claim 39, and further comprising the step of outputting the compliant document.
41. A method for scheduling harvesting of information by a host computer from one or more information providers for one or more users, comprising the steps of:
(a) for a selected information provider, determining an update time for information stored by the selected information provider;
(b) for the selected information provider, determining a set of end users whose information could be modified by an update at the determined update time;
(c) generating a predicted login time for each end user in the determined set of end users;
(d) sorting the determined set of end users according to the predicted login time generated for each end user in the determined set;
(e) assigning a harvesting time for each end user based on each end user's predicted login time.
(a) for a selected information provider, determining an update time for information stored by the selected information provider;
(b) for the selected information provider, determining a set of end users whose information could be modified by an update at the determined update time;
(c) generating a predicted login time for each end user in the determined set of end users;
(d) sorting the determined set of end users according to the predicted login time generated for each end user in the determined set;
(e) assigning a harvesting time for each end user based on each end user's predicted login time.
42. The method of claim 41, wherein the step of sorting the determined set of end users comprises sorting the determined set in ascending order of predicted login time.
43. The method of claim 41, wherein the step of generating a predicted login time for each end user in the determined set of end users comprises:
(i) for each end user, determining whether a login time profile associated with the end user meets a predetermined confidence threshold;
(ii) for each end user whose login time profile does not meet the predetermined confidence threshold, assigning a predicted login time corresponding to the present day and time; and (iii) for each end user whose login time profile does meet the predetermined confidence threshold, assigning a predicted login time based on the end user's login time profile.
(i) for each end user, determining whether a login time profile associated with the end user meets a predetermined confidence threshold;
(ii) for each end user whose login time profile does not meet the predetermined confidence threshold, assigning a predicted login time corresponding to the present day and time; and (iii) for each end user whose login time profile does meet the predetermined confidence threshold, assigning a predicted login time based on the end user's login time profile.
44. The method of claim 41, and further comprising the step of shifting each end user's predicted login time back a predetermined time interval.
45. The method of claim 44, wherein the step of assigning a harvest time comprises assigning a harvest time for each end user corresponding to his shifted login time.
46. The method of claim 41, wherein the step of assigning a harvest time comprises:
(i) performing a distribution fit across time to generate a polynomial function that allows determination of the number of end users subject to harvesting over a specified time period;
(ii) determining a network activity curve of network activity associated with the host computer and the selected information provider;
(iii) generating an inverse of the determined network activity curve;
(iv) performing an integral matching algorithm utilizing the generated polynomial function and the generated inverse of the network activity curve; and (v) assigning harvesting times for each end user to redistribute peak harvesting time towards time zero to flatten the distribution fit across time.
(i) performing a distribution fit across time to generate a polynomial function that allows determination of the number of end users subject to harvesting over a specified time period;
(ii) determining a network activity curve of network activity associated with the host computer and the selected information provider;
(iii) generating an inverse of the determined network activity curve;
(iv) performing an integral matching algorithm utilizing the generated polynomial function and the generated inverse of the network activity curve; and (v) assigning harvesting times for each end user to redistribute peak harvesting time towards time zero to flatten the distribution fit across time.
47. The method of claim 41, and further comprising the step of harvesting the information for each end user in the determined set of end user from the selected information provider at the harvesting time assigned to each end user.
48. A system for scheduling harvesting of information by a host computer from one or more information providers for one or more users, comprising:
(a) a user store for storing data associated with end users;
(b) a provider store for storing data associated with information providers;
and (c) a host computer in communication with the user store and the provider store, the host computer comprising a processor for performing the steps of:
(i) for a selected information provider, determining an update time for information stored by the selected information provider based on data associated with the selected information provider in the provider store;
(ii) for the selected information provider, determining a set of end users whose information could be modified by an update at the determined update time based on data associated with end users in the user store;
(iii) generating a predicted login time for each end user in the determined set of end users;
(iv) sorting the determined set of end users according to the predicted login time generated for each end user in the determined set; and (v) assigning a harvesting time for each end user based on each end user's predicted login time.
(a) a user store for storing data associated with end users;
(b) a provider store for storing data associated with information providers;
and (c) a host computer in communication with the user store and the provider store, the host computer comprising a processor for performing the steps of:
(i) for a selected information provider, determining an update time for information stored by the selected information provider based on data associated with the selected information provider in the provider store;
(ii) for the selected information provider, determining a set of end users whose information could be modified by an update at the determined update time based on data associated with end users in the user store;
(iii) generating a predicted login time for each end user in the determined set of end users;
(iv) sorting the determined set of end users according to the predicted login time generated for each end user in the determined set; and (v) assigning a harvesting time for each end user based on each end user's predicted login time.
49. The system of claim 48, wherein the host computer processor performs the further step of harvesting the personal information for each end user in the determined set of end user from the selected information provider at the harvesting time assigned to each end user.
50. A computer-readable storage device storing instructions that upon execution cause a processor to schedule harvesting of information by a host computer from one or more information providers for one or more users by performing the steps of:
(a) for a selected information provider, determining an update time for information stored by the selected information provider;
(b) for the selected information provider, determining a set of end users whose information could be modified by an update at the determined update time;
(c) generating a predicted login time for each end user in the determined set of end users;
(d) sorting the determined set of end users according to the predicted login time generated for each end user in the determined set; and (e) assigning a harvesting time for each end user based on each end user's predicted login time.
(a) for a selected information provider, determining an update time for information stored by the selected information provider;
(b) for the selected information provider, determining a set of end users whose information could be modified by an update at the determined update time;
(c) generating a predicted login time for each end user in the determined set of end users;
(d) sorting the determined set of end users according to the predicted login time generated for each end user in the determined set; and (e) assigning a harvesting time for each end user based on each end user's predicted login time.
51. A method for automatically performing an action for an end user based on personal information associated with the end user aggregated from one or more information providers and records associated with the end user in an end user store, wherein each record identifies a trigger event and an associated response to be performed with respect to the personal information, the method comprising the steps of:
(a) for each record associated with the end user, determining whether the trigger event has occurred based on the aggregated personal; and (b) for each record for which the trigger event was determined to have occurred, executing the associated response.
(a) for each record associated with the end user, determining whether the trigger event has occurred based on the aggregated personal; and (b) for each record for which the trigger event was determined to have occurred, executing the associated response.
52. The method of claim 51, wherein the step of executing the associated response comprises delivering a notification of the trigger event to a predetermined delivery platform.
53. The method of claim 52, wherein the predetermined delivery platform is selected from the group consisting of a wireless device, a facsimile, a telephone, a printing device, a pager, a Web page residing on a Web server and an electronic mail system.
54. The method of claim 51, wherein the step of executing the associated response comprises:
(i) retrieving data associated with an information provider based on the associated response;
(ii) connecting to an information provider computer based on the accessed data associated with the information provider; and (iii) executing a transaction script on the information provider computer based on the accessed data associated with the information provider, the associated response and end user data associated with the end user in the end user store.
(i) retrieving data associated with an information provider based on the associated response;
(ii) connecting to an information provider computer based on the accessed data associated with the information provider; and (iii) executing a transaction script on the information provider computer based on the accessed data associated with the information provider, the associated response and end user data associated with the end user in the end user store.
55. The method of claim 54, wherein the step of executing the associated response further comprises delivering a notification of the trigger event and the execution of the associated response to a predetermined delivery platform.
56. The method of claim 55, wherein the predetermined delivery platform is selected from the group consisting of a wireless device, a facsimile, a telephone, a printing device, a pager, a Web page residing on a Web server and an electronic mail system.
57. A computer-readable storage device storing instruction that upon execution cause a processor to automatically perform an action for an end user based on personal information associated with the end user aggregated from one or more information providers and records associated with the end user in an end user store, wherein each record identifies a trigger event and an associated response to be performed with respect to the personal information, by performing the steps of:
(a) for each record associated with the end user, determining whether the trigger event has occurred based on the aggregated personal information;
and (b) for each record for which the trigger event was determined to have occurred, executing the associated response.
(a) for each record associated with the end user, determining whether the trigger event has occurred based on the aggregated personal information;
and (b) for each record for which the trigger event was determined to have occurred, executing the associated response.
58. The storage device of claim 57, wherein the instructions causing the processor to perform the step of executing the associated response comprise instructions causing the processor to perform the step of delivering a notification of the trigger event to a predetermined delivery platform.
59. The storage device of claim 57, wherein the instructions causing the processor to perform the step of executing the associated response comprises instructions causing the processor to perform the steps of:
(i) accessing data associated with an information provider based on the associated response;
(ii) connecting to an information provider computer based on the accessed data associated with the information provider; and (iii) executing a transaction script on the information provider computer based on the accessed data associated with the information provider, the associated response and end user data associated with the end user in the end user store.
(i) accessing data associated with an information provider based on the associated response;
(ii) connecting to an information provider computer based on the accessed data associated with the information provider; and (iii) executing a transaction script on the information provider computer based on the accessed data associated with the information provider, the associated response and end user data associated with the end user in the end user store.
60. The storage device of claim 59, wherein the instructions causing the processor to perform the step of executing the associated response comprise instructions causing the processor to perform the further step of delivering a notification of the trigger event to a predetermined delivery platform.
61. A system for automatically performing an action for an end user based on personal information associated with the end user aggregated from one or more information providers and records associated with the end user in a user store, wherein each record identifies a trigger event and an associated response to be performed with respect to the personal information, the system comprising:
(a) a user store for storing end user data associated with an end user and the records identifying trigger events and associated responses to be performed with respect to the personal information;
(b) a personal information store for storing personal information associated with the end user; and (c) a host computer in communication with the user store and the personal information store, the host computer comprising a processor for performing the steps of:
(i) for each record associated with the end user in the user store, determining whether the trigger event has occurred based on the aggregated personal information; and (ii) for each record for which the trigger event was determined to have occurred, executing the associated response.
(a) a user store for storing end user data associated with an end user and the records identifying trigger events and associated responses to be performed with respect to the personal information;
(b) a personal information store for storing personal information associated with the end user; and (c) a host computer in communication with the user store and the personal information store, the host computer comprising a processor for performing the steps of:
(i) for each record associated with the end user in the user store, determining whether the trigger event has occurred based on the aggregated personal information; and (ii) for each record for which the trigger event was determined to have occurred, executing the associated response.
62. A method for monitoring interactions between a personal information provider and an end user of personal information via an intermediary computer to determine revenue derived from the interactions, comprising the steps of:
(a) receiving from the intermediary computer a request concerning personal information associated with the end user;
(b) servicing the received request based on the personal information associated with the end user stored at the personal information provider;
(c) updating accounting data associated with the intermediary computer based on the serviced request; and (d) generating an invoice to the intermediary computer based on the updated accounting data associated with the intermediary computer.
(a) receiving from the intermediary computer a request concerning personal information associated with the end user;
(b) servicing the received request based on the personal information associated with the end user stored at the personal information provider;
(c) updating accounting data associated with the intermediary computer based on the serviced request; and (d) generating an invoice to the intermediary computer based on the updated accounting data associated with the intermediary computer.
63. The method of claim 62, wherein the step of generating an invoice occurs periodically.
64. The method of claim 62, and further comprising the step of delivering the generated invoice to a selected destination.
65. The method of claim 64, wherein the selected destination is selected from the group consisting of an electronic mail destination, a print device, a Web page residing on a Web server, an Internet client, a telephone, and a facsimile.
66. The method of claim 62, and further comprising the step of debiting an account associated with the intermediary computer.
67. The method of claim 62, wherein the step of servicing the received request comprises providing personal information to the intermediary computer.
68. The method of claim 67, wherein the step of updating accounting data associated with the intermediary computer comprises incrementing a count of requests concerning personal information made via the intermediary computer for a selected time period.
69. The method of claim 68, and further comprising the step of debiting an account associated with the intermediary computer based on the count of requests.
70. The method of claim 67, wherein the step of updating accounting data associated with the intermediary computer comprises incrementing a count of users associated with the intermediary computer if an end user has not accessed his personal information via the intermediary computer for a selected time period.
71. The method of claim 70, and further comprising the step of debiting an account associated with the intermediary computer based on the count of users.
72. The method of claim 62, wherein the step of servicing the received request comprises executing a transaction involving personal information via the intermediary computer.
73. The method of claim 72, wherein the step of updating accounting data associated with the intermediary computer comprises incrementing a count of requests concerning personal information made via the intermediary computer for a selected time period.
74. The method of claim 73, and further comprising the step of debiting an account associated with the intermediary computer based on the count of requests.
75. The method of claim 72, wherein the step of updating accounting data associated with the intermediary computer comprises incrementing a count of users associated with the intermediary computer if an end user has not executed a transaction concerning his personal information via the intermediary computer for a selected time period.
76. The method of claim 75, and further comprising the step of debiting an account associated with the intermediary computer based on the count of users.
77. The method of claim 72, wherein the step of updating accounting data associated with the intermediary computer comprises incrementing a commission total associated with the intermediary computer for a selected time period based on the executed transaction.
78. The method of claim 77, and further comprising the step of debiting an account associated with the intermediary computer based on the commission total.
79. A computer-readable storage device containing instructions that upon execution cause a processor to monitor interactions between a personal information provider and an end user of personal information via an intermediary computer to determine revenue derived from the interactions by performing the steps comprising of:
{a) receiving from the intermediary computer a request concerning personal information associated with the end user;
(b) servicing the received request based on the personal information associated with the end user stored at a selected information provider;
(c) updating accounting data associated with the intermediary computer based on the serviced request; and (d) generating an invoice to the intermediary computer based on the updated accounting data associated with the intermediary computer.
{a) receiving from the intermediary computer a request concerning personal information associated with the end user;
(b) servicing the received request based on the personal information associated with the end user stored at a selected information provider;
(c) updating accounting data associated with the intermediary computer based on the serviced request; and (d) generating an invoice to the intermediary computer based on the updated accounting data associated with the intermediary computer.
80. The storage device of claim 79, and storing further instructions that upon execution cause the processor to perform the step of delivering the generated invoice to a selected destination.
81. The storage device of claim 79, and storing further instructions that upon execution cause the processor to perform the step of debiting an account associated with the intermediary computer.
82. A system for monitoring interactions between a personal information provider and an end user of personal information via an intermediary computer to determine revenue derived from the interactions, comprising:
(a) a personal information store for storing personal information associated with an end user;
(b) an accounting store for storing accounting data associated with the intermediary computer;
(c) a host computer in communication with the personal information store, the accounting store and the intermediary computer, the host computer comprising a processor for performing the steps of:
(i) receiving from the intermediary computer a request concerning personal information associated with the end user;
(ii) servicing the received request based on the personal information associated with the end user stored in the personal information store;
(iii) updating accounting data associated with the intermediary computer based on the serviced request in the accounting store;
and (iv) generating an invoice to the intermediary computer based on the updated accounting data associated with the intermediary computer from the accounting store.
(a) a personal information store for storing personal information associated with an end user;
(b) an accounting store for storing accounting data associated with the intermediary computer;
(c) a host computer in communication with the personal information store, the accounting store and the intermediary computer, the host computer comprising a processor for performing the steps of:
(i) receiving from the intermediary computer a request concerning personal information associated with the end user;
(ii) servicing the received request based on the personal information associated with the end user stored in the personal information store;
(iii) updating accounting data associated with the intermediary computer based on the serviced request in the accounting store;
and (iv) generating an invoice to the intermediary computer based on the updated accounting data associated with the intermediary computer from the accounting store.
83. The system of claim 82, wherein the host computer processor performs the additional step of delivering the generated invoice to a selected destination.
84. The system of claim 21, wherein the host computer processor performs the additional step of debiting an account associated with the intermediary computer.
85. A method for automated access to personal information associated with an end user, wherein the personal information is stored on a personal information provider, the method comprising the steps of:
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, downloading an application to the client computer, wherein the downloaded application upon execution on the client computer performs the steps of:
(i) connecting to the personal information provider;
(ii) navigating to the personal information on the personal information provider; and (iii) presenting the personal information to the user of the client computer.
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, downloading an application to the client computer, wherein the downloaded application upon execution on the client computer performs the steps of:
(i) connecting to the personal information provider;
(ii) navigating to the personal information on the personal information provider; and (iii) presenting the personal information to the user of the client computer.
86. The method of claim 85, and further comprising the steps of:
(a) transmitting end user data associated with the end user to the client computer; and (b) transmitting personal information provider data associated with the personal information provider to the client computer.
(a) transmitting end user data associated with the end user to the client computer; and (b) transmitting personal information provider data associated with the personal information provider to the client computer.
87. The method of claim 86, wherein the step of transmitting personal information provider data associated with the personal information provider comprises transmitting a navigation script corresponding to the personal information.
88. The method of claim 87, wherein the step of transmitting end user data associated with the end user comprises transmitting end user data associated with the end user based on the transmitted navigation script.
89. The method of claim 85, and further comprising the step of generating an application for downloading to the client computer based on personal information provider data associated with the personal information provider, on the personal information and on end user data associated with the end user.
90. A method for automated access to personal information associated with an end user, wherein the personal information is stored on a personal information provider, the method comprising the steps of:
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, transmitting a page containing a form which includes login information that upon opening by the client computer redirects the client computer to a post login page on the personal information provider.
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, transmitting a page containing a form which includes login information that upon opening by the client computer redirects the client computer to a post login page on the personal information provider.
91. A method for automated access to personal information associated with an end user, wherein the personal information is stored on a personal information provider, the method comprising the steps of:
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, driving the client computer to the personal information stored on the personal information provider by performing the steps of:
(i) connecting to the personal information provider;
(ii) navigating to the personal information on the personal information provider;
(iii) presenting the personal information to the user of the client computer; and (iv) proxying subsequent requests from the client computer to the personal information provider.
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, driving the client computer to the personal information stored on the personal information provider by performing the steps of:
(i) connecting to the personal information provider;
(ii) navigating to the personal information on the personal information provider;
(iii) presenting the personal information to the user of the client computer; and (iv) proxying subsequent requests from the client computer to the personal information provider.
92. A computer-readable storage device storing instruction that upon execution cause a processor to automatically access personal information associated with an end user, wherein the personal information is stored on a personal information provider, by performing the steps comprising of:
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, downloading an application to the client computer, wherein the downloaded application upon execution on the client computer performs the steps of:
(i) connecting to the personal information provider;
(ii) navigating to the personal information on the personal information provider; and (iii) presenting the personal information to the user of the client computer.
(a) presenting on a client computer associated with the end user a representation of personal information and a link corresponding to the personal information stored on the personal information provider;
(b) upon activation of the presented link, downloading an application to the client computer, wherein the downloaded application upon execution on the client computer performs the steps of:
(i) connecting to the personal information provider;
(ii) navigating to the personal information on the personal information provider; and (iii) presenting the personal information to the user of the client computer.
93. A system for automated access to personal information associated with an end user, wherein the personal information is stored on a personal information provider, the system comprising:
(a) a user store for storing data associated with the end user;
(b) a personal information provider store for storing data associated with the personal information provider; and (c) a processor in communication with the user store and the personal information provider store, the processor for performing the steps of:
(i) presenting on a client computer associated with the end user a representation of personal information and a Link corresponding to the personal information stored on the personal information provider;
(ii) upon activation of the presented link, downloading an application to the client computer, wherein the downloaded application upon execution on the client computer performs the steps of:
(A) connecting to the personal information provider;
(B) navigating to the personal information on the personal information provider; and (C) presenting the personal information to the user of the client computer.
(a) a user store for storing data associated with the end user;
(b) a personal information provider store for storing data associated with the personal information provider; and (c) a processor in communication with the user store and the personal information provider store, the processor for performing the steps of:
(i) presenting on a client computer associated with the end user a representation of personal information and a Link corresponding to the personal information stored on the personal information provider;
(ii) upon activation of the presented link, downloading an application to the client computer, wherein the downloaded application upon execution on the client computer performs the steps of:
(A) connecting to the personal information provider;
(B) navigating to the personal information on the personal information provider; and (C) presenting the personal information to the user of the client computer.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA002308242A CA2308242A1 (en) | 1998-10-28 | 1999-10-27 | Apparatus and method for automated aggregation and delivery of and transactions involving electronic personal information or data |
CA002308246A CA2308246A1 (en) | 1998-10-28 | 1999-10-27 | System and method for automated access to personal information |
Applications Claiming Priority (5)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10591798P | 1998-10-28 | 1998-10-28 | |
US60/105,917 | 1998-10-28 | ||
US13439599P | 1999-05-17 | 1999-05-17 | |
US60/134,395 | 1999-05-17 | ||
PCT/US1999/025181 WO2000025227A1 (en) | 1998-10-28 | 1999-10-27 | Apparatus and method for automated aggregation and delivery of electronic personal information or data |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002308246A Division CA2308246A1 (en) | 1998-10-28 | 1999-10-27 | System and method for automated access to personal information |
CA002308242A Division CA2308242A1 (en) | 1998-10-28 | 1999-10-27 | Apparatus and method for automated aggregation and delivery of and transactions involving electronic personal information or data |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2306083A1 true CA2306083A1 (en) | 2000-05-04 |
Family
ID=26803095
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002306083A Abandoned CA2306083A1 (en) | 1998-10-28 | 1999-10-27 | Apparatus and method for automated aggregation and delivery of electronic personal information or data |
Country Status (11)
Country | Link |
---|---|
US (5) | US6317783B1 (en) |
EP (1) | EP1198765B1 (en) |
JP (2) | JP2002528819A (en) |
CN (3) | CN1497465A (en) |
AT (3) | ATE268484T1 (en) |
AU (1) | AU737572C (en) |
BR (1) | BR9907075A (en) |
CA (1) | CA2306083A1 (en) |
DE (3) | DE69908610T2 (en) |
ES (1) | ES2200753T3 (en) |
WO (1) | WO2000025227A1 (en) |
Families Citing this family (382)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1997014108A1 (en) * | 1995-10-11 | 1997-04-17 | Block Financial Corporation | Financial information access system |
US5706442A (en) * | 1995-12-20 | 1998-01-06 | Block Financial Corporation | System for on-line financial services using distributed objects |
US6181694B1 (en) | 1998-04-03 | 2001-01-30 | Vertical Networks, Inc. | Systems and methods for multiple mode voice and data communciations using intelligently bridged TDM and packet buses |
US6389009B1 (en) | 2000-12-28 | 2002-05-14 | Vertical Networks, Inc. | Systems and methods for multiple mode voice and data communications using intelligently bridged TDM and packet buses |
US7072330B2 (en) | 1998-04-03 | 2006-07-04 | Consolidated Ip Holdings, Inc. | Systems for voice and data communications having TDM and packet buses and telephony station cards including voltage generators |
JP3142821B2 (en) * | 1998-08-27 | 2001-03-07 | 株式会社エヌ・ティ・ティ・ドコモ | Information communication network billing method |
JP3142820B2 (en) | 1998-08-27 | 2001-03-07 | 株式会社エヌ・ティ・ティ・ドコモ | Push type information distribution method and its relay device |
US6374231B1 (en) | 1998-10-21 | 2002-04-16 | Bruce Bent | Money fund banking system |
US7536350B1 (en) | 1998-10-21 | 2009-05-19 | Island Intellectual Property Llc | Systems and methods for providing enhanced account management services for multiple banks |
US7668772B1 (en) | 1998-10-21 | 2010-02-23 | Island Intellectual Property Llc | Systems and methods for money fund banking with flexible interest allocation |
US7752129B2 (en) | 1998-10-21 | 2010-07-06 | Island Intellectual Property Llc | Systems and methods for managing client accounts |
US7680734B1 (en) | 1998-10-21 | 2010-03-16 | Island Intellectual Property Llc | Money fund banking system |
US6871220B1 (en) * | 1998-10-28 | 2005-03-22 | Yodlee, Inc. | System and method for distributed storage and retrieval of personal information |
ATE268484T1 (en) | 1998-10-28 | 2004-06-15 | Verticalone Corp | SYSTEM AND METHOD FOR AUTOMATIC ACCESS TO PERSONAL DATA |
US20080091663A1 (en) * | 1998-12-08 | 2008-04-17 | Inala Suman K | Software Bundle for Providing Automated Functionality to a WEB-Browser |
US7085997B1 (en) * | 1998-12-08 | 2006-08-01 | Yodlee.Com | Network-based bookmark management and web-summary system |
US8069407B1 (en) | 1998-12-08 | 2011-11-29 | Yodlee.Com, Inc. | Method and apparatus for detecting changes in websites and reporting results to web developers for navigation template repair purposes |
US8266266B2 (en) | 1998-12-08 | 2012-09-11 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization, authentication and accounting |
US7937325B2 (en) * | 1998-12-08 | 2011-05-03 | Yodlee.Com, Inc. | Interactive bill payment center |
US7672879B1 (en) | 1998-12-08 | 2010-03-02 | Yodlee.Com, Inc. | Interactive activity interface for managing personal data and performing transactions over a data packet network |
JP3833409B2 (en) * | 1999-02-05 | 2006-10-11 | 株式会社日立製作所 | Communication proxy device |
US6507857B1 (en) * | 1999-03-12 | 2003-01-14 | Sun Microsystems, Inc. | Extending the capabilities of an XSL style sheet to include components for content transformation |
US6826597B1 (en) * | 1999-03-17 | 2004-11-30 | Oracle International Corporation | Providing clients with services that retrieve data from data sources that do not necessarily support the format required by the clients |
US6643779B1 (en) * | 1999-04-15 | 2003-11-04 | Brian Leung | Security system with embedded HTTP server |
US6847969B1 (en) * | 1999-05-03 | 2005-01-25 | Streetspace, Inc. | Method and system for providing personalized online services and advertisements in public spaces |
US7366682B1 (en) * | 1999-05-07 | 2008-04-29 | E.Piphany, Inc. | System, method, and code for providing promotions in a network environment |
US6615234B1 (en) * | 1999-05-11 | 2003-09-02 | Taylor Corporation | System and method for network-based document delivery |
US6668271B1 (en) * | 1999-05-19 | 2003-12-23 | Richo Company, Ltd. | System for distributing, installing and running web applications (agents) |
US9262384B2 (en) | 1999-05-21 | 2016-02-16 | E-Numerate Solutions, Inc. | Markup language system, method, and computer program product |
US7650355B1 (en) | 1999-05-21 | 2010-01-19 | E-Numerate Solutions, Inc. | Reusable macro markup language |
US7249328B1 (en) * | 1999-05-21 | 2007-07-24 | E-Numerate Solutions, Inc. | Tree view for reusable data markup language |
US9262383B2 (en) | 1999-05-21 | 2016-02-16 | E-Numerate Solutions, Inc. | System, method, and computer program product for processing a markup document |
US9268748B2 (en) | 1999-05-21 | 2016-02-23 | E-Numerate Solutions, Inc. | System, method, and computer program product for outputting markup language documents |
US6477565B1 (en) * | 1999-06-01 | 2002-11-05 | Yodlee.Com, Inc. | Method and apparatus for restructuring of personalized data for transmission from a data network to connected and portable network appliances |
US7752535B2 (en) | 1999-06-01 | 2010-07-06 | Yodlec.com, Inc. | Categorization of summarized information |
US6526438B1 (en) * | 1999-07-12 | 2003-02-25 | Divine, Inc. | Method for distributing information to subscribers over a network |
US7039863B1 (en) | 1999-07-23 | 2006-05-02 | Adobe Systems Incorporated | Computer generation of documents using layout elements and content elements |
US7222293B1 (en) * | 1999-08-12 | 2007-05-22 | Applieoe, Inc. | Professional time tracking and reporting system |
US20020174201A1 (en) * | 1999-09-30 | 2002-11-21 | Ramer Jon E. | Dynamic configuration of context-sensitive personal sites and membership channels |
US8463231B1 (en) * | 1999-11-02 | 2013-06-11 | Nvidia Corporation | Use of radius in UMTS to perform accounting functions |
US6865169B1 (en) | 1999-11-02 | 2005-03-08 | Ipwireless, Inc. | Cellular wireless internet access system using spread spectrum and internet protocol |
US6876991B1 (en) | 1999-11-08 | 2005-04-05 | Collaborative Decision Platforms, Llc. | System, method and computer program product for a collaborative decision platform |
US6981040B1 (en) * | 1999-12-28 | 2005-12-27 | Utopy, Inc. | Automatic, personalized online information and product services |
US6691104B1 (en) * | 2000-01-12 | 2004-02-10 | International Business Machines Corporation | System and method for personalizing and applying a post processing tool system |
US8620286B2 (en) | 2004-02-27 | 2013-12-31 | Synchronoss Technologies, Inc. | Method and system for promoting and transferring licensed content and applications |
US6671757B1 (en) | 2000-01-26 | 2003-12-30 | Fusionone, Inc. | Data transfer and synchronization system |
US8156074B1 (en) | 2000-01-26 | 2012-04-10 | Synchronoss Technologies, Inc. | Data transfer and synchronization system |
US6591260B1 (en) * | 2000-01-28 | 2003-07-08 | Commerce One Operations, Inc. | Method of retrieving schemas for interpreting documents in an electronic commerce system |
US6665090B1 (en) * | 2000-03-13 | 2003-12-16 | Hewlett-Packard Development Company, L.P. | System and method for creating and printing a creative expression |
JP2001282730A (en) * | 2000-03-30 | 2001-10-12 | Sony Corp | Information processor, server connecting method, program storage medium, and network connection system |
US20030154171A1 (en) * | 2000-03-31 | 2003-08-14 | Hewlett Packard Company | Apparatus and method for selling personal information |
US20010037405A1 (en) * | 2000-04-07 | 2001-11-01 | Sideek Sinnathambi Mohamed | Wireless web generation from conventional web sites by pattern identification and dynamic content extraction |
US6801936B1 (en) * | 2000-04-07 | 2004-10-05 | Arif Diwan | Systems and methods for generating customized bundles of information |
US7725523B2 (en) * | 2000-04-11 | 2010-05-25 | Bolnick David A | System, method and computer program product for gathering and delivering personalized user information |
AU2001245744A1 (en) * | 2000-04-14 | 2001-10-30 | Yodlee.Com, Inc. | Method and apparatus for providing auto-registration and service access to internet sites for internet portal subscribers |
US7540021B2 (en) * | 2000-04-24 | 2009-05-26 | Justin Page | System and methods for an identity theft protection bot |
US8005755B2 (en) * | 2000-04-25 | 2011-08-23 | Yodlee.Com, Inc. | System and method for syndicated transactions |
US8244635B2 (en) * | 2000-04-25 | 2012-08-14 | Yodlee.Com, Inc. | System and method for syndicated collection, aggregation and delivery of personal data |
JP4037999B2 (en) * | 2000-05-15 | 2008-01-23 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Website, robot type search engine response system, robot type search engine registration method, storage medium, and program transmission device |
US8086697B2 (en) | 2005-06-28 | 2011-12-27 | Claria Innovations, Llc | Techniques for displaying impressions in documents delivered over a computer network |
US7475404B2 (en) | 2000-05-18 | 2009-01-06 | Maquis Techtrix Llc | System and method for implementing click-through for browser executed software including ad proxy and proxy cookie caching |
US6725268B1 (en) * | 2000-08-11 | 2004-04-20 | At&T Corp. | System and method for providing status information from multiple information sources in a single display |
US7376740B1 (en) * | 2000-06-13 | 2008-05-20 | Microsoft Corporation | Phone application state management mechanism |
US20020054080A1 (en) * | 2000-06-15 | 2002-05-09 | Belanger David Gerald | Internet service controller with real time status display |
US7370011B2 (en) * | 2000-06-28 | 2008-05-06 | Yahoo! Inc. | Financial information portal |
US7640200B2 (en) * | 2000-07-10 | 2009-12-29 | Byallaccounts, Inc. | Financial portfolio management system and method |
US7660737B1 (en) * | 2000-07-18 | 2010-02-09 | Smartpenny.Com, Inc. | Economic filtering system for delivery of permission based, targeted, incentivized advertising |
US7895334B1 (en) | 2000-07-19 | 2011-02-22 | Fusionone, Inc. | Remote access communication architecture apparatus and method |
US8073954B1 (en) | 2000-07-19 | 2011-12-06 | Synchronoss Technologies, Inc. | Method and apparatus for a secure remote access system |
US7013310B2 (en) * | 2002-01-03 | 2006-03-14 | Cashedge, Inc. | Method and apparatus for retrieving and processing data |
US8086508B2 (en) | 2000-07-24 | 2011-12-27 | Cashedge, Inc. | Method and apparatus for delegating authority |
US7797207B1 (en) | 2000-07-24 | 2010-09-14 | Cashedge, Inc. | Method and apparatus for analyzing financial data |
US7536340B2 (en) | 2000-07-24 | 2009-05-19 | Cashedge, Inc. | Compliance monitoring method and apparatus |
US7146338B2 (en) * | 2001-06-28 | 2006-12-05 | Checkfree Services Corporation | Inter-network financial service |
US7117239B1 (en) | 2000-07-28 | 2006-10-03 | Axeda Corporation | Reporting the state of an apparatus to a remote computer |
US6757714B1 (en) * | 2000-07-28 | 2004-06-29 | Axeda Systems Operating Company, Inc. | Reporting the state of an apparatus to a remote computer |
US20070214075A1 (en) * | 2000-08-23 | 2007-09-13 | Ablan Gerald H | Auction management system |
JP3745207B2 (en) * | 2000-08-23 | 2006-02-15 | キヤノン株式会社 | Network print system, information processing apparatus and control method therefor |
US6745011B1 (en) | 2000-09-01 | 2004-06-01 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
US6754470B2 (en) * | 2000-09-01 | 2004-06-22 | Telephia, Inc. | System and method for measuring wireless device and network usage and performance metrics |
JP2002083148A (en) * | 2000-09-06 | 2002-03-22 | Seiko Epson Corp | Browsing information forming system and digital contents delivery system |
JP2002092324A (en) * | 2000-09-14 | 2002-03-29 | Nisshin Business Development Co Ltd | Property information managing method and storage medium |
US20030236728A1 (en) * | 2000-09-20 | 2003-12-25 | Amir Sunderji | Method and apparatus for managing a financial transaction system |
US7383223B1 (en) | 2000-09-20 | 2008-06-03 | Cashedge, Inc. | Method and apparatus for managing multiple accounts |
US20080015982A1 (en) * | 2000-09-20 | 2008-01-17 | Jeremy Sokolic | Funds transfer method and system including payment enabled invoices |
US7185014B1 (en) | 2000-09-22 | 2007-02-27 | Axeda Corporation | Retrieving data from a server |
US8108543B2 (en) | 2000-09-22 | 2012-01-31 | Axeda Corporation | Retrieving data from a server |
US7373382B2 (en) * | 2000-10-03 | 2008-05-13 | Sharp Kabushiki Kaisha | Electronic apparatus, information communications apparatus, management system for same electronic apparatus, and management method for same electronic apparatus |
US6868070B1 (en) | 2000-10-06 | 2005-03-15 | Vertical Networks, Inc. | Systems and methods for providing voice/data communication systems and voice/data communications |
AUPR066300A0 (en) * | 2000-10-09 | 2000-11-02 | A & Mt Projects Pty Limited | The use of wireless application protocol for making trading decisions and executing transactions in real time |
US20020073149A1 (en) * | 2000-10-11 | 2002-06-13 | Young Christopher Tyler | Dynamic content linking |
US7254619B2 (en) * | 2000-10-13 | 2007-08-07 | Matsushita Electric Industrial Co., Ltd. | Apparatus for outputting individual authentication information connectable to a plurality of terminals through a network |
US6651060B1 (en) * | 2000-11-01 | 2003-11-18 | Mediconnect.Net, Inc. | Methods and systems for retrieval and digitization of records |
US6629103B1 (en) * | 2000-11-02 | 2003-09-30 | Oridus, Inc. | Method for securely providing a text file for execution |
US7587446B1 (en) * | 2000-11-10 | 2009-09-08 | Fusionone, Inc. | Acquisition and synchronization of digital media to a personal information space |
US20020059397A1 (en) * | 2000-11-13 | 2002-05-16 | The Belo Company, | Content operating system |
WO2002042952A1 (en) * | 2000-11-27 | 2002-05-30 | Commonwealth Bank Of Australia | Aggregation service |
US7325067B1 (en) * | 2000-11-27 | 2008-01-29 | Esaya, Inc. | Personalized account migration system and method |
SE0004476L (en) * | 2000-12-05 | 2002-06-06 | Creative Media Design At Integ | Device and system |
US6957198B2 (en) * | 2000-12-07 | 2005-10-18 | International Business Machines Corporation | Use of persona object in electronic transactions |
US7818435B1 (en) | 2000-12-14 | 2010-10-19 | Fusionone, Inc. | Reverse proxy mechanism for retrieving electronic content associated with a local network |
US7051070B2 (en) * | 2000-12-18 | 2006-05-23 | Timothy Tuttle | Asynchronous messaging using a node specialization architecture in the dynamic routing network |
US8505024B2 (en) | 2000-12-18 | 2013-08-06 | Shaw Parsing Llc | Storing state in a dynamic content routing network |
WO2002050691A1 (en) * | 2000-12-19 | 2002-06-27 | Mediagate, Inc. | Software architecture for interaction with dynamic data sources and role based access control |
US7415607B2 (en) | 2000-12-22 | 2008-08-19 | Oracle International Corporation | Obtaining and maintaining real time certificate status |
US7380008B2 (en) | 2000-12-22 | 2008-05-27 | Oracle International Corporation | Proxy system |
US7581011B2 (en) | 2000-12-22 | 2009-08-25 | Oracle International Corporation | Template based workflow definition |
US8015600B2 (en) | 2000-12-22 | 2011-09-06 | Oracle International Corporation | Employing electronic certificate workflows |
US7349912B2 (en) | 2000-12-22 | 2008-03-25 | Oracle International Corporation | Runtime modification of entries in an identity system |
US6816871B2 (en) * | 2000-12-22 | 2004-11-09 | Oblix, Inc. | Delivering output XML with dynamically selectable processing |
US7711818B2 (en) | 2000-12-22 | 2010-05-04 | Oracle International Corporation | Support for multiple data stores |
US7213249B2 (en) | 2000-12-22 | 2007-05-01 | Oracle International Corporation | Blocking cache flush requests until completing current pending requests in a local server and remote server |
US7937655B2 (en) | 2000-12-22 | 2011-05-03 | Oracle International Corporation | Workflows with associated processes |
US7085834B2 (en) | 2000-12-22 | 2006-08-01 | Oracle International Corporation | Determining a user's groups |
US7475151B2 (en) | 2000-12-22 | 2009-01-06 | Oracle International Corporation | Policies for modifying group membership |
US6782379B2 (en) * | 2000-12-22 | 2004-08-24 | Oblix, Inc. | Preparing output XML based on selected programs and XML templates |
US7363339B2 (en) | 2000-12-22 | 2008-04-22 | Oracle International Corporation | Determining group membership |
US7802174B2 (en) | 2000-12-22 | 2010-09-21 | Oracle International Corporation | Domain based workflows |
US20020087621A1 (en) * | 2000-12-29 | 2002-07-04 | Hendriks Chris L. | Method and system to manage internet user navigation data |
US9600842B2 (en) | 2001-01-24 | 2017-03-21 | E-Numerate Solutions, Inc. | RDX enhancement of system and method for implementing reusable data markup language (RDL) |
JP4166437B2 (en) * | 2001-01-31 | 2008-10-15 | 株式会社日立製作所 | Authenticity output method, apparatus for implementing the method, and processing program therefor |
US20030041065A1 (en) * | 2001-03-14 | 2003-02-27 | Mark Lucovsky | Schema-based services for identity-based access to contacts data |
US20030061365A1 (en) * | 2001-03-14 | 2003-03-27 | Microsoft Corporation | Service-to-service communication for network services |
US20030069887A1 (en) * | 2001-03-14 | 2003-04-10 | Lucovsky Mark H. | Schema-based services for identity-based access to inbox data |
US7302634B2 (en) * | 2001-03-14 | 2007-11-27 | Microsoft Corporation | Schema-based services for identity-based data access |
US7024662B2 (en) | 2001-03-14 | 2006-04-04 | Microsoft Corporation | Executing dynamically assigned functions while providing services |
US20020133706A1 (en) * | 2001-03-19 | 2002-09-19 | Alok Khanna | Login for online account aggregation |
US20020133604A1 (en) * | 2001-03-19 | 2002-09-19 | Alok Khanna | Instruction set file generation for online account aggregation |
WO2002075555A1 (en) * | 2001-03-19 | 2002-09-26 | Adhesion Technologies, Inc. | Login for online account aggregation |
US20020133605A1 (en) * | 2001-03-19 | 2002-09-19 | Alok Khanna | Generation and use of rules for reading of data for online account aggregation |
US8615566B1 (en) | 2001-03-23 | 2013-12-24 | Synchronoss Technologies, Inc. | Apparatus and method for operational support of remote network systems |
US20020143812A1 (en) * | 2001-03-27 | 2002-10-03 | Bedingfield James C. | System and method of automatically updating content on a web site |
US8990678B2 (en) * | 2001-03-27 | 2015-03-24 | At&T Intellectual Property I, L.P. | Systems and methods for automatically providing alerts of web site content updates |
DE10120173B4 (en) * | 2001-04-24 | 2006-02-23 | Gebr. Pöttinger GmbH | Method and device for operating agricultural machines |
US20030014336A1 (en) * | 2001-05-04 | 2003-01-16 | Fu-Tak Dao | Analytically determining revenue of internet companies using internet metrics |
ES2372636T3 (en) * | 2001-05-09 | 2012-01-25 | 2011 Intellectual Property Asset Trust | INDICATION TO A FINAL USER TEAM THAT YOU MUST REGISTER. |
US20060064666A1 (en) | 2001-05-25 | 2006-03-23 | Amaru Ruth M | Business rules for configurable metamodels and enterprise impact analysis |
US7146399B2 (en) * | 2001-05-25 | 2006-12-05 | 2006 Trident Company | Run-time architecture for enterprise integration with transformation generation |
US8412746B2 (en) * | 2001-05-25 | 2013-04-02 | International Business Machines Corporation | Method and system for federated querying of data sources |
JP2002366753A (en) * | 2001-06-06 | 2002-12-20 | Scale:Kk | Financial management system |
US20020194226A1 (en) * | 2001-06-15 | 2002-12-19 | Dinesh Sheth | Internet information aggregation system using programmatic data extraction |
US7181500B2 (en) * | 2001-06-18 | 2007-02-20 | Microsoft Corporation | System and method for utilizing personal information to customize an application program |
US7571166B1 (en) * | 2001-06-19 | 2009-08-04 | Click Acquisitions, Inc. | Virtual private supply chain |
US7181488B2 (en) * | 2001-06-29 | 2007-02-20 | Claria Corporation | System, method and computer program product for presenting information to a user utilizing historical information about the user |
US20030018915A1 (en) * | 2001-07-19 | 2003-01-23 | Louis Stoll | Method and system for user authentication and authorization of services |
JP4604422B2 (en) | 2001-07-31 | 2011-01-05 | ソニー株式会社 | COMMUNICATION SYSTEM, COMMUNICATION DEVICE, AND COMMUNICATION METHOD |
US20030028427A1 (en) * | 2001-08-02 | 2003-02-06 | International Business Machines Corporation | User control of electronic personal information while browsing the Web |
US20030036462A1 (en) * | 2001-08-20 | 2003-02-20 | Sundaram Ravikumar | Powered antithrombotic foot mobility device |
US20030037139A1 (en) * | 2001-08-20 | 2003-02-20 | Koninklijke Philips Electronics N.V. | Content distribution model |
US20030044012A1 (en) * | 2001-08-31 | 2003-03-06 | Sharp Laboratories Of America, Inc. | System and method for using a profile to encrypt documents in a digital scanner |
US20030051215A1 (en) * | 2001-09-11 | 2003-03-13 | Muneki Nakao | Communication apparatus, method of controlling same, and control program |
US7191216B2 (en) * | 2001-10-03 | 2007-03-13 | Nokia Corporation | System and method for controlling access to downloadable resources |
US20030074209A1 (en) * | 2001-10-15 | 2003-04-17 | Tobin Christopher M. | User device with service finding and purchasing functionality |
US7917394B2 (en) * | 2001-11-19 | 2011-03-29 | Csg Systems, Inc. | System and method for providing access to network services |
US7225256B2 (en) | 2001-11-30 | 2007-05-29 | Oracle International Corporation | Impersonation in an access system |
US20030120660A1 (en) * | 2001-12-07 | 2003-06-26 | Maritzen L. Michael | Consumer-centric context-aware switching model |
US7254601B2 (en) | 2001-12-20 | 2007-08-07 | Questra Corporation | Method and apparatus for managing intelligent assets in a distributed environment |
US20040236653A1 (en) * | 2002-01-03 | 2004-11-25 | Sokolic Jeremy N. | System and method for associating identifiers with data |
US20050187867A1 (en) * | 2002-01-03 | 2005-08-25 | Sokolic Jeremy N. | System and method for associating identifiers with transactions |
US7203845B2 (en) * | 2002-01-11 | 2007-04-10 | Cashedge, Inc. | Multiple trust modes for handling data |
US20030144944A1 (en) * | 2002-01-31 | 2003-07-31 | Kalt David Samuels | Financial instruments trading system and method |
US7890393B2 (en) | 2002-02-07 | 2011-02-15 | Ebay, Inc. | Method and system for completing a transaction between a customer and a merchant |
AU2003213621A1 (en) * | 2002-03-01 | 2003-09-16 | Tralix, L.L.C. | Method and system of sending and tracking electronic mail messages |
US7461262B1 (en) | 2002-03-19 | 2008-12-02 | Cisco Technology, Inc. | Methods and apparatus for providing security in a caching device |
AU2002244775A1 (en) * | 2002-03-28 | 2003-10-13 | Nokia Corporation | Providing personalized services for mobile users |
US20030191669A1 (en) * | 2002-04-09 | 2003-10-09 | Fitzgerald David | System for providing consumer access to healthcare related information |
US7797172B2 (en) * | 2002-04-16 | 2010-09-14 | Siemens Medical Solutions Usa, Inc. | Healthcare financial data and clinical information processing system |
US7178149B2 (en) | 2002-04-17 | 2007-02-13 | Axeda Corporation | XML scripting of soap commands |
EP1504393A4 (en) | 2002-04-23 | 2008-03-19 | Clearing House Service Company | Payment identification code and payment system using the same |
US6820078B2 (en) * | 2002-05-09 | 2004-11-16 | Kevin Nip | Method and system for the automated collection and display of database information via a communications network |
US7840658B2 (en) | 2002-05-15 | 2010-11-23 | Oracle International Corporation | Employing job code attributes in provisioning |
US7216163B2 (en) | 2002-05-15 | 2007-05-08 | Oracle International Corporation | Method and apparatus for provisioning tasks using a provisioning bridge server |
AU2003248568A1 (en) * | 2002-05-22 | 2003-12-12 | Commnav, Inc. | Method and system for multiple virtual portals |
US7367059B2 (en) * | 2002-05-30 | 2008-04-29 | Nokia Corporation | Secure content activation during manufacture of mobile communication devices |
US20040078228A1 (en) * | 2002-05-31 | 2004-04-22 | Fitzgerald David | System for monitoring healthcare patient encounter related information |
JP3907184B2 (en) * | 2002-06-17 | 2007-04-18 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Database search system and data sharing system |
US20040006564A1 (en) * | 2002-06-28 | 2004-01-08 | Lucovsky Mark H. | Schema-based service for identity-based data access to category data |
US9886309B2 (en) | 2002-06-28 | 2018-02-06 | Microsoft Technology Licensing, Llc | Identity-based distributed computing for device resources |
US7706359B2 (en) | 2002-07-01 | 2010-04-27 | Converged Data Solutions, Inc. | Systems and methods for voice and data communications including a network drop and insert interface for an external data routing resource |
US7869424B2 (en) | 2002-07-01 | 2011-01-11 | Converged Data Solutions Inc. | Systems and methods for voice and data communications including a scalable TDM switch/multiplexer |
US7797403B2 (en) * | 2002-07-12 | 2010-09-14 | Microsoft Corporation | Deployment of configuration information |
JP3586269B2 (en) * | 2002-07-16 | 2004-11-10 | 株式会社コナミオンライン | Network service system and point transfer system |
US7206788B2 (en) * | 2002-07-30 | 2007-04-17 | Microsoft Corporation | Schema-based services for identity-based access to device data |
US6876979B2 (en) * | 2002-08-12 | 2005-04-05 | Paybyclick Corporation | Electronic commerce bridge system |
US20040039601A1 (en) * | 2002-08-23 | 2004-02-26 | Anderson Corey D. | Virtual file cabinet including health information method and apparatus |
US7603341B2 (en) | 2002-11-05 | 2009-10-13 | Claria Corporation | Updating the content of a presentation vehicle in a computer network |
US20040128534A1 (en) * | 2002-12-18 | 2004-07-01 | Walker Nicholas John | Method and product for identifying a website visitor session by visitor e-mail address |
US20040143649A1 (en) * | 2003-01-21 | 2004-07-22 | An Feng | Multiple dynamic view enabled web services |
US8150766B1 (en) | 2003-01-27 | 2012-04-03 | Island Intellectual Property Llc | System and method for investing public deposits |
US7966418B2 (en) | 2003-02-21 | 2011-06-21 | Axeda Corporation | Establishing a virtual tunnel between two computer programs |
US20080147813A1 (en) * | 2003-02-28 | 2008-06-19 | Tralix, L.L.C. | Systems and methods for electronic mail message server component |
US7146563B2 (en) * | 2003-05-29 | 2006-12-05 | International Business Machines Corporation | Maintaining screen and form state in portlets |
AU2003903229A0 (en) * | 2003-06-25 | 2003-07-10 | Ewise Systems Pty Ltd | A system and method for facilitating on-line payment |
EP1652048A4 (en) | 2003-07-21 | 2009-04-15 | Fusionone Inc | Device message management system |
US7340447B2 (en) | 2003-10-09 | 2008-03-04 | Oracle International Corporation | Partitioning data access requests |
US7882132B2 (en) | 2003-10-09 | 2011-02-01 | Oracle International Corporation | Support for RDBMS in LDAP system |
US7904487B2 (en) | 2003-10-09 | 2011-03-08 | Oracle International Corporation | Translating data access requests |
US8170912B2 (en) | 2003-11-25 | 2012-05-01 | Carhamm Ltd., Llc | Database structure and front end |
US8725607B2 (en) | 2004-01-30 | 2014-05-13 | The Clearing House Payments Company LLC | Electronic payment clearing and check image exchange systems and methods |
CA2557132C (en) * | 2004-02-23 | 2014-05-20 | I4 Licensing Llc | Computer-implemented method, system and apparatus for the dynamic verification of a consumer engaged in a transaction with a merchant and authorization of the transaction |
US9542076B1 (en) | 2004-05-12 | 2017-01-10 | Synchronoss Technologies, Inc. | System for and method of updating a personal profile |
CN1998224A (en) | 2004-05-12 | 2007-07-11 | 富盛旺公司 | Advanced contact identification system |
WO2006009879A2 (en) | 2004-06-18 | 2006-01-26 | Washington Mutual, Inc. | System for automatically transferring account information, such as information regarding a financial servicees account |
EP1789875A1 (en) * | 2004-08-17 | 2007-05-30 | Shaw Parsing LLC | Modular event-driven processing |
WO2006023508A1 (en) * | 2004-08-17 | 2006-03-02 | Shaw Parsing Llc | Techniques for upstream failure detection and failure recovery |
JP5162240B2 (en) * | 2004-08-17 | 2013-03-13 | ショー パーシング リミティド ライアビリティ カンパニー | A technique for distributing individual contents via a real-time distribution network |
US8255413B2 (en) | 2004-08-19 | 2012-08-28 | Carhamm Ltd., Llc | Method and apparatus for responding to request for information-personalization |
US8078602B2 (en) | 2004-12-17 | 2011-12-13 | Claria Innovations, Llc | Search engine for a computer network |
US8732004B1 (en) | 2004-09-22 | 2014-05-20 | Experian Information Solutions, Inc. | Automated analysis of data to generate prospect notifications based on trigger events |
CA2582271A1 (en) * | 2004-09-30 | 2006-04-13 | Optionsxpress Holdings,Inc. | System and methods for prioritized management of financial instruments |
JP2006154262A (en) * | 2004-11-29 | 2006-06-15 | Kyocera Corp | Portable terminal, and method for controlling the same, and program |
US20110238592A1 (en) * | 2004-12-20 | 2011-09-29 | Mccutcheon Timothy M | Method of and System for Preparing an Employee Benefits Plan |
US7693863B2 (en) | 2004-12-20 | 2010-04-06 | Claria Corporation | Method and device for publishing cross-network user behavioral data |
US8001040B2 (en) | 2005-01-25 | 2011-08-16 | Ebay Inc. | Computer-implemented method and system for dynamic consumer rating in a transaction |
US20060195398A1 (en) * | 2005-02-04 | 2006-08-31 | Sanjeev Dheer | Method and apparatus for processing payment requests |
US8645941B2 (en) | 2005-03-07 | 2014-02-04 | Carhamm Ltd., Llc | Method for attributing and allocating revenue related to embedded software |
US8073866B2 (en) | 2005-03-17 | 2011-12-06 | Claria Innovations, Llc | Method for providing content to an internet user based on the user's demonstrated content preferences |
US7527195B2 (en) * | 2005-04-11 | 2009-05-05 | Bill Me Later, Inc. | Method and system for risk management in a transaction |
US8756099B2 (en) * | 2005-04-11 | 2014-06-17 | Bill Me Later, Inc. | Consumer processing system and method |
US7881283B2 (en) * | 2005-07-13 | 2011-02-01 | Research In Motion Limited | Customizability of event notification on telephony-enabled devices |
US7546290B2 (en) * | 2005-08-11 | 2009-06-09 | Marc Colando | Systems and methods for extracting and adapting data |
US7529236B2 (en) * | 2005-08-15 | 2009-05-05 | Technocom Corporation | Embedded wireless location validation benchmarking systems and methods |
US7738864B2 (en) | 2005-08-15 | 2010-06-15 | At&T Mobility Ii Llc | Embedded wireless benchmarking systems and methods |
US20070067239A1 (en) * | 2005-09-19 | 2007-03-22 | Cashedge, Inc. | Method and Apparatus for Transferring Financial Information |
WO2007044364A2 (en) * | 2005-10-05 | 2007-04-19 | Optionsxpress Holdings, Inc. | System and methods for facilitating informed trading of financial instruments |
US8611856B2 (en) * | 2005-10-18 | 2013-12-17 | Google Inc. | Identifying spurious requests for information |
US20070100748A1 (en) * | 2005-10-19 | 2007-05-03 | Sanjeev Dheer | Multi-channel transaction system for transferring assets between accounts at different financial institutions |
US8230481B2 (en) * | 2005-11-23 | 2012-07-24 | Armstrong Quinton Co. LLC | Methods, systems, and computer program products for reconfiguring an operational mode of an input interface based on a privacy level |
US7711636B2 (en) | 2006-03-10 | 2010-05-04 | Experian Information Solutions, Inc. | Systems and methods for analyzing data |
US7761384B2 (en) * | 2006-03-16 | 2010-07-20 | Sushil Madhogarhia | Strategy-driven methodology for reducing identity theft |
KR101583268B1 (en) | 2006-03-27 | 2016-01-08 | 닐슨 미디어 리서치 인코퍼레이티드 | Methods and systems to meter media content presented on a wireless communication device |
US7886000B1 (en) | 2006-06-27 | 2011-02-08 | Confluence Commons, Inc. | Aggregation system for social network sites |
US8990340B1 (en) | 2006-06-27 | 2015-03-24 | Fingerprint Cards Ab | Aggregation system |
US7552862B2 (en) * | 2006-06-29 | 2009-06-30 | Microsoft Corporation | User-controlled profile sharing |
US7997485B2 (en) | 2006-06-29 | 2011-08-16 | Microsoft Corporation | Content presentation based on user preferences |
US8775214B2 (en) | 2006-07-19 | 2014-07-08 | Thompson Reuters (Market) LLC | Management method and system for a user |
US7606752B2 (en) | 2006-09-07 | 2009-10-20 | Yodlee Inc. | Host exchange in bill paying services |
US8370479B2 (en) | 2006-10-03 | 2013-02-05 | Axeda Acquisition Corporation | System and method for dynamically grouping devices based on present device conditions |
US8239677B2 (en) * | 2006-10-10 | 2012-08-07 | Equifax Inc. | Verification and authentication systems and methods |
US8359278B2 (en) | 2006-10-25 | 2013-01-22 | IndentityTruth, Inc. | Identity protection |
US8154760B2 (en) * | 2006-11-30 | 2012-04-10 | Ricoh Company, Ltd. | Image forming apparatus, content display method, and computer program product |
US8065397B2 (en) | 2006-12-26 | 2011-11-22 | Axeda Acquisition Corporation | Managing configurations of distributed devices |
WO2008083309A1 (en) * | 2006-12-28 | 2008-07-10 | New Tier, Inc. | Communicator program manager |
US7925554B1 (en) * | 2006-12-29 | 2011-04-12 | Amazon Technologies, Inc. | Using configured application pricing to determine end user fees for use of invocable services |
US10853780B1 (en) | 2006-12-29 | 2020-12-01 | Amazon Technologies, Inc. | Providing configurable pricing for use of invocable services by applications |
US8620952B2 (en) | 2007-01-03 | 2013-12-31 | Carhamm Ltd., Llc | System for database reporting |
US8554669B2 (en) * | 2007-01-09 | 2013-10-08 | Bill Me Later, Inc. | Method and system for offering a credit product by a credit issuer to a consumer at a point-of sale |
US8433648B2 (en) | 2007-02-26 | 2013-04-30 | Bill Me Later, Inc. | Method and system for engaging in a transaction between a consumer and a merchant |
US8380621B1 (en) | 2007-02-28 | 2013-02-19 | Island Intellectual Property Llc | Systems, methods and program products for swap processing for uninsured accounts |
US7752107B1 (en) | 2007-02-28 | 2010-07-06 | Island Intellectual Property Llc | System and method for managing aggregated accounts |
US8260705B1 (en) | 2007-02-28 | 2012-09-04 | Island Intellectual Property Llc | Systems, methods and program products for deposit and withdrawal processing |
US8032456B1 (en) | 2008-02-11 | 2011-10-04 | Island Intellectual Property Llc | System, methods and program products for processing for a self clearing broker dealer |
US8285656B1 (en) | 2007-03-30 | 2012-10-09 | Consumerinfo.Com, Inc. | Systems and methods for data verification |
US20080288376A1 (en) | 2007-04-27 | 2008-11-20 | Cashedge, Inc. | Centralized payment hub method and system |
US20080301022A1 (en) * | 2007-04-30 | 2008-12-04 | Cashedge, Inc. | Real-Time Core Integration Method and System |
US20080272188A1 (en) | 2007-05-02 | 2008-11-06 | I4 Commerce Inc. | Distributed system for commerce |
US20080301023A1 (en) * | 2007-05-02 | 2008-12-04 | Cashedge, Inc. | Multi-Channel and Cross-Channel Account Opening |
WO2008144772A1 (en) * | 2007-05-24 | 2008-11-27 | Arpu, Inc. | Subscription promotion and management system and method |
US8478861B2 (en) | 2007-07-06 | 2013-07-02 | Axeda Acquisition Corp. | Managing distributed devices with limited connectivity |
US9721315B2 (en) | 2007-07-13 | 2017-08-01 | Cerner Innovation, Inc. | Claim processing validation system |
US8374929B1 (en) | 2007-08-06 | 2013-02-12 | Gogrid, LLC | System and method for billing for hosted services |
US20090076959A1 (en) * | 2007-09-11 | 2009-03-19 | Patrick Devaney | System and method for brokering ad hoc personal identification transactions between two consenting parties |
US9690820B1 (en) | 2007-09-27 | 2017-06-27 | Experian Information Solutions, Inc. | Database system for triggering event notifications based on updates to database records |
US9990674B1 (en) | 2007-12-14 | 2018-06-05 | Consumerinfo.Com, Inc. | Card registry systems and methods |
US8181111B1 (en) | 2007-12-31 | 2012-05-15 | Synchronoss Technologies, Inc. | System and method for providing social context to digital activity |
US20090182675A1 (en) * | 2008-01-04 | 2009-07-16 | Brody Edward | Method and system for conducting electronic commerce over a network using a shadow credit card number |
US20100030687A1 (en) * | 2008-01-18 | 2010-02-04 | Cashedge, Inc. | Real-Time Settlement of Financial Transactions Using Electronic Fund Transfer Networks |
US10275524B2 (en) | 2008-01-23 | 2019-04-30 | Sears Holdings Management Corporation | Social network searching with breadcrumbs |
US8503991B2 (en) * | 2008-04-03 | 2013-08-06 | The Nielsen Company (Us), Llc | Methods and apparatus to monitor mobile devices |
US20090276359A1 (en) * | 2008-04-24 | 2009-11-05 | Cashedge, Inc. | Multi-Product-Multi-Channel Payment Platform System and Method |
US8261334B2 (en) | 2008-04-25 | 2012-09-04 | Yodlee Inc. | System for performing web authentication of a user by proxy |
US8719164B2 (en) | 2008-06-19 | 2014-05-06 | Bill Me Later, Inc. | Method and system for engaging in a transaction between a business entity and a merchant |
US8312033B1 (en) | 2008-06-26 | 2012-11-13 | Experian Marketing Solutions, Inc. | Systems and methods for providing an integrated identifier |
US8060424B2 (en) | 2008-11-05 | 2011-11-15 | Consumerinfo.Com, Inc. | On-line method and system for monitoring and reporting unused available credit |
US8346615B2 (en) | 2008-11-25 | 2013-01-01 | Yodlee, Inc. | Financial gadgets |
US20100174638A1 (en) | 2009-01-06 | 2010-07-08 | ConsumerInfo.com | Report existence monitoring |
US8965784B2 (en) | 2009-01-14 | 2015-02-24 | Signature Systems Llc | Reward exchange method and system implementing data collection and analysis |
US8555359B2 (en) | 2009-02-26 | 2013-10-08 | Yodlee, Inc. | System and methods for automatically accessing a web site on behalf of a client |
WO2010111068A1 (en) | 2009-03-24 | 2010-09-30 | Yodlee, Inc. | Directing payments to satisfy periodic financial obligations |
AU2009345651B2 (en) | 2009-05-08 | 2016-05-12 | Arbitron Mobile Oy | System and method for behavioural and contextual data analytics |
US8781931B1 (en) | 2009-05-26 | 2014-07-15 | Island Intellectual Property Llc | Method and system for allocating deposits over a plurality of depository institutions |
US8352342B1 (en) | 2009-06-19 | 2013-01-08 | Island Intellectual Property Llc | Method and system for determining fees for deposits allocated over a plurality of deposit institutions |
US10242402B1 (en) | 2009-07-24 | 2019-03-26 | Wells Fargo Bank, N.A. | Collection system and method |
US9552610B1 (en) | 2009-07-24 | 2017-01-24 | Wells Fargo Bank, N.A. | Online collection portal system and method |
US9262754B1 (en) | 2009-08-21 | 2016-02-16 | Wells Fargo Bank, N.A. | Request tracking system and method |
US8255006B1 (en) | 2009-11-10 | 2012-08-28 | Fusionone, Inc. | Event dependent notification system and method |
US8370236B1 (en) | 2009-11-24 | 2013-02-05 | Island Intellectual Property Llc | Method and system for allocating funds over a plurality of time deposit instruments in depository institutions |
US8407726B2 (en) | 2009-12-31 | 2013-03-26 | International Business Machines Corporation | Collaboration in low bandwidth applications |
US8332509B2 (en) * | 2010-02-20 | 2012-12-11 | Microsoft Corporation | Parameterized computer monitoring system |
US9652802B1 (en) | 2010-03-24 | 2017-05-16 | Consumerinfo.Com, Inc. | Indirect monitoring and reporting of a user's credit data |
EP2572338A4 (en) | 2010-05-21 | 2016-04-27 | Hsbc Technology & Services Usa Inc | Account opening computer system architecture and process for implementing same |
US9275360B2 (en) | 2010-05-21 | 2016-03-01 | Hsbc Technology & Services (Usa) Inc. | Account opening flow configuration computer system and process for implementing same |
US8589213B2 (en) | 2010-10-21 | 2013-11-19 | Hsbc Technology & Services (Usa) Inc. | Computer metrics system and process for implementing same |
US9183560B2 (en) | 2010-05-28 | 2015-11-10 | Daniel H. Abelow | Reality alternate |
US8458089B1 (en) | 2010-06-14 | 2013-06-04 | Island Intellectual Property Llc | System, method and program product for administering fund movements using depository institution groups |
US9002924B2 (en) | 2010-06-17 | 2015-04-07 | Microsoft Technology Licensing, Llc | Contextual based information aggregation system |
US20110314482A1 (en) * | 2010-06-18 | 2011-12-22 | Microsoft Corporation | System for universal mobile data |
WO2011163060A2 (en) | 2010-06-23 | 2011-12-29 | Managed Audience Share Solutions LLC | Methods, systems, and computer program products for managing organized binary advertising asset markets |
CA3020551C (en) | 2010-06-24 | 2022-06-07 | Arbitron Mobile Oy | Network server arrangement for processing non-parametric, multi-dimensional, spatial and temporal human behavior or technical observations measured pervasively, and related method for the same |
US8340685B2 (en) | 2010-08-25 | 2012-12-25 | The Nielsen Company (Us), Llc | Methods, systems and apparatus to generate market segmentation data with anonymous location data |
US8583545B1 (en) | 2010-09-20 | 2013-11-12 | Island Intellectual Property Llc | Systems and methods for money fund banking with flexible interest allocation |
WO2012051180A1 (en) | 2010-10-11 | 2012-04-19 | Hsbc Technologies Inc. | Computer architecture and process for application processing engine |
EP2633480A4 (en) | 2010-10-27 | 2016-08-17 | Hsbc Technology & Services Usa Inc | Integrated customer communications computer system and process for implementing same |
US8943428B2 (en) | 2010-11-01 | 2015-01-27 | Synchronoss Technologies, Inc. | System for and method of field mapping |
US9235728B2 (en) | 2011-02-18 | 2016-01-12 | Csidentity Corporation | System and methods for identifying compromised personally identifiable information on the internet |
US9558519B1 (en) | 2011-04-29 | 2017-01-31 | Consumerinfo.Com, Inc. | Exposing reporting cycle information |
US20120317003A1 (en) * | 2011-06-09 | 2012-12-13 | Mcgrane Russell | Automated expense account report generator |
US9483606B1 (en) | 2011-07-08 | 2016-11-01 | Consumerinfo.Com, Inc. | Lifescore |
US8452702B1 (en) | 2011-09-08 | 2013-05-28 | Island Intellectual Property Llc | System, method and program product for minimizing fund movements |
US9106691B1 (en) | 2011-09-16 | 2015-08-11 | Consumerinfo.Com, Inc. | Systems and methods of identity protection and management |
US8655689B1 (en) | 2011-10-13 | 2014-02-18 | Island Intellectual Property Llc | System, method and program product for modeling fund movements |
US8738516B1 (en) | 2011-10-13 | 2014-05-27 | Consumerinfo.Com, Inc. | Debt services candidate locator |
US11030562B1 (en) | 2011-10-31 | 2021-06-08 | Consumerinfo.Com, Inc. | Pre-data breach monitoring |
US9606972B2 (en) | 2011-11-09 | 2017-03-28 | Microsoft Technology Licensing, Llc | Document collaboration with collaboration context data |
US8442859B1 (en) | 2011-12-23 | 2013-05-14 | Managed Audience Share Solutions LLC | Methods, systems, and computer program products for optimizing liquidity and price discovery in advertising markets |
JP5714523B2 (en) * | 2012-02-29 | 2015-05-07 | 京セラ株式会社 | Mobile terminal, mobile terminal control method and program |
US9853959B1 (en) | 2012-05-07 | 2017-12-26 | Consumerinfo.Com, Inc. | Storage and maintenance of personal data |
EP2901303A4 (en) | 2012-09-25 | 2016-06-01 | Moneydesktop Inc | Aggregation source routing |
US8626659B1 (en) | 2012-09-28 | 2014-01-07 | Fiserv, Inc. | Facilitating presentation of content relating to a financial transaction |
US9654541B1 (en) | 2012-11-12 | 2017-05-16 | Consumerinfo.Com, Inc. | Aggregating user web browsing data |
US9916621B1 (en) | 2012-11-30 | 2018-03-13 | Consumerinfo.Com, Inc. | Presentation of credit score factors |
US20140188728A1 (en) | 2012-12-31 | 2014-07-03 | Fiserv, Inc. | Systems and methods for performing financial transactions |
US9076182B2 (en) | 2013-03-11 | 2015-07-07 | Yodlee, Inc. | Automated financial data aggregation |
US8812387B1 (en) | 2013-03-14 | 2014-08-19 | Csidentity Corporation | System and method for identifying related credit inquiries |
US9406085B1 (en) | 2013-03-14 | 2016-08-02 | Consumerinfo.Com, Inc. | System and methods for credit dispute processing, resolution, and reporting |
US10102570B1 (en) | 2013-03-14 | 2018-10-16 | Consumerinfo.Com, Inc. | Account vulnerability alerts |
US10685398B1 (en) | 2013-04-23 | 2020-06-16 | Consumerinfo.Com, Inc. | Presenting credit score information |
US10200478B1 (en) * | 2013-08-19 | 2019-02-05 | Dell Software Inc. | Systems and methods for predictive logins to session(s) or resource(s) |
US20150067046A1 (en) | 2013-09-03 | 2015-03-05 | International Business Machines Corporation | Social networking information consumption gap resolution |
US10102536B1 (en) | 2013-11-15 | 2018-10-16 | Experian Information Solutions, Inc. | Micro-geographic aggregation system |
US9477737B1 (en) | 2013-11-20 | 2016-10-25 | Consumerinfo.Com, Inc. | Systems and user interfaces for dynamic access of multiple remote databases and synchronization of data based on user rules |
US10262362B1 (en) | 2014-02-14 | 2019-04-16 | Experian Information Solutions, Inc. | Automatic generation of code for attributes |
US20190188230A1 (en) | 2014-03-12 | 2019-06-20 | Michael Bilotta | Systems and methods for an information-based life view |
US9959424B2 (en) * | 2014-03-12 | 2018-05-01 | Michael Bilotta | Information based life view |
US9595023B1 (en) | 2014-05-21 | 2017-03-14 | Plaid Technologies, Inc. | System and method for facilitating programmatic verification of transactions |
US9449346B1 (en) | 2014-05-21 | 2016-09-20 | Plaid Technologies, Inc. | System and method for programmatically accessing financial data |
US10878470B2 (en) | 2014-09-05 | 2020-12-29 | Micro Focus Llc | Frameworks to demonstrate live products |
US9922375B1 (en) | 2014-09-22 | 2018-03-20 | Certify, Inc. | Systems and methods of parsing receipts |
US10210579B1 (en) | 2014-09-22 | 2019-02-19 | Certify, Inc. | Automated expense reports systems and methods |
US11295308B1 (en) | 2014-10-29 | 2022-04-05 | The Clearing House Payments Company, L.L.C. | Secure payment processing |
US10339527B1 (en) | 2014-10-31 | 2019-07-02 | Experian Information Solutions, Inc. | System and architecture for electronic fraud detection |
US10185946B2 (en) | 2014-12-31 | 2019-01-22 | Fiserv, Inc. | Facilitating presentation of content relating to a financial transaction |
US9374370B1 (en) | 2015-01-23 | 2016-06-21 | Island Intellectual Property, Llc | Invariant biohash security system and method |
CN104579931B (en) * | 2015-01-23 | 2017-11-03 | 浪潮通用软件有限公司 | The access method and device of a kind of copending document based on mail |
US10672000B1 (en) | 2015-03-18 | 2020-06-02 | Access Control Advantage, Inc. | Bypass system |
US11042882B2 (en) | 2015-07-01 | 2021-06-22 | The Clearing House Payments Company, L.L.C. | Real-time payment system, method, apparatus, and computer program |
US11694168B2 (en) | 2015-07-01 | 2023-07-04 | The Clearing House Payments Company L.L.C. | Real-time payment system, method, apparatus, and computer program |
US11151468B1 (en) | 2015-07-02 | 2021-10-19 | Experian Information Solutions, Inc. | Behavior analysis using distributed representations of event data |
CA2997115C (en) | 2015-09-08 | 2022-01-04 | Plaid Technologies, Inc. | Secure permissioning of access to user accounts, including secure deauthorization of access to user accounts |
US20170109752A1 (en) * | 2015-10-15 | 2017-04-20 | Mastercard International Incorporated | Utilizing enhanced cardholder authentication token |
US9692815B2 (en) | 2015-11-12 | 2017-06-27 | Mx Technologies, Inc. | Distributed, decentralized data aggregation |
US11410230B1 (en) | 2015-11-17 | 2022-08-09 | Consumerinfo.Com, Inc. | Realtime access and control of secure regulated data |
US10757154B1 (en) | 2015-11-24 | 2020-08-25 | Experian Information Solutions, Inc. | Real-time event-based notification system |
US11233789B1 (en) | 2015-11-30 | 2022-01-25 | Mx Technologies, Inc. | Automatic event migration |
US11288359B1 (en) | 2015-11-30 | 2022-03-29 | Mx Technologies, Inc. | Automatic account protection |
US10726491B1 (en) | 2015-12-28 | 2020-07-28 | Plaid Inc. | Parameter-based computer evaluation of user accounts based on user account data stored in one or more databases |
US9852309B2 (en) * | 2016-01-05 | 2017-12-26 | Prifender Ltd. | System and method for securing personal data elements |
US10984468B1 (en) | 2016-01-06 | 2021-04-20 | Plaid Inc. | Systems and methods for estimating past and prospective attribute values associated with a user account |
US9836188B2 (en) * | 2016-04-14 | 2017-12-05 | Qamar Hasan | Web button listing multiple descriptions in a single button |
US10372474B2 (en) * | 2016-05-31 | 2019-08-06 | Vmware, Inc. | Predictive login of virtual machines |
US11309075B2 (en) | 2016-12-29 | 2022-04-19 | Cerner Innovation, Inc. | Generation of a transaction set |
CN110383319B (en) | 2017-01-31 | 2023-05-26 | 益百利信息解决方案公司 | Large scale heterogeneous data ingestion and user resolution |
US11379618B2 (en) | 2017-06-01 | 2022-07-05 | International Business Machines Corporation | Secure sensitive personal information dependent transactions |
US11468085B2 (en) | 2017-07-22 | 2022-10-11 | Plaid Inc. | Browser-based aggregation |
US10878421B2 (en) | 2017-07-22 | 2020-12-29 | Plaid Inc. | Data verified deposits |
US10699028B1 (en) | 2017-09-28 | 2020-06-30 | Csidentity Corporation | Identity security architecture systems and methods |
CN113139009A (en) | 2017-10-23 | 2021-07-20 | 创新先进技术有限公司 | Data auditing method and device |
US10896472B1 (en) | 2017-11-14 | 2021-01-19 | Csidentity Corporation | Security and identity verification system and architecture |
US11436577B2 (en) | 2018-05-03 | 2022-09-06 | The Clearing House Payments Company L.L.C. | Bill pay service with federated directory model support |
US10880313B2 (en) | 2018-09-05 | 2020-12-29 | Consumerinfo.Com, Inc. | Database platform for realtime updating of user data from third party sources |
US10963434B1 (en) | 2018-09-07 | 2021-03-30 | Experian Information Solutions, Inc. | Data architecture for supporting multiple search models |
US11316862B1 (en) | 2018-09-14 | 2022-04-26 | Plaid Inc. | Secure authorization of access to user accounts by one or more authorization mechanisms |
US11315179B1 (en) | 2018-11-16 | 2022-04-26 | Consumerinfo.Com, Inc. | Methods and apparatuses for customized card recommendations |
US11200339B1 (en) * | 2018-11-30 | 2021-12-14 | United Services Automobile Association (Usaa) | System for securing electronic personal user data |
US11238656B1 (en) | 2019-02-22 | 2022-02-01 | Consumerinfo.Com, Inc. | System and method for an augmented reality experience via an artificial intelligence bot |
US11941065B1 (en) | 2019-09-13 | 2024-03-26 | Experian Information Solutions, Inc. | Single identifier platform for storing entity data |
US11887129B1 (en) | 2020-02-27 | 2024-01-30 | MeasureOne, Inc. | Consumer-permissioned data processing system |
US20210286475A1 (en) * | 2020-03-13 | 2021-09-16 | Jpmorgan Chase Bank, N.A. | Method and system for generating a user interface for managing a data set |
US11887069B2 (en) | 2020-05-05 | 2024-01-30 | Plaid Inc. | Secure updating of allocations to user accounts |
US11327960B1 (en) | 2020-10-16 | 2022-05-10 | Plaid Inc. | Systems and methods for data parsing |
US20220217136A1 (en) * | 2021-01-04 | 2022-07-07 | Bank Of America Corporation | Identity verification through multisystem cooperation |
US11880377B1 (en) | 2021-03-26 | 2024-01-23 | Experian Information Solutions, Inc. | Systems and methods for entity resolution |
Family Cites Families (313)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4727243A (en) | 1984-10-24 | 1988-02-23 | Telenet Communications Corporation | Financial transaction system |
CA1341310C (en) | 1988-07-15 | 2001-10-23 | Robert Filepp | Interactive computer network and method of operation |
US4987538A (en) | 1989-04-27 | 1991-01-22 | Western Medical Consultants | Automated processing of provider billings |
US5220501A (en) | 1989-12-08 | 1993-06-15 | Online Resources, Ltd. | Method and system for remote delivery of retail banking services |
DE69225828T2 (en) | 1991-02-27 | 1998-11-12 | Canon Kk | Procedure for discovering incorrect overwriting of stored data |
ZA926734B (en) | 1991-09-12 | 1993-07-22 | Hydrotech Chemical Corp | Heat exchanger manifold for swimming-pool or spa heaters. |
US5619716A (en) | 1991-11-05 | 1997-04-08 | Hitachi, Ltd. | Information processing system having a configuration management system for managing the software of the information processing system |
US5237499A (en) | 1991-11-12 | 1993-08-17 | Garback Brent J | Computer travel planning system |
US5640577A (en) | 1991-12-30 | 1997-06-17 | Davox Corporation | Data processing system with automated at least partial forms completion |
US5446891A (en) | 1992-02-26 | 1995-08-29 | International Business Machines Corporation | System for adjusting hypertext links with weighed user goals and activities |
US5655089A (en) | 1992-04-10 | 1997-08-05 | Bucci; Joseph J. | Method for the consolidation summarization and transmission of a plurality of mailable materials |
AU5364794A (en) * | 1992-10-22 | 1994-05-09 | American Express Travel Related Services Company, Inc. | Automated billing consolidation system and method |
US5887133A (en) | 1997-01-15 | 1999-03-23 | Health Hero Network | System and method for modifying documents sent over a communications network |
SE9300671D0 (en) | 1993-03-01 | 1993-03-01 | Sven Nauckhoff | WORK FLOW MANAGEMENT |
US5340537A (en) | 1993-04-16 | 1994-08-23 | Big Three Industries, Inc. | Temperature indicating compositions |
US5544352A (en) | 1993-06-14 | 1996-08-06 | Libertech, Inc. | Method and apparatus for indexing, searching and displaying data |
US5649118A (en) | 1993-08-27 | 1997-07-15 | Lucent Technologies Inc. | Smart card with multiple charge accounts and product item tables designating the account to debit |
US5838918A (en) | 1993-12-13 | 1998-11-17 | International Business Machines Corporation | Distributing system configuration information from a manager machine to subscribed endpoint machines in a distrubuted computing environment |
US5694549A (en) | 1994-03-03 | 1997-12-02 | Telescan, Inc. | Multi-provider on-line communications system |
US5893075A (en) | 1994-04-01 | 1999-04-06 | Plainfield Software | Interactive system and method for surveying and targeting customers |
US5799151A (en) | 1994-04-04 | 1998-08-25 | Hoffer; Steven M. | Interactive electronic trade network and user interface |
US5537314A (en) | 1994-04-18 | 1996-07-16 | First Marketrust Intl. | Referral recognition system for an incentive award program |
US5918214A (en) | 1996-10-25 | 1999-06-29 | Ipf, Inc. | System and method for finding product and service related information on the internet |
US5724567A (en) | 1994-04-25 | 1998-03-03 | Apple Computer, Inc. | System for directing relevance-ranked data objects to computer users |
US5768521A (en) | 1994-05-16 | 1998-06-16 | Intel Corporation | General purpose metering mechanism for distribution of electronic information |
US5878215A (en) * | 1994-05-23 | 1999-03-02 | Mastercard International Incorporated | System and method for processing multiple electronic transaction requests |
DE4418231C2 (en) | 1994-05-25 | 1997-02-27 | Siemens Ag | Modularly structured service personal computer |
US5459306A (en) | 1994-06-15 | 1995-10-17 | Blockbuster Entertainment Corporation | Method and system for delivering on demand, individually targeted promotions |
US5948040A (en) | 1994-06-24 | 1999-09-07 | Delorme Publishing Co. | Travel reservation information and planning system |
JP3374876B2 (en) | 1994-07-08 | 2003-02-10 | ソニー株式会社 | User terminal device and information processing method |
US5768577A (en) | 1994-09-29 | 1998-06-16 | International Business Machines Corporation | Performance optimization in a heterogeneous, distributed database environment |
US5590196A (en) | 1994-10-06 | 1996-12-31 | Connotech Experts Conseils Inc. | Secure payment method using facsimile |
EP0709982B1 (en) | 1994-10-26 | 2004-06-30 | International Business Machines Corporation | Medium access control scheme for wireless LAN using a variable length interleaved time division frame |
US5696965A (en) * | 1994-11-03 | 1997-12-09 | Intel Corporation | Electronic information appraisal agent |
US5717923A (en) | 1994-11-03 | 1998-02-10 | Intel Corporation | Method and apparatus for dynamically customizing electronic information to individual end users |
US5613012A (en) | 1994-11-28 | 1997-03-18 | Smarttouch, Llc. | Tokenless identification system for authorization of electronic transactions and electronic transmissions |
US5758257A (en) | 1994-11-29 | 1998-05-26 | Herz; Frederick | System and method for scheduling broadcast of and access to video programs and other data using customer profiles |
US6029195A (en) | 1994-11-29 | 2000-02-22 | Herz; Frederick S. M. | System for customized electronic identification of desirable objects |
US5634127A (en) | 1994-11-30 | 1997-05-27 | International Business Machines Corporation | Methods and apparatus for implementing a message driven processor in a client-server environment |
US5619648A (en) | 1994-11-30 | 1997-04-08 | Lucent Technologies Inc. | Message filtering techniques |
US6237096B1 (en) | 1995-01-17 | 2001-05-22 | Eoriginal Inc. | System and method for electronic transmission storage and retrieval of authenticated documents |
WO1996027155A2 (en) | 1995-02-13 | 1996-09-06 | Electronic Publishing Resources, Inc. | Systems and methods for secure transaction management and electronic rights protection |
US5892900A (en) | 1996-08-30 | 1999-04-06 | Intertrust Technologies Corp. | Systems and methods for secure transaction management and electronic rights protection |
US5890140A (en) | 1995-02-22 | 1999-03-30 | Citibank, N.A. | System for communicating with an electronic delivery system that integrates global financial services |
JP4309480B2 (en) * | 1995-03-07 | 2009-08-05 | 株式会社東芝 | Information processing device |
US5793966A (en) | 1995-12-01 | 1998-08-11 | Vermeer Technologies, Inc. | Computer system and computer-implemented process for creation and maintenance of online services |
US5855015A (en) | 1995-03-20 | 1998-12-29 | Interval Research Corporation | System and method for retrieval of hyperlinked information resources |
US5819284A (en) | 1995-03-24 | 1998-10-06 | At&T Corp. | Personalized real time information display as a portion of a screen saver |
US5870552A (en) | 1995-03-28 | 1999-02-09 | America Online, Inc. | Method and apparatus for publishing hypermedia documents over wide area networks |
US5790793A (en) | 1995-04-04 | 1998-08-04 | Higley; Thomas | Method and system to create, transmit, receive and process information, including an address to further information |
US5734883A (en) | 1995-04-27 | 1998-03-31 | Michael Umen & Co., Inc. | Drug document production system |
US5708825A (en) | 1995-05-26 | 1998-01-13 | Iconovex Corporation | Automatic summary page creation and hyperlink generation |
US5752246A (en) | 1995-06-07 | 1998-05-12 | International Business Machines Corporation | Service agent for fulfilling requests of a web browser |
US5745754A (en) | 1995-06-07 | 1998-04-28 | International Business Machines Corporation | Sub-agent for fulfilling requests of a web browser using an intelligent agent and providing a report |
US5701451A (en) | 1995-06-07 | 1997-12-23 | International Business Machines Corporation | Method for fulfilling requests of a web browser |
US5793964A (en) | 1995-06-07 | 1998-08-11 | International Business Machines Corporation | Web browser system |
US5721908A (en) | 1995-06-07 | 1998-02-24 | International Business Machines Corporation | Computer network for WWW server data access over internet |
US5796945A (en) | 1995-06-07 | 1998-08-18 | Tarabella; Robert M. | Idle time multimedia viewer method and apparatus for collecting and displaying information according to user defined indicia |
US5710918A (en) | 1995-06-07 | 1998-01-20 | International Business Machines Corporation | Method for distributed task fulfillment of web browser requests |
US5740549A (en) | 1995-06-12 | 1998-04-14 | Pointcast, Inc. | Information and advertising distribution system and method |
JP3756954B2 (en) | 1995-07-11 | 2006-03-22 | 株式会社 日立製作所 | Service provision system |
US5907837A (en) | 1995-07-17 | 1999-05-25 | Microsoft Corporation | Information retrieval system in an on-line network including separate content and layout of published titles |
US5860073A (en) | 1995-07-17 | 1999-01-12 | Microsoft Corporation | Style sheets for publishing system |
US6199082B1 (en) | 1995-07-17 | 2001-03-06 | Microsoft Corporation | Method for delivering separate design and content in a multimedia publishing system |
US5649186A (en) | 1995-08-07 | 1997-07-15 | Silicon Graphics Incorporated | System and method for a computer-based dynamic information clipping service |
US5710887A (en) | 1995-08-29 | 1998-01-20 | Broadvision | Computer system and method for electronic commerce |
US5812769A (en) | 1995-09-20 | 1998-09-22 | Infonautics Corporation | Method and apparatus for redirecting a user to a new location on the world wide web using relative universal resource locators |
US5712979A (en) | 1995-09-20 | 1998-01-27 | Infonautics Corporation | Method and apparatus for attaching navigational history information to universal resource locator links on a world wide web page |
US6732369B1 (en) | 1995-10-02 | 2004-05-04 | Starsight Telecast, Inc. | Systems and methods for contextually linking television program information |
US6029175A (en) | 1995-10-26 | 2000-02-22 | Teknowledge Corporation | Automatic retrieval of changed files by a network software agent |
US5905865A (en) | 1995-10-30 | 1999-05-18 | Web Pager, Inc. | Apparatus and method of automatically accessing on-line services in response to broadcast of on-line addresses |
US5699528A (en) | 1995-10-31 | 1997-12-16 | Mastercard International, Inc. | System and method for bill delivery and payment over a communications network |
EP0941515A1 (en) * | 1995-10-31 | 1999-09-15 | Frederick S.M. Herz | System for customized electronic identification of desirable objects |
WO1997019415A2 (en) | 1995-11-07 | 1997-05-29 | Cadis, Inc. | Search engine for remote object oriented database management system |
US5778367A (en) | 1995-12-14 | 1998-07-07 | Network Engineering Software, Inc. | Automated on-line information service and directory, particularly for the world wide web |
US5706442A (en) | 1995-12-20 | 1998-01-06 | Block Financial Corporation | System for on-line financial services using distributed objects |
US5978766A (en) | 1995-12-20 | 1999-11-02 | Starwave Corporation | Machine, method and medium for assisted selection of information from a choice space |
JP3935986B2 (en) | 1995-12-26 | 2007-06-27 | 富士通株式会社 | Network information resource monitoring system for notifying changes in information resources in a network |
US5732074A (en) | 1996-01-16 | 1998-03-24 | Cellport Labs, Inc. | Mobile portable wireless communication system |
US6119101A (en) | 1996-01-17 | 2000-09-12 | Personal Agents, Inc. | Intelligent agents for electronic commerce |
US5931907A (en) | 1996-01-23 | 1999-08-03 | British Telecommunications Public Limited Company | Software agent for comparing locally accessible keywords with meta-information and having pointers associated with distributed information |
US5710503A (en) | 1996-02-01 | 1998-01-20 | Aims Systems, Inc. | On-line battery monitoring system with defective cell detection capability |
US5987498A (en) | 1996-02-16 | 1999-11-16 | Atcom, Inc. | Credit card operated computer on-line service communication system |
US5963915A (en) | 1996-02-21 | 1999-10-05 | Infoseek Corporation | Secure, convenient and efficient system and method of performing trans-internet purchase transactions |
US5832474A (en) | 1996-02-26 | 1998-11-03 | Matsushita Electric Industrial Co., Ltd. | Document search and retrieval system with partial match searching of user-drawn annotations |
US5862325A (en) | 1996-02-29 | 1999-01-19 | Intermind Corporation | Computer-based communication system and method using metadata defining a control structure |
US5878219A (en) * | 1996-03-12 | 1999-03-02 | America Online, Inc. | System for integrating access to proprietary and internet resources |
US6006333A (en) | 1996-03-13 | 1999-12-21 | Sun Microsystems, Inc. | Password helper using a client-side master password which automatically presents the appropriate server-side password to a particular remote server |
US5838910A (en) | 1996-03-14 | 1998-11-17 | Domenikos; Steven D. | Systems and methods for executing application programs from a memory device linked to a server at an internet site |
JPH09259028A (en) | 1996-03-19 | 1997-10-03 | Toshiba Corp | Information presentation method |
US5901287A (en) | 1996-04-01 | 1999-05-04 | The Sabre Group Inc. | Information aggregation and synthesization system |
US6009408A (en) | 1996-04-01 | 1999-12-28 | Electronic Data Systems Corporation | Automated processing of travel related expenses |
US5995943A (en) | 1996-04-01 | 1999-11-30 | Sabre Inc. | Information aggregation and synthesization system |
US5923736A (en) | 1996-04-02 | 1999-07-13 | National Semiconductor Corporation | Hypertext markup language based telephone apparatus |
US5815665A (en) | 1996-04-03 | 1998-09-29 | Microsoft Corporation | System and method for providing trusted brokering services over a distributed network |
US5867799A (en) | 1996-04-04 | 1999-02-02 | Lang; Andrew K. | Information system and method for filtering a massive flow of information entities to meet user information classification needs |
US5794233A (en) | 1996-04-09 | 1998-08-11 | Rubinstein; Seymour I. | Browse by prompted keyword phrases |
US5727156A (en) | 1996-04-10 | 1998-03-10 | Hotoffice Technologies, Inc. | Internet-based automatic publishing system |
US5809242A (en) | 1996-04-19 | 1998-09-15 | Juno Online Services, L.P. | Electronic mail system for displaying advertisement at local computer received from remote system while the local computer is off-line the remote system |
US5905736A (en) | 1996-04-22 | 1999-05-18 | At&T Corp | Method for the billing of transactions over the internet |
US6085238A (en) | 1996-04-23 | 2000-07-04 | Matsushita Electric Works, Ltd. | Virtual LAN system |
US5894554A (en) | 1996-04-23 | 1999-04-13 | Infospinner, Inc. | System for managing dynamic web page generation requests by intercepting request at web server and routing to page server thereby releasing web server to process other requests |
US5848396A (en) | 1996-04-26 | 1998-12-08 | Freedom Of Information, Inc. | Method and apparatus for determining behavioral profile of a computer user |
US5963924A (en) | 1996-04-26 | 1999-10-05 | Verifone, Inc. | System, method and article of manufacture for the use of payment instrument holders and payment instruments in network electronic commerce |
US5742769A (en) | 1996-05-06 | 1998-04-21 | Banyan Systems, Inc. | Directory with options for access to and display of email addresses |
US5884033A (en) | 1996-05-15 | 1999-03-16 | Spyglass, Inc. | Internet filtering system for filtering data transferred over the internet utilizing immediate and deferred filtering actions |
US5961601A (en) | 1996-06-07 | 1999-10-05 | International Business Machines Corporation | Preserving state information in a continuing conversation between a client and server networked via a stateless protocol |
JP2000512044A (en) | 1996-06-07 | 2000-09-12 | エイ・ティ・アンド・ティ・コーポレーション | Internet file system |
US5897621A (en) | 1996-06-14 | 1999-04-27 | Cybercash, Inc. | System and method for multi-currency transactions |
US5943424A (en) | 1996-06-17 | 1999-08-24 | Hewlett-Packard Company | System, method and article of manufacture for processing a plurality of transactions from a single initiation point on a multichannel, extensible, flexible architecture |
US5724595A (en) | 1996-06-19 | 1998-03-03 | Sun Microsystems, Inc. | Simple method for creating hypertext links |
US5813007A (en) | 1996-06-20 | 1998-09-22 | Sun Microsystems, Inc. | Automatic updates of bookmarks in a client computer |
US5983170A (en) | 1996-06-25 | 1999-11-09 | Continuum Software, Inc | System and method for generating semantic analysis of textual information |
US6125352A (en) | 1996-06-28 | 2000-09-26 | Microsoft Corporation | System and method for conducting commerce over a distributed network |
US6006227A (en) * | 1996-06-28 | 1999-12-21 | Yale University | Document stream operating system |
US5825884A (en) | 1996-07-01 | 1998-10-20 | Thomson Consumer Electronics | Method and apparatus for operating a transactional server in a proprietary database environment |
US5835724A (en) | 1996-07-03 | 1998-11-10 | Electronic Data Systems Corporation | System and method for communication information using the internet that receives and maintains information concerning the client and generates and conveys the session data to the client |
DE69735486T2 (en) * | 1996-07-22 | 2006-12-14 | Cyva Research Corp., San Diego | TOOL FOR SAFETY AND EXTRACTION OF PERSONAL DATA |
US5918019A (en) | 1996-07-29 | 1999-06-29 | Cisco Technology, Inc. | Virtual dial-up protocol for network communication |
US6185601B1 (en) | 1996-08-02 | 2001-02-06 | Hewlett-Packard Company | Dynamic load balancing of a network of client and server computers |
US6014429A (en) | 1996-08-12 | 2000-01-11 | Lucent Technologies, Inc. | Two-way wireless messaging system with transaction server |
US5933811A (en) | 1996-08-20 | 1999-08-03 | Paul D. Angles | System and method for delivering customized advertisements within interactive communication systems |
US5839088A (en) | 1996-08-22 | 1998-11-17 | Go2 Software, Inc. | Geographic location referencing system and method |
US6134534A (en) | 1996-09-04 | 2000-10-17 | Priceline.Com Incorporated | Conditional purchase offer management system for cruises |
US5897620A (en) | 1997-07-08 | 1999-04-27 | Priceline.Com Inc. | Method and apparatus for the sale of airline-specified flight tickets |
US5890152A (en) | 1996-09-09 | 1999-03-30 | Seymour Alvin Rapaport | Personal feedback browser for obtaining media files |
US6003077A (en) | 1996-09-16 | 1999-12-14 | Integrated Systems, Inc. | Computer network system and method using domain name system to locate MIB module specification and web browser for managing SNMP agents |
US6253188B1 (en) | 1996-09-20 | 2001-06-26 | Thomson Newspapers, Inc. | Automated interactive classified ad system for the internet |
US5892909A (en) | 1996-09-27 | 1999-04-06 | Diffusion, Inc. | Intranet-based system with methods for co-active delivery of information to multiple users |
US5787425A (en) | 1996-10-01 | 1998-07-28 | International Business Machines Corporation | Object-oriented data mining framework mechanism |
US6029182A (en) | 1996-10-04 | 2000-02-22 | Canon Information Systems, Inc. | System for generating a custom formatted hypertext document by using a personal profile to retrieve hierarchical documents |
US5895468A (en) | 1996-10-07 | 1999-04-20 | Whitmyer, Jr.; Wesley W. | System automating delivery of professional services |
US6172677B1 (en) | 1996-10-07 | 2001-01-09 | Compaq Computer Corporation | Integrated content guide for interactive selection of content and services on personal computer systems with multiple sources and multiple media presentation |
US5983200A (en) | 1996-10-09 | 1999-11-09 | Slotznick; Benjamin | Intelligent agent for executing delegated tasks |
CA2267951C (en) | 1996-10-09 | 2003-12-30 | Visa International Service Association | Electronic statement presentment system |
US5897622A (en) | 1996-10-16 | 1999-04-27 | Microsoft Corporation | Electronic shopping and merchandising system |
US6070150A (en) | 1996-10-18 | 2000-05-30 | Microsoft Corporation | Electronic bill presentment and payment system |
US5745884A (en) | 1996-10-21 | 1998-04-28 | Mobile Area Networks, Inc. | System and method for billing data grade network use on a per connection basis |
US6385655B1 (en) | 1996-10-24 | 2002-05-07 | Tumbleweed Communications Corp. | Method and apparatus for delivering documents over an electronic network |
US6192407B1 (en) | 1996-10-24 | 2001-02-20 | Tumbleweed Communications Corp. | Private, trackable URLs for directed document delivery |
US5933816A (en) | 1996-10-31 | 1999-08-03 | Citicorp Development Center, Inc. | System and method for delivering financial services |
US5828839A (en) | 1996-11-14 | 1998-10-27 | Interactive Broadcaster Services Corp. | Computer network chat room based on channel broadcast in real time |
US5995965A (en) | 1996-11-18 | 1999-11-30 | Humetrix, Inc. | System and method for remotely accessing user data records |
US5966441A (en) | 1996-11-18 | 1999-10-12 | Apple Computer, Inc. | Method and apparatus for creating a secure autonomous network entity of a network component system |
GB2319862A (en) | 1996-11-28 | 1998-06-03 | Ibm | Performing computer-based on-line commerce using an intelligent agent |
US6125186A (en) | 1996-11-28 | 2000-09-26 | Fujitsu Limited | Encryption communication system using an agent and a storage medium for storing that agent |
US5913202A (en) | 1996-12-03 | 1999-06-15 | Fujitsu Limited | Financial information intermediary system |
US6023698A (en) | 1996-12-05 | 2000-02-08 | International Business Machines Corporation | System and method for transparently registering and updating information over the internet |
US5907838A (en) | 1996-12-10 | 1999-05-25 | Seiko Epson Corporation | Information search and collection method and system |
EP0848338A1 (en) | 1996-12-12 | 1998-06-17 | SONY DEUTSCHLAND GmbH | Server providing documents according to user profiles |
US5991799A (en) | 1996-12-20 | 1999-11-23 | Liberate Technologies | Information retrieval system using an internet multiplexer to focus user selection |
US5854897A (en) | 1996-12-27 | 1998-12-29 | Quantum Systems, Inc. | Network communications marketing system |
US5987611A (en) | 1996-12-31 | 1999-11-16 | Zone Labs, Inc. | System and methodology for managing internet access on a per application basis for client computers connected to the internet |
US5983268A (en) | 1997-01-14 | 1999-11-09 | Netmind Technologies, Inc. | Spreadsheet user-interface for an internet-document change-detection tool |
US5898836A (en) | 1997-01-14 | 1999-04-27 | Netmind Services, Inc. | Change-detection tool indicating degree and location of change of internet documents by comparison of cyclic-redundancy-check(CRC) signatures |
US5978842A (en) | 1997-01-14 | 1999-11-02 | Netmind Technologies, Inc. | Distributed-client change-detection tool with change-detection augmented by multiple clients |
JP3579204B2 (en) | 1997-01-17 | 2004-10-20 | 富士通株式会社 | Document summarizing apparatus and method |
US5961593A (en) | 1997-01-22 | 1999-10-05 | Lucent Technologies, Inc. | System and method for providing anonymous personalized browsing by a proxy system in a network |
US5875296A (en) | 1997-01-28 | 1999-02-23 | International Business Machines Corporation | Distributed file system web server user authentication with cookies |
AUPO489297A0 (en) | 1997-01-31 | 1997-02-27 | Aunty Abha's Electronic Publishing Pty Ltd | A system for electronic publishing |
US5918010A (en) | 1997-02-07 | 1999-06-29 | General Internet, Inc. | Collaborative internet data mining systems |
US5920848A (en) | 1997-02-12 | 1999-07-06 | Citibank, N.A. | Method and system for using intelligent agents for financial transactions, services, accounting, and advice |
US5949326A (en) * | 1997-02-13 | 1999-09-07 | Sony Corporation | Internet monitoring and input pager |
US5908469A (en) | 1997-02-14 | 1999-06-01 | International Business Machines Corporation | Generic user authentication for network computers |
CA2198189C (en) | 1997-02-21 | 2001-05-29 | Ibm Canada Limited-Ibm Canada Limitee | Internet browser based data entry architecture |
US5818935A (en) | 1997-03-10 | 1998-10-06 | Maa; Chia-Yiu | Internet enhanced video system |
US6073173A (en) | 1997-03-17 | 2000-06-06 | International Business Machines Corporation | Method and apparatus for optimal rebasing of web page transmission |
US5796952A (en) | 1997-03-21 | 1998-08-18 | Dot Com Development, Inc. | Method and apparatus for tracking client interaction with a network resource and creating client profiles and resource database |
US5884035A (en) | 1997-03-24 | 1999-03-16 | Pfn, Inc. | Dynamic distributed group registry apparatus and method for collaboration and selective sharing of information |
US6345300B1 (en) | 1997-03-25 | 2002-02-05 | Intel Corporation | Method and apparatus for detecting a user-controlled parameter from a client device behind a proxy |
US5995608A (en) | 1997-03-28 | 1999-11-30 | Confertech Systems Inc. | Method and apparatus for on-demand teleconferencing |
JPH10326289A (en) * | 1997-03-28 | 1998-12-08 | Nippon Telegr & Teleph Corp <Ntt> | Method for providing information and system therefor and storage medium for storing the same program |
US6055570A (en) | 1997-04-03 | 2000-04-25 | Sun Microsystems, Inc. | Subscribed update monitors |
US5893091A (en) | 1997-04-11 | 1999-04-06 | Immediata Corporation | Multicasting with key words |
US6119229A (en) | 1997-04-11 | 2000-09-12 | The Brodia Group | Virtual property system |
US6341353B1 (en) | 1997-04-11 | 2002-01-22 | The Brodia Group | Smart electronic receipt system |
US5930777A (en) | 1997-04-15 | 1999-07-27 | Barber; Timothy P. | Method of charging for pay-per-access information over a network |
US6119079A (en) | 1997-04-24 | 2000-09-12 | Hewlett-Packard Company | Method and structure for tokenized message logging system |
US6286029B1 (en) | 1997-04-28 | 2001-09-04 | Sabre Inc. | Kiosk controller that retrieves content from servers and then pushes the retrieved content to a kiosk in the order specified in a run list |
US5924090A (en) | 1997-05-01 | 1999-07-13 | Northern Light Technology Llc | Method and apparatus for searching a database of records |
US5951637A (en) | 1997-05-07 | 1999-09-14 | Intel Corporation | Bandwidth reservation system |
US5999940A (en) | 1997-05-28 | 1999-12-07 | Home Information Services, Inc. | Interactive information discovery tool and methodology |
US5937168A (en) | 1997-05-30 | 1999-08-10 | Bellsouth Corporation | Routing information within an adaptive routing architecture of an information retrieval system |
US6289389B1 (en) | 1997-06-03 | 2001-09-11 | Lextron Systems, Inc. | Enhanced integrated data delivery system |
US5903881A (en) | 1997-06-05 | 1999-05-11 | Intuit, Inc. | Personal online banking with integrated online statement and checkbook user interface |
US5987454A (en) | 1997-06-09 | 1999-11-16 | Hobbs; Allen | Method and apparatus for selectively augmenting retrieved text, numbers, maps, charts, still pictures and/or graphics, moving pictures and/or graphics and audio information from a network resource |
US6134658A (en) | 1997-06-09 | 2000-10-17 | Microsoft Corporation | Multi-server location-independent authentication certificate management system |
US5983227A (en) | 1997-06-12 | 1999-11-09 | Yahoo, Inc. | Dynamic page generator |
US5978828A (en) | 1997-06-13 | 1999-11-02 | Intel Corporation | URL bookmark update notification of page content or location changes |
US6301621B1 (en) | 1997-06-19 | 2001-10-09 | International Business Machines Corporation | Web server with direct mail capability |
US6018724A (en) | 1997-06-30 | 2000-01-25 | Sun Micorsystems, Inc. | Method and apparatus for authenticating on-line transaction data |
US6088711A (en) | 1997-07-01 | 2000-07-11 | Microsoft Corporation | Method and system for defining and applying a style to a paragraph |
US6044465A (en) | 1997-07-07 | 2000-03-28 | International Business Machines Corporation | User profile storage on and retrieval from a non-native server domain for use in a client running a native operating system |
US6223292B1 (en) | 1997-07-15 | 2001-04-24 | Microsoft Corporation | Authorization systems, methods, and computer program products |
US6377567B1 (en) | 1997-07-16 | 2002-04-23 | Mci Communications Corporation | System and method for distributing data collected from call center services |
US6044372A (en) | 1997-07-18 | 2000-03-28 | Dazel Corporation | Method and apparatus for publishing information to a communications network and enabling subscriptions to such information |
US6038601A (en) | 1997-07-21 | 2000-03-14 | Tibco, Inc. | Method and apparatus for storing and delivering documents on the internet |
US6205473B1 (en) | 1997-10-03 | 2001-03-20 | Helius Development Corporation | Method and system for asymmetric satellite communications for local area networks |
US5956709A (en) | 1997-07-28 | 1999-09-21 | Xue; Yansheng | Dynamic data assembling on internet client side |
US5937392A (en) | 1997-07-28 | 1999-08-10 | Switchboard Incorporated | Banner advertising display system and method with frequency of advertisement control |
US5951642A (en) | 1997-08-06 | 1999-09-14 | Hypertak, Inc. | System for collecting detailed internet information on the basis of the condition of activities of information viewers viewing information of service providers |
US5974406A (en) | 1997-08-18 | 1999-10-26 | International Business Machines Corporation | Automated matching, scheduling, and notification system |
US6301584B1 (en) | 1997-08-21 | 2001-10-09 | Home Information Services, Inc. | System and method for retrieving entities and integrating data |
US6717376B2 (en) * | 1997-08-26 | 2004-04-06 | Color Kinetics, Incorporated | Automotive information systems |
US6038668A (en) | 1997-09-08 | 2000-03-14 | Science Applications International Corporation | System, method, and medium for retrieving, organizing, and utilizing networked data |
US6128603A (en) | 1997-09-09 | 2000-10-03 | Dent; Warren T. | Consumer-based system and method for managing and paying electronic billing statements |
US5931947A (en) | 1997-09-11 | 1999-08-03 | International Business Machines Corporation | Secure array of remotely encrypted storage devices |
US6112212A (en) | 1997-09-15 | 2000-08-29 | The Pangea Project Llc | Systems and methods for organizing and analyzing information stored on a computer network |
US6085229A (en) | 1998-05-14 | 2000-07-04 | Belarc, Inc. | System and method for providing client side personalization of content of web pages and the like |
US6000832A (en) | 1997-09-24 | 1999-12-14 | Microsoft Corporation | Electronic online commerce card with customer generated transaction proxy number for online transactions |
US5974430A (en) | 1997-09-30 | 1999-10-26 | Unisys Corp. | Method for dynamically embedding objects stored in a web server within HTML for display by a web browser |
US6141333A (en) | 1997-09-30 | 2000-10-31 | Lucent Technologies Inc. | Tiered satellite internet delivery system |
US6023684A (en) | 1997-10-01 | 2000-02-08 | Security First Technologies, Inc. | Three tier financial transaction system with cache memory |
US6304860B1 (en) | 1997-10-03 | 2001-10-16 | Joseph B. Martin, Jr. | Automated debt payment system and method using ATM network |
US6081830A (en) | 1997-10-09 | 2000-06-27 | Gateway 2000, Inc. | Automatic linking to program-specific computer chat rooms |
US6119098A (en) | 1997-10-14 | 2000-09-12 | Patrice D. Guyot | System and method for targeting and distributing advertisements over a distributed network |
US5966697A (en) | 1997-10-30 | 1999-10-12 | Clearcommerce Corporation | System and method for secure transaction order management processing |
US5990887A (en) | 1997-10-30 | 1999-11-23 | International Business Machines Corp. | Method and system for efficient network desirable chat feedback over a communication network |
US5991756A (en) | 1997-11-03 | 1999-11-23 | Yahoo, Inc. | Information retrieval from hierarchical compound documents |
US6157924A (en) | 1997-11-07 | 2000-12-05 | Bell & Howell Mail Processing Systems Company | Systems, methods, and computer program products for delivering information in a preferred medium |
US6128624A (en) | 1997-11-12 | 2000-10-03 | Ncr Corporation | Collection and integration of internet and electronic commerce data in a database during web browsing |
US5978779A (en) | 1997-11-14 | 1999-11-02 | Merrill Lynch, Pierce, Fenner & Smith | Distributed architecture utility |
US6134532A (en) | 1997-11-14 | 2000-10-17 | Aptex Software, Inc. | System and method for optimal adaptive matching of users to most relevant entity and information in real-time |
US6041326A (en) | 1997-11-14 | 2000-03-21 | International Business Machines Corporation | Method and system in a computer network for an intelligent search engine |
US5978780A (en) | 1997-11-21 | 1999-11-02 | Craig Michael Watson | Integrated bill consolidation, payment aggregation, and settlement system |
US5987466A (en) | 1997-11-25 | 1999-11-16 | International Business Machines Corporation | Presenting web pages with discrete, browser-controlled complexity levels |
US6000033A (en) | 1997-11-26 | 1999-12-07 | International Business Machines Corporation | Password control via the web |
US6236991B1 (en) | 1997-11-26 | 2001-05-22 | International Business Machines Corp. | Method and system for providing access for categorized information from online internet and intranet sources |
US5860068A (en) | 1997-12-04 | 1999-01-12 | Petabyte Corporation | Method and system for custom manufacture and delivery of a data product |
US6240443B1 (en) | 1997-12-05 | 2001-05-29 | Ntt Software Corporation | Communication system and communication method |
US6065120A (en) | 1997-12-09 | 2000-05-16 | Phone.Com, Inc. | Method and system for self-provisioning a rendezvous to ensure secure access to information in a database from multiple devices |
US6260039B1 (en) | 1997-12-15 | 2001-07-10 | International Business Machines Corporation | Web interface and method for accessing directory information |
US5963949A (en) | 1997-12-22 | 1999-10-05 | Amazon.Com, Inc. | Method for data gathering around forms and search barriers |
US6101500A (en) | 1998-01-07 | 2000-08-08 | Novell, Inc. | System and method for managing objects in a hierarchical data structure |
US6032162A (en) | 1998-01-08 | 2000-02-29 | Burke; Alexander James | System for processing and storing internet bookmark address links |
US6226750B1 (en) | 1998-01-20 | 2001-05-01 | Proact Technologies Corp. | Secure session tracking method and system for client-server environment |
US6064985A (en) * | 1998-01-21 | 2000-05-16 | Assured Equities, Inc. | Automated portfolio management system with internet datafeed |
US6041307A (en) | 1998-01-23 | 2000-03-21 | Lucent Technologies Inc. | Technique for effectively managing resources in a network |
US6252544B1 (en) | 1998-01-27 | 2001-06-26 | Steven M. Hoffberg | Mobile communication device |
US6078924A (en) | 1998-01-30 | 2000-06-20 | Aeneid Corporation | Method and apparatus for performing data collection, interpretation and analysis, in an information platform |
US6078907A (en) | 1998-02-18 | 2000-06-20 | Lamm; David | Method and system for electronically presenting and paying bills |
US6108686A (en) | 1998-03-02 | 2000-08-22 | Williams, Jr.; Henry R. | Agent-based on-line information retrieval and viewing system |
US6055236A (en) | 1998-03-05 | 2000-04-25 | 3Com Corporation | Method and system for locating network services with distributed network address translation |
US6199079B1 (en) | 1998-03-09 | 2001-03-06 | Junglee Corporation | Method and system for automatically filling forms in an integrated network based transaction environment |
US6366923B1 (en) | 1998-03-23 | 2002-04-02 | Webivore Research, Llc | Gathering selected information from the world wide web |
US6438580B1 (en) | 1998-03-30 | 2002-08-20 | Electronic Data Systems Corporation | System and method for an interactive knowledgebase |
US6085188A (en) | 1998-03-30 | 2000-07-04 | International Business Machines Corporation | Method of hierarchical LDAP searching with relational tables |
US6192380B1 (en) | 1998-03-31 | 2001-02-20 | Intel Corporation | Automatic web based form fill-in |
US6148402A (en) | 1998-04-01 | 2000-11-14 | Hewlett-Packard Company | Apparatus and method for remotely executing commands using distributed computing environment remote procedure calls |
US6199113B1 (en) | 1998-04-15 | 2001-03-06 | Sun Microsystems, Inc. | Apparatus and method for providing trusted network security |
US6282278B1 (en) | 1998-04-22 | 2001-08-28 | International Business Machines Corporation | Universal conference control manager |
US6138158A (en) | 1998-04-30 | 2000-10-24 | Phone.Com, Inc. | Method and system for pushing and pulling data using wideband and narrowband transport systems |
GB2337903B (en) | 1998-05-28 | 2000-06-07 | 3Com Corp | Methods and apparatus for collecting storing processing and using network traffic data |
US6182085B1 (en) | 1998-05-28 | 2001-01-30 | International Business Machines Corporation | Collaborative team crawling:Large scale information gathering over the internet |
US6253326B1 (en) | 1998-05-29 | 2001-06-26 | Palm, Inc. | Method and system for secure communications |
US6141651A (en) | 1998-06-19 | 2000-10-31 | First Data Corporation | Funding and settlement integrated suspense processing system |
US6330561B1 (en) | 1998-06-26 | 2001-12-11 | At&T Corp. | Method and apparatus for improving end to end performance of a data network |
US6182142B1 (en) | 1998-07-10 | 2001-01-30 | Encommerce, Inc. | Distributed access management of information resources |
US6128655A (en) | 1998-07-10 | 2000-10-03 | International Business Machines Corporation | Distribution mechanism for filtering, formatting and reuse of web based content |
US6484155B1 (en) | 1998-07-21 | 2002-11-19 | Sentar, Inc. | Knowledge management system for performing dynamic distributed problem solving |
US6122673A (en) | 1998-07-22 | 2000-09-19 | Fore Systems, Inc. | Port scheduler and method for scheduling service providing guarantees, hierarchical rate limiting with/without overbooking capability |
US6212548B1 (en) | 1998-07-30 | 2001-04-03 | At & T Corp | System and method for multiple asynchronous text chat conversations |
US6499036B1 (en) | 1998-08-12 | 2002-12-24 | Bank Of America Corporation | Method and apparatus for data item movement between disparate sources and hierarchical, object-oriented representation |
US6202210B1 (en) | 1998-08-21 | 2001-03-13 | Sony Corporation Of Japan | Method and system for collecting data over a 1394 network to support analysis of consumer behavior, marketing and customer support |
US6286043B1 (en) | 1998-08-26 | 2001-09-04 | International Business Machines Corp. | User profile management in the presence of dynamic pages using content templates |
US6356899B1 (en) | 1998-08-29 | 2002-03-12 | International Business Machines Corporation | Method for interactively creating an information database including preferred information elements, such as preferred-authority, world wide web pages |
US6263362B1 (en) * | 1998-09-01 | 2001-07-17 | Bigfix, Inc. | Inspector for computed relevance messaging |
US6292787B1 (en) | 1998-09-11 | 2001-09-18 | Financial Engines, Inc. | Enhancing utility and diversifying model risk in a portfolio optimization framework |
US6161098A (en) * | 1998-09-14 | 2000-12-12 | Folio (Fn), Inc. | Method and apparatus for enabling small investors with a portfolio of securities to manage taxable events within the portfolio |
US6324569B1 (en) | 1998-09-23 | 2001-11-27 | John W. L. Ogilvie | Self-removing email verified or designated as such by a message distributor for the convenience of a recipient |
US6271840B1 (en) | 1998-09-24 | 2001-08-07 | James Lee Finseth | Graphical search engine visual index |
US6058417A (en) * | 1998-10-23 | 2000-05-02 | Ebay Inc. | Information presentation and management in an online trading environment |
ATE268484T1 (en) | 1998-10-28 | 2004-06-15 | Verticalone Corp | SYSTEM AND METHOD FOR AUTOMATIC ACCESS TO PERSONAL DATA |
US6360205B1 (en) | 1998-10-30 | 2002-03-19 | Trip.Com, Inc. | Obtaining and utilizing commercial information |
US6134548A (en) | 1998-11-19 | 2000-10-17 | Ac Properties B.V. | System, method and article of manufacture for advanced mobile bargain shopping |
US6219705B1 (en) * | 1998-11-12 | 2001-04-17 | Paradyne Corporation | System and method of collecting and maintaining historical top communicator information on a communication device |
US20010020242A1 (en) | 1998-11-16 | 2001-09-06 | Amit Gupta | Method and apparatus for processing client information |
US6195651B1 (en) | 1998-11-19 | 2001-02-27 | Andersen Consulting Properties Bv | System, method and article of manufacture for a tuned user application experience |
US6473740B2 (en) | 1998-11-29 | 2002-10-29 | Qpass, Inc. | Electronic commerce using a transaction network |
US6330592B1 (en) | 1998-12-05 | 2001-12-11 | Vignette Corporation | Method, memory, product, and code for displaying pre-customized content associated with visitor data |
US20010016034A1 (en) | 1998-12-08 | 2001-08-23 | Sukhinder Singh | Method and apparatus for obtaining and aggregating off-line user data for re-packaging and presentation to users over a data-packet-network |
US6859212B2 (en) | 1998-12-08 | 2005-02-22 | Yodlee.Com, Inc. | Interactive transaction center interface |
US6199077B1 (en) | 1998-12-08 | 2001-03-06 | Yodlee.Com, Inc. | Server-side web summary generation and presentation |
US6517587B2 (en) | 1998-12-08 | 2003-02-11 | Yodlee.Com, Inc. | Networked architecture for enabling automated gathering of information from Web servers |
US6412073B1 (en) | 1998-12-08 | 2002-06-25 | Yodiee.Com, Inc | Method and apparatus for providing and maintaining a user-interactive portal system accessible via internet or other switched-packet-network |
US7734541B2 (en) | 1998-12-08 | 2010-06-08 | Yodlee.Com, Inc. | Interactive funds transfer interface |
US20020059369A1 (en) | 1998-12-08 | 2002-05-16 | Christoph Kern | Method and apparatus for creating and distributing non-sensitized information summaries to users |
US7937325B2 (en) | 1998-12-08 | 2011-05-03 | Yodlee.Com, Inc. | Interactive bill payment center |
US20010051907A1 (en) | 1998-12-08 | 2001-12-13 | Srihari Kumar | Interactive financial portfolio tracking interface |
US20020015480A1 (en) | 1998-12-08 | 2002-02-07 | Neil Daswani | Flexible multi-network voice/data aggregation system architecture |
US6802042B2 (en) | 1999-06-01 | 2004-10-05 | Yodlee.Com, Inc. | Method and apparatus for providing calculated and solution-oriented personalized summary-reports to a user through a single user-interface |
US7644023B2 (en) | 1998-12-08 | 2010-01-05 | Yodlee.Com, Inc. | Portfolio synchronizing between different interfaces |
US6278993B1 (en) | 1998-12-08 | 2001-08-21 | Yodlee.Com, Inc. | Method and apparatus for extending an on-line internet search beyond pre-referenced sources and returning data over a data-packet-network (DPN) using private search engines as proxy-engines |
US20010023414A1 (en) | 1998-12-08 | 2001-09-20 | Srihari Kumar | Interactive calculation and presentation of financial data results through a single interface on a data-packet-network |
US6349307B1 (en) | 1998-12-28 | 2002-02-19 | U.S. Philips Corporation | Cooperative topical servers with automatic prefiltering and routing |
US6424979B1 (en) | 1998-12-30 | 2002-07-23 | American Management Systems, Inc. | System for presenting and managing enterprise architectures |
US6694546B1 (en) | 1999-01-27 | 2004-02-24 | Jean Kasem | Canopy assembly having universal components for different types of canopies |
US6317718B1 (en) | 1999-02-26 | 2001-11-13 | Accenture Properties (2) B.V. | System, method and article of manufacture for location-based filtering for shopping agent in the physical world |
US6202062B1 (en) | 1999-02-26 | 2001-03-13 | Ac Properties B.V. | System, method and article of manufacture for creating a filtered information summary based on multiple profiles of each single user |
US6397212B1 (en) | 1999-03-04 | 2002-05-28 | Peter Biffar | Self-learning and self-personalizing knowledge search engine that delivers holistic results |
US6199099B1 (en) | 1999-03-05 | 2001-03-06 | Ac Properties B.V. | System, method and article of manufacture for a mobile communication network utilizing a distributed communication network |
US6356905B1 (en) | 1999-03-05 | 2002-03-12 | Accenture Llp | System, method and article of manufacture for mobile communication utilizing an interface support framework |
US6339761B1 (en) | 1999-05-13 | 2002-01-15 | Hugh V. Cottingham | Internet service provider advertising system |
US6442590B1 (en) | 1999-05-27 | 2002-08-27 | Yodlee.Com, Inc. | Method and apparatus for a site-sensitive interactive chat network |
US6147975A (en) | 1999-06-02 | 2000-11-14 | Ac Properties B.V. | System, method and article of manufacture of a proactive threhold manager in a hybrid communication system architecture |
US6349257B1 (en) | 1999-09-15 | 2002-02-19 | International Business Machines Corporation | System for personalized mobile navigation information |
US6351464B1 (en) | 1999-09-20 | 2002-02-26 | Mci Worldcom, Inc. | Virtual second line hybrid network communication system |
US6266615B1 (en) | 1999-09-27 | 2001-07-24 | Televigation, Inc. | Method and system for an interactive and real-time distributed navigation system |
WO2001033759A1 (en) | 1999-11-03 | 2001-05-10 | Avantcom Network, Inc. | Method of sharing proprietary information |
US8244635B2 (en) | 2000-04-25 | 2012-08-14 | Yodlee.Com, Inc. | System and method for syndicated collection, aggregation and delivery of personal data |
AU2001263013B2 (en) | 2000-05-09 | 2006-06-29 | Metavante Corporation | Electronic bill presentment and payment system |
US6380890B1 (en) | 2000-08-11 | 2002-04-30 | Motorola, Inc. | Information appliance system having a navigational position generator and method |
US20020082990A1 (en) | 2000-12-22 | 2002-06-27 | J.J. & Associates Inc. | Method of invoice presentation and payment |
-
1999
- 1999-10-27 AT AT00108963T patent/ATE268484T1/en not_active IP Right Cessation
- 1999-10-27 DE DE69908610T patent/DE69908610T2/en not_active Expired - Fee Related
- 1999-10-27 CN CNA001202413A patent/CN1497465A/en active Pending
- 1999-10-27 DE DE69917766T patent/DE69917766D1/en not_active Expired - Lifetime
- 1999-10-27 DE DE69919411T patent/DE69919411D1/en not_active Expired - Lifetime
- 1999-10-27 EP EP99971117A patent/EP1198765B1/en not_active Expired - Lifetime
- 1999-10-27 AT AT99971117T patent/ATE273538T1/en not_active IP Right Cessation
- 1999-10-27 BR BR9907075-8A patent/BR9907075A/en not_active Application Discontinuation
- 1999-10-27 US US09/428,511 patent/US6317783B1/en not_active Expired - Lifetime
- 1999-10-27 US US09/427,794 patent/US6567850B1/en not_active Expired - Lifetime
- 1999-10-27 JP JP2000578743A patent/JP2002528819A/en active Pending
- 1999-10-27 US US09/427,790 patent/US7552190B1/en not_active Expired - Fee Related
- 1999-10-27 AT AT00108964T patent/ATE242511T1/en not_active IP Right Cessation
- 1999-10-27 US US09/427,602 patent/US6405245B1/en not_active Expired - Lifetime
- 1999-10-27 AU AU12367/00A patent/AU737572C/en not_active Ceased
- 1999-10-27 WO PCT/US1999/025181 patent/WO2000025227A1/en active IP Right Grant
- 1999-10-27 US US09/427,811 patent/US7765279B1/en not_active Expired - Fee Related
- 1999-10-27 CA CA002306083A patent/CA2306083A1/en not_active Abandoned
- 1999-10-27 ES ES00108964T patent/ES2200753T3/en not_active Expired - Lifetime
- 1999-10-27 CN CN99801737A patent/CN1287640A/en active Pending
-
2000
- 2000-07-14 CN CN00120240A patent/CN1420445A/en active Pending
-
2003
- 2003-06-18 JP JP2003174051A patent/JP2004164573A/en not_active Withdrawn
Also Published As
Publication number | Publication date |
---|---|
US6405245B1 (en) | 2002-06-11 |
ATE268484T1 (en) | 2004-06-15 |
DE69908610T2 (en) | 2003-12-11 |
DE69919411D1 (en) | 2004-09-16 |
ES2200753T3 (en) | 2004-03-16 |
EP1198765A1 (en) | 2002-04-24 |
DE69908610D1 (en) | 2003-07-10 |
EP1198765B1 (en) | 2004-08-11 |
DE69917766D1 (en) | 2004-07-08 |
US6567850B1 (en) | 2003-05-20 |
WO2000025227A1 (en) | 2000-05-04 |
CN1420445A (en) | 2003-05-28 |
BR9907075A (en) | 2000-10-17 |
US6317783B1 (en) | 2001-11-13 |
US7552190B1 (en) | 2009-06-23 |
AU1236700A (en) | 2000-05-15 |
US7765279B1 (en) | 2010-07-27 |
AU737572C (en) | 2004-05-20 |
CN1287640A (en) | 2001-03-14 |
JP2002528819A (en) | 2002-09-03 |
AU737572B2 (en) | 2001-08-23 |
EP1198765A4 (en) | 2002-04-24 |
JP2004164573A (en) | 2004-06-10 |
ATE273538T1 (en) | 2004-08-15 |
CN1497465A (en) | 2004-05-19 |
ATE242511T1 (en) | 2003-06-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
AU737572B2 (en) | Apparatus and method for automated aggregation and delivery of and transactions involving electronic personal information or data | |
US6871220B1 (en) | System and method for distributed storage and retrieval of personal information | |
US8768833B2 (en) | System and method for syndicated transactions | |
US8260706B2 (en) | System and method for syndicated transactions | |
US7490135B2 (en) | Method for providing node targeted content in an addressable network | |
US7558795B2 (en) | Method and apparatus for tracking functional states of a Web-site and reporting results to web developers | |
AU2003204104B8 (en) | Use of Extensible Markup Language in a System and Method for Influencing a Position on a Search Result List Generated by a Computer Network Search Engine | |
EP1107125B1 (en) | Apparatus and method for automated aggregation and delivery of and transactions involving electronic personal information or data | |
CA2308246A1 (en) | System and method for automated access to personal information | |
AU4721000A (en) | Apparatus and method for automated aggregation and delivery of and transactions involving electronic personal information or data apparatus | |
AU4720900A (en) | System and method for automated access to personal information | |
JP2001147893A (en) | Device and method for automated aggregation, device and method for delivering electronic personal information or data and transaction including electronic personal information or data | |
JP2001142905A (en) | System and method for automatically accessing personal information | |
JP2001147892A (en) | Device and method for automated aggregation, device and method for delivering electronic personal information or data and transaction including electronic personal information or data | |
WO2001086543A1 (en) | System and method for syndicated transactions | |
MXPA00005913A (en) | Apparatus and method for automated aggregation and delivery of electronic personal information or data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |