WO2016006998A1

WO2016006998A1 - Method and system to retrieve relevant data based on linked-up service with embedded access control

Info

Publication number: WO2016006998A1
Application number: PCT/MY2015/000049
Authority: WO
Inventors: Sharipah Setapa; Azuraini ABU BAKAR; Ros-LIsa ABDUL RAHMAN
Original assignee: Mimos Berhad
Priority date: 2014-06-20
Filing date: 2015-06-17
Publication date: 2016-01-14
Also published as: MY168514A

Abstract

The present invention provides a method and system to retrieve relevant data based on linked-up service (704) with embedded access control. The method and system comprises authenticating a user, by a user authentication engine, that has raised a request (1) to retrieve data from an embedded access control list. This is followed by filtering data, by retrieval engine (2), based on data relevance, processed by a storage means (708), using meta data measured (3) by an orchestra meta flow use case engine to identify at least one data repository (702) from which the data will be retrieved. Thereafter, the method and system comprises storing in a virtual memory (706), data relevance in a relevance database (4) and data non-relevance in a non-relevance database (5), data relevance and data non-relevance is returned to the at least one data repository after a predetermined period of time (6).

Description

METHOD AND SYSTEM TO RETRIEVE RELEVANT DATA BASED ON LINKED-UP SERVICE WITH EMBEDDED ACCESS CONTROL

FIELD OF INVENTION

The present invention relates generally to a method and system to retrieve relevant data based on linked-up service with embedded access control, more particularly a method and system that utilizes linked-up service to provide high accuracy when retrieving relevant resource/application/data for respective use case with embedded access control for the integrity and protection of meta knowledge base through measurement of orchestra meta flow.

BACKGROUND ART

At present a lot of effort is utilized for repetitive activities of searching and retrieving multiple resource/application/data redundancy. This causes an increase in recycle time and man hours as well as the possibility of a security breach. This impacts data security level and data reporting. Use cases and its respective data/resource/application are being re-developed for existing or similar requirements although many already exist. This is due to the difficulty of searching and retrieving the relevance of use cases and its respective data/resource/application with high accuracy while maintaining correct reporting level access. SUMMARY OF INVENTION

The present invention provides a method and system to retrieve relevant data based on linked-up service with embedded access control. The present invention proposes a method and system that will reduce redundancy of resource/application/data/ with its ability to recommend and retrieve relevant use case while maintaining security of meta knowledge base with an embedded access control. In one aspect of the present invention is a method to retrieve relevant data based on linked-up service with embedded access control. The method comprises authenticating a user, by a user authentication engine, that has raised a request to retrieve data from an embedded access control list. This is followed by filtering data, by retrieval engine, based on data relevance, processed by a storage means, using meta data measured by an orchestra meta flow use case engine to identify at least one data repository from which the data will be retrieved. Thereafter, the method comprises storing in a virtual memory, data relevance in a relevance database and data non-relevance in a non-relevance database, data relevance and data non-relevance is returned to the at least one data repository after a predetermined period of time.

In another aspect of the present invention is a system to retrieve relevant data based on linked-up service with embedded access control, the system comprises at least one data repository; a linked-up service; at least one virtual memory; and a storage means. The linked-up service further comprises an access control list, a user authentication engine, an orchestra meta flow use case engine and a retrieval engine. The virtual memory further comprises a relevance database and a non-relevance database. The storage means further comprising a primary storage and a secondary storage.

In one embodiment of the present invention, the method further comprises classifying data based on data properties of title, identification, author, owner, purposes, features and content; checking and linking data; level reporting a user and a user exposure; listing classified data stored in at least one storage means wherein a secrecy level is colour coded; and providing a seal for data specific to an owner through a table list, the table list is updated based on a current owner.

The checking and linking of data further comprises rejecting redundancy data if linked-up service identifies identical data in the at least one data repository; rejecting redundancy data identified through the table list; disallowing user to retrieve redundancy data; and permitting the retrieval of data upon receiving non-redundancy.

The authenticating of the user further comprises allowing the user access to download, read, modify, write and functionality of data; binding data based on role and resource; grouping resource based on role which have multiple resources; and repeating verification of level reporting if conflicting with multiple role.

