Patent Description:
Currently, electronic devices provide a low power display mode referred to as always on display (AOD). In the AOD mode, power consumption of the display can be reduced. However, in existing scenarios, only pre-defined applications or widgets can be compatible with the AOD mode. For example, navigation applications, comprehensive always on content, always on user controls such as widgets, television (TV)/internet of things (IoT) remote and so on may not be compatible with the AOD mode. Further, a display rate (i.e., frames per second (FPS)), color depth and brightness can be reduced while displaying incompatible content on the AOD.

<CIT>discloses methods and apparatus for displaying notification information in various modes, including an AOD mode, controlled by user swipes on the display.

From <CIT>a process and device for displaying and altering content in a low-power state of the electronic device is known that allows executing an AOD mode for enabling the display unit to be always turned on at low power while at least one application is running in a background state.

Accordingly, an aspect of the disclosure is to provide methods for displaying content on a low power display of an electronic device, wherein the electronic device supports at least one low power mode setting.

Preferred embodiments of the invention are matter of the dependent claims.

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

The above and other aspects, features, and advantages of certain embodiments of the disclosure will be more apparent from the following description taken in conjunction with the accompanying drawings. The embodiments covered by the claims correspond to <FIG>, <FIG> and <FIG>, while the embodiments of the remaining figures are examples useful for understanding the invention.

The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of various embodiments of the disclosure as defined by the appended claims. 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 disclosure as defined by the appended claims.

The embodiments herein disclose methods and systems for displaying content on an electronic device.

A method disclosed herein includes receiving the content to be displayed on a low power display (LPD) of the electronic device. Further, the method includes determining one or more characteristics of the content. Further, the method performs compatibility check to determine compatibility of at least one portion of the content with the LPD. The compatibility check can be performed based on the one or more characteristics of the content. Depending on the results of the compatibility check, the method includes performing one or more actions on the at least one portion of the content for placing the at least one portion of the content on the LPD. In an embodiment, the method includes displaying the at least one portion on the LPD with low power touch (LPT) enabled.

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

<FIG> illustrate an example electronic device comprising of a low power content integration (LPCI) engine for displaying content on a low power display (LPD) according to embodiments as disclosed herein.

Referring to <FIG>, an example electronic device <NUM> can be, but is not limited to, a mobile phone, a smartphone, tablet, a phablet, a personal digital assistant (PDA), a laptop, a computer, a wearable device, an Internet of Things (IoT) device, a vehicle infotainment system, a medical device, a television (TV) or any other device which supports low power display mode settings.

The electronic device <NUM> includes the LPCI engine <NUM>, a low power module <NUM> and a database <NUM>. The low power module <NUM> includes a low power display <NUM>. Embodiments herein use the terms low power display (LPD), low power mode screen, and always on display (AOD), to refer to a display in the electronic device <NUM>, wherein the display can use low power display mode settings, while being always on.

Referring to <FIG>, the low power module <NUM> of the electronic device <NUM> includes a low power display <NUM> and may include a low power touch <NUM>. Embodiments herein use the terms LPT and always on touch (AOT) interchangeably to enable a user to have minimal interaction with the content displayed on the LPD <NUM>.

Referring to <FIG>, the LPCI engine <NUM> is configured to display the content on the LPD <NUM> of the electronic device <NUM>. In an embodiment, the LPCI engine <NUM> is configured to display the content on the LPD <NUM> with LPT enabled, as illustrated in <FIG>. The content can be, but is not limited to, text, a user control/widget, a document, an application (such as, but not limited to, a navigation application/map, a calendar application, a gaming application, a health and fitness application, a weather application, a remote application for a TV or another appliance, a camera application and so on), an icon, media (an image, a video, an animation and so on), a barcode, a quick response (QR) code and so on.

In order to integrate the content in to the low power mode operation, the LPCI engine <NUM> receives the content and determines characteristics of the content. Based on the characteristics of the content, the LPCI engine <NUM> performs a compatibility check to classify at least one portion of the content which is compatible with the LPD <NUM>. Further, the LPCI engine <NUM> transforms the at least one portion of the content based on the result of the compatibility check. Further, the LPCI engine <NUM> places the at least one portion of the content on the LPD <NUM> when the at least one portion of the content is compatible with the LPD <NUM>. In an embodiment, the LPCI engine <NUM> performs the compatibility check to classify at least one portion of the content which can be compatible with the LPT. Further, the LPCI engine <NUM> performs actions on the determined portions of the content to display the portions of the content on the LPD <NUM> with LPT <NUM> enabled.

In an embodiment, the LPCI engine <NUM> may receive information about policies or recommendations from a cloud server <NUM> for performing the actions on the determined portions of the content. Further, the LPCI engine <NUM> stores the results of the compatibility check and the actions performed on the content in a database <NUM>.

