Claims:CLAIMS
What is claimed is:
1) A method for interacting with an application bundle, said method comprising:
generating said application bundle, by a User Equipment (UE), wherein said application bundle comprises of current state information pertaining to at least one application;
providing at least one interface for a user of said UE to access said application bundle, by said UE; and
triggering at least one action corresponding to said state of said at least one application in said application bundle, by said UE.
2) The method as claimed in claim 1, wherein said application bundle for said at least one application is generated by said UE, upon receiving an input from said user.
3) The method as claimed in claim 1, wherein said application bundle for said at least one application is automatically generated by said UE, by capturing said state of said at least one application, at set time intervals.
4) The method as claimed in claim 1, wherein generating said application bundle for a single application further comprises of:
receiving a user command to generate said application bundle, when said application is open on said UE, by said UE, wherein said user command is pre-configured;
saving state of said application at the instance said command is received, by said UE; and
generating said application bundle using said saved state of said application, by said UE.
5) The method as claimed in claim 1, wherein generating said application bundle for a plurality of applications further comprises of:
receiving a user command to generate said application bundle, when said plurality of applications are open on said UE, by said UE;
saving state of said plurality of applications at the instance said command is received, by said UE; and
generating said application bundle using said saved state of said plurality of applications, by said UE.
6) The method as claimed in claim 1, wherein said at least one action corresponding to said state of said at least one application in said application bundle is pre-configured with said UE.
7) A system for interacting with an application bundle, said system configured for:
generating said application bundle, by a User Equipment (UE), wherein said application bundle comprises of current state information pertaining to at least one application;
providing at least one interface for a user of said UE to access said application bundle, by said UE; and
triggering at least one action corresponding to said state of said at least one application in said application bundle, by said UE.
8) The system as claimed in claim 7, wherein said UE is configured to generate said application bundle for said at least one application, upon receiving an input from said user.
9) The system as claimed in claim 7, wherein said UE is configured to automatically generate said application bundle for said at least one application, by capturing said state of said at least one application, at set time intervals.
10) The system as claimed in claim 7, wherein said UE is configured to generate said application bundle for a single application by:
receiving a user command to generate said application bundle, when said application is open on said UE, wherein said user command is pre-configured;
saving state of said application at the instance said command is received; and
generating said application bundle using said saved state of said application.
11) The system as claimed in claim 7, wherein said UE is configured to generate said application bundle for a plurality of applications by:
receiving a user command to generate said application bundle, when said plurality of applications are open on said UE;
saving state of said plurality of applications at the instance said command is received; and
generating said application bundle using said saved state of said plurality of applications.
12) The system as claimed in claim 7, wherein said system is configured to pre-configure information pertaining to said at least one action corresponding to said state of said at least one application in said application bundle, with said UE.

Dated this 4th January 2016


Description:TECHNICAL FIELD
[001] The embodiments herein relate to digital equipments and, more particularly, to allow interaction with application bundles in digital equipments.

BACKGROUND
[002] With the advancement in technology, the world is getting digitalized. This stands true in different aspects of our day to day life such as communication, entertainment, data storage, and so on. For example, mobile phones have become very common nowadays, and they support and facilitate communication across the globe. Similarly, devices such as but not limited to PDAs and tablet PCs are used for data storage, communication, and various other applications.
[003] In order to improve user experience, almost all such devices support multitasking. Multitasking allows simultaneous operation of more than one application in the device. This may involve combination of background and foreground operation of applications. For example, in a smartphone, while a call is in progress in the foreground, GPS based location tracking may be running in the background, thereby ensuring continued location tracking services even when the user is operating other applications.
[004] However, a disadvantage with the current systems/devices that support multitasking is that they do not support different operations to be performed on the same application. For example, assume that a user of a smartphone was editing a contact in the smartphone’s contact list. While the editing is in progress, if the user tries to open and edit a different contact in the contact list, the action is not supported by the smartphone. This means that multitasking within same application is not supported by the existing systems/methods and devices.