The measuring of data by an orchestra meta flow use case engine further comprises obtaining at least one data property based on a bidirectional orchestra meta flow data to be made a core measurement; extracting data from a table list; a new data and flow is recreated if is the /application/information is updated for current measurement and the value collected separately; and the core measurement is recalibrated within a predetermined period of time for synchronization with the current measurement.

The linked-up service further comprises measuring, by a usefer filter, a current measurement of data by comparing with a core measurement of the data; test collecting by at least using profiler of user data, flow and response time; and ranking level of similarity based on evidence of the data corresponding to specific data. The present invention consists of features and a combination of parts hereinafter fully described and illustrated in the accompanying drawings, it is being understood that various changes in the details may be made without departing from the scope of the invention or sacrificing any of the advantages of the present invention.

BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

To further clarify various aspects of some embodiments of the present invention, a more particular description of the invention will be rendered by references to specific embodiments thereof, which are illustrated, in the appended drawings. It is appreciated that these drawings depict only typical embodiments of the invention and are therefore not to be considered limiting of its scope. The invention will be described and explained with additional specificity and detail through the accompanying drawings in which:

FIGURE 1 illustrates a system and method to retrieve relevant data based on linked-up service with embedded access control. FIGURE 2 is a flow chart illustrating a method to retrieve relevant data based on linked-up service with embedded access control.

FIGURE 3 is a flow chart illustrating a preliminary method to identify the relationship of data.

FIGURE 4 is a flow chart illustrating a test use case model.

FIGURE 5 is a flow chart illustrating use case model measurement. FIGURE 6 is a flow chart illustrating evaluation and comparison of measurement.

FIGURE 7 is a flow chart illustrating role and resource with valid relevance for embedded access control. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

The present invention relates to a method and system to retrieve relevant data based on linked-up service with embedded access control. Hereinafter, this specification will describe the present invention according to the preferred embodiments of the present invention. However, it is to be understood that limiting the description to the preferred embodiments of the invention is merely to facilitate discussion of the present invention and it is envisioned that those skilled in the art may devise various modifications and equivalents without departing from the scope of the appended claims.

The present invention more particularly relates a method and system that utilizes linked-up service to provide high accuracy when retrieving relevant resource/application/data for respective use case with embedded access control for the integrity and protection of meta knowledge base through measurement of orchestra meta flow. The present invention proposes a method and system that will reduce redundancy of resource/application/data/ with its ability to recommend and retrieve relevant use case while maintaining security of meta knowledge base with an embedded access control. This is achieved by an orchestra meta flow based measurement, for a first layer of protection, wherein this measurement is used to obtain a protected database from which resource/application/data will be retrieved using Linked-Up Service through query by index and embedding using access control list, for a second layer of protection, to protect the meta knowledge base where resource/application/data has been stored.

Use case consists of input, output and "black box" function of the data which comprises resource/application/data. Resource/application/data is the high level requirement which defines input required and the corresponding output that would be generated. In practice, the foremost development design requires much iteration of modifications in order to obtain a complete structure and finalized. When a new request for resource/application/data is made, the said request can be tagged to an existing resource/application/data such as flow design, test case and etc, which have been previously developed. Resource/application/data provides functional requirement through requirement that has been previously gathered. It may be further developed, modified and adjusted to suit the requirement of the new request. This reduces the need for repetition to create similar resource/application/data and flow design for the new request which may delay the process of development.

The data that is stored in existing databases are combined with all various resource/application/data. A user will have to weed out individual data to obtain the relevant data request in the new request. The resource/application/data have an exemplary structure that includes title, date, authors, functionality and etc. The resource/application/data also have a characteristic format which include actor, brief description, preconditions, postconditions, include, rules and notes. During the development design stage, the resource/application/data are created based on the skill set of the developer as there are no general standards or rules to standardize the creation of the resource/application/data. The relevant data/resource/application/data will be retrieved based on high frequency of flows, data level reporting, keywords and this is populated to the proposed table list based on ranking. For a first layer of protection, an orchestra meta flow based measurement is performed and is taken as the core measurement, wherein this measurement is used to obtain a protected database from which resource/application/data will be retrieved using Use case Linked-Up Service through query by index. For a second layer of protection, embedding using access control list is performed, to protect the meta knowledge base where resource/application/data has been stored.

