IRC-infoid data standardization for use in a plurality of mobile applications

• US 10,666,731 B2
• Filed: 02/13/2019
• Issued: 05/26/2020
• Est. Priority Date: 01/11/2017
• Status: Active Grant

• Current Assignee: Sprinklr Inc.
• Original Assignee: Sprinklr Inc.
• Inventors: Thomas, Ragy, Alessandroni, Jared
• Primary Examiner(s): Nguyen, Minh Chau
• Application Number:
  US16/275,043
• Publication Number:
  US 20190182324A1
• Time in Patent Office: 468 Days
• Field of Search: 709223
• CPC Class Codes: G06F 16/00 Information retrieval; Database structures therefor; File system structures therefor
• CPC Class Codes: H04L 63/00 Network architectures or network communication protocols for network security cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00; network architectures or network communication protocols for wireless network security H04W12/00; security arrangements for protecting computers or computer systems against unauthorised activity G06F21/00
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/306 User profiles

Abstract

An object-oriented data management method and system comprising nested structural-elements that form inter-related containers of IRC-Infoids that include information, processing-rules, and an atomic-action layer, enabling functions to operate across disparate-systems using self-normalizing data-definitions is disclosed. The creation and management of the IRC-Infoid objects, rules and actions are handled by an IRC-Infoid Engine. The IRC-Infoid is an object with its own definitions, properties, and rules, related to a single parent element. Six properties define the IRC-Infoid: event, user, file, message, data and relationship. These properties follow inter-relationship rules, which force internal consistency, data optimization, and maintain data integrity. The IRC-Infoid data structure includes documentation, thought leadership and chatter, which when parsed through the rule sets, gets attached to standard or triggered actions, including periodic updates and called actions for use across disparate systems.

Claims

1. An object-oriented data management system comprising:

memory for storing data;

a processor operatively coupled to the memory, the processor comprising an Inter-Related Container of Infoids (IRC-Infoid) engine that receives disparate data types and creates and manages standardized IRC-Infoid data structures, wherein the standardized IRC-Infoid data structure comprises information, processing-rules, and an atomic-action layer, enabling functions to operate across disparate-systems using data-definitions; and

an IRC-Infoid runner operatively coupled to the IRC-Infoid engine, wherein the IRC-Infoid runner exposes application program interface (API) endpoints for create, read, update, and delete (CRUD) and batch import and export of data,

wherein the IRC-Infoid runner comprises an authentication and create, read, update, and delete (CRUD) module that exposes the API end points to websites, social media sites and external data storage systems,

wherein the authentication and CRUD module enables the IRC-Infoid runner to authenticate itself with the websites and social media sites to enable extraction and import of data and information from the websites, social media sites, and external data storage systems and export the standardized data as IRC-Infoids.

2. The system of claim 1, wherein the standardized IRC-Infoid is defined by properties, wherein the properties comprise event, user, file, message, data and relationship.

3. The system of claim 2, wherein the properties follow inter-relationship rules to force internal consistency, data optimization, and maintain data integrity of the standardized IRC-Infoid data.

4. The system of claim 1, wherein the standardized IRC-Infoid data structure comprises documentation, thought leadership and chatter, which when parsed through rule sets, gets attached to standard or triggered actions.

5. The system of claim 1, wherein the IRC-Infoid Engine further validates internal consistency of rules.

6. The system of claim 1, wherein the IRC-Infoid runner is coupled to at least one of:

social networking websites, cloud storage facilities, and other data storage facilities.

7. The system of claim 1, further comprising a user Infoid group coupled to the IRC-Infoid Runner, wherein the user Infoid group comprises stored user preferences Infoids of users of the system.

8. The system of claim 1, further comprising a structural standardization module to check the structural integrity and standard format of any collected and compiled data and information.

9. The system of claim 1, further comprising a rule conformity check and verification module to check the standardized data and information sets to see that they are conform to the set of rules established for the data structures for the users.

10. The system of claim 1, further comprising a user interface that comprises a user request input module and a user response module.

