Systems and methods for context development

Patent metadata

Field	Value
Publication number	US-10848451-B1
Application number	US-202016778566-A
Country	US
Kind code	B1
Filing date	Jan 31, 2020
Priority date	Jan 31, 2020
Publication date	Nov 24, 2020
Grant date	Nov 24, 2020

Abstract

Disclosed are methods, systems, and non-transitory computer-readable medium for context development. For instance, a first method may include obtaining first micro-application actor information associated with a first micro-application actor. The first micro-application actor information may include information for workflow rules, and the workflow rules may include data set rules, extract, transform, load (ETL) rules, and functional expressions. The first method may further include obtaining data from data sources based on the data set rules; applying the ETL rules to the obtained data to generate processed data; applying the functional expressions to the processed data to obtain an output; and performing at least one processing action based on the output. A second method may include generating a system component corresponding to a blueprint based on a user request; associating the system component with a domain of a user account; and performing processes associated the system component.

First claim

The invention claimed is:

1. A method, comprising:
receiving a user message from a user on a platform for developing context between a plurality of micro-application actors, wherein:
each micro-application actor is configured to retrieve a respective data set, generate an output by applying a respective set of rules to the respective data set, and perform at least one act by applying the respective set of rules to the generated output;
the user message includes a request for one of a component formation and a component edit for a micro-application actor;
the request is associated with formation of an indirect link between the micro-application actor and a second micro-application actor; and
the indirect link is a link other than a correlation between data sources of the micro-application actor and the second micro-application actor, and is a link other than a correlation between the respective data sets of the micro-application actor and the second micro-application actor;

determining whether the user message requests the component formation or the component edit for the micro-application actor;
in response to determining the user message requests the component formation, performing a component formation process to form the component such that the component includes the indirect link to the second micro-application actor;
in response to determining the user message requests the component edit, performing a component edit process to edit the component such that the component includes the indirect link to the second micro-application actor; and
based on a result of the component formation process or the component edit process, transmitting a status message to the user.

2. The method of claim 1 , wherein the determining whether the user message requests the component formation or the component edit for the micro-application actor includes:
obtaining the user message;
parsing the user message to extract a request identifier; and
determining whether the request identifier is a formation identifier or an edit identifier;
in response to determining the request identifier is the formation identifier, determining the user message requests the component formation; and
in response to determining the request identifier is the edit identifier, determining the user message requests the component edit.

3. The method of claim 1 , wherein the component formation process includes:
obtaining the user message;
parsing the user message to extract request features of a component formation request;
generating workflow rules based on the request features; and
associating the workflow rules with the micro-application actor.

4. The method of claim 3 , wherein the generating the workflow rules based on the request features includes:
determining whether the request features include an alert feature; and
in response to determining the request features include the alert feature, performing an alert formation process.

5. The method of claim 4 , wherein the alert formation process includes:
obtaining the request features;
parsing the request features to extract a data element indicator, a trigger condition, and a defined action; and
generating a program as the workflow rules, the program being configured to:
obtain data from a data source indicated by the data element indicator;
determine whether the trigger condition is satisfied based on the obtained data; and
in response to determining the trigger condition is satisfied, perform the defined action.

6. The method of claim 5 , wherein the defined action includes one or a combination of: generate/update a graphic and/or notify associated users using one or more communication channels.

7. The method of claim 1 , wherein the user message includes the request for the content formation, and the indirect link is formed via a relationship formation process that includes:
obtaining the request features;
parsing the request features to extract a micro-application actor indicator, the micro-application actor indicator indicating the second micro-application actor; and
generating a program as workflow rules of the micro-application actor, the program being configured to notify the second micro-application actor in response to a trigger condition of the micro-application actor being triggered.

8. The method of claim 1 , wherein the component edit process includes:
obtaining the user message;
parsing the user message to extract request features of a component edit request;
obtaining workflow rules associated with the micro-application actor; and
updating the workflow rules based on the request features.

9. The method of claim 8 , wherein the updating the workflow rules based on the request features includes:
determining whether the request features includes an alert feature; and
in response to determining the request features includes the alert feature, performing an alert edit process.

10. The method of claim 9 , wherein the alert edit process includes:
obtaining the request features;
parsing the request features to extract a data element indicator, a trigger condition, and a defined action;
obtaining a program of the workflow rules;
determining whether an existing data element indicator, an existing trigger condition, or an existing defined action is different from the data element indicator, the trigger condition, or the defined action, respectively; and
in response to determining the existing data element indicator, the existing trigger condition, or the existing defined action is different from the data element indicator, the trigger condition, or the defined action, updating the program with the data element indicator, the trigger condition, or the defined action that is different.

11. The method of claim 9 , wherein the user message includes the request for the component edit, and the indirect link is formed via a relationship edit process that includes:
obtaining the request features;
parsing the request features to extract a micro-application actor indicator, the micro-application actor indicator indicating the second micro-application actor;
obtaining a program of the workflow rules;
determining whether the program includes the second micro-application actor as an affected micro-application actor; and
in response to determining the program does not include the second micro-application actor as an affected micro-application actor, updating the program to include the second micro-application actor as an affected micro-application actor.

12. A system for context development on a platform, the system comprising:
a memory storing instructions; and
a processor executing the instructions to perform a process including:
receiving a user message from a user on a platform for developing context between a plurality of micro-application actors, wherein:
each micro-application actor is configured to retrieve a respective data set, generate an output by applying a respective set of rules to the respective data set, and perform at least one act by applying the respective set of rules to the generated output;
the user message includes a request for a component formation for a micro-application actor;
the request is associated with formation of an indirect link between the micro-application actor and a second micro-application actor; and
the indirect link is a link other than a correlation between data sources of the micro-application actor and the second micro-application actor, and is a link other than a correlation between the respective data sets of the micro-application actor and the second micro-application actor;

determining whether the user message requests a component formation for the

Assignees

• Capital One Services Llc

Inventors

• Moore Patrick
• Frank Colleen
• Mandali Venkata
• Criqui Bradley

Classifications

• H04L51/214

  using selective forwarding · CPC title

• H04L51/56

  Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM] · CPC title

• H04L51/046

  Interoperability with other network applications or services · CPC title

• H04L51/18 Primary

  Commands or executable codes · CPC title

• H04L51/02

  using automatic reactions or user delegation, e.g. automatic replies or chatbot-generated messages · CPC title