Reference is now being made to FIGURE 1. FIGURE 1 illustrates a system and method to retrieve relevant data based on linked-up service with embedded access control. Upon an authenticated user, authenticated by an authentication engine, accessing the access control list (ACL) to obtain resource/application/data (1 ), the retrieval engine will assist to filter out data that is accurate or relevant (3) as processed by a storage means from meta data resource/application/data that has been measured using orchestra meta flow obtain a protected data repository (702) from which resource/application/data will be retrieved (2). If relevant, user is able to retrieve based at least on the role or resource. Once completed, it will be passed to the specific database. Accuracy is stored in the relevance database (4) of a virtual memory (706) while non-relevance is stored in the non relevance database (5) of the virtual memory and is returned to the data repository after a certain period of time (6).

Linked-up service (704) allows for searching and retrieving resource/application/data easily with high accuracy. Linked-up service processes the user request for the respective resource/application/data by checking the resource/application/data ID, characteristic and properties of resource/application/data.

The results of checking the afore-mentioned parameters are determined as the current measurement, the linked-up service will compare the current measurement to the core measurement within the use case filter (Usefer filter). If the specific data/resource/application/data cannot be trace, then a notification of null or empty or not matching, is sent back to the user. If the comparison value is different, the usecase model needs to be re-defined again. If the comparison gap exceeds a predetermined threshold, a load balancing and checking of data repository is performed. This creates awareness that a data has been added into the data repository without following the proper procedure. This resource/application/data will fall into the non-relevant resource/application/data. If the measurement value is almost similar then the nearest value for the respective resource/application/data will be taken. This respective resource/application/data will fall into the relevant resource/application/data. The similar resource/application/data will be retrieved, and for convenience to the user a ranking is defined for each resource/application/data. The highest ranking will be chosen as the accurate resource/application/data for the automatic retrieval.

This relevant and non-relevant resource/application/data will be placed into separate the relevant database and non-relevant database respectively under the virtual memory. Data relevance and data non- relevance is returned to the data repository after a predetermined period of time. The primary and secondary storage means (708) will be used to process the queue and information before passing the same on to next process. Secondary storage means will be used once the primary storage is full. Resource/application/data is classified based on title, identification, author, owner, purposes, features and content as well as reporting level. Each resource/application/data will be specified and identification (ID) that will be used during comparison and for load balancing by repository_usecase. The ID will be created through the resource/application/data linked-up service and will be stored in structure repository_usecase based. The accuracy relevance database will be represented with the embeded access control list which bins with the role and resource and is capable of performing read, download, modify and etc. If the role is found to match the users' request, then permission is granted to perform actions based a predefine role and resource for each user. Automatic retrieval warrants only the correct resource/application/data and role can be accessed and this ensures the integrity of retrieved data. If the user is rejected then the user is not authorized to perform any actions as the role is not eligible for the resource.

Reference is being made to FIGURE 2. FIGURE 2 is a flow chart illustrating a method to retrieve relevant data based on linked-up service with embedded access control. During the development design stage, the resource/application/data are created based on the skill set of the developer as there are no general standards or rules to standardize the creation of the resource/application/data. The characteristic and classification of resource/application/data will be determined (100). Data and resource/application/data which relate to the resource/application/data will be tagged and represented (200) before being selected through properties such as title, author, content and resource/application/data ID. Each property will be given a checksum. Firstly a measurement of test collection or user collection will be measure (300). Then this will be store as a core measurement or benchmark (400). A search based on the respective resource/application/data will be conducted and will be tagged and represented to respective resource/application/data for automatic retrieval (500). Upon completion, the embedded access control list (600) will authorized the user if the user is authorized to read, download or modify the data. Once completed, an automatic retrieval of resource/application/data can be performed for respective resource/application/data with a high level of accuracy.

Reference is being made to FIGURE 3. FIGURE 3 is a flow chart illustrating a preliminary method to identify the relationship of data. The resource/application/data will be analysed to identify (101 ) the relationship between one another (102). Once this process is completed, the search will be conducted through index and queries (103) to collect the related information (104). This ensures a speedy search. A resource/application/data package (105) may be created once the relationship has been identified.

Reference is being made to FIGURE 4. FIGURE 4 is a flow chart illustrating a test use case model. The relevance of resource/application/data may be presumed as resource/application/data mining (106). It will be meta tagged (107) and categorized (108), and a model will be developed (109). Once the model is completed, it is then tested (110). If the model is relevant, then a use case model based on the resource/application/data will be finalized. Otherwise, a new model is recreated (111 ).

