Abstract: This disclosure generally relates to computer-implemented analytics, and more particularly to systems and methods for improved security and precision in executing analytics using SDKs. In one embodiment, an analytics system is disclosed, comprising: a processor; and a memory device operatively connected to the processor and storing processor-executable instructions for: receiving an application programming interface (API) call for a service; parsing the API call to extract an API call name and one or more API call parameters; generating prediction values for one or more interpreted-data parameters; obtaining one or more analytics rules; performing, to generate an analytics result, an analytics operation according to the one or more analytics rules, using the generated prediction values for the one or more interpreted-data parameters and the extracted one or more API call parameters; generating a visual representation of the analytics result; and providing the visual representation of the analytics result.
CLIAMS:We claim:
1. An analytics system, comprising:
a processor; and
a memory device operatively connected to the processor and storing processor-executable instructions for:
receiving an application programming interface (API) call for a service;
parsing the API call to extract an API call name and one or more API call parameters;
generating prediction values for one or more interpreted-data parameters;
obtaining one or more analytics rules;
performing, to generate an analytics result, an analytics operation according to the one or more analytics rules, using the generated prediction values for the one or more interpreted-data parameters and the extracted one or more API call parameters;
generating a visual representation of the analytics result; and
providing the visual representation of the analytics result.
2. The system of claim 1, the memory device further storing instructions for:
obtaining a user input requesting a new iteration of prediction values for the one or more interpreted-data parameters; and
wherein generating prediction values for the one or more interpreted-data parameters may include updating previously generated values for the one or more interpreted-data parameters.
3. The system of claim 2, wherein the generated prediction values for the one or more interpreted-data parameters are selected from a plurality of predetermined values, with the value selections for the parameters being independent of each other.
4. The system of claim 3, wherein the one or more interpreted-data parameters are selected via user input.
5. The system of claim 4, wherein the user input is obtained after determining that user input is required for generating prediction values for one or more interpreted-data parameters rather than programmatic selection of the prediction values.
6. The system of claim 3, wherein the generated prediction values for a subset of the one or more interpreted-data parameters are utilized to generate the prediction values for another subset of the one or more interpreted-data parameters.
7. The system of claim 1, wherein the service is a web application service.
8. The system of claim 1, wherein one or more of the analytics rules are obtained from a secure database configured to be accessible to an operator of the analytics system but inaccessible to: a user device providing the API call; a developer of an application executing on the user device providing the API call; and a service provider of the service.
9. The system of claim 1, wherein identifications of one or more of the analytics rules are included in the API call.
10. The system of claim 1, the memory device further storing instructions for:
generating at least one of: a new API call name; or a new API call address, using the extracted the API call name or the one or more API call parameters;
generating a new API call for the service using the generated at least one of: the new API call name; or the new API call address; and
providing the generated new API call for the service.
11. The system of claim 10, wherein the new API call name is generated, by extracting a string subset of the API call name.
12. The system of claim 11, wherein an API call address for the generated new API call is the same as an API call address for the received API call for the service.
13. The system of claim 10, wherein the new API call address is generated, by providing the API call name as input to a lookup table.
14. The system of claim 13, wherein an API call name for the generated new API call is the same as the API call name.
15. An analytics method, comprising:
receiving an application programming interface (API) call for a service;
parsing the API call to extract an API call name and one or more API call parameters;
generating, via a processor, prediction values for one or more interpreted-data parameters;
obtaining one or more analytics rules;
performing, to generate an analytics result, an analytics operation, via the processor, according to the one or more analytics rules, using the generated prediction values for the one or more interpreted-data parameters and the extracted one or more API call parameters;
generating a visual representation of the analytics result; and
providing the visual representation of the analytics result.
16. The method of claim 15, further comprising:
obtaining a user input requesting a new iteration of prediction values for the one or more interpreted-data parameters; and
wherein generating prediction values for the one or more interpreted-data parameters may include updating previously generated values for the one or more interpreted-data parameters.
17. The method of claim 16, wherein the generated prediction values for the one or more interpreted-data parameters are selected from a plurality of predetermined values, with the value selections for the parameters being independent of each other.
18. The method of claim 17, wherein the one or more interpreted-data parameters are selected via user input.
19. The method of claim 18, wherein the user input is obtained after determining that user input is required for generating prediction values for one or more interpreted-data parameters rather than programmatic selection of the prediction values.
20. The method of claim 17, wherein the generated prediction values for a subset of the one or more interpreted-data parameters are utilized to generate the prediction values for another subset of the one or more interpreted-data parameters.
21. The method of claim 15, wherein the service is a web application service.
22. The method of claim 15, wherein one or more of the analytics rules are obtained from a secure database configured to be accessible to an operator of the analytics system but inaccessible to: a user device providing the API call; a developer of an application executing on the user device providing the API call; and a service provider of the service.
23. The method of claim 15, wherein identifications of one or more of the analytics rules are included in the API call.
24. The method of claim 15, further comprising:
generating at least one of: a new API call name; or a new API call address, using the extracted the API call name or the one or more API call parameters;
generating a new API call for the service using the generated at least one of: the new API call name; or the new API call address; and
providing the generated new API call for the service.
25. The method of claim 24, wherein the new API call name is generated, by extracting a string subset of the API call name.
26. The method of claim 25, wherein an API call address for the generated new API call is the same as an API call address for the received API call for the service.
27. The method of claim 24, wherein the new API call address is generated, by providing the API call name as input to a lookup table.
28. The method of claim 27, wherein an API call name for the generated new API call is the same as the API call name.
29. A non-transitory computer-readable medium storing computer-executable analytics instructions, comprising instructions for:
receiving an application programming interface (API) call for a service;
parsing the API call to extract an API call name and one or more API call parameters;
generating prediction values for one or more interpreted-data parameters;
obtaining one or more analytics rules;
performing, to generate an analytics result, an analytics operation according to the one or more analytics rules, using the generated prediction values for the one or more interpreted-data parameters and the extracted one or more API call parameters;
generating a visual representation of the analytics result; and
providing the visual representation of the analytics result.
30. The medium of claim 29, further storing instructions for:
obtaining a user input requesting a new iteration of prediction values for the one or more interpreted-data parameters; and
wherein generating prediction values for the one or more interpreted-data parameters may include updating previously generated values for the one or more interpreted-data parameters.
31. The medium of claim 30, wherein the generated prediction values for the one or more interpreted-data parameters are selected from a plurality of predetermined values, with the value selections for the parameters being independent of each other.
32. The medium of claim 31, wherein the one or more interpreted-data parameters are selected via user input.
33. The medium of claim 32, wherein the user input is obtained after determining that user input is required for generating prediction values for one or more interpreted-data parameters rather than programmatic selection of the prediction values.
34. The medium of claim 31, wherein the generated prediction values for a subset of the one or more interpreted-data parameters are utilized to generate the prediction values for another subset of the one or more interpreted-data parameters.
35. The medium of claim 29, wherein the service is a web application service.
36. The medium of claim 29, wherein one or more of the analytics rules are obtained from a secure database configured to be accessible to an operator of the analytics system but inaccessible to: a user device providing the API call; a developer of an application executing on the user device providing the API call; and a service provider of the service.
37. The medium of claim 29, wherein identifications of one or more of the analytics rules are included in the API call.
38. The medium of claim 29, further storing instructions for:
generating at least one of: a new API call name; or a new API call address, using the extracted the API call name or the one or more API call parameters;
generating a new API call for the service using the generated at least one of: the new API call name; or the new API call address; and
providing the generated new API call for the service.
39. The medium of claim 38, wherein the new API call name is generated, by extracting a string subset of the API call name.
40. The medium of claim 39, wherein an API call address for the generated new API call is the same as an API call address for the received API call for the service.
41. The medium of claim 38, wherein the new API call address is generated, by providing the API call name as input to a lookup table.
42. The medium of claim 41, wherein an API call name for the generated new API call is the same as the API call name.
Dated this 09th day of May, 2013
MADHUSUDAN S.T
K&S PARTNERS
AGENT FOR THE APPLICANT
,TagSPECI:TECHNICAL FIELD
This disclosure generally relates to computer-implemented analytics, and more particularly to systems and methods for improved security and precision in executing analytics using SDKs.
| # | Name | Date |
|---|---|---|
| 1 | 2072-CHE-2013 FORM-9 09-05-2013.pdf | 2013-05-09 |
| 1 | 2072-CHE-2013-IntimationOfGrant18-04-2023.pdf | 2023-04-18 |
| 2 | 2072-CHE-2013-PatentCertificate18-04-2023.pdf | 2023-04-18 |
| 2 | IP23623-Spec.pdf | 2013-05-10 |
| 3 | IP23623-FIG.pdf | 2013-05-10 |
| 3 | 2072-CHE-2013-Written submissions and relevant documents [16-03-2023(online)].pdf | 2023-03-16 |
| 4 | FORM 5.pdf | 2013-05-10 |
| 4 | 2072-CHE-2013-AMENDED DOCUMENTS [09-02-2023(online)].pdf | 2023-02-09 |
| 5 | FORM 3.pdf | 2013-05-10 |
| 5 | 2072-CHE-2013-Correspondence to notify the Controller [09-02-2023(online)].pdf | 2023-02-09 |
| 6 | 2072-CHE-2013-FORM 13 [09-02-2023(online)].pdf | 2023-02-09 |
| 6 | 2072-CHE-2013 FORM-13 14-05-2013.pdf | 2013-05-14 |
| 7 | 2072-CHE-2013-POA [09-02-2023(online)].pdf | 2023-02-09 |
| 7 | 2072-CHE-2013 CORRESPONDENCE OTHERS 14-05-2013.pdf | 2013-05-14 |
| 8 | 2072-CHE-2013-US(14)-HearingNotice-(HearingDate-01-03-2023).pdf | 2023-02-01 |
| 8 | 2072-CHE-2013 FORM-18 04-07-2013.pdf | 2013-07-04 |
| 9 | 2072-CHE-2013 CORRESPONDENCE OTHERS 04-07-2013.pdf | 2013-07-04 |
| 9 | 2072-CHE-2013-FER_SER_REPLY [11-11-2019(online)].pdf | 2019-11-11 |
| 10 | 2072-CHE-2013 FORM-1 16-07-2013.pdf | 2013-07-16 |
| 10 | 2072-CHE-2013-Annexure [08-11-2019(online)].pdf | 2019-11-08 |
| 11 | 2072-CHE-2013 CORRESPODNENCE OTHERS 16-07-2013.pdf | 2013-07-16 |
| 11 | 2072-CHE-2013-FORM 3 [08-11-2019(online)].pdf | 2019-11-08 |
| 12 | 2072-CHE-2013 FORM-3 03-09-2013.pdf | 2013-09-03 |
| 12 | 2072-CHE-2013-FER.pdf | 2019-05-09 |
| 13 | 2072-CHE-2013 FORM-3 03-09-2013.pdf | 2013-09-03 |
| 13 | 2072-CHE-2013-FER.pdf | 2019-05-09 |
| 14 | 2072-CHE-2013 CORRESPODNENCE OTHERS 16-07-2013.pdf | 2013-07-16 |
| 14 | 2072-CHE-2013-FORM 3 [08-11-2019(online)].pdf | 2019-11-08 |
| 15 | 2072-CHE-2013 FORM-1 16-07-2013.pdf | 2013-07-16 |
| 15 | 2072-CHE-2013-Annexure [08-11-2019(online)].pdf | 2019-11-08 |
| 16 | 2072-CHE-2013 CORRESPONDENCE OTHERS 04-07-2013.pdf | 2013-07-04 |
| 16 | 2072-CHE-2013-FER_SER_REPLY [11-11-2019(online)].pdf | 2019-11-11 |
| 17 | 2072-CHE-2013-US(14)-HearingNotice-(HearingDate-01-03-2023).pdf | 2023-02-01 |
| 17 | 2072-CHE-2013 FORM-18 04-07-2013.pdf | 2013-07-04 |
| 18 | 2072-CHE-2013-POA [09-02-2023(online)].pdf | 2023-02-09 |
| 18 | 2072-CHE-2013 CORRESPONDENCE OTHERS 14-05-2013.pdf | 2013-05-14 |
| 19 | 2072-CHE-2013-FORM 13 [09-02-2023(online)].pdf | 2023-02-09 |
| 19 | 2072-CHE-2013 FORM-13 14-05-2013.pdf | 2013-05-14 |
| 20 | FORM 3.pdf | 2013-05-10 |
| 20 | 2072-CHE-2013-Correspondence to notify the Controller [09-02-2023(online)].pdf | 2023-02-09 |
| 21 | FORM 5.pdf | 2013-05-10 |
| 21 | 2072-CHE-2013-AMENDED DOCUMENTS [09-02-2023(online)].pdf | 2023-02-09 |
| 22 | IP23623-FIG.pdf | 2013-05-10 |
| 22 | 2072-CHE-2013-Written submissions and relevant documents [16-03-2023(online)].pdf | 2023-03-16 |
| 23 | IP23623-Spec.pdf | 2013-05-10 |
| 23 | 2072-CHE-2013-PatentCertificate18-04-2023.pdf | 2023-04-18 |
| 24 | 2072-CHE-2013-IntimationOfGrant18-04-2023.pdf | 2023-04-18 |
| 24 | 2072-CHE-2013 FORM-9 09-05-2013.pdf | 2013-05-09 |
| 1 | 2072_08-05-2019.pdf |