Systems and methods for receiving, storing, and rendering digital video, music, and pictures on a personal media player

Information

  • Patent Grant
  • 10178141
  • Patent Number
    10,178,141
  • Date Filed
    Thursday, November 19, 2015
    8 years ago
  • Date Issued
    Tuesday, January 8, 2019
    5 years ago
Abstract
A personal media player (PMP) uses a digital media processing system—comprising a video rendering subsystem, a music rendering subsystem, and a picture rendering subsystem—to produce moving-video (video), audio (music), still-graphics (picture), and other output rendered from media files ported to the PMP from another source. The PMP further comprises a user interface system, a display unit system, a power source system, and a data port system utilizing Universal Plug and Play functionality, all of which are coupled directly or indirectly to the digital media processing system. The physical components constituting the aforementioned systems and subsystems are then encased in a portable housing unit suitable for hand-held use and ready portability.
Description
TECHNICAL FIELD

The invention relates generally to personal digital media players and, more specifically, to systems and methods for receiving, storing, and rendering digital video, audio, and still images on a portable playback device.


BACKGROUND

There are a variety of digital video formats, including MPEG, AVI, QuickTime, and Windows Media, among others. The MPEG standards, for example, are an evolving set of standards for video and audio compression and for multimedia delivery developed by the Moving Picture Experts Group (MPEG). MPEG-1 was designed for coding progressive video at a transmission rate of about 1.5 million bits per second, and MPEG-1 audio layer-3 (MP3) has also evolved from this early MPEG work. The current predominant standard, MPEG-2, was designed for coding interlaced images at transmission rates above 4 million bits per second and is used for digital TV broadcast and DVD. The newer MPEG-4 is a much more ambitious standard and addresses speech and video synthesis, fractal geometry, computer visualization, and an artificial intelligence (AI) approach to reconstructing images. MPEG-4 addresses a standard way for authors to create and define the media objects in a multimedia presentation, how these can be synchronized and related to each other in transmission, and how users are to be able to interact with the media objects. Finally, MPEG-21, which is still under development, provides a larger, architectural framework for the creation and delivery of multimedia. Due to their widespread use and versatility, the MPEG standards have been adopted for a variety of consumer formats including Digital Versatile Disc (DVD), computer media files, and web-based streaming media, and Personal Video Recorder (PVR).


A PVR is an interactive TV recording device that is sometimes referred to as a digital video recorder (DVR), a personal TV receiver (PTR), a personal video station (PVS), or a hard disk recorder (HDR). Like the familiar video cassette recorder (VCR), a PVR records and plays back television programs, but, unlike the VCR, it stores the programs in digital (rather than analog) form. The PVR encodes an incoming video data stream as MPEG-1 or MPEG-2 and stores it on a computer-readable medium, generally a hard disk drive.


To view video files, a user needs a computer system or other electronic system with sufficient processor speed to render the video images adequately, internal memory to support the rendering, physical media storage space (such as a hard drive) to store the sometimes large MPEG files, and appropriate software to render the raw MPEG file into image data that can be displayed to the user. Ideally, such a system would also be small and portable in order to accommodate the mobility needs of its user.


While portable (e.g., hand-held) products are available to render digital video, music, and picture files for consumers, there is lacking in the art an easy-to-use personal media player that can be readily loaded with a variety of media files.


SUMMARY

A personal media player (PMP) uses a digital media processing system—comprising a video rendering subsystem, a music rendering subsystem, and a picture rendering subsystem—to produce moving-video (video), audio (music), still-graphics (picture), and other output rendered from media files ported to the PMP from another source. The PMP further comprises a user interface system, a display unit system, a power source system, and a data port system utilizing Universal Plug and Play functionality, all of which are coupled directly or indirectly to the digital media processing system. The physical components constituting the aforementioned systems and subsystems are then encased in a portable housing unit suitable for hand-held use and ready portability.





BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description of preferred embodiments, is better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there is shown in the drawings exemplary constructions of the invention; however, the invention is not limited to the specific methods and instrumentalities disclosed. In the drawings:



FIG. 1 is a block diagram illustrating functional components of one embodiment of a personal media player;



FIG. 2 is a block diagram illustrating physical components of one embodiment of a personal media player;



FIGS. 3A and 3B illustrate the external appearance from a top-view perspective of one embodiment of the personal media player;



FIGS. 4A and 4B illustrate two embodiments of the personal digital player while connected to external media content sources; and



FIG. 5 is a flow chart depicting one embodiment of the operation for porting digital media content to the personal media player using Universal Plug and Play (UPnP) functionality, a personal computer operating as a UPnP control point, and Digital Rights Management technology.





DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Overview


The following discussion is directed to a system comprising a portable device that receives, stores, and renders digital video. The subject matter is described with specificity to meet statutory requirements. However, the description itself is not intended to limit the scope of this patent. Rather, the inventors have contemplated that the claimed subject matter might also be embodied in other ways, to include different elements or combinations of elements similar to the ones described in this document, in conjunction with other present or future technologies.


Functional Components



FIG. 1 is a block diagram illustrating functional components of one embodiment of a personal media player 100. In this embodiment, the functional components comprising the personal media player 100 include a digital media processing system 102, a user interface system 110, a display unit system 112, a power source system 114, and a data port system 116. The digital media processing system 102 further comprises a video rendering 104, a music rendering subsystem 106, and a picture rendering subsystem 108.


The digital media processing system 102 is the central processing system for the personal media player 100 and is akin to similar or equivalent processing systems found in a variety of electronic devices such as personal computers (PCs), portable wireless handsets, palmtops, personal digital assistants (PDAs), pocket personal computers (PPCs), portable gaming systems, digital recording and playback systems, and other electronic devices.


Some of the primary functions of the digital media processing system 102 may include receiving media files downloaded to the unit, coordinating storage of such media files, recalling specific media files on demand, and rendering media files into audio/visual output for the user of the personal media player 100. Additional functions of the digital media processing system 102 may also include searching external resources for media files, coordinating Digital Rights Management protocols for protected media files, and interfacing directly with other recording and playback systems.


The digital media processing system 102 further comprises three subsystems: the video rendering subsystem 104 which handles all functionality related to video-based media files (includes files in MPEG and other formats); the music rendering subsystem 106 which handles all functionality related to audio-based media files including music (including files using MP3—that is, MPEG-1 Audio Layer-3—and other formats); and the picture rendering subsystem 108 which handles all functionality related to picture-based media files (including JPEG, GIF, and other picture formats). Although these subsystems are logically distinguished herein, each may in fact share hardware and software components with each other and with the rest of the personal media player 100.


Functionally coupled to the digital media processing system 102 is a user interface system 110 whereby the user of the personal media player 100 can, to a certain degree, control the operation of the device. A display unit system 112 is also functionally coupled to the digital media processing system and may comprise a video display and an audio output for playback of rendered video, music, and pictures media files. The display unit system 112 may also functionally support and compliment the operation of the user interface system 110 by providing visual and audio output to the user during operation.


The data port system 114 is also functionally coupled to the digital media processing system 102 and provides a means by which the personal media player 100 can interface with external electronic systems in order to download media content therefrom. In certain embodiments, the data port system 114 may comprise a Universal Serial Bus port, a network connection, or some other means of connectivity.


The personal media player 100 has a power source system 116 that provides power to the entire device. The power source system in this embodiment is coupled directly to the digital media processing system 102 and indirectly to the other systems and subsystems through the digital media processing system 102. The power source system 116 may also be directly coupled to any other system or subsystem of the personal media player 100—alternative configurations are well-known and understand by those skilled in the art—and thus any reference herein this specification or in the claims that the power source system 116 is coupled to the digital media processing system 102 should be interpreted to mean that the power source system 102 is directly or indirectly providing power to every system and subsystem of the personal media player 100 that requires electric power for operation. In the present embodiment, the power source may be a battery, a power converter/transformer, a solar converter, or any other type of electric-providing power source, portable or otherwise.


