Operating system supporting mixed 2D, stereoscopic 3D and multi-view 3D displays
Operating systems are described that interface applications and display screens capable of displaying two-dimensional and three-dimensional content. In one aspect, an operating system includes an application programming interface (API), a display driver interface, and a display driver. The API enables one or more applications to deliver requests that define a screen region and either a two-dimension indicator or a three-dimension indicator. The display driver interface passes configuration commands corresponding to the requests. The display driver is associated with a display screen. The display driver receives the configuration commands and responds by generating screen control signals to adjust the display screen to support the screen region.
Latest Broadcom Corporation Patents:
This application claims the benefit of U.S. Provisional Application No. 61/291,818, filed on Dec. 31, 2009, which is incorporated by reference herein in its entirety; and
This application claims the benefit of U.S. Provisional Application No. 61/303,119, filed on Feb. 10, 2010, which is incorporated by reference herein in its entirety.
This application is also related to the following U.S. Patent Applications, each of which also claims the benefit of U.S. Provisional Patent Application Nos. 61/291,818 and 61/303,119 and each of which is incorporated by reference herein:
U.S. patent application Ser. No. 12/845,409, titled “Display With Adaptable Parallax Barrier,” filed Jul. 28, 2010;
U.S. patent application Ser. No. 12/845,440, titled “Adaptable Parallax Barrier Supporting Mixed 2D And Stereoscopic 3D Display Regions,” filed Jul. 28, 2010;
U.S. patent application Ser. No. 12/845,461, titled “Display Supporting Multiple Simultaneous 3D Views,” filed Jul. 28, 2010;
U.S. patent application Ser. No. 12/774,307, titled “Display with Elastic Light Manipulator,” filed May 5, 2010;
U.S. patent application Ser. No. 12/982,020, titled “Backlighting Array Supporting Adaptable Parallax Barrier,” filed on same date herewith;
U.S. patent application Ser. No. 12/982,140, titled “Internet Browser And Associated Content Definition Supporting Mixed Two And Three Dimensional Displays,” filed on same date herewith;
U.S. patent application Ser. No. 12/982,173, titled “Application Programming Interface Supporting Mixed Two And Three Dimensional Displays,” filed on same date herewith; and
U.S. patent application Ser. No. 12/982,156, titled “Programming Architecture Supporting Mixed Two And Three Dimensional Displays,” filed on same date herewith.
BACKGROUND OF THE INVENTION1. Field of the Invention
The present invention relates to operating systems associated with three-dimensional image displays.
2. Background Art
Images may be generated for display in various forms. For instance, television (TV) is a widely used telecommunication medium for transmitting and displaying images in monochromatic (“black and white”) or color form. Conventionally, images are provided in analog form and are displayed by display devices in two-dimensions. More recently, images are being provided in digital form for display in two-dimensions on display devices having improved resolution (e.g., “high definition” or “HD”). Even more recently, images capable of being displayed in three-dimensions are being generated.
Conventional displays may use a variety of techniques to achieve three-dimensional image viewing functionality. For example, various types of glasses have been developed that may be worn by users to view three-dimensional images displayed by a conventional display. Examples of such glasses include glasses that utilize color filters or polarized filters. In each case, the lenses of the glasses pass two-dimensional images of differing perspective to the user's left and right eyes. The images are combined in the visual center of the brain of the user to be perceived as a three-dimensional image. In another example, synchronized left eye, right eye LCD (liquid crystal display) shutter glasses may be used with conventional two-dimensional displays to create a three-dimensional viewing illusion. In still another example, LCD display glasses are being used to display three-dimensional images to a user. The lenses of the LCD display glasses include corresponding displays that provide images of differing perspective to the user's eyes, to be perceived by the user as three-dimensional.
Some displays are configured for viewing three-dimensional images without the user having to wear special glasses, such as by using techniques of autostereoscopy. For example, a display may include a parallax barrier that has a layer of material with a series of precision slits. The parallax barrier is placed proximal to a display so that a user's eyes each see a different set of pixels to create a sense of depth through parallax. Another type of display for viewing three-dimensional images is one that includes a lenticular lens. A lenticular lens includes an array of magnifying lenses configured so that when viewed from slightly different angles, different images are magnified. Displays are being developed that use lenticular lenses to enable autostereoscopic images to be generated.
As such, many types of display devices exist that are capable of displaying three-dimensional images, and further types are being developed. Different types of displays that enable three-dimensional image viewing may have different capabilities and attributes, including having different depth resolutions, being configured for three-dimensional image viewing only, being switchable between two-dimensional image viewing and three-dimensional image viewing, and further capabilities and attributes. Furthermore, different types of applications may be configured to provide and/or interact with the displays to provide either two-dimensional or three-dimensional image content. However, each application may not be directly compatible with each type of display device.
BRIEF SUMMARY OF THE INVENTIONMethods, systems, and apparatuses are described for an operating system that interfaces users and applications with display devices that have three-dimensional image generating capability, substantially as shown in and/or described herein in connection with at least one of the figures, as set forth more completely in the claims.
The accompanying drawings, which are incorporated herein and form a part of the specification, illustrate the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the pertinent art to make and use the invention.
The present invention will now be described with reference to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements. Additionally, the left-most digit(s) of a reference number identifies the drawing in which the reference number first appears.
DETAILED DESCRIPTION OF THE INVENTION I. IntroductionThe present specification discloses one or more embodiments that incorporate the features of the invention. The disclosed embodiment(s) merely exemplify various aspects of the invention. The scope of the invention is not limited to the disclosed embodiment(s). The invention is defined by the claims appended hereto.
References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
Furthermore, it should be understood that spatial descriptions (e.g., “above,” “below,” “up,” “left,” “right,” “down,” “top,” “bottom,” “vertical,” “horizontal,” etc.) used herein are for purposes of illustration only, and that practical implementations of the structures described herein can be spatially arranged in any orientation or manner.
II. Exemplary EmbodimentsEmbodiments of the present invention relate to operating systems that interface users and applications with display devices that have three-dimensional image display capability. Numerous types of applications and display devices may be interfaced by the operating system. For example, the display devices may include one or more light manipulators, such as parallax barriers and/or lenticular lenses, to deliver 3D media content in the form of images or views to the eyes of the viewers. Other types may include display devices with 3D display pixel constructs that may or may not employ such light manipulators. When used, light manipulators may be fixed or dynamically modified to change the manner in which the views are delivered. For instance, embodiments enable light manipulators that are adaptable to accommodate a changing viewer sweet spot, switching between two-dimensional (2D), stereoscopic three-dimensional (3D), and multi-view 3D views, as well as the simultaneous display of 2D, stereoscopic 3D, and multi-view 3D content. With regard to parallax barriers, example features that may be dynamically modified include one or more of a number of slits in the parallax barriers, the dimensions of each slit, the spacing between the slits, and the orientation of the slits. Slits of the parallax barriers may also be turned on or off in relation to certain regions of the screen such that simultaneous mixed 2D, stereoscopic 3D, and multi-view 3D presentations can be accommodated. Similarly, a lenticular lens may be dynamically modified, such as by modifying a width of the lenticular lens, to modify delivered images.
The following subsections describe numerous exemplary embodiments of the present invention. For instance, the next subsection describes embodiments for operating systems, followed by a subsection that describes embodiments for interfacing applications with display devices, a subsection that describes embodiments for interfacing users with display devices, a subsection that describes operating system start up embodiments, a subsection that describes example display environments, and a subsection that describes example electronic devices.
It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made to the embodiments described herein without departing from the spirit and scope of the invention. Thus, the breadth and scope of the present invention should not be limited by any of exemplary embodiments described herein.
A. Example Operating System EmbodimentsIn embodiments, operating systems that provide native support for the display of mixed content are provided. For example, in one embodiment, an operating system comprises a graphical user interface (GUI) in which video content, such as that produced by executing an application, can be displayed in a window or frame. The operating system enables one or more parameters to be associated with the window or frame, wherein the parameters can specify, for example, one or more of: a type of video content to be displayed within the window or frame (e.g., 2D, stereoscopic 3D, or a particular type of multi-view 3D), a desired orientation of the video content within the window or frame, a brightness/contrast to be associated with the window or frame, and/or a video resolution to be associated with the window or frame. The parameters to be associated with a window or frame may be specified programmatically or determined dynamically at run-time. The parameters may also be modified at run-time by a user through a user control interface provided by the operating system. The operating system is further configured to cause one or more function calls to be placed to a graphics API (application programming interface) or device driver so that a window is opened on the display and the video content is presented therein in a manner that is consistent with the associated parameters.
For instance,
OS 106 provides a platform on which programs may be executed. OS 106 may be implemented in software (e.g., computer programs and/or data) that runs on a device. OS 106 manages hardware 108, provides common services, enables execution of application(s) 104, and enables application(s) 104 to access hardware 108. Application(s) 104 may call OS 106 and/or be interrupted by OS 106 for various reasons. OS 106 may include a user interface, such as a graphical user interface (GUI), which a user may interact with to access application(s) 104 and/or hardware 108. In some cases, application(s) 104 may interact directly with hardware 108. Hardware 108 may include one or more hardware components, such as one or more processors (e.g., a central processing unit) and/or memory devices (e.g., random access memory (RAM)), disk drives, printers, one or more display devices, a keyboard, a mouse, etc. Application(s) 104 may be implemented according to any suitable programming languages. Example description of implementations of programming languages for applications 104 and other applications described herein is provided in pending U.S. patent application Ser. No. 12/982,156, titled “Programming Architecture Supporting Mixed Two And Three Dimensional Displays,” filed on same date herewith, which is incorporated by reference herein in its entirety, although application(s) 104 and further applications described herein are not limited to such implementations.
As shown in
For instance,
System 200 may be implemented in one or more devices. For example, in one embodiment, application(s) 104, OS 106, and display device 204 may be implemented in a common electronic device 206 accessed by a user, such as a mobile computing device (e.g., a handheld computer, a laptop computer, a notebook computer, a tablet computer (e.g., an Apple iPad™), a netbook, etc.), a mobile phone (e.g., a cell phone, a smart phone), a mobile email device, some types of televisions, etc. In another embodiment, as shown in
In embodiments, display device 204 may be one of a variety of display devices capable of displaying two-dimensional and/or three-dimensional images/content. For instance,
OS 106 may be implemented in various ways to interface a user and application(s) 104 with display devices that are capable of displaying two-dimensional content and/or three-dimensional content. For instance,
As shown in
API 404 is an interface implemented in software (e.g., computer program code or logic) that is configured to interface one or more applications (e.g., application(s) 104 of
Kernel 406 is a central component of OS 400 that is configured to bridge applications and hardware. Kernel 406 may manage resources of device 412, and enable applications to run and to use the resources. For instance, kernel 406 may allocate running applications to one or more processors of device 412, may allocate memory to the applications, and may allocate requests from applications to perform I/O (input/output) operations with regard to hardware resources associated with device 412, such as a keyboard, mouse, disk drives, printers, and displays. For example, as shown in
Display driver(s) 408 are one or more display drivers that may be included in operating system 400. A display driver 408 may be implemented in software, and enables applications (e.g., higher-level application code) to interact with a display device. Each display driver of display driver(s) 408 is typically display device-specific, although some display drivers may be capable of driving multiple types of display devices. Due to the presence of display driver(s) 408, programmers can write and input higher-level application code to API 404 independently of the specific display device associated with device 412, enabling the application code and display device to interface in a standard way. Each type of display device typically is controlled by its own display device-specific commands. In contrast, most applications communicate with display devices according to high-level device-generic commands. A display driver 408 accepts the generic high-level commands (via API 404 and display driver interface 410), and breaks them into a series of low-level display device-specific commands, as used by the particular display device. In an embodiment, a display driver 408 may be configured to filter out one or more parameters received with a command that is/are incompatible with the display device screen coupled to device 412.
As such, using a display driver 408, multiple applications that communicate using standard high-level commands can access a particular display device through OS 400. Furthermore, OS 400 may include multiple display drivers 408 to enable multiple applications to communicate with multiple corresponding display devices.
As described above, OS 400 of
Display system 450 is an example of a display system that is capable of displaying mixed 2D and 3D content (e.g., via mixed 2D/3D supporting logic 110). As shown in
2D display 418a, 3D display with 2D mode 418b, and regionally configurable 2D/3Dx display 418c are example types of display devices that may be interfaced with applications by OS 400. One or more of displays 418a-418c may be separately coupled to OS 400 (via display circuitry 416a-416c) or simultaneously coupled to OS 400. 2D display 418a is an example of 2D display device 304 of
First-third application programs 414a-414c are examples of application(s) 104 of
API supporting regional 2D/3Dx 428 is an example of API 404 of
User input interfaces 420 are an example of user input interface 402 of
2D, 3Dx & mixed display driver interface 422 is an example of display driver interface 410 of
Shell operations 424 may be present in OS 400 to control and/or enable user configuration of environmental properties, such as the 2D and/or 3D display configuration of an environmental background, of desktop icons, of displayed windows, etc. In embodiments, shell operations 424 may be implemented in hardware, software, firmware, or any combination thereof, including as a shell operations module. Examples of shell operations 424 are described elsewhere herein.
Mixed 2D and 3Dx, & mixed 3Dx and 3Dy translation services 426 may be present in OS 400 to provide for translation of received content (e.g., from applications 414a-414c) from a first dimensionality to a second dimensionality. For instance, translation services 426 may be configured to translate received 3D content to 2D content, such as when an application provides 3D content, and 2D display 418a is the target display (e.g., the target display is not capable of displaying 3D content). In another example, translation services 426 may be configured to translate a first type of 3D content to a second type of 3D content, such as when an application provides regional 2D and/or 3D content, and 3Dx display with 2D mode is the target display (e.g., the target display is not capable of displaying content regionally), and/or to translate 3D content having a first number “x” of cameras (e.g., 3D-8 content) to 3D content having a second number “y” of cameras (e.g., 3D-4 content), if the target display does not support “x” camera views. Still further, translation services 426 may be configured to translate 2D content to 3D content, and/or may be able to perform other forms of content translations. Example embodiments for mixed 2D and 3Dx, & mixed 3Dx and 3Dy translation services 426 (e.g., translators) are described elsewhere herein.
Display circuitry 416a-416c may have the form of hardware, software, firmware, or any combination thereof, such as having the form of a graphics card, circuitry etc. Display circuitry 416a-416c may be present to interface OS 400 with displays 418a-418c, respectively. Display circuitry 416a-416c may receive content signals and control signals from OS 400, and may be configured to generate drive signals to drive displays 418a-418c, respectively. Examples of display circuitry (e.g., drive circuits) are described elsewhere herein.
As shown in
The embodiments of display system 450 of
As described above, API 404 receives requests and content from applications for display devices associated with device 412.
Flowchart 500 begins with step 502. In step 502, a command directing display of content on a screen is received from an application. For example, as shown in
In step 504, the command is responded to by sending a control signal that places the screen in a display mode corresponding to the content. For example, as shown in
Note that request 608 may have any suitable format, as defined by API 404. For instance,
For example, request 700 may be a request from application 604 to open a frame or window for display by screen 620 of display device 606. In such an example, command 702 may be an “open frame” or “open window” command. Furthermore, one or more parameters 704 may be present to define attributes of the frame/window to be opened. For instance, one or more parameters 704 may be present to define a size of a region of screen 620 in which the frame or window is to be opened. For instance, parameters 704a-704d may be row, column, width, and height parameters, respectively, where the row and column parameters (window position parameters) define coordinates of an upper left corner of the window to be opened, and the width and height parameters (window size parameters) define the width and height (e.g., in pixels or other measure) of the window to be opened. Furthermore, a parameter may be present to define whether the window to be opened is to display two-dimensional content or three-dimensional content. For instance, parameter 704e may be a 2D/3D indicator parameter that contains either a two-dimensional indicator or a three-dimensional indicator to define the window to be opened as displaying two-dimensional content or three-dimensional content, respectively.
The “open window” command may include further parameters 704, such as a window resolution parameter, a window orientation parameter (e.g., whether image content is to be displayed vertically or rotated by 90 degrees or by other amount), a three-dimensional display type parameter, a subframe/full frame/child window parameter, a freeform window parameter (e.g., whether the window may have a non-rectangular shape), a three-dimensional content source indication parameter, etc. For example, in an embodiment, where a three-dimensional indicator is present in request 700, a three-dimensional display type parameter may be present to define a number of image pairs to be provided to the window to be opened, corresponding to a number of three-dimensional views to be provided by the window (e.g., whether the window is not multiview or is multiview 4-3D, 16-3D, etc.). Furthermore, a three-dimensional display type parameter may be present to define a depth of three-dimensionality to be provided in the window to be opened. In another example, a parameter may be provided to indicate whether the window to be opened is to provide three-dimensional content and is to be adaptable based on factors such as bandwidth (e.g., increasing or decreasing a number of camera views that are displayed based on a data rate of incoming content), etc.
In a similar manner as the “open window” command, further commands may be defined by request 700. In further examples, request 700 may be a request from application 604 to close a window displayed in screen 620, to move a window displayed in screen 620, to resize a window displayed in screen 620, to rotate a window displayed in screen 620, or other type of request. As such, command 702 may be a “close window” command, and one of parameters 704 may include a window handle identifying the window to be closed. In another example, command 702 may be “move window” command, and parameters 704 may include row and column parameters that define the new upper left corner of the window being moved. In another example, command 702 may be “resize window” command, and parameters 704 may include width and height parameters that define the new width and height of the window being resized. In still another example, command 702 may be “rotate window” command, and parameters 704 may include an indication (e.g., in degrees) of an amount by which the window is to be rotated.
In further embodiments, command 702 and parameters 704 may have other forms to define further functions, as would be apparent to persons skilled in the relevant art(s). For example, in embodiments, request 700 may be a request for information regarding an open window. For instance, command 702 may define a request for a window type (e.g., 2D or 3D), a window handle, a window position, an indication of the capabilities of the window and/or screen, and/or other window or screen characteristic. Another example command 702 may define a request to OS 400 for capabilities of screen 620/display device 606 so that applications may learn of window/screen capabilities prior to attempting to open and populate windows. Further commands 702 and parameters 704 may be defined as directed to frames, objects, and/or other display elements, having similar parameters as those defined above for windows, or having other parameters.
Referring back to
As described above, multiple applications may simultaneously interface with a display device through OS 400. For example,
Flowchart 800 begins with step 802. In step 802, a first command is received from a first application directing display of two-dimensional content within a first region of the screen. For example, as shown in
In step 804, the first command is responded to by sending a first control signal that places the screen in a two-dimensional mode within the first region. For instance, as shown in
In step 806, a second command is received from a second application directing display of three-dimensional content within a second region of the screen. For example, as shown in
In step 808, the second command is responded to by sending a second control signal that places the screen in a three-dimensional mode within the second region. For instance, as shown in
As such, according to flowchart 800, multiple applications may simultaneously direct the display of two-dimensional or three-dimensional content within corresponding regions of screen 620. Furthermore, in embodiments, the display on screen 620 of different types of three-dimensional content (e.g., different resolutions, different numbers of image pairs, different stereoscopic depths, etc.) may be directed by multiple applications simultaneously. In embodiments, any number of different types of two-dimensional and three-dimensional content may be displayed in any number of regions of screen 620.
For instance,
In another example,
In another example,
Desktop 1222 includes a background having a 2D sky area 1201 and a 3D grass region 1203 that appears to stretch far into the distance. Desktop 1222 further includes unselected icons 1213, 1215, and 1219 of random or arbitrary shapes which appear floating in mid-air in local 3D. Icons 1213 and 1219 may contain OS generated content, and icon 1215 may contain 3D content delivered live via an external server, for example. In accordance with this example, the 3D content in icon 1215 may be actively changing and/or moving around. Desktop 1222 further includes a selected icon 1217 which seems to be moving closer then farther away in a cycle, while the window 1225 that was opened and relates to selected icon 1217 has a boundary region 1211 that seems to actively change in synchrony therewith.
Desktop 1222 also includes an active, moving 2D or 3D object 1221 that has a non-rectangular boundary. Desktop 1222 further includes a pointer 1223 used to assist a viewer input and display control architecture 1229 that may be anything illustrated and discussed in the present application, and through which screen region configuration commands (command 1, command 2, etc.) can be accessed via, for example, a right click that opens a pop-up window 1225 or other type of window. Desktop 1222 also includes a rectangular window 1205 with 3D icons 1207 that may move and present local or delivered content, a 2D or 3D content screen 1209 (2D text or 3D movie for example originating remotely), and a 2D or 3D boundary 1211 as mentioned above related to the selected icon 1217.
Viewer input and display control architecture 1229 represents one or more of any type of integrated and multiple-housing display and viewer control architectures. For instance, architecture 1229 may include one or more user input interfaces configured to receive user input. Examples of a user input interface include but are not limited to a remote control device, a traditional computer input device such as a keyboard or mouse, a touch screen, a gamepad or other type of gaming console input device, or one or more sensors including but not limited to video cameras, microphones and motion sensors. Such user input interface may generate an input signal that specifies settings for regionally adjustable characteristics of a screen assembly for presentation of the instances of content in the respective areas of desktop 1222, for example, based on the user input.
The visual elements of desktop 1222, including 2D and/or 3D aspects, sizes, movement, brightness, etc., of 2D sky area 1201, 3D grass region 1203, window 1205, content screen 1209, icons 1213, 1215, 1217, and 1219, object 1221, pop-up window 1225, etc., may be configured by applications providing commands through operating systems and/or OS commands generated by user interaction (e.g., with user input interfaces 420), including commands for opening and tailoring windows, frame 3D/2D characteristics, depth, user interaction, supporting 2D/3D graphic objects, etc.
It is noted that the examples of
For example, in an embodiment, display drivers of OS 400 may be configured to translate types of content that are not supported by a display device associated with the display drivers to supported types of content.
First translator 1302 is configured to translate received 3D data to 2D data for display by a display device. For example, as shown in
Similarly, second translator 1304 is configured to translate received 3D data of a first 3D content type to 3D data of a second 3D content type for display by a display device. As shown in
First translator 1302 may be configured in various ways to translate received 3D data to 2D data. For instance, in an embodiment, three-dimensional data 1306 may be received as a stream of right image data and left image data. First translator 1302 may be configured to combine the right and left image data into two-dimensional image data that defines a stream of two-dimensional images that may be output as two-dimensional data 1308. In another embodiment, first translator 1302 may be configured to select the right image data or the left image data to be output as two-dimensional data 1308, while the other of the right image data or left image data is not used. In further embodiments, first translator 1302 may translate received 3D data to 2D data in other ways.
Second translator 1304 may be configured in various ways to translate 3D data of a first 3D content type to 3D data of a second 3D content type. For instance, second translator 1304 may translate a first 3D multiview type (e.g., 3D-16) to a second 3D multiview type (e.g., 3D-4) or to a single 3D view. In such an embodiment, second translator 1304 may not pass extra left-right image pairs from first-type three-dimensional data 1310 to second-type three-dimensional data 1312. In further embodiments, second translator 1304 may translate 3D data in other ways.
Referring back to flowchart 500 of
Flowchart 1400 begins with step 1402. In step 1402, a response is received from the screen regarding the control signal. For example, as shown in
In step 1404, the response is provided to the application. For example, display driver 618 may forward response 1502 to display driver interface 410 as response 1504, and display driver interface 410 may forward response 1504 to API 404 as response 1506. Alternatively, display driver 618 may forward response 1502 directly to API 404. API 404 receives response 1506, and provides response 1506 to application 604 as response 1508.
Response 1508 may include any information suitable for a response by display device 606 to a control signal generated in response to a request 608. For example, if request 608 included an “open window” command, response 1508 may indicate whether the window was successfully opened, and if so, may include a window handle for the opened window. Furthermore, response 1506 may indicate whether a “move window” command, a “close window” command, a “move window” command, a “resize window” command, a “rotate window” command, or other command included in a request 608 was successful.
C. Example User Input Interface EmbodimentsAs described above, user input interface 402 receives user input to enable persons to interact with display devices associated with device 412. For example, via user input interface 402, a user may be enabled to move displayed graphical objects (e.g., icons, windows, etc.), may be able to modify (e.g., rotate, resize, etc.) displayed graphical objects, to interact with displayed controls, etc. User input interface 402 may provide a command-line interface, a GUI, and/or other interface with which the user can interact. In embodiments, user input interface 402 may enable users to adjust three-dimensional characteristics of displayed three-dimensional content. For example, user input interface 402 may enable three-dimensionality of displayed content to be turned on or off (e.g., to toggle between two-dimensionality and three-dimensionality). User input interface 402 may enable a degree of three-dimensionality of displayed content to be modified (e.g., increased or decreased, such as by changing a depth of three-dimensionality, increasing or decreasing a number of supplied camera views, etc.), may enable three-dimensional objects to be rotated in three-dimensions, and/or may enable further types of adjustment to three-dimensional characteristics of displayed three-dimensional content. Furthermore, user input interface 402 may enable other characteristics of displayed content to be modified, such as modifying contrast, brightness, etc.
For instance,
Flowchart 1600 begins with step 1602. In step 1602, an input signal is received from a user input interface. For example, as shown in
In embodiments, the user may interact with user input interface 402 in various ways, including using a mouse/pointing device to move a displayed pointer/cursor. The pointer may be used to “click and drag” objects to move them, to resize objects, to rotate objects, to select controls/settings, to open a pop-up menu, etc. In other embodiments, the user may interact with a keyboard, a thumb wheel or other wheel, a roller ball, a stick pointer, a touch sensitive display, any number of virtual interface elements (e.g., such as a keyboard or other user interface element displayed by screen 620), a voice recognition system, and/or other user interface elements described elsewhere herein or otherwise known to provide user input. For instance, user input interface 402 may support a touch screen that is reactive to user finger touches to the screen to cause three-dimensional characteristics of displayed objects to be modified. For instance, particular motions of one or more figures against the screen may cause object resizing, 3D rotation, movement in 3D, etc. (e.g., touching two fingers to the screen, and dragging them together may be interpreted as “grabbing” a window and moving the window in 3D).
In step 1604, a control signal is generated in response to the input signal, the control signal relating to a three-dimensional characteristic. For instance, as shown in
In step 1606, the control signal is delivered to cause the adjustment of the three-dimensional characteristic of a three-dimensional content being displayed within the region of the screen. For example, as shown in
For example, in step 1602 of flowchart 1600, a user may interact with one of regions 1202-1218, and/or with an object displayed within one of regions 1202-1218. The user may resize a region and/or object that is displayed as three-dimensional, may rotate a region and/or object that is displayed as three-dimensional, may move a region and/or object that is displayed as three-dimensional in any of the three degrees (e.g., left-right, up-down, or forward-backward in
In embodiments, users may have preferences with regard to a display environment upon powering on and/or logging into a device. Such preferences may include preferences with regard to display of three-dimensional content. For example, a user may desire for a television to power up in a two-dimensional or three-dimensional display mode, and if a three-dimensional display mode is desired, the user may have particular three-dimensional display preferences (e.g., a preferred degree of displayed three-dimensionality). In another example, with regard to a computer, a user may desire for the user's desktop environment to load with particular two-dimensional and/or three-dimensional display preferences. For instance, the user may desire for the desktop background to be displayed in two- or three-dimensions, may desire icons representing various executable applications to be displayed in two-dimensions and/or three-dimensions, etc. Furthermore, for each of the objects and/or regions displayed in three-dimensions, the user may have particular three-dimensional display preferences.
Embodiments enable display preferences to be set by users, and to be used to configure the display environments of users upon device boot up and/or user login. For instance,
Memory 1806 may include one or more random access memory (RAM) devices, one or more read only memory (ROM) devices, and/or other memory devices. As shown in
Operating system 1812 may include a graphical user interface (GUI) generator (e.g., in user input interface 402) used to render graphical user interfaces for users. For instance,
For example, as shown in
Thus, upon boot up, GUI generator 1902 may generate a GUI environment displayed in screen 620 for the user. GUI generator 1902 may execute boot up module 1904 to determine user preferences for the user (e.g., user preferences associated with a user account of the user). Furthermore, in an embodiment, boot up module 1904 may be configured to determine display capabilities of screen 620. For instance, boot up module 1904 may perform a handshake with screen 620 on boot up to determine a three-dimensional display capability of screen 620. GUI generator 1902 may then configure the GUI environment according to the determined capabilities of screen 620 and the preferences of the user. For instance, the user preferences of the user may include three-dimensional display characteristics that are beyond the determined capabilities of screen 620. In such case, GUI generator 1902 may use determined default display characteristics (e.g., two-dimensional and/or three-dimensional) instead of the determined user preferences. Furthermore, in embodiments, three-dimensional characteristics of screen 620 may be selected based on other factors, including selecting/modifying an aspect of the display of the three-dimensional content based on change in a data rate of a received three-dimensional content data stream, and/or other factors.
E. Example Display Device Screen EmbodimentsEmbodiments described herein for operating systems that support the display of two-dimensional and three-dimensional content may be implemented with respect to various types of display devices. For example, as described above, some display screens are configured for displaying two-dimensional content, although they may display two-dimensional images that may be combined to form three-dimensional images by special glasses worn by users. Some other types of display screens are capable of display two-dimensional content and three-dimensional content without the users having to wear special glasses using techniques of autostereoscopy.
As described above, display devices, such as display device 606, may be implemented in various ways. For instance, display device 606 may be a television display (e.g., an LCD (liquid crystal display) television, a plasma television, etc.), a computer monitor, or any other type of display device. Display device 606 may include any suitable type or combination of light and image generating devices, including an LCD screen, a plasma screen, an LED (light emitting device) screen (e.g., an OLED (organic LED) screen), etc. Furthermore, display device 606 may include any suitable type of light filtering device, such as a parallax barrier (e.g., an LCD filter, a mechanical filter (e.g., that incorporates individually controllable shutters), etc.) and/or a lenticular lens, and may be configured in any manner, including as a thin-film device (e.g., formed of a stack of thin film layers), etc. Furthermore, display device 606 may include any suitable light emitting device as backlighting, including a panel of LEDs or other light emitting elements.
For instance,
Examples of light manipulator 2004 include a parallax barrier and a lenticular lens. For instance, light manipulator 2004 may be a parallax barrier that has a layer of material with a series of precision slits. The parallax barrier is placed proximal to a light emitting pixel array so that a user's eyes each see a different set of pixels to create a sense of depth through parallax. In another embodiment, light manipulator 2004 may be a lenticular lens that includes an array of magnifying lenses configured so that when viewed from slightly different angles, different images are magnified. Such a lenticular lens may be used to deliver light from a different set of pixels of a pixel array to each of the user's eyes to create a sense of depth. Embodiments are applicable display devices that include such light manipulators, include other types of light manipulators, and that may include multiple light manipulators.
As shown in
In contrast,
Device 2100 receives one or more control signals 2106 (e.g., from OS 400) that are configured to place screen 2102 in a desired display mode (e.g., either a two-dimensional display mode or a three-dimensional display mode), and/or to configure three-dimensional characteristics of any number and type as described above, such as configuring adaptable light manipulator 2104 to deliver different types of three-dimensional images, to deliver three-dimensional images to different/moving regions of a viewing space, and to deliver two-dimensional and/or three-dimensional images from any number of regions of screen 2102 to the viewing space.
As shown in
Content signals 2008 and 2108 may include video content according to any suitable format. For example, content signals 2008 and 2108 may include video content delivered over an HDMI (High-Definition Multimedia Interface) interface, over a coaxial cable, as composite video, as S-Video, a VGA (video graphics array) interface, etc.
Exemplary embodiments for display devices 2000 and 2100 of
Display devices 2000 and 2100 may include parallax barriers as light manipulators 2004 and 2104, respectively. For instance,
Pixel array 2208 includes a two-dimensional array of pixels (e.g., arranged in a grid or other distribution). Pixel array 2208 is a self-illuminating or light-generating pixel array such that the pixels of pixel array 2208 each emit light included in light 2252 emitted from image generator 2212. Each pixel may be a separately addressable light source (e.g., a pixel of a plasma display, an LCD display, an LED display such as an OLED display, or of other type of display). Each pixel of pixel array 2208 may be individually controllable to vary color and intensity. In an embodiment, each pixel of pixel array 2208 may include a plurality of sub-pixels that correspond to separate color channels, such as a trio of red, green, and blue sub-pixels included in each pixel.
Parallax barrier 2220 is positioned proximate to a surface of pixel array 2208. Barrier element array 2210 is a layer of parallax barrier 2220 that includes a plurality of barrier elements or blocking regions arranged in an array. Each barrier element of the array is configured to be selectively opaque or transparent. Combinations of barrier elements may be configured to be selectively opaque or transparent to enable various effects. For example, in one embodiment, each barrier element may have a round, square, or rectangular shape, and barrier element array 2210 may have any number of rows of barrier elements that extend a vertical length of barrier element array 2210. In another embodiment, each barrier element may have a “band” shape that extends a vertical length of barrier element array 2210, such that barrier element array 2210 includes a single horizontal row of barrier elements. Each barrier element may include one or more of such bands, and different regions of barrier element array may include barrier elements that include different numbers of such bands.
One advantage of such a configuration where barrier elements extend a vertical length of barrier element array 2210 is that such barrier elements do not need to have spacing between them because there is no need for drive signal routing in such space. For instance, in a two-dimensional LCD array configuration, such as TFT (thin film transistor) display, a transistor-plus-capacitor circuit is typically placed onsite at the corner of a single pixel in the array, and drive signals for such transistors are routed between the LCD pixels (row-column control, for example). In a pixel configuration for a parallax barrier, local transistor control may not be necessary because barrier elements may not need to be changing as rapidly as display pixels (e.g., pixels of pixel array 2208). For a single row of vertical bands of barrier elements, drive signals may be routed to the top and/or bottom of barrier elements. Because in such a configuration drive signal routing between rows is not needed, the vertical bands can be arranged side-by-side with little-to-no space in between. Thus, if the vertical bands are thin and oriented edge-to-edge, one band or multiple adjacent bands (e.g., five bands) may comprise a barrier element in a blocking state, followed by one band or multiple adjacent bands (e.g., two bands) that comprise a barrier element in a non-blocking state (a slit), and so on. In the example of five bands in a blocking state and two bands in a non-blocking state, the five bands may combine to offer a single black barrier element of approximately 2.5 times the width of a single transparent slit with no spaces therein.
It is noted that in some embodiments, barrier elements may be capable of being completely transparent or opaque, and in other embodiments, barrier elements may not be capable of being fully transparent or opaque. For instance, such barrier elements may be capable of being 95% transparent when considered to be “transparent” and may be capable of being 5% transparent when considered to be “opaque.” “Transparent” and “opaque” as used herein are intended to encompass barrier elements being substantially transparent (e.g., greater than 75% transparent, including completely transparent) and substantially opaque (e.g., less than 25% transparent, including completely opaque), respectively.
Display driver circuit 2202 receives control signal 2222 and content signal 2224. As described below, content signal 2224 includes two-dimensional and/or three-dimensional content for display. Control signal 2222 may be control signal 2006 of
For example, drive signal 2214 may control sets of pixels of pixel array 2208 to each emit light representative of a respective image, to provide a plurality of images. Drive signal 2216 may control barrier elements of barrier element array 2210 to filter the light received from pixel array 2208 according to the provided images such that one or more of the images are received by users 2218 in two-dimensional form. For instance, drive signal 2216 may select one or more sets of barrier elements of barrier element array 2210 to be transparent, to transmit one or more corresponding two-dimensional images or views to users 2218. Furthermore, drive signal 2216 may control sections of barrier element array 2210 to include opaque and transparent barrier elements to filter the light received from pixel array 2208 so that one or more pairs of images or views provided by pixel array 2208 are each received by users 2218 as a corresponding three-dimensional image or view. For example, drive signal 2216 may select parallel strips of barrier elements of barrier element array 2210 to be transparent to form slits that enable three-dimensional images to be received by users 2218.
In embodiments, drive signal 2216 may be generated by barrier array driver circuit 2206 to configure one or more characteristics of barrier element array 2210. For example, drive signal 2216 may be generated to form any number of parallel strips of barrier elements of barrier element array 2210 to be transparent, to modify the number and/or spacing of parallel strips of barrier elements of barrier element array 2210 that are transparent, to select and/or modify a width and/or a length (in barrier elements) of one or more strips of barrier elements of barrier element array 2210 that are transparent or opaque, to select and/or modify an orientation of one or more strips of barrier elements of barrier element array 2210 that are transparent, to select one or more areas of barrier element array 2210 to include all transparent or all opaque barrier elements, etc.
Backlighting 2316 is a backlight panel that emits light 2338. Light element array 2336 (or “backlight array”) of backlighting 2316 includes a two-dimensional array of light sources. Such light sources may be arranged, for example, in a rectangular grid. Each light source in light element array 2336 is individually addressable and controllable to select an amount of light emitted thereby. A single light source may comprise one or more light-emitting elements depending upon the implementation. In one embodiment, each light source in light element array 2336 comprises a single light-emitting diode (LED) although this example is not intended to be limiting. Further description of implementations of backlighting 2316 and other backlighting implementations described herein is provided in pending U.S. Patent Appl. No. 12/982,020, titled “Backlighting Array Supporting Adaptable Parallax Barrier,” filed on same date herewith, which is incorporated by reference herein in its entirety.
Parallax barrier 2220 is positioned proximate to a surface of backlighting 2316 (e.g., a surface of the backlight panel). As described above, barrier element array 2210 is a layer of parallax barrier 2220 that includes a plurality of barrier elements or blocking regions arranged in an array. Each barrier element of the array is configured to be selectively opaque or transparent. Barrier element array 2210 filters light 2338 received from backlighting 2316 to generate filtered light 2340. Filtered light 2340 is configured to enable a two-dimensional image or a three-dimensional image (e.g., formed by a pair of two-dimensional images in filtered light 2272) to be formed based on images subsequently imposed on filtered light 2340 by pixel array 2322.
Similarly to pixel array 2208 of
Display driver circuit 2202 of
For example, drive signal 2334 may control sets of light sources of light element array 2336 to emit light 2338. Drive signal 2216 may control barrier elements of barrier element array 2210 to filter light 2338 received from light element array 2336 to enable filtered light 2340 to enable two- and/or three-dimensionality. Drive signal 2332 may control sets of pixels of pixel array 2322 to filter filtered light 2340 according to respective images, to provide a plurality of images. For instance, drive signal 2216 may select one or more sets of the barrier elements of barrier element array 2210 to be transparent, to enable one or more corresponding two-dimensional images to be delivered to users 2218. Furthermore, drive signal 2216 may control sections of barrier element array 2210 to include opaque and transparent barrier elements to filter the light received from light element array 2336 so that one or more pairs of images provided by pixel array 2322 are each enabled to be received by users 2218 as a corresponding three-dimensional image. For example, drive signal 2216 may select parallel strips of barrier elements of barrier element array 2210 to be transparent to form slits that enable three-dimensional images to be received by users 2218.
Flowchart 2400 begins with step 2402. In step 2402, light is received at an array of barrier elements. For example, as shown in
In step 2404, a first set of the barrier elements of the array of barrier elements is configured in the blocking state and a second set of the barrier elements of the array of barrier elements is configured in the non-blocking state to enable a viewer to be delivered a three-dimensional view. Three-dimensional image content may be provided for viewing in viewing space 2270. In such case, referring to
For instance,
Referring back to
For example, as shown in
Furthermore, light emanating from pixel array 2502 is filtered by barrier element array 2504 to form a plurality of images in a viewing space 2526, including a first image 2506a at a first location 2508a and a second image 2506b at a second location 2508b. A portion of the light emanating from pixel array 2502 is blocked by blocking barrier elements 2510, while another portion of the light emanating from pixel array 2502 passes through non-blocking barrier elements 2512, according to the filtering by barrier element array 2504. For instance, light 2524a from pixel 2514a is blocked by blocking barrier element 2510a, and light 2524b and light 2524c from pixel 2514b are blocked by blocking barrier elements 2510b and 2510c, respectively. In contrast, light 2518a from pixel 2514a is passed by non-blocking barrier element 2512a and light 2518b from pixel 2514b is passed by non-blocking barrier element 2512b.
By forming parallel non-blocking slits in a barrier element array, light from a pixel array can be filtered to form multiple images or views in a viewing space. For instance, system 2500 shown in
First and second images 2506a and 2506b are configured to be perceived by a user as a three-dimensional image or view. For example, a viewer may receive first image 2506a at a first eye location and second image 2506b at a second eye location, according to an exemplary embodiment. First and second images 2506a and 2506b may be generated by first set of pixels 2514a-2514d and second set of pixels 2516a-2516d as images that are slightly different perspective from each other. Images 2506a and 2506b are combined in the visual center of the brain of the viewer to be perceived as a three-dimensional image or view. In such an embodiment, first and second images 2506a and 2506b may be formed by display system 2500 such that their centers are spaced apart a width of a user's pupils (e.g., an “interocular distance”).
Note that in the embodiments of
For instance,
In another example,
Furthermore, as shown in
As such, in
As described above, in an embodiment, display device 2102 of
In embodiments, display systems may be configured to generate multiple two-dimensional images or views for viewing by users in a viewing space. For example,
As such, display system 3000 of
In an embodiment, display system 2500 may be configured to generate multiple three-dimensional images that include related image content (e.g., each three-dimensional image is a different viewpoint of a common scene), or that each include unrelated image content, for viewing by users in a viewing space. Each of the three-dimensional images may correspond to a pair of images generated by pixels of the pixel array. The barrier element array filters light from the pixel array to form the image pairs in a viewing space to be perceived by users as three-dimensional images.
For instance,
Flowchart 3100 begins with step 3102. In step 3102, light is received from an array of pixels that includes a plurality of pairs of sets of pixels. For instance, in the example of
As described above, in the current embodiment, pixel array 3202 is segmented into a plurality of pairs of sets of pixels. For instance, in the example of
In step 3104, a plurality of strips of barrier elements of a barrier element array is selected to be non-blocking to form a plurality of parallel non-blocking slits. As shown in
In step 3106, the light is filtered at the barrier element array to form a plurality of pairs of images in a viewing space corresponding to the plurality of pairs of sets of pixels, each pair of images of the plurality of pairs of images being configured to be perceived as a corresponding three-dimensional image of a plurality of three-dimensional images. As shown in
In the embodiment of
In the example of
In
Further description regarding using a parallax barrier to deliver three-dimensional views, including adaptable versions of parallax barriers, is provided in pending U.S. patent application Ser. No. 12/845,409, titled “Display With Adaptable Parallax Barrier,” in pending U.S. patent application Ser. No. 12/845,440, titled “Adaptable Parallax Barrier Supporting Mixed 2D And Stereoscopic 3D Display Regions,” and in pending U.S. patent application Ser. No. 12/845,461, titled “Display Supporting Multiple Simultaneous 3D Views,” which are each incorporated by reference herein in their entireties.
2. Exemplary Embodiments Using Lenticular LensesIn embodiments, as described herein, display devices 2000 and 2100 of
In one embodiment, lenticular lens 3300 may be fixed in size. For example, light manipulator 2004 of
Further description regarding using a lenticular lens to deliver three-dimensional views, including adaptable versions of lenticular lenses, is provided in pending U.S. patent application Ser. No. 12/774,307, titled “Display with Elastic Light Manipulator,” which is incorporated by reference herein in its entirety.
3. Exemplary Embodiments Using Multiple Light ManipulatorsDisplay devices 2000 and 2100 may include multiple layers of light manipulators in embodiments. Multiple three-dimensional images may be displayed in a viewing space using multiple light manipulator layers, according to embodiments. In embodiments, the multiple light manipulating layers may enable spatial separation of the images. For instance, in such an embodiment, for example, a display device that includes multiple light manipulator layers may be configured to display a first three-dimensional image in a first region of a viewing space (e.g., a left-side area), a second three-dimensional image in a second region of the viewing space (e.g., a central area), a third three-dimensional image in a third region of the viewing space (e.g., a right-side area), etc. In embodiments, a display device may be configured to display any number of spatially separated three-dimensional images, as desired for a particular application (e.g., according to a number and spacing of viewers in the viewing space, etc.).
For instance,
Flowchart 3500 begins with step 3502. In step 3502, light is received from an array of pixels that includes a plurality of pairs of sets of pixels. For example, as shown in
In step 3504, the light from the array of pixels is manipulated with a first light manipulator. For example, first light manipulator 3614a may be configured to manipulate light 2252 received from pixel array 2208. As shown in
In step 3506, the light manipulated by the first light manipulator is manipulated with a second light manipulator to form a plurality of pairs of images corresponding to the plurality of pairs of sets of pixels in a viewing space. For example, as shown in
As such, display system 3600 has a single viewing plane or surface (e.g., a plane or surface of pixel array 2208, first light manipulator 3614a, second light manipulator 3614b) that supports multiple viewers with media content in the form of three-dimensional images or views. The single viewing plane of display system 3600 may provide a first three-dimensional view based on first three-dimensional media content to a first viewer, a second three-dimensional view based on second three-dimensional media content to a second viewer, and optionally further three-dimensional views based on further three-dimensional media content to further viewers. First and second light manipulators 3614a and 3614b each cause three-dimensional media content to be presented to a corresponding viewer via a corresponding area of the single viewing plane, with each viewer being enabled to view corresponding media content without viewing media content directed to other viewers. Furthermore, the areas of the single viewing plane that provide the various three-dimensional views of media content overlap each other at least in part. In the embodiment of
Display system 3600 may be configured in various ways to generate multiple three-dimensional images according to flowchart 3500, in embodiments. Furthermore, as described below, embodiments of display system 3600 may be configured to generate two-dimensional views, as well as any combination of one or more two-dimensional views simultaneously with one or more three-dimensional views.
For instance, in an embodiment, delivery of three-dimensional images may be performed in system 3600 using multiple parallax barriers.
As shown in the example of
Each of pixels 3714a-3714c, 3716a-3716c, 3718a-3718c, and 3720a-3720c is configured to generate light, which emanates from the surface of pixel array 3702 towards first barrier element array 3704. Each set of pixels is configured to generate a corresponding image. For example,
First-fourth images 3806a-3806d may be formed in viewing space 3802 at a distance from pixel array 3702 and at a lateral location of viewing space 3802 as determined by a configuration of display system 3700 of
In an embodiment, system 3600 of
As shown in
As described above, light manipulators may be reconfigured to change the locations of delivered views based on changing viewer positions. As such, a position of a viewer may be determined/tracked so that a parallax barrier and/or light manipulator may be reconfigured to deliver views consistent with the changing position of the viewer. For instance, with regard to a parallax barrier, a spacing, number, arrangement, and/or other characteristic of slits may be adapted according to the changing viewer position. With regard to a lenticular lens, a size of the lenticular lens may be adapted (e.g., stretched, compressed) according to the changing viewer position. In embodiments, a position of a viewer may be determined/tracked by determining a position of the viewer directly, or by determining a position of a device associated with the viewer (e.g., a device worn by the viewer, held by the viewer, sitting in the viewer's lap, in the viewer's pocket, sitting next the viewer, etc.).
Examples of display environments for display embodiments described herein include environments having a single viewer, as well as environments having multiple viewers. For example, in one type of environment (e.g., an office, living room, etc.), a single viewer interacts with an electronic device, mobile or stationary, to view and/or interact with mixed 2D and 3D content, such as a mobile or desktop computer, smart phone, television, or other mobile or stationary device. It is noted that this type of environment may include more than one viewer. In another type of environment (e.g., a living room, a home theatre room, etc.), multiple viewers are enabled to interact with an electronic device, such as a television set (e.g., high-def, small screen, large screen, etc.), to view and/or interact with mixed 2D and 3D content in the form of television content, movies, video games, etc.
For instance,
Remote control 4004a is a device that viewer 4006a may use to interact with display device 4002, and remote control 4004b is a device that viewer 4006b may use to interact with display device 4002. For example, as shown in
Headsets 4012a and 4012b are worn by viewers 4006a and 4006b, respectively. Headsets 4012a and 4012b each include one or two speakers (e.g., earphones) that enable viewers 4006a and 4006b to hear audio associated with the media content of views 4008a and 4008b. Headsets 4012a and 4012b enable viewers 4006a and 4006b to hear audio of their respective media content without hearing audio associated the media content of the other of viewers 4006a and 4006b. Headsets 4012a and 4012b may each optionally include a microphone to enable viewers 4006a and 4006b to interact with display device 4002 using voice commands.
Display device 4002a, headset 4012a, and/or remote control 4004a may operate to provide position information 4010a regarding viewers 4006a to display device 4002, and display device 4002b, headset 4012b, and/or remote control 4004b may operate to provide position information 4010b regarding viewers 4006b to display device 4002. Display device 4002 may use position information 4010a and 4010b to reconfigure one or more light manipulators (e.g., parallax barriers and/or lenticular lenses) of display device 4002 to enable views 4008a and 4008b to be delivered to viewers 4006a and 4006b, respectively, at various locations. For example, display device 4002a, headset 4012a, and/or remote control 4004a may use positioning techniques to track the position of viewer 4006a, and display device 4002b, headset 4012b, and/or remote control 4004b may use positioning techniques to track the position of viewer 4006b.
G. Example Electronic Device ImplementationsEmbodiments may be implemented in hardware, software, firmware, or any combination thereof. For example, application(s) 104, operating system 106, operating system 400, user input interface 402, API 404, kernel 406, display driver interface 410, display driver(s) 408, application 604, display driver 618, first translator 1302, second translator 1304, boot loader 1810, operating system 1812, GUI generator 1902, and/or boot up module 1904 may be implemented as computer program code configured to be executed in one or more processors.
For instance,
Electronic device 4100 also includes a primary or main memory 4106, such as random access memory (RAM). Main memory 4106 has stored therein control logic 4128A (computer software), and data.
Electronic device 4100 also includes one or more secondary storage devices 4110. Secondary storage devices 4110 include, for example, a hard disk drive 4112 and/or a removable storage device or drive 4114, as well as other types of storage devices, such as memory cards and memory sticks. For instance, electronic device 4100 may include an industry standard interface, such a universal serial bus (USB) interface for interfacing with devices such as a memory stick. Removable storage drive 4114 represents a floppy disk drive, a magnetic tape drive, a compact disk drive, an optical storage device, tape backup, etc.
As shown in
Removable storage drive 4114 interacts with a removable storage unit 4116. Removable storage unit 4116 includes a computer useable or readable storage medium 4124 having stored therein computer software 4128B (control logic) and/or data. Removable storage unit 4116 represents a floppy disk, magnetic tape, compact disk, DVD, optical storage disk, or any other computer data storage device. Removable storage drive 4114 reads from and/or writes to removable storage unit 4116 in a well known manner.
Electronic device 4100 further includes a communication or network interface 4118. Communication interface 4118 enables the electronic device 4100 to communicate with remote devices. For example, communication interface 4118 allows electronic device 4100 to communicate over communication networks or mediums 4142 (representing a form of a computer useable or readable medium), such as LANs, WANs, the Internet, etc. Network interface 4118 may interface with remote sites or networks via wired or wireless connections.
Control logic 4128C may be transmitted to and from electronic device 4100 via the communication medium 4142.
Any apparatus or manufacture comprising a computer useable or readable medium having control logic (software) stored therein is referred to herein as a computer program product or program storage device. This includes, but is not limited to, electronic device 4100, main memory 4106, secondary storage devices 4110, and removable storage unit 4116. Such computer program products, having control logic stored therein that, when executed by one or more data processing devices, cause such data processing devices to operate as described herein, represent embodiments of the invention.
Devices in which embodiments may be implemented may include storage, such as storage drives, memory devices, and further types of computer-readable media. Examples of such computer-readable storage media include a hard disk, a removable magnetic disk, a removable optical disk, flash memory cards, digital video disks, random access memories (RAMs), read only memories (ROM), and the like. As used herein, the terms “computer program medium” and “computer-readable medium” are used to generally refer to the hard disk associated with a hard disk drive, a removable magnetic disk, a removable optical disk (e.g., CDROMs, DVDs, etc.), zip disks, tapes, magnetic storage devices, MEMS (micro-electromechanical systems) storage, nanotechnology-based storage devices, as well as other media such as flash memory cards, digital video discs, RAM devices, ROM devices, and the like. Such computer-readable storage media may store program modules that include computer program logic for application(s) 104, operating system 106, operating system 400, user input interface 402, API 404, kernel 406, display driver interface 410, display driver(s) 408, application 604, display driver 618, first translator 1304, second translator 1304, boot loader 1810, operating system 1812, GUI generator 1902, boot up module 1904, flowchart 500, flowchart 800, flowchart 1400, flowchart 1600, (including any one or more steps of flowcharts 500, 800, 1400, and 1600), and/or further embodiments of the present invention described herein. Embodiments of the invention are directed to computer program products comprising such logic (e.g., in the form of program code or software) stored on any computer useable medium. Such program code, when executed in one or more processors, causes a device to operate as described herein.
The invention can work with software, hardware, and/or operating system implementations other than those described herein. Any software, hardware, and operating system implementations suitable for performing the functions described herein can be used.
As described herein, electronic device 4100 may be implemented in association with a variety of types of display devices. For instance, electronic device 4100 may be one of a variety of types of media devices, such as a stand-alone display (e.g., a television display such as flat panel display, etc.), a computer, a game console, a set top box, a digital video recorder (DVR), other electronic device mentioned elsewhere herein, etc. Media content that is delivered in two-dimensional or three-dimensional form according to embodiments described herein may be stored locally or received from remote locations. For instance, such media content may be locally stored for playback (replay TV, DVR), may be stored in removable memory (e.g. DVDs, memory sticks, etc.), may be received on wireless and/or wired pathways through a network such as a home network, through Internet download streaming, through a cable network, a satellite network, and/or a fiber network, etc. For instance,
Media input interfaces 4202 includes one or more media input interfaces, wired or wireless, for received media, such as those described elsewhere herein. For instance, media input interface 4202 may include an interface for receiving media content from a local media player device, such as a DVD player, a memory stick, a computer media player, etc., and may include commercially available (e.g., USB, HDMI, etc.) or proprietary interfaces for receiving local media content. Media input interface 4202 may include an interface for receiving media content from a remote source, such as the Internet, satellite, cable, etc.), and may include commercially available (e.g., WLAN, Data Over Cable Service Interface Specification (DOCSIS), etc.) or proprietary interfaces for receiving remote media content.
Host processing circuitry 4204 may include one or more integrated circuit chips and/or additional circuitry, which may be configured to execute software/firmware, including operating system 4220 and application programs 4222. Operating system 4220 is an example of OS 400 described herein. User input interfaces 4220 is an example of user input interfaces 420 of
User input devices 4206 includes one or more user input devices that a user may use to interact with display system 4200. Examples of user input devices are described elsewhere herein, such as a keyboard, a mouse/pointer, etc.
Display processing circuitry 4208 may be included in host processing circuitry 4204, or may be separate from host processing circuitry 4204 as shown in
Adaptable display driver circuitry 4210 includes one or more display driver circuits for an adaptable display. Examples of adaptable display driver circuitry 4210 are described above, such as with regard to
Adaptable 2D, 3Dx and mixed display 4212 includes a display that is adaptable, and is capable of displaying 2D content, 3D content, and a mixture of 2D and/or 3D content. Examples of adaptable 2D, 3Dx and mixed display 4212 are described elsewhere herein.
First-third interface circuitry 4214-4218 is optional. For instance, as shown in
Note that the embodiment of display system 4200 shown in
While various embodiments of the present invention have been described above, it should be understood that they have been presented by way of example only, and not limitation. It will be apparent to persons skilled in the relevant art that various changes in form and detail can be made therein without departing from the spirit and scope of the invention. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
Claims
1. A method performed by one or more processors and used in an operating system to support simultaneous display on a screen of both two-dimensional content and three-dimensional content, the method comprising:
- receiving, by the operating system, from a first application a first command directing display of the two-dimensional content within a first region of the screen;
- responding, by the operating system, to the first command by sending a first control signal that places the screen in a two-dimensional mode within the first region;
- receiving, by the operating system, from a second application a second command directing display of the three-dimensional content within a second region of the screen;
- responding, by the operating system, to the second command by sending a second control signal that places the screen in a three-dimensional mode within the second region, wherein the first region of the screen is configured to display the two-dimensional content and the second region of the screen is configured to display the three-dimensional content simultaneously with the two-dimensional content;
- receiving an input signal from a user input interface;
- generating a third control signal in response to the input signal, the third control signal relating to a configurable depth of the three-dimensional content; and
- delivering the third control signal to cause the adjustment of the configurable depth of the three-dimensional content being displayed within the second region of the screen.
2. The method of claim 1, further comprising receiving user input directing movement of the three-dimensional content from the second region of the screen to a third region of the screen, and sending a third control signal directing the movement via corresponding modifications to the screen.
3. The method of claim 1, further comprising delivering three-dimensional content to a pixel array of the screen that corresponds with the second region of the screen in which an adaptable light manipulator of the screen is operating in the three-dimensional mode.
4. The method of claim 1, wherein the first command and second command are part of an application program interface.
5. The method of claim 1, further comprising:
- receiving an indication from the screen of whether the second control signal was successful;
- generating a response to the second command based on the indication; and
- providing the response to the second application.
6. The method of claim 5, wherein said providing comprises:
- providing a window handle in the response to the second application, the window handle being a handle for a window opened in the second region to display the three-dimensional content.
7. The method of claim 1, wherein the second command includes one or more parameters, wherein said receiving comprises:
- generating the second control signal to configure the screen based on the one or more parameters.
8. The method of claim 7, wherein the second command is configured to cause a window that displays the three-dimensional content to be opened in the second region.
9. The method of claim 7, wherein said generating comprises:
- filtering out a parameter of the one or more parameters that is incompatible with the screen.
10. The method of claim 1, further comprising:
- receiving a request from the second application for an indication of at least one characteristic of the screen; and
- providing the requested indication of the at least one characteristic to the second application.
11. An operating system that supports a plurality of software applications that are at least partially executed by one or more processors and at least one of a plurality of screens, a first of the plurality of screens supporting at least three-dimensional display on a first screen region of the first of the plurality of screens and at least two-dimensional display on a second screen region of the first of the plurality of screens simultaneously, and a second of the plurality of screens supporting at least two-dimensional display, the operating system comprising:
- an application programming interface through which a first of the plurality of software applications can deliver at least one first request to the operating system that defines the first screen region and a three-dimension indicator that causes the displaying of three-dimensional content in the first screen region, at least one second request to the operating system that defines the second screen region of the first of the plurality of screens and a two-dimension indicator that causes the displaying of two-dimensional content in the second screen region, the three-dimensional content in the first screen region and the two-dimensional content in the second screen region being caused to be displayed simultaneously, and at least one third request to the operating system configured to cause the displaying of three-dimensional content in the second of the plurality of screens;
- a display driver interface through which at least one configuration command corresponding to at least one of the at least one first request, the at least one second request, and the at least one third request are passed;
- a first display driver, associated with the first screen of the plurality of screens, that receives the at least one configuration command and responds by generating one or more screen control signals to adjust the first screen to support the first screen region of the first of the plurality of screens; and
- a second display driver, associated with the second of the plurality of screens, that receives and responds to the at least one configuration command by translating incoming three-dimensional data to two-dimensional data for display on the second screen of the plurality of screens.
12. The operating system of claim 11, wherein the at least one configuration command causes the display driver to manipulate incoming pixel data before delivery to the plurality of screens.
13. The operating system of claim 11, wherein the display driver is configured to receive an indication from the first screen of whether a screen control signal was successful, to generate a response to the at least one request that includes the indication, and to transmit the response to the first application via the application programming interface.
14. The operating system of claim 11, wherein a first request of the at least one request defines the first screen region, and includes the three-dimension indicator and one or more parameters.
15. The operating system of claim 14, wherein the display driver interface is configured to filter out a parameter of the one or more parameters that is incompatible with the first screen.
16. The operating system of claim 14, wherein the first request is an open window command, and the one or more parameters includes at least one of a window size parameter, a window position parameter, a display resolution parameter, a window type parameter, a three-dimensional display type parameter, or a three-dimensional content source indication parameter.
17. The operating system of claim 11, further comprising:
- a user input interface configured to receive a user input directed to three-dimensional content displayed in the first screen region, to generate a second configuration command based on the user input, the second configuration command being configured to adjust a three-dimensional characteristic of three-dimensional content displayed by the first screen region, the display driver interface being configured to pass the second configuration to the first display driver, the first display driver receiving the generated configuration command and generating a screen control signal to adjust the three-dimensional characteristic of the three-dimensional content being displayed within the first screen region.
18. A non-transitory computer readable storage medium having computer program instructions embodied in said computer readable storage medium for enabling a processor to execute an operating system to support simultaneous display on a screen of both two-dimensional content and three-dimensional content, the computer program instructions including instructions executable to perform operations comprising:
- receiving, by the operating system, from a first application a first command directing display of the two-dimensional content within a first region of the screen;
- responding, by the operating system, to the first command by sending a first control signal that places the screen in a two-dimensional mode within the first region;
- receiving, by the operating system, from a second application a second command directing display of the three-dimensional content within a second region of the screen;
- responding, by the operating system, to the second command by sending a second control signal that places the screen in a three-dimensional mode within the second region, wherein the first region of the screen is configured to display the two-dimensional content and the second region of the screen is configured to display the three-dimensional content simultaneously with the two-dimensional content;
- receiving an input signal from a user input interface;
- generating a third control signal in response to the input signal, the third control signal relating to a configurable depth of the three-dimensional content; and
- delivering the third control signal to cause the adjustment of the configurable depth of the three-dimensional content being displayed within the second region of the screen.
19. The non-transitory computer readable storage medium of claim 18, the operations further comprising receiving user input directing movement of the three-dimensional content from the second region of the screen to a third region of the screen, and sending a third control signal directing the movement via corresponding modifications to the screen.
20. The non-transitory computer readable storage medium of claim 18, the operations further comprising delivering three-dimensional content to a pixel array of the screen that corresponds with the second region of the screen in which an adaptable light manipulator of the screen is operating in the three-dimensional mode.
| 4829365 | May 9, 1989 | Eichenlaub |
| 5493427 | February 20, 1996 | Nomura et al. |
| 5615046 | March 25, 1997 | Gilchrist |
| 5855425 | January 5, 1999 | Hamagishi |
| 5945965 | August 31, 1999 | Inoguchi et al. |
| 5959597 | September 28, 1999 | Yamada et al. |
| 5969850 | October 19, 1999 | Harrold et al. |
| 5990975 | November 23, 1999 | Nan et al. |
| 6023277 | February 8, 2000 | Osaka et al. |
| 6049424 | April 11, 2000 | Hamagishi |
| 6094216 | July 25, 2000 | Taniguchi et al. |
| 6144375 | November 7, 2000 | Jain et al. |
| 6188442 | February 13, 2001 | Narayanaswami |
| 6285368 | September 4, 2001 | Sudo |
| 6697687 | February 24, 2004 | Kasahara et al. |
| 6710920 | March 23, 2004 | Mashitani et al. |
| 6909555 | June 21, 2005 | Wohlstadter |
| 7030903 | April 18, 2006 | Sudo |
| 7038698 | May 2, 2006 | Palm et al. |
| 7091471 | August 15, 2006 | Wenstrand et al. |
| 7123213 | October 17, 2006 | Yamazaki et al. |
| 7190518 | March 13, 2007 | Kleinberger et al. |
| 7359105 | April 15, 2008 | Jacobs et al. |
| 7389214 | June 17, 2008 | Yelich et al. |
| 7440193 | October 21, 2008 | Gunasekaran et al. |
| 7511774 | March 31, 2009 | Lee et al. |
| 7626644 | December 1, 2009 | Shestak et al. |
| 7646451 | January 12, 2010 | Vogel et al. |
| 7692859 | April 6, 2010 | Redert et al. |
| 7885079 | February 8, 2011 | Chen et al. |
| 7911442 | March 22, 2011 | Wang et al. |
| 7924456 | April 12, 2011 | Kahn et al. |
| 7954967 | June 7, 2011 | Kashiwagi et al. |
| 7997783 | August 16, 2011 | Song et al. |
| 8040952 | October 18, 2011 | Park et al. |
| 8044983 | October 25, 2011 | Nonaka et al. |
| 8049710 | November 1, 2011 | Shestak et al. |
| 8072411 | December 6, 2011 | Chen et al. |
| 8139024 | March 20, 2012 | Daiku |
| 8154686 | April 10, 2012 | Mather et al. |
| 8154799 | April 10, 2012 | Kim et al. |
| 8174564 | May 8, 2012 | Kim et al. |
| 8183788 | May 22, 2012 | Ma |
| 8209396 | June 26, 2012 | Raman et al. |
| 8233034 | July 31, 2012 | Sharp et al. |
| 8284119 | October 9, 2012 | Kim et al. |
| 8310527 | November 13, 2012 | Ko et al. |
| 8334933 | December 18, 2012 | Tsukada et al. |
| 8363928 | January 29, 2013 | Sharp |
| 8368745 | February 5, 2013 | Nam et al. |
| 8384774 | February 26, 2013 | Gallagher |
| 8400392 | March 19, 2013 | Kimura et al. |
| 8411746 | April 2, 2013 | Chen et al. |
| 8438601 | May 7, 2013 | Putterman et al. |
| 8441430 | May 14, 2013 | Lee |
| 8466869 | June 18, 2013 | Kobayashi et al. |
| 8482512 | July 9, 2013 | Adachi et al. |
| 8487863 | July 16, 2013 | Park et al. |
| 8525942 | September 3, 2013 | Robinson et al. |
| 8587642 | November 19, 2013 | Shestak et al. |
| 8587736 | November 19, 2013 | Kang |
| 8605136 | December 10, 2013 | Yu et al. |
| 8687042 | April 1, 2014 | Karaoguz et al. |
| 8736659 | May 27, 2014 | Liu |
| 8766905 | July 1, 2014 | Adachi |
| 8788676 | July 22, 2014 | Alameh et al. |
| 8823782 | September 2, 2014 | Karaoguz et al. |
| 8854531 | October 7, 2014 | Karaoguz et al. |
| 8885026 | November 11, 2014 | Endo |
| 8922545 | December 30, 2014 | Bennett et al. |
| 8964013 | February 24, 2015 | Bennett et al. |
| 8988506 | March 24, 2015 | Bennett et al. |
| 20020010798 | January 24, 2002 | Ben-Shaul et al. |
| 20020037037 | March 28, 2002 | Van Der Schaar |
| 20020167862 | November 14, 2002 | Tomasi et al. |
| 20020171666 | November 21, 2002 | Endo et al. |
| 20020194604 | December 19, 2002 | Sanchez et al. |
| 20030012425 | January 16, 2003 | Suzuki et al. |
| 20030103165 | June 5, 2003 | Bullinger et al. |
| 20030137506 | July 24, 2003 | Efran et al. |
| 20030154261 | August 14, 2003 | Doyle et al. |
| 20030223499 | December 4, 2003 | Routhier et al. |
| 20040027452 | February 12, 2004 | Yun et al. |
| 20040036763 | February 26, 2004 | Swift et al. |
| 20040041747 | March 4, 2004 | Uehara et al. |
| 20040081302 | April 29, 2004 | Kim et al. |
| 20040109093 | June 10, 2004 | Small-Stryker |
| 20040141237 | July 22, 2004 | Wohlstadter |
| 20040164292 | August 26, 2004 | Tung et al. |
| 20040239231 | December 2, 2004 | Miyagawa et al. |
| 20040252187 | December 16, 2004 | Alden |
| 20040255337 | December 16, 2004 | Doyle et al. |
| 20050044489 | February 24, 2005 | Yamagami et al. |
| 20050073472 | April 7, 2005 | Kim et al. |
| 20050128353 | June 16, 2005 | Young et al. |
| 20050185515 | August 25, 2005 | Berstis et al. |
| 20050237487 | October 27, 2005 | Chang |
| 20050248561 | November 10, 2005 | Ito et al. |
| 20050259147 | November 24, 2005 | Nam et al. |
| 20060050785 | March 9, 2006 | Watanabe et al. |
| 20060087556 | April 27, 2006 | Era |
| 20060109242 | May 25, 2006 | Simpkins |
| 20060139448 | June 29, 2006 | Ha et al. |
| 20060139490 | June 29, 2006 | Fekkes et al. |
| 20060244918 | November 2, 2006 | Cossairt et al. |
| 20060256136 | November 16, 2006 | O'Donnell et al. |
| 20060256302 | November 16, 2006 | Hsu |
| 20060271791 | November 30, 2006 | Novack et al. |
| 20070002041 | January 4, 2007 | Kim et al. |
| 20070008406 | January 11, 2007 | Shestak et al. |
| 20070008620 | January 11, 2007 | Shestak et al. |
| 20070052807 | March 8, 2007 | Zhou et al. |
| 20070072674 | March 29, 2007 | Ohta et al. |
| 20070085814 | April 19, 2007 | Ijzerman et al. |
| 20070096125 | May 3, 2007 | Vogel et al. |
| 20070097103 | May 3, 2007 | Yoshioka et al. |
| 20070097208 | May 3, 2007 | Takemoto et al. |
| 20070110035 | May 17, 2007 | Bennett |
| 20070139371 | June 21, 2007 | Harsham et al. |
| 20070146267 | June 28, 2007 | Jang et al. |
| 20070147827 | June 28, 2007 | Sheynman et al. |
| 20070153122 | July 5, 2007 | Ayite et al. |
| 20070153916 | July 5, 2007 | Demircin et al. |
| 20070162392 | July 12, 2007 | McEnroe et al. |
| 20070225994 | September 27, 2007 | Moore |
| 20070258140 | November 8, 2007 | Shestak et al. |
| 20070270218 | November 22, 2007 | Yoshida et al. |
| 20070296874 | December 27, 2007 | Yoshimoto et al. |
| 20080025390 | January 31, 2008 | Shi et al. |
| 20080037120 | February 14, 2008 | Koo et al. |
| 20080043096 | February 21, 2008 | Vetro et al. |
| 20080043644 | February 21, 2008 | Barkley et al. |
| 20080068329 | March 20, 2008 | Shestak et al. |
| 20080086321 | April 10, 2008 | Walton |
| 20080086391 | April 10, 2008 | Maynard et al. |
| 20080126557 | May 29, 2008 | Motoyama et al. |
| 20080133122 | June 5, 2008 | Mashitani et al. |
| 20080150853 | June 26, 2008 | Peng et al. |
| 20080165176 | July 10, 2008 | Archer et al. |
| 20080168129 | July 10, 2008 | Robbin et al. |
| 20080184301 | July 31, 2008 | Boylan et al. |
| 20080191964 | August 14, 2008 | Spengler |
| 20080192112 | August 14, 2008 | Hiramatsu et al. |
| 20080204550 | August 28, 2008 | De Zwart et al. |
| 20080246757 | October 9, 2008 | Ito |
| 20080259233 | October 23, 2008 | Krijn et al. |
| 20080273242 | November 6, 2008 | Woodgate et al. |
| 20080284844 | November 20, 2008 | Woodgate et al. |
| 20080303832 | December 11, 2008 | Kim et al. |
| 20090002178 | January 1, 2009 | Guday et al. |
| 20090010264 | January 8, 2009 | Zhang |
| 20090051759 | February 26, 2009 | Adkins et al. |
| 20090052164 | February 26, 2009 | Kashiwagi et al. |
| 20090058845 | March 5, 2009 | Fukuda et al. |
| 20090102915 | April 23, 2009 | Arsenich |
| 20090115783 | May 7, 2009 | Eichenlaub |
| 20090115800 | May 7, 2009 | Berretty et al. |
| 20090133051 | May 21, 2009 | Hildreth |
| 20090138280 | May 28, 2009 | Morita et al. |
| 20090138805 | May 28, 2009 | Hildreth |
| 20090141182 | June 4, 2009 | Miyashita et al. |
| 20090167639 | July 2, 2009 | Casner et al. |
| 20090174700 | July 9, 2009 | Daiku |
| 20090232202 | September 17, 2009 | Chen et al. |
| 20090238378 | September 24, 2009 | Kikinis et al. |
| 20090244262 | October 1, 2009 | Masuda et al. |
| 20090244266 | October 1, 2009 | Brigham |
| 20090268816 | October 29, 2009 | Pandit et al. |
| 20090319625 | December 24, 2009 | Kouhi |
| 20100007582 | January 14, 2010 | Zalewski |
| 20100066850 | March 18, 2010 | Wilson et al. |
| 20100070987 | March 18, 2010 | Amento et al. |
| 20100071015 | March 18, 2010 | Tomioka et al. |
| 20100079374 | April 1, 2010 | Cortenraad et al. |
| 20100097525 | April 22, 2010 | Mino |
| 20100107184 | April 29, 2010 | Shintani |
| 20100128112 | May 27, 2010 | Marti et al. |
| 20100135640 | June 3, 2010 | Zucker et al. |
| 20100182407 | July 22, 2010 | Ko et al. |
| 20100208042 | August 19, 2010 | Ikeda et al. |
| 20100215343 | August 26, 2010 | Ikeda et al. |
| 20100218231 | August 26, 2010 | Frink et al. |
| 20100225576 | September 9, 2010 | Morad et al. |
| 20100231511 | September 16, 2010 | Henty et al. |
| 20100238274 | September 23, 2010 | Kim et al. |
| 20100238367 | September 23, 2010 | Montgomery et al. |
| 20100245548 | September 30, 2010 | Sasaki et al. |
| 20100272174 | October 28, 2010 | Toma et al. |
| 20100299390 | November 25, 2010 | Alameh et al. |
| 20100302461 | December 2, 2010 | Lim et al. |
| 20100306800 | December 2, 2010 | Jung et al. |
| 20100309290 | December 9, 2010 | Myers |
| 20110016004 | January 20, 2011 | Loyall et al. |
| 20110043475 | February 24, 2011 | Rigazio et al. |
| 20110050687 | March 3, 2011 | Alyshev et al. |
| 20110063289 | March 17, 2011 | Gantz |
| 20110090233 | April 21, 2011 | Shahraray et al. |
| 20110090413 | April 21, 2011 | Liou |
| 20110093882 | April 21, 2011 | Candelore et al. |
| 20110109964 | May 12, 2011 | Kim et al. |
| 20110113343 | May 12, 2011 | Trauth |
| 20110122944 | May 26, 2011 | Gupta et al. |
| 20110137894 | June 9, 2011 | Narayanan et al. |
| 20110149026 | June 23, 2011 | Luthra |
| 20110157167 | June 30, 2011 | Bennett et al. |
| 20110157168 | June 30, 2011 | Bennett et al. |
| 20110157170 | June 30, 2011 | Bennett et al. |
| 20110157172 | June 30, 2011 | Bennett et al. |
| 20110157257 | June 30, 2011 | Bennett et al. |
| 20110157264 | June 30, 2011 | Seshadri et al. |
| 20110157309 | June 30, 2011 | Bennett et al. |
| 20110157315 | June 30, 2011 | Bennett et al. |
| 20110157322 | June 30, 2011 | Bennett et al. |
| 20110157326 | June 30, 2011 | Karaoguz et al. |
| 20110157327 | June 30, 2011 | Seshadri et al. |
| 20110157330 | June 30, 2011 | Bennett et al. |
| 20110157336 | June 30, 2011 | Bennett et al. |
| 20110157339 | June 30, 2011 | Bennett et al. |
| 20110157471 | June 30, 2011 | Seshadri et al. |
| 20110157696 | June 30, 2011 | Bennett et al. |
| 20110157697 | June 30, 2011 | Bennett et al. |
| 20110159929 | June 30, 2011 | Karaoguz et al. |
| 20110161843 | June 30, 2011 | Bennett et al. |
| 20110164034 | July 7, 2011 | Bennett et al. |
| 20110164111 | July 7, 2011 | Karaoguz et al. |
| 20110164115 | July 7, 2011 | Bennett et al. |
| 20110164188 | July 7, 2011 | Karaoguz et al. |
| 20110169913 | July 14, 2011 | Karaoguz et al. |
| 20110169919 | July 14, 2011 | Karaoguz et al. |
| 20110169930 | July 14, 2011 | Bennett et al. |
| 20110199469 | August 18, 2011 | Gallagher |
| 20110234754 | September 29, 2011 | Newton et al. |
| 20110254698 | October 20, 2011 | Eberl et al. |
| 20110268177 | November 3, 2011 | Tian et al. |
| 20110282631 | November 17, 2011 | Poling et al. |
| 20120016917 | January 19, 2012 | Priddle et al. |
| 20120081515 | April 5, 2012 | Jang |
| 20120212414 | August 23, 2012 | Osterhout et al. |
| 20120235900 | September 20, 2012 | Border et al. |
| 20120308208 | December 6, 2012 | Karaoguz et al. |
| 20130127980 | May 23, 2013 | Haddick et al. |
| 20150015668 | January 15, 2015 | Bennett et al. |
| 0833183 | April 1998 | EP |
| 1662808 | May 2006 | EP |
| 1816510 | August 2007 | EP |
| 1993294 | November 2008 | EP |
| 2454771 | May 2009 | GB |
| 200938878 | September 2009 | TW |
| 2005/045488 | May 2005 | WO |
| 2007/024118 | March 2007 | WO |
| 2008/126557 | October 2008 | WO |
| 2009031872 | March 2009 | WO |
| 2009/098622 | August 2009 | WO |
- European Search Report received for European Patent application No. 10015984.7, mailed on May 3, 2011, 3 pages.
- European search Report received for European Patent application No. 10016055.5, mailed on Apr. 12, 2011, 3 pages.
- Office Action received for European Patent Application No. 10016055.5, mailed on Apr. 5, 2013, 6 pages.
- “How Browsers Work”, retrieved from <http://taligarsiel.com/Projects/howbrowserswork1.htm> on Oct. 21, 2010, 54 pages.
- IEEE 100 The Authoritative Dictionary of IEEE Standards Terms Seventh Edition, entry for “engine”, IEEE 100-2000, 2000, pp. 349-411.
- IEEE 100 The Authoritative Dictionary of IEEE Standards Terms Seventh Edition, entry for “Web page”, IEEE 100-2000, 2000, pp. 1269-1287.
- Wikipedia entry on “Scripting language”, retrieved on Aug. 16, 2012, 4 pages.
- Peterka, “Dynallax: Dynamic Parallax Barrier Autostereoscopic Display”, Ph.D. Dissertation, University of Illinois at Chicago, 2007, 134 pages.
- Shan et al., “Principles and Evaluation of Autostereoscopic Photogrammetric Measurement”, Photogrammetric Engineering and Remote Sensing, vol. 72, No. 4, Apr. 2006, pp. 365-372.
- Yanagisawa et al., “A Focus Distance Controlled 3DTV”, SPIE, vol. 3012, Stereoscopic Displays and Virtual Reality Systems IV, May 15, 1997, pp. 256-261.
- Yanaka, “Stereoscopic Display Technique for Web3D Images”, SIGGRAPH 2009, New Orleans, Louisiana, Aug. 3-7, 2009, 1 page.
- Fono, et al.,“EyeWindows: Evaluation of Eye-Controlled Zooming Windows for Focus Selection”,CHI 2005, Papers: Eyes on Interaction, Portland, Oregon, Apr. 2-7, 2005, pp. 151-160.
- Kumar et al.,“Eye Point: Practical Pointing and Selection Using Gaze and Keyboard”,CHI 2007, Apr. 28-May 3, 2007,10 pages.
- “Displaying Stereoscopic 3D (S3D) with Intel HD Graphics Processors for Software Developers”, Intel, Aug. 2011, pp. 1-10.
- Liao, et al.,“The Design and Application of High-Resolution 3D Stereoscopic graphics Display on PC”, Purdue University School of Science, 2000, 7 pages.
- Office Action received for Chinese Patent Application No. 201010619649.3, mailed on Oct. 11, 2014, 5 pages (Official Copy only).
- Office Action received for Chinese Patent Application No. 201010619646.X, mailed on Mar. 5, 2014, 4 pages.
- Office Action received for Chinese Patent Application No. 201010619649.3, mailed on Mar. 31, 2014, 7 pages.
- Office Action received for Taiwan Patent Application No. 099147124, mailed on Mar. 31, 2014, 8 pages.
- Ko et al., “Facial Feature Tracking and Head Orientation-Based Gaze Tracking”, Electronics and Telecommunications Research Institute (ETRI), 2005, 4 pages.
- Ruddarraju et al., “Perceptual User Interfaces using Vision-Based Eye Tracking”, In Proceedings of the 5th International Conference on Multimodal Interfaces (ICMI'03), Nov. 5-7, 2013, 7 pages.
Type: Grant
Filed: Dec 30, 2010
Date of Patent: Sep 1, 2015
Patent Publication Number: 20110157169
Assignee: Broadcom Corporation (Irvine, CA)
Inventors: James D. Bennett (Hroznetin), Jeyhan Karaoguz (Irvine, CA)
Primary Examiner: Phu K Nguyen
Application Number: 12/982,124
International Classification: G06T 15/00 (20110101); H04N 13/04 (20060101); H04N 13/00 (20060101); G06F 3/14 (20060101); G09G 3/00 (20060101); G09G 3/20 (20060101); H04N 21/235 (20110101); H04N 21/41 (20110101); H04N 21/435 (20110101); G03B 35/24 (20060101); H04S 7/00 (20060101); G06F 3/0346 (20130101); G02B 6/00 (20060101); G09G 5/00 (20060101); G09G 5/14 (20060101);
