Multiple URL identity syntaxes and identities

• US 7,958,266 B1
• Filed: 05/04/2009
• Issued: 06/07/2011
• Est. Priority Date: 07/30/2003
• Status: Expired due to Fees

• Current Assignee: Faraday Mew LLC
• Original Assignee: Faraday Mew LLC
• Inventors: Sun, Chen
• Primary Examiner(s): Swearingen; Jeffrey R
• Application Number:
  US12/387,545
• Time in Patent Office: 764 Days
• Field of Search: None
• US Class Current: 709/245
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06Q 10/10 Office automation; Time management

Abstract

Any arrangement of URLv identity syntax can now be used in a repository, once its second.top domain is known to have an identity syntax. The repository can extract, select, store, organize, prioritize, and consolidate URLvs of differing identity syntaxes. The correlation and association among different contact entities'"'"' containing the same individual'"'"'s identities can yield accurate same individual'"'"'s identity and URLvs. These increase the competition of the Internet by enabling users to transport their data easily to websites allowing for individuals'"'"' data-transport.

Claims

1. A method of contact management in which a first individual can input a URLv containing an identity into his or her Internet-connected contact manager, and the URLv is automatically associated with a second individual'"'"'s contact entity object containing the second individual'"'"'s other URLvs, the method steps comprising of:

providing a plurality of URLvs each containing a first second-top level domain name and a known identity of said second individual;

providing a URLv containing a second second-top level domain name and a known identity of said second individual;

providing said URLvs of said first and second second-top level domains with addressed webpages containing said second individual'"'"'s data;

providing a database of known identity syntaxes for second-top level domain names and said database contains identity syntaxes of said first and said second second-top level domain names;

providing a contact manager with contact entity objects and with a contact-manager'"'"'s URLv input field;

providing Internet-connected processors and applications to generate said URLvs'"'"' webpages and to host said database and said contact manager;

inputting a said URLv containing a said first second-top level domain name into said contact entity object;

inputting a said URLv containing a second second-top level domain name into said contact entity object;

inputting into said contact manager'"'"'s URLv input field a said URLv containing a first second-top level domain name wherein said contact manager'"'"'s inputted URLv is different from the said contact entity object'"'"'s said URLvs;

deriving URLv identities of said contact entity object'"'"'s inputted URLvs and said contact manager'"'"'s inputted URLvs based on said database of known identity syntaxes; and

associating said contact manager'"'"'s inputted URLv to the said contact entity object containing said same URLv identity;

wherein said contact manager automatically associates URLvs inputted in said contact manager to said same second individual'"'"'s contact entity object containing differing second-top level domain names.

2. The method of claim 1, further comprising:

said contact-manager'"'"'s inputted URLv is further automatically inputted into said associated contact entity object;

wherein said first individual inputs a said URLv into said contact manager'"'"'s input URLv field, and said contact manager will automatically places said URLv into said contact entity object with same said second individual'"'"'s other URLvs.

3. The method of claim 2, further comprising:

said contact entity object'"'"'s inputted URLvs are web accessible, and the second individual'"'"'s data is extracted, consolidated, and presented as data fields within the contact entity object;

wherein said first individual saves time by simply inputting only URLvs into said contact manager'"'"'s URLv input box, and said contact manager automatically populates fields in a contact entity object and presents said fields in a contact entity object in a compact format, without said first individual having to search for said second individual'"'"'s contact entity object in said contact manager.

4. The method of claim 1, further comprising:

providing a plurality of Internet-connected contact managers each containing probabilistic URLv identity syntaxes;

providing a threshold that determines when multiple probabilistic URLv identity syntaxes become known URLv identity syntax;

establishing said known identity syntax using probabilistic and statistical methods applied to said contact managers'"'"' probabilistic identity syntaxes, and then exceeding said threshold that determines when multiple probabilistic URLv identity syntaxes become a known URLv identity syntax; and

adding said established known identity syntax to said known identity syntax database;

wherein said known identity syntax database is updated regularly by multiple individual'"'"'s contact managers.

5. The method of claim 1, wherein said identity syntaxes include encoded identity syntaxes.

6. The method of claim 2, wherein said identity syntaxes include encoded identity syntaxes.

7. The method of claim 3, wherein said identity syntaxes include encoded identity syntaxes.

8. The method of claim 4, wherein said identity syntaxes include encoded identity syntaxes.

9. The method of claim 1, wherein said identity syntaxes includes an identity syntax for a subidentity.

10. The method of claim 2, wherein said identity syntaxes includes an identity syntax for a subidentity.

11. The method of claim 3, wherein said identity syntaxes includes an identity syntax for a subidentity.

12. The method of claim 4, wherein said identity syntaxes includes an identity syntax for a subidentity.

13. The method of claim 1, wherein said identity syntaxes in said known identity syntax database consist of known identities and wherein the step of deriving the URLv identities of said contact entity object'"'"'s inputted URLvs and said contact manager'"'"'s inputted URLvs is based on said known identities in the database of identity syntaxes.

14. The method of claim 2, wherein said identity syntaxes in said known identity syntax database consist of known identities and wherein the step of deriving the URLv identities of said contact entity object'"'"'s inputted URLvs and said contact manager'"'"'s inputted URLvs is based on said known identities in the database of identity syntaxes.

15. The method of claim 3, wherein said identity syntaxes in said known identity syntax database consist of known identities and wherein the step of deriving the URLv identities of said contact entity object'"'"'s inputted URLvs and said contact manager'"'"'s inputted URLvs is based on said known identities in the database of identity syntaxes.

16. The method of claim 4, further comprising:

wherein said identity syntaxes in said known identity syntax database consist of known identities;

wherein the step of deriving the URLv identities of said contact entity object'"'"'s inputted URLvs and said contact manager'"'"'s inputted URLvs is based on said known identities in the database of identity syntaxes;

wherein said probabilistic URLv identity syntaxes in said Internet-connected contact managers each contain probabilistic URLv identities;

wherein said threshold determines when multiple probabilistic identities become known identity syntax, wherein said known identity syntax is a known identity;

wherein the step of establishing a said known identity syntax establishes a known identity using probabilistic and statistical methods applied to probabilistic identities in said contact manager'"'"'s identity syntaxes; and

wherein the step of adding said established known identity syntax to said known identity syntax database adds said known identity syntax, to said known identity syntax database, wherein said known identity syntax consists of said established known identity.