OBJECT OF INVENTION
[005] An object of the embodiments herein is to save different states/instances of same application as different application bundles.
[006] Another object of the embodiments herein is to create an application bundle comprising instances of different applications.
[007] Another object of the embodiments herein is to trigger at least an action based on contexts of application(s) that constitutes an application bundle.
[008] Another object of the embodiments herein is to allow different operations simultaneously on the same application, using application bundles.
[009] Another object of the embodiments herein is to allow different instances of the same application to be active at the same time.
SUMMARY
[0010] In view of the foregoing, an embodiment herein provides a method for interacting with an application bundle. A UE generates the application bundle, wherein the application bundle comprises of current state information pertaining to at least one application. The UE provides at least an interface for a user of the UE to access the application bundle, and triggers at least one action corresponding to the state of the at least one application in the application bundle.
[0011] Embodiments further disclose a system for interacting with an application bundle. The system is configured generating the application bundle, by a User Equipment (UE), wherein the application bundle comprises of current state information pertaining to at least one application. The UE provides at least one interface for a user of the UE to access the application bundle, and then triggers at least one action corresponding to the state of the at least one application in the application bundle.
[0012] These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings.

BRIEF DESCRIPTION OF THE FIGURES
[0013] The embodiments herein will be better understood from the following detailed description with reference to the drawings, in which:
[0014] FIG. 1 illustrates a block diagram of the User Equipment (UE) that supports interaction with application bundles, as disclosed in the embodiments herein;
[0015] FIG. 2 is a flow diagram that depicts steps involved in the process of interaction with an application bundle using the UE, as disclosed in the embodiments herein;
[0016] FIG. 3 is a flow diagram that depicts steps involved in the process of generating an application bundle by the UE, as disclosed in the embodiments herein;
[0017] FIGS. 4a-4c depict examples of application bundles, as disclosed in the embodiments herein;
[0018] FIG. 5 depicts an example of accessing application bundles using a wearable gadget, as disclosed in the embodiments herein;
[0019] FIG. 6 depicts an example of creating and managing email bundles, as disclosed in the embodiments herein;
[0020] FIG. 7 depicts an example of creating video bundles for a video, as disclosed in the embodiments herein;
[0021] FIG. 8 depicts an example an application bundle of web view, as disclosed in the embodiments herein;
[0022] FIGS. 9a, 9b and 9c depict example of different types of views of an application bundle, as disclosed in the embodiments herein;
[0023] FIG. 10 depicts an example of display and access of an application bundle using task manager, as disclosed in the embodiments herein; and
[0024] FIG. 11 depicts an example of display and access of an application bundle using an edge display, as disclosed in the embodiments herein.

