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

• US 10,397,326 B2
• Filed: 01/11/2017
• Issued: 08/27/2019
• Est. Priority Date: 01/11/2017
• Status: Active Grant

• Current Assignee: TPG Specialty Lending Incorporated
• Original Assignee: Sprinklr Inc.
• Inventors: Thomas, Ragy, Alessandroni, Jared
• Primary Examiner(s): Nguyen, Minh Chau
• Application Number:
  US15/403,861
• Publication Number:
  US 20180198860A1
• Time in Patent Office: 958 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. A computerized method for object-oriented data management comprising:

defining a construct and structure of a standardized IRC-Infoid;

generating a structurally standardized data model of the IRC-Infoid, wherein generating the structurally standardized data model comprises defining structural standardization checks, rule checks and verification checks;

instantiating an Infoid system with an the Infoid processing 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;

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

using the structured data model, the Infoid runner establishes 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.

2. The method of claim 1, further comprising generating the user preference-related data in the standardized form of IRC-Infoids.

3. The method of claim 2, wherein generating the user preference-related data in the standardized form of IRC-Infoids comprises:

authenticating an Infoid runner with websites and data storage units prior to engaging with the web sites and data storage units;

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

checking the websites and data storage units to find information data and supporting documentation matching the user preferences;

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

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

checking the IRC-Infoid for structural integrity;

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

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

4. The method of claim 3, further comprising updating the stored user specific IRC-Infoids with information and data pulled from the connected websites and data storage units to keep the information current.

5. The method of claim 1, further comprising:

once the structure of the collected data is finalized, establishing 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.

6. The method of claim 5, wherein the rules comprise data integrity rules, structural conformity and structural integrity rules, self-depreciation rules, permission rules and access control, and valuation rules.

7. The method of claim 1, further comprising generating user preference IRC-Infoids for users of the system.

8. The method of claim 7, wherein generating user preference IRC-Infoids for users of the system comprises:

identifying approved users of the system;

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

collecting user preferences;

compiling a user profile for each individual user;

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

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

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

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

saving and linking 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.

9. The method of claim 1, wherein the standardized structured relevant data comprises:

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

10. The method of claim 1, further comprising:

accepting user inputs and based on the user inputs, accessing and collecting 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.

11. The method of claim 1, further comprising collecting data and converting the data into the standardized IRC-Infoid format, and saving the converted data.