Patent Description:
Generally, it is common for a user when using a primary application want to access data available in a secondary application. Typically, the user is required to manually activate the secondary application and navigate to the desired data. Further, the user then needs to close the secondary application to return to the primary application.

In systems and methods of the related art, consider a scenario where the user needs to access content in an application from another application context. In this case, the user needs to perform multiple operations manually such as navigating to other application and performing interactions such as copy-paste, drag, etc. which is inconvenient and time consuming for the user. Consider another scenario where the user needs to access or transfer the content within the same application. In this case, the user needs to transition across different screens manually involving multiple operations which are inconvenient and time consuming for the user.

<CIT> discloses a mapping application search function and a method for a mobile device connected to a vehicle's interactive communication system that includes a display screen. <CIT> discloses an address harvester that harvests addresses from one or more applications executing on a device. <CIT> discloses a navigation terminal for calculating a route or a route information server sets multiple proposed locations for an appointment according to various conditions or options provided by a user for the determination of an appropriate location for the appointment between multiple parties. <CIT> discloses a suggestive mapping device may predict, suggest, and/or provide potential destinations to a user.

Aspects of the present disclosure are to address at least the above-mentioned problems and/or disadvantages and to provide at least the advantages described below. Accordingly, an aspect of the present disclosure is to provide a system and method for automatically managing content in an electronic device.

Another aspect of the present disclosure is to provide a system and method for receiving, by a content management engine, an input indicating selection of content or a feature event in the electronic device.

Another aspect of the present disclosure is to provide a system and method for determining, by the content management engine, at least one of a current user context and a historic user context.

Another aspect of the present disclosure is to provide a system and method for causing, by the content management engine, to display at least one graphical element of at least one target data item for at least one of the current user context and the historic user context.

In accordance with an aspect of the present disclosure, a method for content management in an electronic device is provided. The method includes determining first attributes of a first content in a first application by analyzing the first content while the first application is active in the electronic device, receiving a query request for second attributes corresponding to a second content of a second application executed in an external device from the external device and transmitting, in response to the second attributes request query, target data information for generating at least one icon based on the first attributes and the second attributes to be displayed on the external device to the external device.

In accordance with another aspect of the present disclosure, an electronic device is provided. The electronic device includes a transceiver configured to communicate with an external device, and at least one processor configured to determine first attributes of a first content in a first application by analyzing the first content while the first application is active in the electronic device, to receive a query request for second attributes corresponding to a second event of a second application executed in the external device from the external device and to transmit, in response to the second attributes request query, data information for generating at least one icon to be displayed on the external device to the external device based on the first attributes and the second attributes.

In accordance with another aspect of the present disclosure, an electronic device is provided. The electronic device includes a memory, configured to store instructions, and at least one processor, that when executing the stored instructions, is configured to determine attributes of content in a first application by analyzing the content while the first application is active in the electronic device, receive a query request for attributes corresponding to an event of a second application executed in at least one external device from the at least one external device, and transmit, in response to the request query, target data information for generating at least one icon to be displayed on the at least one external device to the external device based on the attributes of content in the first application and the attributes corresponding to the event of the second application.

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the present disclosure as defined by the claims and their equivalents. Accordingly, those of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope of the claims.

Accordingly, it should be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustration purpose only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

The various 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 various embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the various embodiments herein can be practiced and to further enable those skilled in the art to practice the various embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the various embodiments herein.

The various embodiments herein disclose a method for automatically managing content in an electronic device. The method includes receiving an input indicating selection of the content or a feature event in an application in the electronic device. In an example, the feature event can be tapping an input area in a chat application. Further, the method includes determining at least one of a current user context and a historic user context. Further, the method includes causing to display at least one graphical element of at least one target data item for at least one of the current user and the historic user context.

Unlike systems and methods of the related art, the proposed method provides a mechanism for triggering an application specific query to determine stored application specific attributes in a memory of the electronic device from a particular application context. Further, the proposed method provides a mechanism for representing the application specific query results returned, using the at least one graphical elements for easy access from the application context. Further, the proposed method can be used to share the content between the electronic devices thus, allowing the user to easily access the content from any application context, including cross-applications or cross-device contents.

Unlike systems and methods of the related art, the proposed method provides a robust and simple mechanism for automatically managing the content. Further, the proposed method enables a user of the electronic device to easily access the relevant content from any application context, including cross-applications content or cross-device contents. Further, the proposed method provides the user with probable route suggestions based on chat conservation. Further, seamless retrieval of routes information from a memory of the electronic device.

Referring now to the drawings, and more particularly to <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.

<FIG> illustrates an example for automatically managing content in an electronic device according to an embodiment of the present disclosure.

Referring to <FIG>, in an embodiment, an electronic device <NUM> can be, for example, a laptop, a desktop computer, a mobile phone, a mobile terminal, a mobile station, a smart phone, personal digital assistants (PDAs), a tablet, a phablet, a consumer electronic device, dual display devices, or any other electronic device.

