Abstract: A computer implemented system and method for seamlessly integrating a plurality of applications that are executable on an enterprise system. The system includes a user action tracker to track interactions of a user and an interaction repository to store the tracked interactions. The system also includes an application tracker to track at least one instance of application resident in at least one node of the enterprise system and an application repository to store the tracked instance of the application. Information related to plurality of events relating to the application, location of at least one of user/event and timing information related to the events along with information related to application history based on the user interactions and the application instances of the user interactions between the user and the application is then utilized to display different applications and their application instances and the relation between the applications and the application instances.
CLIAMS:1. A computer implemented system for seamlessly integrating a plurality of applications executable on an enterprise system, said computer implemented system comprising:
• a user action tracker cooperating with the enterprise system, said user action tracker configured to track interactions of a user with at least one instance of an application being used ;
• a first extractor adapted to extract the tracked interactions from the user action tracker;
• an interaction repository adapted to receive the extracted tracked interactions from the first extractor and store said tracked interactions;
• an application tracker cooperating with the enterprise system, said application tracker configured to track at least one instance of application resident in at least one node of said enterprise system;
• a second extractor adapted to extract the tracked instance of the application from the application tracker;
• an application repository adapted to receive the extracted tracked instance of said application from the second extractor and store said tracked instance of said application;
• an event log module configured to track a plurality of events related to said application;
• a location tracker adapted to track location of at least one of user and events;
• a timer adapted to track timing information related to said events;
• a third extractor adapted to extract the tracked events from the event log module, the tracked location from the location tracker and the tracked timing information from the timer;
• a temporary repository adapted to receive the extracted tracked events, tracked location and tracked timing information from the third extractor, and, store the received tracked events, tracked location and tracked timing information;
• a transceiver adapted to receive the tracked interactions from the interaction repository, tracked instance of the application from the application repository, and, tracked events, tracked location and tracked timing information from the temporary repository and transmit the received tracked interactions, tracked instance, tracked events, tracked location and tracked timing information;
• a data repository adapted to store application history based on the user interactions and the application instances of said user interactions between the user and the application, said data repository further having storage registers to store pre-determined rules for said user interactions;
• a context aware processing engine cooperating with said transceiver and said data repository, said context aware processing engine comprising:
i. a correlator module configured to correlate the tracked interactions, tracked instance, tracked events, tracked location and tracked timing information received from the transceiver with the stored application history and the stored pre-determined rules from the data repository to obtain correlated information;
ii. an analytical engine cooperating with the correlator, said analytical engine having a determinator that receives and analyses the correlated information to determine the next best action to be carried out by the user and transmit information related to said next best action;
iii. a workflow module adapted to receive the correlated information from the correlator, the next best action information from the analytical engine and the stored pre-determined rules from the data repository, said workflow module comprising an identifier configured to analyze the correlated information and the next best action information using stored pre-determined rules to identify whether the user needs to communicate with any other instance of said or any other application to perform the next best action and generate a resultant data;
• a transformation engine configured to receive the resultant data from the workflow module and transform the resultant data into a format desired by a particular application whose instance needs to be communicated with; and
• a user interface cooperating with the transformation engine, said user interface adapted to display an integrated view of the transformed resultant data including different applications and their application instances and the relation between said applications and said application instances.
2. The system as claimed in claim 1, wherein the system includes a user input mechanism configured to allow the user to select the application that needs communication based on users current needs to identify a communication demand.
3. The system as claimed in claim 1, wherein the system includes an application communicator configured to facilitate data communication between at least two instances of the displayed applications on identification of the communication demand by the user input mechanism.
4. The system as claimed in claim 1, wherein the system includes an integrator adapted to integrate said communication between at least two instances of the applications.
5. The system as claimed in claim 1, wherein the system includes a display cooperating with the integrator, said display configured to display the integrated view of said communication.
6. The system as claimed in claim 1, wherein the system includes an editor adapted to edit the data repository based on the integrated communication, said editor further adapted to edit the application history by editing said user interactions and said applications instances to include recent user interactions and recent application instances.
7. The system as claimed in claim 1, wherein said context aware processing engine decides whether a user has communicated with similar application for a particular context of the instance;
8. The system as claimed in claim 1, wherein said context aware processing engine further comprises an application identifier configured to identify the application most relevant to a sensed context, said application identifier further configured to highlight said most relevant application.
9. The system as claimed in claim 1, wherein said user interface further comprises an event generator configured to represent the interaction between the user and said instances of applications, in the form of an event, said event generator further configured to display said events.
10. A computer implemented method for seamlessly integrating a plurality of applications executable on an enterprise system, said computer implemented method including the steps of:
• tracking interactions of a user with at least one instance of an application being used;
• extracting the tracked interactions;
• storing the extracted tracked interactions;
• tracking at least one instance of application in at least one node of said enterprise system;
• extracting the tracked instance of the application;
• storing the extracted tracked instance of the application;
• tracking a plurality of events related to said application;
• tracking location of at least one of user and events;
• tracking timing information related to said events;
• extracting tracked events, tracked location and tracked timing information;
• storing the extracted tracked events, tracked location and tracked timing information;
• receiving the tracked interactions, tracked instance of the application, tracked events, tracked location and tracked timing information;
• transmitting the received tracked interactions, tracked instance of the application, tracked events, tracked location and tracked timing information;
• storing application history based on the user interactions and the application instances of said user interactions between the user and the applications and storing pre-determined rules for said user interactions;
• receiving the tracked interactions, tracked instance of the application, tracked events, tracked location, tracked timing information and the application history and correlating the received information to obtain correlated information;
• receiving the correlated information and analyzing the correlated information to determine the next best action to be carried out by the user;
• transmitting information related to the next best action;
• receiving the next best action, the correlated information and the stored pre-determined rules and, analyzing the next best action and the correlated information using the pre-determined rules for identifying whether the user needs to communicate with any other instance of said or any other application to perform the next best action and for generating a resultant data; receiving the resultant data and transforming the received resultant data into a format desired by a particular application whose instance needs to be communicated with; and
• displaying an integrated view of the transformed resultant data including different applications and their instances and the relation between said applications and said application instances.
11. The method as claimed in claim 10, wherein the method includes a step of accepting user selected application that needs communication based on users current needs for identifying a communication demand.
12. The method as claimed in claim 10, wherein the method includes a step of facilitating the data communication between at least two instances of the displayed applications based on the identified communication demand.
13. The method as claimed in claim 10, wherein the method includes a step of integrating said communication between at least two instances of the applications.
14. The method as claimed in claim 10, wherein the method includes a step of displaying the integrated view of said communication.
15. The method as claimed in claim 10, wherein the method includes a step of editing the application history by editing the user interactions and application instances and including recent user interactions and recent application instances.
16. A method as claimed in claim 10, wherein said method further includes a step of deciding whether a user has communicated with similar application for a particular context of the instance.
17. A method as claimed in claim 10, wherein said method further includes a step of identifying the application most relevant to a sensed context and highlighting said most relevant application.
18. A method as claimed in claim 10, wherein said method further includes a step of representing and displaying the interaction between the user and said instances of applications in the form of an event. ,TagSPECI:FIELD OF THE DISCLOSURE
The present disclosure relates to the field of computing systems. Particularly, the present disclosure relates to providing collaboration between multiple applications being executed in an enterprise system/information system.
BACKGROUND
In a typical enterprise systems/information systems, multitude of applications are executed at any given point of time, and the activities performed using such systems require a user to access multiple applications either simultaneously or sequentially, in order to accomplish a given task. The necessity to access or switch between multiple applications, compels the user to navigate across multiple application views/screens and perform multiple clicks/key-hits. Further, the result obtained as a consequence of such multiple key-hits/mouse-clicks, typically encompasses a plurality of data items/entities, some of which may not be of any significance to the user.
Further, the user is forced to invest a lot of his/her time navigating through various application views/windows while accomplishing a given task since accomplishing the task involves accessing multiple applications displayed across a multitude of windows. Moreover, multiple windows accessed by the user constitute to plurality of data items/elements, and some of the data items/elements may not be of particular importance to the user at that point of time and for the task he is handling at that moment. Therefore, the onus of differentiating between relevant and irrelevant data items and filtering the irrelevant data items rests on the user.
Further, given the fact that multiple applications are executed in an enterprise environment, the user is compelled to make data entries across multiple application windows, and making such entries not only consumes precious time but also results in duplication of work. Moreover, applications under parallel execution are unaware of the events executed across other parallel applications, as there is no opportunity available for the applications to inter-communicate. Applications can only inter-communicate when an inter process communication channel has been explicitly developed & established between them. Also, parallel execution of multiple applications entails functional duplication thereby driving up the cost associated with bundling/integrating enterprise applications.
International patents WO2009055490 and WO2009055492 disclose a model- based composite application platform that enables communication between distributed applications and services. The integration is made possible by building and deploying the applications on the platform that needs to be additionally developed on top of the existing applications. This additional deployment of computational resources increases the effective cost and affects the efficiency of the system.
Similar to the previous patents, the US patent US20080120628 discloses a user interface collaboration system that enables collaboration of plurality of applications by including a server that is coupled to the applications. The method disclosed by the patent consists of a first application interface that reports an event to be communicated to the server, the server in turn forwards this event to the second application to which the server is coupled. This method involves design and application changes and hence time to market. Also, a major disadvantage of this system is that all the applications are tightly coupled, so any change in an application will affect all the involved applications. The system also includes an additional server component for communication between the applications.
Corresponding to US20080120628, another US patent US6334158 that provides user-interactive system and method for integrating applications involves a data server acting as a central hub. The data server receives and sends data objects across the applications. The applications that can use this system need to have additional logic programmed to send and receive messages to/from the data server. Thus, core application logic needs to be altered in order to integrate the applications.
Another European patent EPO853277A2 discloses a modular application collaborator that includes connectors for communication between applications and an interchange server. This system involves additional external resources and requires changes in existing applications to enable the interaction between applications.
Therefore, in view of the aforementioned patents and their drawbacks, there is felt a need for a system that:
• is context-sensitive;
• seamlessly integrates multiple applications at the user’s end (user interface level) thereby reducing the costs associated with application integration;
• seamlessly integrates not only with windows based applications but also supports containers including browsers and various programming applications;
• specifically highlights applications of interest to a user, based on the context with which the user interacts with the applications;
• presents a consolidated (integrated) view of multiple relevant applications under execution, without necessitating the deployment of additional computational resources;
• provides single data entry to the applications of interest by automatically transferring the data within related applications;
• provides context sensitive communication/data transfer between multiple applications; and
• dynamically generates user interface from data across various applications.
OBJECTS
Some of the objects of the present disclosure are described herein below:
An object of the present disclosure is to provide a context sensitive system for integrating multiple applications.
Another object of the present disclosure is to provide a system that seamlessly integrates multiple applications at the user’s end (user interface level).
Yet another object of the present disclosure is to provide a system that seamlessly integrates with windows based applications and also supports containers including browsers and different programming applications.
Still a further object of the present disclosure is to provide a system that specifically highlights applications of interest to a user, based on the context with which the user interacts with the applications.
One more object of the present disclosure is to make available a system that provides a single point of entry for all the data elements purported to be used for various applications.
Yet another object of the present disclosure is to provide a system that presents a consolidated (integrated) view of multiple relevant applications under execution, without necessitating the deployment of additional computational resources.
One more object of the present disclosure is to provide a system that systematically performs operations on the data to be fed to multiple applications, in the background.
Yet another object of the present disclosure is to make available a system that provides for context sensitive communication/data transfer between multiple applications.
One more object of the present disclosure is to provide a system that does not necessitate major modifications at the application level.
Still a further object of the present disclosure is to provide a system that includes ready to deploy components, thereby ensuring that there are no delays in application deployment.
Yet another object of the present disclosure is to provide a system that allows customization for a particular integration based on the application platforms.
One more object of the present disclosure is to provide a system that updates the applications automatically, thus eliminating the reinstallation process.
Still further object of the present disclosure is to provide a system that dynamically generates user interface from data across various applications.
It is an object of the present disclosure to ameliorate one or more problems of the prior art, or, to at least provide a useful alternative.
Other objects and advantages of the present disclosure will be more apparent from the following description when read in conjunction with the accompanying figures, which are not intended to limit the scope of the present disclosure.
SUMMARY
The present disclosure envisages a computer implemented system and method for seamlessly integrating a plurality of applications.
In accordance with one aspect of the present disclosure, the system for seamlessly integrating a plurality of applications that are executable on an enterprise system comprises a user action tracker cooperating with the enterprise system. The user action tracker is configured to track interactions of a user with at least one instance of an application being used. The system includes a first extractor adapted to extract the tracked interactions from the user action tracker and an interaction repository adapted to receive the extracted tracked interactions from the first extractor and store the tracked interactions. An application tracker present in the system cooperates with the enterprise system. This application tracker is configured to track at least one instance of application resident in at least one node of the enterprise system. The system also includes a second extractor adapted to extract the tracked instance of the application from the application tracker and an application repository adapted to receive the extracted tracked instance of the application from the second extractor and store the tracked instance of the application. The system also includes an event log module configured to track a plurality of events related to the application, a location tracker adapted to track location of at least one of user and events and a timer adapted to track timing information related to the events. The system further includes a third extractor adapted to extract the tracked events from the event log module, the tracked location from the location tracker and the tracked timing information from the timer and a temporary repository adapted to receive the extracted tracked events, tracked location and tracked timing information from the third extractor, and, store the received tracked events, tracked location and tracked timing information. A transceiver present in the system is adapted to receive the tracked interactions from the interaction repository, tracked instance of the application from the application repository, and, tracked events, tracked location and tracked timing information from the temporary repository and transmit the received tracked interactions, tracked instance, tracked events, tracked location and tracked timing information. The system comprises a data repository adapted to store application history based on the user interactions and the application instances of the user interactions between the user and the application, the data repository further having storage registers to store pre-determined rules for the user interactions. The system also includes a context aware processing engine cooperating with the transceiver and the data repository, the context aware processing engine comprises:
i. a correlator module configured to correlate the tracked interactions, tracked instance, tracked events, tracked location and tracked timing information received from the transceiver with the stored application history and the stored pre-determined rules from the data repository to obtain correlated information;
ii. an analytical engine cooperating with the correlator, the analytical engine having a determinator that receives and analyses the correlated information to determine the next best action to be carried out by the user and transmit information related to the next best action;
iii. a workflow module adapted to receive the correlated information from the correlator, the next best action information from the analytical engine and the stored pre-determined rules from the data repository, the workflow module comprising an identifier configured to analyze the correlated information and the next best action information using stored pre-determined rules to identify whether the user needs to communicate with any other instance of the or any other application to perform the next best action and generate a resultant data.
The system of the present disclosure also includes a transformation engine configured to receive the resultant data from the workflow module and transform the resultant data into a format desired by a particular application whose instance needs to be communicated with. The system further includes a user interface cooperating with the transformation engine, the user interface adapted to display an integrated view of the transformed resultant data including different applications and their application instances and the relation between the applications and the application instances.
In accordance with another aspect of the present disclosure, there is provided a method for seamlessly integrating a plurality of applications executable on an enterprise system, the computer implemented method includes the steps of:
• tracking interactions of a user with at least one instance of an application being used;
• extracting the tracked interactions;
• storing the extracted tracked interactions;
• tracking at least one instance of application in at least one node of the enterprise system;
• extracting the tracked instance of the application;
• storing the extracted tracked instance of the application;
• tracking a plurality of events related to the application;
• tracking location of at least one of user and events;
• tracking timing information related to the events;
• extracting tracked events, tracked location and tracked timing information;
• storing the extracted tracked events, tracked location and tracked timing information;
• receiving the tracked interactions, tracked instance of the application, tracked events, tracked location and tracked timing information;
• transmitting the received tracked interactions, tracked instance of the application, tracked events, tracked location and tracked timing information;
• storing application history based on the user interactions and the application instances of the user interactions between the user and the applications and storing pre-determined rules for the user interactions;
• receiving the tracked interactions, tracked instance of the application, tracked events, tracked location, tracked timing information and the application history and correlating the received information to obtain correlated information;
• receiving the correlated information and analyzing the correlated information to determine the next best action to be carried out by the user;
• transmitting information related to the next best action;
• receiving the next best action, the correlated information and the stored pre-determined rules and, analyzing the next best action and the correlated information using the pre-determined rules for identifying whether the user needs to communicate with any other instance of the or any other application to perform the next best action and for generating a resultant data; receiving the resultant data and transforming the received resultant data into a format desired by a particular application whose instance needs to be communicated with; and
• displaying an integrated view of the transformed resultant data including different applications and their instances and the relation between the applications and the application instances.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS
The computer implemented system and method for seamlessly integrating a plurality of applications will now be described with reference to the non-limiting, accompanying drawings, in which:
FIGURE 1 illustrates a block-diagram of the system for seamlessly integrating a plurality of applications, in accordance with the present disclosure.
FIGURE 2 is a flow chart illustrating the steps involved in the method for seamlessly integrating a plurality of applications, in accordance with the present disclosure.
FIGURE 3 is a flow chart illustrating an embodiment of present disclosure with an example of data entry process between two applications.
DETAILED DESCRIPTION
The computer implemented system and method for seamlessly integrating multiple applications will now be described with reference to the accompanying drawings which do not limit the scope and ambit of the disclosure. The description provided is purely by way of example and illustration.
Referring to the accompanying drawings, FIGURE 1 shows a schematic of the computer implemented system 100 for seamlessly integrating multiple applications within an enterprise system.
In accordance with one aspect of the present disclosure, the system 100 comprises of a user action tracker 102 that is configured to track every user activity/interaction related to the user interface of various applications. The user action tracker 102 audits the user’s current actions against numerous applications that are being used by the user and provides the list of user accessed applications at that specific time to an application tracker 104. A first extractor 138 extracts the interactions tracked by the user action tracker 102 which are then stored in an interaction repository 140.
The application tracker 104 is configured to track instances of applications resident in at least one node of the enterprise system. A second extractor 142 extracts these tracked instances which are then stored in an application repository 144. These instances benefit in determining the application responses. An event log module 132 is configured to track the events occurring related to an application. A location tracker 134 and a timer 136 are additional components that can be used as triggering components. For example, if an application in use is providing transport related information to a user, and an event is taking place en route user’s travel, the system will track the event related information and provide user with list of possible traffic congestions along with the location and timing information. A third extractor 146 extracts the tracked events from the event log module 132, the tracked location from the location tracker 134 and the tracked timing information from the timer 136. This extracted data is stored in a temporary repository 148. The tracked interactions from the interaction repository 140, tracked instance of the application from the application repository 144, and, tracked events, tracked location and tracked timing information from the temporary repository 148 are received by a transceiver 106.
The system 100 further includes a data repository 108 that is configured to store the history of all previously accessed applications. The data repository 108 stores application history based on the user interactions and the application instances of the user interactions between the user and the application. The data repository 180 further includes storage registers to store pre-determined rules for the user interactions. The information received by the transceiver 106 and the information present in the data repository 108 is then correlated by a correlator 112. The correlator 112 correlates the tracked interactions, tracked instance, tracked events, tracked location and tracked timing information received from the transceiver 106 with the stored application history and the stored pre-determined rules from the data repository 108 to obtain correlated information. An analytical engine 114 cooperates with the correlator 112 and includes a determinator that receives and analyses the correlated information to determine the next best action to be carried out by the user and transmit information related to the next best action. The system 100 includes a workflow module 116 that receives the correlated information from the correlator 112, the next best action information from the analytical engine 114 and the stored pre-determined rules from the data repository 108. The workflow module 116 comprises an identifier configured to analyze the correlated information and the next best action information using stored pre-determined rules to identify whether the user needs to communicate with any other instance of said or any other application to perform the next best action and generate a resultant data.
Various applications have numerous instances that need communication between each other, such instances need manipulation based on the desired format of different applications. The resultant data from the workflow module 116 that is present in a context aware processing engine 110 is fed to a transformation engine 118 that is responsible for the transformation of the resultant data depending on the desired format of paticular applications. The system 100 further includes a user interface 120 that is configured to display an integrated view of the transformed data including different application and the relation between their instances based on user actions. A user input mechanism 122 enables user to select the applications that need communication at that particular time. Based on user’s input, application communication demand is established which is then recognized by an application communicator 124 that is responsible for data exchange between application(s). The application communicator 124 further facilitates the data communication between at least two instances of the applications.
In accordance with the present disclosure, the system further includes an integrator 126 configured to process the resultant data of the communication between the instances of the applications and integrate the resultant to generate an integrated view encompassing the resultants. The integrated view of the resultant of said data communication is further displayed on a configured display 128. The system also includes an editor 130 configured to modify the data repository 108 based on the integrated communication. The editor 130 further edits the application history by editing the user interactions and the applications instances to include recent user interactions and recent application instances.
The system further comprises of a configuration setup component that is configured to monitor all enterprise level setup clients that communicate with each other.
In accordance with the present disclosure, the context aware processing engine 110 further comprises an application identifier configured to identify the application most relevant to a sensed context, said application identifier further configured to highlight said most relevant application.
In accordance with the present disclosure, the user interface 120 further comprises an event generator configured to represent the interaction between the user and said instances of applications, in the form of an event, said event generator further configured to display said events.
The method of seamlessly integrating plurality of applications further includes the step of processing the published events, generating corresponding notifications and transmitting said notifications to other appropriate instance(s) of the application(s).
In one of the embodiment of the present disclosure, the system includes an additional module for invoking a user interface at the backend of an application that lacks a user interface.
The system of the present disclosure also provides authorized users, access to various applications and information available from those application based on permissions. The system also accepts queries/inputs from the users and provides/updates the available information.
In accordance with another aspect of the present disclosure, there is provided a method for seamlessly integrating a plurality of applications executable on an enterprise system. Referring to FIGURE 1 and FIGURE 2 the method for seamlessly integrating a plurality of applications executable on an enterprise system 100 involves the step of tracking 200 with the help of a user action tracker 102. An application tracker 104 performs the step of tracking 202 the relevant instances within the application(s). A transceiver 106 receives the inputs tracked by user action tracker 102 and/or the application tracker 104 along with the information related to events tracked by an event log module 132, location tracked by location tracker 134 and timer information received from a timer 136 to sense the underlying context 204. A correlator 112, an analytical engine 114 and a workflow module 116 carry out the step of comparison and identification to identify the next best action that should be carried out when an instance of the application needs to communicate with any other instance 206 based on the tracked information from the transceiver 106 and application history from data repository 108. Based on the need for communication and the determined next best action, the context of the application is manipulated 208 with respect to the relevant context by a workflow module 116. The data obtained is then transformed into a format 210 suitable to the desired application by the transformation engine 118. The transformed data is then displayed 212 with the help of a user interface 120. The step of facilitating communication between two applications and protocol conversion 214 is then carried out by application communicator 124 depending on the users input from user input mechanism 122. The resultant of data communication between the instances of application(s) is then processed and integrated 216 by integrator 126 and displayed 218 using a display 128. The step of displaying also involves navigation of applications automatically/systematically 218. The data repository 108 is further modified/edited 220 based on the resultant with the help of an editor 130.
FIGURE 3 illustrates a sample flow chart of one of the embodiments of the system in the present disclosure designated by the abbreviation TCAP. TCAP is a composite desktop application that allows seamless integration of plurality of applications. The flowchart explains a process in which two application viz. application A and application B communicate with each other to automatically alter and populate the data in application A depending on the data from application B, thus, saving the time and effort needed by user to carry out the same task. Figure 3 is an illustration wherein only two applications A and B are considered, but typically, TCAP can integrate with one or more applications. The steps included in the considered embodiment are as follows:
• the user has to login into application B 300;
• on successful login TCAP navigates the user and asks to login into application A 302;
• once logged in, TCAP automatically navigates the user to information of user’s interest in application A (e.g. - Case_List_Page) 304;
• user has to select the desired information (from Case_List_Page) on which activity has to be performed and click on Button_One 306;
• TCAP automatically navigates the user to the desired page on application B (e.g. – Case_Details_Page) 308;
• user interface of the desired page on application B is automatically modified to include user interface elements similar to that on application A’s page (e.g. - Status_Page from application B modified to have the same elements like Workflow_Page from application A) 310;
• the user then selects and saves in application B the desired values for the user interface elements to be filled in application A 312;
• TCAP automatically navigates to the desired page of application A and automatically populates the data from application B 314; and
• saves the data populated in application A and return to application B 316.
TECHNICAL ADVANTAGES
The technical advantages envisaged by the present disclosure include the realization of a context sensitive system and method for seamlessly integrating a plurality of applications executed on an enterprise system.
The present disclosure provides for a context sensitive system that seamlessly integrates multiple applications at the user’s end (user interface level).
The system of the present disclosure provides for context sensitive data communication/transfer between the applications under execution. The system senses the context in which a user interacts with a particular application or a plurality of applications and further highlights the applications that could be of interest to the user, based on the sensed context.
The system of the present disclosure provides for a single point of entry to all the data elements purported to be used for various applications under execution.
The system envisaged by the present disclosure does not necessitate deployment of additional computational resources and makes efficient use of the available computational infrastructure to provide a consolidated view of multiple relevant applications under execution.
The system performs the task of data manipulation in the background, and provides for efficient and effective data manipulation and transformation.
The system envisaged by the present disclosure does not necessitate major modifications at the application level.
The system provides ready to use components that could be deployed as applications within a short span of time, thereby providing for minimized delays in application deployment.
The system dynamically generates user interface from data across various applications.
The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
| # | Name | Date |
|---|---|---|
| 1 | 2741-MUM-2014-CORRESPONDENCE-(21-03-2016).pdf | 2016-03-21 |
| 1 | 2741-MUM-2014-RELEVANT DOCUMENTS [30-09-2023(online)].pdf | 2023-09-30 |
| 2 | 2741-MUM-2014-IntimationOfGrant30-11-2022.pdf | 2022-11-30 |
| 2 | TCS2013006_Drawing_Final.pdf | 2018-08-11 |
| 3 | TCS2013006_CS_Final.pdf | 2018-08-11 |
| 3 | 2741-MUM-2014-PatentCertificate30-11-2022.pdf | 2022-11-30 |
| 4 | FORM 3.pdf | 2018-08-11 |
| 4 | 2741-MUM-2014-Written submissions and relevant documents [21-10-2022(online)].pdf | 2022-10-21 |
| 5 | 2741-MUM-2014-Power of Attorney-091214.pdf | 2018-08-11 |
| 5 | 2741-MUM-2014-Correspondence to notify the Controller [04-10-2022(online)].pdf | 2022-10-04 |
| 6 | 2741-MUM-2014-US(14)-HearingNotice-(HearingDate-06-10-2022).pdf | 2022-09-16 |
| 6 | 2741-MUM-2014-FORM 18.pdf | 2018-08-11 |
| 7 | 2741-MUM-2014-FORM 1(25-9-2014).pdf | 2018-08-11 |
| 7 | 2741-MUM-2014-CLAIMS [09-04-2020(online)].pdf | 2020-04-09 |
| 8 | 2741-MUM-2014-FER_SER_REPLY [09-04-2020(online)].pdf | 2020-04-09 |
| 8 | 2741-MUM-2014-Correspondence-091214.pdf | 2018-08-11 |
| 9 | 2741-MUM-2014-CORRESPONDENCE(25-9-2014).pdf | 2018-08-11 |
| 9 | 2741-MUM-2014-OTHERS [09-04-2020(online)].pdf | 2020-04-09 |
| 10 | 2741-MUM-2014-FER.pdf | 2019-11-27 |
| 11 | 2741-MUM-2014-CORRESPONDENCE(25-9-2014).pdf | 2018-08-11 |
| 11 | 2741-MUM-2014-OTHERS [09-04-2020(online)].pdf | 2020-04-09 |
| 12 | 2741-MUM-2014-Correspondence-091214.pdf | 2018-08-11 |
| 12 | 2741-MUM-2014-FER_SER_REPLY [09-04-2020(online)].pdf | 2020-04-09 |
| 13 | 2741-MUM-2014-CLAIMS [09-04-2020(online)].pdf | 2020-04-09 |
| 13 | 2741-MUM-2014-FORM 1(25-9-2014).pdf | 2018-08-11 |
| 14 | 2741-MUM-2014-FORM 18.pdf | 2018-08-11 |
| 14 | 2741-MUM-2014-US(14)-HearingNotice-(HearingDate-06-10-2022).pdf | 2022-09-16 |
| 15 | 2741-MUM-2014-Correspondence to notify the Controller [04-10-2022(online)].pdf | 2022-10-04 |
| 15 | 2741-MUM-2014-Power of Attorney-091214.pdf | 2018-08-11 |
| 16 | 2741-MUM-2014-Written submissions and relevant documents [21-10-2022(online)].pdf | 2022-10-21 |
| 16 | FORM 3.pdf | 2018-08-11 |
| 17 | 2741-MUM-2014-PatentCertificate30-11-2022.pdf | 2022-11-30 |
| 17 | TCS2013006_CS_Final.pdf | 2018-08-11 |
| 18 | 2741-MUM-2014-IntimationOfGrant30-11-2022.pdf | 2022-11-30 |
| 18 | TCS2013006_Drawing_Final.pdf | 2018-08-11 |
| 19 | 2741-MUM-2014-RELEVANT DOCUMENTS [30-09-2023(online)].pdf | 2023-09-30 |
| 19 | 2741-MUM-2014-CORRESPONDENCE-(21-03-2016).pdf | 2016-03-21 |
| 1 | SearchStrategy2AE_12-08-2020.pdf |
| 1 | SearchStrategy_08-11-2019.pdf |
| 2 | SearchStrategy2AE_12-08-2020.pdf |
| 2 | SearchStrategy_08-11-2019.pdf |