The foregoing functional elements and their corresponding physical components are fixed or enclosed by the portable housing unit 118. This portable handheld housing unit, which both protects the electronic components of the personal media player 100 as well as provides a medium in which the physical components can be fixed, may be limited in size to a total unit volume (length by width by height) of no more than fifty cubic inches in order to enable true “hand-held portability.”


Physical Components



FIG. 2 is a block diagram illustrating physical components of one embodiment of a personal media player 100 based on the functional components described in FIG. 1 (and denoted herein this figure by broken-line boxes), including the digital media processing system 102, the user interface system 110, the display unit system 112, the data port system 114, and the power source system 116. However, even though each physical component is shown as included in only a single functional component in the present figure, physical components may in fact be shared by more than one functional component, as understood and appreciated by those skilled in the art, and thus any reference herein this specification or in the claims to a specific physical component should not be interpreted as limiting the use of that component to the functional group in which FIG. 2 indicates it may belong.


As FIG. 2 demonstrates, one physical embodiment of the personal media player may comprise a central processor 202 coupled to a memory controller/chipset 204 by, for example, a multi-pin connection 238. The memory controller/chipset 204, in turn, may be coupled to random access memory (RAM) 206 and/or non-volatile flash memory 208. These components, through connectivity with the memory controller/chipset, may also be collectively coupled to an IDE hard disk drive 210 via an IDE controller 212, as well as to the rest of the functional component systems, via a system bus 236 that couples various system components to each other.


While the present embodiment specifies the use of RAM and/or non-volatile flash memory, various alternative embodiments are also possible. In general, the system memory may include computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) and random access memory (RAM) 132. Moreover, a basic input/output system (e.g., BIOS) containing the basic routines that help to transfer information between elements within the system such as during start-up, may be stored in ROM. RAM, on the other hand, typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by a processing unit.


Although the present embodiment specifies the use of an IDE hard disk drive 210, other computer-readable media may be substituted from among the variety of computer readable media available. In this regard, computer readable media can be any available media that can be accessed by a computer system and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CDROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.


In addition, the system bus 236 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus (also known as Mezzanine bus).


Together the aforementioned components constitute the digital media processing system 102, and each of these physical components also constitute the physical components of each of the three subsystems, the video rendering subsystem 104, the music rendering subsystem 106, the picture rendering subsystem 108, and, in an alternative embodiment, a Digital Rights Management subsystem (not shown).


Regarding the power supply system 116, a battery 226 may be used to provide power to the entire system via connectivity directly to the memory controller/chipset 204 (as shown), or by multiple connections to various physical components. The battery 226, in turn, may also be connected to a battery charger 228 which may be separate from the power supply system 116 and the personal media player 100 (as shown) or, alternately, which may be incorporated into the personal media player 100 and the power supply system.


An LCD panel 218 and its associated video/graphics controller 220, as well as an audio jack 222 and its associated audio controller/codec, may comprise the display unit system and may be directly or indirectly connected to the other physical components via the system bus 236. Likewise, navigation and control buttons 214 and the navigation and control button interface 216 may comprise the user interface system 110, and a Universal Serial Bus port 230 and a network port 234, along with a USB controller 232 and a network interface 236 respectively, may constitute the physical components of the data port system. These components also directly or indirectly connect to the other components via the system bus 236.


External Layout



FIGS. 3A and 3B illustrate the external appearance from a top-view perspective of one embodiment of the personal media player 100. (FIG. 3A illustrates the unit rendering a video media file while FIG. 3B illustrates the unit displaying a video file selection screen.) The portable housing unit 118 houses an LCD panel 218 on which video and picture images are displayed upon rendering. A left-side media select group 302 may enable the user of the personal media player 100 to select the media type for rendering, and the right-side media select group 304 may enable the user to select the specific media file to render and output, including standard controls for video and sound, a five-direction navigation button to browse media selections that may be displayed on the LCD panel 218, and/or volume control, among others. (The left-side media select group 302 and the right-side media select group 304 together comprise the navigation and control buttons 214 of FIG. 2.)


Accessing External Media Content Sources



FIGS. 4A and 4B illustrate two embodiments of the personal digital player 100 while connected to external media content sources. In each embodiment, the personal digital player 100, utilizing Universal Plug and Play (UPnP) functionality, is connected to network hub 404 or a wireless access point 424 either by a physical connection as shown in FIG. 4A or by a wireless connection with wireless network adapters 422, 426, and 428 as shown in FIG. 4B. In these examples, the hub 404 or wireless access point 424 is also connected, either physically or wirelessly, to a UPnP media server 406, a UPnP control point 412, and a DSL/Cable modem 420 which, in turn, is connected to a license server 410 via a distributed network medium such as the Internet 408.


Plug and Play (PnP) is a capability developed by Microsoft for its Windows 95 and later operating systems that gives users the ability to plug a device, such as a personal music player, directly into a personal computer or other computer system and have that computer recognize that the device is there and, thereafter, coordinate interaction between the computer and the device.


Universal Plug and Play (UPnP) has emerged as a parallel to PnP for network connected devices that uses Internet and Web protocols to enable devices such as PCs, peripherals, intelligent appliances, and wireless devices to be plugged into a network and automatically detect and coordinate interaction with each other. With UPnP, when a user plugs a device into a network, the device will configure itself to the network, acquire a TCP/IP address from the network, and use a discovery protocol based on the Internet's Hypertext Transfer Protocol (HTTP) to announce its presence on the network to other devices. For instance, if a user had a camera and a printer connected to the network and needed to print out a photograph, the user could press a button on the camera and have the camera send a “discover” request asking if there were any printers on the network. The printer, in turn, would identify itself and send its location in the form of a universal resource locator (URL). Thereafter the camera and printer would use Extensible Markup Language (XML) to establish a common language, or “protocol negotiation,” to talk to each other and determine the capabilities of the other device. Once a common language was established, the camera, for example, would control the printer and print the photograph the user selected.


Porting Media Content



FIG. 5 is a flow chart depicting one embodiment of the operation for porting digital media content to the personal media player 100 using Universal Plug and Play functionality, a personal computer operating as a UPnP control point 412, and Digital Rights Management technology. At block 502 the user connects the personal media player 100 to a network (via a hub 404 or wireless access point 424 as shown in FIGS. 4A and 4B respectively) and utilizing its UPnP functionality to start the process and identify the resources on the network (in this case, the UPnP media server 406) as described in FIG. 5. At block 504 the user, in this case using the UPnP control point (also referred to herein this figure as the “personal computer” or “PC” to reflect one possible embodiment), browses the UPnP media server and, at block 506, the UPnP application (running on the UPnP control point) issues a UPnP browse request to the UPnP media server 406. Based on information returned by the UPnP media server 406 to this request, at block 508 the UPnP application builds a list of digital media content available on the UPnP media server 406 and, at block 510, the user selects the media files to be transferred to the personal media player 100. At block 512 the UPnP application determines if the content is protected and, if not, at block 514 the UPnP application issues a UPnP import resource command to the UPnP media server 406. Upon receipt of the content at block 516, the media files are temporarily stored on the UPnP control point 412 so that, at block 518, the UPnP application can reformat the media files based on the personal media player's 100 rendering and playback capabilities. After reformat is complete, at block 520 the UPnP application issues a UPnP export resource command to export the media files to the personal media player 100 and, at block 522, the media files are moved from the UPnP control point 412 to the personal media player 100, which ends the process at block 550 and the personal media player 100 can be disconnected from the network (the hub 404 or wireless access point 424).