In an embodiment, the LPCI engine <NUM> transfers the content from a normal mode to the LPD <NUM> and from the LPD <NUM> to the normal mode based on an input received from the user. The input received from the user can be, but is not limited to, a voice command, a gesture performed using stylus pen, a touch gesture (tap, click, press, swipe, hold, drag and so on), an input initiated using an edge display supporting an edge display, an input initiated using a bendable display, a camera and AOT gesture, data received from sensors (proximity sensors, Hall effect sensors and so on), an input initiated using augmented reality (AR)/ virtual reality (VR) techniques, and so on.

<FIG> is a block diagram illustrating various units of a LPCI engine for displaying content on the LPD of an electronic device according to embodiments as disclosed herein.

Referring to <FIG>, the LPCI engine <NUM> includes a reception unit <NUM>, a characteristics determination unit <NUM>, a compatibility checking unit <NUM>, an adaption unit <NUM>, a context determination unit <NUM>, a hardware adaption unit <NUM>, a display unit <NUM>, a learning unit <NUM>, a communication interface unit <NUM> and a memory <NUM>.

The reception unit <NUM> is configured to receive the content which needs to be displayed on the LPD <NUM>. The characteristics determination unit <NUM> is configured to analyze the content for determining the characteristics of the content. The characteristics of the content includes display characteristics and touch input characteristics. The display characteristics are histogram information, color depth, luminance, pixel power, and so on with respect to display. The touch input characteristics include control elements such as, but not limited to, buttons, input elements and so on with respect to touch.

The characteristics determination unit <NUM> can be further configured to obtain constraints associated with the LPD <NUM> and the LPT <NUM>. The constraints associated with the LPD <NUM> and the LPT <NUM> can be obtained based on related technology (e.g., active-matrix organic light-emitting diode (AMOLED), liquid crystal display (LCD) and so on). The constraints associated with the LPD <NUM> and the LPT <NUM> can be operational constraints to achieve power and performance key performance indicators (KPIs). The constraints associated with the LPD <NUM> can be, but is not limited to, frame per second (FPS), color depth and so on. The constraints associated with the LPT <NUM> can be, but is not limited to, area of touch recognition, reduction in scanning rate, and so on.

The compatibility checking unit <NUM> is configured to perform compatibility check for determining the portions of the content which are compatible with the LPD <NUM> and can be further configured to perform compatibility check for determining the portions of the content which can be compatible with the LPT <NUM>. The compatibility checking unit <NUM> correlates the display characteristics of the content with the constraints associated with the LPD <NUM> to determine the compatibility of the portions of the content with the LPD <NUM>. Similarly, the compatibility checking unit <NUM> correlates the touch input characteristics of the content with the constraints associated with the LPT <NUM> to determine the compatibility of the portions of the content with the LPT <NUM>. In an embodiment, the compatibility checking unit <NUM> uses a convolutional neural network (CNN) classifier for performing the compatibility check.

In an embodiment, the compatibility checking unit <NUM> may consider requirements such as, but not limited to, on pixel ratio and AOD limitations (i.e., AOD can have limited area of full screen), content brightness and a motion requirement, sound and network (data, global positioning system (GPS)) requirement compatibility, sensor usage and power compatibility, biometric and iris scanner compatibility, hardware interrupt and sleep wake up compatibility, and so on, for performing the compatibility check.

The adaption unit <NUM> can be configured to transform and place the portions of the content on the LPD <NUM> when the portions of the content can be compatible with the LPD <NUM>. In order to place the portions of the content on the LPD <NUM>, the adaption unit <NUM> performs the actions on the portions of the content based on the results of the compatibility check. The adaption unit <NUM> performs the actions on the portions of the content using a self-organizing feature map (SOFM) neural network. The adaption unit <NUM> provides the portions of the content to the display unit <NUM> for displaying on the LPD <NUM> without applying any transformation rules when the portions of content can be determined as compatible with the LPD <NUM>. In an embodiment, the adaption unit <NUM> provides the portions of the content to the display unit <NUM> for displaying on the LPD <NUM> with LPT enabled without applying any transformation rules when the portions of content can be determined as compatible with the LPD and the LPT <NUM>.

