Abstract:
The invention relates to an efficient system for user rights in a semantic digital network, whereby users are arranged in the same semantic network as the information objects. The rights are thus derived from the semantic relations between users and information objects in a common semantic network.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
       [0001]    This application is a continuation-in-part of U.S. patent application Ser. No. 10/512,778 filed Oct. 26, 2004, which is a national phase entry of PCT/EP03/04373 filed Apr. 28, 2003, which claims priority to DE 102 18 905.6 filed Apr. 26, 2002, all of which are incorporated by reference. 
     
    
     TECHNICAL FIELD 
       [0002]    The invention relates essentially to a method for deriving user rights in a semantic network. 
       BACKGROUND OF THE INVENTION 
       [0003]    Semantic networks are being used in increasing numbers to link information items with one another and to find them again at a later time. These forms of networks with their algorithms are also referred to as knowledge networks or ontologies, whereby information objects are connected with one another by edges which exhibit specific semantics. 
         [0004]    Navigation through the network is effected along these edges and for preference by means of inferential algorithms. These traverse the network in the quest for statements. 
         [0005]    Because of the large variety of information possibly stored in such knowledge networks, the need arises for access to be restricted or made possible to specific areas of the network under certain circumstances. 
         [0006]    In the considerations regarding the structure of the user management, criteria such as efficiency and usability of existing algorithms and data structures play a decisive part. 
         [0007]    Known solutions implement the access control on the table level, as it is known, for example, from relational databases. 
         [0008]    The problem addressed by the invention is to provide an efficient and flexibly configurable access control which is technically and ergonomically integrated, and which takes account of the complexity of knowledge networks. 
         [0009]    U.S. Pat. No. 5,941,947 discloses a method to control the access to network resources. This approach uses a relational database to store the access information. Furthermore the rights are stored explicitly and not as rules, which are executed at runtime. Furthermore the rights are used to control the access of the objects which are located externally. Furthermore U.S. Pat. No. 5,941,947 discloses a tight relation between User-Groups and data-categories. 
         [0010]    US 2003/0126136 A1 discloses a framework and a semantic network 
       DETAILED DESCRIPTION 
       [0011]    This problem is resolved by the invention in accordance with the features of the independent claims. Advantageous further embodiments of the invention are described in the sub-claims. 
         [0012]    If the invention is regarded in abstract terms, the users are represented in the same semantic network as the information objects. Access rights are derived from the semantic relations between users and information objects. 
         [0013]    This solution has the advantage that no further metadata is required, as is the case, for example, with relational databases. Rather, existing algorithms and inference rules can be used in order to derive user rights. In addition to this, the same storage system can be used for contents and access information. A further technical advantage lies in the fact that no adaptation of the code for the representation of the access information is required The users and their relations to the information objects are part of the knowledge network as a whole. 
         [0014]    Thanks to the use of the efficient memory system and the high-performing algorithms, it is possible for the user rights to be calculated at the time of access. This has the advantage that, instead of static rules, access rights can be defined in the form of queries that are executed dynamically. This is described in detail hereinafter. 
         [0015]    The rights system of the present invention makes the decision on access authorization by evaluating a set of access rules with information from the knowledge network. 
         [0016]    Users who are intended to be subject to an access control by the rights system are presented as nodes in the knowledge network. 
         [0017]    These user nodes are set in relationship to other nodes in the knowledge network. 
         [0018]    By means of the rules which configure the rights system it is determined which access rights pertain for the individual user for the knowledge network objects. In this situation a check is carried out as to whether rules exist which allow for an access. This check is performed dynamically at run time. This ensures that any changes in the knowledge network are immediately reflected in changed access rights. 
         [0019]    Roles are likewise defined in the knowledge network and simplify the configuration of the rights system. Depending on the role of a person, it is therefore possible for different rights to be defined for entire groups.
   Considered in formal terms, an access a: &lt;u, t, op&gt; is a triple consisting of the three components user, target, and operation.   A decision d: {grant/deny} states whether an access may be performed or not. A right r: a→d is a mapping of an access to a decision (grant or deny).   ‘grant’ means that the user of a right (user) can carry out the operation specified (operation) on the target of the access (target). If a part of the access is not defined, the access is deemed to apply to all the objects of the knowledge network which come into question for this part. In addition to the specification of individual elements, the components can contain sets of elements. As a result, it is possible to define access rights for groups of users on sets of elements with multiple operations.   
 
         [0023]    In the preferred embodiment, the rights of a knowledge network are defined in a rights tree. The root of this tree is for preference anchored in the central part of the knowledge network. If no rights tree exists in this preferred embodiment, or if this space consists solely of a root node, a default decision, preferably “grant”, is returned for all users on all knowledge network objects. 
         [0024]    Rights are defined in the inner nodes and in the leaves of the rights tree. The inner nodes act as filter for the access(es) that have to be granted or denied. When an access passes all filter levels of the access rights tree and reaches a leaf in the tree, ‘grant’ or ‘deny’ is returned as permission for this access. 
       Components of an Access 
       [0025]    The individual components of an access are explained hereinafter. The components of the rule system, especially the different types of filters, will then be considered. 
       Operations: 
       [0026]    The definition of op in the rights system is effected for preference by the enumeration of the permitted operations (in the preferred implementation “Read”, “Modify”, “Generate” and “Delete”). 
       User: 
       [0027]    Persons (or external systems) that need to access the knowledge network are themselves stored as nodes in the network. There is an explicit mapping between users (preferably login names) and user objects. User objects can be linked to other nodes of the knowledge network. 
       Target: 
       [0028]    In the preferred embodiment, any element of the knowledge net can be target t of an access. Especially, target can be
       A semantic node (such as an address, a customer, an order)   A user object as a specialisation of semantic node   An attribute of a semantic object (such as the date of birth of a certain person, the street name of an address)   A relation between semantic nodes (such as the ‘placed order’ relation between customer object ‘Miller’ and order object ‘67103/03’).       
 
       Components of the Rule System 
       [0033]    Access right rules are organized as a hierarchy (or tree) of filters. Each filter applies to one or more well defined aspects of an access. Each filter can be configured as positive or negative filter. For a positive filter, the filter condition has to evaluate to ‘true’ for an access to let this access pass to the next lower level. Negative filters have their condition evaluate to ‘false’ to let an access pass thru. In the preferred embodiment, different filtering behaviour is reflected in different types of filters: 
       1. Explicit Itemization: 
       [0034]    The users or target objects are configured in the filter explicitly, e.g. by means of an editor. In this situation, individual elements (instances) of the user or target term are determined. 
         [0035]    For example, if some access rules should apply only for user ‘bob’, an explicit filter for access parameter u and configured object ‘bob’ is inserted in the rules tree on top of the rules describing user bob&#39;s special rules. 
       2. Calculation by a Query Expression 
       [0036]    In this case, the filter rule is described by a query expression. If the subject of the filter, namely the target or the user of an access, is contained in the result set of the query, the filter condition evaluates to ‘true’. 
         [0037]    If it is intended, for example, that in a knowledge network with project data only the knowledge network objects should be accessible for each owner/user from their own project in each case, this can be attained by setting up a query for ‘projects owned by the current user’ as target filter. 
       3. Restriction to Certain Types of Attributes or Relations 
       [0038]    This filter works only for targets of an access. The relation or attribute types that match this filter are configured explicitly. In contrast to filter type  1  which would apply to explicit attributes/relations (e.g. the attribute “date of birth” of person “Adele”), this filter applies to types of attributes/relations (e.g. all “date of birth” attributes). 
       Evaluation of Access Requests 
       [0039]    When accessing an information object, the computer on which the invention is running (client, middleware or server) automatically generates an access and evaluates the said right tree with that access. 
         [0040]    During the examination of whether an access may be carried out, the rule tree is traversed in pre-order. If an access is filtered out by an inner node n 1 , this node&#39;s sub tree is not traversed in further depth, and traversal is continued with the neighbour of n 1 . When the traversal reaches a leaf of the rule tree, the decision configured for that leaf is returned as result for the access request. 
       Configuration of Access Rights 
       [0041]    The right tree itself is protected against unauthorized manipulation. Standard users may have only read access to check concrete access request, whereas administrators have also the right to change the rights and its rules. To provide only a limited access to the right tree, the right tree has limited entry points which are protected by dedicated interfaces or functions or layers of software. 
       Example Embodiments 
       [0042]    The invention is explained in greater detail hereinafter on the basis of embodiments, which are represented in diagrammatic form in the Figures. The same reference numbers in the individual Figures designate the same elements. 
     
    
     
       SPECIFICALLY, THE FIGURES SHOW 
         [0043]      FIG. 1  An extract from a knowledge network with the user/owner nodes “Ms. Miller”, responsible for the knowledge network object “Building Site Reiber Street”; 
           [0044]      FIG. 2  Rights in tree form with operations folders and user/owner folders; 
       
    
    
     DESCRIPTION OF THE PREFERRED EMBODIMENT 
       [0045]    Within the scope of the invention, numerous derivations and further formulations of the embodiments described can be realised. 
         [0046]      FIG. 1  shows a section from a knowledge network, in which the project structure of a construction company is displayed. Accordingly, “Ms. Miller” is responsible for the project of the “Reiber Street Residential Building”, in the role of “Project Manager”. “Mr. Yates” is leading the Software Project “Redesign Accounting System”. 
         [0047]    The rights system can now be configured in such a way, for example, that Ms. Miller receives writing rights to the building sections relating to the “Building Site Reiber Street” construction project (e.g. “Basement Reiber St.”). Construction sections from other construction projects (e.g. “Building Site Frankfurt Airport”), for which Ms. Miller is not responsible, cannot be processed by her. New construction sections, such as in the sector of “Reiber Street External Installations”, automatically fall into the access area of Ms. Miller. 
         [0048]    Changes in the knowledge network, such as a restructuring, in which the responsibilities for “Residential Building” and “Landscape Gardening” are separated in terms of organization, also automatically change the access entitlements of the users concerned (in this case, Ms. Miller would lose her writing right to the “External Installations”). “Mr. Ford” (being the company owner) has global access rights to all nodes of the knowledge network. 
         [0049]    An example of an access rights configuration can bee seen in  FIG. 2 . 
         [0050]    The first part tree of the access rights tree explicitly grants global access to “Mr. Ford”. 
         [0051]    The second sub tree defines access rights for the operation “modify” for all users (except “Mr. Ford”). If the target of the operation is a project within the responsibility of the current user, modification is allowed. For all other nodes (e.g. a project node outside the user&#39;s responsibility, or the person node “Mr. Yates”), access is denied. 
         [0052]    The third sub tree defines read access rights. If the node to be read is of type “Project”, read access is granted to all users with role “Project Manager”. E.g., “Mr. Yates” can read all aspects of any project. For all other users (like “Mr. Smith”), read access is restricted to the basic properties of a project (project name, start date, and end date in our example). For all other knowledge nodes, read access is denied by the fallback “denied” at the bottom of the rights tree. 
         [0053]    The bottommost leaf of the rights tree defines the default answer of the access rights system when none of the previous rules apply (“denied” in  FIG. 2 ). In the example, no rules are defined for the “Create” operation, so the only one allowed to create any knowledge object is “Mr. Ford”, because of the “grant” in the first part tree which applies regardless the requested operation. 
       LITERATURE LIST 
       [0000]    
       
         1. Knowledge Engineering: Principles and Methods (Rudi Studer, V. Richard Benjamins, and Dieter Fensel). 
         2. Fausto Rabitti, Elisa Bertino, Won Kim, and Darrell Woelk: A Model of Authorization for Next-Generation Database Systems, in: ACM Transactions on Database Systems, Vol. 16, No. 1, March 1991. 
         3. Martin S. Olivier and Sebastian H. von Solms: A Taxonomy for Secure Object-Oriented Databases, in: ACM Transactions on Database Systems, Vol. 19, No. 1, March 1994. 
         4. Gail-Joon Ahn and Ravi Sandhu: Role-Based Authorization Constraints Specification, in: ACM Transactions on Information and System Security, Vol. 3, No. 4, November 2000. 
         5. Elias Bertino, Sushil Jajodia, and Pierangela Samaratia: Flexible Authorization Mechanism for Relational Data Management Systems, in: ACM Transactions on Information Systems, Vol. 17, No. 2, April 1999. 
         6. John F. Sowa: Knowledge Representation: Logical, philosophical, and computational foundations. Brooks/Cole Publishing House, 2000. 
         7. And other references disclosed in the documents referred to above.