Universal relationships, system and method to build and operate a repository to manage and share trusted information of entities and their relationships

• US 9,491,192 B2
• Filed: 07/08/2014
• Issued: 11/08/2016
• Est. Priority Date: 07/08/2014
• Status: Active Grant

• Current Assignee: Universal Relationships LLC
• Original Assignee: Antunes, Marcio Veloso
• Inventors: Antunes, Marcio Veloso
• Primary Examiner(s): AVERY, JEREMIAH L
• Application Number:
  US14/325,379
• Publication Number:
  US 20160014109A1
• Time in Patent Office: 854 Days
• Field of Search: None
• US Class Current: 1/1
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 63/1441 Countermeasures against malicious traffic countermeasures against attacks on cryptographic mechanisms H04L9/002

Abstract

A computer system that registers entities, their relationship, and information related to the relationship. The related information is maintained only by its issuer and read access may be given to related entities. One entity can share with other entities the read access to information granted to it through the relationships it establishes with other entities. When an entity shares information, it gives another entity read access to the information at its source, maintained only by its issuer, without changes. For example, an entity shares its phone number and educational background with some company. The company entity may access all information shared by the entity, and can be sure the information is reliable since it is maintained and shared by its issuer. The phone number will be informed by the phone company and educational background information by each educational institute related to the entity that shared the information.

Claims

1. A method to build a computer system composed by client devices and servers programmed to store relationships between entities and permit the sharing of generated information that is official and legitimate only, preventing the generation and sharing of unofficial or illegitimate information, comprising:

(a) said servers are programmed to authenticate and authorize said entities to access said computer system using said client devices;

(b) said servers are programmed to accept and validate credentials sent by said client devices, through a message exchange process, in order to identify an entity solely among said entities;

(c) said credentials must be formed at least by username and password pair in order to identify solely one of said entities;

(d) said servers stores descriptions of types of generated information, types of relationships, and types of entities;

(e) said servers are programmed to store a set of rules that define which said types of entities are allowed to establish which said types of relationships;

(f) said set of rules encompass also the definition of each type of generated information that may be issued by each type of entity in each type of relationship in which said entity is involved;

(g) said types of entities must encompass at least;

person, government, and enterprise;

(h) said types of relationships must encompass at least;

parental, employment, citizenship, marital, delegation, and legal guardian;

(i) said types of generated information must encompass at least;

username, password, date of birth, social security number, nationality, name, birth name, job title;

(j) said servers are programmed to store also information that defines said entities, information that defines said relationships, and said generated information;

(k) said servers are programmed to provide an interface to said client devices that allows said entities, after said authenticate and authorize process, to establish said relationships, store said generated information, maintain said generated information and share said generated information;

(l) said generated information is related to said relationships;

(m) said interface must encompass at least http protocol;

(n) said servers are programmed to allow said generated information can only be modified by its own issuer entity, and said issuer entity may share only read access rights to said generated information to a related entity through said relationships;

(o) said servers are programmed to allow said related entity to share said read access rights to said generated information to a third related entity, through an established relationship between them, by its own desire without need any intervention of said issuer entity;

(p) said servers are programmed to allow said related entity to revoke said read access rights granted to said third related entity;

(q) said servers are programmed to allow said issuer entity to revoke said read access rights granted to said related entity;

(r) said entity using his/her own client device, sends a relationship invitation for the establishment of a said relationship to an invited entity, said invited entity may accept or refuse said relationship invitation;

(s) the delegation relationship type empowers a delegated entity to represent a represented entity in managing its said relationships and said generated information on behalf of said represented entity, each said relationship invitation sent to said represented entity will be redirected to said delegated entity;

(t) the legal guardian relationship type empowers a guardian entity to authorize or not authorize the establishment of said relationships whenever guarded entity is about to establish said relationships, each said relationship invitation sent to said guarded entity must be approved by said guardian entity before being delivered to said guarded entity.