The adaption unit <NUM> applies the transformation rules on the portions of the content within a pre-defined threshold to place the portions of the content for display. The transformation rules are applied by determining that the portions of the content requires transformation in order to be compatible with at least one of the LPD <NUM> and the LPT <NUM>. For example, the adaption unit <NUM> adjusts (crops) a portion of the content when the portion of the content includes a barcode, or the like. The adaption unit <NUM> applies a contrast enhancement filter on the portion of the content to increase readability when the total light output of display (in the AOD) is much below an ambient light (e.g., in sunlight). The adaption unit <NUM> applies an invert color filter on the portion of the content when the color distribution is determined as less and majority color is determined as white. The adaption unit <NUM> limits FPS when the portion of the content has more FPS. The adaption unit <NUM> reduces the color bit depth and applies an enhancement filter to shift the portion of the content towards the AOD color gamut. The adaption unit <NUM> enables touch only for a region of interest when the region of interest is determined to be an interactive control. The adaption unit <NUM> enhances the content/text size for better readability when the AOD has less brightness. The adaption unit <NUM> hides or views the portion of the content based on authentication (e.g., a biometric input, a hardware button, and so on). The adaption unit <NUM> decides a content target based on the context or the location of a user. The adaption unit <NUM> applies AOD preferences based on a geographic AOD policy. The adaption unit <NUM> translates a position and transforms a size of the portion of the content based on the AOD constraints and a grip sensor.

The transformation rules vary based on the characteristics of the content and constraints associated with the LPD <NUM> and LPT <NUM>. For example, in order to adapt the navigation application (map) and the game application with the LPD <NUM> and the LPT <NUM>, the adaption unit <NUM> may apply color quantization, perform contrast enhancement based on ambient lighting, restrict FPS, resize the application layout, and enable touch only on individual input controls. In an example, for adapting the music widget with the LPD <NUM> and the LPT <NUM>, the adaption unit <NUM> may apply color quantization, perform contrast enhancement based on ambient lighting, restrict FPS and enable touch only on individual input controls. In an example, for making a health and fitness application and a travel application compatible with the LPD <NUM> and the LPT <NUM>, the adaption unit <NUM> may apply color quantization, perform contrast enhancement based on ambient lighting, and restrict FPS.

In an embodiment, the adaption unit <NUM> can apply transformation rules on the portions of the content based on previous learning.

The adaption unit <NUM> recommends a modified version of the portions of the content for displaying on the LPD <NUM> when the portions of the content/the content can be determined as incompatible with at least one of the LPD <NUM> and the LPT <NUM>. The modified version of the portions of the content can include at least one of alternate portions of the content and the alternate content. The adaption unit <NUM> recommends the modified version of the portions of the content based on factors such as, but not limited to, location, policy derived data analytics, features learned using a machine learning model, and so on. For example, the adaption unit <NUM> may recommend the alternate content when heavy graphic games, video players, social applications are determined to be incompatible with the AOD or the AOT due to high FPS, high interaction, drastic color change, different variety of content, and so on.

The context determination unit <NUM> can be configured to determine a suitable location/place on the LPD <NUM> for placing the portions of the content. The context determination unit <NUM> uses contextual information of the electronic device <NUM> to determine the suitable location for placing the portions of the content. The context determination unit <NUM> obtains the contextual information from sensors such as, but not limited to, grip sensors, light sensors, and so on. The context information can be, but is not limited to, status of grip (e.g., information from the grip sensor), left or right handed operations, orientation status of the electronic device (e.g., portrait, landscape, and so on), ambient lighting condition of the electronic device <NUM> (e.g., information obtained from light sensor,) and so on.

The hardware adaption unit <NUM> can be configured to configure settings for the LPD <NUM> and the LPT <NUM> based on operational requirements of the content. For example, the hardware adaption unit <NUM> configures the settings for the LPD <NUM> and the LPT <NUM> when the operational requirements for the portion of content is found to be less than the constraints associated with the LPD <NUM> and the LPT <NUM>.

The display unit <NUM> can be configured to display the portions of the content on the LPD <NUM> on receiving the portions of the content from the adaption unit <NUM>. In an embodiment, the display unit <NUM> can be configured to display the portions of the content on the LPD <NUM> with LPT enabled. The portions of the content can be at least one of the portions of the content without transformation, the transformed portions of the content, and the alternate portions of the content and the alternate content. In an embodiment, the display unit <NUM> displays the portions of the content based on factors such as, but not limited to, contextual information of the electronic device, the configured settings for at least one of the LPD <NUM> and the LPT <NUM>, and so on.

The learning unit <NUM> can be configured to learn information about the results of the compatibility check and the transformation rules. Thus, on receiving new content, requirement for compatibility check and information about the transformation rules can be determined based on the information learned, which further reduces computation time.

The communication interface unit <NUM> can be configured to communicate with the cloud server <NUM>.

The memory <NUM> can be configured to store the content, results of the compatibility check, transformation rules, configured display/touch settings, and so on. 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 memories (EPROM) or electrically erasable and programmable (EEPROM) memories. 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).

<FIG> shows units of the LPCI engine <NUM>, but it is to be understood that other embodiments are not limited thereon. In other embodiments, the LPCI 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 embodiments herein. One or more units can be combined together to perform same or substantially similar function in the LPCI engine <NUM>.

<FIG> is a flow diagram illustrating a method for displaying content on an LPD of an electronic device according to an embodiment of the disclosure.