11. An object-oriented data management system comprising:

memory for storing data;

a processor operatively coupled to the memory, the processor comprising an IRC-Infoid engine that receives disparate data types and creates and manages standardized IRC-Infoid data structures, the processor configured to;

define a construct and data structure of a standardized IRC-Infoid, wherein the standardized IRC-Infoid data structure comprises information, processing-rules, and an atomic-action layer, enabling functions to operate across disparate-systems using data-definitions;

generate a structurally standardized data model of the IRC-Infoid by defining structural standardization checks, rule checks and verification checks;

instantiate an Infoid system with the IRC-Infoid engine comprising an Infoid runner, an authentication module, a standardization check module, a rule check module, a linkage to a user interface, and a user Infoid group which is further linked to links to user preference Infoid modules and to a user data store for storing user data sets;

implement the authentication module, the Infoid runner authenticating itself with websites, social media sites and data stores; and

implement the structured data model, the Infoid runner establishing a capability to convert disparate data streams that may be accessed by the Infoid runner to a standardized structured form as a IRC-Infoid structure, wherein the Infoid runner parses the data to extract relevant information and converts the collected relevant data using the set of rules established for the standardized and structured data.

12. The system of claim 11, wherein the processor is further configured to:

once the structure of the collected data is finalized, establish a set of rules that check and verify the consistency of the data structure within a checker module, wherein the set of rules ensure data integrity, security and valuation of the structured Infoid data set.

13. The system of claim 12, wherein the rules comprise data integrity rules, structural conformity and structural integrity rules, self-depreciation rules, permission rules and access control, and valuation rules.

14. The system of claim 11, wherein the processor is further configured to:

generate user preference IRC-Infoids for users of the system.

15. The system of claim 14, wherein in generating the user preference IRC-Infoids for users of the system, the processor is configured to:

identify approved users of the system;

collect user level of access to the data and determining security status of individual users for each identified user of the system;

collect user preferences;

compile a user profile for each individual user;

input the user profiles for each of the individual users who are allowed to access the system into the Infoid runner;

format the input user profiles to produce a nested IRC-Infoid of the profile for each of the individual users;

check the IRC-Infoid to ensure that the IRC-Infoid conform to the structure of the Infoids using the structure standardization checker module;

check the IRC-Infoid for conformity to the rules of the Infoids using the rules conformity check and verification module; and

save and link the checked IRC-Infoids of the individual users to an individual user IRC-Infoid data-store as part of a user Infoid group and the data set in the IRC-Infoid Data store within the Infoid system.

18. The system of claim 11, wherein the standardized structured relevant data comprises:

relationship information, time constraints, actions, internal support documentation, and actual constraints of the data storage structure.

19. The system of claim 11, wherein the processor is further configured to:

accept user inputs and based on the user inputs, access and collect data and information from the websites, social media sites and data stores to generate and store the generated IRC-Infoids in the User data set.

20. The system of claim 11, wherein the processor is further configured to:

collect data and convert the data into the standardized IRC-Infoid format; and

save the converted data.

16. The system of 11, wherein the processor is further configured to:

generate the user preference-related data in the standardized form of IRC-Infoids.

17. The system of claim 16, wherein in generating the user preference-related data in the standardized form of IRC-Infoids, the processor is configured to:

authenticate the Infoid runner with websites and data storage units prior to engaging with the websites and data storage units;

check user preferences saved in user preference IRC-Infoid locations to determine if any changes have been made by the Infoid engine;

check the websites and data storage units to find information data and support documentation matching the user preferences;

pull the identified information and data available in a plurality of formats from the web sites and data storage units matching the user preferences for processing them to a standardized format;

convert the information, data and supporting documentation collected into the standardized form of the IRC-Infoid;

check the IRC-Infoid for structural integrity;

check the IRC-Infoid for conformity to the rule set of the IRC-Infoid standard; and

store the checked and verified information and data as linked IRC-Infoids in a data store as individual user IRC-Infoids with any related documentation.