Abstract:
The invention relates to data bases for storing and handling data of individuals and organizations, architecture ((graphical) user interfaces, engines) of and methods for operating such databases, (graphical) interfaces suited for use of such data -bases and methods and underlying technology and related software.

Description:
FIELD OF THE INVENTION 
       [0001]    The invention relates to data bases for storing and handling data of individuals and organizations, architecture ((graphical) user interfaces, engines) of and methods for operating such databases, (graphical) interfaces suited for use of such databases and methods and underlying technology and related software. 
       BACKGROUND OF THE INVENTION 
       [0002]    An individual has individual information such as (contact) data (address information, mobile number(s), email address(es), . . . ). An individual his or her individual information may comprise of many different properties/values/features. The wish to share those properties may depend from property to property and also from the class of persons/organization with whom such property may be shared. 
         [0003]    Database get filled with information either by entry of information by the related individual, and/or by entry of information of an individual by another, and/or by (massive) entry of information from other databases. This uncoordinated entry may lead to consistency issues and/or inefficient entry if no optimal use of already available information is made. Moreover many of the features (like country, city or street name) are not unique to a single individual/organizations (typically it is the set of features which are unique) while other databases with high quality information about those features exist. 
         [0004]    Moreover handling of databases with individual information becomes more and more regulated from the perspective of privacy via privacy law. 
       Aim of the Invention 
       [0005]    The invention provides technological solutions curing the above mentioned problems, more in particular a database structure or system design (subsequently implemented in software) and related use methods, build on a well selected underlying concept, the use thereof with a dedicated application. 
       SUMMARY OF THE INVENTION 
       [0006]    In a first aspect of the invention a database for storing and handling data of individuals is provided wherein an individual can choose for each property (or group of properties) to assign or relate an attribute/context (such as professional, personal, . . . ) and can further choose (at the time of entry and/or upon request) based on such attribute to make this property accessible for, everybody (public), a predefined class(es) of others (selective public) or even to no one (private). 
         [0007]    In a second aspect of the invention a database for storing and handling of data of individuals is provided, wherein use of high quality information (meta-data) from other databases for non-unique and even unique features might be used. 
         [0008]    In a third aspect of the invention various methods for (smart) entry/adding of information to a database for storing and handling information of individuals (such as but not limited to the databases of the first and/or second aspect of the invention) in a manner compliant with privacy law by establishing a suitable sharing (privacy by design) and also communication flow between the parties involved (the individual whose data is entered, the individual entering which may be the same or another individual, the organizations using and/or willing to share information for the database). 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0009]    The accompanying drawings are used to illustrate presently preferred non-limiting exemplary embodiments of the present invention. The above and other advantages of the features and objects of the invention will become more apparent and the invention will be better understood from the following detailed description when read in conjunction with the accompanying drawings. 
           [0010]      FIG. 1  shows the underlying concept of the invention and more in particular the graph (node, relationship) representation thereof. 
           [0011]      FIG. 2  shows an exemplary embodiment of  FIG. 1 . 
           [0012]      FIG. 3  shows a use of the concept of  FIG. 1  in terms of individuals and contacts. 
           [0013]      FIG. 4  shows the application of the concept of  FIG. 3 . 
           [0014]      FIG. 5  shows an exemplary embodiment of the application of  FIG. 4 . 
           [0015]      FIG. 6  illustrates that the concept can be adapted for use of data values residing in another system. 
           [0016]      FIGS. 7-12  demonstrate the privacy policy implementation in the graph based embodiment of the invented database. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0017]    The application incorporates by reference U.S. provisional US 62/030242 application in its entirety. 
         [0018]    The invention relates to databases for storing, handling, managing data/information of an individual, such as address information, whereby such database is suitable for on-line access. The database is adapted for use by individuals and organizations such as companies. Various applications and/or individual-organization relationships have an underlying application and/or relationship specific database. The invention relates to a generic database, usable for a plurality of application and/or relationships, and able to tune for each of said applications and relationships the required necessities such as the information to be shared (made accessible) or not. The invention relates to technology supportive for such databases, such as a graph based approach. With database is meant any computer system or systems with storage means (computer memories of various kinds) and related technology and software for handling any of the data stored thereon. 
         [0019]    The use of a kind of virtually (the hardware implementation is unrelated thereto) central database linking to various applications leads to a dynamic context wherein the data is life/active/dynamic meaning if changed it is visible everywhere where the related user wanted it to be visible and/or changed. The use of such central database is supported by various possible ways of entry of information either in the excepted way by the data owner him or herself but also by a scheme of inviting or by importing or by making suggestions or requesting. The use of such central database requires trust in the system and therefore methods to clean the data by use of trusted databases and also ensuring privacy by design by only providing access to certain data features in full accordance with the policy that a user sets is foreseen. In essence the user remains owner of his data and controls the data fields governing the access and that user get supported in setting such data fields for instance when receiving requests and/or request confirmations. 
         [0020]    In essence the invention provides concepts and methods overcoming the problems of having lack of context and/or having lack of control/verification possibilities when only considering data values on their own but instead understanding that the relationships therein between are defining one or more contexts which can be used to identify/search/find a person, create suggestion possibilities, define control/verification (either implicit or explicit) and sharing possibilities. 
         [0021]    While the invention provides lots of flexibility to the user to define this profile ( 100 ) (defined as a selection of properties ( 110 ) as shown in  FIG. 1 ) in an embodiment of the invention predefined templates thereof are made available for classes of users. In an embodiment of the invention users can define their preferred/custom templates. For each property (or group of properties) an attribute/property context ( 140 ) (such as professional, personal, . . . ) is assigned . Properties can get a value ( 120 ). It is a contribution of the invention to emphasize the difference to be made between the property of the user (individual, organization) who&#39;s data is to be stored and the value assigned thereto.  FIG. 1  shows the underlying concept of splitting profile, property and value and more in particular the graph (node ( 150 ), relationship ( 160 )) representation thereof supporting the invented database operations.  FIG. 2  shows an example wherein as property the first name of a person is chosen while a property context the working environment of that person, hence one might label the property, property context and the possible values by the type of info expected.  FIG. 3  now demonstrates the use of these above explained concept in that an “individual” is a profile, with properties organized in property contexts as registered on the database or database networks as the case might be. A “contact” is a static profile of another party, with properties organized in property contexts that you can also have in address book, related to the target database. Note again the node/relationship approach. As shown in  FIG. 4  a link between individuals is not made directly but via the contact node. Indeed “Individual  1 ” has a static “contact” that represents “Individual  2 ” and can connect to “Individual  2 ” through this contact. Upon connection, this contact, can become a dynamic representation of the connected “Individual  2 ”, and its properties, within the appropriate context(s). When disconnected, shared properties become static again in the “contact”. The basic philosophy of the database is to profit from the invented “stored-once” principle as demonstrated in  FIG. 5 . A “profile” can have properties and in certain cases the possibility to verify them. Upon verification ownership can be claimed of this property. Based on this verified property we can start making matches and suggestions, always based on the consent &amp; privacy settings of the users. Based on different verification methods, the design of the database and taking into account the number of shared properties a degree of reliability is deduced for a given profile. 
         [0022]    It is worth noting at this stage that the system provides a granularity of defining a privacy policy on a per feature basis as the database is adapted in that for at least a part of said data fields, either individually or in group, at least one further second data field is provided wherein the individual or an organization can select (or assign or relate or choose) one or more attributes defining the by the individual or organization required communication method for determining the accessibility or not (if any) for (a predefined classes of) third parties. This is bilaterally possible say a opting in or an opting out procedure. 
         [0023]    It is also to be observed that in an embodiment of the provided database (see shown in the right part of  FIG. 6 ) the data values can be part of an another system, external to the database, in particular the use of a node for a profile pointing to a feature or property which can then further point to a value, which can be outside the database itself enables this. Alternatively said the database is for storing a plurality of individual or an organization information, the database comprising for each of such individual or an organization a plurality of first data fields, each for storing or a feature of such individual or organization (of which a part define the contact information thereof) includes databases adapted in such way that the actual value stored is by reference only (by use of a suitable interface). 
         [0024]    Note that the concept of centralizing enables checking by many users and therefore the amount of links actually represent a measure or metric of reliability of the underlying data. In an embodiment of the invention such measure is shown in the interface showing the data and its reliability. Moreover the invention provides also methods to further increase the reliability of the underlying data by making suggestions to users in further increase the trust in their data e.g. by identifying to many isolated properties or circular relationships. 
         [0025]    In an embodiment of the invention a further selection of a suitable database structure is put forward. Indeed as the database is intended for use by many users and further that many users preferably have each many data fields or properties and since as indicated above many methods operate on the database and require a search on the database, special considerations are preferably made. 
         [0026]    Many database concept exist (e.g. SQL) but in accordance with the present embodiment of the invention a graph database is elected as preferred concept. Indeed the underlying requirements of the invention in that verified (by design) data is aimed at, leads to a use of a data model, wherein a difference is made between the property of the user (individual, organization) who&#39;s data is to be stored and the value assigned thereto. In essence a structure relating user to properties and a property to a value is elected, whereby user, property and value are a separate node in a graph and the relationship is then represented by the bridges between the nodes. For such data model graph based databases and related search methods are most suitable, especially as they also allow searching along the bridges/the relationships. This embodiment of the invention hence provides a fundamental understanding of the true required nature of the data model and related database and (whether uni- or bidirectional along the edges of the graph) search methods to be used, in that the named property must be decomposed or separated from its value. Instead of representing the data space as nodes representing people or organizations and arcs/bridges or relations therein between, a further decomposition is made, representing each of those people or organizations themselves as a group of nodes, representing their properties and further relating these properties to stand-alone values. In this way the complicated connections in the society get represented by the elected data model. Note that relationships themselves can also have properties. 
         [0027]    Indeed by considering values as separate items (stored once), the operations on the database in essence boils down on operations on the relationships. And if a value of a property needs a change, not the value get changed, but a pointing to another (or a new) value is performed (which enable storage of previous information and retrieval thereof). This also ensures that such change can become visible to all authorized connections at once. 
         [0028]    The above embodiment has the advantages that it provides an ideal match between the defined (but extendable) requirements and the technical implementation in that the ‘stored once’ principle leads not only to data reduction (storage size reduction) per se, but ensures that the data in the values can serve as a trusted set of master data, with build-in by design consistency and/or privacy. 
         [0029]    In a further embodiment one or more of the data fields are encrypted. In an exemplary embodiment thereon the encryption is applied to the values and/or the relationships in the graph based databases. 
         [0030]    In summary one or more of the following features of the invention, which can be used separately or in combination are once more indicated below:
       1. Public/Private/Upon Request   2. Active (dynamic)/Passive (static)   3. Opt IN &amp; OUT   4. Privacy by design   5. Verified by different means (tool/connections/networked effect/ . . . )   6. Add manually/Request Confirmation (invite)/Request   7. Stored Once: match based on verified properties/suggestions       
 
         [0038]    A person of skill in the art would readily recognize that steps of various above-described methods can be performed by programmed computers. Herein, some embodiments are also intended to cover program storage devices, e.g., digital data storage media, which are machine or computer readable and encode machine-executable or computer-executable programs of instructions, wherein said instructions perform some or all of the steps of said above-described methods. The program storage devices may be, e.g., digital memories, magnetic storage media such as a magnetic disks and magnetic tapes, hard drives, or optically readable digital data storage media. The embodiments are also intended to cover computers programmed to perform said steps of the above-described methods. 
         [0039]    Alternatively formulated one can state that an embodiment of invention relates to a database for storing a plurality of individual or an organization information, said database being constructed in that data used therein is verified by design, meaning the operations, interfaces and underlying database set-up is made to realize this, in a preferred embodiment the database being a graph database. 
         [0040]    In essence the database comprises for each of such individual or an organization a plurality of first data fields, each for storing a feature/property of such individual or organization (of which a part define the contact information thereof), whereby the database is based on a data model, wherein a difference is made between the feature/property of the user (individual, organization) who&#39;s data is to be stored and the value assigned thereto (as described in  FIGS. 1 and 2 ), more specifically a data model/structure relating user to properties and a property to a value is elected, whereby user, property and value are a separate node in a graph and the relationship is then represented by the bridges between the nodes. Therefore the invention relates to methods for using/handling an target individual or an organization his/her or its information stored in such databases, based on search methods, using said bridges. 
         [0041]    The invention provides technological solutions curing the above mentioned problems, more in particular a database structure or system design (subsequently implemented in software) and related use methods, build on a well selected underlying concept, the use thereof with a dedicated application, for supporting one or more of the indicated aspects of the invention (accessibility control, high quality data and/or smart entry), in particular by choice of the specific data model outlined above and/or the selection of a suitable technology solution in the field of databases, especially a graph based database. 
         [0042]    Ensuring that once can determine the accessibility (if any) for (a predefined classes of) third parties of feature value (the so-called privacy policy) is (as shown in  FIG. 6 ) by use of mechanisms related to the property (node), not the value referenced by it.  FIG. 7-12  demonstrate an exemplary embodiment thereof. In essence a specialized node ( 300 ) (called access request or alternatively to be called access management node) is used. In an embodiment thereon the node has a dual state (requested, granted) but alternative embodiments with more states are equally possible. This node is used in combination with the contact node defined earlier in particular a relationship between said contact node and said access management node is made. As the fine per property granularity allows, a request can be on a per feature or property basis. When a request is made (and corresponding property and value exist) and granted, instead of copying values (leading to the problems discussed above of maintenance) a link is made instead to the same value (as this property becomes denoted a shared property). 
         [0043]    Whilst the principles of the invention have been set out above in connection with specific embodiments, it is to be understood that this description is merely made by way of example and not as a limitation of the scope of protection which is determined by the appended claims. Alternatively formulated the invention relates to a database system comprising: a graph based database, a query engine for performing queries to the graph based database; one or more applications operable for requesting and receiving data from the query engine; a memory for storing machine executable instructions for implementing the database system; and a processor for executing the machine executable instructions in support of the various methods supported by the database system and its linked applications.