Referring to <FIG>, a method 300a for displaying content includes identifying the content to be displayed on the LPD <NUM> at operation <NUM>. The method 300a allows the reception unit <NUM> to receive the content to be displayed on the LPD <NUM>.

At operation <NUM>, the method includes determining the characteristics of the content. The method allows the characteristics determination unit <NUM> to determine the characteristics of the content.

At operation <NUM>, the method includes determining the compatibility of the at least one portion of the content with the LPD <NUM>. The method allows the compatibility checking unit <NUM> to perform the compatibility check for determining the compatibility of the at least one portion of the content with the LPD <NUM>. The compatibility checking unit <NUM> performs the compatibility check using the CNN classifier. The compatibility checking unit <NUM> correlates the characteristics of the content with the constraints associated with the LPD <NUM> to check the compatibility of the portion of the content with the LPD <NUM>. Thus, the portions of the content which can be compatible with the LPD <NUM> can be classified using the CNN classifier.

At operation <NUM>, the method includes transforming and placing the portions of the content on the LPD <NUM> when the portions of the content can be compatible with the LPD <NUM>. The method allows the adaption unit <NUM> to transform and place the portions of the content on the LPD when the portions of the content can be compatible with the LPD <NUM>. Based on the results of the compatibility check, the adaption unit <NUM> performs the actions to place the portions of the content on the LPD <NUM>. The actions can be at least one of recommending the portion of the content without applying the transformation rules, recommending the portion of the content by applying the transformation rules, and recommending the alternate portion of the content/the alternate content for displaying on the LPD <NUM>. The adaption unit <NUM> can recommend the portion of the content without applying the transformation rules in response to determining that the portion of the content adapts with the LPD <NUM> without requiring any changes. The adaption unit <NUM> applies the transformation rules on the portion of the content when the portion of the content requires transformation. The adaption unit <NUM> recommends the alternate portion of the content when the portion of the content can be determined as incompatible with the LPD <NUM>. Thus, the content can be integrated into the low power mode of operations for display and touch environment with an improved power profile.

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

<FIG> is a flow diagram illustrating a method for displaying a compatible portion of content on a LPD according to an embodiment of the disclosure.

Referring to <FIG>, a method 300b includes determining the suitable location on the LPD <NUM> for displaying the portion of the content. The method 300b allows the context determination unit <NUM> to determine the suitable location on the LPD <NUM> for displaying the portion of the content on the LPD <NUM>. The portion of the content can be at least one of an original portion of content (without transformation), the transformed portion of the content, the alternate portion of the content and the alternate content. The suitable location can be determined using the contextual information of the electronic device <NUM>. The contextual information can be obtained from the sensors such as, grip sensors, light sensors and so on.

At operation <NUM>, the method includes configuring the settings for the LPD <NUM> for displaying the portion of the content on the LPD <NUM>. The method allows the hardware adaption unit <NUM> to configure the settings for the LPD <NUM> for displaying the portion of the content on the LPD <NUM>. The portion of the content can be an original portion of content (without transformation), the transformed portion of the content, the alternate portion of the content, and the alternate content. The settings can be configured based on the operational requirements of the content. Thus, the LPD configurations can be optimized for displaying the content on the LPD <NUM>.

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

<FIG> depicts an example electronic device comprising of a LPCI engine for displaying the content on an LPD <NUM> with LPT enabled according to an embodiment of the disclosure.

Referring to <FIG>, the electronic device comprises of a display hardware/panel, an operating system, a windowing system (comprising a display manger, and an input manager), the LPCI engine <NUM>, databases that include e of various preferences (prefs), knowledge bases (KB), a low power display module (comprising a LPD and a LPT), installed widgets/controls, and so on. The electronic device can be connected to the cloud server. The LPCI engine <NUM> performs evaluation and transformation of the content against the LPD and touch capabilities based on the characteristics of the content. Further, the LPCI engine <NUM> performs optimization of the low power hardware (i.e., the LPD and the LPT) against the operational requirements of the content.

<FIG> is an example flow diagram illustrating content integration in a low power mode according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may receive information about the content that needs to be displayed, and the constraints associated with the LPD <NUM> and the LPT <NUM>. The LPCI engine <NUM> further analyzes the content and determines the display characteristics and the touch input characteristics related to the content.

Based on the identified characteristics, the LPCI engine <NUM> checks whether the display characteristics can be compatible with the LPD <NUM> or not. The LPCI engine <NUM> recommends the alternate content by determining that the content cannot be compatible with the LPD <NUM>. If the content can be compatible with the LPD <NUM>, the LPCI engine <NUM> checks for an optimization of the LPD configurations. If the configurations can be optimized, the LPCI engine <NUM> identifies the optimized configuration settings based on the operational requirements of the content. Further, the LPCI engine <NUM> configures the settings for the LPD <NUM>. In addition, the LPCI engine <NUM> transforms the content by applying the set of rules. For example, the LPCI engine <NUM> transforms the content by normalizing brightness, reducing color entropy, and so on.

