Patent Description:
A primary function of mobile devices is the ability to provide communications and text messaging capabilities to workers, especially those working in logistics capacities. Not only is a conventional telephone talk function helpful to employees, but also text messaging is helpful for sending and sharing information to and with the employees. Although the use of mobile devices with text functionality is helpful, there are inefficiencies that can occur if a user has to look at a primary electronic display of the mobile device each time a text message is received. <CIT> discloses a data collection system having a scan engine, an auxiliary visualizer and a host system. <CIT>, on which the preamble of the independent claims is based, discloses a dual screen display for a mobile computing device, which may include scanner functionality.

To improve the functionality of mobile devices used in commercial, industrial, military applications, a mobile device according to the invention includes, besides a primary electronic display, a secondary electronic display and a barcode scanner engine.

In an embodiment, the barcode scanner engine and the secondary electronic display are positioned adjacent to one another on a top surface of the mobile electronic device to make operating the barcode scanner engine easier and support the functionality of messaging access without having to remove the mobile device from a belt holder.

Because the barcode scanner engine uses a laser or other bright illumination device to perform scanning, the mobile device may be configured to prevent simultaneous operation of the barcode scanner engine and secondary display so as to prevent eye injury as a user of the mobile device will look at secondary electronic display repeatedly throughout the day. To further prevent potential eye injury mishap, the mobile device may be configured to turn the secondary electronic display to an OFF state if the primary electronic display is in an ON state. Moreover, the mobile electronic device may be configured to prevent the barcode scanner engine from being in in ON state without the primary electronic display being in an ON state as a primary electronic display may have controls for the barcode reader engine being displayed during setup and operation. These controls and other safety features may reduce or eliminate the ability for a user to have an accidental injury as a result of the barcode scanner engine illuminating a laser beam into an eye of the user of the mobile electronic device.

One embodiment of a mobile electronic device includes a primary electronic display positioned on a front face of the mobile electronic device, a machine-readable scanner engine and in particular a barcode scanner engine including a laser or other bright illumination device and an optical sensor configured to capture light reflected from a machine-readable indicia to be used in reading the machine-readable indicia, and a secondary electronic display, the machine-readable scanner engine, in particular barcode scanner engine, and the secondary electronic display being positioned adjacent to one another on a top face of the mobile electronic device. The mobile electronic device is configured to prevent simultaneous operation of the machine-readable scanner engine and secondary display.

The machine-readable scanner engine and secondary electronic display may be in communication with a processor of the mobile device, the processor being configured to execute a display control module to control operation of the secondary electronic display, the display control module causing the secondary electronic display to be in an OFF state when the primary electronic display is in an unlocked or ON state.

Additionally, the display control module may be configured to enable the secondary electronic display to be in an ON state when the primary electronic display is in a locked or OFF state.

Additionally or alternatively, the display control module may be further configured to:.

Additionally or alternatively the display control module may be further configured to queue messages for display on the secondary electronic display.

The display control module may be further configured to enable a user to scroll through the messages in response to the user activating one or more user-interface elements of the mobile electronic device.

The display control module may be configured to detect a condition from an onboard sensor of the mobile electric device, and cause the secondary electronic display to be enabled in response to detecting the condition. Any of the above further features may apply also in this case.

Additionally or alternatively to any of the above further features, the device may further comprise a scanner engine control module configured to control operation of the machine-readable scanner engine, the scanner engine control module causing the machine-readable scanner engine to be an OFF state when the primary electronic display is not in an ON state.

Additionally or alternatively to any of the above further features the device may further comprise a housing configured to support the primary electronic display to form at least a portion of a front face and the machine-readable reader engine and secondary electronic display to form at least a portion of a top face of the mobile electronic device. The housing may be integrated as part of the mobile electronic device or it may be a temporary housing that is configured to be removable from the mobile electronic device.

Additionally or alternatively to any of the above further features the secondary electronic display may be touch sensitive, and in response to a user touching the secondary electronic display, the machine-readable scanner engine may be triggered to perform a machine-readable indicia scan.

One embodiment of a method, in particular a process for operation of a mobile device, includes operating a machine-readable scanner engine and in particular a barcode scanner engine of a mobile electronic device that includes a primary electronic display positioned on a front face of the mobile device. The machine-readable scanner engine includes a laser or other bright illumination device and an optical sensor configured to capture light reflected from a machine-readable indicia to be used in reading the machine-readable indicia. A secondary electronic display is operated, the machine-readable scanner engine, in particular barcode scanner engine, and the secondary electronic display being positioned adjacent to one another on a top face of the mobile electronic device. Simultaneous operation of the machine-readable indicia scanner engine and the secondary electronic display is prevented.

