Abstract: Systems and methods for performing dynamic orchestration of rules in big data environment are described. The system monitors activities performed by entity in the big data environment to detect events. The events are associated with product/service. Further, the system determines scenario by analyzing data pertaining to the product or the service. The scenario comprises one or more scenario categories. Further, the scenario is correlated with the events based on the one or more scenario categories. The correlation is further validated by the system based on dimensions. Further, the system derives one or more rules for each of the correlation of the scenario and the events upon validation. The system may further apply an operational constraints and migration controls to the one or more rules to perform dynamic orchestration. Thus, the system provides one-stop solution for deriving the rules based on context of the scenarios and migrating them to target systems. FIG. 1
Claims:WE CLAIM:
1. A method of performing dynamic orchestration of rules in a big data environment, the method comprising:
monitoring, by a rule orchestration system (102), activities performed by an entity in the big data environment to detect one or more events, wherein the one or more events are associated with at least one of a product and a service;
determining, by the rule orchestration system (102), at least one scenario by analyzing data pertaining to the at least one of the product and the service, wherein the at least one scenario comprises one or more scenario categories;
correlating, by the rule orchestration system (102), the at least one scenario with the one or more events based on the one or more scenario categories;
validating, by the rule orchestration system (102), the correlation between the at least one scenario and the one or more events based on one or more dimensions, wherein the one or more dimensions indicate parameters affecting the at least one scenario;
deriving, by the rule orchestration system (102), one or more rules and corresponding rule hierarchies for each of the correlation of the at least one scenario and the one or more events upon validation; and
applying, by the rule orchestration system (102), at least one of operational constraints and migration controls to the one or more rules to perform dynamic orchestration.
2. The method as claimed in claim 1, wherein the determining the at least one scenario further comprises:
receiving, by the rule orchestration system (102), one or more predefined scenarios from a scenario database (212);
comparing, by the rule orchestration system (102), the at least one scenario with the one or more predefined scenarios to determine whether the at least one scenario is preexisting in the scenario database (212); and
updating, by the rule orchestration system (102), the at least one scenario in the scenario database (212) based on the comparing.
3. The method as claimed in claim 1, wherein the determining the at least one scenario further comprises validating the at least one scenario based on the one or more dimensions.
4. The method as claimed in claim 1 further comprises determining the one or more scenario categories associated with the at least one scenario based on a utilization map associated with least one of the product or the service and interrelationship amongst the product or the service.
5. The method as claimed in claim 1 further comprises:
determining, by the rule orchestration system (102), whether the one or more dimensions are defined to correlate with the at least one scenario;
associating, by the rule orchestration system (102), the data pertaining to the at least one of the product and the service with big data query specification based on the determining; and
deriving, by the rule orchestration system (102), the one or more dimensions based on the association.
6. The method as claimed in claim 1, wherein the one or more dimensions comprises at least one of predefined technology dimensions, application dimensions, social dimensions, economic dimensions, geolocation dimensions and legal dimensions.
7. The method as claimed in claim 1, wherein the deriving the one or more rules further comprises:
determining, by the rule orchestration system (102), whether the one or more rules are predefined in a rule database (214);
identifying, by the rule orchestration system (102), a level of the one or more rules based on a rules hierarchy based on the determining, wherein the rules hierarchy is updated dynamically based on the data pertaining to the at least one of the product and the service; and
adding, by the rule orchestration system (102), the one or more rules to the rule database (214) along with the level.
8. The method as claimed in claim 1 further comprises:
deriving, by the rule orchestration system (102), the migration controls to continuously migrate the one or more rules to one or more target systems 103; and
defining, by the rule orchestration system (102), the operational constraints in association with the migration controls.
9. A rule orchestration system (102) for performing dynamic orchestration of rules in a big data environment, the rule orchestration system (102) comprising:
a processor (204); and
a memory (206) communicatively coupled to the processor (204), wherein the memory (206) stores processor-executable instructions, which, on execution, causes the processor (204) to:
monitor activities performed by an entity in the big data environment to detect one or more events, wherein the one or more events are associated with at least one of a product and a service;
determine at least one scenario by analyzing data pertaining to the at least one of the product and the service, wherein the at least one scenario comprises one or more scenario categories;
correlate the at least one scenario with the one or more events based on the one or more scenario categories;
validate the correlation between the at least one scenario and the one or more events based on one or more dimensions, wherein the one or more dimensions indicate parameters affecting the at least one scenario;
derive one or more rules and corresponding rule hierarchies for each of the correlation of the at least one scenario and the one or more events upon validation; and
apply at least one of operational constraints and migration controls to the one or more rules to perform dynamic orchestration.
10. The rule orchestration system (102) as claimed in claim 9 determines the at least one scenario by further performing steps to:
receive one or more predefined scenarios from a scenario database (212);
compare the at least one scenario with the one or more predefined scenarios to determine whether the at least one scenario is preexisting in the scenario database (212); and
update the at least one scenario in the scenario database (212) based on the comparing.
11. The rule orchestration system (102) as claimed in claim 9 determines the at least one scenario by validating the at least one scenario based on the one or more dimensions.
12. The rule orchestration system (102) as claimed in claim 9 determines the one or more scenario categories associated with the at least one scenario based on a utilization map associated with least one of the product or the service and interrelationship amongst the product or the service.
13. The rule orchestration system (102) as claimed in claim 9 further configured to:
determine whether the one or more dimensions are defined to correlate with the at least one scenario;
associate the data pertaining to the at least one of the product and the service with big data query specification based on the determining; and
derive the one or more dimensions based on the association.
14. The rule orchestration system (102) as claimed in claim 9, wherein the one or more dimensions comprises at least one of predefined technology dimensions, application dimensions, social dimensions, economic dimensions, geolocation dimensions and legal dimensions.
15. The rule orchestration system (102) as claimed in claim 9 derives the one or more rules by performing steps to:
determine whether the one or more rules are predefined in a rule database (214);
identify a level of the one or more rules based on a rules hierarchy based on the determining, wherein the rules hierarchy is updated dynamically based on the data pertaining to the at least one of the product and the service; and
add the one or more rules to the rule database (214) along with the level.
16. The rule orchestration system (102) as claimed in claim 9 further configured to:
derive the migration controls to continuously migrate the one or more rules to one or more target systems (104); and
define the operational constraints in association with the migration controls.
Dated this 17th day of August, 2016
Swetha SN
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
The present disclosure relates in general to data analytics. More particularly, but not exclusively, the present disclosure discloses a method and system for dynamic orchestration of business rules in a big data environment.
| # | Name | Date |
|---|---|---|
| 1 | 201644028072-PROOF OF ALTERATION [17-10-2023(online)].pdf | 2023-10-17 |
| 1 | Form9_Earlier Publication_17-08-2016.pdf | 2016-08-17 |
| 2 | 201644028072-IntimationOfGrant20-07-2023.pdf | 2023-07-20 |
| 2 | Form 5 [17-08-2016(online)].pdf | 2016-08-17 |
| 3 | Form 3 [17-08-2016(online)].pdf | 2016-08-17 |
| 3 | 201644028072-PatentCertificate20-07-2023.pdf | 2023-07-20 |
| 4 | Form 18 [17-08-2016(online)].pdf_227.pdf | 2016-08-17 |
| 4 | 201644028072-FER_SER_REPLY [23-06-2020(online)].pdf | 2020-06-23 |
| 5 | Form 18 [17-08-2016(online)].pdf | 2016-08-17 |
| 5 | 201644028072-FORM 3 [23-06-2020(online)].pdf | 2020-06-23 |
| 6 | Drawing [17-08-2016(online)].pdf | 2016-08-17 |
| 6 | 201644028072-Information under section 8(2) [23-06-2020(online)].pdf | 2020-06-23 |
| 7 | Description(Complete) [17-08-2016(online)].pdf | 2016-08-17 |
| 7 | 201644028072-FER.pdf | 2020-03-11 |
| 8 | Form 26 [22-08-2016(online)].pdf | 2016-08-22 |
| 8 | Correspondence by Agent_Form1_10-11-2016.pdf | 2016-11-10 |
| 9 | 201644028072-Power of Attorney-240816.pdf | 2016-09-22 |
| 9 | Other Patent Document [07-11-2016(online)].pdf | 2016-11-07 |
| 10 | 201644028072-Correspondence-PA-240816.pdf | 2016-09-22 |
| 10 | Other Patent Document [07-11-2016(online)].pdf_37.pdf | 2016-11-07 |
| 11 | 201644028072-Correspondence-PA-240816.pdf | 2016-09-22 |
| 11 | Other Patent Document [07-11-2016(online)].pdf_37.pdf | 2016-11-07 |
| 12 | 201644028072-Power of Attorney-240816.pdf | 2016-09-22 |
| 12 | Other Patent Document [07-11-2016(online)].pdf | 2016-11-07 |
| 13 | Correspondence by Agent_Form1_10-11-2016.pdf | 2016-11-10 |
| 13 | Form 26 [22-08-2016(online)].pdf | 2016-08-22 |
| 14 | 201644028072-FER.pdf | 2020-03-11 |
| 14 | Description(Complete) [17-08-2016(online)].pdf | 2016-08-17 |
| 15 | 201644028072-Information under section 8(2) [23-06-2020(online)].pdf | 2020-06-23 |
| 15 | Drawing [17-08-2016(online)].pdf | 2016-08-17 |
| 16 | 201644028072-FORM 3 [23-06-2020(online)].pdf | 2020-06-23 |
| 16 | Form 18 [17-08-2016(online)].pdf | 2016-08-17 |
| 17 | 201644028072-FER_SER_REPLY [23-06-2020(online)].pdf | 2020-06-23 |
| 17 | Form 18 [17-08-2016(online)].pdf_227.pdf | 2016-08-17 |
| 18 | Form 3 [17-08-2016(online)].pdf | 2016-08-17 |
| 18 | 201644028072-PatentCertificate20-07-2023.pdf | 2023-07-20 |
| 19 | Form 5 [17-08-2016(online)].pdf | 2016-08-17 |
| 19 | 201644028072-IntimationOfGrant20-07-2023.pdf | 2023-07-20 |
| 20 | Form9_Earlier Publication_17-08-2016.pdf | 2016-08-17 |
| 20 | 201644028072-PROOF OF ALTERATION [17-10-2023(online)].pdf | 2023-10-17 |
| 1 | searchE_05-03-2020.pdf |