Similarly, the LPCI engine <NUM> checks whether the touch input characteristics can be compatible with the LPT <NUM>. The LPCI engine <NUM> recommends the alternate content by determining that the content cannot be compatible with the LPT <NUM>. If the content can be compatible with the LPT, the LPCI engine <NUM> checks for an optimization of the LPT configurations. If the configurations can be optimized, the LPCI engine <NUM> identifies the optimized configuration settings for the LPT <NUM> based on the operational requirements of the content. Further, the LPCI engine <NUM> configures the settings for the LPT <NUM>. In addition, the LPCI engine <NUM> transforms the content by applying the set of rules. For example, the LPCI engine <NUM> transforms the content by normalizing brightness, reducing color entropy and so on.

After transforming the content and optimizing the LPD and the LPT configurations, the LPCI engine <NUM> obtains the contextual information of the electronic device. Based on the contextual information, the LPCI engine <NUM> identifies placement on the LPD <NUM> for the content. The LPCI engine <NUM> displays the content according to the identified placement on the LPD <NUM> with LPT enabled.

<FIG>, <FIG> and <FIG> are example diagrams illustrating displaying content on an LPD of an electronic device according to an embodiment of the disclosure.

Referring to <FIG>, an example diagram illustrates display of a navigation application on the LPD <NUM> with LPT enabled. Referring to <FIG>, on receiving the navigation application, the LPCI engine <NUM> determines the characteristics and corresponding values related to the portions of the navigation application. The characteristics can be, but not limited to, FPS, luminance variance, color variance, and so on. The LPCI engine <NUM> uses the characteristics of the navigation application to perform the compatibility check. After determining that a portion of the navigation application can be compatible with the AOD and the AOT, the LPCI engine <NUM> performs transformation of the portion of the navigation application to be compatible with the AOD and the AOT. For example, the LPCI engine <NUM> may change the FPS and the color variance using local features and the SOFM neural network. Further, the LPCI engine <NUM> may use color quantization techniques. In addition, the LPCI engine <NUM> may restrict FPS and transform the portion of the navigation application to be AOD compatible.

Once the portion of the navigation application is transformed, the LPCI engine <NUM> identifies the suitable position on the AOD for the placement of the portion of the navigation application. The suitable position can be identified based on factors such as, but not limited to, size of the navigation application, grip, left or right hand operations, location, importance and so on.

Referring to <FIG>, the LPCI engine <NUM> configures the settings for the AOD and the AOT. Based on the identified position and the configured settings, the LPCI engine <NUM> displays the transformed portion of the navigation application on the AOD with enabled AOT for region of interest (i.e., the marked region as illustrated in <FIG>).

Referring to <FIG> an example diagram illustrates the display of remote control and play music widget on the LPD <NUM>. The LPCI engine <NUM> performs the compatibility check for determining whether the remote control widget and the play music widget is compatible with the AOD or the AOT. The remote control widget requires minimal changes to be compatible with the AOD and the AOT. The play music widget requires moderate changes to be compatible with the AOD and the AOT.

After determining that the remote control widget and the play music widget are made compatible with the AOD and the AOT, the LPCI engine <NUM> performs transformation of the widgets. For example, the LPCI engine <NUM> applies a black-white (BW) filter on the remote control widget and transforms the remote control widget to be AOD compatible. Similarly, the LPCI engine <NUM> applies a BW filter and FPS restrictions on the play music widget and adapts the play music widget with the AOD and the AOT. The LPCI engine <NUM> identifies the suitable position on the AOD for the placement of the remote control widget and the play music widget based on usage, grip, and so on. Further, the LPCI engine <NUM> configures the settings for the AOD and the AOT. Based on the configured settings, the LPCI engine <NUM> displays the remote control and the play music widgets on the AOD with enabled AOT for marked regions (region of interest) as illustrated in <FIG>.

Referring to <FIG>, an example diagram illustrates the display of weather widgets on the LPD <NUM> with LPT enabled for at least one region of interest areas. Embodiments herein enable the LPCI engine <NUM> to perform the compatibility check for determining whether the first and second weather widgets can be compatible or not with the AOD or the AOT.

After determining that the second widget cannot be compatible with the AOD and the AOT, the LPCI engine <NUM> recommends alternate content. For example, after determining that the first weather widget can be compatible with the AOD and the AOT, the LPCI engine <NUM> performs transformation of the first weather widget. The LPCI engine <NUM> applies minimal color filter and FPS restriction on the first weather widget. The LPCI engine <NUM> identifies the suitable position on the AOD for the placement of the weather widget based on a user's grip. Further, the LPCI engine <NUM> configures the settings for the AOD and the AOT. Based on the configured settings and the identified position, the LPCI engine <NUM> displays the weather widget on the AOD with the enabled AOT for control surface (marked region) as illustrated in <FIG>.