Another method or process lying outside the scope of the claimed invention may include operating a secondary electronic display of a mobile device that includes a machine-readable indicia scanner engine and a primary electronic display. A machine-readable indicia scanner engine may be operated, in particular by the mobile device. In response to the machine-readable indicia scanner engine being transitioned to an ON state, the secondary electronic display may be caused to be in an OFF state.

Illustrative embodiments of the present invention are described in detail below with reference to the attached drawing figures, which are incorporated by reference herein and wherein:.

With regard to <FIG>, an illustration of an illustrative mobile electronic device <NUM> including a main or primary display <NUM> is shown. The mobile electric device <NUM> may further include a housing <NUM> in which the primary electronic display <NUM> is positioned along with electronics (not shown) for use in operating the mobile electronic device <NUM> to perform conventional functions of mobile electronic devices and support advanced features, such as those shown in <FIG>.

With regard to <FIG>, an illustration of a top view of the mobile electronic device <NUM> is shown to include a secondary display <NUM> positioned adjacent to a barcode or machine-readable indicia scanner engine or scan engine <NUM> that are both affixed to a top portion of the housing <NUM>. The secondary display <NUM> may be an e-ink or other low-power consumption electronic display device. The secondary display <NUM> is shown to be displaying text <NUM>, such as a text message from a messaging app or other notification message. It should be understood that in an alternative embodiment other information and data format, including graphics, images, and/or any other content capable of being displayed on the secondary electronic display may be performed. The barcode scanner engine <NUM> may include an optical sensor <NUM> configured to sense optical data reflected from a machine-readable indicia, such as a barcode, QR code, alphanumeric text, and/or any other machine-readable indicia format.

The scanner engine <NUM> may further include a laser element (e.g., laser diode) <NUM> for use in scanning a machine-readable indicia, as understood in the art. The use of a laser element <NUM> can be problematic for users as inadvertent illumination of an eye by the laser element <NUM> may cause eye damage. For typical uses of the mobile electronic device <NUM>, users will naturally look at the secondary display <NUM> for information being displayed thereon. As a result, additional safety precautions and processes to avoid a user having a laser beam from the laser element <NUM> enter a user's eye directly is to be taken, as further described hereinbelow. In an embodiment, the mobile electronic device <NUM> may be configured to communicate and display a preview of background app notifications on the secondary display <NUM>, which enables the user to see the notifications (i) without having to remove the mobile electronic device <NUM> from his or her belt holster or pocket, and (ii) without having to be concerned that the laser element <NUM> could be mistakenly left in an ON state.

Moreover, because the scanner engine <NUM> is disposed adjacent to the second electronic display <NUM>, particular safety measures as to when scanner engine <NUM> is turned ON (i.e., in an ON state) versus when the secondary electronic display <NUM> is turned ON is accounted for to avoid risking eye injury to a user, as further described hereinbelow. Although not shown, it is possible to include a mechanical component (e.g., slide cover) that allows for one or the other of the secondary electronic display <NUM> or scanner engine <NUM> to be physically covered so as to prevent a user from viewing both of the devices simultaneously. In an embodiment, the cover could be spring-loaded and defaults to cover the barcode scanner engine <NUM>. An electro-mechanical device may additionally or alternatively be controllable by the mobile electronic device <NUM> such that the barcode scanner engine <NUM> is uncovered when selected to be used by the user. Still yet, if the cover is physically moved to uncover the barcode scanner engine <NUM>, the mobile electronic device <NUM> may automatically turn ON the primary display <NUM> to enable the user to perform scanning of machine-readable indicia.

With regard to <FIG>, a left side view of the mobile electronic device <NUM> is shown to include the housing <NUM>, battery pack <NUM>, and user-interface buttons 116a and 116b (collectively <NUM>), in this case volume up and down buttons, that the user may operate (i) in a conventional mobile electronic device mode to adjust volume, but, (i) in a mode when the secondary electronic display <NUM> is being utilized, to enable the user to scroll through successive available messages to be displayed on the secondary electronic display <NUM>. In an embodiment, pressing the user-interface button (e.g., volume up button) 116a may enable the user to scroll forward through the messages in an ascending, time-sequential order, and pressing the user-interface button (e.g., volume down button) 116b may enable the user to scroll through the messages in a descending, time-sequential order. The use of these particular user-interface buttons is illustrative and may have alternative control functionality with regard to the secondary electronic display <NUM>, as well. For example, the user-interface button(s) <NUM> may turn ON a light, adjust brightness, change color, extend duration of time that a message is displayed or a light of the secondary electronic display <NUM> remains ON, and so on. The user-interface buttons <NUM> may also provide for certain control over the scan engine <NUM>, such as enable and disable, time of scan before automatic transition to an OFF state, and so on. Further description of processes for the use of the user-interface elements is provided herein with regard to <FIG> and <FIG>.