DETAILED DESCRIPTION OF EMBODIMENTS
[0025] The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0026] The embodiments herein disclose a mechanism for generation and interaction with application bundles, as disclosed in the embodiments herein. Referring now to the drawings, and more particularly to FIGS. 1 through 11, where similar reference characters denote corresponding features consistently throughout the figures, there are shown embodiments.
[0027] FIG. 1 illustrates a block diagram of the User Equipment (UE) that supports interaction with application bundles, as disclosed in the embodiments herein. The UE 100 comprises of an Input/Output (I/O) interface 101, a state capturing module 102, a bundle generator 103, a memory module 104, and a response triggering module 105.
[0028] The UE 100 can be any device that supports installation and use of software applications for same or different purposes. For example, the UE 100 can be a smartphone, a tablet PC, a laptop, or any such device. The UE 100 can be configured to provide means for saving state/instances of applications as application bundles. In various embodiments, an application bundle can comprise of state of one or more applications. The UE 100 can be further configured to identify at least one action that matches the state of the application(s) present in the application bundle. The UE 101 can be further configured to allow a user to access the application bundle, using a suitable user interface. The UE 100 can be further configured to trigger the action that matches the state of the application(s), upon receiving an input.
[0029] The I/O interface 101 can be configured to provide suitable options and related user interfaces for a user to interact with the UE 100, so as to configure, change, and/or manage settings associated with the application bundle generation, interaction, and any such related functionality. The state capturing module 102 can be configured to monitor in real time, state of all applications that are open on the UE 100. The state capturing module 102 can be further configured to capture/record the state of the application(s) being monitored, upon receiving a command from the user. The state capturing module 102 can be further configured to provide the captured data as input to the bundle generator 103, through a suitable interface.
[0030] The bundle generator 103 can be configured to collect the state information from the state capturing module 102 as input, and then process the collected data further, to generate the corresponding application bundle. In various embodiments, the bundle generator 103 generates the application bundle, using state information of one or more application. The bundle generator 103 can be further configured to save the generated application bundle(s) in the memory module 104.
[0031] The memory module 104 can be configured to store any data that is associated with the bundle generation, management, and action triggering processes. In various embodiments, the memory module 104 can be configured to store data permanently and/or temporarily, based on the type of data as well as the user inputs. For example, the memory module 104 stores data pertaining to action(s) to be triggered, corresponding to different states of a single application, or for a combination of states of at least two applications, wherein this information is pre-configured. The memory module 104 can be further configured to store the application bundles generated by the bundle generator 103. The memory module 104 can be further configured to erase selected type of data automatically by detecting a trigger, wherein the trigger can be a time based, event based, and/or any of such pre-defined type. The memory module 104 can be further configured to erase selected type of data, based on manual inputs provided by a user.
[0032] The response triggering module 105 can be configured to access the application bundle and identify the application(s), and the state of application(s), that are stored in the bundle. The response triggering module 105, for the identified state of application or combination of applications, and for the corresponding state information, selects at least one action to be triggered, based on the data stored in the memory module 105. The response triggering module 105 further executes the identified action.
[0033] In various embodiments, the application bundle stored in the memory module 104 can have pre-defined life term or can be deleted based on an input received from the user. The UE 100 can be configured to allow a user to define certain triggers which can result in the corresponding application bundle getting deleted. For example, the trigger can be time based such that the application bundle gets deleted after a pre-defined time period. In another example, the application bundle can get deleted, once it gets used by any/a specific application for a particular number of times, as pre-configured.
[0034] FIG. 2 is a flow diagram that depicts steps involved in the process of interaction with an application bundle using the UE, as disclosed in the embodiments herein. The UE 100 generates (202) at least one application bundle, based on the application(s) that is open at the instance the instruction to generate the application bundle is received. In various embodiments, the instruction to generate the application bundle can be at least one of or a combination of a user command of a pre-defined type, and/or an event (for example, closure of at least an application in a manner that is pre-defined manner).
[0035] Once the application bundle is generated, the same is displayed to the user, using a suitable interface. Further, user access is permitted (204) to the application bundle, by providing suitable interfaces, and the user is permitted to perform selected actions on the application bundles. For example, the user can drag and drop (as depicted in Fig. 4c) an application to an application bundle to trigger a particular action. All such user actions and the corresponding actions that will be triggered by the UE 100 are pre-defined and pre-configured. The action(s) corresponding to the state of application(s) in the application bundle being considered, is identified (206) by the UE 100. In another embodiment, the user access using a wearable gadget can also be permitted (as depicted in Fig. 5), by providing display and control options that in turn facilitates access and use of application bundles using different types of wearable devices. The display and access interfaces for different wearable gadgets can be configured and customized, as per requirements. The UE 100 can be configured to collect inputs pertaining to display and/or control of the application bundles, from at least one of the connected wearable devices, determine/identify the action to be triggered corresponding to the input(s) received from the wearable gadget, and trigger/execute the identified action.
[0036] Further, upon identifying at least one of the aforementioned actions or any other type of trigger, the UE 100 executes (208) the identified action(s). The various actions in method 200 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 2 may be omitted.
[0037] FIG. 3 is a flow diagram that depicts steps involved in the process of generating an application bundle by the UE, as disclosed in the embodiments herein. The state capturing module 102 in the UE 100 monitors (302) on a real-time basis, state of applications that are open in the UE 100. The state capturing module 102 checks at specific time intervals and/or real-time, for a trigger to generate the application bundle. Upon identifying/detecting at least one trigger of a pre-configured type, the state capturing module 102 saves (306) status of all applications that are being monitored at the instance the user command is received. Further, the saved statuses of the application(s) are grouped and saved (308) to generate the application bundle (as depicted in Figs. 4a and 4b). The example depicted in Fig. 4a shows an application bundle A1 being generated by saving the marked statuses of application A, and an application bundle B1 being generated by saving the marked statuses of application B.
[0038] The various actions in method 300 may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions listed in FIG. 3 may be omitted.
[0039] FIG. 6 depicts an example of creating and managing email bundles, as disclosed in the embodiments herein. As depicted, the email bundle ‘E’ comprises of contacts, attachments, and text. While the user accesses the bundle ‘E’, the UE 100 provides options i.e. actions that can be triggered corresponding to each component of the bundle. For example, the UE 100, using a suitable interface, may display the contact list and prompt the user to add the contact in the email bundle, to the contact list. Similarly, the UE 100 can prompt the user to save the attachments, or automatically invoke application(s) that can be used to view the attachments. The UE 100 can be further configured to provide options for copying the text that is present in the bundle.
[0040] FIG. 7 depicts an example of creating video bundles for a video, as disclosed in the embodiments herein. As depicted, video bundle 1 is created for a particular instance (i.e. time 00:22:12) of Video 1, and video bundle 2 is created for a particular instance (i.e. time 1:17:26) of Video 2. Further, when the user accesses any of the bundles (in this example, bundle 2), content of the bundle is displayed to the user, by invoking suitable application. Further, while content of one video bundle is being watched, the same can be paused and then resumed later.
[0041] Similarly, different bundles can be created for different instances of the same video, such that viewing of the same video can be resumed from different points, as saved in the corresponding video bundles. In an embodiment, the bundle(s) and contents of the bundle being accessed are displayed simultaneously on the screen, using different windows positioned side by side i.e. a dual display mode. In another embodiment, when the user accesses a particular bundle, the content of the bundle is displayed to the user in a window in the foreground, while the bundle is displayed in a different screen that gets pushed to the background while the contents are being displayed to the user. Similarly,
[0042] FIG. 8 depicts an example an application bundle of web view, as disclosed in the embodiments herein. The UE 100 allows bundles to be created for a web-view of a particular webpage being viewed/open at that instance, wherein at least one context of the webpage can also be saved as an area of interest, in the bundle. In an embodiment, the area of interest may be saved in any suitable format such as but not limited to a web clip.
[0043] FIGS. 9a, 9b and 9c depict examples of different types of views of an application bundle, as disclosed in the embodiments herein. Fig. 9a depicts display and access of an application bundle using a menu manager. In this example, the menu manager permits stack view of application bundles pertaining to different applications. Further, when the user selects a particular application bundle (Video bundle in this example), the contents of the video bundle are displayed to the user, using a suitable format. A task manager view of the application bundles is depicted in Fig. 9b. As depicted, the task manager displays the application bundles pertaining to different applications, in a suitable format, such that the user can open at least one of the application bundles. Further, when the user accesses a bundle, contents of the bundle are displayed to the user using suitable interface. Fig. 9c depicts the interface provided on a device with a secondary display i.e. an edge screen in this scenario. Suitable interfaces can be provided by the UE 100 such that the bundle can be accessed and all or certain actions can be performed on selected bundle(s), using interfaces on the edge screen as well as on the main screen.
[0044] The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module.
[0045] The embodiments disclosed herein specify a mechanism for generating and interacting with application bundles. The mechanism allows multi-tasking within an application with the help of application bundles, providing a system thereof. Therefore, it is understood that the scope of protection is extended to such a system and by extension, to a computer readable means having a message therein, said computer readable means containing a program code for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The method is implemented in a preferred embodiment using the system together with a software program written in, for ex. Very high speed integrated circuit Hardware Description Language (VHDL), another programming language, or implemented by one or more VHDL or several software modules being executed on at least one hardware device. The hardware device can be any kind of device which can be programmed including, for ex. any kind of a computer like a server or a personal computer, or the like, or any combination thereof, for ex. one processor and two FPGAs. The device may also include means which could be for ex. hardware means like an ASIC or a combination of hardware and software means, an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. Thus, the means are at least one hardware means or at least one hardware-cum-software means. The method embodiments described herein could be implemented in pure hardware or partly in hardware and partly in software. Alternatively, the embodiment may be implemented on different hardware devices, for ex. using a plurality of CPUs.
[0046] 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 claims as described herein.