<FIG> is an example diagram illustrating context based display of the content on a LPD of an electronic device according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may display a related picture on the AOD on the specific weekday. Further, the LPCI engine <NUM> displays a specific type of animation on the LPD <NUM> when a person calls the user. Similarly, the LPCI engine <NUM> displays a specific type of emoji on the AOD in response to determining that the user is laughing.

<FIG> is an example diagram illustrating context based display of text on a television (TV) according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may display useful information on the TV which supports the AOD. The useful information can be displayed by communicating with the user's mobile device. The LPCI engine <NUM> displays the useful information upon specific events such as, but not limited to, while entering home, while leaving home, and so on. For example, the LPCI engine <NUM> displays the text like "welcome home" while the user is entering the home and "have a nice day" while leaving the home. Also, the LPCI engine <NUM> displays daily updates on the AOD of the TV. The updates may be related to mail received by the user, authentication failures, and so on. Further, the LPCI engine <NUM> recommends the user to switch off the fan and take the car keys by displaying the recommendation text on the AOD of the TV while leaving the home.

<FIG> and <FIG> are example diagrams illustrating displaying private content on a LPD according to various embodiments of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> displays the locked content on the AOD based on the content privacy. The content can be unlocked by performing biometric (face, iris, and so on) authentication. For example, once the iris authentication is successful, the LPCI engine <NUM> unlocks and displays the content on the AOD.

Referring to <FIG>, an example diagram illustrates usage of an AOD button for displaying private content on the AOD. Referring to <FIG>, the AOD button may be provided and the user may be allowed to press the AOD button for receiving the content. The AOD button triggers the authentication process such as an iris scan, a face identification scan, and so on based on user preferences. After successful authentication, the LPCI engine <NUM> displays the private content on the AOD.

<FIG> is an example diagram illustrating display of personalized content on a LPD according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may display the content on the AOD based on a location of the user. If the user is at the office, the LPCI engine <NUM> displays basic information on the AOD such as a clock, a calendar, and so on. If the user is at home, the LPCI engine <NUM> displays the information related to IoT devices present at the home on the AOD. Thus, the status of the IoT devices such as, but not limited to, an air conditioner, bulbs, fans, and so on can be displayed on the LPD based on the location of the user.

<FIG> is an example diagram illustrating display of content on a LPD based on previous learning according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may learn rules used for transformation of the content to display the content on the AOD. On receiving a new content similar to the previous displayed content, the LPCI engine <NUM> applies the rules and the settings from a previous learning to display the new content on the AOD.

<FIG> is an example diagram illustrating communication between a LPCI engine and a cloud server for modeling data, according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may send AOD modeling data (i.e., rules used for transformation) to the cloud server <NUM>. On receiving the AOD modeling data, the cloud server <NUM> provides policies or recommendations based on a geographic region, a people category, and so on as additional inputs to modeling data to the LPCI engine <NUM> of the electronic device <NUM>. For example, the LPCI engine <NUM> may send the rules used for transforming the navigation application to the server. On receiving and analyzing the rules, the cloud server <NUM> may understand the AOD preferences based on weather conditions of the user location and may recommend the LPCI engine <NUM> to enhance the brightness of the navigation application for better visibility.

<FIG> is an example diagram illustrating utilization of a low power core for screen refresh while displaying content on a LPD according to embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may enable the low power core in an AOD mode for refreshing AOD screen while displaying the content on the AOD. Thus, power consumption can be reduced. The low power core performs update functions such as, but not limited to, gathering of sensor data, handling stylus drawings, inferring context, making incremental user interface (UI) updates (e.g., navigation pointer movement), and so on.

Further, the low power core decides whether a full wake up mode or a co-operative mode is required to perform the screen refresh while displaying the content on the AOD. In the full wake up mode, the low power core operates along with an application processor (AP). The low power core performs update operations such as, but not limited to, performing face identification and finger print scanning, supporting game applications, and so on using feedback received from the AP.

<FIG> are example diagrams illustrating utilization of a low power core and an application processor for displaying content on a LPD according to various embodiments of the disclosure.

Referring to <FIG>, an example diagram illustrates the low power core supported content in the AOD mode. In the AOD mode, the LPCI engine <NUM> enables the low power core to perform functions such as, but not limited to, performing a clock update, performing a memo update and calendar schedules, displaying barcodes related to tickets (e.g., movie tickets, flight tickets, and so on), and so on. Also, simple games can be run by enabling the low power core.