Setup of parameters of the secondary electronic display <NUM> and/or scan engine <NUM> may be performed in conjunction with the secondary electronic display <NUM> or primary electronic display <NUM>. However, the setup of the functionality of the secondary electronic display <NUM> and/or scan engine <NUM> may be easier or more intuitive while looking at the secondary electronic display <NUM>. In the event that the user is performing a setup of the laser element via the secondary electronic display <NUM>, the laser element <NUM> is to be maintained in an OFF state. If operational parameters of the laser element <NUM> are being set up and would benefit from the laser element <NUM> being turned ON, then such a setup operation is to be performed on the primary electronic display <NUM>.

With regard to <FIG>, a right side view of the mobile electronic device <NUM> is shown to include the housing <NUM>. A power button <NUM> of the mobile electronic device <NUM> may be used for swapping operational modes of the secondary electronic display <NUM> (e.g., enable/disable, display of all app messages or just messages related to the user of the scanner engine <NUM>, etc.) or sorting through messages displayed on the secondary electronic display <NUM>. It should be understood that any number of user-controlled elements, such as the user-interface elements <NUM>, power button <NUM>, or otherwise, may be utilized to control mode an operation of the secondary electronic display <NUM> and/or scan engine <NUM>. For example, the user may double press the power button <NUM> to cause the scan engine <NUM> to turn ON and perform a machine-readable indicia scan. Alternatively, pressing and holding one of the user-interface elements <NUM> for a certain time period (e.g., <NUM> seconds) may cause the scan engine <NUM> to turn ON and remain ON while the user holds down the button.

With regard to <FIG>, an illustration of a rear view of the mobile electronic device <NUM> is shown to include a rear of the housing <NUM>. The housing <NUM> may be integrated as part of the mobile electronic device <NUM>. Alternatively, the housing <NUM> may be a temporary housing that is configured to be removable from the mobile electronic device <NUM>. In the event of the housing <NUM> being removable, an electrical port (not shown) that interfaces with a standard electrical port of the mobile electronic device <NUM> may be utilized. Otherwise, the secondary electronic display <NUM> and scanner engine <NUM> may be integrated into a communications bus of the mobile electronic device <NUM>, as understood in the art.

With regard to <FIG>, a block diagram of an illustrative mobile electronic device <NUM> including a processor <NUM>, a primary electronic display or primary display <NUM>, a secondary electronic display or secondary display <NUM>, and a barcode or machine-readable indicia scanner engine <NUM> is shown. The processor <NUM> may include one or more processing device(s) including one or more processing core(s) that perform(s) logical, mathematical, and/or any other computing operations. The processor <NUM> may include a general processing unit (GPU), digital signal processor (DPS), image processor, or other processing device. The processor <NUM> may be formed of any technology, such as an ASIC, EEPROM, and/or any other technology. Memory for storing software and/or data may also be included on the mobile electronic device, as understood in the art, and be usable for performing the machine-readable indicia scanning by the barcode scanner engine <NUM> and be used for operating the secondary display <NUM>. The barcode scanner engine <NUM> may be configured with a laser source (not shown) configured to output a laser beam that is used for scanning machine-readable indicia (e.g., barcodes, QR codes, or any other markings capable of being read by a device). The barcode scanner engine <NUM> may further be configured with an optical sensor configured to receive reflections of the laser beam to capture the machine-readable indicia. The optical sensor may be a light sensor and/or image sensor. Because of the inherent danger of laser beams to human eyes, the user is to avoid having the laser beam be applied directly to her or her eye, such that certain safety control mechanisms are to be employed by the software <NUM>.

The processor <NUM> is configured to execute software <NUM> that is configured (i) to manage conventional functionality of a mobile electronic device, and (ii) to perform functions specifically related to controlling and communicating data with the secondary display <NUM> and barcode scanner engine <NUM>. The conventional functionality may include voice communications, data communications, and any other functionality possible by a mobile electronic device, such as a smart phone, that may include various electronics, such as global positioning system (GPS) electronics, camera, fingerprint scanner, motion sensing electronics, and so on.

The software <NUM> is shown to include a scanner engine control module <NUM>, displays ON/OFF control module <NUM>, first display communications or control module <NUM>, and second display communications or control module <NUM>. In an embodiment, the modules <NUM> and <NUM> may be considered to be a display control module. The scanner engine control module <NUM> may be configured to control operation of the barcode scanner engine <NUM>. In operation, the scanner engine control module <NUM> may be configured to control the barcode scanner engine <NUM> to be enabled/disabled, ON/OFF, and scan a machine-readable indicia. The scanner engine control module <NUM> may act in coordination with other electronic devices, such as the primary display <NUM> and primary display <NUM>, as further described herein. The displays ON/OFF control module <NUM> may be configured to coordinate when the primary display <NUM> and secondary display <NUM> are turned ON/OFF. As previously described, the secondary display <NUM> and barcode scanner engine <NUM> are to be mutually exclusively turned ON, while the primary display <NUM> and barcode scanner engine <NUM> are to be simultaneously activate, as further described herein.

