Method and apparatus to perform online credential reporting

• US 9,449,195 B2
• Filed: 01/22/2010
• Issued: 09/20/2016
• Est. Priority Date: 01/23/2009
• Status: Expired due to Fees

• Current Assignee: Avuli Incorporated
• Original Assignee: Avow Networks Incorporated
• Inventors: Wineinger, Gerald William, Wineinger, Travis Jay, Coleman, Joseph Eric, Hegg, Terry James
• Primary Examiner(s): TANK, ANDREW L
• Application Number:
  US12/691,901
• Publication Number:
  US 20100192068A1
• Time in Patent Office: 2,433 Days
• Field of Search: 715/738, 715/744, 715/205, 715/835, 715853-855, 726 17- 21, 713/175
• US Class Current: 1/1
• CPC Class Codes: G06F 16/955 using information identifiers, e.g. uniform resource locators [URL]
• CPC Class Codes: G06F 16/9574 of access to content, e.g. by caching
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06F 21/645 using a third party
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/1483 service impersonation, e.g. phishing, pharming or web spoofing detection of rogue wireless access points H04W12/12
• CPC Class Codes: H04L 9/321 involving a third party or a trusted authority

Abstract

Embodiments of the invention provide a process for displaying a graphical indicator on an Internet enabled device which conveys relationships between an entity associated with a website and third party entities with respect to the website entity. One example method may include obtaining the relationship data from a credential service provider, using a portion of a uniform resource identifier as a key to access the relationship data on the credential service provider, and rendering a representation of the relationship data, wherein the rendering of the relationship data is performed in a graphical user interface of a web browser, and wherein the web browser displays a rendering of the representation of the relationship data such that there is a relationship between an entity associated with the uniform resource identifier and a third party entity.

Claims

1. A method to display relationship data, comprising:

obtaining the relationship data from a credential service provider, wherein the relationship data is a credential bestowed by an issuer entity onto a holder entity, wherein the credential is a statement made by the issuer entity about the holder entity, wherein the credential service provider is a repository of the relationship data, wherein the issuer entity provides the relationship data to the credential service provider, wherein the issuer entity, the holder entity, and the credential service provider are separate entities;

using a portion of a uniform resource identifier as a key to access the relationship data on the credential service provider, wherein the relationship comprises an existence of an issued credential between an issuer entity and the holder entity associated with the uniform resource identifier, wherein the issuer entity has provided the credential to the credential service provider for storage;

retrieving the issued credential by bypassing the holder entity and forwarding the issued credential from the credential service provider to a web browser; and

rendering a representation of the relationship data, wherein the rendering of the relationship data is performed in a graphical user interface of the web browser, and wherein the web browser displays a rendering of the representation of the relationship data such that there is a visual representation of the relationship between the issuer entity and the holder entity associated with the uniform resource identifier.

2. The method of claim 1, further comprising:

storing the relationship data via a cache engine.

3. The method of claim 2, further comprising:

analyzing tokens to control query frequency to the credential service provider.

4. The method of claim 2, further comprising:

controlling access and determining access to the credential service provider via a network dispersion engine.

5. The method of claim 1, further comprising:

analyzing tokens to control query frequency to the credential service provider via a uniqueness identifier engine.

6. The method of claim 1, further comprising:

controlling access and determining access to the credential service provider via a network dispersion engine.

7. The method of claim 1, further comprising:

determining whether a query is necessary based on a user initiated access operation, and, if so, performing the query, and, if not, determining whether there is relationship data and modifying the user interface based on the relationship data.

8. An apparatus configured to display relationship data, comprising:

a processor configured to

obtain the relationship data from a credential service provider, wherein the relationship data is a credential bestowed by an issuer entity onto a holder entity, wherein the credential is a statement made by the issuer entity about the holder entity, wherein the credential service provider is a repository of the relationship data, wherein the issuer entity provides the relationship data to the credential service provider, wherein the issuer entity, the holder entity, and the credential service provider are separate entities,

use a portion of a uniform resource identifier as a key to access the relationship data on the credential service provider, wherein the relationship comprises an existence an issued credential established between an issuer entity and the holder entity associated with the uniform resource identifier, wherein the issuer entity has provided the credential to the credential service provider for storage,

retrieve the issued credential by bypassing the holder entity and forward the issued credential from the credential service provider to a web browser;

render a representation of the relationship data, wherein the rendering of the relationship data is performed in a graphical user interface of the web browser; and

a display with a web browser configured to display a rendering of the representation of the relationship data such that there is a visual representation of the relationship between the issuer entity and the holder party entity associated with the uniform resource identifier.

9. The apparatus of claim 8, further comprising:

a cached engine configured to store the relationship data.

10. The apparatus of claim 9, wherein the processor is further configured to analyze tokens to control query frequency to the credential service provider.

11. The apparatus of claim 9, further comprising:

a network dispersion engine configured to control access and to determine access to the credential service provider.

12. The apparatus of claim 8, further comprising:

a uniqueness identifier engine configured to analyze tokens to control query frequency to the credential service provider.

13. The apparatus of claim 8, further comprising:

a network dispersion engine configured to control access and determine access to the credential service provider.

14. The apparatus of claim 8, wherein the processor is further configured to perform determining whether a query is necessary based on a user initiated access operation, and, if so, performing the query, and, if not, determining whether there is relationship data and modifying the user interface based on the relationship data.

15. A non-transitory computer readable storage medium configured to store instructions, that when executed causes a processor to perform:

obtaining relationship data from a credential service provider, wherein the relationship data is a credential bestowed by an issuer entity onto a holder entity, wherein the credential is a statement made by the issuer entity about the holder entity, wherein the credential service provider is a repository of the relationship data, wherein the issuer entity provides the relationship data to the credential service provider, wherein the issuer entity, the holder entity, and the credential service provider are separate entities;

using a portion of a uniform resource identifier as a key to access the relationship data on the credential service provider, wherein the relationship comprises an existence of an issued credential between an issuer entity and the holder entity associated with the uniform resource identifier, wherein the issuer entity has provided the credential to the credential service provider for storage;

retrieving the issued credential by bypassing the holder entity and forwarding the issued credential from the credential service provider to a web browser; and

rendering a representation of the relationship data, wherein the rendering of the relationship data is performed in a graphical user interface of the web browser, and wherein the web browser displays a rendering of the representation of the relationship data such that there is a visual representation of the relationship between the issuer entity and the holder entity associated with the uniform resource identifier.

16. The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform:

storing the relationship via a cache engine.

17. The non-transitory computer readable storage medium of claim 16, wherein the processor is further configured to perform:

analyzing tokens to control query frequency to the credential service provider.

18. The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform:

analyzing tokens to control query frequency to the credential service provider via a uniqueness identifier engine.

19. The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform:

controlling access and determining access to the credential service provider via a network dispersion engine.

20. The non-transitory computer readable storage medium of claim 15, wherein the processor is further configured to perform:

determining whether a query is necessary based on a user initiated access operation, and, if so, performing the query, and, if not, determining whether there is relationship data and modifying the user interface based on the relationship data.