Abstract: The present disclosure discloses a method and system for integrating a dynamic scene Database (DB) with a Human Machine Interface (HMI) application. The method comprises receiving a scene specification. The scene specification comprises scene data and one or more parameters associated with the scene data. Further, a data pool and a design interface are generated based on the scene specification and a business logic associated with the scene data. Thereafter, a dynamic scene DB is developed based on the one or more parameters, the data pool and the design interface. Furthermore, the scene data in the dynamic scene DB is updated when the scene data in the scene specification is updated. Lastly, the dynamic scene DB is integrated with a HMI application for displaying a view. The HMI application retrieves the updated scene data from the dynamic scene DB for displaying an updated view. Figure 1
Claims:We claim:
1. A method for integrating a dynamic scene Database (DB) with a Human Machine Interface (HMI) application, the method comprising:
receiving, by a Database (DB) development tool, a scene specification from one or more input sources, wherein the scene specification comprises scene data and one or more parameters associated with the scene data, wherein the scene data represents a view;
associating, by the DB development tool, the scene data with a business logic, wherein associating comprises generating a data pool and design interface;
developing, by the DB development tool, a dynamic scene DB based on at least one of the data pool, the design interface and the one or more parameters, wherein the dynamic scene DB comprises the scene data of the scene specification;
updating, by the DB development tool, the scene data in the dynamic scene DB when at least one of the scene data in the scene specification and the business logic is updated; and
integrating, by the DB development tool, the dynamic scene DB with a HMI application for displaying the view, wherein the HMI application retrieves the updated scene data from the dynamic scene DB for implementing at least one of the updated business logic and the updated scene data.
2. The method as claimed in claim 1, wherein the scene specification is in a scene specification format.
3. The method as claimed in claim 1, wherein the scene data comprises at least one of one or more screens, one or more containers, one or more widgets, one or more texts, one or more numerical, and one or more symbols.
4. The method as claimed in claim 1, wherein the dynamic scene DB is updated using one or more queries, and wherein each of the one or more queries is configured to perform an action.
5. The method as claimed in claim 1, further comprises testing the dynamic scene DB, wherein the testing comprises performing an independent test on the updated scene data.
6. The method as claimed in claim 1, wherein developing the scene DB comprises:
parsing one or more layers of the scene data;
detecting at least one vector object from the scene data;
identifying at least one container and corresponding one or more widgets, based on the at least one vector object;
extracting one or more parameters of the one or more widgets;
extracting one or more raster images from the scene data to determine pixel parameters of each of the one or more widgets; and
updating the scene DB with the one or more parameters of the one or more widgets and corresponding pixel parameters.
7. The method as claimed in claim 1, wherein the scene data is associated with a unique Identity (ID).
8. A dynamic scene Database (DB) development tool for integrating with a Human Machine Interface (HMI) application, comprising:
a processor; and
a memory, communicatively coupled with the processor, which stores processor executable instructions, which on execution causes the processor to:
receive a scene specification from one or more input sources, wherein the scene specification comprises scene data and one or more parameters associated with the scene data, wherein the scene data represents a view;
associate the scene data with a business logic, wherein associating comprises generating a data pool and design interface;
develop a dynamic scene DB based on at least one of the data pool, the design interface and the one or more parameters, wherein the dynamic scene DB comprises the scene data of the scene specification;
update the scene data in the dynamic scene DB when at least one of the scene data in the scene specification and the business logic is updated; and
integrate the dynamic scene DB with a HMI application for displaying the view, wherein the HMI application retrieves the updated scene data from the dynamic scene DB for implementing at least one of the updated business logic and the updated scene data.
9. The dynamic scene DB development tool as claimed in claim 8, wherein the scene specification is in a scene specification format.
10. The dynamic scene DB development tool as claimed in claim 8, wherein the scene data comprises at least one of a screen, a container, a widget, a text, a numerical, and a symbol.
11. The dynamic scene DB development tool as claimed in claim 8, wherein the dynamic scene DB is updated using one or more queries, and wherein each of the one or more queries is configured to perform an action.
12. The dynamic scene DB development tool as claimed in claim 8, wherein the processor is further configured to test the dynamic scene DB, wherein the test comprises performing an independent test on the updated scene data.
13. The dynamic scene DB development tool as claimed in claim 8, wherein during developing the scene DB, the processor is configured to:
parse one or more layers of the scene data;
detect at least one vector object from the scene data;
identify at least one container and corresponding one or more widgets, based on the at least one vector object;
extract one or more parameters of the one or more widgets;
extract one or more raster images from the scene data to determine pixel parameters of each of the one or more widgets; and
update the scene DB with the one or more parameters of the one or more widgets and corresponding pixel parameters.
14. The dynamic scene DB development tool as claimed in claim 8, wherein the scene data is associated with a unique Identity (ID).
Dated this 16th day of February, 2018
R Ramya Rao
IN/PA-1607
Of K&S Partners
Agent for the Applicant
, Description:TECHNICAL FIELD
The present disclosure relates to Human Machine Interface (HMI). More specifically, but not exclusively, the present disclosure relates to a method and a system for integrating a scene database with a HMI application.
| Section | Controller | Decision Date |
|---|---|---|
| 15,43 | raj kumar | 2023-10-17 |
| 15,43 | raj kumar | 2023-10-17 |
| # | Name | Date |
|---|---|---|
| 1 | 201841005971-IntimationOfGrant17-10-2023.pdf | 2023-10-17 |
| 1 | 201841005971-STATEMENT OF UNDERTAKING (FORM 3) [16-02-2018(online)].pdf | 2018-02-16 |
| 2 | 201841005971-PatentCertificate17-10-2023.pdf | 2023-10-17 |
| 2 | 201841005971-REQUEST FOR EXAMINATION (FORM-18) [16-02-2018(online)].pdf | 2018-02-16 |
| 3 | 201841005971-Written submissions and relevant documents [06-10-2023(online)].pdf | 2023-10-06 |
| 3 | 201841005971-POWER OF AUTHORITY [16-02-2018(online)].pdf | 2018-02-16 |
| 4 | 201841005971-FORM 18 [16-02-2018(online)].pdf | 2018-02-16 |
| 4 | 201841005971-AMENDED DOCUMENTS [29-08-2023(online)].pdf | 2023-08-29 |
| 5 | 201841005971-FORM 1 [16-02-2018(online)].pdf | 2018-02-16 |
| 5 | 201841005971-Correspondence to notify the Controller [29-08-2023(online)].pdf | 2023-08-29 |
| 6 | 201841005971-FORM 13 [29-08-2023(online)].pdf | 2023-08-29 |
| 6 | 201841005971-DRAWINGS [16-02-2018(online)]_70.pdf | 2018-02-16 |
| 7 | 201841005971-POA [29-08-2023(online)].pdf | 2023-08-29 |
| 7 | 201841005971-DRAWINGS [16-02-2018(online)].pdf | 2018-02-16 |
| 8 | 201841005971-US(14)-HearingNotice-(HearingDate-21-09-2023).pdf | 2023-08-24 |
| 8 | 201841005971-DECLARATION OF INVENTORSHIP (FORM 5) [16-02-2018(online)].pdf | 2018-02-16 |
| 9 | 201841005971-COMPLETE SPECIFICATION [16-02-2018(online)]_71.pdf | 2018-02-16 |
| 9 | 201841005971-FER.pdf | 2021-10-17 |
| 10 | 201841005971-CLAIMS [22-09-2021(online)].pdf | 2021-09-22 |
| 10 | 201841005971-COMPLETE SPECIFICATION [16-02-2018(online)].pdf | 2018-02-16 |
| 11 | 201841005971-COMPLETE SPECIFICATION [22-09-2021(online)].pdf | 2021-09-22 |
| 11 | abstract 201841005971 .jpg | 2018-02-20 |
| 12 | 201841005971-DRAWING [22-09-2021(online)].pdf | 2021-09-22 |
| 12 | 201841005971-REQUEST FOR CERTIFIED COPY [05-03-2018(online)]_15.pdf | 2018-03-05 |
| 13 | 201841005971-FER_SER_REPLY [22-09-2021(online)].pdf | 2021-09-22 |
| 13 | 201841005971-REQUEST FOR CERTIFIED COPY [05-03-2018(online)].pdf | 2018-03-05 |
| 14 | 201841005971-FORM 3 [22-09-2021(online)].pdf | 2021-09-22 |
| 14 | 201841005971-Proof of Right (MANDATORY) [02-05-2018(online)].pdf | 2018-05-02 |
| 15 | 201841005971-Information under section 8(2) [22-09-2021(online)].pdf | 2021-09-22 |
| 15 | Correspondence by Agent_Form 1_07-05-2018.pdf | 2018-05-07 |
| 16 | 201841005971-OTHERS [22-09-2021(online)].pdf | 2021-09-22 |
| 16 | 201841005971-PETITION UNDER RULE 137 [22-09-2021(online)].pdf | 2021-09-22 |
| 17 | 201841005971-PETITION UNDER RULE 137 [22-09-2021(online)].pdf | 2021-09-22 |
| 17 | 201841005971-OTHERS [22-09-2021(online)].pdf | 2021-09-22 |
| 18 | 201841005971-Information under section 8(2) [22-09-2021(online)].pdf | 2021-09-22 |
| 18 | Correspondence by Agent_Form 1_07-05-2018.pdf | 2018-05-07 |
| 19 | 201841005971-FORM 3 [22-09-2021(online)].pdf | 2021-09-22 |
| 19 | 201841005971-Proof of Right (MANDATORY) [02-05-2018(online)].pdf | 2018-05-02 |
| 20 | 201841005971-FER_SER_REPLY [22-09-2021(online)].pdf | 2021-09-22 |
| 20 | 201841005971-REQUEST FOR CERTIFIED COPY [05-03-2018(online)].pdf | 2018-03-05 |
| 21 | 201841005971-DRAWING [22-09-2021(online)].pdf | 2021-09-22 |
| 21 | 201841005971-REQUEST FOR CERTIFIED COPY [05-03-2018(online)]_15.pdf | 2018-03-05 |
| 22 | 201841005971-COMPLETE SPECIFICATION [22-09-2021(online)].pdf | 2021-09-22 |
| 22 | abstract 201841005971 .jpg | 2018-02-20 |
| 23 | 201841005971-CLAIMS [22-09-2021(online)].pdf | 2021-09-22 |
| 23 | 201841005971-COMPLETE SPECIFICATION [16-02-2018(online)].pdf | 2018-02-16 |
| 24 | 201841005971-FER.pdf | 2021-10-17 |
| 24 | 201841005971-COMPLETE SPECIFICATION [16-02-2018(online)]_71.pdf | 2018-02-16 |
| 25 | 201841005971-US(14)-HearingNotice-(HearingDate-21-09-2023).pdf | 2023-08-24 |
| 25 | 201841005971-DECLARATION OF INVENTORSHIP (FORM 5) [16-02-2018(online)].pdf | 2018-02-16 |
| 26 | 201841005971-POA [29-08-2023(online)].pdf | 2023-08-29 |
| 26 | 201841005971-DRAWINGS [16-02-2018(online)].pdf | 2018-02-16 |
| 27 | 201841005971-FORM 13 [29-08-2023(online)].pdf | 2023-08-29 |
| 27 | 201841005971-DRAWINGS [16-02-2018(online)]_70.pdf | 2018-02-16 |
| 28 | 201841005971-FORM 1 [16-02-2018(online)].pdf | 2018-02-16 |
| 28 | 201841005971-Correspondence to notify the Controller [29-08-2023(online)].pdf | 2023-08-29 |
| 29 | 201841005971-FORM 18 [16-02-2018(online)].pdf | 2018-02-16 |
| 29 | 201841005971-AMENDED DOCUMENTS [29-08-2023(online)].pdf | 2023-08-29 |
| 30 | 201841005971-Written submissions and relevant documents [06-10-2023(online)].pdf | 2023-10-06 |
| 30 | 201841005971-POWER OF AUTHORITY [16-02-2018(online)].pdf | 2018-02-16 |
| 31 | 201841005971-PatentCertificate17-10-2023.pdf | 2023-10-17 |
| 31 | 201841005971-REQUEST FOR EXAMINATION (FORM-18) [16-02-2018(online)].pdf | 2018-02-16 |
| 32 | 201841005971-IntimationOfGrant17-10-2023.pdf | 2023-10-17 |
| 32 | 201841005971-STATEMENT OF UNDERTAKING (FORM 3) [16-02-2018(online)].pdf | 2018-02-16 |
| 1 | SearchStrategyMatrixE_19-03-2021.pdf |