The first display communications module <NUM> may include software drivers that are used to communicate data 220a to the primary display <NUM> for displaying text, graphics, windows, images, and/or any other information for conventional software (e.g., mobile apps), and data 220b to the secondary display <NUM> for displaying textual information, such as text alerts and notifications for conventional software and as related to the barcode scanner engine <NUM>. In general, the data 220b includes standard notifications that are or would otherwise be sent to the primary display <NUM> for display thereon via data 220a. As provided herein, the secondary display <NUM> may operate while the primary display <NUM> is not in an ON state, thereby allowing a user to see the notifications on the secondary display <NUM>. By having the notifications displayed on the secondary display <NUM> as opposed to the primary display <NUM>, the mobile electronic device <NUM> may save battery power and the user may reduce or eliminate having to remove the mobile electronic device <NUM> from his or her belt holder or pocket, for example.

The processor <NUM> may be in electrical communication with each of the primary display <NUM>, secondary display <NUM>, and barcode scanner engine <NUM>. As shown, the processor <NUM> may communicate control signals and/or data 220a, 220b, and 220c (collectively <NUM>) to and from the primary display <NUM>, secondary display <NUM>, and barcode scanner engine <NUM>. In particular, control signals <NUM>, <NUM>, and <NUM> may be communicated to each of the primary display <NUM>, secondary display <NUM>, and barcode scanner engine <NUM> to turn ON/OFF each of the respective devices in accordance with the algorithms described hereinbelow.

In general, since the scanning feature is to be avoided when the secondary display <NUM> is active, (i) the secondary display <NUM> is to be switched ON if the following condition is satisfied: (Condition <NUM>) the keyboard is locked, and (ii) the secondary display <NUM> is to be switched OFF if the following condition is satisfied: (Condition <NUM>) the keyboard is unlocked. The two conditions shall be verified using a software object or module, which in the Android operating system is the KeyguardManager. The KeyguardManager is generally responsible for handling locking/unlocking of the keyboard with a PIN, pattern, face, password lock or default lock (e.g., slide to unlock), and so on. Depending on the supported device inputs, the KeyguardManager handles a lock screen, buttons or keyboard, if any, and other device inputs. The KeyguardManager may also be configured to operate in conjunction with the secondary display <NUM>.

More particularly, the processor <NUM> may be configured by the software <NUM> to communicate text alerts and notifications of one or more apps, including to the secondary display <NUM>. The secondary display may be disabled by default, and every time the secondary display <NUM> is enabled, a disclaimer pop-up shall be accepted by the user so that the user is alerted to not mistakenly look at the secondary display <NUM> when using the barcode scanner engine <NUM> and that both will not be simultaneously turned ON.

For the purposes of controlling the secondary display, the KeyguardManager may be configured to perform the following functions:.

When the secondary display <NUM> is switched ON to display content or the secondary display <NUM> is already switched ON, but the content is to be updated, the secondary display <NUM> may display fixed content, cutting or not displaying part of text if the text does not fully fit within the secondary display <NUM> with rolling disabled until a configurable timeout or fixed text timeout expires. After the fixed text timeout is expired, the displayed text may start rolling in order to show to the user the whole text on the secondary display <NUM> until a configurable timeout or rolling text timeout expires. After the rolling text timeout is expired, the processor <NUM> may be allowed to transition into a suspend mode. With the processor <NUM> in the suspend mode, the rolling feature disabling may be accepted and replaced with fixed text. When the processor <NUM> transitions into the suspend mode, the secondary display <NUM> may remained turned ON until a configurable timeout or switch off timeout expires. After the switch off timeout is expired, the secondary display <NUM> may be switched OFF.

A number of different embodiments for controlling operation of the secondary display <NUM> and barcode scanner engine <NUM> may be provided to enable a user to have both safety and functionality with the mobile electronic device <NUM>.

An illustrative first embodiment includes the secondary display <NUM> being disabled by default and enabled by a user explicitly enabling the secondary display <NUM>, when needed. Once enabled, the secondary display <NUM> may operate, as follows. The secondary display may be switched ON (i.e., transitioned to an ON state) when the primary display <NUM> is in a locked state, as controlled by an operating system screen lock mechanism, or switched OFF in response to the primary display <NUM> being transitioned to an unlocked state. In such conditions, in response to the operating system receiving a new notification, the secondary display <NUM> may receive a message or notification, and the notification may be displayed and persist for a configurable amount of time (e.g., <NUM> seconds). When the primary display <NUM> is switched ON and unlocked by the user, the secondary display <NUM> stops operating and is switched OFF. <FIG> provides an illustrative detailed process flow of the first embodiment.