Initially, the electronic device <NUM> can be configured to analyze previous interaction history of a user with various applications available in the electronic device <NUM> and application data. Based on the interaction history and the application data, the electronic device <NUM> can be configured to extract (or determine) and store a relation between a data object and its intended target. Further, the electronic device <NUM> can be configured to use the pending relation stored across other electronic devices to intelligently generate new sharing targets (at least one graphical elements of at least one target application) such as across applications, across services, and across other electronic devices associated with the user.

In an embodiment, consider a scenario where the user selects content (i.e., text, photo, music, or the like) or an application feature (i.e., event) in the electronic device <NUM>. As shown in the <FIG>, the user selects inspirational quote image. After selecting the inspirational quote image, corresponding attributes of the inspirational quote image are analyzed and compared with the pending relations in the electronic device <NUM>. The different applications (i.e., social networking site (SNS)-<NUM>, SNS-<NUM>), other electronic devices, and the services with which the content can be shared are displayed to the user of the electronic device <NUM> as shown in the <FIG>. In an embodiment, metadata of the user selected image is analyzed and the applications, other electronic devices, the services with which the content can be shared are displayed on the electronic device <NUM>.

<FIG> illustrates various units of an electronic device for automatically managing the content according to an embodiment of the present disclosure.

Referring to <FIG>, in an embodiment, the electronic device <NUM> includes a content management engine <NUM>, a graphical element generator <NUM>, a memory <NUM>, a semantic engine <NUM>, and a transceiver or communicator <NUM>.

The content management engine <NUM> is configured to receive an input indicating selection of the content (for example, the content herein can refer to a feature of an application or data) in the electronic device <NUM>. In an example, the content can be the text, the photo, the music, or the like) or the application feature (i.e., event). Further, the content management engine <NUM> can be configured to determine at least one of a current user context and a historic user context. In an embodiment, the current user context is associated with an application currently active on the electronic device <NUM>. In an example, the application can be a Chat application, a Messenger application, a SNS application, an E-mail application, a Gallery application, a Navigation application, a Calendar application or any other applications available in the electronic device <NUM>. In an embodiment, the historic context is associated with one of an application conversation, user behavior, and past interactions of the user. In an example, the application conversation, can a chat conversation.

Further, the content management engine <NUM> is configured to extract parameters associated with the content from a current interaction context. Further, the content management engine <NUM> can be configured to determine a degree of similarity between the extracted parameters associated with the content and parameters associated with at least one of the current user context and the historic user context. Further, the content management engine <NUM> can be configured to cause to display at least one graphical element of at least one target data item corresponding to at least one of the current user context and the historic user context based on the degree of similarity. Further, the functionalities of the content management engine <NUM> are explained in conjunction with <FIG>. In an example, the graphical element is an icon. In an example, the target data item is a target application, a target service, a target device, or the like. In an embodiment, the at least one graphical element of the at least one target data item is dynamically generated by the graphical element generator <NUM>.

The memory <NUM> may include one or more computer-readable storage media. The memory <NUM> may include non-volatile storage elements. Examples of such non-volatile storage elements may include magnetic hard discs, optical discs, floppy discs, flash memories, or forms of electrically programmable read only memories (EPROM) or electrically erasable and programmable ROM (EEPROM). In addition, the memory <NUM> may, in some examples, be considered a non-transitory storage medium. The term "non-transitory" may indicate that the storage medium is not embodied in a carrier wave or a propagated signal. However, the term "non-transitory" should not be interpreted to mean that the memory <NUM> is non-movable. In some examples, the memory <NUM> can be configured to store larger amounts of information than the memory. In certain examples, a non-transitory storage medium may store data that can, over time, change (e.g., in random access memory (RAM) or cache). Further, the functionalities of the memory <NUM> are explained in conjunction with <FIG>. In an example, the memory <NUM> can be cloud storage. The functionalities of the semantic engine <NUM> are explained in conjunction with <FIG> and <FIG>. The communicator <NUM> can be configured for communicating internally between the units and externally with the networks.

<FIG> shows various units of the electronic device <NUM>, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the electronic device <NUM> may include less or more number of units. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the disclosure. One or more units can be combined together to perform same or substantially similar function in the electronic device <NUM>.

<FIG> is a schematic overview of a framework in an electronic device for automatically managing the content according to an embodiment of the present disclosure.

Referring to <FIG>, in an embodiment, a framework <NUM> includes a plurality of applications 302N (i.e., here after referred as the application(s) <NUM>), the content management engine <NUM>, the graphical element generator <NUM>, the memory <NUM>, and the communicator <NUM>. The content management engine <NUM> includes a data delivery unit <NUM>, an attribute extractor <NUM>, and a core engine <NUM> (i.e., a relation detector and matcher component).