Returning to block 512, if the UPnP application determines that the content is indeed protected—such as protections afforded by Digital Rights Management technologies as known and well-understood by those of skill in the art (and described in additional detail herein below)—at block 524 the UPnP application retrieves the license for the selected content from the media server, at block 526 the UPnP application parses the license for usage rights established for the selected protected content. Based on these rights, the UPnP application can now ascertain if it is permissible to copy the selected content based on and, if not, the download process is immediately ended at block 550. On the other hand, if it is permissible to copy the selected content, at block 530 the UPnP application retrieves keys from the personal media player 100 and, at block 532, the UPnP application uses these keys to validate the personal media player 100 with the license server 410. If the personal media player 100 is not validated at block 534, and if the personal media player 100 has not been initialized at block 536, at block 538 the UPnP application initializes the personal media player 100 with the license server 410 and returns to block 534. On the other hand, if the personal media player 100 is not validated at block 534 and if the personal media player 100 has already been initialized at block 536, the process immediately terminates at block 550.


After the personal media player 100 is validated, at block 540 the UPnP application downloads new keys pertaining to the selected content from the license server 410 for the purpose of creating a portable license. At block 542 the UPnP application then issues a UPnP import resource command to the UPnP media server 406. Upon receipt of the content, at block 544 the media files are temporarily stored on the UPnP control point 412 so that, at block 546, the UPnP application can reformat the media files based on the personal media player's 100 rendering and playback capabilities. Furthermore, at block 548 the UPnP application also binds the content to the personal media player 100 using the portable license data provided by the UPnP media server 410, as such binding techniques are known and understood by those of skill in the art. After reformat and binding is complete, at block 520 the UPnP application issues a UPnP export resource command to export the media files to the personal media player 100 and, at block 522, the media files and portable licenses are moved from the UPnP control point 412 to the personal media player 100 which, in turn, ends the process at block 550 and the personal media player 100 can be disconnected from the network (the hub 404 or wireless access point 424).


In regard to the embodiment described above, Digital Rights Management (DRM) is a type of server software developed to enable secure distribution and prevent illegal distribution of paid content over the Web. Various DRM technologies have been developed as a means of protection against the online piracy of commercially marketed material which has proliferated through the widespread use of peer-to-peer file exchange programs. Although online content is protected by copyright laws, policing the Web and catching law-breakers is very difficult. DRM technology focuses on making it impossible to steal Web content in the first place, a much surer approach to the problem than the hit-and-miss strategies aimed at apprehending online poachers after the fact. A number of companies have released various DRM products based on a variety of approaches and technologies. In general, DRM products are turnkey packages that include everything needed for the operation, such as, for example, server software and user plug-ins.


For example, and not by way of limitation, ContentGuard DRM software uses XrML (Extensible Rights Markup Language) and has four major components: a protection toolkit that allows users to decide on their own access and encryption rules, a distribution toolkit that helps users create interfaces for content distribution, a consumer toolkit that verifies authorization before content is distributed, and a back-office component that tracks usage and licensing. Another example, InterTrust DRM, focuses on the protection of graphic and text content such as JPEG, GIF, and PDF files. And EMediator DRM works through a plug-in that users must download before they receive access to protected material. When the plug-in is downloaded, administrators can set various policies for access to different components of the content, such as print or copy restrictions set on material that may be freely viewed, or may set a time limit on access.


Although the present embodiment describes interactivity in a system where the UPnP control point 412 and the UPnP application are separate and distinct from the personal media player 100, an alternative embodiment of the present invention would be a personal media player 100 possessing some or all of the functionality of the UPnP control point 412 and/or the UPnP application. Another alternative embodiment of the present invention would also enable the personal media player 100 to control one or more of the processes described herein for porting media files to the PMP, as opposed to the entire porting process being entirely controlled by the UPnP control point 412.


Conclusion


The various techniques described herein may be implemented with hardware or software or, where appropriate, with a combination of both. Thus, the methods and apparatus of the present invention, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the invention. In the case of program code execution on programmable computers, the computer will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. One or more programs are preferably implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) can be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.


The methods and apparatus of the present invention may also be embodied in the form of program code that is transmitted over some transmission medium, such as over electrical wiring or cabling, through fiber optics, or via any other form of transmission, wherein, when the program code is received and loaded into and executed by a machine, such as an EPROM, a gate array, a programmable logic device (PLD), a client computer, a video recorder or the like, the machine becomes an apparatus for practicing the invention. When implemented on a general-purpose processor, the program code combines with the processor to provide a unique apparatus that operates to perform the indexing functionality of the present invention.


While the present invention has been described in connection with the preferred embodiments of the various figures, it is to be understood that other similar embodiments may be used or modifications and additions may be made to the described embodiment for performing the same function of the present invention without deviating there from. For example, while exemplary embodiments of the invention are described in the context of digital devices emulating the functionality of personal computers and PDAs, one skilled in the art will recognize that the present invention is not limited to such digital devices, as described in the present application may apply to any number of existing or emerging computing devices or environments, such as a gaming console, handheld computer, portable computer, etc. whether wired or wireless, and may be applied to any number of such computing devices connected via a communications network, and interacting across the network. Furthermore, it should be emphasized that a variety of computer platforms, including handheld device operating systems and other application specific operating systems, are herein contemplated, especially as the number of wireless networked devices continues to proliferate. Therefore, the present invention should not be limited to any single embodiment, but rather construed in breadth and scope in accordance with the appended claims.

Claims
  • 1. A device, comprising: a processor; anda memory communicatively coupled with the processor, the memory comprising instructions for performing the following: requesting, by the device, access to protected media content stored on a remote device;receiving a validation that the device can access the protected media content based on at least one validation key stored on the device;in response to receiving the validation, receiving, from the remote device the protected media content and at least one portable license key; andprocessing the protected media content using the portable license key.
  • 2. The device of claim 1, wherein the memory further comprises instructions for retrieving a license for the protected media content.
  • 3. The device of claim 2, wherein the memory further comprises instructions for determining whether to proceed with requesting the protected media content based upon the retrieved license.
  • 4. The device of claim 1, further comprising sending a validation key to the remote device.
  • 5. The device of claim 1, wherein the memory further comprises instructions for reformatting the received media content into a format suitable for rendering on the device.
  • 6. The device of claim 1, wherein the memory further comprises instructions for binding the received media content to the device.
  • 7. The device of claim 1, wherein the memory further comprises instructions for requesting a list of media content from the remote device.
  • 8. A computer storage device comprising computer-executable instructions for controlling access to media content, the instructions executable for implementing steps comprising: processing a request from a computing device for selected media content on a remote device;receiving, from the computing device, at least one key for validating the computing device with the remote device;validating the computing device with the remote device using the at least one key;transferring at least one portable license and at least one media file associated with the portable license to the computing device.
  • 9. The computer storage device of claim 8, further comprising instructions for retrieving a license for the selected media content.
  • 10. The computer storage device of claim 9, further comprising instructions for determining whether to proceed with requesting the selected media content based upon the retrieved license.
  • 11. The computer storage device of claim 8, wherein validating the computing device with the remote device comprises retrieving one or more keys from the computing device and forwarding the one or more keys to the remote device.
  • 12. The computer storage device of claim 8, further comprising instructions for reformatting the at least one media file associated with the portable license into a format suitable for rendering on the computing device.
  • 13. The computer storage device of claim 8, further comprising instructions for binding the at least one media file associated with the portable license to the computing device.
  • 14. The computer storage device of claim 8, further comprising instructions for receiving a request for a list of media content from the computing device and transmitting a request for a list of media content to the remote device.
  • 15. The computer storage device of claim 14, further comprising instructions for communicating a list of media content to the computing device.
  • 16. A computing system adapted to control access to media content, comprising: a remote computing device; anda computing memory communicatively coupled to the remote computing device, the computing memory having stored therein a software application adapted for the following: validating a computing device;receiving a request for available media content, wherein receiving the request comprises receiving a Universal Plug and Play (UPnP) browse request;receiving a request for selected media content, wherein the selected media content is associated with at least one key identifier; andcommunicating the selected media content and the at least one key identifier of the selected media content, wherein data derived from the at least one key identifier controls processing of the selected media content.
  • 17. The computing system of claim 16, wherein receiving a request for available media content comprises receiving at least one request to browse available media content.
  • 18. The computing system of claim 16, wherein receiving a request for selected media content comprises receiving a request to import at, least one media file associated with the selected media content.
  • 19. The computing system of claim 16, further comprising reformatting the selected media content based on the computing device's rendering capabilities.
  • 20. The computing system of claim 16, further comprising reformatting the selected media content based on the computing device's playback capabilities.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of, and claims priority to U.S. application Ser. No. 13/897,602, now U.S. Pat. No. 9,479,553, filed May 20, 2013, which is a continuation of, and claims priority to U.S. application Ser. No. 12/201,815, now U.S. Pat. No. 8,503,861, filed Aug. 29, 2008, which is a continuation of, and claims priority to U.S. application Ser. No. 10/384,923, now U.S. Pat. No. 7,426,329, filed Mar. 6, 2003, each of which is hereby incorporated by reference in their entirety.