An illustrative second embodiment includes the secondary display <NUM> being enabled by default, where the secondary display <NUM> may work, as follows. The secondary display <NUM> may be switched ON when the primary display <NUM> is in a locked state, through an operating system screen lock mechanism, or switched OFF in response to the primary display <NUM> being transitioned to an unlocked state. In such conditions, in response to the operating system receiving a new notification, the secondary display <NUM> may be updated accordingly and the notification may be displayed thereon for a configurable amount of time. When the primary display <NUM> is switched ON and unlocked by the user, the secondary display <NUM> stops operating and will be switched OFF.

An illustrative third embodiment includes secondary display <NUM> being enabled when sensors (e.g., accelerometer, light sensor, etc.) on the mobile electronic display <NUM> detecting a specific condition (e.g., vertical position and dark environment, such as being in a pocket). In such conditions, in response to the operating system receiving a new notification, the secondary display <NUM> may be updated accordingly and the notification may be displayed thereon. If the user does not want to unlock the primary display <NUM> (e.g., the mobile electronic device <NUM> remains in his or her pocket), the notification is to be displayed on the secondary electronic display <NUM> for a configurable amount of time. When the device <NUM> is handled or moved by the user (i.e., the above conditions are no longer satisfied), the secondary display <NUM> stops operating and disabled or switched OFF.

With regard to <FIG>, an illustration of an illustrative mobile device assembly <NUM> inclusive of a mobile device <NUM> including a first display <NUM>, such as a liquid crystal monitor (LCM), and second display <NUM>, such as a liquid crystal monitor, is shown. The first LCM <NUM> may be configured to display multimedia <NUM>, as understood in the art. In displaying the multimedia <NUM> on the LCM <NUM>, commands and data may be communicated to the LCM via a mini display port (MDP) <NUM> and/or mobile industry processor interface/digital serial interface (MIPI/DSI) <NUM>. In an embodiment, the second LCM <NUM> may be in communication with the mobile device <NUM> via a wired or wireless communications path <NUM> (e.g., serial peripheral interface (SPI)). It should be understood that a wide range of interface types and communications protocols may be utilized to enable communication of commands and data to either or both of the first and second LCMs <NUM> and <NUM>.

With regard to <FIG>, an illustration of an illustrative process <NUM> for controlling operation of a mobile electronic device including multiple displays and a barcode scanner engine, such as provided in <FIG>, is shown. The process <NUM> may start at step <NUM>, where a secondary display setting may be set to an ON state. By setting the secondary display to an ON state, messages and notifications may be routed to and displayed on the secondary display as opposed to or in addition to the primary display. At step <NUM>, the mobile electronic device may be set to a suspended/sleep mode with the primary display being set to an OFF state, scan engine being set to an OFF state, and secondary display being in an ON/idle state. At step <NUM>, a determination may be made as to whether a message or notification has been received by the mobile electronic device. The notification may be any number of notifications, such as a text message, alert from a mobile app, alarm, or otherwise.

If a determination is made at step <NUM> that a notification has not been received, then the process may return to step <NUM>. Otherwise, if a notification has been received, then the process may continue to step <NUM>, where the device remains in suspend/sleep mode, and the primary display remains in an OFF state, the scan engine remains in an OFF state, and the secondary display, which is in an ON state, outputs text associated with the received notification. The text ON state may remain active for a configurable amount of time, and at step <NUM>, a determination may be made as to whether a timeout has expired. If the timeout has expired, then the process may return to step <NUM>. Otherwise, if the timeout has not expired, then the process continues to step <NUM>, where a determination as to whether the user has pressed an ON/OFF key may be determined. If the user has not pressed an ON/OFF key, then the process may return to step <NUM>. Otherwise, the process continues to step <NUM>, where the device remains in a locked state such that the primary display is in a lock screen, the scan engine is in an OFF state, and the secondary display is in an ON state - the state of the text being displayed or not displayed may not be a factor.

At step <NUM>, a determination as to whether a timeout has occurred may be made. If a timeout has not been made, then the process continues to step <NUM>, where a determination is made as to whether the user has unlocked the primary display. If the user has not unlocked the primary display, then the process <NUM> returns to step <NUM>. If the user has unlocked the primary display at step <NUM>, then the process continues to step <NUM>, where the mobile electronic device is unlocked, with the main display being turned to an ON state, the scan engine being set to an ON state, and the secondary display being turned to an OFF state. If, at step <NUM>, a timeout has expired, then the process <NUM> returns to step <NUM>.