Referring to <FIG>, an example diagram illustrates the low power core and the AP supporting content in the co-operative mode. In the co-operative mode, the LPCI engine <NUM> enables the AP to provide feedback to the low power core for performing operations such as, but not limited to, performing weather/navigation update, supporting image capture/selfie mode, supporting audio music play, supporting remotes and so on.

<FIG>, <FIG> and <FIG> are example diagrams illustrating user interactions for displaying content on a LPD according to various embodiments of the disclosure.

Referring to <FIG>, an example diagram illustrates AOD user interaction with a hardware button of the electronic device <NUM>. Embodiments herein allow the user to interact with an AOD hardware button of the electronic device <NUM>. When the user presses the AOD button, the LPCI engine <NUM> can highlight all possible widgets for the user to select and resize. After selecting a widget, the LPCI engine <NUM> checks the compatibility of the selected widget with the AOD and the AOT using the CNN classifier. If the selected widget can be determined as incompatible with the AOD and the AOT, the LPCI engine <NUM> displays an error due to incompatibility message to the user. Otherwise the LPCI engine <NUM> transforms the selected widget using the SOFM neural network and displays the transformed widget on the AOD.

Referring to <FIG>, an example diagram illustrates user control compatibility check performed using a launcher. Embodiments herein allow the user to click and hold desired widget to be transferred to the AOD. Further, the desired widget may be dragged across a launcher screen to an AOD transfer icon. Thereafter, the LPCI engine <NUM> may perform the compatibility check on the desired widget using the CNN classifier. If the desired widget can be determined as incompatible with the AOD and the AOT, the LPCI engine <NUM> displays an error due to incompatibility message to the user. Otherwise the LPCI engine <NUM> transforms the desired widget using the SOFM Neural network and displays the transformed widget on the AOD.

Referring to <FIG>, an example diagram illustrates a transition from the AOD mode to normal mode based on touch gestures. Embodiments herein allow the user to swipe on the AOD screen to go to a normal lock screen mode as illustrated in <FIG>. Based on the swipe gesture, the LPCI engine <NUM> performs the transition of the AOD to the normal lock screen mode.

<FIG> is an example diagram illustrating an AOD overlay UI provided for transforming a portion of content for a LPD according to an embodiment of the disclosure.

Referring to <FIG>, the LPCI engine <NUM> may display an AOD overlay UI button on the content. For example, the AOD overlay UI button may be displayed on navigation application as illustrated in <FIG>. When the user clicks the AOD overlay UI button, the LPCI engine <NUM> may perform the compatibility check and transform a portion of the navigation application. Further, the LPCI engine <NUM> displays the transformed portion of the navigation application on the AOD screen.

<FIG> are example scenarios illustrating transfer of content on a LPD based on touch gestures according to various embodiments of the disclosure.

Referring to <FIG>, an example diagram illustrates transferring a widget to the LPD screen based on tap gestures. Embodiments herein enable any third party widget or control or content to be transferred to AOD via UI sequences or gestures. Embodiments herein enable application of UI transformations on the content to make the content compatible for the LPD <NUM>. The user can perform a pre-determined gesture (for example, a tap gesture) to initiate the widget transfer to the AOD. The widget is transformed as per the AOD constraint and stays displayed.

Referring to <FIG>, an example diagram illustrates transfer of content to the LPD screen based on swipe gestures. For example, the user wants to display a boarding pass with a quick response (QR) code and ticket confirmation messages. The user can select the content on the device. Based on the swipe gesture performed by the user, the full boarding pass with adapted content can be displayed on the AOD.

<FIG>, and <FIG> are example diagrams illustrating compatibility check and transformation rules applied on content for displaying on a LPD according to embodiments as disclosed herein.

Referring to <FIG>, and <FIG>, when receiving the content which needs to be displayed on the AOD with LPT enabled, the LPCI engine <NUM> checks whether the similar content is shared to the AOD earlier. For example, the content can be a map (as illustrated in <FIG>), a score and commentary board (as illustrated in <FIG>) and a gaming application (as illustrated in <FIG>). In response to determining that the content is already shared to the AOD, the LPCI engine <NUM> applies transformation rules on the content from the previous learning and displays the content on the AOD. Otherwise, the LPCI engine <NUM> performs compatibility check and records data with a content type.

For performing the compatibility check, the LPCI engine <NUM> analyzes the AOD and the AOT constraints. For example, in case of displaying the map (as illustrated in <FIG>), the considered AOD constraints may include a display that flickers and turns green due to a smaller on pixel ratio and a low power buck booster. Further, the image may not be visible in bright sunlight due to AOD brightness limitation and lower AOD color depth. The AOT constraints may include slow touch response due to limitation in touch refresh rate in the AOT and lack of map zoom option due to limited touch area in AOT.