Reference is being made to FIGURE 5. FIGURE 5 is a flow chart illustrating use case model measurement. The relevance of use case model will be measured (301 ) to be a core measurement or benchmark (302). A query (303) will be requested to identify the exact value to be made a current measurement if the value that was received is not satisfactory. If a query is not requested, the process is halted (304) and the use case model will be a core measurement (305) for any future request of the respective resource/application/data. Reference is being made to FIGURE 6. FIGURE 6 is a flow chart illustrating evaluation and comparison of measurement. The relevance information (401 ) retrieved will be selected, combine and evaluated. Ranking will be generated (403), assigned and stored. It will be compared (404) to existing core measurement. Usefer filter (405) will perform filtering based on measurement of test collection and will search the accuracy (406). Resource/application/data will be retrieved (407) and placed in the relevance and non-relevance database (408). Reference is being made to FIGURE 7. FIGURE 7 is a flow chart illustrating role and resource with valid relevance for embedded access control. Embedded access control is a second layer of protection after integrity measurement the first layer protection in the orchestra meta flow (601 ). The embedded access control checks the authorization through role and resource which compliment each other. Once the check is complete, the user is binded with specific a role and resource and a permission will be given to obtain the data (602). If data retrieval is unsuccessful! (603), then user role is assessed to ascertain whether it is being bind with a specific resource. If it is not, the process is disconnected or halted . Otherwise, there will be a halt or deny (605) of the data based on resource which has been declared for a specific role. If the data is successfully retrieved, then the resource such as download or modify can be applied (606) to specific resource/application/data.

Claims

1. A method to retrieve relevant data based on linked-up service with embedded access control, the method comprises

authenticating a user, by a user authentication engine, that has raised a request (1 ) to retrieve data from an embedded access control list;

filtering data, by retrieval engine (2), based on data relevance, processed by a storage means, using meta data measured (3) by an orchestra meta flow use case engine to identify at least one data repository from which the data will be retrieved; and

storing in a virtual memory, data relevance in a relevance database (4) and data non-relevance in a non-relevance database (5), data relevance and data non-relevance is returned to the at least one data repository after a predetermined period of time (6).

2. A method according to claim 1 wherein the method further comprises

classifying data based on data properties of title, identification, author, owner, purposes, features and content; checking and linking data;

level reporting a user and a user exposure;

listing classified data stored in at least one storage means wherein a secrecy level is colour coded; and

providing a seal for data specific to an owner through a table list, the table list is updated based on a current owner.

3. A method according to claim 2 wherein checking and linking data further comprises

rejecting redundancy data if linked-up service identifies identical data in the at least one data repository; rejecting redundancy data identified through the table list; disallowing user to retrieve redundancy data; and permitting the retrieval of data upon receiving non- redundancy.

A method according to claim 1 wherein authenticating the user further comprises

allowing the user access to download, read, modify, write and functionality of data;

binding data based on role and resource;

grouping resource based on role which have multiple resources; and

repeating verification of level reporting if conflicting with multiple role.

A method according to claim 1 wherein measuring data by an orchestra meta flow use case engine further comprises

obtaining at least one data property based on a bidirectional orchestra meta flow data to be made a core measurement; extracting data from a table list;

a new data and flow is recreated if is the

/application/information is updated for current measurement and the value collected separately; and

the core measurement is recalibrated within a predetermined period of time for synchronization with the current measurement. A method according to claim 1 wherein the linked-up service further comprises

measuring, by a usefer filter, a current measurement of data by comparing with a core measurement of the data;

test collecting by at least using profiler of user data, flow and response time; and

ranking level of similarity based on evidence of the data corresponding to specific data.

A system to retrieve relevant data based on linked-up service with embedded access control, the system comprises

at least one data repository (702);

a linked-up service (704);

at least one virtual memory (706); and

a storage means (708);

characterized in that

the linked-up service (702) further comprises an access control list, a user authentication engine, an orchestra meta flow use case engine and a retrieval engine;

the virtual memory (706) further comprises a relevance database and a non-relevance database; and the storage means (708) further comprising a primary storage and a secondary storage.