With regard to <FIG>, an illustration of an illustrative process for a mobile device to control a secondary display and presenting text on the secondary display, as shown in <FIG>. The process <NUM> may start at step <NUM>, where the secondary display is configured to receive and display content. At step <NUM>, a fixed text timeout countdown is initiated, where the fixed text timeout may be a short time duration, such as <NUM> or <NUM> seconds. At step <NUM>, the text may be displayed, and a determination at step <NUM> may be made as to whether the fixed text timeout has expired. If the fixed text timeout has not timed out, the process <NUM> returns the step <NUM> to continue displaying the fixed text. Otherwise, if the fixed text timeout has expired, the process <NUM> may continue at step <NUM>, where a rolling text timeout countdown may start. The rolling text may be displayed at step <NUM>. Rolling text may include scrolling text to the left to show more text than may be displayed on a single line of the secondary display.

The process <NUM> may continue at step <NUM>, where a determination may be made as to whether the rolling text timeout has expired. If not, then the process returns to step <NUM> to continue rolling the text. Otherwise, the process continues at step <NUM>, where the mobile device processor may be set in a suspend mode. At step <NUM>, a switch off timeout countdown may start that, when expired, causes the secondary display to switch OFF. At step <NUM>, the same or different fixed text may be displayed. At step <NUM>, a determination may be made as to whether the switch off timeout has expired. If not, then the fixed text may continue being displayed at step <NUM>. Alternatively, if the switch off timeout has expired, then the process may continue at step <NUM>, where the secondary display may be switched OFF. The secondary display is turned OFF at step <NUM>.

With regard to <FIG>, an illustrative secondary display <NUM> of a mobile device on which a caller ID <NUM> and caller telephone number <NUM> extracted from a call is displayed is shown. In response to an incoming call, a caller ID module may be configured to extract or otherwise access caller ID <NUM> and telephone number data <NUM> for display on the secondary display <NUM>. In an embodiment, during an incoming call, the caller ID <NUM> may be displayed on a first line <NUM> and the phone number <NUM> may be displayed on a second line <NUM> of the secondary display <NUM>. The caller ID and caller telephone number may be displayed as fixed text initially, then as rolling text, and finally as fixed text, as previously described with regard to <FIG>.

More specifically, the secondary display <NUM> may show incoming call information, if (condition <NUM> -- keyboard locked) while the device is receiving an incoming call. The secondary display <NUM> and/or software being executed by the processor controlling the secondary display <NUM> may remove the incoming call information from being displayed on the secondary display <NUM> when the mobile device stops ringing because the incoming call is finished, which means that the incoming call is refused or is taken by the user. In an embodiment, the lifetime of information related to the incoming call shown on the secondary display <NUM> may be the same information that is or would otherwise be shown on the primary display of the mobile electronic device.

The incoming call notifications have higher priority than the other information being displayed or to be displayed on the secondary display <NUM>. Therefore, when the mobile electronic device receives an incoming call, the secondary display <NUM> is to show the incoming call information independently from information that was displayed prior to receiving the incoming call. When the incoming call information is removed, the secondary display <NUM> or software controlling the secondary display <NUM> is to restore a previous state of information that had been displayed. Therefore, if the secondary display <NUM> was showing some content before the incoming call was received, the secondary display <NUM> is to restore the previously shown content. If the secondary display <NUM> was switched OFF before the incoming call was received, the secondary display <NUM> is to be switched OFF again when the incoming call information is removed. In order to restore content that was being displayed prior to receiving an incoming call, when an incoming call is received, the information currently being displayed is to be stored before updating the secondary display <NUM> with the incoming call information.

With regard to <FIG>, a standard preview pop-up of the Android notifications system may be used for displaying pop-up information on a secondary display <NUM>. As shown, a title <NUM> may be displayed on a first line <NUM> and notification text <NUM> may be displayed on the second line <NUM> of the secondary display <NUM>. Also displayed on the first line <NUM> is a notification number <NUM>, in this case notification <NUM>-of-<NUM> or <NUM>/<NUM>. In an embodiment, the notifications may be displayed on both the primary display (not shown) and secondary display <NUM> of the mobile electronic device. In the event that the user reads and deletes the notification on the primary display, the notification may be removed from being displayed or available for display on the secondary display <NUM>. It should be understood that the secondary display and process used for displaying notifications and caller IDs may be performed on other operating systems using the same or similar processes and controls.