The attribute extractor <NUM> can be configured to extract (or determine) the interaction history of the user with different applications, across all other devices of the user. Further, the attribute extractor <NUM> can be configured to extract various types of attributes (for example: metadata, meta-type, natural language processing (NLP), semantics, location, or the like) and provide to the core engine 102c for relation formation and matching. The metadata involves inherent meaning of the data. In an example, the semantic meaning relating actors with an object or a topic. In case of an image or a video, the metadata can be the object or a scene recognized within the image or the video data. An example scenario illustrating extraction of the attributes from a chat application and a navigation application is explained in conjunction with <FIG>. The core engine <NUM> can be configured to detect the relation between interaction identification (ID), corresponding data object, or data input, and the extracted attributes. Further, the core engine <NUM> can be configured to identify whether the data is pending or target input is pending. After identifying that the data is pending or the target input is pending, the core engine <NUM> can be configured to add a pending entry in the memory <NUM>.

Further, the core engine <NUM> can be configured to compare the attributes with the existing entries in the memory <NUM>. Further, the core engine <NUM> can be configured to retrieve a matching entry from the memory <NUM>. An example scenario for retrieving the matching entry from the memory <NUM> for the chat application and the navigation application is explained in conjunction with <FIG>. Further, the core engine <NUM> can be configured to communicate with other units in the electronic device <NUM>. The graphical element generator <NUM> can be configured to generate the at least one graphical element (i.e., icon) dynamically from the interaction ID. Further, the graphical element generator <NUM> can be configured to provide the generated at least one graphical element to the core engine <NUM>. The data delivery unit 102a can be configured to use the interaction ID and provided data to deliver to the target application input, with which the data needs to be shared. The communicator <NUM> can be configured to communicate with the users other devices or other electronic devices, available in an authorization list.

In an example, authorized user ID and device ID is shown below in Table <NUM>:.

The content management engine <NUM> can be configured to track and can collaborate the interaction history in all the users' devices (single login/authorized as self). If added to the authorization list, the content management engine <NUM> can be configured to communicate and deliver the data to other electronic devices. A target location in other electronic device is selected based on the matched interaction ID stored in the memory <NUM>.

In an embodiment, the target location can be extended to build a shared database across users for much wider sharing of the interaction history and the content sharing. However, this should be limited to a privileged group, based on a user setting or user-prompt, as this might involve privacy concerns. The memory <NUM> stores discovered relations as the user keeps on interacting with various applications (for example: interaction ID vs. context information, pending data vs. target device, etc.). Further, different priority approaches are described below:.

Priority Approach-<NUM>: Current Interaction > Recent Cross Device Interactions > Historical Interactions.

Each data entry is assigned a priority (high value) and the priority reduces as the data entry spends more time in the memory <NUM>. After a threshold time, the data entry is removed from the memory <NUM>. Thus, latest data gets the highest priority. When multiple matches occur, the top priority data entries can be displayed in order.

In this approach, metadata information (i.e., several feature information points) is extracted about the captured context. Based on the match score, the highest matching element gets the highest priority. Further, the calculation of the match point can be performed based on supervised, semi-supervised, or un-supervised learning techniques which can rank the items based on similarity or relation among feature points between the query parameters and the stored parameters belonging to current or historical context. In an example, getting a probability score for each pair of comparisons and using it as the matching score. The lowest priority or unused data entries, spending more time in the memory <NUM> can be removed after the threshold time. This is due to the fact that some of the items in the memory <NUM>, might not match with any queries for long duration. Such items can be removed after a threshold time to reduce the usage of the memory <NUM>.

In an embodiment, the content management engine <NUM> operates on the electronic device <NUM> and interacts with other electronic device as a distributed system. In an embodiment, the data is exchanged across the electronic devices only whenever some user interaction occurs on the data within authorized users or the electronic devices.

In an embodiment, the content management engine <NUM> can also be implemented as server based solution. In this case, only a communication component at the electronic device <NUM> is required. Core logic of the content management engine <NUM> can be implemented at the server.

In another embodiment, the content management engine <NUM> may include less or more number of units. Further, the labels or names of the units are used only for illustrative purpose and does not limit the scope of the disclosure. One or more units can be combined together to perform same or substantially similar function in the content management engine <NUM>.

<FIG> is a flow chart illustrating a method for automatically managing the content in an electronic device according to an embodiment of the present disclosure.

Referring to <FIG>, at operation <NUM>, the method includes receiving the input indicating selection of the content in the electronic device <NUM>. The method allows the content management engine <NUM> to receive the input indicating selection of the content in the electronic device <NUM>.

At operation <NUM>, the method includes determining at least one of the current user context and the historic user context. The method allows the content management engine <NUM> to determine at least one of the current user context and the historic user context. In an embodiment, the current user context is associated with the application currently active on the electronic device <NUM>. In an embodiment, the historic user context is associated with one of the chat conversation, user behavior, and past interactions of a user. At operation <NUM>, the method includes extracting parameters associated with the content from the current interaction context. The method allows the content management engine <NUM> to extract parameters associated with the content from the current interaction context.

At operation <NUM>, the method includes determining the degree of similarity between the extracted parameters associated with the content and the parameters associated with at least one of the current user context and the historic user context. The method allows the content management engine <NUM> to determine the degree of similarity between the extracted parameters associated with the content and the parameters associated with at least one of the current user context and the historic user context. In an embodiment, the target data item is the target application, the target service, the target device, or the like.

At operation <NUM>, the method includes causing to display the at least one graphical element of the at least one target data item corresponding to the at least one of the current user context and the historic user context based on the degree of similarity. The method allows the content management engine <NUM> to cause to display the at least one graphical element of the at least one target data item corresponding to the at least one of the current user context and the historic user context based on the degree of similarity. In an embodiment, the at least one graphical element of the at least one target data item is dynamically generated by the graphical element generator <NUM>. In an embodiment, the at least one graphical element is dynamically arranged based on the priority associated with the graphical element.

The various actions, acts, blocks, operations, or the like in the flow chart <NUM> may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

<FIG> illustrates an example for registering application specific parameters according to an embodiment of the present disclosure.

Application Specific Parameters describe a specific set of parameters which the application registers one time with the content management engine <NUM>. The parameters include various simple and complex data types such as address, image, contact, route information, uniform resource locator (URL), etc. Further, the parameters are used to form queries for receiving the attributes from the content management engine <NUM>.

Referring to <FIG>, the content management engine <NUM> can be configured to capture the interaction history of the user with the chat application <NUM> and the interaction history of the user with the navigation application <NUM>. Further, the content management engine <NUM> can be configured to extract various attributes. In case of the chat application <NUM>, the content management engine <NUM> can be configured to perform registration of the parameters such as the image, the address, a contact, a URL, a topic, or the like. In case of the navigation application <NUM>, the content management engine <NUM> can be configured to perform registration of the parameters such as the address, the route information, or the like. In an embodiment, the parameters, set by the application during registration is shown below Table <NUM>:.

<FIG> illustrates an example for extracting the attributes for the application (i.e., parameter specific) according to an embodiment of the present disclosure.

Attributes: The parameter is used to filter out corresponding attributes during the content/event analysis by components such as NLP/semantic engine etc. These attributes are then stored in the memory <NUM> along with other contextual information. Further, the attributes are also used to form a query and retrieve the results.

In case of the chat application <NUM>, the content management engine <NUM> can be configured to send the query to extract the attributes of the chat application <NUM>. The query sent to the chat application <NUM> and the data received from the chat application <NUM>, by the content management engine <NUM>, is described below:.

Chat application <NUM> attributes (Query):.

Chat application <NUM> attribute (data):.

In case of the navigation application <NUM>, the content management engine <NUM> can be configured to send the query to extract the attributes of the navigation application <NUM>. The query sent to the navigation application <NUM> and the data received from the navigation application <NUM>, by the content management engine <NUM>, is described below:.

Navigation application <NUM> attributes (Query):.

Navigation application <NUM> attributes (Data):
b. Route: Vehicle route, time (current), Type (visit), etc..

<FIG> is a system illustrating an interaction between a content management unit and an NLP unit for extracting the attributes from an NLP server according to an embodiment of the present disclosure.

Referring to <FIG>, the system includes the electronic device <NUM> and an NLP server <NUM>. The electronic device <NUM> includes the applications <NUM>, the content management engine <NUM>, and an NLP unit <NUM>. In an example, the application can be the chat application <NUM>, the mail application, the message application, the SNS application, a browser application, a voice conversation application, the navigation application <NUM>, or any other applications available in the electronic device <NUM>.