Similarly, in case of displaying the score and commentary board and the gaming application (as illustrated in <FIG> and <FIG>), the considered AOD constraints may include a display that flickers and turns green due to smaller on pixel ratio and a low power buck booster. Further, the image may not be visible in bright sunlight due to AOD brightness limitation and lower AOD color depth. In addition, immediate score update may not be possible due to FPS limitations of AOD. The AOT constraints may include slow touch response due to limitation in touch refresh rate in the AOT.

After identifying the characteristics of the content and the AOD and the AOT constraints, the LPCI engine <NUM> compares the display characteristics of the content such as, white pixel density, color variance, SOFM and so on with a pre-defined threshold (related to the AOD constraints). In order to check for the compatibility of the content with the AOT, the LPCI engine <NUM> checks the touch input characteristics of the contents with a threshold defined in an AOT register.

After determining that the content can be compatible with the AOT and AOD, the LPCI engine <NUM> applies the transformation rules on the content based on the AOD and the AOT constraints. For example, in case of displaying the map and the gaming application, the LPCI engine <NUM> may perform actions such as, but not limited to, reducing the color of the map and the gaming application using local features and the SOFM neural network, applying color quantization, performing color enhancement depending on the ambient lighting, restricting FPS, enabling touch on individual input controls, or the like on the map and gaming application. Similarly, in case of displaying the score and commentary board, the LPCI engine <NUM> may perform actions such as, but not limited to, reducing the color of the map application using local features and the SOFM neural network, applying color quantization, performing color enhancement depending on the ambient lighting, restricting FPS or the like on the score and commentary board.

After applying the transformation rules on the content, the LPCI engine <NUM> analyzes performance and power consumption of the low power core used for displaying and updating the content on the AOD. The LPCI engine <NUM> determines factors such as, but not limited to, time taken for an image hash SOFM estimation and compatibility check, updates needed to be performed, and power consumption. For example, in case of displaying the map, the LPCI engine <NUM> determines that the time taken for the image hash SOFM estimation may be less than <NUM> and the time taken for compatibility check may be less than <NUM>. The LPCI engine <NUM> determines that the navigation pointer updates needed to be performed per second. Further, the LPCI engine <NUM> calculates power consumed in AOD may be less than <NUM>. Further based on the determined factors, the average increase in AOD power consumption can be determined as <NUM>~3mA per performance. Thus, based on the determined performance and power consumption, the LPCI engine <NUM> displays the transformed map application on the AOD with AOT enabled for a region of interest (marked region as illustrated in <FIG>).

Similarly in case of displaying the score and commentary board, the LPCI engine <NUM> determines that the time taken for image hash SOFM estimation may be less than <NUM> and the time taken for compatibility check may be less than <NUM>. The LPCI engine <NUM> determines that the commentary sections needed to be updated per second. Further, the LPCI engine <NUM> calculates that the power consumed in AOD may be less than <NUM>. Further based on the determined factors, the average increase in AOD power consumption can be determined as <NUM>~3mA per performance. Thus, based on the determined performance and power consumption, the LPCI engine <NUM> displays the score and commentary board on the AOD with AOT enabled for a region of interest (marked region as illustrated in <FIG>).

Further, in case of displaying the gaming application, the LPCI engine <NUM> determines that the time taken for the image hash SOFM estimation may be less than <NUM> and the time taken for compatibility check may be less than <NUM>. Further, the LPCI engine <NUM> calculates that the power consumed in AOD may be less than <NUM>. Further based on determined factors, the average increase in AOD power consumption can be determined as <NUM>~2mA per performance. Thus, based on the determined performance and power consumption, the LPCI engine <NUM> displays the gaming application on the AOD with AOT enabled for a region of interest (marked region as illustrated in <FIG>).

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

Claim 1:
A method for displaying a widget on an electronic device (<NUM>) that supports at least one low power display mode, the method comprising:
identifying characteristics of a first widget to be displayed on a low power display, LPD, (<NUM>) of the electronic device, wherein the characteristics of the first widget include at least one of histogram information, color depth, luminance, or pixel power of the widget;
determining compatibility of the first widget with the LPD based on the characteristics of the first widget and constraints associated with the LPD;
in response to determining that the first widget is compatible with the LPD, transforming the first widget based on the characteristics of the first widget and the constraints associated with the LPD, and displaying the transformed first widget on the LPD; and
in response to determining that the first widget is not compatible with the LPD,
recommending a second widget that is compatible with the LPD based on characteristics of the second widget and the constraints associated with the LPD, wherein the characteristics of the second widget include at least one of histogram information, color depth, luminance, or pixel power of the widget;
transforming the second widget based on the characteristics of the second widget and the constraints associated with the LPD; and
displaying the second widget on the LPD, wherein the first widget and the second widget are different widgets that provide same type of information; wherein the transforming of the first widget or the second widget comprises at least one of applying frame rate restriction or applying minimal color filter.