With regard to <FIG>, a flow diagram <NUM> of an illustrative process for displaying a notification message on the secondary display is shown. The secondary display may be in an OFF state at step <NUM>. At step <NUM>, a determination may be made as to whether the keyboard is locked (condition <NUM>). If not, the process <NUM> returns to step <NUM>. Otherwise, the process <NUM> continues to step <NUM>, where a determination may be made as to whether a new notification is received. If a determination that a new notification, which is not a telephone call, is being received, then the process <NUM> may continue at step <NUM>, where the secondary display may be switched ON and new notification may be displayed thereon. The secondary display thereafter handles the content to be displayed at step <NUM>. Thereafter, the process <NUM> returns to step <NUM>.

At step <NUM>, when the secondary display is switched OFF and a new notification is not determined to be received at step <NUM>, a determination may be made as to whether a user element (e.g., volume up or down button) is pressed. If no user interface element is being pressed, then the process may return to step <NUM>. Otherwise, if a user interface element is determined to be pressed at step <NUM>, the process may continue to step <NUM>, where a determination may be made as to whether a volume control feature to change the audio stream volumes, such as music stream, ring stream, notification stream, alarm stream, etc. If an audio stream volume is changed, then the process may continue to step <NUM> where the secondary display is switched ON and a defined alert message is shown. The process <NUM> may continue to step <NUM>. If it is determined at step <NUM> that no audio stream volume is changed, then a determination may be made at step <NUM> to determine if any notifications exist. If so, then the process may continue to step <NUM>, where if the secondary display is turned OFF (condition <NUM>), then the secondary display may be switched ON and a last received notification may be displayed. The process <NUM> may continue at step <NUM>. If, at step <NUM>, no notifications exist, then the process <NUM> may continue to step <NUM>.

As an example, the user may be listening music with an app in the background with the mobile electronic device being locked and the primary display switched off. At the same time, the user may want to read some previously received notifications on the secondary display. To do so, the user may press a user interface element, such as the volume up button or volume down button, to switch the secondary display to an ON state. In this case, the volume up/down button pressure for switching the secondary display to an ON state may also change the music stream audio while the user is listening music. This side effect may be annoying for users, so to help avoid the side effect of the volume changing, the user may be discouraged to control the secondary display while volume buttons are able to change some audio stream volumes. Other user interface button(s) may be utilized to avoid this situation, including configuring the software to respond to the first volume button press, but not an opposite volume button press. Finally, in this condition, the previous defined text message shall be shown on the secondary display to explain to the user why the secondary display is not responding to the user commands and to avoid that response to the user elements could be perceived as a device bug by the user.

With regard to <FIG>, a flow diagram of an illustrative process for managing a secondary electronic display when receiving notifications is shown. The process <NUM> may start at step <NUM>, where a secondary display may be in an ON state. At step <NUM>, a determination may be made as to whether the keyboard is locked. If not, then the process <NUM> continues at step <NUM>, where the secondary display may be turned to an OFF state after a configurable time period, as previously described. Otherwise, if the keyboard is determined to be in a locked state while the secondary display in an ON state, the process continues at step <NUM>, where a determination is made as to whether a new notification is received. If a new notification is received while the keyboard is locked and the secondary display is in an ON state, then the process <NUM> continues to step <NUM>, where content of the new notification may be used to update the content being displayed by the secondary display. The process <NUM> may continue at step <NUM>, where the secondary display handles the content to be displayed. Thereafter, as previously described, the secondary display may be transitioned to an OFF state after a time period at step <NUM>. If, at step <NUM>, a new notification has not been received, then the process may continue at step <NUM>, where a determination may be made as to whether a volume down button (or other button) has been pressed. If so, then the process may continue at step <NUM>, where content being displayed on the secondary display may be updated with the previous notification (i.e., to display an historical message). The process may continue at step <NUM>, where the secondary display handles the content to be displayed. If a determination is made at step <NUM> that the volume down button has not been pressed, then a determination may be made as to whether a volume up button was pressed at step <NUM>. If so, then the process <NUM> may continue at step <NUM>, where the secondary display content is updated with the text notification. The process may continue thereafter at step <NUM>. If, however, it is determined at step <NUM> that the volume up button was not pressed, then the process returns to step <NUM>.

With regard to the secondary display, each application running in the mobile device may be configured by the user as enabled or disabled. Notifications received from enabled applications may be displayed, while notifications received from applications that have been disabled may not be displayed.

The maximum length of the notifications number field may be <NUM> characters, so that the maximum number of unread notification will be <NUM>. When the maximum number of unread notifications is exceeded, the number of unread notification may be displayed with the symbol "+". The following examples show how to manage the possible cases:.

The secondary display may not group standard notifications as the primary display groups notifications. Operating system standard notifications may be shown as a single notification on the secondary display, even if the displayed notifications are related to the same App and are grouped on primary display.