US Referenced Citations (200)
Number Name Date Kind
4504701 Lucchesi Mar 1985 A
4527156 Yamaki et al. Jul 1985 A
4649499 Sutton et al. Mar 1987 A
4831368 Masimo et al. May 1989 A
5119079 Hube et al. Jun 1992 A
5134390 Kishimoto et al. Jul 1992 A
5142655 Drumm Aug 1992 A
5329577 Norimatsu Jul 1994 A
5334805 Knowles et al. Aug 1994 A
5337353 Boi et al. Aug 1994 A
5347295 Agulnick et al. Sep 1994 A
5396443 Mese et al. Mar 1995 A
5454043 Freeman Sep 1995 A
5481595 Ohashi et al. Jan 1996 A
5485600 Joseph et al. Jan 1996 A
5499334 Staab Mar 1996 A
5546301 Agrawal et al. Aug 1996 A
5574479 Odell Nov 1996 A
5586182 Miyashita Dec 1996 A
5588041 Meyer et al. Dec 1996 A
5602566 Motosyuku et al. Feb 1997 A
5657372 Ahlberg et al. Aug 1997 A
5661632 Register Aug 1997 A
5689664 Narayanan et al. Nov 1997 A
5689665 Mitsui et al. Nov 1997 A
5705599 Felixberger et al. Jan 1998 A
5705997 Park Jan 1998 A
5712911 Her Jan 1998 A
5714997 Anderson Feb 1998 A
5729604 Van et al. Mar 1998 A
5742264 Inagaki et al. Apr 1998 A
5761071 Bernstein Jun 1998 A
5812865 Theimer et al. Sep 1998 A
5835919 Stern et al. Nov 1998 A
5860016 Nookala et al. Jan 1999 A
5910882 Burrell Jun 1999 A
5924046 Martensson Jul 1999 A
5953683 Hansen et al. Sep 1999 A
5963952 Smith Oct 1999 A
5995852 Yasuda et al. Nov 1999 A
6038467 De Bliek et al. Mar 2000 A
6157935 Tran et al. May 2000 A
6088018 DeLeeuw et al. Jul 2000 A
6104969 Beeks Aug 2000 A
6115025 Buxton et al. Sep 2000 A
6119186 Watts et al. Sep 2000 A
6137468 Martinez et al. Oct 2000 A
6147678 Kumar et al. Nov 2000 A
6148149 Kagle Nov 2000 A
6148669 Roest Nov 2000 A
6154214 Uyehara et al. Nov 2000 A
6160899 Lee et al. Dec 2000 A
6181344 Tarpenning et al. Jan 2001 B1
6184847 Fateh et al. Feb 2001 B1
6201554 Lands Mar 2001 B1
6204852 Kumar et al. Mar 2001 B1
6215993 Ulveland Apr 2001 B1
6216016 Cronin Apr 2001 B1
6216106 John Apr 2001 B1
6246862 Grivas et al. Jun 2001 B1
6256019 Allport Jul 2001 B1
6259787 Schulze Jul 2001 B1
6262769 Anderson et al. Jul 2001 B1
6288704 Flack et al. Sep 2001 B1
6292674 David Sep 2001 B1
6295052 Kato et al. Sep 2001 B1
6298314 Blackadar et al. Oct 2001 B1
6304765 Cosgrove et al. Oct 2001 B1
6310955 Reeves Oct 2001 B1
6314426 Martin et al. Nov 2001 B1
6326978 Robbins Dec 2001 B1
6330457 Yoon et al. Dec 2001 B1
6335725 Koh et al. Jan 2002 B1
6340957 Adler et al. Jan 2002 B1
6370323 Adolph et al. Apr 2002 B1
6374040 Sakamoto et al. Apr 2002 B2
6374145 Lignoul Apr 2002 B1
6381540 Beason et al. Apr 2002 B1
6396506 Hoshino May 2002 B1
6408187 Merriam Jun 2002 B1
6426736 Ishihara Jul 2002 B1
6445383 Chambers et al. Sep 2002 B1
6449363 Kielsnia Sep 2002 B1
6452494 Harrison Sep 2002 B1
6466198 Feinstein Oct 2002 B1
6477117 Narayanaswami et al. Nov 2002 B1
6487663 Jaisimha et al. Nov 2002 B1
6492979 Kent et al. Dec 2002 B1
6498600 Vance et al. Dec 2002 B1
6509907 Kuwabara Jan 2003 B1
6516202 Hawkins et al. Feb 2003 B1
6518956 Sato Feb 2003 B1
6532447 Christensson Mar 2003 B1
6542436 Myllyla Apr 2003 B1
6560466 Shorko May 2003 B1
6567068 Rekimoto May 2003 B2
6567101 Thomas May 2003 B1
6573883 Bartlett Jun 2003 B1
6597384 Harrison Jul 2003 B1
6597817 Silverbrook Jul 2003 B1
6599130 Moehrle Jul 2003 B2
6545669 Kinawi et al. Aug 2003 B1
6621508 Shiraishi et al. Sep 2003 B1
6621800 Klein Sep 2003 B1
6623119 Lehmeier et al. Sep 2003 B2
6624824 Tognazzini et al. Sep 2003 B1
6631192 Fukiharu Oct 2003 B1
6658272 Lenchik et al. Dec 2003 B1
6686927 Meier et al. Feb 2004 B2
6721738 Verplaetse et al. Apr 2004 B2
6750848 Pryor Jun 2004 B1
6765553 Odamura Jul 2004 B1
6798429 Bradski Sep 2004 B2
6799195 Thibault et al. Sep 2004 B1
6809724 Shiraishi et al. Oct 2004 B1
6822683 Torikai Nov 2004 B1
6868543 Nusbickel Mar 2005 B1
6870956 Qi et al. Mar 2005 B2
6888532 Wong et al. May 2005 B2
6897368 Georges et al. May 2005 B2
6911916 Wang et al. Jun 2005 B1
6931592 Ramaley et al. Aug 2005 B1
6970182 Schultz et al. Nov 2005 B1
7006881 Hoffberg et al. Feb 2006 B1
7046230 Zadesky May 2006 B2
7084859 Pryor Aug 2006 B1
7103574 Peinado et al. Sep 2006 B1
7103852 Kariris Sep 2006 B2
7110664 Yogeshwar et al. Sep 2006 B2
7161618 Niikawa et al. Jan 2007 B1
7164432 Amemiya Jan 2007 B1
7190331 Genc et al. Mar 2007 B2
7200559 Wang Mar 2007 B2
7263607 Ingerman et al. Aug 2007 B2
7275092 Copp Sep 2007 B2
7289102 Hinckley et al. Oct 2007 B2
7299304 Saint-Hilaire et al. Nov 2007 B2
7302280 Hinckley et al. Nov 2007 B2
7409540 Ingerman et al. Aug 2008 B2
7426329 Calhoon et al. Sep 2008 B2
7460105 Rosenberg et al. Dec 2008 B2
7532196 Hinckley May 2009 B2
7626598 Manchester Dec 2009 B2
8120625 Hinckley Feb 2012 B2
8503861 Calhoon et al. Aug 2013 B2
9134760 Hinckley Sep 2015 B2
9189069 Hinckley et al. Nov 2015 B2
9479553 Calhoon et al. Oct 2016 B2
20010005687 Ushida et al. Jun 2001 A1
20010031633 Tuomela et al. Oct 2001 A1
20010035845 Zwern Nov 2001 A1
20010044318 Mantyjarvi et al. Nov 2001 A1
20010050672 Kobayashi Dec 2001 A1
20020021278 Hinckley et al. Feb 2002 A1
20020036622 Jaeger Mar 2002 A1
20020049738 Epstein Apr 2002 A1
20020053019 Ruttan et al. May 2002 A1
20020056575 Keely et al. May 2002 A1
20020091762 Sohn et al. Jul 2002 A1
20020091763 Shah et al. Jul 2002 A1
20020093491 Gillespie et al. Jul 2002 A1
20020116205 Ankireddipally et al. Aug 2002 A1
20020129068 Takasu et al. Sep 2002 A1
20020140675 Ali et al. Oct 2002 A1
20020149613 Gutta et al. Oct 2002 A1
20020184373 Maes Dec 2002 A1
20030009698 Linderman et al. Jan 2003 A1
20030030680 Cofta et al. Feb 2003 A1
20030055655 Suominen Mar 2003 A1
20030222917 Trantow Apr 2003 A1
20030085870 Hinckley May 2003 A1
20030104800 Zak Jun 2003 A1
20030105812 Flowers, Jr. et al. Jun 2003 A1
20030145094 Staamann et al. Jul 2003 A1
20030176205 Oota et al. Sep 2003 A1
20030188151 Sato et al. Oct 2003 A1
20030221876 Doczy et al. Dec 2003 A1
20040049743 Bogward Mar 2004 A1
20040078596 Kent, Jr. et al. Apr 2004 A1
20040139027 Molaro Jul 2004 A1
20040148356 Bishop, Jr. et al. Jul 2004 A1
20040153512 Friend Aug 2004 A1
20040156554 McIntyre Aug 2004 A1
20040175098 Calhoon et al. Sep 2004 A1
20040201595 Manchester Oct 2004 A1
20040203589 Want et al. Oct 2004 A1
20040204130 Khazaka et al. Oct 2004 A1
20040212597 Nuovo et al. Oct 2004 A1
20040243678 Smith Dec 2004 A1
20040257341 Bear et al. Dec 2004 A1
20050030255 Chiu et al. Feb 2005 A1
20050140696 Buxton Jun 2005 A1
20070180496 Fransdonk Aug 2007 A1
20110084984 Manchester Apr 2011 A1
20110090256 Manchester Apr 2011 A1
20110264928 Hinckley et al. Oct 2011 A1
20110265046 Hinckley et al. Oct 2011 A1
20110267263 Hinckley Nov 2011 A1
20150062180 Manchester Mar 2015 A1
20160150179 Calhoon et al. May 2016 A1
Foreign Referenced Citations (9)
Number Date Country
19651781 Jul 1997 DE
1063843 Mar 2006 EP
1889569 Feb 2008 EP
63284678 Nov 1988 JP
8292826 Nov 1996 JP
2000124970 Apr 2000 JP
2001094636 Apr 2001 JP
WO 1998014863 May 1998 WO
WO 1999022338 Jun 1999 WO
Non-Patent Literature Citations (269)
Entry
U.S. Appl. No. 13/175,651, Office Action dated Apr. 7, 2017, 31 pgs.
U.S. Appl. No. 13/175,651, Amendment and Response filed Nov. 21, 2016, 10 pgs.
U.S. Appl. No. 14/520,026, Office Action dated Dec. 6, 2016, 12 pgs.
U.S. Appl. No. 14/520,026, Amendment and Response filed Sep. 19, 2016, 20 pgs.
U.S. Appl. No. 13/897,602, Notice of Allowance dated Sep. 22, 2016, 2 pages.
“Motorola Cellular Telephone Owners Manual”, Retrieved From <<http://www.motorola.com/mdirect/manuals/Profile_300_user_Manual_pdf>>, Jul. 17, 2003, 64 Pages.
Fount, T., “Universal Plug and Play in Windows® XP”, In Microsoft Windows XP Operating System, Jul. 2001, 33 Pages.
“ESD Simulator System”, Top Class ESD Simulation, NSG 438 brochure, Feb. 2002, 6 pages.
“Upgraded ESD pistol exceeds all the standards”, Electronicstalk, Jun. 21, 2002, obtained online at: http://www.electronicstalk.com/news/sca/sca141.html, Apr. 19, 2011, 2 pages.
Bartlett, J.F., “Rock'n'Scroll Is Here to Stay,” IEEE Computer Graphics and Applications, pp. 40-45, (May/Jun. 2000).
Bolas, Mark T. “Human Factors in the Design of an Immersive Display,” Jan. 1994, IEEE Computer Graphics and Application, vol. 14, Issue 1, pp. 55-59.
DoubleClickWidth, http://technet.microsoft.com/en-us/library/cc978661(d=printer).aspx. Printed on Oct. 9, 2012.
DoubleClickWidth, http://technet.microsoft.com/en-us/library/cc978663(d=printer).aspx. Printed on Oct. 9, 2012.
Harrison, Beverly L. et al, “Squeeze Me, Hold Me, Tilt Me! An Exploration of Manipulative User Interfaces,” pp. 17-24 (Apr. 18-23, 1998), CHI '98.
Harrison, et al, “The Design and Use of Squeezable Computers: An Exploration of Manipulative User Interfaces,” Submitted to Conference on Human Factors in Computing Systems, Apr. 18, 1998, 8 pages.
Hinckley et al., “Two-Handed Virtual Manipulation”, ACM Transactions on Computer-Human Interaction, Sep. 1998, pp. 260-302, vol. 5, No. 3.
Hinckley, K. “Bumping Object Together as Semantically Rich Way Forming Connections between Ubiquitous Devices”, UbiComp 2003 Conference, Oct. 12, 2003.
Hinckley, K. Distribution and Local Sending Techniques for Face-to-Face Collaboration (Short Paper), Proceedings of the 5th International Conference on Multimodal Interfaces, Vancouver, British Columbia, Canada, pp. 81-84, Nov. 3-5, 2003.
Hinckley, K. “Synchronous Gestures for Multiple Persons and Computers”, Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology, Vancouver, Canada, pp. 149-158, Nov. 2-5, 2003.
Hinckley, Ken et al., “Sensing Techniques for Mobile Interaction”, CHI Letters, 2000, pp. 91-100, vol. 2, 2, UIST '00, San Diego, CA.
Hinckley, Ken et al., “Sticking: Pen Gestures that Span Multiple Displays”. Http://patrickbaudisch.com/publications/2004-Hinckley-AV104-Stiching.pdf, Oct. 6, 2003.
Manco, Giuseppe, et al., A Framework for Adaptive Mail Classification, ICAR-CNR-Institute of Italian National Research Council, 2002 IEEE, pp. 387-392.
McIntryre, U.S. Appl. No. 60/418,576, filed Oct. 15, 2002.
Microsoft Visual C# Programming: introduction to Dialog Boxes, 2010, retrieved at http://csharpkey.com/visualsharp/dlboxes/introduction.htm on Mar. 19, 2012.
One Page (19) from Technology Review dated Mar. 2002.
Pavlovic et al., “Visual Interpretation of Hand Gestures for Human-Computer Interaction: A Review”, IEEE Transactions on Pattern Analysis and Machine Intelligence, Jul. 1997, pp. 677-695, vol. 19, No. 7.
Rekimoto, et al. J., “SyncTap: An Interaction Technique for Mobile Networking”, New Generation of IP-Phone Enabled Mobile Devices, Mobile HCI 2002, pp. 319-323, 2002.
Rekimoto, Jun. “Tilting Operations for Small Screen Interfaces (Tech Note),” In Proceedings of the 9th Annual ACM Symposium on User Interface Software and Technology, Nov. 1, 1996, pp. 167-168.
Rotoview by Innoventions. “Features and Specifications”, 1995, 2003.
Rotoview by Innoventions. “How It Works”, 1995, 2003.
Rotoview by Innoventions. “The Intuitive Display Navigation Solution for Hand Held Devices”, 1995, 2003.
Schmidt, Albrect et al., “Advanced Interaction in Context,” 13 pages, HUC '00.
Schmidt, Albrect et al., “Implicit Human Computer Interaction Through Context,” pp. 1-5, 2nd Workship on Human Computer Interaction with Mobile Devices, 1999.
Schmidt, Albrect et al., “There Is More to Context Than Location,” Environment Sensing Technologies for Adaptive Mobile User Interfaces, 5 pages, IMC '98.
Shellconsize, http://technet.microsoft.com/en-us/library/cc938239(d=printer).aspx. Printed on Oct. 9, 2012.
Size, http://technet.microsoft.com/en-us/library/cc9838240(d=printer),aspx. Printed on Oct. 9, 2012.
Small., David et al., “Design of Spatially Aware Graspable Displays,” Extended Abstracts of CHI '97, pp. 1-2, (Mar. 22-27, 1997).
Stiefelhagen et al., “Gaze Tracking for Multimodal Human-Computer Interaction”, 1997 IEEE International Conference on Acoustics, Speech, and Signal Processing, ICASSP-97, Apr. 21-24, 1997, pp. 2617-2620, vol. 4.
Strietelmeier, Julie, “Official Gadgeteer Hands on Review: Casio E-100”, May 23, 1999, obtained online at: http://www.the-gadgeteer.com/e100-review.html, Jul. 19, 2004, 7 pages.
U.S. Appl. No. 09/875,477, Advisory Action dated Aug. 27, 2004, 3 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Feb. 9, 2004, 15 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Mar. 7, 2007, 14 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Apr. 10, 2006, 16 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed May 31, 2005, 15 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Jul. 6, 2004, 13 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Aug. 8, 2007, 10 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Sep. 25, 2006, 15 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Sep. 30, 2004, 15 pages.
U.S. Appl. No. 09/875,477, Amendment and Response filed Dec. 15, 2004, 7 pages.
U.S. Appl. No. 09/875,477, Final Office Action dated Apr. 30, 2004, 8 pages.
U.S. Appl. No. 09/875,477, Final Office Action dated Jun. 8, 2007, 7 pages.
U.S. Appl. No. 09/875,477, Non-Final Office Action dated Jan. 9, 2006, 12 pages.
U.S. Appl. No. 09/875,477, Non-Final Office Action dated Mar. 14, 2005, 10 pages.
U.S. Appl. No. 09/875,477, Non-Final Office Action dated Oct. 6, 2003, 15 pages.
U.S. Appl. No. 09/875,477, Non-Final Office Action dated Dec. 7, 2006, 9 pages.
U.S. Appl. No. 09/875,477, Non-Office Action dated Jun. 20, 2006, 12 pages.
U.S. Appl. No. 09/875,477, Notice of Allowance dated Aug. 24, 2007, 4 pages.
U.S. Appl. No. 10/162,487, Advisory Action dated Nov. 16, 2006, 3 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Jan. 30, 2006, 11 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Apr. 25, 2005, 11 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Apr. 27, 2007, 10 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Jul. 19, 2006, 13 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Sep. 13, 2007, 4 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Sep. 15, 2005, 10 pages.
U.S. Appl. No. 10/162,487, Amendment and Response filed Oct. 31, 2006, 9 pages.
U.S. Appl. No. 10/162,487, Final Office Action dated Jun. 5, 2007, 13 pages.
U.S. Appl. No. 10/162,487, Final Office Action dated Aug. 29, 2006, 20 pages.
U.S. Appl. No. 10/162,487, Final Office Action dated Dec. 1, 2005, 18 pages.
U.S. Appl. No. 10/162,487, Non-Final Office Action dated Jan. 7, 2005, 15 pages.
U.S. Appl. No. 10/162,487, None-Final Office Action dated Jan. 25, 2007, 12 pages.
U.S. Appl. No. 10/162,487, Non-Final Office Action dated Apr. 17, 2006, 17 pages.
U.S. Appl. No. 10/162,487, Non-Final Office Action dated Jun. 13, 2005, 16 pages.
U.S. Appl. No. 10/162,487, Notice of Allowance dated Sep. 27, 2007, 4 pages.
U.S. Appl. No. 10/294,286, Advisory Action dated Jan. 18, 2006, 3 pages.
U.S. Appl. No. 10/294,286, Amendment and response Filed Jan. 20, 2011, 12 pages.
U.S. Appl. No. 10/294,286, Amendment and response filed Jan. 26, 2010, 9 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Feb. 6, 2006, 8 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Apr. 15, 2009, 9 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Jun. 1, 2010, 10 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Jul. 10, 2006, 9 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Sep. 21, 2009, 9 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Sep. 28, 2010, 9 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Sep. 29, 2005, 7 pages.
U.S. Appl. No. 10/294,286, Amendment and Response filed Oct. 13, 2005, 10 pages.
U.S. Appl. No. 10/294,286, Appeal Brief filed Sep. 29, 2011, 23 pages.
U.S. Appl. No. 10/294,286, Appeal Brief filed Dec. 26, 2006, 19 pages.
U.S. Appl. No. 10/294,286, Examiner's Answer to Appeal Brief mailed Nov. 2, 2007, 12 pages.
U.S. Appl. No. 10/294,286, Final Office Action dated Mar. 23, 2011, 18 pages.
U.S. Appl. No. 10/294,286, Final Office Action dated Jul. 28, 2010, 13 pages.
U.S. Appl. No. 10/294,286, Final Office Action dated Aug. 22, 2006, 30 pages.
U.S. Appl. No. 10/294,286, Final Office Action dated Nov. 2, 2005, 7 pages.
U.S. Appl. No. 10/294,286, Final Office Action dated Dec. 9, 2009, 11 pages.
U.S. Appl. No. 10/294,286, Non-Final Office Action dated Mar. 1, 2010, 12 pages.
U.S. Appl. No. 10/294,286, Non-Final Office Action dated Apr. 6, 2006, 9 pages.
U.S. Appl. No. 10/294,286, Non-Final Office Action dated Apr. 25, 2007, 10 pages.
U.S. Appl. No. 10/294,286, Non-Final Office Action dated Jul. 1, 2009, 12 pages.
U.S. Appl. No. 10/294,286, Non-Final Office Action dated Jul. 22, 2005, 7 pages.
U.S. Appl. No. 10/294,286, Non-Final Office Action dated Oct. 20, 2010, 15 pages.
U.S. Appl. No. 10/294,286, Notice of Allowance dated Dec. 14, 2011, 7 pages.
U.S. Appl. No. 10/294,286, Notice of Appeal and Appeal Brief filed Jul. 25, 2007, 18 pages.
U.S. Appl. No. 10/294,286, Notice of Appeal filed Jul. 23, 2011, 2 pages.
U.S. Appl. No. 10/294,286, Response After Final Action filed Dec. 12, 2005, 4 pages.
U.S. Appl. No. 10/384,923, Advisory Action dated Jan. 31, 2008, 3 pages.
U.S. Appl. No. 10/384,923, Amendment and Response filed Jan. 22, 2008, 11 pages.
U.S. Appl. No. 10/384,923, Amendment and Response filed May 23, 2007, 6 pages.
U.S. Appl. No. 10/384,923, Amendment and Response filed Jun. 5, 2008, 12 pages.
U.S. Appl. No. 10/384,923, Amendment and Response filed Nov. 12, 2007, 8 pages.
U.S. Appl. No. 10/384,923, Notice of Allowance dated Jul. 9, 2008, 11 pages.
U.S. Appl. No. 10/384,923, Office Action dated Feb. 23, 2007, 11 pages.
U.S. Appl. No. 10/384,923, Office Action dated Jul. 23, 2007, 12 pages.
U.S. Appl. No. 10/384,923. Office Action dated Mar. 6, 2008, 12 pages.
U.S. Appl. No. 10/412,042, Advisory Action dated Jun. 25, 2007, 3 pages.
U.S. Appl. No. 10/412,042, Advisory Action dated Jun. 28, 2005, 3 pages.
U.S. Appl. No. 10/412,042, Advisory Action dated Aug. 23, 2005, 3 pages.
U.S. Appl. No. 10/412,042, Advisory Action dated Dec. 11, 2008, 3 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Jan. 24, 2007, 22 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Feb. 13, 2015, 25 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Feb. 16, 2010, 19 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Mar. 10, 2006, 16 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed May 21, 2009, 17 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed May 14, 2008, 19 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Jun. 7, 2005, 15 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Jun. 19, 2007, 17 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Jul. 9, 2015, 28 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Jul. 15, 2010, 21 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Aug. 2, 2005, 17 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Sep. 7, 2005, 18 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Sep. 15, 2009, 19 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Sep. 21, 2006, 19 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Oct. 18, 2004, 23 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Oct. 30, 2007, 18 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Nov. 25, 2008, 18 pages.
U.S. Appl. No. 10/412,042, Appeal Brief filed Mar. 9, 2011, 35 pages.
U.S. Appl. No. 10/412,042, Examiner's Answer dated Apr. 21, 2011, 37 pages.
U.S. Appl. No. 10/412,042, Non-Final Office Action dated Apr. 9, 2015, 49 pages.
U.S. Appl. No. 10/412,042, Non-Final Office Action dated Aug. 6, 2015. 52 pages.
U.S. Appl. No. 10/412,042, Non-Final Rejection dated Mar. 4, 2015, 49 pages.
U.S. Appl. No. 10/412,042, Non-Final Rejection dated Oct. 16, 2014, 42 pages.
U.S. Appl. No. 10/412,042, Notice of Allowance dated Feb. 10, 2014, 5 pages.
U.S. Appl. No. 10/412,042, Office Action dated Feb. 14, 2008, 31 pages.
U.S. Appl. No. 10/412,042, Office Action dated Feb. 17, 2009, 30 pages.
U.S. Appl. No. 10/412,042, Office Action dated Apr. 7, 2005, 27 pages.
U.S. Appl. No. 10/412,042, Office Action dated Apr. 15, 2010, 8 pages.
U.S. Appl. No. 10/412,042, Office Action dated Apr. 23, 2007, 31 pages.
U.S. Appl. No. 10/412,042, Office Action dated Jun. 15, 2009, 34 pages.
U.S. Appl. No. 10/412,042, Office Action dated Jul. 26, 2006, 31 pages.
U.S. Appl. No. 10/412,042, Office Action dated Jul. 30, 2004, 25 pages.
U.S. Appl. No. 10/412,042, Office Action dated Aug. 9, 2010, 35 pages.
U.S. Appl. No. 10/412,042, Office Action dated Aug. 28, 2008, 31 pages.
U.S. Appl. No. 10/412,042, Office Action dated Nov. 16, 2009, 32 pages.
U.S. Appl. No. 10/412,042, Office Action dated Nov. 17, 2006, 31 pages.
U.S. Appl. No. 10/412,042, Office Action dated Dec. 13, 2005, 33 pages.
U.S. Appl. No. 10/412,042, Patent Board Decision dated Feb. 3, 2014, 12 pages.
U.S. Appl. No. 10/412,042, Reply Brief filed Jun. 21, 2011, 10 pages.
U.S. Appl. No. 10/987,859, Advisory Action dated Feb. 1, 2008, 3 pages.
U.S. Appl. No. 10/987,859, Amendment and Response filed Jan. 16, 2008, 13 pages.
U.S. Appl. No. 10/987,859, Amendment and Response filed Feb. 21, 2007, 14 pages.
U.S. Appl. No. 10/987,859, Amendment and Response filed Mar. 12, 2009, 12 pages.
U.S. Appl. No. 10/987,859, Amendment and Response filed Jun. 16, 2009, 3 pages.
U.S. Appl. No. 10/987,859, Amendment and Response filed Aug. 8, 2007, 13 pages.
U.S. Appl. No. 10/987,859, Amendment and Response filed Oct. 29, 2008, 14 pages.
U.S. Appl. No. 10/987,859, Notice of Allowance dated Jun. 26, 2009, 6 pages.
U.S. Appl. No. 10/987,859, Notice of Allowance dated Oct. 14, 2009, 10 pages.
U.S. Appl. No. 10/987,859, Office Action dated May 17, 2007, 18 pages.
U.S. Appl. No. 10/987,859, Office Action dated Jul. 31, 2008, 12 pages.
U.S. Appl. No. 10/987,859, Office Action dated Nov. 16, 2007, 12 pages.
U.S. Appl. No. 10/987,859, Office Action dated Nov. 30, 2006, 15 pages.
U.S. Appl. No. 10/987,859, Office Action dated Dec. 12, 2008, 4 pages.
U.S. Appl. No. 12/201,815, Amendment filed Feb. 14, 2013 (9 pages).
U.S. Appl. No. 12/201,815, Amendment filed Jul. 23, 2012 (16 pages).
U.S. Appl. No. 12/201,815, Final Office Action dated Nov. 20, 2012 (17 pages).
U.S. Appl. No. 12/201,815, Non-Final Office Action dated Apr. 23, 2012 (20 pages).
U.S. Appl. No. 12/201,815, Notice of Allowance dated Feb. 28, 2013 (10 pages).
U.S. Appl. No. 12/201,815, Notice of Allowance dated Jun. 19, 2013, 2 pages.
U.S. Appl. No. 12/201,815, Preliminary Amendment filed Apr. 16, 2010 (8 pages).
U.S. Appl. No. 12/974,173, Amendment and Response filed Feb. 14, 2014, 19 pages.
U.S. Appl. No. 12/974,173, Amendment and Response filed Jun. 26, 2013, 9 pages.
U.S. Appl. No. 12/974,173, Amendment and Response filed Jul. 28, 2011, 18 pages.
U.S. Appl. No. 12/974,173, Amendment and Response filed Oct. 11, 2013, 10 pages.
U.S. Appl. No. 12/974,173, Amendment and Response filed Dec. 7, 2011, 8 pages.
U.S. Appl. No. 12/974,173, Final Office Action dated Mar. 7, 2014, 12 pages.
U.S. Appl. No. 12/974,173, Final Office Action dated Jul. 11, 2013, 13 pages.
U.S. Appl. No. 12/974,173, Non-Final Office Action dated Mar. 26, 2013 (13 pages).
U.S. Appl. No. 12/974,173, Non-Final Office Action dated Nov. 14, 2013, 31 pages.
U.S. Appl. No. 12/974,173, Office Action dated Feb. 14, 2011, 25 pages.
U.S. Appl. No. 12/974,173, Office Action dated Sep. 7, 2011, 10 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Feb. 3, 2015, 15 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Apr. 4, 2014, 13 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Jun. 25, 2013, 9 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Jul. 9, 2015, 16 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Jul. 28, 2011, 13 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Sep. 5, 2014, 16 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Oct. 11, 2013, 11 pages.
U.S. Appl. No. 12/974,327, Amendment and Response filed Dec. 7, 2011, 10 pages.
U.S. Appl. No. 12/974,327, Final Office Action dated Feb. 20, 2015, 29 pages.
U.S. Appl. No. 12/974,327, Final Office Action dated May 5, 2014, 18 pages.
U.S. Appl. No. 12/974,327, Final Office Action dated Jul. 11, 2013, 15 pages.
U.S. Appl. No. 12/974,327, Final Office Action dated Aug. 5, 2015, 29 pages.
U.S. Appl. No. 12/974,327, Non-Final Office Action dated Mar. 25, 2013 (13 pages).
U.S. Appl. No. 12/974,327, Non-Final Office Action dated Apr. 9, 2015, 30 pages.
U.S. Appl. No. 12/974,327, Non-Final Office Action dated Nov. 4, 2014, 25 pages.
U.S. Appl. No. 12/974,327, Non-Final Office Action dated Dec. 4, 2013, 18 pages.
U.S. Appl. No. 12/974,327, Office Action dated Feb. 14, 2011, 15 pages.
U.S. Appl. No. 12/974,327, Office Action dated Sep. 7, 2011, 13 pages.
U.S. Appl. No. 13/175,649 Non-Final Office Action dated Jun. 2, 2014, 18 pages.
U.S. Appl. No. 13/175,649, Amendment and Response filed Feb. 24, 2014, 12 pages.
U.S. Appl. No. 13/175,649, Amendment and Response Filed Mar. 19, 2012, 7 pages.
U.S. Appl. No. 13/175,649, Amendment and Response filed Apr. 2, 2015, 11 pages.
U.S. Appl. No. 13/175,649, Amendment and Response Filed Jul. 27, 2012, 7 pages.
U.S. Appl. No. 13/175,649, Amendment and Response filed Aug. 26, 2014, 14 pages.
U.S. Appl. No. 13/175,649, Amendment and Response filed Aug. 30, 2013, 8 pages.
U.S. Appl. No. 13/175,649, Final Office Action dated May 2, 2012, 9 pages.
U.S. Appl. No. 13/175,649, Final Office Action dated Oct. 25, 2013, 14 pages.
U.S. Appl. No. 13/175,649, Final Office Action dated Dec. 19, 2014, 19 pages.
U.S. Appl. No. 13/175,649, Non-Final Office Action dated Jun. 13, 2013, 14 pages.
U.S. Appl. No. 13/175,649, Non-Final Office Action dated Dec. 19, 2011, 7 pages.
U.S. Appl. No. 13/175,649, Notice of Allowance dated Jul. 8, 2015, 5 pages.
U.S. Appl. No. 13/175,649, Notice of Allowance dated Jul. 16, 2015, 4 pages.
U.S. Appl. No. 13/175,649, Notice of Allowance dated Aug. 5, 2015, 4 pages.
U.S. Appl. No. 13/175,649, Notice of Allowance dated Aug. 19, 2015, 2 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Feb. 27, 2014, 9 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed May 1, 2013, 7 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Jun. 25, 2012, 8 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Jul. 9, 2015, 11 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Aug. 30, 2013, 8 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Sep. 23, 2014, 9 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Oct. 10, 2012, 8 pages.
U.S. Appl. No. 13/175,651, Final Office Action dated Jun. 16, 2014, 21 pages.
U.S. Appl. No. 13/175,651, Non-Final Office Action dated Feb. 1, 2013, 11 pages.
U.S. Appl. No. 13/175,651, Non-Final Office Action dated Feb. 24, 2012, 9 pages.
U.S. Appl. No. 13/175,651, Non-Final Office Action dated Apr. 9, 2015, 23 pages.
U.S. Appl. No. 13/175,651, Non-Final Office Action dated Jul. 10, 2012, 10 pages.
U.S. Appl. No. 13/175,651, Non-Final Office Action dated Jul. 26, 2013, 17 pages.
U.S. Appl. No. 13/175,651, Non-Final Office Action dated Nov. 29, 2013, 17 pages.
U.S. Appl. No. 13/175,655, Amendment and Action filed Feb. 10, 2015, 5 pages.
U.S. Appl. No. 13/175,655, Amendment and Response filed Apr. 25, 2012, 9 pages.
U.S. Appl. No. 13/175,655, Amendment and Response filed May 2, 2014, 11 pages.
U.S. Appl. No. 13/175,655, Amendment and Response filed May 13, 2015, 6 pages.
U.S. Appl. No. 13/175,655, Amendment and Response filed Aug. 22, 2013, 8 pages.
U.S. Appl. No. 13/175,655, Amendment and Response filed Aug. 26, 2014, 11 pages.
U.S. Appl. No. 13/175,655, Amendment and Response filed Sep. 27, 2012, 8 pages.
U.S. Appl. No. 13/175,655, Final Office Action dated Jan. 2, 2014, 15 pages.
U.S. Appl. No. 13/175,655, Final Office Action dated Nov. 10, 2014, 19 pages.
U.S. Appl. No. 13/175,655, Final Office Action dated Jun. 27, 2012, 11 pages.
U.S. Appl. No. 13/175,655, Non-Final Office Action dated May 27, 2014, 16 pages.
U.S. Appl. No. 13/175,655, Non-Office Action dated Jan. 25, 2012, 10 pages.
U.S. Appl. No. 13/175,655, Non-Office Action dated May 22, 2013, 12 pages.
U.S. Appl. No. 13/175,655, Notice of Allowance dated Mar. 6, 2015, 3 pages.
U.S. Appl. No. 13/175,655, Notice of Allowance dated Feb. 20, 2015, 7 pages.
U.S. Appl. No. 13/175,655, Notice of Allowance dated May 27, 2015, 8 pages.
U.S. Appl. No. 13/897,602, Amendment and Response filed Jul. 22, 2015, 14 pages.
U.S. Appl. No. 13/897,602, Amendment and Response filed Jul. 29, 2015, 14 pages.
U.S. Appl. No. 13/897,602, Non-Final Office Action dated Jan. 22, 2015, 23 pages.
U.S. Appl. No. 13/897,602, Notice of Allowance dated Aug. 20, 2015, 6 pages.
Weimer et al., “A Synthetic Visual Environment with Hand Gesturing and Voice Input”, CHI '89 Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, May 1989, pp. 235-240, vol. 20, Issue SI.
Zhai et al., “Dual Stream Input for Pointing and Scrolling”, CHI 97, Late-Breaking/Short Talks, Mar. 22-27, 1997, pp. 305-306.
“Microsoft Computer Dictionary, Fifth Edition”, Microsoft Press, 2002, 648 Pages.
U.S. Appl. No. 13/897,602, Notice of Allowance dated Oct. 29, 2015, 2 pages.
U.S. Appl. No. 13/897,602, Notice of Allowance dated Jan. 13, 2016, 6 pages.
U.S. Appl. No. 10/412,042, Amendment and Response filed Nov. 6, 2015, 31 pages.
U.S. Appl. No. 10/412,042, Final Office Action dated Dec. 7, 2015, 57 pages.
U.S. Appl. No. 13/175,651, Final Office Action dated Oct. 22, 2015, 28 pages.
U.S. Appl. No. 13/175,651, Amendment and Response filed Feb. 22, 2016, 13 pages.
U.S. Appl. No. 13/897,602, Amendment after Allowance filed Aug. 5, 2016, 3 pages.
U.S. Appl. No. 13/897,602, USPTO Response dated Aug. 18, 2016, 2 pages.
U.S. Appl. No. 13/175,651, Office Action dated Jul. 26, 2016, 26 pages.
U.S. Appl. No. 13/897,602, Notice of Allowance dated May 5, 2016, 6 pages.
U.S. Appl. No. 13/897,602, Notice of Allowance dated Jun. 29, 2016, 2 pages.
U.S. Appl. No. 14/520,026, Office Action dated May 19, 2016, 33 pgs.
Related Publications (1)
Number Date Country
20160150179 A1 May 2016 US
Continuations (3)
Number Date Country
Parent 13897602 May 2013 US
Child 14946114 US
Parent 12201815 Aug 2008 US
Child 13897602 US
Parent 10384923 Mar 2003 US
Child 12201815 US