Main-memory based conceptual framework for file storage and fast data retrieval

• US 9,483,479 B2
• Filed: 08/12/2013
• Issued: 11/01/2016
• Est. Priority Date: 08/12/2013
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Shah, Dhwanit
• Primary Examiner(s): Stevens, Robert
• Application Number:
  US13/964,736
• Publication Number:
  US 20150046494A1
• Time in Patent Office: 1,177 Days
• Field of Search: 707/783, 707/822
• US Class Current: 1/1
• CPC Class Codes: G06F 16/13 File access structures, e.g. distributed indices arrangements of input from, or output to, record carriers G06F3/06

Abstract

A conceptual framework is built including a conceptual hierarchy, a containment hierarchy, and concept relationships. The concepts created in the conceptual framework are associated with resources located on the local file system. The resources are stored in the conceptual framework that is stored in the main memory of the system. Thus, search capabilities based on complex multivariate queries involving relationships and multiple conditions between concepts are provided. The conceptual framework is based on an in-memory engine that enables superfast resource access, reduced file storage redundancy, reduced updating errors, increased consistency, greater data integrity and independence from application level programs, query based concept and file access.

Claims

1. A computer implemented method, the method comprising:

creating a concept data object with a super class concept in a conceptual hierarchy, wherein creating the concept data object comprises marking the concept data object as a compositional data object or a non compositional data object based upon a user input;

receiving a selection of the concept data object as a source concept;

receiving a selection of a second concept data object as a target concept included in a containment hierarchy, wherein the containment hierarchy is a nested data tree structure that includes concepts and resources of a file storage system modeled as attributes of the concepts with a URL as a key and a file path as a value;

adding an association type between the source concept and the target concept, wherein the association type is based on a selected role concept;

associating a resource of the file storage system with the concept data object;

importing the resource in the local file system, wherein the resource is initially located on a remote file system; and

storing the source concept, the target concept, the role concept, the association type, and the resource in main memory.

2. The method of claim 1, wherein associating the resource comprises:

receiving a location of the resource; and

adding the resource location as an attribute for the source concept.

3. The method of claim 2, further comprising:

selecting a file concept as the super class concept;

marking the file concept as an instance file concept; and

selecting a system concept as the container concept.

4. The method of claim 3, further comprising:

automatically adding a set of file properties and a set of access permissions into the file concept.

5. The method of claim 1, further comprising:

adding one or more attributes for the concept data object; and

modifying the one or more attributes for the concept data object by editing or deleting key and value information for the one or more attributes.

6. The method of claim 1 further comprising:

creating a role type instance of the role concept that specifies a role that the source concept plays on the target concept, wherein the role concept is defined as a separate concept data object.

7. A computer system, comprising:

a processor;

a memory in communication with the processor, the memory comprising;

a conceptual framework;

a conceptual hierarchy as part of the conceptual framework, wherein a concept data object is created with a super class concept in the conceptual hierarchy, and wherein creating the concept data object comprises marking the concept data object as a compositional data object or a non compositional data object based upon a user input and receiving a selection of the concept data object as a source concept; and

a containment hierarchy as part of the conceptual framework, wherein a second concept is selected as a target concept, wherein an association type between the source concept and the target concept is created, and wherein the association type is based on a selected role concept, and wherein the containment hierarchy is a nested data tree structure that includes concepts and resources of a file storage system modeled as attributes of the concepts with a URL as a key and a file path as a value;

a resource located on a local file system, wherein the resource is imported in the local file system if the resource is initially located on a remote file system; and

a main memory that stores the source concept, the target concept, the role concept, the association type, and the resource.

8. The system of claim 7, wherein a role type instance of the role concept is created that specifies a role that the source concept plays on the target concept, wherein the role concept is defined as a separate concept.

9. The system of claim 7, wherein one or more attributes are added for the concept data object.

10. The system of claim 7, wherein the resource location is added as an attribute for the source concept.

11. The system of claim 7, wherein a set of file properties and a set of access permissions are automatically added into a file concept, wherein the file concept is defined as the super class concept.

12. A non-transitory computer-readable medium storing instructions, which when executed cause a computer system to:

create a concept data object with a super class concept in a conceptual hierarchy, wherein creating the concept data object comprises marking the concept data object as a compositional data object or a non compositional data object based upon a user input;

receive a selection of the concept data object as a source concept;

receive a selection of a second concept data object as a target concept included in a containment hierarchy, wherein the containment hierarchy is a nested data tree structure that includes concepts and resources of a file storage system modeled as attributes of the concepts with a URL as a key and a file path as a value;

add an association type between the source concept and the target concept, wherein the association type is based on a selected role concept;

associate a resource of a local file system with the concept data object;

import the resource in the local file system, wherein the resource is initially located on a remote file system; and

store the source concept, the target concept, the role concept, the association type, and the resource in main memory.

13. The computer-readable medium of claim 12 further comprising instructions that cause the computer system to:

receive a location of the resource; and

add the resource location as an attribute for the source concept.

14. The computer-readable medium of claim 13, further comprising instructions to cause the computer system to:

select a file concept as the super class concept;

mark the file concept as an instance file concept; and

select a system concept as the container concept.

15. The computer-readable medium of claim 14, further comprising instructions to cause the computer system to automatically add a set of file properties and a set of access permissions into the file concept.

16. The computer-readable medium of claim 12 further comprising instructions that cause the computer system to:

add one or more attributes for the concept data object; and

modify the one or more attributes for the concept data object by editing or deleting key and value information for the one or more attributes.

17. The computer-readable medium of claim 12, further comprising instructions that cause the computer system to:

create a role type instance of the role concept that specifies a role that the source concept plays on the target concept, wherein the role concept is defined as a separate concept.