US20060224514A1 - Method and system for managing web profile information - Google Patents
Method and system for managing web profile information Download PDFInfo
- Publication number
- US20060224514A1 US20060224514A1 US11/393,926 US39392606A US2006224514A1 US 20060224514 A1 US20060224514 A1 US 20060224514A1 US 39392606 A US39392606 A US 39392606A US 2006224514 A1 US2006224514 A1 US 2006224514A1
- Authority
- US
- United States
- Prior art keywords
- user
- user profile
- profile
- provider site
- central storage
- 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
Images
Classifications
-
- 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/06—Buying, selling or leasing transactions
Definitions
- the present invention is directed to web profile information, and more particularly to a method and system for managing web profile information.
- This information may include name, address, birth date, e-mail details et cetera.
- registration information may include name, address, birth date, e-mail details et cetera.
- each web site has a slightly different registration form and each time it is necessary to manually fill in the form.
- One object of the present invention is to overcome at least some of the problems associated with the prior art and provide a method and system for managing web profile information.
- the present invention discloses a method of managing web profile information comprising the steps of:
- the present invention discloses a system of managing web profile information comprising:
- the user needs only add profile information once at a central storage location. This avoids the need for multiple and repetitive entry of information.
- the user needs to change any profile information it is merely necessary to connect to the central storage location and update that rather than a multitude of individual locations such as merchant sites etc.
- FIG. 1 is a diagram showing how a user profile is created in accordance with the present invention.
- FIG. 2 is a diagram showing user profile retrieval by a third party.
- FIG. 3 is a diagram showing a web profile update process.
- FIG. 4 is a flow chart showing the method of the present invention.
- a web user 110 is connected via appropriate means (not shown) to a web page 112 .
- the web page 112 is that of a profile provider 114 .
- the web user 110 connects to the web page 112 in order to either enroll and create a profile, update and maintain a profile, or delete a profile.
- ID login identification
- password password
- the personal data entered by the web user 110 will include the following list, which is by way of example only and may include more or less data as appropriate. Some of the data may be essential and some may be optional.
- the data may include the following:
- the user profile may not always relate to a customer, but may relate to an object for example a car.
- car details may be stored and used to populate an insurance provider's profile form and a garage profile form.
- An individual may have a user profile which includes different sections which can individually or in combination be used to populate a provider profile form.
- the user profile may only be accessed by the web user 110 using the login and password; an administrator if the web user 110 loses the login and/or password; and a merchant web site (details to be described below). If the administrator needs to access the profile the web user 110 will be asked a number of questions including certain security questions, as is well known in the art.
- the web user 210 accesses a merchant web site 212 with the intention of purchasing something.
- the merchant web site 212 has an ability to link to the profile provider 214 (same as profile provider 114 , FIG. 1 ), but can only receive information from the profile provider 214 if certain conditions are met.
- the web user 210 makes a profile retrieval request 216 through a selection on the merchant web site 212 .
- the merchant web site 212 may have an optional merchant authentication process 218 which links the merchant web site 212 to certain information at the profile provider 214 .
- There will also be an authentication process 220 for the web user 210 which requires an entry of one or more of a login ID; a password; authentication information; a security question and answers, etc.
- the user profile 224 is transferred 222 from the profile provider 214 to the merchant web site 212 .
- the user profile 224 can then be used to populate the profile requirements of the merchant web site 212 .
- the profile information is thus provided to the merchant web site 212 without any data entry from the web user 210 .
- a record is maintained at the profile provider 214 of all merchant web sites 212 which have a certain user profile 224 .
- the web user 310 (same as web user 110 ( FIG. 1 ) and 210 ( FIG. 2 )) wishes to update some or all of their user profile, i.e., a new address, bank detail, etc.
- the web user 310 need only connect to the web page 312 (same as web page 112 , FIG. 1 ) of the profile provider 314 (same as profile provider 114 ( FIG. 1 ) and 214 ( FIG. 2 )).
- the web user 310 may update the profile information. This information is then sent 316 from the profile provider 314 to each merchant web site 318 and 320 in FIG. 3 .
- the updates will be sent to as many live merchant web sites as are known to have previously received the given user profile. If the user has accessed the profile provider 314 to delete the user profile, the update to the merchant web sites may include either a request to delete the user profile or an update of the user profile with empty fields.
- a web user logs onto a web page belonging to a profile provider, step 410 .
- the web user then enters profile information including login and password details on the web page, step 412 .
- the user enters a web page of a merchant site in order to purchase a product, step 416 .
- the user requests the merchant site to connect to the profile provider to retrieve user profile information, step 418 .
- An authentication process occurs between the merchant site and the profile provider (optional) and between the user and the profile provider via the merchant site, step 420 .
- Once authentication has been confirmed the user profile is downloaded from profile provider to the merchant site, without the user needing to enter the information in the user profile of the merchant site, step 422 .
- the user may re-enter the profile provider web page to make changes to the user profile, step 424 .
- Authentication process occurs, step 426 and then the user profile is updated, step 428 .
- the updated user profile is then sent to any merchant site which has previously had the user profile, step 430 .
- an appropriate authentication process is included in step 430 .
- the present invention has been described in the context of web pages but may equally apply to any place where a user may be required to enter profile information, e.g., a phone or other pda device connected to a provider of some sort.
- the provider may not be a merchant, but may instead be another type of provider, e.g., services, information storage, etc.
Abstract
A method and system for providing, storing and managing a user profile. A user profile is originally stored in a central storage repository which can then be accessed by many different providers. After appropriate authentication the user profile can then be downloaded to the provider sites. This means a user does not have to enter their details many times when accessing and using different providers.
Description
- The present invention is directed to web profile information, and more particularly to a method and system for managing web profile information.
- Whenever a user accesses a web page it is generally necessary to complete certain registration information. This information may include name, address, birth date, e-mail details et cetera. Usually each web site has a slightly different registration form and each time it is necessary to manually fill in the form.
- As the user may fill in many registrations it is possible that the user will lose track of some or all of the registration details. In addition, if the user changes any details it is necessary to remember all the registrations and correct the information on each.
- One object of the present invention is to overcome at least some of the problems associated with the prior art and provide a method and system for managing web profile information.
- More particularly the present invention discloses a method of managing web profile information comprising the steps of:
- storing a user profile on a central storage repository,
- providing web access to the central storage repository from a provider site,
- authenticating a connection between the provider site and the central storage repository in which the provider site requests a download of the user profile, and
- downloading the user profile to the provider site.
- More particularly the present invention discloses a system of managing web profile information comprising:
- a system for storing a user profile on a central storage repository,
- a system for providing web access to the central storage repository from a provider site,
- a system for authenticating a connection between the provider site and the central storage repository in which the provider site requests a download of the user profile, and
- a system for downloading the user profile to the provider site.
- Advantages of the present invention are set out below. The user needs only add profile information once at a central storage location. This avoids the need for multiple and repetitive entry of information. In addition, if the user needs to change any profile information it is merely necessary to connect to the central storage location and update that rather than a multitude of individual locations such as merchant sites etc.
- Reference will now be made, by way of example, to the accompanying drawings, in which:
-
FIG. 1 is a diagram showing how a user profile is created in accordance with the present invention. -
FIG. 2 is a diagram showing user profile retrieval by a third party. -
FIG. 3 is a diagram showing a web profile update process. -
FIG. 4 is a flow chart showing the method of the present invention. - Referring initially to
FIG. 1 , aweb user 110 is connected via appropriate means (not shown) to aweb page 112. Theweb page 112 is that of aprofile provider 114. Theweb user 110 connects to theweb page 112 in order to either enroll and create a profile, update and maintain a profile, or delete a profile. - The first time the
web user 110 accesses theweb page 112 it will be necessary to enroll and create a user profile. This will involve entering personal data as identified below including setting up a login identification (ID) and a password. - At subsequent visits to the
web page 112 it will be necessary to always enter the login ID and the password before access is given to the user profile. The user profile can then be easily amended or deleted as appropriate by theweb user 110. - The personal data entered by the
web user 110 will include the following list, which is by way of example only and may include more or less data as appropriate. Some of the data may be essential and some may be optional. - The data may include the following:
- Name
- Address
- Telephone Number
- Mobile Number
- Fax Number
- E-mail
- Gender
- Age
- Date of birth
- Authentication information (the purpose of this is described in further detail below)
- Security questions and answers
- Bank or credit card details
- Possible delivery addresses
- Demographic information
- Interests/hobbies etc
- The user profile may not always relate to a customer, but may relate to an object for example a car. In this case car details may be stored and used to populate an insurance provider's profile form and a garage profile form. An individual may have a user profile which includes different sections which can individually or in combination be used to populate a provider profile form.
- Once the
web user 110 has set up the user profile, the user profile may only be accessed by theweb user 110 using the login and password; an administrator if theweb user 110 loses the login and/or password; and a merchant web site (details to be described below). If the administrator needs to access the profile theweb user 110 will be asked a number of questions including certain security questions, as is well known in the art. - Referring now to
FIG. 2 , the web user 210 (same asweb user 110,FIG. 1 ) accesses amerchant web site 212 with the intention of purchasing something. Themerchant web site 212 has an ability to link to the profile provider 214 (same asprofile provider 114,FIG. 1 ), but can only receive information from theprofile provider 214 if certain conditions are met. - The
web user 210 makes aprofile retrieval request 216 through a selection on themerchant web site 212. Themerchant web site 212 may have an optionalmerchant authentication process 218 which links themerchant web site 212 to certain information at theprofile provider 214. There will also be anauthentication process 220 for theweb user 210 which requires an entry of one or more of a login ID; a password; authentication information; a security question and answers, etc. - Once the authentication process or processes have been successfully completed, the user profile 224 is transferred 222 from the
profile provider 214 to themerchant web site 212. The user profile 224 can then be used to populate the profile requirements of themerchant web site 212. The profile information is thus provided to themerchant web site 212 without any data entry from theweb user 210. A record is maintained at theprofile provider 214 of allmerchant web sites 212 which have a certain user profile 224. - Referring now to
FIG. 3 , an update mechanism is now described. If the web user 310 (same as web user 110 (FIG. 1 ) and 210 (FIG. 2 )) wishes to update some or all of their user profile, i.e., a new address, bank detail, etc., theweb user 310 need only connect to the web page 312 (same asweb page 112,FIG. 1 ) of the profile provider 314 (same as profile provider 114 (FIG. 1 ) and 214 (FIG. 2 )). At theweb page 312, after appropriate user authentication, theweb user 310 may update the profile information. This information is then sent 316 from theprofile provider 314 to eachmerchant web site FIG. 3 . The updates will be sent to as many live merchant web sites as are known to have previously received the given user profile. If the user has accessed theprofile provider 314 to delete the user profile, the update to the merchant web sites may include either a request to delete the user profile or an update of the user profile with empty fields. - Referring now to
FIG. 4 the steps that occur in the present invention are now described. A web user logs onto a web page belonging to a profile provider,step 410. - The web user then enters profile information including login and password details on the web page,
step 412. This creates a user profile which is stored on the profileprovider server step 414. - At a later time the user enters a web page of a merchant site in order to purchase a product,
step 416. The user requests the merchant site to connect to the profile provider to retrieve user profile information,step 418. An authentication process occurs between the merchant site and the profile provider (optional) and between the user and the profile provider via the merchant site,step 420. Once authentication has been confirmed the user profile is downloaded from profile provider to the merchant site, without the user needing to enter the information in the user profile of the merchant site,step 422. - At a still later time (maybe many months or more) the user may re-enter the profile provider web page to make changes to the user profile,
step 424. Authentication process occurs,step 426 and then the user profile is updated,step 428. The updated user profile is then sent to any merchant site which has previously had the user profile,step 430. Obviously an appropriate authentication process is included instep 430. The present invention has been described in the context of web pages but may equally apply to any place where a user may be required to enter profile information, e.g., a phone or other pda device connected to a provider of some sort. The provider may not be a merchant, but may instead be another type of provider, e.g., services, information storage, etc. - While the invention has been particularly shown and described with reference to a preferred embodiment, it will be understood that various changes in form and detail may be made therein without departing from the spirit and the scope of the invention.
Claims (14)
1. A method of managing web profile information comprising the steps of:
storing a user profile on a central storage repository,
providing web access to the central storage repository from a provider site,
authenticating a connection between the provider site and the central storage repository in which the provider site requests a download of the user profile, and
downloading the user profile to the provider site.
2. The method of claim 1 , wherein the step of authenticating the connection comprises entering user authentication data via the provider site to authenticate the provider site with respect to the user.
3. The method of claim 1 , further comprising providing profile information in the user profile in a form of a plurality of pieces of personal information.
4. The method of claim 1 , wherein the downloading step comprises downloading the user profile to the provider site to populate a provider site user profile.
5. The method of claim 1 , further comprising updating the user profile via access to the central storage repository and sending the updated user profile to the provider site.
6. The method of claim 1 , further comprising authenticating a connection between a plurality of provider sites and the central storage repository to allow download of the user profile to all authenticated provider sites.
7. The method of claim 1 , wherein the authenticating step comprises:
at a first access to the central storage repository entering a user identification and a password; storing the user identification and the password at the central storage repository; and
at a later access to the central storage repository entering an entered user identification and an entered password via either the provider site or directly comparing the entered user identification and password with the user identification and the password stored at the central repository.
8. A system of managing web profile information comprising:
a system for storing a user profile on a central storage repository,
a system for providing web access to the central storage repository from a provider site,
a system for authenticating a connection between the provider site and the central storage repository in which the provider site requests a download of the user profile, and
a system for downloading the user profile to the provider site.
9. The system of claim 8 , wherein the authenticating system further includes a system for entering user authentication data via the provider site to authenticate the provider site with respect to the user.
10. The system of claim 8 , further comprising a system for providing profile information in the user profile in a form of a plurality of pieces of personal information.
11. The system of claim 8 , wherein the system for downloading further comprises a system for downloading the user profile to the provider site to populate a provider site user profile.
12. The system of claim 8 , further comprising a system for updating the user profile via access to the central storage repository and a system for sending the updated user profile to the provider site.
13. The system of claim 8 , further comprising a system for authenticating a connection between a plurality of provider sites and the central storage repository to allow download of the user profile to all authenticated provider sites.
14. The system of claim 8 , wherein the system for authenticating further comprises:
a system for entering a user identification and a password at a first access to the central storage repository; a system for storing the user identification and the password at the central storage repository; and
a system for entering an entered user identification and an entered password at a later access to the central storage repository via either the provider site or for directly comparing the entered user identification and password with the user identification and the password stored at the central repository.
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP05368010.4 | 2005-03-31 | ||
EP05368010 | 2005-03-31 |
Publications (1)
Publication Number | Publication Date |
---|---|
US20060224514A1 true US20060224514A1 (en) | 2006-10-05 |
Family
ID=37030411
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/393,926 Abandoned US20060224514A1 (en) | 2005-03-31 | 2006-03-30 | Method and system for managing web profile information |
Country Status (2)
Country | Link |
---|---|
US (1) | US20060224514A1 (en) |
CN (1) | CN1841393B (en) |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090049070A1 (en) * | 2007-08-15 | 2009-02-19 | Arieh Steinberg | Web-based social network badges |
US20100057742A1 (en) * | 2008-08-28 | 2010-03-04 | Visa Usa, Inc. | Mrw interface and method for support of merchant data processing |
US20100057786A1 (en) * | 2008-08-28 | 2010-03-04 | Visa Usa, Inc. | Acquirer device and method for support of merchant data processing |
US20100058156A1 (en) * | 2008-08-28 | 2010-03-04 | Visa Usa, Inc. | Ftp device and method for merchant data processing |
US20100077464A1 (en) * | 2008-09-23 | 2010-03-25 | Visa Usa, Inc. | Merchant device and method for support of merchant data processing |
US20140149243A1 (en) * | 2012-11-29 | 2014-05-29 | Red Hat, Inc. | Vendor download integration |
US9092390B1 (en) | 2010-07-23 | 2015-07-28 | Google Inc. | Electronic badge clearinghouse |
US20160285884A1 (en) * | 2015-03-27 | 2016-09-29 | Accenture Global Services Limited | Configurable sharing of user information |
US10269077B2 (en) | 2014-06-09 | 2019-04-23 | Visa International Service Association | Systems and methods to detect changes in merchant identification information |
Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5729735A (en) * | 1995-02-08 | 1998-03-17 | Meyering; Samuel C. | Remote database file synchronizer |
US5754938A (en) * | 1994-11-29 | 1998-05-19 | Herz; Frederick S. M. | Pseudonymous server for system for customized electronic identification of desirable objects |
US5790935A (en) * | 1996-01-30 | 1998-08-04 | Hughes Aircraft Company | Virtual on-demand digital information delivery system and method |
US6298228B1 (en) * | 1998-11-12 | 2001-10-02 | Ericsson Inc. | Lazy updates of profiles in a system of communication devices |
US20020165967A1 (en) * | 2001-05-02 | 2002-11-07 | Morgan Paul A. | Global personalization engine |
US6584505B1 (en) * | 1999-07-08 | 2003-06-24 | Microsoft Corporation | Authenticating access to a network server without communicating login information through the network server |
US6587867B1 (en) * | 1997-05-22 | 2003-07-01 | Mci Communications Corporation | Internet-based subscriber profile management of a communications system |
US20040064480A1 (en) * | 2002-07-19 | 2004-04-01 | Bartlett Troy L. | System and method for utilizing profile information |
US20040198386A1 (en) * | 2002-01-16 | 2004-10-07 | Dupray Dennis J. | Applications for a wireless location gateway |
US20050132024A1 (en) * | 2003-12-15 | 2005-06-16 | Masayuki Habaguchi | Method and system for facilitating the exchange of information between a vehicle and a remote location |
US6944677B1 (en) * | 2000-05-09 | 2005-09-13 | Aspect Communications Corporation | Common user profile server and method |
US20060020530A1 (en) * | 2000-02-14 | 2006-01-26 | Hsu Phillip K | Systems for providing financial services |
US20060031114A1 (en) * | 1999-09-22 | 2006-02-09 | Oleg Zommers | Interactive personal information system and method |
US7020696B1 (en) * | 2000-05-20 | 2006-03-28 | Ciena Corp. | Distributed user management information in telecommunications networks |
US7027801B1 (en) * | 2001-02-06 | 2006-04-11 | Nortel Networks Limited | Method delivering location-base targeted advertisements to mobile subscribers |
-
2006
- 2006-02-13 CN CN2006100042762A patent/CN1841393B/en not_active Expired - Fee Related
- 2006-03-30 US US11/393,926 patent/US20060224514A1/en not_active Abandoned
Patent Citations (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5754938A (en) * | 1994-11-29 | 1998-05-19 | Herz; Frederick S. M. | Pseudonymous server for system for customized electronic identification of desirable objects |
US5754939A (en) * | 1994-11-29 | 1998-05-19 | Herz; Frederick S. M. | System for generation of user profiles for a system for customized electronic identification of desirable objects |
US5729735A (en) * | 1995-02-08 | 1998-03-17 | Meyering; Samuel C. | Remote database file synchronizer |
US5790935A (en) * | 1996-01-30 | 1998-08-04 | Hughes Aircraft Company | Virtual on-demand digital information delivery system and method |
US6587867B1 (en) * | 1997-05-22 | 2003-07-01 | Mci Communications Corporation | Internet-based subscriber profile management of a communications system |
US6298228B1 (en) * | 1998-11-12 | 2001-10-02 | Ericsson Inc. | Lazy updates of profiles in a system of communication devices |
US6584505B1 (en) * | 1999-07-08 | 2003-06-24 | Microsoft Corporation | Authenticating access to a network server without communicating login information through the network server |
US20060031114A1 (en) * | 1999-09-22 | 2006-02-09 | Oleg Zommers | Interactive personal information system and method |
US20060020530A1 (en) * | 2000-02-14 | 2006-01-26 | Hsu Phillip K | Systems for providing financial services |
US6944677B1 (en) * | 2000-05-09 | 2005-09-13 | Aspect Communications Corporation | Common user profile server and method |
US7020696B1 (en) * | 2000-05-20 | 2006-03-28 | Ciena Corp. | Distributed user management information in telecommunications networks |
US7027801B1 (en) * | 2001-02-06 | 2006-04-11 | Nortel Networks Limited | Method delivering location-base targeted advertisements to mobile subscribers |
US20020165967A1 (en) * | 2001-05-02 | 2002-11-07 | Morgan Paul A. | Global personalization engine |
US20040198386A1 (en) * | 2002-01-16 | 2004-10-07 | Dupray Dennis J. | Applications for a wireless location gateway |
US20040064480A1 (en) * | 2002-07-19 | 2004-04-01 | Bartlett Troy L. | System and method for utilizing profile information |
US20050132024A1 (en) * | 2003-12-15 | 2005-06-16 | Masayuki Habaguchi | Method and system for facilitating the exchange of information between a vehicle and a remote location |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090049070A1 (en) * | 2007-08-15 | 2009-02-19 | Arieh Steinberg | Web-based social network badges |
WO2009023735A1 (en) * | 2007-08-15 | 2009-02-19 | Facebook, Inc. | Web-based social network badges |
US8527474B2 (en) * | 2008-08-28 | 2013-09-03 | Visa Usa, Inc. | Acquirer device and method for support of merchant data processing |
US20100057786A1 (en) * | 2008-08-28 | 2010-03-04 | Visa Usa, Inc. | Acquirer device and method for support of merchant data processing |
US20100058156A1 (en) * | 2008-08-28 | 2010-03-04 | Visa Usa, Inc. | Ftp device and method for merchant data processing |
US20100057742A1 (en) * | 2008-08-28 | 2010-03-04 | Visa Usa, Inc. | Mrw interface and method for support of merchant data processing |
US8744998B2 (en) | 2008-08-28 | 2014-06-03 | Visa Usa, Inc. | FTP device and method for merchant data processing |
US20100077464A1 (en) * | 2008-09-23 | 2010-03-25 | Visa Usa, Inc. | Merchant device and method for support of merchant data processing |
US9092390B1 (en) | 2010-07-23 | 2015-07-28 | Google Inc. | Electronic badge clearinghouse |
US20140149243A1 (en) * | 2012-11-29 | 2014-05-29 | Red Hat, Inc. | Vendor download integration |
US10269077B2 (en) | 2014-06-09 | 2019-04-23 | Visa International Service Association | Systems and methods to detect changes in merchant identification information |
US10817957B2 (en) | 2014-06-09 | 2020-10-27 | Visa International Services Association | Systems and methods to detect changes in merchant identification information |
US20160285884A1 (en) * | 2015-03-27 | 2016-09-29 | Accenture Global Services Limited | Configurable sharing of user information |
US9825962B2 (en) * | 2015-03-27 | 2017-11-21 | Accenture Global Services Limited | Configurable sharing of user information |
Also Published As
Publication number | Publication date |
---|---|
CN1841393A (en) | 2006-10-04 |
CN1841393B (en) | 2012-08-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20060224514A1 (en) | Method and system for managing web profile information | |
US11601550B1 (en) | Methods and systems for customizing interactive voice response calls | |
US20230122616A1 (en) | Initiating direct session with bank access control server in a user verification process | |
US9928508B2 (en) | Single sign-on for access to a central data repository | |
US10055747B1 (en) | Consumer Portal | |
US8255978B2 (en) | Verified personal information database | |
US7484001B2 (en) | Method and apparatus for integrating distributed shared services system | |
JP4864871B2 (en) | Ordering method for mobile radio network users | |
US20090030718A1 (en) | System and method for automatic acquisition and distribution of information in a real estate context | |
US20080249938A1 (en) | System and method for merchant discovery and transfer of payment data | |
US20020023108A1 (en) | Automatic web form interaction proxy | |
US20080120507A1 (en) | Methods and systems for authentication of a user | |
US8682806B1 (en) | Computer based job application via SMS message or mobile email | |
US11196857B1 (en) | Methods and systems for authenticating a user on a call | |
US8668139B2 (en) | Method of protecting an individual's privacy when providing service based on electronic tag | |
CN102160067A (en) | Data communication method | |
EP1710743A1 (en) | A method and system for managing web profile information | |
KR20190109804A (en) | Apparatus and method of car calling service in autonomous vehicle | |
US20030172287A1 (en) | Methods and apparatus for providing security for a resource | |
JP3860555B2 (en) | Program providing method, member service subscription method, member service providing method, and program issuing server | |
JP7470159B2 (en) | System and method for managing user registrations based on integrated authentication between systems | |
US20020013746A1 (en) | Method and system of uniquely identifying real estate | |
JP7370414B1 (en) | User information update system, user information update method, and program | |
KR20070092391A (en) | System and method for providing unfaced channel user interface by using nickname and recording medium | |
Appiah-Nyamekye | West Africa Election Observers’ Network (WAEON)-Why technology? |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:BUSCHI, GIOVANNI;COULOMB, BEATRICE;GIBAULT, DIMITRIS;AND OTHERS;REEL/FRAME:017828/0302 Effective date: 20060303 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |