Embodiments of the present disclosure relate to the field of electronics. More particularly, embodiments of the present disclosure relate to interaction of smart devices in a network.
Smart devices are devices that are digital, active, and computer networked. The smart devices are also user configurable and can operate to some extent autonomously. Appliances are devices that are task specific and under control of some embedded system or application specific operating system. One distinctive difference between the smart devices and the appliances may lie in the ability of the smart devices in supporting multiple tasks, whereas the appliances may be configured to perform a single task.
Some of the examples of the smart devices may include a personal computer (PC), a tablet PC, a smart TV, a mobile phone, a laptop computer, etc. Some of the examples of the appliances may include a home appliance, which further include major appliances (e.g., an air-conditioner, a dishwasher, a clothes dryer, a freezer, a kitchen stove, a water heater, a washing machine, a trash compactor, a microwave oven, etc.) as well as small appliances (e.g., a CD/DVD player, camcorder, a camera, a clock, a telephone, etc.). Recently, the smart devices and the appliances are being connected through a network as an effort for automating home or office.
One embodiment of the present disclosure pertains to a method of a smart device interacting with associated smart devices via a network. The method comprises identifying one or more associated smart devices upon activation of a smart device in a network, where the smart device and the associated smart devices are configured to communicate with each other for notification or for executing one or more commands. The method also comprises determining a mode of the smart device upon receiving data from the associated smart devices, where the mode of the smart device is set through configuring a user experience environment of the smart device. The method further comprises selectively processing the data from the associated smart devices based on the mode of the smart device.
Example embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:
Other features of the present embodiments will be apparent from the accompanying drawings and from the detailed description that follows.
A method, device and/or system are disclosed that selectively interact data based on the mode of the device. According to embodiments of this disclosure, a number of smart devices and/or smart appliances may be connected through a network (e.g., a home network). If a user is currently using a particular device, the user may want to be notified of any developments with the remaining smart devices or smart appliances that the user cannot attend to. However, the user may choose to block unnecessary messages of low importance or priority to concentrate on or enjoy the user's current task.
As a solution, the user may selectively process data (e.g., notification data, command data, etc.) from the associated device(s) with respect to the current mode of the smart device currently operated by the user. For example, if the user is using a tablet PC, the user may configure the mode of the tablet PC to set up the communication mode of the tablet PC, first. For example, if the user is currently free to receive any message or notification, then the user may configure the threshold level of the data received and to be processed by the tablet PC to be the lowest. Accordingly, any message or notification from the associated device(s) may be processed and displayed on a display unit of the tablet PC. Alternatively, if the user is fully occupied by the current task on the tablet PC, the user may set the threshold level of the received data to be processed by the tablet PC to be the highest or choose to block any message addressed to the tablet PC.
In another embodiment, the user may configure the user experience (UX) environment (e.g., a home screen) of the smart device currently operated by the user such that the mode of the smart device automatically changes on a temporal basis. For example, the mode of the smart device (e.g., a mobile phone) may be set to put the mode of the mobile phone in an organize mode (e.g., which put forwards apps such as Outlook® calendar, etc. on the home screen of the smart device) between 6 am and 9 am, in a work mode (e.g., which put forwards apps such as MS Word®, Power Point®, etc.) between 9 am and 6 pm, in a connect mode (e.g., which put forwards widgets such as Hotmail®, Gmail®, Gtalk®, etc.), and a relax mode between 9 pm and 6 am (e.g., which put forwards apps and/or widgets such as YouTube®, games, etc.). Once the mode of the mobile phone is set on the temporal basis, then the mode of the mobile phone may be determined by referring to the time upon the receipt of data from an associated smart device. Then, the data may be processed based on the mode of the mobile phone. As discussed above, if the priority of the data from the associated device is lower than the threshold level of data to be processed by the mobile phone under the current mode, then the data may be ignored by the mobile phone.
As described above, the selective interaction of the smart devices sharing a network may enable the user of the smart devices to automatically filter the amount of data that need to be processed by the user. More particularly, by selectively screening messages or notifications from associated devices with respect to the current mode of the smart device, the user may be able to enjoy more of the UX environment afforded by the smart device, while freeing the user from attending to needless tasks.
Reference will now be made in detail to the embodiments of the disclosure, examples of which are illustrated in the accompanying drawings. While the disclosure will be described in conjunction with the embodiments, it will be understood that they are not intended to limit the disclosure to these embodiments. On the contrary, the disclosure is intended to cover alternatives, modifications and equivalents, which may be included within the spirit and scope of the disclosure. Furthermore, in the detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be obvious to one of ordinary skill in the art that the present disclosure may be practiced without these specific details. In other instances, well known methods, procedures, components, and circuits have not been described in detail as not to unnecessarily obscure aspects of the present disclosure. Further, throughout this document, the smart devices may be used to include any devices or appliances that can communicate with one or more other smart devices or appliances through a network.
As illustrated in
In one example implementation, the smart devices 104A-N include a personal computer (PC), a tablet PC, a smart TV, a mobile phone, a laptop computer, etc. Further, the smart appliances 106A-N include a home appliance, such as an air-conditioner, a dishwasher, a clothes dryer, a freezer, a kitchen stove, a water heater, a washing machine, a trash compactor, a microwave oven, a CD/DVD player, camcorder, a camera, a clock, a telephone, etc.
In addition, the processor 110 is configured to determine a mode of the smart device 104A upon receiving data from one or more of the associated smart appliances 106A-N and/or the smart devices 104B-N, where the mode of the smart device 104A is set through configuring a user experience (UX) environment of the smart device 104A, as will be illustrated in details in
For example, the network view 204 is displayed on the display unit of the smart device 104A to inform the user that the smart device 104B (e.g., a mobile phone), the smart device 104N (e.g., a smart TV), the smart appliance 106A (e.g., an air conditioner), the smart appliance 106B (e.g., a CD player), and the smart appliance 106C (e.g., a washing machine) are currently connected to the smart device 104A through the network 102. It is appreciated that the button 202 may be realized through a soft button on a touch panel or through voice recognition technology instead. The application view 206 may process one or more applications (e.g., web application(s) and/or application software implemented on the smart device 104A), such as Face Book®.
In operation 302, one or more of the associated smart devices 104B-N and 106A-N are identified upon activation of the smart device 104A in the network 102, where the smart device 104A and the associated smart devices 104B-N and 106A-N are configured to communicate with each other for notification or for executing one or more commands. In operation 304, a mode of the smart device 104A is determined upon receiving data from one of the associated smart devices 104B-N and 106A-N, where the mode of the smart device 104A is set through configuring a UX environment of the smart device 104A. For example, the data from the associated smart devices 104B-N and 106A-N is notification data for notifying the smart device 104A or command data for causing the smart device 104A execute one or more commands.
In operation 306, the data from one of the associated smart devices 104B-N and 106A-N is selectively processed based on the mode of the smart device 104A, as will be illustrated in detail in
It is appreciated that the methods disclosed in
More particularly, as illustrated in
In an alternative embodiment, the mode of the smart device 104A is set based on the regional basis 414. Although it is not shown, the mode of the smart device 104A or the UX environment 402 may be set based on the global positioning system (GPS) information associated with the smart device 104A. For example, the mode of the smart device 104A may be configured to be in the organize mode 404 when the user is in route to the work from home, to be in the work mode 406 when the user is at work, to be in the connect mode 408 when the user is in route to home from work, and to be in the relax mode 410 when the user is at home.
In yet another alternative embodiment, the mode of the smart device 104A is set based on a primary task currently executed on the UX environment 402. That is, the mode of the smart device 104A may be set based on the user's choosing of a particular application as the primary task of the smart device 104A. For example, the mode of the smart device 104A may be put to the organize mode 404 if the user is currently executing a calendar program as the primary task, to the work mode 406 if the user is currently executing a word processing program as the primary task, to the connect mode 408 if the user is currently running an email program as the primary task, or to the relax mode 410 if the user is currently executing an online game program as the primary task.
In
While the smart device 104A is in the organize mode 404, data from the associated devices 104B-N and/or the associated appliances 106A-N in
However, in an alternative embodiment, a message notifying a receipt of the data is masked when the mode of the smart device 104A is configured to cease the processing of the data from the associated smart device 104B-N and/or the associated smart appliances 106A-N. In one exemplary implementation of the alternative embodiment, a processing value is set to ‘false’ if the priority level of the data is lower than the threshold level. Accordingly, the UX environment 402 may not display any message indicating arrival of the data from the associated smart device. This way, notification of events with minimal importance with respect to the current mode of the user device may be avoided.
While the smart device 104A is in the work mode 406, data from the associated devices 104B-N and the associated appliances 106A-N in
For example, the threshold level may be set to ‘1’ for the work mode 406 of the smart device 104A, so that the data from any smart device or appliance may be processed to be displayed on the display unit of the smart device 104 only if the priority level of the data is equal to ‘1.’ In this example, only the priority level of the data from the smart device 104B (e.g., the mobile phone) may be set to equal to ‘1’ to allow its processing by the smart device 104A. Accordingly, only an alert message which notifies a receipt of the data from the smart device 104B is displayed on the display unit of the smart device 104A. However, data from the remaining smart devices or smart appliances may be ignored or queued for processing until the mode of the smart device 104A is changed to a lower priority.
While the smart device 104A is in the connect mode 408, data from the associated devices 104B-N and the associated appliances 106A-N in
While the smart device 104A is in the relax mode 410, data from the associated devices 104B-N and the associated appliances 106A-N in
In operation 902, one or more associated smart devices 104B-N and 106A-N are identified upon activation of the smart device 104A in the network 102, where the smart device 104A and the associated smart devices 104B-N and 106A-N are configured to communicate with each other for notification or for executing one or more commands. In operation 904, a mode of the smart device 104A is determined upon receiving data from one of the associated smart devices 104B-N and 106A-N, where the mode of the smart device 104A is set through configuring the UX environment 402 of the smart device 104A.
In operation 906, a priority level of the data from the one of the associated smart devices 104B-N and 106A-N is identified. In operation 908, it is determined whether the priority level of the data is valid for processing. That is, a processing value of the data is set to ‘true’ or ‘valid’ if the priority level of the data from the one of the associated smart devices 104B-N and 106A-N is equal to or higher than the threshold level of data to be processed by the mode of the smart device 104A. Otherwise, the processing value of the data is set to ‘false’ or ‘invalid.’ If the priority level of the data is valid for processing, in operation 910, a notification message or an alert message which notifies a receipt of the data is displayed on a display unit of the smart device 104A. However, if the priority level of the data is not valid for processing, in operation 912, the display unit of the smart device 104A won't notify the user of the arrival of the data from the associated smart device.
For example, in
For example, in
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and features disclosed herein.
This application is the National Phase of PCT/KR2010/006012 filed on Sep. 3, 2010 which claims priority under 35 U.S.C. 119(e) to U.S. Provisional Application No. 61/365,790 filed on Jul. 20, 2010, all of which are hereby expressly incorporated by reference into the present application.
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/KR2010/006012 | 9/3/2010 | WO | 00 | 12/1/2010 |
Publishing Document | Publishing Date | Country | Kind |
---|---|---|---|
WO2012/011630 | 1/26/2012 | WO | A |
Number | Name | Date | Kind |
---|---|---|---|
6725303 | Hoguta et al. | Apr 2004 | B1 |
6771290 | Hoyle | Aug 2004 | B1 |
6983244 | Junqua et al. | Jan 2006 | B2 |
7636365 | Chang et al. | Dec 2009 | B2 |
7734148 | Lee | Jun 2010 | B2 |
7996412 | Bae et al. | Aug 2011 | B2 |
8131763 | Tuscano et al. | Mar 2012 | B2 |
20030236770 | Kurapati et al. | Dec 2003 | A1 |
20040172588 | Mattaway | Sep 2004 | A1 |
20050030708 | Kawasaki et al. | Feb 2005 | A1 |
20050091595 | Shappell et al. | Apr 2005 | A1 |
20060117001 | Jung et al. | Jun 2006 | A1 |
20060271618 | Kokubo et al. | Nov 2006 | A1 |
20070005707 | Teodosiu et al. | Jan 2007 | A1 |
20070050778 | Lee et al. | Mar 2007 | A1 |
20070156664 | Norton et al. | Jul 2007 | A1 |
20070294357 | Antoine | Dec 2007 | A1 |
20080082936 | Helvick | Apr 2008 | A1 |
20080310510 | Hiwasa et al. | Dec 2008 | A1 |
20090023395 | Chang et al. | Jan 2009 | A1 |
20090049380 | Rehling et al. | Feb 2009 | A1 |
20090094531 | Danieli et al. | Apr 2009 | A1 |
20090157513 | Bonev et al. | Jun 2009 | A1 |
20090158170 | Narayanan et al. | Jun 2009 | A1 |
20090249359 | Caunter et al. | Oct 2009 | A1 |
20090299960 | Lineberger | Dec 2009 | A1 |
20090307168 | Bockius et al. | Dec 2009 | A1 |
20090313004 | Levi et al. | Dec 2009 | A1 |
20100030578 | Siddique et al. | Feb 2010 | A1 |
20100043061 | Martin et al. | Feb 2010 | A1 |
20100066698 | Seo | Mar 2010 | A1 |
20100088634 | Tsuruta et al. | Apr 2010 | A1 |
20100122184 | Vonog et al. | May 2010 | A1 |
20100138767 | Wang et al. | Jun 2010 | A1 |
20100169823 | Audet | Jul 2010 | A1 |
20100174993 | Pennington et al. | Jul 2010 | A1 |
20100241980 | Sosnosky et al. | Sep 2010 | A1 |
20100241989 | Wen | Sep 2010 | A1 |
20100295992 | Lee et al. | Nov 2010 | A1 |
20100299628 | Har'el et al. | Nov 2010 | A1 |
20110066957 | Prats et al. | Mar 2011 | A1 |
20110113385 | Sayers et al. | May 2011 | A1 |
20120092253 | Irani et al. | Apr 2012 | A1 |
Number | Date | Country |
---|---|---|
1835384 | Sep 2007 | EP |
2004-38283 | Feb 2004 | JP |
2004-62369 | Feb 2004 | JP |
2005-285274 | Oct 2005 | JP |
2007-42173 | Feb 2007 | JP |
2007-272625 | Oct 2007 | JP |
4564488 | Oct 2010 | JP |
10-2008-0023575 | Mar 2008 | KE |
10-2005-0055101 | Jun 2005 | KR |
10-2005-0099741 | Oct 2005 | KR |
10-2009-0062371 | Jun 2009 | KR |
10-2009-0113508 | Nov 2009 | KR |
10-2010-002758 | Jan 2010 | KR |
WO 2008048008 | Apr 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20120023212 A1 | Jan 2012 | US |
Number | Date | Country | |
---|---|---|---|
61365790 | Jul 2010 | US |