With regard to <FIG>, a flow diagram of an illustrative process <NUM> for operating a mobile device including a secondary electronic display and barcode scanner engine is shown. The process <NUM> may start at step <NUM>, where a barcode scanner engine of a mobile electronic device that includes a primary electronic display may be operated. A secondary electronic display positioned adjacent to the barcode scanner engine may be operated at step <NUM>. At step <NUM>, in response to the primary electronic display being unlocked or transitioned to an ON state, the secondary electronic display may be caused to be in an OFF state because the barcode scanner engine may be active only when the primary display is in the ON state.

In response to the primary electronic display being locked or transitioned to an OFF state, the machine-readable indicia scanner engine may be caused to being in an OFF state.

The process may further enable the secondary electronic display to be in an ON state when the primary electronic display is in a locked or an OFF state.

In an embodiment, messages may be received from one or more applications being executed by the mobile electric device; and be displayed on the secondary electronic display.

Additionally or alternatively, messages may be queued for display on the secondary electronic display.

A user may be enabled to scroll through the messages in response to the user activating one or more user-interface elements of the mobile electronic device.

Additionally or alternatively, the process may further include automatically turning OFF a displayed message after a set period of time.

In the same or another embodiment, a condition may be detected from an onboard sensor of the mobile electric device, and the secondary electronic display may be caused to be enabled in response to detecting the condition.

In any embodiment, controlling operation of the barcode scanner engine may include causing the barcode scanner engine to be an OFF state when the primary electronic display is not in an ON or unlocked state.

In response to a user touching the secondary electronic display, the barcode scanner engine may be triggered to perform a barcode scan.

Another embodiment of a process may include operating a secondary electronic display of a mobile device that includes a machine-readable indicia scanner engine and a primary electronic display. A machine-readable indicia scanner engine may be operated by the mobile device. In response to the machine-readable indicia scanner engine being transitioned to an ON state, the secondary electronic display may be caused to be in an OFF state.

As will be appreciated by one of skill in the art the steps in the foregoing embodiments may be performed in any order. Words such as "then," "next," etc. are not intended to limit the order of the steps; these words are simply used to guide the reader through the description of the methods. Although process flow diagrams may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination may correspond to a return of the function to the calling function or the main function.

Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the principles of the present invention.

Embodiments implemented in computer software may be implemented in software, firmware, middleware, microcode, hardware description languages, or any combination thereof. A code segment or machine-executable instructions may represent a procedure, a function, a subprogram, a program, a routine, a subroutine, a module, a software package, a class, or any combination of instructions, data structures, or program statements. A code segment may be coupled to another code segment or a hardware circuit by passing and/or receiving information, data, arguments, parameters, or memory contents. Information, arguments, parameters, data, etc. may be passed, forwarded, or transmitted via any suitable means including memory sharing, message passing, token passing, network transmission, etc..

The actual software code or specialized control hardware used to implement these systems and methods is not limiting of the invention. Thus, the operation and behavior of the systems and methods were described without reference to the specific software code being understood that software and control hardware can be designed to implement the systems and methods based on the description herein.

When implemented in software, the functions may be stored as one or more instructions or code on a non-transitory computer-readable or processor-readable storage medium. The steps of a method or algorithm disclosed herein may be embodied in a processor-executable software module which may reside on a computer-readable or processor-readable storage medium. A non-transitory computer-readable or processor-readable media includes both computer storage media and tangible storage media that facilitate transfer of a computer program from one place to another. A non-transitory processor-readable storage media may be any available media that may be accessed by a computer. By way of example, and not limitation, such non-transitory processor-readable media may comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other tangible storage medium that may be used to store desired program code in the form of instructions or data structures and that may be accessed by a computer or processor. Disk and disc, as used herein, include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk, and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Additionally, the operations of a method or algorithm may reside as one or any combination or set of codes and/or instructions on a non-transitory processor-readable medium and/or computer-readable medium, which may be incorporated into a computer program product.

The preceding description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present invention. 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 within the scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the following claims.

Claim 1:
A mobile electronic device (<NUM>, <NUM>), comprising:
a primary electronic display (<NUM>, <NUM>) positioned on a front face of the mobile electronic device (<NUM>, <NUM>);
a machine-readable scanner engine (<NUM>, <NUM>), the machine-readable scanner engine (<NUM>, <NUM>) including a laser or other bright illumination device and an optical sensor (<NUM>) configured to capture light reflected from a machine-readable indicia to be used in reading the machine-readable indicia; and
a secondary electronic display (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>),
characterized in that the machine-readable scanner engine (<NUM>, <NUM>) and the secondary electronic display (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>) are positioned adjacent to one another on a top face of the mobile electronic device (<NUM>, <NUM>), and in that the mobile electronic device (<NUM>, <NUM>) is configured to prevent simultaneous operation of the machine-readable scanner engine (<NUM>, <NUM>) and secondary display (<NUM>, <NUM>, <NUM>, <NUM>, <NUM>.