U.S. patent application number 13/843195 was filed with the patent office on 2014-09-18 for mobile handset recharge.
This patent application is currently assigned to Z124. The applicant listed for this patent is Z124. Invention is credited to Michael J. Flynn.
Application Number | 20140266012 13/843195 |
Document ID | / |
Family ID | 51524663 |
Filed Date | 2014-09-18 |
United States Patent
Application |
20140266012 |
Kind Code |
A1 |
Flynn; Michael J. |
September 18, 2014 |
Mobile Handset Recharge
Abstract
Methods and devices for connecting a mobile device with
different data storage devices located either locally or remotely
are provided. The device may apply one or more rules to create a
hierarchical virtualization of the several data storage devices.
The virtualization may then be provided to the user as a single,
hierarchical file system. Further, a monitoring system may monitor
the file system to determine if any new applications have been
installed or if applications are currently being executed. If a
connection is made to a secure network, the system may provide the
information derived from the monitoring to the secure network. The
secure network can then analyze the information to determine if any
of the applications should be uninstalled from the device or should
be stopped while the device is connected to the network.
Inventors: |
Flynn; Michael J.;
(Burlington, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Z124 |
George Town |
|
KY |
|
|
Assignee: |
Z124
George Town
KY
|
Family ID: |
51524663 |
Appl. No.: |
13/843195 |
Filed: |
March 15, 2013 |
Current U.S.
Class: |
320/107 ;
320/137; 320/162 |
Current CPC
Class: |
H04M 1/0214 20130101;
H04B 1/3883 20130101; H04M 1/04 20130101; H04M 2250/16 20130101;
H02J 7/0044 20130101; H02J 7/342 20200101; H04B 1/3888 20130101;
H02J 7/0045 20130101; H02J 7/007 20130101 |
Class at
Publication: |
320/107 ;
320/137; 320/162 |
International
Class: |
H02J 7/00 20060101
H02J007/00 |
Claims
1. A method, comprising: placing a device in a holster; and
charging the device from a power source associated with the
holster.
2. The method of claim 1, further comprising determining a charge
on the device.
3. The method of claim 2, further comprising determining a power
level for the power source associated with the holster.
4. The method of claim 3, further comprising determining if there
is more change in the power source.
5. The method of claim 4, further comprising, if there is more
change in the power source, charging the device from the power
source.
6. The method of claim 5, further comprising if there is not more
change in the power source, waiting a period of time before
determining the charge on the device and the power level for the
power source associated with the holster.
7. The method of claim 6, wherein the holster includes the power
source.
8. The method of claim 7, wherein the power source is a
battery.
9. The method of claim 8, wherein the power source and a battery of
the device are connected by a connector on the device and a mating
connector in the holster.
10. The method of claim 9, wherein the connector on the device and
the mating connector in the holster are universal serial bus (USB)
connectors.
11. A device, comprising: a first screen, the first screen
including a first gesture capture region; a second screen, wherein
the second screen faces an opposite direction from the first screen
when the device is closed, and wherein an image capture lens is
associated with the second screen; a memory; a processor in
communication with the memory, the first screen, and the second
screen, the processor operable to: determine that the device has
been inserted into a holster; and receive a charge for a battery of
the device from a power source associated with the holster.
12. The device of claim 11, the processor further operable to:
determine a charge on the device; and determine a power level for
the power source associated with the holster.
13. The device of claim 12, the processor further operable to:
determine if there is more change in the power source; if there is
more change in the power source, charge the device from the power
source; and if there is not more change in the power source, wait a
period of time before determining the charge on the device and the
power level for the power source associated with the holster.
14. The device of claim 13, wherein the power source is a
battery.
15. The device of claim 14, wherein the power source and a battery
of the device are connected by a USB connector on the device and a
mating USB connector in the holster.
16. A computer readable medium having stored thereon
computer-executable instructions, the computer executable
instructions causing a processor of a device to execute a method
for providing a remote device filter, the computer-executable
instructions comprising: instructions to determine that the device
has been inserted into a holster; and instructions to receive a
charge for a battery of the device from a power source associated
with the holster.
17. The computer readable medium of claim 16, the
computer-executable instructions further comprising: instructions
to determine a charge on the device; and instructions to determine
a power level for the power source associated with the holster.
18. The computer readable medium of claim 17, the
computer-executable instructions further comprising: instructions
to determine if there is more change in the power source; if there
is more change in the power source, instructions to charge the
device from the power source; and if there is not more change in
the power source, instructions to wait a period of time before
determining the charge on the device and the power level for the
power source associated with the holster.
19. The computer readable medium of claim 18, wherein the power
source is a battery.
20. The computer readable medium of claim 19, wherein the power
source and a battery of the device are connected by a USB connector
on the device and a mating USB connector in the holster.
Description
CROSS REFERENCE TO RELATED APPLICATION
[0001] The present application relates to U.S. patent application
Ser. No. 10/423,490, filed Apr. 25, 2003; Ser. No. 11/125,883,
filed May 9, 2005; as well as, U.S. patent application Ser. No.
13/248,578, filed Sep. 29, 2011; Ser. No. 13/249,056, filed Sep.
29, 2011; Ser. No. 13/223,778, filed Sep. 1, 2011; Ser. No.
13/223,039, filed Aug. 31, 2011; Ser. No. 13/223,043, filed Aug.
31, 2011; PCT/US11/53924, filed Sep. 29, 2011; Ser. No. 13/247,815,
filed Sep. 28, 2011; Ser. No. 13/248,496, filed Sep. 29, 2011; Ser.
No. 13/248,427, filed Sep. 29, 2011; Ser. No. 13/222,970, filed
Aug. 31, 2011; PCT/US11/53805, filed Sep. 29, 2011; Ser. No.
13/248,138, filed Sep. 29, 2011; PCT/US11/53953, filed Sep. 29,
2011; Ser. No. 13/223,848, filed Sep. 1, 2011; PCT/US11/53806,
filed Sep. 29, 2011; Ser. No. 13/248,188, filed Sep. 29, 2011;
PCT/US11/53929, filed Sep. 29, 2011; Ser. No. 13/248,228, filed
Sep. 29, 2011; PCT/US11/53945, filed Sep. 29, 2011; Ser. No.
13/247,808, filed Sep. 28, 2011; PCT/US11/53851, filed Sep. 29,
2011; Ser. No. 13/248,275, filed Sep. 29, 2011; PCT/US11/53939,
filed Sep. 29, 2011; Ser. No. 13/222,921, filed Aug. 31, 2011;
PCT/US11/53861, filed Sep. 29, 2011; Ser. No. 13/223,015, filed
Aug. 31, 2011; PCT/US11/53855, filed Sep. 29, 2011; Ser. No.
13/247,817, filed Sep. 28, 2011; PCT/US11/53849, filed Sep. 29,
2011; Ser. No. 13/222,910, filed Aug. 31, 2011; PCT/US11/53844,
filed Sep. 29, 2011; Ser. No. 13/247,982, filed Sep. 28, 2011;
PCT/US11/53942, filed Sep. 29, 2011; Ser. No. 13/247,977, filed
Sep. 28, 2011; PCT/US11/53937, filed Sep. 29, 2011; Ser. No.
13/247,971, filed Sep. 28, 2011; PCT/US11/53948, filed Sep. 29,
2011; Ser. No. 13/247,325, filed Sep. 28, 2011; PCT/US11/53889,
filed Sep. 29, 2011; Ser. No. 13/247,345, filed Sep. 28, 2011;
PCT/US11/53893, filed Sep. 29, 2011; Ser. No. 13/248,305, filed
Sep. 29, 2011; PCT/US11/53933, filed Sep. 29, 2011; Ser. No.
13/247,735, filed Sep. 28, 2011; PCT/US11/53919, filed Sep. 29,
2011; Ser. No. 13/247,739, filed Sep. 28, 2011; PCT/US11/53917,
filed Sep. 29, 2011; Ser. No. 13/248,714, filed Sep. 29, 2011; Ser.
No. 13/248,544, filed Sep. 29, 2011; Ser. No. 13/249,014, filed
Sep. 29, 2011; Ser. No. 13/249,103, filed Sep. 29, 2011; Ser. No.
13/247,402, filed Sep. 28, 2011; PCT/US11/53891, filed Sep. 29,
2011; Ser. No. 13/247,749, filed Sep. 28, 2011; Ser. No.
13/249,040, filed Sep. 29, 2011; Ser. No. 13/247,480, filed Sep.
28, 2011; Ser. No. 13/247,359, filed Sep. 28, 2011; PCT/US11/53884,
filed Sep. 29, 2011; Ser. No. 13/222,902, filed Aug. 31, 2011;
PCT/US11/53839, filed Sep. 29, 2011; Ser. No. 13/247,787, filed
Sep. 28, 2011; PCT/US11/53914, filed Sep. 29, 2011; Ser. No.
13/247,797, filed Sep. 28, 2011; PCT/US11/53902, filed Sep. 29,
2011; Ser. No. 13/247,311, filed Sep. 28, 2011; PCT/US11/54032,
filed Sep. 29, 2011; Ser. No. 13/247,823, filed Sep. 28, 2011; Ser.
No. 13/222,888, filed Aug. 31, 2011; Ser. No. 13/247,514, filed
Sep. 28, 2011; Ser. No. 13/223,747, filed Sep. 1, 2011;
PCT/US11/53771, filed Sep. 28, 2011; Ser. No. 13/223,674, filed
Sep. 1, 2011; PCT/US11/53773, filed Sep. 28, 2011; Ser. No.
13/247,822, filed Sep. 28, 2011; Ser. No. 13/247,741, filed Sep.
28, 2011; PCT/US11/53905, filed Sep. 29, 2011; Ser. No. 13/247,744,
filed Sep. 28, 2011; PCT/US11/53896, filed Sep. 29, 2011; Ser. No.
13/247,824, filed Sep. 28, 2011; Ser. No. 13/247,751, filed Sep.
28, 2011; PCT/US11/53880, filed Sep. 29, 2011; Ser. No. 13/247,827,
filed Sep. 28, 2011; Ser. No. 13/247,829, filed Sep. 28, 2011; Ser.
No. 13/247,839, filed Sep. 28, 2011; PCT/US11/53875, filed Sep. 29,
2011; Ser. No. 13/247,836, filed Sep. 28, 2011; Ser. No.
13/223,809, filed Sep. 1, 2011; PCT/US11/53776, filed Sep. 28,
2011; Ser. No. 13/223,727, filed Sep. 1, 2011; PCT/US11/53779,
filed Sep. 28, 2011; Ser. No. 13/223,697, filed Sep. 1, 2011;
PCT/US11/53781, filed Sep. 28, 2011; Ser. No. 13/247,369, filed
Sep. 28, 2011; PCT/US11/53963, filed Sep. 29, 2011; Ser. No.
13/247,708, filed Sep. 28, 2011; Ser. No. 13/247,719, filed Sep.
28, 2011; Ser. No. 13/247,728, filed Sep. 28, 2011; Ser. No.
13/247,388, filed Sep. 28, 2011; PCT/US11/53898, filed Sep. 29,
2011; Ser. No. 13/248,199, filed Sep. 29, 2011; Ser. No.
13/248,450, filed Sep. 29, 2011; Ser. No. 13/247,955, filed Sep.
28, 2011; PCT/US11/53951, filed Sep. 29, 2011; Ser. No. 13/247,949,
filed Sep. 28, 2011; PCT/US11/53960, filed Sep. 29, 2011; Ser. No.
13/247,801, filed Sep. 28, 2011; PCT/US11/53906, filed Sep. 29,
2011; Ser. No. 13/247,581, filed Sep. 28, 2011; PCT/US11/54039,
filed Sep. 29, 2011; Ser. No. 13/247,606, filed Sep. 28, 2011;
PCT/US11/54046, filed Sep. 29, 2011; Ser. No. 13/247,621, filed
Sep. 28, 2011; PCT/US11/54042, filed Sep. 29, 2011; Ser. No.
13/247,634, filed Sep. 28, 2011; Ser. No. 13/248,618, filed Sep.
29, 2011; Ser. No. 13/247,647, filed Sep. 28, 2011; Ser. No.
13/247,663, filed Sep. 28, 2011; Ser. No. 13/247,696, filed Sep.
28, 2011; Ser. No. 13/247,711, filed Sep. 28, 2011; Ser. No.
13/247,724, filed Sep. 28, 2011; Ser. No. 13/247,733, filed Sep.
28, 2011; Ser. No. 13/248,665, filed Sep. 29, 2011; Ser. No.
13/223,056, filed Aug. 31, 2011; Ser. No. 13/571,724, filed Aug.
10, 2012; Ser. No. 13/571,829, filed Aug. 10, 2012; Ser. No.
13/571,951, filed Aug. 10, 2012, and Ser. No. 13/251,768, filed
Aug. 10, 2012. All of the applications listed above are hereby
incorporated by reference, in their entirety, for all that they
teach and for all purposes.
BACKGROUND
[0002] A substantial number of handheld computing devices, such as
cellular phones, tablets, and E-Readers, make use of a touch screen
display not only to deliver display information to the user but
also to receive inputs from user interface commands. While touch
screen displays may increase the configurability of the handheld
device and provide a wide variety of user interface options, this
flexibility typically comes at a price. The dual use of the touch
screen to provide content and receive user commands, while flexible
for the user, may obfuscate the display and cause visual clutter,
thereby leading to user frustration and loss of productivity.
[0003] The small form factor of handheld computing devices requires
a careful balancing between the displayed graphics and the area
provided for receiving inputs. On the one hand, the small display
constrains the display space, which may increase the difficulty of
interpreting actions or results. On the other, a virtual keypad or
other user interface scheme is superimposed on or positioned
adjacent to an executing application, requiring the application to
be squeezed into an even smaller portion of the display.
[0004] This balancing act is particularly difficult for single
display touch screen devices. Single display touch screen devices
are crippled by their limited screen space. When users are entering
information into the device, through the single display, the
ability to interpret information in the display can be severely
hampered, particularly when a complex interaction between display
and interface is required.
SUMMARY
[0005] There is a need for a dual multi-display handheld computing
device that provides for enhanced power and/or versatility compared
to conventional single display handheld computing devices. These
and other needs are addressed by the various aspects, embodiments,
and/or configurations of the present disclosure. Also, while the
disclosure is presented in terms of exemplary embodiments, it
should be appreciated that individual aspects of the disclosure can
be separately claimed.
[0006] Additionally, it is desirable to have the multi-display
device that can connect with different data storage devices located
either locally or remotely. The device may then apply one or more
rules to create a hierarchical virtualization of the several data
storage devices. The virtualization may then be provided to the
user as a single, hierarchical file system. Further, a system may
then monitor the file system to determine if any new applications
have been installed or if applications are currently being
executed. If a connection is made to a secure network, the system
may provide the information derived from the monitoring to the
secure network. The secure network can then analyze the information
to determine if any of the applications should be uninstalled from
the device or should be stopped while the device is connected to
the network.
[0007] The phrases "at least one", "one or more", and "and/or" are
open-ended expressions that are both conjunctive and disjunctive in
operation. For example, each of the expressions "at least one of A,
B and C", "at least one of A, B, or C", "one or more of A, B, and
C", "one or more of A, B, or C" and "A, B, and/or C" means A alone,
B alone, C alone, A and B together, A and C together, B and C
together, or A, B and C together.
[0008] The term "a" or "an" entity refers to one or more of that
entity. As such, the terms "a" (or "an"), "one or more" and "at
least one" can be used interchangeably herein. It is also to be
noted that the terms "comprising", "including", and "having" can be
used interchangeably.
[0009] The term "automatic" and variations thereof, as used herein,
refers to any process or operation done without material human
input when the process or operation is performed. However, a
process or operation can be automatic, even though performance of
the process or operation uses material or immaterial human input,
if the input is received before performance of the process or
operation. Human input is deemed to be material if such input
influences how the process or operation will be performed. Human
input that consents to the performance of the process or operation
is not deemed to be "material".
[0010] The term "computer-readable medium" as used herein refers to
any tangible storage and/or transmission medium that participate in
providing instructions to a processor for execution. Such a medium
may take many forms, including but not limited to, non-volatile
media, volatile media, and transmission media. Non-volatile media
includes, for example, NVRAM, or magnetic or optical disks.
Volatile media includes dynamic memory, such as main memory. Common
forms of computer-readable media include, for example, a floppy
disk, a flexible disk, hard disk, magnetic tape, or any other
magnetic medium, magneto-optical medium, a CD-ROM, any other
optical medium, punch cards, paper tape, any other physical medium
with patterns of holes, a RAM, a PROM, and EPROM, a FLASH-EPROM, a
solid state medium like a memory card, any other memory chip or
cartridge, a carrier wave as described hereinafter, or any other
medium from which a computer can read. A digital file attachment to
e-mail or other self-contained information archive or set of
archives is considered a distribution medium equivalent to a
tangible storage medium. When the computer-readable media is
configured as a database, it is to be understood that the database
may be any type of database, such as relational, hierarchical,
object-oriented, and/or the like. Accordingly, the disclosure is
considered to include a tangible storage medium or distribution
medium and prior art-recognized equivalents and successor media, in
which the software implementations of the present disclosure are
stored.
[0011] The term "desktop" refers to a metaphor used to portray
systems. A desktop is generally considered a "surface" that
typically includes pictures, called icons, widgets, folders, etc.
that can activate show applications, windows, cabinets, files,
folders, documents, and other graphical items. The icons are
generally selectable to initiate a task through user interface
interaction to allow a user to execute applications or conduct
other operations.
[0012] The term "screen," "touch screen," or "touchscreen" refers
to a physical structure that includes one or more hardware
components that provide the device with the ability to render a
user interface and/or receive user input. A screen can encompass
any combination of gesture capture region, a touch sensitive
display, and/or a configurable area. The device can have one or
more physical screens embedded in the hardware. However a screen
may also include an external peripheral device that may be attached
and detached from the device. In embodiments, multiple external
devices may be attached to the device. Thus, in embodiments, the
screen can enable the user to interact with the device by touching
areas on the screen and provides information to a user through a
display. The touch screen may sense user contact in a number of
different ways, such as by a change in an electrical parameter
(e.g., resistance or capacitance), acoustic wave variations,
infrared radiation proximity detection, light variation detection,
and the like. In a resistive touch screen, for example, normally
separated conductive and resistive metallic layers in the screen
pass an electrical current. When a user touches the screen, the two
layers make contact in the contacted location, whereby a change in
electrical field is noted and the coordinates of the contacted
location calculated. In a capacitive touch screen, a capacitive
layer stores electrical charge, which is discharged to the user
upon contact with the touch screen, causing a decrease in the
charge of the capacitive layer. The decrease is measured, and the
contacted location coordinates determined. In a surface acoustic
wave touch screen, an acoustic wave is transmitted through the
screen, and the acoustic wave is disturbed by user contact. A
receiving transducer detects the user contact instance and
determines the contacted location coordinates.
[0013] The term "display" refers to a portion of one or more
screens used to display the output of a computer to a user. A
display may be a single-screen display or a multi-screen display,
referred to as a composite display. A composite display can
encompass the touch sensitive display of one or more screens. A
single physical screen can include multiple displays that are
managed as separate logical displays. Thus, different content can
be displayed on the separate displays although part of the same
physical screen.
[0014] The term "displayed image" refers to an image produced on
the display. A typical displayed image is a window or desktop. The
displayed image may occupy all or a portion of the display.
[0015] The term "display orientation" refers to the way in which a
rectangular display is oriented by a user for viewing. The two most
common types of display orientation are portrait and landscape. In
landscape mode, the display is oriented such that the width of the
display is greater than the height of the display (such as a 4:3
ratio, which is 4 units wide and 3 units tall, or a 16:9 ratio,
which is 16 units wide and 9 units tall). Stated differently, the
longer dimension of the display is oriented substantially
horizontal in landscape mode while the shorter dimension of the
display is oriented substantially vertical. In the portrait mode,
by contrast, the display is oriented such that the width of the
display is less than the height of the display. Stated differently,
the shorter dimension of the display is oriented substantially
horizontal in the portrait mode while the longer dimension of the
display is oriented substantially vertical.
[0016] The term "composite display" refers to a logical structure
that defines a display that can encompass one or more screens. A
multi-screen display can be associated with a composite display
that encompasses all the screens. The composite display can have
different display characteristics based on the various orientations
of the device.
[0017] The term "gesture" refers to a user action that expresses an
intended idea, action, meaning, result, and/or outcome. The user
action can include manipulating a device (e.g., opening or closing
a device, changing a device orientation, moving a trackball or
wheel, etc.), movement of a body part in relation to the device,
movement of an implement or tool in relation to the device, audio
inputs, etc. A gesture may be made on a device (such as on the
screen) or with the device to interact with the device.
[0018] The term "module" as used herein refers to any known or
later developed hardware, software, firmware, artificial
intelligence, fuzzy logic, or combination of hardware and software
that is capable of performing the functionality associated with
that element.
[0019] The term "gesture capture" refers to a sense or otherwise a
detection of an instance and/or type of user gesture. The gesture
capture can occur in one or more areas of the screen, A gesture
region can be on the display, where it may be referred to as a
touch sensitive display or off the display where it may be referred
to as a gesture capture area.
[0020] A "multi-screen application" or "multiple-display
application" refers to an application that is capable of multiple
modes. The multi-screen application mode can include, but is not
limited to, a single screen mode (where the application is
displayed on a single screen) or a composite display mode (where
the application is displayed on two or more screens). A
multi-screen application can have different layouts optimized for
the mode. Thus, the multi-screen application can have different
layouts for a single screen or for a composite display that can
encompass two or more screens. The different layouts may have
different screen/display dimensions and/or configurations on which
the user interfaces of the multi-screen applications can be
rendered. The different layouts allow the application to optimize
the application's user interface for the type of display, e.g.,
single screen or multiple screens. In single screen mode, the
multi-screen application may present one window pane of
information. In a composite display mode, the multi-screen
application may present multiple window panes of information or may
provide a larger and a richer presentation because there is more
space for the display contents. The multi-screen applications may
be designed to adapt dynamically to changes in the device and the
mode depending on which display (single or composite) the system
assigns to the multi-screen application. In alternative
embodiments, the user can use a gesture to request the application
transition to a different mode, and, if a display is available for
the requested mode, the device can allow the application to move to
that display and transition modes.
[0021] A "single-screen application" refers to an application that
is capable of single screen mode. Thus, the single-screen
application can produce only one window and may not be capable of
different modes or different display dimensions. A single-screen
application may not be capable of the several modes discussed with
the multi-screen application.
[0022] The term "window" refers to a, typically rectangular,
displayed image on at least part of a display that contains or
provides content different from the rest of the screen. The window
may obscure the desktop.
[0023] The terms "determine", "calculate" and "compute," and
variations thereof, as used herein, are used interchangeably and
include any type of methodology, process, mathematical operation or
technique.
[0024] It shall be understood that the term "means" as used herein
shall be given its broadest possible interpretation in accordance
with 35 U.S.C., Section 112, Paragraph 6. Accordingly, a claim
incorporating the term "means" shall cover all structures,
materials, or acts set forth herein, and all of the equivalents
thereof. Further, the structures, materials or acts and the
equivalents thereof shall include all those described in the
summary of the invention, brief description of the drawings,
detailed description, abstract, and claims themselves.
[0025] The preceding is a simplified summary of the disclosure to
provide an understanding of some aspects of the disclosure. This
summary is neither an extensive nor exhaustive overview of the
disclosure and its various aspects, embodiments, and/or
configurations. It is intended neither to identify key or critical
elements of the disclosure nor to delineate the scope of the
disclosure but to present selected concepts of the disclosure in a
simplified form as an introduction to the more detailed description
presented below. As will be appreciated, other aspects,
embodiments, and/or configurations of the disclosure are possible
utilizing, alone or in combination, one or more of the features set
forth above or described in detail below.
BRIEF DESCRIPTION OF THE DRAWINGS
[0026] FIG. 1A includes a first view of an embodiment of a
multi-screen user device;
[0027] FIG. 1B includes a second view of an embodiment of a
multi-screen user device;
[0028] FIG. 1C includes a third view of an embodiment of a
multi-screen user device;
[0029] FIG. 1D includes a fourth view of an embodiment of a
multi-screen user device;
[0030] FIG. 1E includes a fifth view of an embodiment of a
multi-screen user device;
[0031] FIG. 1F includes a sixth view of an embodiment of a
multi-screen user device;
[0032] FIG. 1G includes a seventh view of an embodiment of a
multi-screen user device;
[0033] FIG. 1H includes a eighth view of an embodiment of a
multi-screen user device;
[0034] FIG. 1I includes a ninth view of an embodiment of a
multi-screen user device;
[0035] FIG. 1J includes a tenth view of an embodiment of a
multi-screen user device;
[0036] FIG. 2 is a block diagram of an embodiment of the hardware
of the device;
[0037] FIG. 3A is a block diagram of an embodiment of the state
model for the device based on the device's orientation and/or
configuration;
[0038] FIG. 3B is a table of an embodiment of the state model for
the device based on the device's orientation and/or
configuration;
[0039] FIG. 4A is a first representation of an embodiment of user
gesture received at a device;
[0040] FIG. 4B is a second representation of an embodiment of user
gesture received at a device;
[0041] FIG. 4C is a third representation of an embodiment of user
gesture received at a device;
[0042] FIG. 4D is a fourth representation of an embodiment of user
gesture received at a device;
[0043] FIG. 4E is a fifth representation of an embodiment of user
gesture received at a device;
[0044] FIG. 4F is a sixth representation of an embodiment of user
gesture received at a device;
[0045] FIG. 4G is a seventh representation of an embodiment of user
gesture received at a device;
[0046] FIG. 4H is a eighth representation of an embodiment of user
gesture received at a device;
[0047] FIG. 5A is a block diagram of an embodiment of the device
software and/or firmware;
[0048] FIG. 5B is a second block diagram of an embodiment of the
device software and/or firmware;
[0049] FIG. 6A is a first representation of an embodiment of a
device configuration generated in response to the device state;
[0050] FIG. 6B is a second representation of an embodiment of a
device configuration generated in response to the device state;
[0051] FIG. 6C is a third representation of an embodiment of a
device configuration generated in response to the device state;
[0052] FIG. 6D is a fourth representation of an embodiment of a
device configuration generated in response to the device state;
[0053] FIG. 6E is a fifth representation of an embodiment of a
device configuration generated in response to the device state;
[0054] FIG. 6F is a sixth representation of an embodiment of a
device configuration generated in response to the device state;
[0055] FIG. 6G is a seventh representation of an embodiment of a
device configuration generated in response to the device state;
[0056] FIG. 6H is a eighth representation of an embodiment of a
device configuration generated in response to the device state;
[0057] FIG. 6I is a ninth representation of an embodiment of a
device configuration generated in response to the device state;
[0058] FIG. 6J is a tenth representation of an embodiment of a
device configuration generated in response to the device state;
[0059] FIG. 7A is representation of a logical window stack;
[0060] FIG. 7B is another representation of an embodiment of a
logical window stack;
[0061] FIG. 7C is another representation of an embodiment of a
logical window stack;
[0062] FIG. 7D is another representation of an embodiment of a
logical window stack;
[0063] FIG. 7E is another representation of an embodiment of a
logical window stack;
[0064] FIG. 8 is block diagram of an embodiment of a logical data
structure for a window stack;
[0065] FIG. 9 is a flow chart of an embodiment of a method for
creating a window stack;
[0066] FIG. 10 illustrates an exemplary method for managing the
display of an email client application based on application mode
and device configuration;
[0067] FIG. 11 is a block diagram of an embodiment of a data
storage configuration;
[0068] FIG. 12 is a diagram of an embodiment of a hierarchical
arrangement of data storage;
[0069] FIG. 13 is a block diagram of an embodiment of a system for
creating a hierarchical data storage;
[0070] FIG. 14 is a block diagram of an embodiment of a system for
controlling applications in a data storage system;
[0071] FIG. 15 is a flow diagram of an embodiment of a method for
creating a hierarchical storage system;
[0072] FIG. 16 is a flow diagram of an embodiment of a method for
controlling applications in a data storage system;
[0073] FIG. 17 is a flow diagram of an embodiment of a method for
searching a hierarchical data storage system;
[0074] FIG. 18 is a block diagram of an embodiment of the modules
for a selective remote wipe function;
[0075] FIG. 19 is a flow diagram of an embodiment of a method for
selectively wiping data from a mobile device;
[0076] FIG. 20 is a view of an embodiment of a holster for a mobile
device that provide auxiliary power;
[0077] FIG. 21 is a block diagram of an embodiment of the modules
for a holster;
[0078] FIG. 22 is a flow diagram of an embodiment of a method for
providing power to a mobile device from a holster.
[0079] In the appended figures, similar components and/or features
may have the same reference label. Further, various components of
the same type may be distinguished by following the reference label
by a letter that distinguishes among the similar components. If
only the first reference label is used in the specification, the
description is applicable to any one of the similar components
having the same first reference label irrespective of the second
reference label.
DETAILED DESCRIPTION
[0080] Presented herein are embodiments of a device. The device can
be a communications device, such as a cellular telephone, or other
smart device. The device can include two screens that are oriented
to provide several unique display configurations. Further, the
device can receive user input in unique ways. The overall design
and functionality of the device provides for an enhanced user
experience making the device more useful and more efficient.
[0081] Mechanical Features:
[0082] FIGS. 1A-1J illustrate a device 100 in accordance with
embodiments of the present disclosure. As described in greater
detail below, device 100 can be positioned in a number of different
ways each of which provides different functionality to a user. The
device 100 is a multi-screen device that includes a primary screen
104 and a secondary screen 108, both of which are touch sensitive.
In embodiments, the entire front surface of screens 104 and 108 may
be touch sensitive and capable of receiving input by a user
touching the front surface of the screens 104 and 108. Primary
screen 104 includes touch sensitive display 110, which, in addition
to being touch sensitive, also displays information to a user.
Secondary screen 108 includes touch sensitive display 114, which
also displays information to a user. In other embodiments, screens
104 and 108 may include more than one display area.
[0083] Primary screen 104 also includes a configurable area 112
that has been configured for specific inputs when the user touches
portions of the configurable area 112. Secondary screen 108 also
includes a configurable area 116 that has been configured for
specific inputs. Areas 112a and 116a have been configured to
receive a "back" input indicating that a user would like to view
information previously displayed. Areas 112b and 116b have been
configured to receive a "menu" input indicating that the user would
like to view options from a menu. Areas 112c and 116c have been
configured to receive a "home" input indicating that the user would
like to view information associated with a "home" view. In other
embodiments, areas 112a-c and 116a-c may be configured, in addition
to the configurations described above, for other types of specific
inputs including controlling features of device 100, some
non-limiting examples including adjusting overall system power,
adjusting the volume, adjusting the brightness, adjusting the
vibration, selecting of displayed items (on either of screen 104 or
108), operating a camera, operating a microphone, and
initiating/terminating of telephone calls. Also, in some
embodiments, areas 112a-C and 116a-C may be configured for specific
inputs depending upon the application running on device 100 and/or
information displayed on touch sensitive displays 110 and/or
114.
[0084] In addition to touch sensing, primary screen 104 and
secondary screen 108 may also include areas that receive input from
a user without requiring the user to touch the display area of the
screen. For example, primary screen 104 includes gesture capture
area 120, and secondary screen 108 includes gesture capture area
124. These areas are able to receive input by recognizing gestures
made by a user without the need for the user to actually touch the
surface of the display area. In comparison to touch sensitive
displays 110 and 114, the gesture capture areas 120 and 124 are
commonly not capable of rendering a displayed image.
[0085] The two screens 104 and 108 are connected together with a
hinge 128, shown clearly in FIG. 1C (illustrating a back view of
device 100). Hinge 128, in the embodiment shown in FIGS. 1A-1J, is
a center hinge that connects screens 104 and 108 so that when the
hinge is closed, screens 104 and 108 are juxtaposed (i.e.,
side-by-side) as shown in FIG. 1B (illustrating a front view of
device 100). Hinge 128 can be opened to position the two screens
104 and 108 in different relative positions to each other. As
described in greater detail below, the device 100 may have
different functionalities depending on the relative positions of
screens 104 and 108.
[0086] FIG. 1D illustrates the right side of device 100. As shown
in FIG. 1D, secondary screen 108 also includes a card slot 132 and
a port 136 on its side. Card slot 132 in embodiments, accommodates
different types of cards including a subscriber identity module
(SIM). Port 136 in embodiments is an input/output port (I/O port)
that allows device 100 to be connected to other peripheral devices,
such as a display, keyboard, or printing device. As can be
appreciated, these are merely some examples and in other
embodiments device 100 may include other slots and ports such as
slots and ports for accommodating additional memory devices and/or
for connecting other peripheral devices. Also shown in FIG. 1D is
an audio jack 140 that accommodates a tip, ring, sleeve (TRS)
connector for example to allow a user to utilize headphones or a
headset.
[0087] Device 100 also includes a number of buttons 158. For
example, FIG. 1E illustrates the left side of device 100. As shown
in FIG. 1E, the side of primary screen 104 includes three buttons
144, 148, and 152, which can be configured for specific inputs. For
example, buttons 144, 148, and 152 may be configured to, in
combination or alone, control a number of aspects of device 100.
Some non-limiting examples include overall system power, volume,
brightness, vibration, selection of displayed items (on either of
screen 104 or 108), a camera, a microphone, and
initiation/termination of telephone calls. In some embodiments,
instead of separate buttons two buttons may be combined into a
rocker button. This arrangement is useful in situations where the
buttons are configured to control features such as volume or
brightness. In addition to buttons 144, 148, and 152, device 100
also includes a button 156, shown in FIG. 1F, which illustrates the
top of device 100. In one embodiment, button 156 is configured as
an on/off button used to control overall system power to device
100. In other embodiments, button 156 is configured to, in addition
to or in lieu of controlling system power, control other aspects of
device 100. In some embodiments, one or more of the buttons 144,
148, 152, and 156 are capable of supporting different user
commands. By way of example, a normal press has a duration commonly
of less than about 1 second and resembles a quick tap. A medium
press has a duration commonly of 1 second or more but less than
about 12 seconds. A long press has a duration commonly of about 12
seconds or more. The function of the buttons is normally specific
to the application that is currently in focus on the respective
display 110 and 114. In a telephone application for instance and
depending on the particular button, a normal, medium, or long press
can mean end call, increase in call volume, decrease in call
volume, and toggle microphone mute. In a camera or video
application for instance and depending on the particular button, a
normal, medium, or long press can mean increase zoom, decrease
zoom, and take photograph or record video.
[0088] There are also a number of hardware components within device
100. As illustrated in FIG. 1C, device 100 includes a speaker 160
and a microphone 164. Device 100 also includes a camera 168 (FIG.
1B). Additionally, device 100 includes two position sensors 172A
and 172B, which are used to determine the relative positions of
screens 104 and 108. In one embodiment, position sensors 172A and
172B are Hall effect sensors. However, in other embodiments other
sensors can be used in addition to or in lieu of the Hall effect
sensors. An accelerometer 176 may also be included as part of
device 100 to determine the orientation of the device 100 and/or
the orientation of screens 104 and 108. Additional internal
hardware components that may be included in device 100 are
described below with respect to FIG. 2.
[0089] The overall design of device 100 allows it to provide
additional functionality not available in other communication
devices. Some of the functionality is based on the various
positions and orientations that device 100 can have. As shown in
FIGS. 1B-1G, device 100 can be operated in an "open" position where
screens 104 and 108 are juxtaposed. This position allows a large
display area for displaying information to a user. When position
sensors 172A and 172B determine that device 100 is in the open
position, they can generate a signal that can be used to trigger
different events such as displaying information on both screens 104
and 108. Additional events may be triggered if accelerometer 176
determines that device 100 is in a portrait position (FIG. 1B) as
opposed to a landscape position (not shown).
[0090] In addition to the open position, device 100 may also have a
"closed" position illustrated in FIG. 1H. Again, position sensors
172A and 172B can generate a signal indicating that device 100 is
in the "closed" position. This can trigger an event that results in
a change of displayed information on screen 104 and/or 108. For
example, device 100 may be programmed to stop displaying
information on one of the screens, e.g., screen 108, since a user
can only view one screen at a time when device 100 is in the
"closed" position. In other embodiments, the signal generated by
position sensors 172A and 172B, indicating that the device 100 is
in the "closed" position, can trigger device 100 to answer an
incoming telephone call. The "closed" position can also be a
preferred position for utilizing the device 100 as a mobile
phone.
[0091] Device 100 can also be used in an "easel" position which is
illustrated in FIG. 1I. In the "easel" position, screens 104 and
108 are angled with respect to each other and facing outward with
the edges of screens 104 and 108 substantially horizontal. In this
position, device 100 can be configured to display information on
both screens 104 and 108 to allow two users to simultaneously
interact with device 100. When device 100 is in the "easel"
position, sensors 172A and 172B generate a signal indicating that
the screens 104 and 108 are positioned at an angle to each other,
and the accelerometer 176 can generate a signal indicating that
device 100 has been placed so that the edge of screens 104 and 108
are substantially horizontal. The signals can then be used in
combination to generate events that trigger changes in the display
of information on screens 104 and 108.
[0092] FIG. 1J illustrates device 100 in a "modified easel"
position. In the "modified easel" position, one of screens 104 or
108 is used as a stand and is faced down on the surface of an
object such as a table. This position provides a convenient way for
information to be displayed to a user in landscape orientation.
Similar to the easel position, when device 100 is in the "modified
easel" position, position sensors 172A and 172B generate a signal
indicating that the screens 104 and 108 are positioned at an angle
to each other. The accelerometer 176 would generate a signal
indicating that device 100 has been positioned so that one of
screens 104 and 108 is faced downwardly and is substantially
horizontal. The signals can then be used to generate events that
trigger changes in the display of information of screens 104 and
108. For example, information may not be displayed on the screen
that is face down since a user cannot see the screen.
[0093] Transitional states are also possible. When the position
sensors 172A and B and/or accelerometer indicate that the screens
are being closed or folded (from open), a closing transitional
state is recognized. Conversely when the position sensors 172A and
B indicate that the screens are being opened or folded (from
closed), an opening transitional state is recognized. The closing
and opening transitional states are typically time-based, or have a
maximum time duration from a sensed starting point. Normally, no
user input is possible when one of the closing and opening states
is in effect. In this manner, incidental user contact with a screen
during the closing or opening function is not misinterpreted as
user input. In embodiments, another transitional state is possible
when the device 100 is closed. This additional transitional state
allows the display to switch from one screen 104 to the second
screen 108 when the device 100 is closed based on some user input,
e.g., a double tap on the screen 110,114.
[0094] As can be appreciated, the description of device 100 is made
for illustrative purposes only, and the embodiments are not limited
to the specific mechanical features shown in FIGS. 1A-1J and
described above. In other embodiments, device 100 may include
additional features, including one or more additional buttons,
slots, display areas, hinges, and/or locking mechanisms.
Additionally, in embodiments, the features described above may be
located in different parts of device 100 and still provide similar
functionality. Therefore, FIGS. 1A-1J and the description provided
above are nonlimiting.
[0095] Hardware Features:
[0096] FIG. 2 illustrates components of a device 100 in accordance
with embodiments of the present disclosure. In general, the device
100 includes a primary screen 104 and a secondary screen 108. While
the primary screen 104 and its components are normally enabled in
both the opened and closed positions or states, the secondary
screen 108 and its components are normally enabled in the opened
state but disabled in the closed state. However, even when in the
closed state a user or application triggered interrupt (such as in
response to a phone application or camera application operation)
can flip the active screen, or disable the primary screen 104 and
enable the secondary screen 108, by a suitable command. Each screen
104, 108 can be touch sensitive and can include different operative
areas. For example, a first operative area, within each touch
sensitive screen 104 and 108, may comprise a touch sensitive
display 110, 114. In general, the touch sensitive display 110, 114
may comprise a full color, touch sensitive display. A second area
within each touch sensitive screen 104 and 108 may comprise a
gesture capture region 120, 124. The gesture capture region 120,
124 may comprise an area or region that is outside of the touch
sensitive display 110, 114 area, and that is capable of receiving
input, for example in the form of gestures provided by a user.
However, the gesture capture region 120, 124 does not include
pixels that can perform a display function or capability.
[0097] A third region of the touch sensitive screens 104 and 108
may comprise a configurable area 112, 116. The configurable area
112, 116 is capable of receiving input and has display or limited
display capabilities. In embodiments, the configurable area 112,
116 may present different input options to the user. For example,
the configurable area 112, 116 may display buttons or other
relatable items. Moreover, the identity of displayed buttons, or
whether any buttons are displayed at all within the configurable
area 112, 116 of a touch sensitive screen 104 or 108, may be
determined from the context in which the device 100 is used and/or
operated. In an exemplary embodiment, the touch sensitive screens
104 and 108 comprise liquid crystal display devices extending
across at least those regions of the touch sensitive screens 104
and 108 that are capable of providing visual output to a user, and
a capacitive input matrix over those regions of the touch sensitive
screens 104 and 108 that are capable of receiving input from the
user.
[0098] One or more display controllers 216a, 216b may be provided
for controlling the operation of the touch sensitive screens 104
and 108, including input (touch sensing) and output (display)
functions. In the exemplary embodiment illustrated in FIG. 2, a
separate touch screen controller 216a or 216b is provided for each
touch screen 104 and 108. In accordance with alternate embodiments,
a common or shared touch screen controller 216 may be used to
control each of the included touch sensitive screens 104 and 108.
In accordance with still other embodiments, the functions of a
touch screen controller 216 may be incorporated into other
components, such as a processor 204.
[0099] The processor 204 may comprise a general purpose
programmable processor or controller for executing application
programming or instructions. In accordance with at least some
embodiments, the processor 204 may include multiple processor
cores, and/or implement multiple virtual processors. In accordance
with still other embodiments, the processor 204 may include
multiple physical processors. As a particular example, the
processor 204 may comprise a specially configured application
specific integrated circuit (ASIC) or other integrated circuit, a
digital signal processor, a controller, a hardwired electronic or
logic circuit, a programmable logic device or gate array, a special
purpose computer, or the like. The processor 204 generally
functions to run programming code or instructions implementing
various functions of the device 100.
[0100] A communication device 100 may also include memory 208 for
use in connection with the execution of application programming or
instructions by the processor 204, and for the temporary or long
term storage of program instructions and/or data. As examples, the
memory 208 may comprise RAM, DRAM, SDRAM, or other solid state
memory. Alternatively or in addition, data storage 212 may be
provided. Like the memory 208, the data storage 212 may comprise a
solid state memory device or devices. Alternatively or in addition,
the data storage 212 may comprise a hard disk drive or other random
access memory.
[0101] In support of communications functions or capabilities, the
device 100 can include a cellular telephony module 228. As
examples, the cellular telephony module 228 can comprise a GSM,
CDMA, FDMA and/or analog cellular telephony transceiver capable of
supporting voice, multimedia and/or data transfers over a cellular
network. Alternatively or in addition, the device 100 can include
an additional or other wireless communications module 232. As
examples, the other wireless communications module 232 can comprise
a Wi-Fi, BLUETOOTH.TM., WiMax, infrared, or other wireless
communications link. The cellular telephony module 228 and the
other wireless communications module 232 can each be associated
with a shared or a dedicated antenna 224.
[0102] A port interface 252 may be included. The port interface 252
may include proprietary or universal ports to support the
interconnection of the device 100 to other devices or components,
such as a dock, which may or may not include additional or
different capabilities from those integral to the device 100. In
addition to supporting an exchange of communication signals between
the device 100 and another device or component, the docking port
136 and/or port interface 252 can support the supply of power to or
from the device 100. The port interface 252 also comprises an
intelligent element that comprises a docking module for controlling
communications or other interactions between the device 100 and a
connected device or component.
[0103] An input/output module 248 and associated ports may be
included to support communications over wired networks or links,
for example with other communication devices, server devices,
and/or peripheral devices. Examples of an input/output module 248
include an Ethernet port, a Universal Serial Bus (USB) port,
Institute of Electrical and Electronics Engineers (IEEE) 1394, or
other interface.
[0104] An audio input/output interface/device(s) 244 can be
included to provide analog audio to an interconnected speaker or
other device, and to receive analog audio input from a connected
microphone or other device. As an example, the audio input/output
interface/device(s) 244 may comprise an associated amplifier and
analog to digital converter. Alternatively or in addition, the
device 100 can include an integrated audio input/output device 256
and/or an audio jack for interconnecting an external speaker or
microphone. For example, an integrated speaker and an integrated
microphone can be provided, to support near talk or speaker phone
operations.
[0105] Hardware buttons 158 can be included for example for use in
connection with certain control operations. Examples include a
master power switch, volume control, etc., as described in
conjunction with FIGS. 1A through 1J. One or more image capture
interfaces/devices 240, such as a camera, can be included for
capturing still and/or video images. Alternatively or in addition,
an image capture interface/device 240 can include a scanner or code
reader. An image capture interface/device 240 can include or be
associated with additional elements, such as a flash or other light
source.
[0106] The device 100 can also include a global positioning system
(GPS) receiver 236. In accordance with embodiments of the present
invention, the GPS receiver 236 may further comprise a GPS module
that is capable of providing absolute location information to other
components of the device 100. An accelerometer(s) 176 may also be
included. For example, in connection with the display of
information to a user and/or other functions, a signal from the
accelerometer 176 can be used to determine an orientation and/or
format in which to display that information to the user.
[0107] Embodiments of the present invention can also include one or
more position sensor(s) 172. The position sensor 172 can provide a
signal indicating the position of the touch sensitive screens 104
and 108 relative to one another. This information can be provided
as an input, for example to a user interface application, to
determine an operating mode, characteristics of the touch sensitive
displays 110, 114, and/or other device 100 operations. As examples,
a screen position sensor 172 can comprise a series of Hall effect
sensors, a multiple position switch, an optical switch, a
Wheatstone bridge, a potentiometer, or other arrangement capable of
providing a signal indicating of multiple relative positions the
touch screens are in.
[0108] Communications between various components of the device 100
can be carried by one or more buses 222. In addition, power can be
supplied to the components of the device 100 from a power source
and/or power control module 260. The power control module 260 can,
for example, include a battery, an AC to DC converter, power
control logic, and/or ports for interconnecting the device 100 to
an external source of power.
[0109] Device State:
[0110] FIGS. 3A and 3B represent illustrative states of device 100.
While a number of illustrative states are shown, and transitions
from a first state to a second state, it is to be appreciated that
the illustrative state diagram may not encompass all possible
states and/or all possible transitions from a first state to a
second state. As illustrated in FIG. 3, the various arrows between
the states (illustrated by the state represented in the circle)
represent a physical change that occurs to the device 100, that is
detected by one or more of hardware and software, the detection
triggering one or more of a hardware and/or software interrupt that
is used to control and/or manage one or more functions of device
100.
[0111] As illustrated in FIG. 3A, there are twelve exemplary
"physical" states: closed 304, transition 308 (or opening
transitional state), easel 312, modified easel 316, open 320,
inbound/outbound call or communication 324, image/video capture
328, transition 332 (or closing transitional state), landscape 340,
docked 336, docked 344 and landscape 348. Next to each illustrative
state is a representation of the physical state of the device 100
with the exception of states 324 and 328, where the state is
generally symbolized by the international icon for a telephone and
the icon for a camera, respectfully.
[0112] In state 304, the device is in a closed state with the
device 100 generally oriented in the portrait direction with the
primary screen 104 and the secondary screen 108 back-to-back in
different planes (see FIG. 1H). From the closed state, the device
100 can enter, for example, docked state 336, where the device 100
is coupled with a docking station, docking cable, or in general
docked or associated with one or more other devices or peripherals,
or the landscape state 340, where the device 100 is generally
oriented with the primary screen 104 facing the user, and the
primary screen 104 and the secondary screen 108 being
back-to-back.
[0113] In the closed state, the device can also move to a
transitional state where the device remains closed by the display
is moved from one screen 104 to another screen 108 based on a user
input, e.g., a double tap on the screen 110, 114. Still another
embodiment includes a bilateral state. In the bilateral state, the
device remains closed, but a single application displays at least
one window on both the first display 110 and the second display
114. The windows shown on the first and second display 110, 114 may
be the same or different based on the application and the state of
that application. For example, while acquiring an image with a
camera, the device may display the view finder on the first display
110 and displays a preview for the photo subjects (full screen and
mirrored left-to-right) on the second display 114.
[0114] In state 308, a transition state from the closed state 304
to the semi-open state or easel state 312, the device 100 is shown
opening with the primary screen 104 and the secondary screen 108
being rotated around a point of axis coincidence with the hinge.
Upon entering the easel state 312, the primary screen 104 and the
secondary screen 108 are separated from one another such that, for
example, the device 100 can sit in an easel-like configuration on a
surface.
[0115] In state 316, known as the modified easel position, the
device 100 has the primary screen 104 and the secondary screen 108
in a similar relative relationship to one another as in the easel
state 312, with the difference being one of the primary screen 104
or the secondary screen 108 are placed on a surface as shown.
[0116] State 320 is the open state where the primary screen 104 and
the secondary screen 108 are generally on the same plane. From the
open state, the device 100 can transition to the docked state 344
or the open landscape state 348. In the open state 320, the primary
screen 104 and the secondary screen 108 are generally in the
portrait-like orientation while in landscaped state 348 the primary
screen 104 and the secondary screen 108 are generally in a
landscape-like orientation.
[0117] State 324 is illustrative of a communication state, such as
when an inbound or outbound call is being received or placed,
respectively, by the device 100. While not illustrated for clarity,
it should be appreciated the device 100 can transition to the
inbound/outbound call state 324 from any state illustrated in FIG.
3. In a similar manner, the image/video capture state 328 can be
entered into from any other state in FIG. 3, with the image/video
capture state 328 allowing the device 100 to take one or more
images via a camera and/or videos with a video capture device
240.
[0118] Transition state 322 illustratively shows primary screen 104
and the secondary screen 108 being closed upon one another for
entry into, for example, the closed state 304.
[0119] FIG. 3B illustrates, with reference to the key, the inputs
that are received to detect a transition from a first state to a
second state. In FIG. 3B, various combinations of states are shown
with in general, a portion of the columns being directed toward a
portrait state 352, a landscape state 356, and a portion of the
rows being directed to portrait state 360 and landscape state
364.
[0120] In FIG. 3B, the Key indicates that "H" represents an input
from one or more Hall Effect sensors, "A" represents an input from
one or more accelerometers, "T" represents an input from a timer,
"P" represents a communications trigger input and "I" represents an
image and/or video capture request input. Thus, in the center
portion 376 of the chart, an input, or combination of inputs, are
shown that represent how the device 100 detects a transition from a
first physical state to a second physical state.
[0121] As discussed, in the center portion of the chart 376, the
inputs that are received enable the detection of a transition from,
for example, a portrait open state to a landscape easel
state--shown in bold--"HAT." For this exemplary transition from the
portrait open to the landscape easel state, a Hall Effect sensor
("H"), an accelerometer ("A") and a timer ("T") input may be
needed. The timer input can be derived from, for example, a clock
associated with the processor.
[0122] In addition to the portrait and landscape states, a docked
state 368 is also shown that is triggered based on the receipt of a
docking signal 372. As discussed above and in relation to FIG. 3,
the docking signal can be triggered by the association of the
device 100 with one or more other device 100s, accessories,
peripherals, smart docks, or the like.
[0123] User Interaction:
[0124] FIGS. 4A through 4H depict various graphical representations
of gesture inputs that may be recognized by the screens 104, 108.
The gestures may be performed not only by a user's body part, such
as a digit, but also by other devices, such as a stylus, that may
be sensed by the contact sensing portion(s) of a screen 104, 108.
In general, gestures are interpreted differently, based on where
the gestures are performed (either directly on the display 110, 114
or in the gesture capture region 120, 124). For example, gestures
in the display 110,114 may be directed to a desktop or application,
and gestures in the gesture capture region 120, 124 may be
interpreted as for the system.
[0125] With reference to FIGS. 4A-4H, a first type of gesture, a
touch gesture 420, is substantially stationary on the screen
104,108 for a selected length of time. A circle 428 represents a
touch or other contact type received at particular location of a
contact sensing portion of the screen. The circle 428 may include a
border 432, the thickness of which indicates a length of time that
the contact is held substantially stationary at the contact
location. For instance, a tap 420 (or short press) has a thinner
border 432a than the border 432b for a long press 424 (or for a
normal press). The long press 424 may involve a contact that
remains substantially stationary on the screen for longer time
period than that of a tap 420. As will be appreciated, differently
defined gestures may be registered depending upon the length of
time that the touch remains stationary prior to contact cessation
or movement on the screen.
[0126] With reference to FIG. 4C, a drag gesture 400 on the screen
104,108 is an initial contact (represented by circle 428) with
contact movement 436 in a selected direction. The initial contact
428 may remain stationary on the screen 104,108 for a certain
amount of time represented by the border 432. The drag gesture
typically requires the user to contact an icon, window, or other
displayed image at a first location followed by movement of the
contact in a drag direction to a new second location desired for
the selected displayed image. The contact movement need not be in a
straight line but have any path of movement so long as the contact
is substantially continuous from the first to the second
locations.
[0127] With reference to FIG. 4D, a flick gesture 404 on the screen
104,108 is an initial contact (represented by circle 428) with
truncated contact movement 436 (relative to a drag gesture) in a
selected direction. In embodiments, a flick has a higher exit
velocity for the last movement in the gesture compared to the drag
gesture. The flick gesture can, for instance, be a finger snap
following initial contact. Compared to a drag gesture, a flick
gesture generally does not require continual contact with the
screen 104,108 from the first location of a displayed image to a
predetermined second location. The contacted displayed image is
moved by the flick gesture in the direction of the flick gesture to
the predetermined second location. Although both gestures commonly
can move a displayed image from a first location to a second
location, the temporal duration and distance of travel of the
contact on the screen is generally less for a flick than for a drag
gesture.
[0128] With reference to FIG. 4E, a pinch gesture 408 on the screen
104,108 is depicted. The pinch gesture 408 may be initiated by a
first contact 428a to the screen 104,108 by, for example, a first
digit and a second contact 428b to the screen 104,108 by, for
example, a second digit. The first and second contacts 428a,b may
be detected by a common contact sensing portion of a common screen
104,108, by different contact sensing portions of a common screen
104 or 108, or by different contact sensing portions of different
screens. The first contact 428a is held for a first amount of time,
as represented by the border 432a, and the second contact 428b is
held for a second amount of time, as represented by the border
432b. The first and second amounts of time are generally
substantially the same, and the first and second contacts 428 a, b
generally occur substantially simultaneously. The first and second
contacts 428 a, b generally also include corresponding first and
second contact movements 436 a, b, respectively. The first and
second contact movements 436 a, b are generally in opposing
directions. Stated another way, the first contact movement 436a is
towards the second contact 436b, and the second contact movement
436b is towards the first contact 436a. More simply stated, the
pinch gesture 408 may be accomplished by a user's digits touching
the screen 104,108 in a pinching motion.
[0129] With reference to FIG. 4F, a spread gesture 410 on the
screen 104,108 is depicted. The spread gesture 410 may be initiated
by a first contact 428a to the screen 104,108 by, for example, a
first digit and a second contact 428b to the screen 104,108 by, for
example, a second digit. The first and second contacts 428a,b may
be detected by a common contact sensing portion of a common screen
104,108, by different contact sensing portions of a common screen
104,108, or by different contact sensing portions of different
screens. The first contact 428a is held for a first amount of time,
as represented by the border 432a, and the second contact 428b is
held for a second amount of time, as represented by the border
432b. The first and second amounts of time are generally
substantially the same, and the first and second contacts 428 a, b
generally occur substantially simultaneously. The first and second
contacts 428 a, b generally also include corresponding first and
second contact movements 436a, b, respectively. The first and
second contact movements 436 a, b are generally in a common
direction. Stated another way, the first and second contact
movements 436 a, b are away from the first and second contacts
428a, b. More simply stated, the spread gesture 410 may be
accomplished by a user's digits touching the screen 104,108 in a
spreading motion.
[0130] The above gestures may be combined in any manner, such as
those shown by FIGS. 4G and 4H, to produce a determined functional
result. For example, in FIG. 4G a tap gesture 420 is combined with
a drag or flick gesture 412 in a direction away from the tap
gesture 420. In FIG. 4H, a tap gesture 420 is combined with a drag
or flick gesture 412 in a direction towards the tap gesture
420.
[0131] The functional result of receiving a gesture can vary
depending on a number of factors, including a state of the device
100, display 110, 114, or screen 104, 108, a context associated
with the gesture, or sensed location of the gesture. The state of
the device commonly refers to one or more of a configuration of the
device 100, a display orientation, and user and other inputs
received by the device 100. Context commonly refers to one or more
of the particular application(s) selected by the gesture and the
portion(s) of the application currently executing, whether the
application is a single- or multi-screen application, and whether
the application is a multi-screen application displaying one or
more windows in one or more screens or in one or more stacks.
Sensed location of the gesture commonly refers to whether the
sensed set(s) of gesture location coordinates are on a touch
sensitive display 110, 114 or a gesture capture region 120, 124,
whether the sensed set(s) of gesture location coordinates are
associated with a common or different display or screen 104,108,
and/or what portion of the gesture capture region contains the
sensed set(s) of gesture location coordinates.
[0132] A tap, when received by an a touch sensitive display 110,
114, can be used, for instance, to select an icon to initiate or
terminate execution of a corresponding application, to maximize or
minimize a window, to reorder windows in a stack, and to provide
user input such as by keyboard display or other displayed image. A
drag, when received by a touch sensitive display 110, 114, can be
used, for instance, to relocate an icon or window to a desired
location within a display, to reorder a stack on a display, or to
span both displays (such that the selected window occupies a
portion of each display simultaneously). A flick, when received by
a touch sensitive display 110, 114 or a gesture capture region 120,
124, can be used to relocate a window from a first display to a
second display or to span both displays (such that the selected
window occupies a portion of each display simultaneously). Unlike
the drag gesture, however, the flick gesture is generally not used
to move the displayed image to a specific user-selected location
but to a default location that is not configurable by the user.
[0133] The pinch gesture, when received by a touch sensitive
display 110, 114 or a gesture capture region 120, 124, can be used
to minimize or otherwise increase the displayed area or size of a
window (typically when received entirely by a common display), to
switch windows displayed at the top of the stack on each display to
the top of the stack of the other display (typically when received
by different displays or screens), or to display an application
manager (a "pop-up window" that displays the windows in the stack).
The spread gesture, when received by a touch sensitive display 110,
114 or a gesture capture region 120, 124, can be used to maximize
or otherwise decrease the displayed area or size of a window, to
switch windows displayed at the top of the stack on each display to
the top of the stack of the other display (typically when received
by different displays or screens), or to display an application
manager (typically when received by an off-screen gesture capture
region on the same or different screens).
[0134] The combined gestures of FIG. 4G, when received by a common
display capture region in a common display or screen 104,108, can
be used to hold a first window stack location in a first stack
constant for a display receiving the gesture while reordering a
second window stack location in a second window stack to include a
window in the display receiving the gesture. The combined gestures
of FIG. 4H, when received by different display capture regions in a
common display or screen 104,108 or in different displays or
screens, can be used to hold a first window stack location in a
first window stack constant for a display receiving the tap part of
the gesture while reordering a second window stack location in a
second window stack to include a window in the display receiving
the flick or drag gesture. Although specific gestures and gesture
capture regions in the preceding examples have been associated with
corresponding sets of functional results, it is to be appreciated
that these associations can be redefined in any manner to produce
differing associations between gestures and/or gesture capture
regions and/or functional results.
[0135] Firmware and Software:
[0136] The memory 508 may store and the processor 504 may execute
one or more software components. These components can include at
least one operating system (OS) 516, an application manager 562, a
desktop 566, and/or one or more applications 564a and/or 564b from
an application store 560. The OS 516 can include a framework 520,
one or more frame buffers 548, one or more drivers 512, previously
described in conjunction with FIG. 2, and/or a kernel 518. The OS
516 can be any software, consisting of programs and data, which
manages computer hardware resources and provides common services
for the execution of various applications 564. The OS 516 can be
any operating system and, at least in some embodiments, dedicated
to mobile devices, including, but not limited to, Linux,
ANDROID.TM., iPhone OS (IOS.TM.), WINDOWS PHONE 7.TM., etc. The OS
516 is operable to provide functionality to the phone by executing
one or more operations, as described herein.
[0137] The applications 564 can be any higher level software that
executes particular functionality for the user. Applications 564
can include programs such as email clients, web browsers, texting
applications, games, media players, office suites, etc. The
applications 564 can be stored in an application store 560, which
may represent any memory or data storage, and the management
software associated therewith, for storing the applications 564.
Once executed, the applications 564 may be run in a different area
of memory 508.
[0138] The framework 520 may be any software or data that allows
the multiple tasks running on the device to interact. In
embodiments, at least portions of the framework 520 and the
discrete components described hereinafter may be considered part of
the OS 516 or an application 564. However, these portions will be
described as part of the framework 520, but those components are
not so limited. The framework 520 can include, but is not limited
to, a Multi-Display Management (MDM) module 524, a Surface Cache
module 528, a Window Management module 532, an Input Management
module 536, a Task Management module 540, an Application Model
Manager 542, a Display Controller, one or more frame buffers 548, a
task stack 552, one or more window stacks 550 (which is a logical
arrangement of windows and/or desktops in a display area), and/or
an event buffer 556.
[0139] The MDM module 524 includes one or more modules that are
operable to manage the display of applications or other data on the
screens of the device. An embodiment of the MDM module 524 is
described in conjunction with FIG. 5B. In embodiments, the MDM
module 524 receives inputs from the other OS 516 components, such
as, the drivers 512, and from the applications 564 to determine
continually the state of the device 100. The inputs assist the MDM
module 524 in determining how to configure and allocate the
displays according to the application's preferences and
requirements, and the user's actions. Once a determination for
display configurations is made, the MDM module 524 can bind the
applications 564 to a display. The configuration may then be
provided to one or more other components to generate a window with
a display.
[0140] The Surface Cache module 528 includes any memory or storage
and the software associated therewith to store or cache one or more
images of windows. A series of active and/or non-active windows (or
other display objects, such as, a desktop display) can be
associated with each display. An active window (or other display
object) is currently displayed. A non-active windows (or other
display objects) were opened and, at some time, displayed but are
now not displayed. To enhance the user experience, before a window
transitions from an active state to an inactive state, a "screen
shot" of a last generated image of the window (or other display
object) can be stored. The Surface Cache module 528 may be operable
to store a bitmap of the last active image of a window (or other
display object) not currently displayed. Thus, the Surface Cache
module 528 stores the images of non-active windows (or other
display objects) in a data store.
[0141] In embodiments, the Window Management module 532 is operable
to manage the windows (or other display objects) that are active or
not active on each of the displays. The Window Management module
532, based on information from the MDM module 524, the OS 516, or
other components, determines when a window (or other display
object) is visible or not active. The Window Management module 532
may then put a non-visible window (or other display object) in a
"not active state" and, in conjunction with the Task Management
module Task Management 540 suspends the application's operation.
Further, the Window Management module 532 may assign, through
collaborative interaction with the MDM module 524, a display
identifier to the window (or other display object) or manage one or
more other items of data associated with the window (or other
display object). The Window Management module 532 may also provide
the stored information to the application 564, the Task Management
module 540, or other components interacting with or associated with
the window (or other display object). The Window Management module
532 can also associate an input task with a window based on window
focus and display coordinates within the motion space.
[0142] The Input Management module 536 is operable to manage events
that occur with the device. An event is any input into the window
environment, for example, a user interface interactions with a
user. The Input Management module 536 receives the events and
logically stores the events in an event buffer 556. Events can
include such user interface interactions as a "down event," which
occurs when a screen 104, 108 receives a touch signal from a user,
a "move event," which occurs when the screen 104, 108 determines
that a user's finger is moving across a screen(s), an "up event,
which occurs when the screen 104, 108 determines that the user has
stopped touching the screen 104, 108, etc. These events are
received, stored, and forwarded to other modules by the Input
Management module 536. The Input Management module 536 may also map
screen inputs to a motion space which is the culmination of all
physical and virtual display available on the device.
[0143] The motion space is a virtualized space that includes all
touch sensitive displays 110,114 "tiled" together to mimic the
physical dimensions of the device 100. For example, when the device
100 is unfolded, the motion space size may be 960.times.800, which
may be the number of pixels in the combined display area for both
touch sensitive displays 110, 114. If a user touches on a first
touch sensitive display 110 on location (40, 40), a full screen
window can receive touch event with location (40, 40). If a user
touches on a second touch sensitive display 114, with location (40,
40), the full screen window can receive touch event with location
(520, 40), because the second touch sensitive display 114 is on the
right side of the first touch sensitive display 110, so the device
100 can offset the touch by the first touch sensitive display's 110
width, which is 480 pixels. When a hardware event occurs with
location info from a driver 512, the framework 520 can up-scale the
physical location to the motion space because the location of the
event may be different based on the device orientation and state.
The motion space may be as described in U.S. patent application
Ser. No. 13/187,026, filed Jul. 20, 2011, entitled "Systems and
Methods for Receiving Gesture Inputs Spanning Multiple Input
Devices," which is hereby incorporated by reference in its entirety
for all that it teaches and for all purposes.
[0144] A task can be an application and a sub-task can be an
application component that provides a window with which users can
interact to do something, such as dial the phone, take a photo,
send an email, or view a map. Each task may be given a window in
which to draw a user interface. The window typically fills a
display (for example, touch sensitive display 110,114), but may be
smaller than the display 110,114 and float on top of other windows.
An application usually consists of multiple sub-tasks that are
loosely bound to each other. Typically, one task in an application
is specified as the "main" task, which is presented to the user
when launching the application for the first time. Each task can
then start another task or sub-task to perform different
actions.
[0145] The Task Management module 540 is operable to manage the
operation of one or more applications 564 that may be executed by
the device. Thus, the Task Management module 540 can receive
signals to launch, suspend, terminate, etc. an application or
application sub-tasks stored in the application store 560. The Task
Management module 540 may then instantiate one or more tasks or
sub-tasks of the application 564 to begin operation of the
application 564. Further, the Task Management Module 540 may
launch, suspend, or terminate a task or sub-task as a result of
user input or as a result of a signal from a collaborating
framework 520 component. The Task Management Module 540 is
responsible for managing the lifecycle of applications (tasks and
sub-task) from when the application is launched to when the
application is terminated.
[0146] The processing of the Task Management Module 540 is
facilitated by a task stack 552, which is a logical structure
associated with the Task Management Module 540. The task stack 552
maintains the state of all tasks and sub-tasks on the device 100.
When some component of the operating system 516 requires a task or
sub-task to transition in its lifecycle, the OS 516 component can
notify the Task Management Module 540. The Task Management Module
540 may then locate the task or sub-task, using identification
information, in the task stack 552, and send a signal to the task
or sub-task indicating what kind of lifecycle transition the task
needs to execute. Informing the task or sub-task of the transition
allows the task or sub-task to prepare for the lifecycle state
transition. The Task Management Module 540 can then execute the
state transition for the task or sub-task. In embodiments, the
state transition may entail triggering the OS kernel 518 to
terminate the task when termination is required.
[0147] Further, the Task Management module 540 may suspend the
application 564 based on information from the Window Management
Module 532. Suspending the application 564 may maintain application
data in memory but may limit or stop the application 564 from
rendering a window or user interface. Once the application becomes
active again, the Task Management module 540 can again trigger the
application to render its user interface. In embodiments, if a task
is suspended, the task may save the task's state in case the task
is terminated. In the suspended state, the application task may not
receive input because the application window is not visible to the
user.
[0148] The frame buffer 548 is a logical structure(s) used to
render the user interface. The frame buffer 548 can be created and
destroyed by the OS kernel 518. However, the Display Controller 544
can write the image data, for the visible windows, into the frame
buffer 548. A frame buffer 548 can be associated with one screen or
multiple screens. The association of a frame buffer 548 with a
screen can be controlled dynamically by interaction with the OS
kernel 518. A composite display may be created by associating
multiple screens with a single frame buffer 548. Graphical data
used to render an application's window user interface may then be
written to the single frame buffer 548, for the composite display,
which is output to the multiple screens 104,108. The Display
Controller 544 can direct an application's user interface to a
portion of the frame buffer 548 that is mapped to a particular
display 110,114, thus, displaying the user interface on only one
screen 104 or 108. The Display Controller 544 can extend the
control over user interfaces to multiple applications, controlling
the user interfaces for as many displays as are associated with a
frame buffer 548 or a portion thereof. This approach compensates
for the multiple physical screens 104,108 that are in use by the
software component above the Display Controller 544.
[0149] The Application Manager 562 is an application that provides
a presentation layer for the window environment. Thus, the
Application Manager 562 provides the graphical model for rendering
by the Task Management Module 540. Likewise, the Desktop 566
provides the presentation layer for the Application Store 560.
Thus, the desktop provides a graphical model of a surface having
selectable application icons for the Applications 564 in the
Application Store 560 that can be provided to the Window Management
Module 556 for rendering.
[0150] Further, the framework can include an Application Model
Manager (AMM) 542. The Application Manager 562 may interface with
the AMM 542. In embodiments, the AMM 542 receives state change
information from the device 100 regarding the state of applications
(which are running or suspended). The AMM 542 can associate bit map
images from the Surface Cache Module 528 to the tasks that are
alive (running or suspended). Further, the AMM 542 can convert the
logical window stack maintained in the Task Manager Module 540 to a
linear ("film strip" or "deck of cards") organization that the user
perceives when the using the off gesture capture area 120 to sort
through the windows. Further, the AMM 542 may provide a list of
executing applications to the Application Manager 562.
[0151] An embodiment of the MDM module 524 is shown in FIG. 5B. The
MDM module 524 is operable to determine the state of the
environment for the device, including, but not limited to, the
orientation of the device, whether the device 100 is opened or
closed, what applications 564 are executing, how the applications
564 are to be displayed, what actions the user is conducting, the
tasks being displayed, etc. To configure the display, the MDM
module 524 interprets these environmental factors and determines a
display configuration, as described in conjunction with FIGS.
6A-6J. Then, the MDM module 524 can bind the applications 564 or
other device components to the displays. The configuration may then
be sent to the Display Controller 544 and/or the other components
within the OS 516 to generate the display. The MDM module 524 can
include one or more of, but is not limited to, a Display
Configuration Module 568, a Preferences Module 572, a Device State
Module 574, a Gesture Module 576, a Requirements Module 580, an
Event Module 584, and/or a Binding Module 588.
[0152] The Display Configuration Module 568 determines the layout
for the display. In embodiments, the Display Configuration Module
568 can determine the environmental factors. The environmental
factors may be received from one or more other MDM modules 524 or
from other sources. The Display Configuration Module 568 can then
determine from the list of factors the best configuration for the
display. Some embodiments of the possible configurations and the
factors associated therewith are described in conjunction with
FIGS. 6A-6F.
[0153] The Preferences Module 572 is operable to determine display
preferences for an application 564 or other component. For example,
an application can have a preference for Single or Dual displays.
The Preferences Module 572 can determine an application's display
preference (e.g., by inspecting the application's preference
settings) and may allow the application 564 to change to a mode
(e.g., single screen, dual screen, max, etc.) if the device 100 is
in a state that can accommodate the preferred mode. However, some
user interface policies may disallow a mode even if the mode is
available. As the configuration of the device changes, the
preferences may be reviewed to determine if a better display
configuration can be achieved for an application 564.
[0154] The Device State Module 574 is operable to determine or
receive the state of the device. The state of the device can be as
described in conjunction with FIGS. 3A and 3B. The state of the
device can be used by the Display Configuration Module 568 to
determine the configuration for the display. As such, the Device
State Module 574 may receive inputs and interpret the state of the
device. The state information is then provided to the Display
Configuration Module 568.
[0155] The Gesture Module 576 is shown as part of the MDM module
524, but, in embodiments, the Gesture module 576 may be a separate
Framework 520 component that is separate from the MDM module 524.
In embodiments, the Gesture Module 576 is operable to determine if
the user is conducting any actions on any part of the user
interface. In alternative embodiments, the Gesture Module 576
receives user interface actions from the configurable area 112,116
only. The Gesture Module 576 can receive touch events that occur on
the configurable area 112,116 (or possibly other user interface
areas) by way of the Input Management Module 536 and may interpret
the touch events (using direction, speed, distance, duration, and
various other parameters) to determine what kind of gesture the
user is performing. When a gesture is interpreted, the Gesture
Module 576 can initiate the processing of the gesture and, by
collaborating with other Framework 520 components, can manage the
required window animation. The Gesture Module 576 collaborates with
the Application Model Manager 542 to collect state information with
respect to which applications are running (active or paused) and
the order in which applications must appear when a user gesture is
performed. The Gesture Module 576 may also receive references to
bitmaps (from the Surface Cache Module 528) and live windows so
that when a gesture occurs it can instruct the Display Controller
544 how to move the window(s) across the display 110,114. Thus,
suspended applications may appear to be running when those windows
are moved across the display 110,114.
[0156] Further, the Gesture Module 576 can receive task information
either from the Task Manage Module 540 or the Input Management
module 536. The gestures may be as defined in conjunction with
FIGS. 4A through 4H. For example, moving a window causes the
display to render a series of display frames that illustrate the
window moving. The gesture associated with such user interface
interaction can be received and interpreted by the Gesture Module
576. The information about the user gesture is then sent to the
Task Management Module 540 to modify the display binding of the
task.
[0157] The Requirements Module 580, similar to the Preferences
Module 572, is operable to determine display requirements for an
application 564 or other component. An application can have a set
display requirement that must be observed. Some applications
require a particular display orientation. For example, the
application "Angry Birds" can only be displayed in landscape
orientation. This type of display requirement can be determined or
received, by the Requirements Module 580. As the orientation of the
device changes, the Requirements Module 580 can reassert the
display requirements for the application 564. The Display
Configuration Module 568 can generate a display configuration that
is in accordance with the application display requirements, as
provided by the Requirements Module 580.
[0158] The Event Module 584, similar to the Gesture Module 576, is
operable to determine one or more events occurring with an
application or other component that can affect the user interface.
Thus, the Event Module 584 can receive event information either
from the event buffer 556 or the Task Management module 540. These
events can change how the tasks are bound to the displays. The
Event Module 584 can collect state change information from other
Framework 520 components and act upon that state change
information. In an example, when the phone is opened or closed or
when an orientation change has occurred, a new message may be
rendered in a secondary screen. The state change based on the event
can be received and interpreted by the Event Module 584. The
information about the events then may be sent to the Display
Configuration Module 568 to modify the configuration of the
display.
[0159] The Binding Module 588 is operable to bind the applications
564 or the other components to the configuration determined by the
Display Configuration Module 568. A binding associates, in memory,
the display configuration for each application with the display and
mode of the application. Thus, the Binding Module 588 can associate
an application with a display configuration for the application
(e.g. landscape, portrait, multi-screen, etc.). Then, the Binding
Module 588 may assign a display identifier to the display. The
display identifier associated the application with a particular
display of the device 100. This binding is then stored and provided
to the Display Controller 544, the other components of the OS 516,
or other components to properly render the display. The binding is
dynamic and can change or be updated based on configuration changes
associated with events, gestures, state changes, application
preferences or requirements, etc.
[0160] User Interface Configurations:
[0161] With reference now to FIGS. 6A-J, various types of output
configurations made possible by the device 100 will be described
hereinafter.
[0162] FIGS. 6A and 6B depict two different output configurations
of the device 100 being in a first state. Specifically, FIG. 6A
depicts the device 100 being in a closed portrait state 304 where
the data is displayed on the primary screen 104. In this example,
the device 100 displays data via the touch sensitive display 110 in
a first portrait configuration 604. As can be appreciated, the
first portrait configuration 604 may only display a desktop or
operating system home screen. Alternatively, one or more windows
may be presented in a portrait orientation while the device 100 is
displaying data in the first portrait configuration 604.
[0163] FIG. 6B depicts the device 100 still being in the closed
portrait state 304, but instead data is displayed on the secondary
screen 108. In this example, the device 100 displays data via the
touch sensitive display 114 in a second portrait configuration
608.
[0164] It may be possible to display similar or different data in
either the first or second portrait configuration 604, 608. It may
also be possible to transition between the first portrait
configuration 604 and second portrait configuration 608 by
providing the device 100 a user gesture (e.g., a double tap
gesture), a menu selection, or other means. Other suitable gestures
may also be employed to transition between configurations.
Furthermore, it may also be possible to transition the device 100
from the first or second portrait configuration 604, 608 to any
other configuration described herein depending upon which state the
device 100 is moved.
[0165] An alternative output configuration may be accommodated by
the device 100 being in a second state. Specifically, FIG. 6C
depicts a third portrait configuration where data is displayed
simultaneously on both the primary screen 104 and the secondary
screen 108. The third portrait configuration may be referred to as
a Dual-Portrait (PD) output configuration. In the PD output
configuration, the touch sensitive display 110 of the primary
screen 104 depicts data in the first portrait configuration 604
while the touch sensitive display 114 of the secondary screen 108
depicts data in the second portrait configuration 608. The
simultaneous presentation of the first portrait configuration 604
and the second portrait configuration 608 may occur when the device
100 is in an open portrait state 320. In this configuration, the
device 100 may display one application window in one display 110 or
114, two application windows (one in each display 110 and 114), one
application window and one desktop, or one desktop. Other
configurations may be possible. It should be appreciated that it
may also be possible to transition the device 100 from the
simultaneous display of configurations 604, 608 to any other
configuration described herein depending upon which state the
device 100 is moved. Furthermore, while in this state, an
application's display preference may place the device into
bilateral mode, in which both displays are active to display
different windows in the same application. For example, a Camera
application may display a viewfinder and controls on one side,
while the other side displays a mirrored preview that can be seen
by the photo subjects. Games involving simultaneous play by two
players may also take advantage of bilateral mode.
[0166] FIGS. 6D and 6E depicts two further output configurations of
the device 100 being in a third state. Specifically, FIG. 6D
depicts the device 100 being in a closed landscape state 340 where
the data is displayed on the primary screen 104. In this example,
the device 100 displays data via the touch sensitive display 110 in
a first landscape configuration 612. Much like the other
configurations described herein, the first landscape configuration
612 may display a desktop, a home screen, one or more windows
displaying application data, or the like.
[0167] FIG. 6E depicts the device 100 still being in the closed
landscape state 340, but instead data is displayed on the secondary
screen 108. In this example, the device 100 displays data via the
touch sensitive display 114 in a second landscape configuration
616. It may be possible to display similar or different data in
either the first or second portrait configuration 612, 616. It may
also be possible to transition between the first landscape
configuration 612 and second landscape configuration 616 by
providing the device 100 with one or both of a twist and tap
gesture or a flip and slide gesture. Other suitable gestures may
also be employed to transition between configurations. Furthermore,
it may also be possible to transition the device 100 from the first
or second landscape configuration 612, 616 to any other
configuration described herein depending upon which state the
device 100 is moved.
[0168] FIG. 6F depicts a third landscape configuration where data
is displayed simultaneously on both the primary screen 104 and the
secondary screen 108. The third landscape configuration may be
referred to as a Dual-Landscape (LD) output configuration. In the
LD output configuration, the touch sensitive display 110 of the
primary screen 104 depicts data in the first landscape
configuration 612 while the touch sensitive display 114 of the
secondary screen 108 depicts data in the second landscape
configuration 616. The simultaneous presentation of the first
landscape configuration 612 and the second landscape configuration
616 may occur when the device 100 is in an open landscape state
340. It should be appreciated that it may also be possible to
transition the device 100 from the simultaneous display of
configurations 612, 616 to any other configuration described herein
depending upon which state the device 100 is moved.
[0169] FIGS. 6G and 6H depict two views of a device 100 being in
yet another state. Specifically, the device 100 is depicted as
being in an easel state 312. FIG. 6G shows that a first easel
output configuration 618 may be displayed on the touch sensitive
display 110. FIG. 6H shows that a second easel output configuration
620 may be displayed on the touch sensitive display 114. The device
100 may be configured to depict either the first easel output
configuration 618 or the second easel output configuration 620
individually. Alternatively, both the easel output configurations
618, 620 may be presented simultaneously. In some embodiments, the
easel output configurations 618, 620 may be similar or identical to
the landscape output configurations 612, 616. The device 100 may
also be configured to display one or both of the easel output
configurations 618, 620 while in a modified easel state 316. It
should be appreciated that simultaneous utilization of the easel
output configurations 618, 620 may facilitate two-person games
(e.g., Battleship.RTM., chess, checkers, etc.), multi-user
conferences where two or more users share the same device 100, and
other applications. As can be appreciated, it may also be possible
to transition the device 100 from the display of one or both
configurations 618, 620 to any other configuration described herein
depending upon which state the device 100 is moved.
[0170] FIG. 6I depicts yet another output configuration that may be
accommodated while the device 100 is in an open portrait state 320.
Specifically, the device 100 may be configured to present a single
continuous image across both touch sensitive displays 110, 114 in a
portrait configuration referred to herein as a Portrait-Max (PMax)
configuration 624. In this configuration, data (e.g., a single
image, application, window, icon, video, etc.) may be split and
displayed partially on one of the touch sensitive displays while
the other portion of the data is displayed on the other touch
sensitive display. The Pmax configuration 624 may facilitate a
larger display and/or better resolution for displaying a particular
image on the device 100. Similar to other output configurations, it
may be possible to transition the device 100 from the Pmax
configuration 624 to any other output configuration described
herein depending upon which state the device 100 is moved.
[0171] FIG. 6J depicts still another output configuration that may
be accommodated while the device 100 is in an open landscape state
348. Specifically, the device 100 may be configured to present a
single continuous image across both touch sensitive displays 110,
114 in a landscape configuration referred to herein as a
Landscape-Max (LMax) configuration 628. In this configuration, data
(e.g., a single image, application, window, icon, video, etc.) may
be split and displayed partially on one of the touch sensitive
displays while the other portion of the data is displayed on the
other touch sensitive display. The Lmax configuration 628 may
facilitate a larger display and/or better resolution for displaying
a particular image on the device 100. Similar to other output
configurations, it may be possible to transition the device 100
from the Lmax configuration 628 to any other output configuration
described herein depending upon which state the device 100 is
moved.
[0172] The device 100 manages desktops and/or windows with at least
one window stack 700, 728, as shown in FIGS. 7A and 7B. A window
stack 700, 728 is a logical arrangement of active and/or inactive
windows for a multi-screen device. For example, the window stack
700, 728 may be logically similar to a deck of cards, where one or
more windows or desktops are arranged in order, as shown in FIGS.
7A and 7B. An active window is a window that is currently being
displayed on at least one of the touch sensitive displays 110, 114.
For example, windows 104 and 108 are active windows and are
displayed on touch sensitive displays 110 and 114. An inactive
window is a window that was opened and displayed but is now
"behind" an active window and not being displayed. In embodiments,
an inactive window may be for an application that is suspended, and
thus, the window is not displaying active content. For example,
windows 712, 716, 720, and 724 are inactive windows.
[0173] A window stack 700, 728 may have various arrangements or
organizational structures. In the embodiment shown in FIG. 7A, the
device 100 includes a first stack 760 associated with a first touch
sensitive display 110 and a second stack associated with a second
touch sensitive display 114. Thus, each touch sensitive display
110, 114 can have an associated window stack 760, 764. These two
window stacks 760, 764 may have different numbers of windows
arranged in the respective stacks 760, 764. Further, the two window
stacks 760, 764 can also be identified differently and managed
separately. Thus, the first window stack 760 can be arranged in
order from a first window 704 to a next window 720 to a last window
724 and finally to a desktop 722, which, in embodiments, is at the
"bottom" of the window stack 760. In embodiments, the desktop 722
is not always at the "bottom" as application windows can be
arranged in the window stack below the desktop 722, and the desktop
722 can be brought to the "top" of a stack over other windows
during a desktop reveal. Likewise, the second stack 764 can be
arranged from a first window 708 to a next window 712 to a last
window 716, and finally to a desktop 718, which, in embodiments, is
a single desktop area, with desktop 722, under all the windows in
both window stack 760 and window stack 764. A logical data
structure for managing the two window stacks 760, 764 may be as
described in conjunction with FIG. 8.
[0174] Another arrangement for a window stack 728 is shown in FIG.
7B. In this embodiment, there is a single window stack 728 for both
touch sensitive displays 110, 114. Thus, the window stack 728 is
arranged from a desktop 758 to a first window 744 to a last window
756. A window can be arranged in a position among all windows
without an association to a specific touch sensitive display 110,
114. In this embodiment, a window is in the order of windows.
Further, at least one window is identified as being active. For
example, a single window may be rendered in two portions 732 and
736 that are displayed on the first touch sensitive screen 110 and
the second touch sensitive screen 114. The single window may only
occupy a single position in the window stack 728 although it is
displayed on both displays 110, 114.
[0175] Yet another arrangement of a window stack 760 is shown in
FIGS. 7C through 7E. The window stack 760 is shown in three
"elevation" views. In FIG. 7C, the top of the window stack 760 is
shown. Two sides of the window stack 760 are shown in FIGS. 7D and
7E. In this embodiment, the window stack 760 resembles a stack of
bricks. The windows are stacked on each other. Looking from the top
of the window stack 760 in FIG. 7C, only the top most windows in
the window stack 760 are seen in different portions of the
composite display 764. The composite display 764 represents a
logical model for the entire display area of the device 100, which
can include touch sensitive display 110 and touch sensitive display
114. A desktop 786 or a window can occupy part or all of the
composite display 764.
[0176] In the embodiment shown, the desktop 786 is the lowest
display or "brick" in the window stack 760. Thereupon, window 1
782, window 2 782, window 3 768, and window 4 770 are layered.
Window 1 782, window 3 768, window 2 782, and window 4 770 only
occupy a portion of the composite display 764. Thus, another part
of the stack 760 includes window 8 774 and windows 5 through 7
shown in section 790. Only the top window in any portion of the
composite display 764 is actually rendered and displayed. Thus, as
shown in the top view in FIG. 7C, window 4 770, window 8 774, and
window 3 768 are displayed as being at the top of the display in
different portions of the window stack 760. A window can be
dimensioned to occupy only a portion of the composite display 760
to "reveal" windows lower in the window stack 760. For example,
window 3 768 is lower in the stack than both window 4 770 and
window 8 774 but is still displayed. A logical data structure to
manage the window stack can be as described in conjunction with
FIG. 8.
[0177] When a new window is opened, the newly activated window is
generally positioned at the top of the stack. However, where and
how the window is positioned within the stack can be a function of
the orientation of the device 100, the context of what programs,
functions, software, etc. are being executed on the device 100, how
the stack is positioned when the new window is opened, etc. To
insert the window in the stack, the position in the stack for the
window is determined and the touch sensitive display 110, 114 to
which the window is associated may also be determined. With this
information, a logical data structure for the window can be created
and stored. When user interface or other events or tasks change the
arrangement of windows, the window stack(s) can be changed to
reflect the change in arrangement. It should be noted that these
same concepts described above can be used to manage the one or more
desktops for the device 100.
[0178] A logical data structure 800 for managing the arrangement of
windows or desktops in a window stack is shown in FIG. 8. The
logical data structure 800 can be any data structure used to store
data whether an object, record, file, etc. The logical data
structure 800 can be stored in any type of database or data storage
system, regardless of protocol or standard. In embodiments, the
logical data structure 800 includes one or more portions, fields,
attributes, etc. that store data in a logical arrangement that
allows for easy storage and retrieval of the information.
Hereinafter, these one or more portions, fields, attributes, etc.
shall be described simply as fields. The fields can store data for
a window identifier 804, dimensions 808, a stack position
identifier 812, a display identifier 816, and/or an active
indicator 820. Each window in a window stack can have an associated
logical data structure 800. While only a single logical data
structure 800 is shown in FIG. 8, there may be more or fewer
logical data structures 800 used with a window stack (based on the
number of windows or desktops in the stack), as represented by
ellipses 824. Further, there may be more or fewer fields than those
shown in FIG. 8, as represented by ellipses 828.
[0179] A window identifier 804 can include any identifier (ID) that
uniquely identifies the associated window in relation to other
windows in the window stack. The window identifier 804 can be a
globally unique identifier (GUID), a numeric ID, an alphanumeric
ID, or other type of identifier. In embodiments, the window
identifier 804 can be one, two, or any number of digits based on
the number of windows that can be opened. In alternative
embodiments, the size of the window identifier 804 may change based
on the number of windows opened. While the window is open, the
window identifier 804 may be static and remain unchanged.
[0180] Dimensions 808 can include dimensions for a window in the
composite display 760. For example, the dimensions 808 can include
coordinates for two or more corners of the window or may include
one coordinate and dimensions for the width and height of the
window. These dimensions 808 can delineate what portion of the
composite display 760 the window may occupy, which may the entire
composite display 760 or only part of composite display 760. For
example, window 4 770 may have dimensions 880 that indicate that
the window 770 will occupy only part of the display area for
composite display 760, as shown in FIGS. 7c through 7E. As windows
are moved or inserted in the window stack, the dimensions 808 may
change.
[0181] A stack position identifier 812 can be any identifier that
can identify the position in the stack for the window or may be
inferred from the window's control record within a data structure,
such as a list or a stack. The stack position identifier 812 can be
a GUID, a numeric ID, an alphanumeric ID, or other type of
identifier. Each window or desktop can include a stack position
identifier 812. For example, as shown in FIG. 7A, window 1 704 in
stack 1 760 can have a stack position identifier 812 of 1
identifying that window 704 is the first window in the stack 760
and the active window. Similarly, window 6 724 can have a stack
position identifier 812 of 3 representing that window 724 is the
third window in the stack 760. Window 2 708 can also have a stack
position identifier 812 of 1 representing that window 708 is the
first window in the second stack 764. As shown in FIG. 7B, window 1
744 can have a stack position identifier 812 of 1, window 3,
rendered in portions 732 and 736, can have a stack position
identifier 812 of 3, and window 6 756 can have a stack position
identifier 812 of 6. Thus, depending on the type of stack, the
stack position identifier 812 can represent a window's location in
the stack.
[0182] A display identifier 816 can identify that the window or
desktop is associated with a particular display, such as the first
display 110 or the second display 114, or the composite display 760
composed of both displays. While this display identifier 816 may
not be needed for a multi-stack system, as shown in FIG. 7A, the
display identifier 816 can indicate whether a window in the serial
stack of FIG. 7B is displayed on a particular display. Thus, window
3 may have two portions 732 and 736 in FIG. 7B. The first portion
732 may have a display identifier 816 for the first display while
the second portion 736 may have a display identifier 816 for the
second display 114. However, in alternative embodiments, the window
may have two display identifier 816 that represent that the window
is displayed on both of the displays 110, 114, or a display
identifier 816 identifying the composite display. In another
alternate embodiment, the window may have a single display
identifier 816 to represent that the window is displayed on both of
the displays 110, 114.
[0183] Similar to the display identifier 816, an active indicator
820 may not be needed with the dual stack system of FIG. 7A, as the
window in stack position 1 is active and displayed. In the system
of FIG. 7B, the active indicator 820 can indicate which window(s)
in the stack is being displayed. Thus, window 3 may have two
portions 732 and 736 in FIG. 7. The first portion 732 may have an
active indicator 820 while the second portion 736 may also have an
active indicator 820. However, in alternative embodiments, window 3
may have a single active indicator 820. The active indicator 820
can be a simple flag or bit that represents that the window is
active or displayed.
[0184] An embodiment of a method 900 for creating a window stack is
shown in FIG. 9. While a general order for the steps of the method
900 is shown in FIG. 9. Generally, the method 900 starts with a
start operation 904 and ends with an end operation 928. The method
900 can include more or fewer steps or can arrange the order of the
steps differently than those shown in FIG. 9. The method 900 can be
executed as a set of computer-executable instructions executed by a
computer system and encoded or stored on a computer readable
medium. Hereinafter, the method 900 shall be explained with
reference to the systems, components, modules, software, data
structures, user interfaces, etc. described in conjunction with
FIGS. 1-8.
[0185] A multi-screen device 100 can receive activation of a
window, in step 908. In embodiments, the multi-screen device 100
can receive activation of a window by receiving an input from the
touch sensitive display 110 or 114, the configurable area 112 or
116, a gesture capture region 120 or 124, or some other hardware
sensor operable to receive user interface inputs. The processor may
execute the Task Management Module 540 may receive the input. The
Task Management Module 540 can interpret the input as requesting an
application task to be executed that will open a window in the
window stack.
[0186] In embodiments, the Task Management Module 540 places the
user interface interaction in the task stack 552 to be acted upon
by the Display Configuration Module 568 of the Multi-Display
Management Module 524. Further, the Task Management Module 540
waits for information from the Multi-Display Management Module 524
to send instructions to the Window Management Module 532 to create
the window in the window stack.
[0187] The Multi-Display Management Module 524, upon receiving
instruction from the Task Management Module 540, determines to
which touch portion of the composite display 760, the newly
activated window should be associated, in step 912. For example,
window 4 770 is associated with the a portion of the composite
display 764 In embodiments, the device state module 574 of the
Multi-Display Management Module 524 may determine how the device is
oriented or in what state the device is in, e.g., open, closed,
portrait, etc. Further, the preferences module 572 and/or
requirements module 580 may determine how the window is to be
displayed. The gesture module 576 may determine the user's
intentions about how the window is to be opened based on the type
of gesture and the location of where the gesture is made.
[0188] The Display Configuration Module 568 may use the input from
these modules and evaluate the current window stack 760 to
determine the best place and the best dimensions, based on a
visibility algorithm, to open the window. Thus, the Display
Configuration Module 568 determines the best place to put the
window at the top of the window stack 760, in step 916. The
visibility algorithm, in embodiments, determines for all portions
of the composite display, which windows are at the top of the
stack. For example, the visibility algorithm determines that window
3 768, window 4 770, and window 8 774 are at the top of the stack
760 as viewed in FIGS. 7C through 7E. Upon determining where to
open the window, the Display Configuration Module 568 can assign a
display identifier 816 and possibly dimensions 808 to the window.
The display identifier 816 and dimensions 808 can then be sent back
to the Task Management Module 540. The Task Management Module 540
may then assign the window a stack position identifier 812
indicating the windows position at the top of the window stack.
[0189] In embodiments, the Task Management Module 540 sends the
window stack information and instructions to render the window to
the Window Management Module 532. The Window Management Module 532
and the Task Management Module 540 can create the logical data
structure 800, in step 924. Both the Task Management Module 540 and
the Window Management Module 532 may create and manage copies of
the window stack. These copies of the window stack can be
synchronized or kept similar through communications between the
Window Management Module 532 and the Task Management Module 540.
Thus, the Window Management Module 532 and the Task Management
Module 540, based on the information determined by the
Multi-Display Management Module 524, can assign dimensions 808, a
stack position identifier 812 (e.g., window 1 782, window 4 770,
etc.), a display identifier 816 (e.g., touch sensitive display 1
110, touch sensitive display 2 114, composite display identifier,
etc,), and an active indicator 820, which is generally always set
when the window is at the "top" of the stack. The logical data
structure 800 may then be stored by both the Window Management
Module 532 and the Task Management Module 540. Further, the Window
Management Module 532 and the Task Management Module 540 may
thereinafter manage the window stack and the logical data
structure(s) 800.
[0190] An embodiment of a method 1000 for executing an application
is shown in FIG. 10. While a general order for the steps of the
method 1000 is shown in FIG. 10. Generally, the method 1000 starts
with a start operation 1004 and ends with an end operation 1040.
The method 1000 can include more or fewer steps or can arrange the
order of the steps differently than those shown in FIG. 10. The
method 1000 can be executed as a set of computer-executable
instructions executed by a computer system and encoded or stored on
a computer readable medium. Hereinafter, the method 1000 shall be
explained with reference to the systems, components, modules,
software, data structures, user interfaces, etc. described in
conjunction with FIGS. 1-9.
[0191] An application is executed, in step 1008. In embodiments, a
processor 204 receives indication to execute an application through
a user interface 110, 114, 112, 116, etc. The indication can be a
selection of an icon associated with the application. In other
embodiments, the indication can be a signal generated from another
application or event, such as receiving an e-mail or other
communication, which causes the application to execute
automatically. The processor 204 can retrieve the application 564a
from the application store 560 and begin its execution. In
executing the application 564a, a user interface can be generated
for a user.
[0192] In creating a user interface, the application 564a can begin
executing to create a manifest, in step 1012. A manifest is a data
structure that indicates the capabilities of the application 564a.
The manifest can generally be created from the resources in the
resources directory of the application 564a. The resources
directory can indicate the types of modes, locations, or other
indications for how the user interface should be configured in the
multi-display device 100. For example, the several modes can
include: "classic mode" that indicates that the application 564a is
capable of being displayed on a single screen or display 110/114;
"dual mode" that indicates that the application 564a is capable of
being displaced on two or more displays 110 and 114; "max mode"
that indicates the application 564a is capable of being displayed
or desires to be displayed across multiple displays 110 and 114;
and/or "bilateral mode" that indicates that the application 564a is
capable of being displayed on 2 or more displays 110 and 114 when
the device 100 is in easel mode (see FIGS. 1I and/or 1J).
[0193] Similarly, the manifest can include a desired or allowed
location within the displays 110/114. The possible locations can
include: "left", which indicates that the application 564a desires
to be displayed on the left display 110; "right", which indicates
that the application 564a desires to be displayed on the right
display 114; and/or other indications of where a location should be
including possible "top" and/or "bottom" of one or more of the
displays 110/114.
[0194] The application 564a can also indicate that it desires to be
displayed in a "minimum" window, which is a window that occupies
less than the full area of a single display. There may be other
modes possible for the application 564a, which may be included in
the manifest. The manifest can be sent from the application 564a to
the multi-display management module 524.
[0195] The multi-display management module 524 can receive the
manifest, in step 1016. In receiving the manifest, the
multi-display management module 524 can use the information to
determine a display binding for the application 564a. The manifest
may be received more than once from the application 564a based on
changes in how the application 564a is being executed, where the
application 564a desires to have a different display setting for
the new mode. Thus, with the manifest, the application 564a can
indicate to the multi-display management module 524 how best to or
what is the desired for the application's user interface. The
multi-display management module 524 can use the information in the
manifest to determine the best fit for the user interface depending
on how the device 100 is currently configured.
[0196] The multi-display management module 524 can determine the
application display mode, in step 1020. Here the multi-display
management module 524 receives or retrieves an indication of the
device 100 configuration. For example, the multi-display management
module 524 can determine if the device is in single display
configuration (see FIG. 6A, 6B, 6D, or 6E), dual display
configuration (see FIG. 6C or 6F), bilateral display configuration
(see FIG. 6G or 6H), or one of the other display configurations
(see FIG. 6I or 6J).
[0197] Further, the multi-display management module 524 can
determine if the device 100 is in a portrait or landscape
orientation. With this information, the multi-display management
module 524 may then consider the capabilities or preferences listed
for the application 564a in the received manifest. The combined
information may then allow the multi-display management module 524
to determine a display binding. The display binding can include
which of the one or more displays 110 and/or 114 are going to be
used to display the application's user interface(s). For example,
the multi-display management module 524 can determine that the
primary display 110, the secondary display 114, or all displays 110
and 114 of the device 100 will be used to display the application's
user interface.
[0198] The display modes setting can be assigned by creating or
setting a number in the display binding. This number can be "0" for
the primary display 110, "1" for the secondary display 114, or "2"
for dual displays 110 and 114. The display mode setting can also
indicate if the application 564a should display the user interface
in portrait or landscape orientation. Further, there may be other
settings, for example, providing a max mode or other setting that
may indicate how the application 564a is to be displayed on the
device. The display binding information is stored in a data
structure to create and set a binding, in step 1024.
[0199] The established display binding may then be provided, by the
multi-display management module 524, to the application 564a, in
step 1028. The provided display binding data structure can become
an attribute of the application 564a. An application 564a may
thereinafter store the display binding attribute in the memory of
the device 100. The application 564a with the display binding may
then generate a user interface based on this display binding. The
application 564a may be unaware of the position of the display
110/114 but may, from the display binding, be able to determine the
size of the available user interface to generate a window that has
particular characteristics for that display setting.
[0200] When a configuration change happens to the device 100, the
multi-display management module 524 may change the display binding
and send a new display binding to the application 564a. In
embodiments, the multi-display management module 524 may indicate
to the application 564a that there is a new binding or, in other
embodiments, the application 564a may request a display
configuration change or a new display binding, in which case the
multi-display management module 524 may send a new display binding
to the application 564a. Thus, the multi-display management module
524 can change the configuration of the display for the application
564a by altering the display binding for the application 564a
during the execution of that application 564a.
[0201] The multi-display management module 524 thereinafter, while
the application 564a is executing, can determine if there has been
a configuration change to the device 100, in step 1032. The
configuration change may be an event (see FIGS. 3A and 3B)
triggered by one or more signals from one or more hardware sensor
172, 176, etc. For example, if the device 100 is changed from
portrait 304 to landscape 340 orientation, Hall effect sensors 172
may indicate to the framework 520 that a display configuration
change has been made. Other changes may include transitions from a
single display 304 to a dual display configuration 320, by opening
the device. Other types of configuration changes may be possible
and may be signaled to alert the multi-display management module
524 of the configuration change. If a configuration change has been
made, the method 1000 proceeds YES to step 1020 so that the
multi-display management module 524 can determine new application
display mode settings and create a new display binding, which may
be passed to the application 564a. If there are no configuration
changes, the method 1000 precedes NO to step 1036.
[0202] In step 1036, a new application mode change may be
determined. Application mode changes can also occur in the
application 564a, and thus, the application 564a can determine if
something has occurred within the application 564a that requires a
different display setting. Modes are described hereinafter with
respect to FIG. 12. The mode change can create a desire to change
the display 110/114, and thus, require the application 564a to
generate a new manifest. If the application 564a does sense a mode
change or an event has occurred that requires a change in display
setting, the method 1000 proceeds YES back to step 1012. At step
1012, a new manifest or preference is created by the application
564a that may be received by the multi-display management module
524 to determine if the multi-display management module 524 can
change the display binding. If it is possible to provide the
preferred display, the multi-display management module 524 can
create a new display binding and send display binding back to the
application 564a and allow the application 564a to alter its user
interface. If no mode change is sensed or an event is not received
to create a mode change, the method 1000 proceeds NO to end
operation 1040.
[0203] An embodiment of a hierarchal data storage system 1100 is
shown in FIG. 11. The hierarchal data storage system 1100 can
include one or more data storage systems or devices either local or
remote to a mobile device 100. The device storage 1104, which is
the same or similar to memory 208 and storage 212 as described in
conjunction with FIG. 2, may be the local storage or top node of a
hierarchal data storage system 1100. The device 100 may be
connected to one or more external devices, for example, laptop
storage 1108. There may be other types of local storage, such as
computer desktops, peripheral data storage, or other types of
systems that may have a physical or wireless connection to the
device 100.
[0204] The data storage of the local system 1108 may be connected
to a network storage device 1112. The network storage device 1112
may be a peripheral data storage, a RAID system, or other type of
data storage that may be connected via a local area network or
other type of local network. This network storage device 1112 may
then be connected to a remote or wide area network 1116. Through
that wide area network or Internet 1116, the network storage device
1112 may be connected to distant storage 1120, 1124. Distant
storage 1120, 1124 can include Cloud storage or remote data storage
that is physically remote from the network storage device 1112.
[0205] A hierarchal definition 1200 of the storage described in
FIG. 11 is as shown in FIG. 12. The hierarchal designation or
definition 1200 may include a terminal node 1204, which may
represent the device storage 1104. There may be one or more
intermediate nodes 1208 and 1212 that may be connected to the
terminal node 1204. Intermediate nodes 1208 and 1212 may represent
local storage 1108. The intermediate storage 1208, 1212 may then be
connected to one or more distal nodes 1215 and 1220, which may
represent the network storage device 1112. One or more additional
nodes, 1224, 1228 may be connected to the distal node 1216 and
represent distant storage 1120 and 1124. The nodal diagram 1200 of
FIG. 12 represents a configuration of the storage system 1100 and
how storage system 1100 will be logically organized for the user of
the mobile device 100.
[0206] An embodiment of a system 1300 for creating a hierarchal
data storage system 1100 for the mobile device 100 is shown in FIG.
13. The system 1300 may include one or more modules which may be
provided in the device memory 208 and executed by the device
processor 204. These modules may be in addition to the software
modules that are described in conjunction with FIGS. 5A and 5B. The
system 1300 can include one or more of, but is not limited to, a
discovery module 1304, an indexer 1308, and a file system 1316.
[0207] The discovery module 1304 may discover the storage devices
as shown in FIG. 11. The discovery module 1304 may then send one or
more signals to and/or receive signals from a local storage 1108, a
network storage 1112, and distal storage 1120, 1124. The identities
of these discovered storage devices may then be provided to the
indexer 1308.
[0208] The indexer 1308 may access one or more rules in a rules
database 1312 to create the hierarchal index 1200 as shown in FIG.
12. The indexer 1308 may receive the information from the discovery
module 1304 and begin to create the hierarchal database 1100 and
the associated index 1200 to provide a single file system with
hierarchal nodes to the file system module 1316. The one or more
rules used by the indexer 1308 may include the following: a T node
(terminal node) may have multiple children nodes; a T node must
have at least one child node of type I (intermediate node); each
child node I can only have one parent or T node; each node type I
must have at least one child of type D (distal storage); each child
node D has only one parent of type I; nodes of type D may have any
number of children including no children at all; type A nodes
(additional storage) may have one or many parents; nodes of type A
may have any number of children including no children at all; each
parent of type A must be a type D or type A and while type A nodes
may have multiple parents, type A nodes may not have any parent of
type D or I. These rules can be stored in the rules database 1312
and provided to the indexer 1308 to index or arrange the storage
system in the proper hierarchal order. There may be more or fewer
rules than those listed here.
[0209] A file system 1316 receives the indexed storage designations
from the indexer 1308. The file system 1316 may then overlay this
information on the data represented by data storage 1320. Thus,
while there may be terminal, local, remote, and distant storage
1104, 1108, 1112, 1120, 1124, as shown in FIG. 11, the data may
appear to a user as a single system 1320 of hierarchal order where
the user can access different storage media through the hierarchal
storage system provided by file system 1316. This hierarchical data
storage provides a simple way for device 100 to provide a view of
the possible data storage that is in communication with device 100.
The file system 1316 may also provide a look up table 1324 which
describes the different nodes by type or string, and which allows
for searching the database 1124, as discussed hereinafter. The
lookup table 1324 provides a description of each node, designates
the node types, and the node's relationships in the hierarchy.
[0210] An embodiment of a system 1400 for monitoring the storage of
applications in the device 100 is shown in FIG. 14. The system 1400
allows for the assurance that only safe and secure applications are
executed during certain times when the device 100 is in
communication with networks that may be vulnerable or networks that
need to be protected from malicious functions or applications. The
device 100 may include one or more modules, which may be executed
by a processor 204 and which may be in addition to those modules
that were shown in FIGS. 5A and 5B.
[0211] The device 100 can include one or more of, but is not
limited to, a monitor module 1408 and an application controller
module 1424. The monitor module 1408 is operable to monitor the
installation and execution of applications on the device 100. As
applications are either installed or executed, the monitor 1408
produces or modifies a report 1412. The report 1412 provides for a
listing or an indication of the different types of applications
that are executed or installed on the device 100. The listing of
applications can include information to identify the applications
and indicate the applications' statuses. The application controller
1424 can control the execution or installation of applications on
the device 100. Thus, the application controller 1424 can access
the file system 1316 and either pause or prevent execution of an
application or can uninstall the applications as needed, per
direction by a censored network 1404.
[0212] The device 100 may at times be connected to a censored
network 1404. The censored network 1404 can be a secure, protected
network that requires a certain level of security for communication
with the device 100. Upon communicating or establishing a session
or connection with the censored network 1404, the monitor module
1408, of the device 100, may send the report 1412 to a censor
server 1416. The censor server 1416 can determine if there are
applications on a connected device 100 which may be malicious and
require attention by the device 100.
[0213] The report 1412 may be compared to a listing or database of
banned and/or allowed applications 1420. The database 1420 can have
information, identifiers, or other descriptions that help identify
applications and then an indication of whether those applications
are banned or allowed. The censor server 1416 can compare the
identifications, in the report 1412, with the determinations of
whether those applications are banned or allowed. Based on the
comparison, the censor server 1416 can send an indication to the
application controller 1424 of whether or not some applications
need to be uninstalled or need to be paused while the device 100 is
in communication with the censored network 1404. The listing,
provided by the censor server 1416, may indicate to the application
controller 1424 the identity of those applications, in the file
system 1316, and list the appropriate action to take (e.g.,
uninstall, pause, or do nothing).
[0214] An embodiment of a method 1500 for creating a hierarchal
data storage system is shown in FIG. 15. While a general order for
the steps of the method 1500 is shown in FIG. 15. Generally, the
method 1500 starts with a start operation 1504 and ends with an end
operation 1528. The method 1500 can include more or fewer steps or
can arrange the order of the steps differently than those shown in
FIG. 15. The method 1500 can be executed as a set of
computer-executable instructions executed by a computer system and
encoded or stored on a computer readable medium. Hereinafter, the
method 1500 shall be explained with reference to the systems,
components, modules, software, data structures, user interfaces,
etc. described in conjunction with FIGS. 1-14.
[0215] A device 100 may be connected to one or more local storage
systems 1108, in step 1508. The physical or wireless connection may
be made by the device 100 being docked or by the device 100 coming
within proximity of the local system and its associated data
storage 1108 and establishing a wireless connection. The discovery
module 1304 of the device 100 may then discover one or more of the
storage devices in communication with the device 100, in step 1512.
As such, the discovery module 1304 may send signals to the local
storage 1108, network storage 1112, or distant storage 1120, 1124.
Upon receiving indications back from the different storage devices
1108-1124, the discovery module 1304 can pass the information of
discovered data storage devices to the indexer 1308.
[0216] The indexer 1308 may then apply rules to the discovered
storage devices to create a hierarchical database, in step 1516.
The indexer 1308 may access rules and rules database 1312. The
rules may be read and then applied to the different storage based
on the type of storage that is discovered. The rules may then
create an index 1200 as indicated in FIG. 12. This index 1200 is
created, in step 1520, and can be passed to the file system 1316.
The file system 1316 may then provide a view, for the user, to the
hierarchal data storage 1320 based on the index scheme 1200, in
step 1524. The file system 1316 may be accessed by the user through
at least one user interface where the data can be managed, stored,
or retrieved through the hierarchal data storage 1320, in step
1524.
[0217] An embodiment of a method 1600 for controlling the execution
or installation of applications on a mobile device 100 is shown in
FIG. 16. While a general order for the steps of the method 1600 is
shown in FIG. 16. Generally, the method 1600 starts with a start
operation 1604 and ends with an end operation 1648. The method 1600
can include more or fewer steps or can arrange the order of the
steps differently than those shown in FIG. 16. The method 1600 can
be executed as a set of computer-executable instructions executed
by a computer system and encoded or stored on a computer readable
medium. Hereinafter, the method 1600 shall be explained with
reference to the systems, components, modules, software, data
structures, user interfaces, etc. described in conjunction with
FIGS. 1-15.
[0218] A device 100 may receive an indication to install an
application, in step 1608. A user can access one or more sites or
servers that allow for the reception and then installation of
applications to be stored and/or executed on the device 100. For
example, an iTunes store may include one or more applications that
may be stored and/or executed onto the device 100. The device 100
may install these applications on the device 100 and store the
application code and/or information in the storage file system
1320.
[0219] A monitor 1408 can monitor the execution or the installation
of the application, in step 1612. Thus, the monitor 1408 passively
looks for indications that an application is being
installed/executed. The monitoring may include reviewing tasks in a
memory stack of the device 100 looking for indications that an
installation/execution is occurring. Upon an indication that an
installation/execution is occurring, the monitor 1408 can identify
the application and create an entry in the report 1412 that
identifies the application being installed/executed. The report
1412 may also include some sort of description to indicate what the
application is or what the application does. Thus, the monitor 1408
can generate the report 1412, in step 1616.
[0220] Sometime thereinafter, the device 100 may connect wirelessly
or electrically with a censored network 1404, in step 1620. The
connection may be made and a session begun between the device 100
and the censored network 1404. Before any type of communication or
data exchange occurs, the monitor 1408 may send the report 1412 to
a censor server 1416, in step 1624. Thus, the censor server 1416
may prevent any type of communication or interaction between the
device 100 and the censored network 1404 until receiving the report
1412.
[0221] The censor server 1416 may then compare the report 1412 to a
listing of banned or allowed applications in database 1420. Thus,
any type of installed application may have enough information in
the report 1412 to be compared to the listing 1420 and to be
categorized either as allowed, banned, or neither allowed nor
banned, in step 1632. The categorization may also indicate whether
the applications are currently executing. The categorization and
any actions that may be needed with each of these types of
applications may then be sent to the application controller 1424
from the censor server 1416, in step 1636. Based on the category of
the application, the controller 1424 may uninstall the application,
stop the application's execution, or perform one or more other
actions, in step 1640.
[0222] For banned applications, the application controller 1424 may
uninstall the application from the device 100. For allowed
applications, the application controller 1424 may allow those
applications to continue to be stored on the device 100 and/or
execute on the device 100. For any applications that are in the
report 1412 but neither listed as a banned or allowed application
in the database 1420, the application controller 1424 may stop
their execution while the device 100 is connected with the censored
network 1404. This action prevents any of those non-listed
applications from conducting malicious functions on the censored
network 1404.
[0223] The actions conducted by the application controller 1404 may
be indicated to a user. Thus, the application controller 1424 can
optionally warn the user of applications being uninstalled or
applications being stopped, in step 1644. The warnings may be a
user interface indication, such as a pop-up window or screen, on
the display(s) 110, 114. The application controller 1424 may
provide what information is necessary for the user to identify what
is being done to which applications.
[0224] An embodiment of a method 1700 for searching in hierarchal
data storage system 1100 is shown in FIG. 17. While a general order
for the steps of the method 1700 is shown in FIG. 17. Generally,
the method 1700 starts with a start operation 1704 and ends with an
end operation 1752. The method 1700 can include more or fewer steps
or can arrange the order of the steps differently than those shown
in FIG. 17. The method 1700 can be executed as a set of
computer-executable instructions executed by a computer system and
encoded or stored on a computer readable medium. Hereinafter, the
method 1700 shall be explained with reference to the systems,
components, modules, software, data structures, user interfaces,
etc. described in conjunction with FIGS. 1-16.
[0225] A file system 1316 may gather received search terms/tags
from a user input, in step 1708. The search terms/tags may be
parsed by the file system 1316 to separate the search terms and
search tags (which can refer to a target device for the search), in
step 1712. The parsed search terms may then be used to search the
local device 1104, in step 1716. The search results may be
evaluated to determine if satisfactory results are provided from
the search, in steps 1720. Satisfactory results indicate whether or
not anything had been discovered by the file system 1316 in the
search of that storage system 1104.
[0226] If there are satisfactory results, the method 1700 proceeds
YES to step 1724 where the file system 1316 provides the results in
a user interface or other output to the user, in step 1724. If the
results are not satisfactory, the file system 1316 may compare the
previously parsed tag strings, to the index 1200. Thus, the file
system 1316 may attempt to compare tag strings to network devices
1104, 1108, 1112, or 1116 in the index 1200, in step 1728. The file
system 1316 may then determine if there is an exact match between a
tag string and a network storage device shown in the index 1200, in
step 1732.
[0227] If there is an exact match, the file system 1316 may conduct
a search on that network device 1104, 1108, 1112, or 1116 using the
search terms, in step 1736. The search results are then analyzed
again in step 1720 to determine if the results are satisfactory. If
the results are satisfactory, those results are provided, in step
1724. If there is no exact match between the tag strings and the
network devices 1104, 1108, 1112, or 1116 in the index 1200, the
method 1700 proceeds NO to step 1740, where the file system 1316
can apply rules to determine where to conduct the search (i.e., on
which network devices 1104, 1108, 1112, or 1116 to conduct the
search).
[0228] The file system 1316 may access a look up table 1324 that
indicates what network storage devices 1104, 1108, 1112, or 1116
are available. The look up table 1324 may also include priority
rules to indicate what should be searched. The priority rules may
include things such as connection speed, connection costs, data
bandwidth limitations, and other such indications of which local,
distal, or additional storage elements indicated in the index 1200
can be or should be searched. Once the appropriate data storage
device 1104, 1108, 1112, or 1116 is determined, the file system
1316 can conduct a search, in step 1744. The search terms are again
analyzed, in steps 1720, to determine if the results are
satisfactory. If those results are satisfactory, the method 1700
proceeds YES to step 1724 where those results are provided to the
user. If, in any case, there are unsatisfactory results from
searching local or distant storage, the method 1700 proceeds NO to
step 1748, where the file system 1316 may ask for additional
information from a user. This additional information may include
additional search terms or refinement of the tag strings to provide
a better search.
[0229] An embodiment of a system 1800 for conducting a remote wipe
of data on a remote device 100 is shown in FIG. 18. A remote wipe
function 1804 can wipe data from the storage 208, 212 of the device
100. The wipe function 1804 can be operated when a user loses or
misplaces their device 100. The wipe insures that sensitive data or
data on the device 100 does not become available to another person
who may have stolen or found the device 100 after it was lost. The
remote wipe function 1804 can access data 1820 to erase that data
after a signal 1824 to remove that data is received.
[0230] The system 1800 may also include a designator 1808 that can
receive data 1812. The designator 1808 can receive signals or
inputs from a user interface or other interactions to help
determine the type of data 1812 being received. If the data is
sensitive data, the sensitive data stored in a separate area in a
sensitive data storage 1820. If the data is non-sensitive, the data
may be stored in non-sensitive data store 1816. The segregation of
the types of data allow for the wipe function to only erase
sensitive data 1890. Thus, non-sensitive data 1816 may be
preserved. The segregation of the data ensures that if the device
100 is misplaced, and the remote wipe function 1804 is executed,
only sensitive data 1890 is erased while non-sensitive data 1816
may be preserved. In this way, if the device 100 is located, the
remote wipe function 1804 will not have erased all the data from
the device 100.
[0231] An embodiment of a method 1900 for managing data on a device
100 is shown in FIG. 19. The system 1800 can receive data, in step
1908. In embodiments, the designator 1808 receives data 1819. The
designator 1808 may then determine if the data is sensitive, in
step 1919. The determination of whether the data is sensitive may
be conducted based on input from a user to the designator 1808. In
other embodiments, the data is analyzed using data analysis
techniques to determine if the data may be sensitive. For example,
if the data includes information such as Social Security numbers,
bank accounts, or other types of personal information, the data may
be deemed as sensitive.
[0232] If the data is not sensitive, the designator 1808 may store
the data in a non-sensitive storage data store 1816, in step 1916.
However, if the data is deemed to be sensitive, the designator 1808
may store the data in the sensitive data store 1890, in step 1920.
Sometime thereinafter, a user or other system may send a remote
wipe signal 1894 to the wipe function 1804, in step 1924. The
signal 1894 can be sent from a remote system or device that may
communicate with the device 100. The signal may engage the wipe
function 1804, which will then erase the sensitive data store 1890,
in step 1928.
[0233] An embodiment of a charging system for the device 100 is
shown in environment 2000 or FIG. 20. The device 100 can include a
charging port, such as a USB connector, 2004. This connector 2004
may be positioned such that when the device 100 is inserted into a
holster 2008, the connector 2004 can mate with an associated
connector 2016 in the holster 2008. The holster 2008 may hold the
device on a belt or other type of implementation to allow the
device 100 to be readily available. Unlike common holsters, holster
2008 includes a power source 2012 that can provide power to the
device 100 through the connection 2016. The connection 2016 can be
a USB connector or other type of connector.
[0234] An embodiment of the electrical and software components 2100
that are associated with the environment 2000 are shown in FIG. 21.
The device 100 may include a battery 2104. The device 100 may be
connected to a holster power source 2108, which is associated with
the power source 2012. The holster power source 2108 can be a
battery, a solar cell, or other type of power source that may
provide power to the battery 2104. An energy equalizer module 2112
may execute to determine if the power in the battery and the
holster power source 2108 are equal or dissimilar. If the battery
power is less than the power provided by the holster power source
2108, the energy equalizer 2112 can cause the holster power 2108 to
power the battery 2104.
[0235] An embodiment of a method 2200 for providing power to a
device 100 through a holster is shown in FIG. 22. A device 100 may
be inserted into a holster, in step 2208. Here, the device 100 may
be set into the holster 2008 such that the connectors 2004 and 2016
mate.
[0236] An energy equalizer 2112 may then determine a charge on the
device battery 2104, in step 2212. The energy equalizer 2112 may
determine if there is an equal amount of energy or power available
in the battery 2104 and the holster power source 2108. Based on the
determination of the power levels, in step 2216, the energy
equalizer 2112 can determine if there is more charge in the holster
power source 2108 than the battery 2104. If there is no greater
charge in the holster power source 2108, the method 2200 proceeds
NO to a wait step 2224. Then, the energy equalizer 2189 may wait a
predetermined period of time before it determines the power source
levels again, in step 2216. The amount of time can be set by a user
or may function as a predetermined period of time, such as 10
seconds, 10 minutes, etcetera.
[0237] If there is more charge in a holster power source 2108 than
the battery 2104, method 2200 proceeds YES to charge the device
100, in step 2228. Thus, the energy equalizer 2112 ensures that
gates or other switches are engaged such that power may flow from
the holster power source 2108 to the battery 2104.
[0238] Furthermore, while the exemplary aspects, embodiments,
and/or configurations illustrated herein show the various
components of the system collocated, certain components of the
system can be located remotely, at distant portions of a
distributed network, such as a LAN and/or the Internet, or within a
dedicated system. Thus, it should be appreciated, that the
components of the system can be combined in to one or more devices,
such as a tablet-like device, or collocated on a particular node of
a distributed network, such as an analog and/or digital
telecommunications network, a packet-switch network, or a
circuit-switched network. It will be appreciated from the preceding
description, and for reasons of computational efficiency, that the
components of the system can be arranged at any location within a
distributed network of components without affecting the operation
of the system. For example, the various components can be located
in a switch such as a PBX and media server, gateway, in one or more
communications devices, at one or more users' premises, or some
combination thereof. Similarly, one or more functional portions of
the system could be distributed between a telecommunications
device(s) and an associated computing device.
[0239] Furthermore, it should be appreciated that the various links
connecting the elements can be wired or wireless links, or any
combination thereof, or any other known or later developed
element(s) that is capable of supplying and/or communicating data
to and from the connected elements. These wired or wireless links
can also be secure links and may be capable of communicating
encrypted information. Transmission media used as links, for
example, can be any suitable carrier for electrical signals,
including coaxial cables, copper wire and fiber optics, and may
take the form of acoustic or light waves, such as those generated
during radio-wave and infra-red data communications.
[0240] Also, while the flowcharts have been discussed and
illustrated in relation to a particular sequence of events, it
should be appreciated that changes, additions, and omissions to
this sequence can occur without materially affecting the operation
of the disclosed embodiments, configuration, and aspects.
[0241] In yet another embodiment, the systems and methods of this
disclosure can be implemented in conjunction with a special purpose
computer, a programmed microprocessor or microcontroller and
peripheral integrated circuit element(s), an ASIC or other
integrated circuit, a digital signal processor, a hard-wired
electronic or logic circuit such as discrete element circuit, a
programmable logic device or gate array such as PLD, PLA, FPGA,
PAL, special purpose computer, any comparable means, or the like.
In general, any device(s) or means capable of implementing the
methodology illustrated herein can be used to implement the various
aspects of this disclosure. Exemplary hardware that can be used for
the disclosed embodiments, configurations and aspects includes
computers, handheld devices, telephones (e.g., cellular, Internet
enabled, digital, analog, hybrids, and others), and other hardware
known in the art. Some of these devices include processors (e.g., a
single or multiple microprocessors), memory, nonvolatile storage,
input devices, and output devices. Furthermore, alternative
software implementations including, but not limited to, distributed
processing or component/object distributed processing, parallel
processing, or virtual machine processing can also be constructed
to implement the methods described herein.
[0242] In yet another embodiment, the disclosed methods may be
readily implemented in conjunction with software using object or
object-oriented software development environments that provide
portable source code that can be used on a variety of computer or
workstation platforms. Alternatively, the disclosed system may be
implemented partially or fully in hardware using standard logic
circuits or VLSI design. Whether software or hardware is used to
implement the systems in accordance with this disclosure is
dependent on the speed and/or efficiency requirements of the
system, the particular function, and the particular software or
hardware systems or microprocessor or microcomputer systems being
utilized.
[0243] In yet another embodiment, the disclosed methods may be
partially implemented in software that can be stored on a storage
medium, executed on programmed general-purpose computer with the
cooperation of a controller and memory, a special purpose computer,
a microprocessor, or the like. In these instances, the systems and
methods of this disclosure can be implemented as program embedded
on personal computer such as an applet, JAVA.RTM. or CGI script, as
a resource residing on a server or computer workstation, as a
routine embedded in a dedicated measurement system, system
component, or the like. The system can also be implemented by
physically incorporating the system and/or method into a software
and/or hardware system.
[0244] Although the present disclosure describes components and
functions implemented in the aspects, embodiments, and/or
configurations with reference to particular standards and
protocols, the aspects, embodiments, and/or configurations are not
limited to such standards and protocols. Other similar standards
and protocols not mentioned herein are in existence and are
considered to be included in the present disclosure. Moreover, the
standards and protocols mentioned herein and other similar
standards and protocols not mentioned herein are periodically
superseded by faster or more effective equivalents having
essentially the same functions. Such replacement standards and
protocols having the same functions are considered equivalents
included in the present disclosure.
[0245] The present disclosure, in various aspects, embodiments,
and/or configurations, includes components, methods, processes,
systems and/or apparatus substantially as depicted and described
herein, including various aspects, embodiments, configurations
embodiments, subcombinations, and/or subsets thereof. Those of
skill in the art will understand how to make and use the disclosed
aspects, embodiments, and/or configurations after understanding the
present disclosure. The present disclosure, in various aspects,
embodiments, and/or configurations, includes providing devices and
processes in the absence of items not depicted and/or described
herein or in various aspects, embodiments, and/or configurations
hereof, including in the absence of such items as may have been
used in previous devices or processes, e.g., for improving
performance, achieving ease and\or reducing cost of
implementation.
[0246] The foregoing discussion has been presented for purposes of
illustration and description. The foregoing is not intended to
limit the disclosure to the form or forms disclosed herein. In the
foregoing Detailed Description for example, various features of the
disclosure are grouped together in one or more aspects,
embodiments, and/or configurations for the purpose of streamlining
the disclosure. The features of the aspects, embodiments, and/or
configurations of the disclosure may be combined in alternate
aspects, embodiments, and/or configurations other than those
discussed above. This method of disclosure is not to be interpreted
as reflecting an intention that the claims require more features
than are expressly recited in each claim. Rather, as the following
claims reflect, inventive aspects lie in less than all features of
a single foregoing disclosed aspect, embodiment, and/or
configuration. Thus, the following claims are hereby incorporated
into this Detailed Description, with each claim standing on its own
as a separate preferred embodiment of the disclosure.
[0247] Moreover, though the description has included description of
one or more aspects, embodiments, and/or configurations and certain
variations and modifications, other variations, combinations, and
modifications are within the scope of the disclosure, e.g., as may
be within the skill and knowledge of those in the art, after
understanding the present disclosure. It is intended to obtain
rights which include alternative aspects, embodiments, and/or
configurations to the extent permitted, including alternate,
interchangeable and/or equivalent structures, functions, ranges or
steps to those claimed, whether or not such alternate,
interchangeable and/or equivalent structures, functions, ranges or
steps are disclosed herein, and without intending to publicly
dedicate any patentable subject matter.
* * * * *