In an embodiment, few implementation options are provided below:
Implementation-<NUM>: As a service (for example, NLP web service application program interfaces (APIs).

Implementation-<NUM>: As an in-device NLP unit <NUM> as shown in the <FIG>, in which the NLP unit <NUM> interacts with the NLP server <NUM> for extracting the attributes.

<FIG> illustrates an example interaction between a content management unit and an NLP unit according to an embodiment of the present disclosure.

Referring to <FIG>, the content management engine <NUM> receives the message content (i.e., chat conversation between the user and his wife) "I am waiting at a Mall, Can you please pick me up? Buy noodles from Sam's grocery while coming". After receiving the message content, the content management engine <NUM> sends the service call to the NLP unit <NUM>. The NLP unit <NUM> sends the following responses as described below:.

After receiving the responses, the content management engine <NUM> can be configured to process and filter based on the parameters. Further, the content management engine <NUM> can be configured to create the entry (or data entry) in the memory <NUM> as shown below in Table <NUM>.

<FIG> is a flow chart illustrating a method for automatically managing content in a source device according to an embodiment of the present disclosure.

Referring to <FIG>, in an embodiment, the source device is an electronic device 100a and a target device is an electronic device 100b.

At operation <NUM>, the method includes receiving the input indicating selection of the content or the feature event in the electronic device 100a. The method allows a content management engine 102a to receive the input indicating selection of the content or the feature event in the electronic device 100a. At operation <NUM>, the method includes analyzing the metadata or the meta-type of the selected content or the feature event. The method allows the content management engine 102a to analyze the metadata or the meta-type of the selected content or the feature event.

If it is determined, at operation <NUM>, that the authorized electronic device 100b is connected then, at operation <NUM>, the method includes forming a query based on the metadata and broadcasting the metadata to the electronic device <NUM> (i.e., target device) for getting matching target graphical element. The method allows the content management engine 102a to form the query based on the metadata and broadcast the metadata to the electronic device 100b. The metadata parameters are sent as part of the query to determine matching data elements from other electronic devices, which are connected. If it is determined, at operation <NUM>, that the authorized electronic device 100b is not connected then, the method is looped back to operation <NUM>.

At operation <NUM>, the method includes receiving the at least one matched target data item, link ID, and match points from the electronic device 100b. The method allows the content management engine 102a to receive the at least one matched target data item, the link ID, and the match points from the electronic device 100b. At operation <NUM>, the method includes generating the at least one graphical element (i.e., destination graphical element) as per the match points order. The method allows the content management engine 102a to generate the at least one graphical element (i.e., destination graphical element) as per the match points order.

At operation <NUM>, the method includes receiving a gesture performed by the user to drag and drop the content onto the graphical element. The method allows the content management engine 102a to receive the gesture performed by the user to drag and drop the content onto the graphical element. At operation <NUM>, the method includes sending the content with the ID information to the electronic device 100b. The method allows the content management engine 102a to send the content with the ID information to the electronic device 100b. At operation <NUM>, the method includes erasing the graphical element and notifying the user. The method allows the content management engine 102a to erase the graphical element and notify the user.

<FIG> is a flow chart illustrating a method for adding an entry into a memory of an electronic device according to an embodiment of the present disclosure.

Referring to <FIG>, at operation 902a, the method includes extracting the interaction history and the content attributes of the SNS <NUM>, users (cross device) interactions <NUM>, the application data <NUM>, or the like. The method allows the content management engine 102b to capture the interaction history and the content attributes of the SNS <NUM>, the users (cross device) interactions <NUM>, the application data <NUM>, or the like.

At operation 904a, the method includes forming the relation between the interaction ID and the attributes. The method allows the content management engine 102b to form the relation between the interaction ID and the attributes. At operation 906a, the method includes adding the entry in the memory 106b of the electronic device 100b with timeout and looped back to operation 902a. The method allows the content management engine 102b to add the entry in the memory 106b for further re-use and looped back to operation 902a. In an embodiment, the entry includes the relation between the interactions ID and the attributes. In an example, some of the attributes, which are stored in the memory <NUM>, can become invalid after some time. Consider a scenario where the user's location at first instance can become invalid after some time if the user is moving or changing his/her location. In this case, the timeout helps to check if the data is valid or not. Further, the stored data is invalidated and trigger fetching of live data, which in turn can be updated and stored in the memory <NUM>.

The various actions, acts, blocks, operations, or the like in the flow chart 900a may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

<FIG> and <FIG> are flow charts illustrating a method for automatically managing content in a target device or a target screen according to an embodiment as of the present disclosure.

Referring to <FIG>, at operation 902b, the method includes receiving the query parameters from the electronic device 100a. The method allows the content management engine 102a to receive the query parameters from the electronic device 100a.

If it is determined, at operation 904b, that the metadata is from the authorized user then, at operation 906b, the method includes determining whether the matching entry present in the memory 106b corresponding to the query parameters. The method allows the content management engine 102b to determine whether the matching entry present in the memory 106b corresponding to the query parameters. If it is determined, at operation 904b, that the metadata is not from the authorized user then, at operation 908b, the method includes sending no match found indication to the electronic device 100a. The method allows the content management engine 102b to send the no match found indication to the electronic device 100a.

If it is determined, at operation 906b, that the metadata of the content exists in the memory 106b then, at operation 910b, the method includes sending the at least one graphical element of the at least one target data item, link ID, match points to the electronic device 100a. The method allows the content management engine 102b to send the at least one graphical element of the at least one target data item, the link ID, the match points to the electronic device 100a. If it is determined, at operation 906b, that the metadata of the content does not exist in the memory 106b then, the method performs operation 908b as described above.

At operation 912b, the method includes receiving the content with ID information from the electronic device 100a. The method allows the content management engine 102b to receive the content with the ID information from the electronic device 100a. If it is determined, at operation 914b, that the content is received from the user's electronic device 100a then, at operation 916b, the method includes launching a screen of a target application and post the content. The method allows the content management engine 102b to launch the screen of the target application and post the content. At operation 918b, the method includes updating the content in the memory 106b. The method allows the content management engine 102b to update the content in the memory 106b. The operation 914b is performed to ensure that the electronic device 100a and the electronic device 100b belong to different users or different users are operating in both the devices. Once the data is transferred and dropped on the graphical icon, it does not create distraction for the other user in his/her device by launching a different application screen than the current screen. A notification bubble can be used to notify that the data is available and ready, but it does not directly launch a new screen until the user selects the bubble. When the user selects the bubble, actual target location screen is launched where the transferred data is dropped.

In an example, consider a scenario where the electronic device 100a has a form field opened and the electronic device 100b has the data. The icon is generated corresponding to the form field. If the data is dropped to the icon, the data is sent to the electronic device 100a and is pasted to the form field. Consider another scenario where there are different users operating in the electronic device 100a and the electronic device 100b and the form field screen is changed (by switching to other application) when the drop is performed in the electronic device 100a. Even though, the data is pushed to the electronic device 100a, it does not launch the form field screen immediately until the user taps the notification bubble.

If it is determined, at operation 914b, that the content is not received from the user's electronic device 100a then, at operation 920b, the method includes determining whether a foreground screen matching with the drop target. If it is determined, at operation 920b, that the foreground screen matching with the drop target then, referring to <FIG>, at operation 916b, the method performs operation 916b as described above. If it is determined, at operation 920b, that the foreground screen not matching with the drop target then, at operation 922b, the method includes creating a content bubble (i.e., notification). The method allows the content management engine 102b to create the content bubble. In an example, the content bubble indicates that the data is dropped in the electronic device 100b after match was detected and the user at the electronic device 100a has performed some gesture on one of the generated icons to send the data to the electronic device 100b. It helps to avoid sudden distraction or transition in the foreground screen if there were some other user operating on the electronic device 100b.

At operation 924b, the method includes detecting an input on the content bubble performed by the user. The method allows the content management engine 102b to detect the input on the content bubble performed by the user. At operation 926b, the method includes launching the screen of the target application and post the content; and the method performs operation 918b as described above. The method allows the content management engine 102b to launch the screen of the target application and post the content; and the method performs operation 918b as described above.

The various actions, acts, blocks, operations, or the like in the flow chart 900b may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some of the actions, blocks, operations, or the like may be omitted, added, modified, skipped, or the like without departing from the scope of the disclosure.

<FIG> is an example sequence diagram illustrating a method for automatically managing the content between a User-A and a User-B according to an embodiment of the present disclosure.

Referring to <FIG>, the sequence diagram illustrates a sequence of operations performed between the electronic device 100a and a car <NUM>. The electronic device 100a includes the chat application <NUM>, a semantic engine <NUM>, and the content management engine 102a. The car <NUM> includes the navigation application <NUM> and the content management engine 102b.

At operation 1002a, initially, the content management engine 102a extracts the parameters of the chat application <NUM> for one time registration. Similarly, the content management engine 102b extracts the parameters of the navigation application <NUM> for one time registration.

At operation 1004a, the content management engine 102a initializes the semantic engine <NUM>. Further, the content management engine 102a sends the extracted parameters to the semantic engine <NUM>.

At operation 1006a, the User-A receives a message "I am waiting at Mall, Can you please pick me up? Buy noodles from Sam's grocery while coming", in the chat application <NUM>, from the User-B (i.e., wife of User-A).

At operation 1008a, the semantic engine <NUM> extracts the message content from the chat application <NUM>.

At operation 1010a, after receiving the message content from the chat application <NUM>, the semantic engine <NUM> analyzes the message content to filter the parameter based attributes.

At operation 1012a, after filtering the attributes, the semantic engine <NUM> sends the attributes to the content management engine 102a. The content management engine 102a stores the attributes in the memory 106a.

At operation 1014a, the navigation application <NUM> displayed on a dashboard of the car <NUM> receives an input indicating the selection of the feature "set destination", by the User-A.

At operation 1016a, the navigation application <NUM> sends the query (i.e., In-device query) for the attributes, to the content management engine 102b.

At operation 1018a, the content management engine 102b sends the query (i.e., cross device query) for the attributes to the content management engine 102a.

At operation 1020a, the content management engine 102a detects the match for address.

At operation 1022a, if the match for address (i.e., Visit pending) is detected then, the content management engine 102a sends address options with the at least one graphical element (i.e., icons) to content management engine 102b.

At operation 1024a, the content management engine 102b displays the address options within the navigation application <NUM>.

At operation 1026a, the User-A sets the suggested address as the destination address in the navigation application <NUM>.

At operation 1028a, the route information is sent to the content management engine 102b to store in the memory 106b.

<FIG> is another sequence diagram for automatically managing the content between the User-A and a User-C according to an embodiment of the present disclosure.

Referring to <FIG>, the sequence diagram illustrates a sequence of operations performed between the electronic device 100a and the car <NUM>.

At operation 1002b, the User-A receives a message "Where are you going" in the chat application <NUM>, from the User-C.

At operation 1004b, the semantic engine <NUM> extracts the message content from the chat application <NUM>.

At operation 1006b, after receiving the message content from the chat application <NUM>, the semantic engine <NUM> analyzes the message content to filter the parameter based attributes.

At operation 1008b, after filtering the attributes, the semantic engine <NUM> sends the attributes ((i.e., Requested data: the User-A next address, route information) and chat ID) to the content management engine 102a. The content management engine 102a stores the attributes in the memory 106a.

At operation 1010b, the User-A performs the feature event: Input selection in the chat application <NUM>.

At operation 1012b, the chat application <NUM> sends the query (i.e., In-device query) for the attributes, to the content management engine 102a.

At operation 1014b, the content management engine 102a sends the query for the attributes (i.e., cross device query for the User-A present route information and destination address, etc.), to the content management engine 102b.

At operation 1016b, the content management engine 102b detects the match for address.

At operation 1018b, if the match for the route information is detected then, the content management engine 102b sends the route options with the graphical elements to the content management engine 102a.

At operation 1020b, the content management engine 102a displays the route options within the screen of the chat application <NUM>.

At operation 1022b, the User-A selects the route or drops the graphical element to chat input.

At operation 1024b, the route information is sent to the content management engine 102b to store in the memory 106b.

In an embodiment, the at least one graphical element of varying size can be generated based on the priority.

<FIG>, <FIG>, <FIG>, and <FIG> illustrate example scenarios in which content of an application is accessed from another application context according to various embodiments of the present disclosure. Here, the image meta-data is used to find the matching target destination as the chat interaction-id.

Referring to <FIG>, the chat conversation between the User-A; and the User-B (User-A wife) is as follows i.e., "I am waiting at the Mall, Can you please pick me at <NUM> PM? Buy noodles from the Sam's grocery while coming. " Based on the chat conversation, the content management engine 102a can be configured to retrieve the interaction ID. The interaction ID can be Pick Up, Mall, Address, and Sam's Grocery. Further, the content management engine 102a can be configured to provide dynamic options for setting destination such as Pickup address via the Sam's Grocery.

Further, the content management engine 102a can be configured to provide the attributes. The attributes can be the destination point and the address. Later, the User-A enters his car <NUM>, the car <NUM> display prompts to set the destination address as shown in the <FIG>. As soon as the User-A selects the destination setting, the content management engine 102b sends the query to the content management engine 102a to detect the match as shown in the <FIG>. Further, if the match is detected, the different address options are displayed based on the chat conversation as shown in the <FIG>. The user-A selects the first address option i.e., Wife' address via Sam's Grocery to be the destination address. The map corresponding to the same is displayed in the navigation screen of the car <NUM> as shown in the <FIG>.

<FIG>, <FIG>, and <FIG> illustrate example scenarios in which multiple electronic devices interact with content, in an Application-<NUM> conversation, between a User-A and a User-B according to various embodiments of the present disclosure. The framework <NUM> components interact with the data when the user performs operations on the device screens.

Consider a scenario where a chat conversation is going on between the User-A; and the User-B. Here, the how User-A's electronic device 100a screen (e.g. a chat application) is shown.

The User-B requests to the User-A over chat: "Please share your US tour photos. " Also, the User-B requests to send the photos in the same chat-group. The chat content is then processed by the content-management engine 102a in the electronic device 100a and attributes extracted along with interaction ID (i.e., chat ID with the User-B in specific chat application). These mappings are stored in the memory 106a as shown in the <FIG>.

Further, when the User-A opens his/her electronic device 100b gallery to share the photos as shown in the <FIG>, as soon as the User-A selects the US tour album photos, the meta-data attributes are extracted from the photo and the same is used to form a query by the content management unit 102b of the electronic device 100b and sent to the electronic device 100a as shown in the <FIG>. If a match is detected with previously stored interaction ID (i.e., chat with the User-B) then, the icon is generated and sent to the tablet. This generated icon is shown in the electronic device 100b, linking it to the actual destination of the electronic device 100a User-A's chat with the User-B as shown in the <FIG>. Once the User-A drops the image on to the icon by performing some gesture over the icon, the image content is sent across and finally it is posted in the chat input of the electronic device 100a.

<FIG> illustrates an example scenario in which an electronic device interacts with content in multi-user scenario according to an embodiment of the present disclosure.

Referring to <FIG>, a conversation between User-A and User-B is shown. The User-B interest captured is "Soccer: Liverpool". Later, while the User-A is browsing web, related to the content displayed on the web page. Based on the related content, the electronic device 100a of the User-A displays the User-B electronic device 100b graphical element as well as the SNS graphical element. The electronic device 100a of the User-A sends the content to the User-B electronic device 100b, which can be viewed later.

<FIG> illustrates a computing environment implementing a method and system for automatically managing content in an electronic device according to an embodiment of the present disclosure.

Referring to <FIG>, as depicted, a computing environment <NUM> comprises at least one processing unit <NUM> that is equipped with a control unit <NUM> and an arithmetic logic unit (ALU) <NUM>, a memory <NUM>, a storage unit <NUM>, plurality of networking devices <NUM>, and a plurality input/output (I/O) devices <NUM>. The processing unit ("processor") <NUM> is responsible for processing the instructions of the schemes. The processing unit <NUM> receives commands from the control unit <NUM> in order to perform its processing. Further, any logical and arithmetic operations involved in the execution of the instructions are computed with the help of the ALU <NUM>. The various methods described in the present disclosure may be executed by the processing unit <NUM>.

The overall computing environment <NUM> can be composed of multiple homogeneous or heterogeneous cores, multiple central processing units (CPUs) of different kinds, special media and other accelerators. The processing unit <NUM> is responsible for processing the instructions of the schemes. Further, the plurality of processing units <NUM> may be located on a single chip or over multiple chips.

The scheme comprising of instructions and codes required for the implementation are stored in either the memory unit <NUM> or the storage <NUM> or both. At the time of execution, the instructions may be fetched from the corresponding memory <NUM> or storage unit <NUM>, and executed by the processing unit <NUM>.

In case of any hardware implementations various networking devices <NUM> or external I/O devices <NUM> may be connected to the computing environment to support the implementation through the networking unit and the I/O device unit. Networking devices <NUM> comprises a communicator to communicate with at least one external device and other electronic devices through wired and/or wireless network.

The various 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 elements. The elements shown in the <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG>, <FIG> include blocks which can be at least one of a hardware device, or a combination of hardware device and software units.

In accordance with an embodiment of the present disclosure, a method comprises determining first attributes of a first content in a first application by analyzing the first content while the first application is active in the electronic device, receiving a query request for second attributes corresponding to a second content of a second application executed in an external device from the external device, and in response to the second attributes request query, transmitting target data information for generating at least one icon to be displayed on the external device to the external device based on the first attributes and the second attributes.

The external device displays at least one icon corresponding to the target data information on an execution display of the second application of the external device.

In response to selection of the at least one icon on the external device, the external device displays target data associated with the data information corresponding to the second attributes on an execution display of the second application based on the content.

The determining the first attributes further comprises extracting parameters of the first application, filtering the first attributes using the parameters, and storing the filtered first attributes in a memory of the electronic device.

The transmitting further comprises detecting match information between the filtered first attributes and the second attributes, and determining the target data corresponding to the second attributes based on the match information.

The first application is at least one of chat, email, and message application, and the first content is at least one of text, image, video, and streaming which are executed in an execution screen of the first application and is selected or input by a user.

The first attributes are determined using metadata of the first content and NLP, and comprises route information, address information, and destination address information.

The second application is a navigation application, and the second content is associated with selection and input of the second content in the second application.

The second attributes are determined using metadata of the second content, and comprises address information, route information, and destination information.

The transmitting further comprises generating the at least one icon corresponding to the second attributes based on the match information, and displaying the generated at least one icon on an execution display of the first application of the electronic device.

In accordance with an embodiment of the present disclosure, an electronic device comprises a communicator configured to communicate with an external device, and a processor configured to determine first attributes of a first content in a first application by analyzing the first content while the first application is active in the electronic device, to receive a query request for second attributes corresponding to a second event of a second application executed in the external device from the external device, and to, in response to the second attributes request query, transmit target data information for generating at least one icon to be displayed on the external device to the external device based on the first attributes and the second attributes.

The electronic device further comprises a memory, and the processor is configured to extract parameters of the first application, to filter the first attributes using the parameters, and to store the filtered first attributes in the memory.

The processor is further configured to detect match information between the filtered first attributes and the second attributes, and to determine the target data corresponding to the second attributes based on the match information.

The electronic device further comprises a display, and the processor is further configured to generate the at least one icon corresponding to the second attributes based on the match information, and to control the display to display the generated at least one icon on an execution display of the first application of the electronic device.

For example, target data information is such as the link ID of at least one applications, interaction ID with which communicate the electronic device, target device, target application, target service, and target data with which the electronic device share as described above in the present disclosure.

Claim 1:
A method for content management in an electronic device (100a), the method comprising:
determining first attributes of a first content in a first application (<NUM>) by analyzing metadata of first content while the first application (<NUM>) is active in the electronic device (100a);
determining whether an external device (100b) is connected to the electronic device (100a);
forming a query based on the metadata;
sending the query request to share information between the electronic device (100a) and the external device (<NUM>);
determining whether there is a matching entry present in the memory of the external device (100b) based on the query parameters;
if there is a matching entry, receiving response of the query request from the external device (100b) and including second attributes corresponding to a second content of a second application (<NUM>) executed in the external device (100b), wherein the second attributes comprise at least one matched target data item, a link ID of at least one application, and calculated match points of the second content;
wherein target data item is a target application, target service or target device,
determining target data information to be shared with the external device (100b) based on the first attributes and the second attributes, and
generating at least one graphical element based on the match points, and
receiving a gesture performed by the user to drag and drop the first content onto the at least one graphical element, and
transmitting, using the at least one graphical element, the target data information to the external device (100b).