Patent Grant
7856564
1. Field of the Invention
The present invention relates to media devices and, more specifically, to portable media players that store and utilize digital media assets.
2. Description of the Related Art
Today, USB drives, also referred to as Flash drives or keychain drives, are popular portable data storage devices. A USB drive can be used in place of other storage mediums such as floppy disks, CDs, DVDs, zip drive disks, etc. In most cases, the USB drive is a plug and play device that includes Flash memory for storing data and a USB connector for connecting to a host device. While these devices work well, they are limited in the operations that they can perform. These devices are only configured for storing and transporting stored data (similar to other portable storage mediums) and therefore they do not include processing components, batteries for powering the processing components, or a user interface that enable users to communicate with the processing components.
Portable media players, also referred to as MP3 players, are also popular today. Portable media players can be grouped into three different categories: those with removable media storage, such as CD or DVD players; those with internal hard drives; and those that store media in non-volatile memory. Each category of portable media player has advantages and drawbacks in terms of size, functionality, battery life, and media storage capabilities.
Those portable media players that store media in non-volatile memory are commonly referred to as Flash MP3 players or Flash media players. Flash media players are often smaller than other types of portable media players. One problem common to many conventional Flash media players is that their small size often results in difficult-to-use media player controls. Although conventional Flash media players typically incorporate a display so that a user can navigate through the media files that are stored on the device, the display adds to the size, weight and power consumption. Even with a display, the media player controls are often not user friendly.
Another common problem with conventional Flash media players is bulky batteries, which are typically required to provide a reasonably long battery life before having to recharge the player or replace the player's batteries. Conventionally, media player designs have been made larger in order to accommodate improved user controls, batteries, and/or a display.
As portable media players have become more popular, there has been an increased demand for improved media player design. Thus, there remains a need for media players having improved user controls, small sizes, and longer battery life.
Broadly speaking, the invention relates to a media device and methods for operating a media device. The invention is particularly suitable for use with portable media players.
According to one aspect of the invention, a portable media device has the capability to store media device status information in persistent memory before powering down. Thereafter, when the portable media device is again powered up, the stored media player status information can be retrieved and utilized.
According to another aspect of the invention, a method allows a media device to form and/or traverse a media asset playlist in an efficient manner. The media asset playlist can, for example, pertain to a media asset continuous playlist or a media asset shuffle playlist.
The invention can be implemented in numerous ways, including as a method, system, device, apparatus, or computer readable medium. Several embodiments of the invention are discussed below.
As a method for operating a portable media player having a memory device, one embodiment of the invention includes at least the acts of: obtaining media player status information for the media player prior to powering down the media player; storing the media player status information in the memory device of the portable media player, the media player status information characterizes a state of the media player; and subsequently restoring the media player to its former state using the media player status information previously stored in the memory device once the media player is powered up.
As a method for operating a portable media player, another embodiment of the invention includes at least the acts of: receiving a first command to power down the media player; obtaining media player status information for the media player after the command to power off the media player has been received; storing the media player status information in persistent memory of the portable media player; and subsequently powering off the media player.
As a computer readable medium including at least computer program code for operating a portable media player having a memory device, one embodiment of the invention includes at least: computer program code for obtaining media player status information for the media player prior to powering down the media player; computer program code for storing the media player status information in the memory device of the portable media player, the media player status information characterizes a state of the media player; and computer program code for subsequently restoring the media player to its former state using the media player status information previously stored in the memory device once the media player is powered up.
As a method for presenting media assets on a portable media player, one embodiment of the invention includes at least the acts of: identifying a list of media assets to be presented on the portable media player; receiving a user input to initiate a shuffle action; and shuffling the list of media assets in response to the user switch input initiating the shuffle action, the shuffling being deferred until a media asset of the list of media assets being presented, if any, has completed.
As a method for presenting media assets on a portable media player, another embodiment of the invention includes at least the acts of: identifying a list of media assets to be presented on the portable media player; selecting one of the media assets from the list of media assets; presenting the selected media asset via the portable music player; receiving, during the presenting, a user input requesting a shuffle action; processing the shuffle action, if still present, once the presenting of the selected media asset has completed; shuffling the list of media assets following the processing, thereby producing a shuffled list; selecting another of the media assets from the shuffled list; and presenting the selected another media asset via the portable music player.
Other aspects and advantages of the invention will become apparent from the following detailed description taken in conjunction with the accompanying drawings which illustrate, by way of example, the principles of the invention.
The invention will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
In general, the invention relates to a media device and methods for operating a media device. The invention is particularly suitable for use with portable media players.
Embodiments of various aspects of the invention are discussed below with reference to
According to one aspect of the invention, a media device can also function as a solid-state drive for data storage. The solid-state drive can store not only media content for media items that can be played or otherwise presented by the portable media device but also data unrelated to media content.
In one embodiment, the form factor of the portable media device is hand-held or smaller. The portable media device may, for example, be small and lightweight enough to be carried in one hand, worn, or placed in a pocket. Although the form factor is generally small and hand-held (or palm-sized), the configuration of the device can vary widely. Some examples of configurations for the form factor are: an elongated stick, a memory stick, a memory drive (e.g., USB drive), etc. In one implementation, the portable media player has no display (display screen).
In another embodiment, the portable media device can use one or more status indicators. The indicators can be audio or visual. As an example, the status indicators can be implemented by dedicated light sources, such as light emitting diodes (LEDs). The indicators can provide visual feedback to a user.
In another embodiment, the portable media device can include a peripheral bus connector that enables the portable media device to removably and easily connect to a peripheral bus port operatively coupled to a host device, such as a personal computer. The portable media device can, therefore, communicate with the host device without using cables or other support devices, i.e., plugs directly into the host device. By way of example, the portable media device may share media files with the host device (or vice versa).
In another embodiment, the portable media device can include a battery and, more particularly, a rechargeable battery. In most cases, the battery serves to power components of the portable media device. In some cases, the battery can be recharged via a peripheral bus.
In yet another embodiment, the portable media device can include one or more input devices so that the portable media device can interact with a user. The input devices may, for example, include switches (e.g., slider switch, buttons, etc.) for controlling media operations or mode/state of the portable media device. In one particular implementation, a slider switch is used to select a media play mode.
As shown in
The media device 100 also includes a memory device 106 for storing data. The data can be transferred back and forth between the media device 100 and the host device when the media device 100 is attached to the host device. The data may include media files (e.g., audio tracks), data files, and/or the like. The memory device 106 may be widely varied. In one particular embodiment, the memory device 106 is non-volatile memory, such as solid-state memory (e.g., Flash memory). Solid-state memory has many advantages over other types of memory devices. One advantage of the solid-state memory is that it tends to be very robust because there are no moving parts to break or skip (e.g., embodiment as an integrated circuit chip). Another advantage of solid-state memory is that the memory device tends to be small and lightweight and therefore lends itself to the portability of the media device 100.
In one embodiment, the media device 100 includes a media module 108 for controlling media operations on the media device. The media can, for example, be audio, video, images and/or the like. The media module 108 may, for example, be used to present (e.g., play) media on the media device 100. Hence, the media device 100 can be considered a media player. The media module 108 cooperates with the memory device 106 to store and retrieve media data. For example, the media module 108 may access the memory device 106 to obtain or deliver media data such as audio tracks (e.g., songs) and/or images (e.g., photos).
In one embodiment, the media device 100 includes an on-board battery 110 for providing power to the media device 100. The on-board battery 110 can, for example, power the media device 100 so that the media device 100 can be fully portable and operate when disconnected from any host device. The on-board battery 110 may be a fixed charged battery that needs to be replaced from time to time or the on-board battery may be a rechargeable battery. By way of example, the on-board battery 110 may be an alkaline battery, NiCad battery, Lithium Ion battery, or other type of battery. Rechargeable batteries are typically preferred over fixed charged batteries since they rarely have to be replaced (ease of use). In some cases, the rechargeable battery can be charged through the power functionality of the connector 104 when the connector 104 is operatively coupled to the port of a host device.
In one embodiment, the media device 100 includes one or more input devices 112. The input devices 112 are configured to transfer data from the outside world into the media device 100. The input devices 112 can, for example, be used to make selections or issue commands for the media device 100. By way of example, the input devices 112 may be selected from buttons, switches, keypads, wheels, joysticks, joy pads, touch screens, touch pads, track balls, and/or the like.
In one particular implementation, the input device 112 is embodied as a sliding switch that slides between various positions in order to change the state or mode of the media device 100. For example, in the case in which the media device 100 provides playing of audio tracks (e.g., music or songs), the sliding switch may include an off position, a shuffle play mode position, and a continuous play mode position. When the sliding switch is in the off position, the audio functionality of the media device 100 is turned off. When in the continuous play mode position, the media device 100 plays audio tracks in some predetermined order (e.g., alphabetically by composer or song title). When in the shuffle play mode position, the media device 100 randomly selects a group of audio tracks and then plays the audio tracks in the selected order.
In another implementation, the input device 112 is embodied as one or more clickable buttons that may be clicked in order to control some aspect of the media device 100. For example, in the case of the media device 100 that includes audio functionality, the clickable buttons may correspond to commands such as previous, next, volume up, volume down and play/pause.
In one embodiment, the media device 100 includes one or more output devices 114. The output devices 114 are configured to transfer data from the media device 100 to the outside world. The output devices 114 can, for example, be used to output audio or visual information to the user. The output devices 114 may be selected from speakers, audio jacks, indicators and/or the like.
Although conventional media devices mandate use of displays (display screens), such as liquid crystal displays (LCDs), for user interaction, the media device 100 advantageously need not include such a display. In one particular implementation, the media device 100 does not include a display, but includes (i) an audio jack for supplying audio output to a headset or external speakers and (ii) one or more indicators that provide user feedback and/or status of the media device. For example, the indicators may inform the user when a particular input device 112 has been actuated or may inform the user of status of battery life. By eliminating a display, the media device 100 can not only have a small form factor and be highly portable, but also reduce power consumption of the media device and therefore extend the life of the battery 110. As a result, the media device 100 can be used for longer periods of time without recharging or changing the on-board battery 110.
The position of the I/O devices 112 and 114 relative to the housing 102 may be widely varied. For example, the I/O devices 112 and 114 may be placed at any external surface of the housing 102 that is accessible to a user during manipulation of the media device 100 (e.g., top, side, front, or back).
In one implementation, the input devices 112 are generally positioned at locations that allow for one-handed operation of the input device 112, and more particularly at locations that allow manipulation with a single finger while holding the media device 100 with one hand. In one particular implementation, the input devices 112 are placed at an upper half of the housing 102. The input devices 112 can therefore be actuated by a thumb of a user's hand when the media device 100 is held by the fingers and palm of the user's hand. The output devices 114 are typically placed at locations that allow access thereto when the media device 100 is held in the user's hand. The output devices 114 may, for example, be placed above the input devices 112 so that they can be accessed when the user is manipulating the input devices 112. By orienting the I/O devices 112 and 114 in this manner, the media device 100 does not have to be constantly repositioned in order to effectively utilize the I/O devices 112 and 114. For example, undesirable repositioning may be necessary if buttons are placed in a row from the top to bottom of the device.
It should be noted that the various embodiments, implementations or features described above can be used separately or in combination. For example, the media device 100 including the connector 104 and the memory device 106 may only be configured with one of the embodiments described above (e.g., only an input device 112). Alternatively, the media device 100 including the connector 104 and the memory device 106 may be configured with two or more of the embodiments described above (e.g., an input device 112 and an output device 114). Alternatively, the media device 100 including the connector 104 and the memory device 106 may integrate all the embodiments described above. By way of example, the media device 100 may integrate the functionality of the accessible connector 104, the memory device 106, the media module 108, the battery 110 and the various I/O devices 112 and 114 into a single all-in-one unit, i.e., all the elements are contained within or positioned on the housing 102 of the media device 100. As a result, no support devices are needed (such as attachable battery packs or I/O devices) when operating the media device 100 away from a host device, i.e., the media device 100 is capable of both storing data as well as controlling, playing and outputting media when on the go. It should be emphasized that in this implementation, the connector 104 is accessible or exposed since its not plugged into any support devices. As such, the user can easily plug the connector 104 into a host device or other device (e.g., a dock, holder, battery pack, or lanyard). The media device 100 can also include a cover that removably attaches to and covers the connector 104.
Alternatively or additionally, the media device 100 may include imaging components for capturing and viewing images. In cases such as these, the media device 100 may act like a camera.
Typically, the media device 200 acts like a storage device (data can be transferred to and from the media device 200) when connected to a host device, and acts as a media player when removed from the host device (songs can be played). Alternatively or additionally, the media device 200 may act like a media player when connected to a host device (i.e., can be used to drive playing of music on the host device). It should be emphasized that all the components needed to support these devices when removed from the host device are contained within or positioned on the media device 200. No other support devices are needed to operate the components of the media device 200 (e.g., contains a battery and I/O devices).
As shown in
The media device 200 also includes a peripheral bus connector 204 that extends out a bottom end of the housing 202. The peripheral bus connector 204 is configured for insertion into a port so that data may be transferred between the media device 200 and a host device (see
As shown, the cross-section of the housing 202 is typically slightly larger than the cross-section of the connector 204, and the length of the housing 202 is typically configured so that the media device 200 can be easily held in a user's hand while providing enough storage for the internal components (see
The media device 200 also includes an audio jack 206 that allows audio information to be output from the media device 200. The audio jack 206 can, for example, receive an audio plug connected to a speaker or a headset (e.g., earphones).
The media device 200 also includes a clickable button actuator 208 located on one side of the housing 202 and a sliding modal switch 214 located on an opposite side of the housing 202. Each of these input devices 208 and 214 allows a user to interact with the media device 200, i.e., provide user inputs. The clickable button actuator 208 provides playback controls for the media player aspect of the media device 200, while the sliding modal switch 214 provides a means for switching between various modes of the media player. More generally, the clickable button actuator 208 is a control input device.
To elaborate, the clickable button actuator 208 is located in a top region on the front side of the housing 202. The clickable button actuator 208 includes a plurality of peripheral buttons 210 that surround a center button 212. In one particular embodiment, the clickable button actuator 208 has a circular arrangement. In the case of a media player, the peripheral buttons 210 may correspond to previous, next, volume up and volume down, and the center button 212 may correspond to play/pause. Moreover, press and hold of the center button 212 can correspond to shuffle. The peripheral buttons 210 may be separate devices that each provide their own clicking action or they may be integrated into a single device that provides a plurality of clicking actions. If the latter, the single device can be divided into a plurality of independent and spatially distinct button zones. The button zones represent regions of the single device that may be tilted or depressed relative to the housing 202 in order to implement a distinct clicking action.
Although not shown, in one embodiment, the clicking actions are arranged to actuate one or more movement indicators contained inside the housing 202. That is, a particular button or button zone 210, 212 moving from a first position (e.g., upright) to a second position (e.g., depressed) is caused to actuate a movement indicator. The movement indicators are configured to detect movements (e.g., a clicking action) and to send signals corresponding to the movements to a controller of the media device 200. By way of example, the movement indicators may be switches, sensors and/or the like. In most cases, there is a movement indicator for each button or button zone 210, 212.
As shown in
In one embodiment, the input device 208 and 214 for the media device 200 are provided only on a front or back surface of the housing 202 for the media device 200. In such an embodiment, there are no input devices on the sides of the media device 200. Advantageously, accidental inputs can reduced and the sides of the media device 200 can be used to grip and hold the media device 200.
The media device 200 does not include a display, but does however include one or more indicators that indicate events associated with the media device 200. By way of example, the events may relate to signals, conditions or status of the media device 200. In one embodiment, the indicators, which can include light sources such as light emitting diodes (LED), are typically normally not illuminated but are illuminated for a limited duration when an event occurs. Furthermore, the indicator may turn on and off (e.g., blink) or cycle with increasing or decreasing intensity, and in some cases may even change colors in order to provide more detailed information about the event that is being monitored. In general, the indicators can also be referred to as status indicators or media device status indicators.
The indicators may be conventional indicators that typically include a small clear plastic insert, which is located in front of the LED, and which is inserted within an opening in the housing thus causing it to exist at the surface of the housing. The LED itself may also be placed in the opening in the housing rather than using an insert. Alternatively, the indicator can be configured not to break the surface of the housing. In this configuration, the light source is disposed entirely inside the housing. The indicator can be configured to illuminate a portion of the housing thereby causing the housing to change its appearance, i.e., change its color. By way of example, a change in color may indicate a change in status of the media device 200. During operation, an indicator light appears on the surface of the housing 202 when the indicator is on, and it disappears from the surface of the housing 202 when the indicator is off. One advantage of this type of indicator is that there is no trace of the indicator when the indicator is off. In other words, the indicator can be perceived only when the indication (e.g., indicator light) is turned on. Furthermore, the indicator avoids substantial breaks, lines, pits or protrusions in the surface of the housing 202, which are aesthetically unpleasing and degrade the look of the media device 200. Example of indicators of this type are disclosed in greater detail in U.S. patent application Ser. No. 10/773,897, filed Feb. 6, 2004 and entitled “ACTIVE ENCLOSURE FOR COMPUTING DEVICE,” which is herein incorporated by reference.
In the illustrated embodiment, the media device 200 includes a condition or control indicator 220 and a status indicator 222. The control indicator 220 is located on the front side of the housing 202 above the clickable button actuator 208. The control indicator 220 is configured to alert or inform a user when a selection has been made via the input device 208. That is, the control indicator 220 provides user feedback so that the user knows that a selection has been successfully made. Because the control indicator 220 is positioned above the input device 208, the control indicator can always be seen by the user even when selections are being made via the input device 208 (see
The status indicator 222, on the other hand, is located on the back side of the housing 202 below the modal input device 214. The status indicator 222 is configured to alert the user to a particular status, particularly the life of the battery of the media device 200. The status indicator 222 can, for example, be illuminated green when the battery is fully charged, yellow when the battery is low, and red when the battery is dangerously low. The status indicator 222 can also flash on and off (blink) when the battery is critically low. The status indicator 222 may be an always-on indicator that always presents status information, or it may be an on-call indicator that only presents status information when prompted by the user. In the latter case (which is shown in
Referring to
Referring to
The control input device 208 further includes one or more mechanical switches 238 disposed between the platform 230 and the housing 202 in order to generate input signals based on movements of the platform 230. The mechanical switches 238 are typically placed in locations that correspond to the various button zones. Each of the button zones includes a distinct mechanical switch 238 located underneath the button zone. The mechanical switches 238 include actuators 240 that cause input signals to be generated when depressed. Tilting the platform 230 in the region of the mechanical switch 238 compresses the actuator 240, thereby causing an input signal to be generated. In most cases, the actuators 240 are spring biased so that they extend away from the mechanical switch 238 and bias the platform 230 in the upright position. The mechanical switches 238 may be attached to the housing 202 or to the platform 230. In the illustrated embodiment, the mechanical switches 238 are attached to the backside of the platform 230. As such, the mechanical switches 238 and more particularly the actuators 240 act as legs for supporting the platform 230 in its upright position within the housing 202 (i.e., the actuators rest on the housing or some component mounted to the housing). By way of example, the mechanical switches 238 may correspond to tact switches, such as dome switches packaged for SMT.
As mentioned above, the platform 230 is movably restrained within a cavity 242 provided in the housing 202. In essence, the platform 230 floats in space relative to the housing 202 while still being constrained thereto (the platform is not attached to the housing). As shown, the platform 230 is surrounded by side walls, a top wall and bottom wall of the housing 202. The side walls are configured to substantially prevent movements in the x and y directions as well as rotations about the z axis (e.g., excluding a small gap that allows a slight amount of play in order to prevent the platform 230 from binding with the housing during the tilting action). The top and bottom walls, however, are configured to allow movement (although limited) in the z direction as well as rotation about the x and y axis in order to provide the tilting action. That is, while the top and bottom walls and may constrain the platform 230 to the cavity 242, they also provide enough room for the platform 230 to tilt in order to depress the actuator 240 of the mechanical switches 238. Furthermore, the spring force provided by the mechanical switches 238 places the top surface of the platform 230 into mating engagement with the bottom surface of the top wall of the housing 202 (e.g., upright position).
During operation, a user simply presses on the top surface of the platform 230 in the location of the desired button zone in order to activate the mechanical switches 238 disposed underneath the platform 230 in the location of the button zones. When activated, the mechanical switches 238 generate input signals that may be used by the media device 200. To activate the mechanical switch 238, a force provided by a finger works against the spring force of the actuator 240 until the mechanical switch 238 is activated. Although the platform 230 essentially floats within the cavity of the housing 202, when the user presses on the desired button zone over one side of the platform 230, the opposite side contacts the top wall (opposite the press) thus causing the platform 230 to pivot about the contact point. In essence, the platform pivots about four different axes.
Furthermore, a button cap 244 is disposed between the cosmetic layer 232 and the top side of the rigid plate 234. A top portion of the button cap 244 is configured to protrude through an opening in the cosmetic layer 232 while a flange portion is retained in a space formed between the cosmetic layer 232 and the rigid plate 234. The top portion of the button cap 244 may be pushed to activate a fifth switch 246 located underneath the button cap 244. The fifth switch 246 may be attached to the housing 202 and pass through openings in the rigid plate 234 and cosmetic layer 232. When assembled, the actuator 248 of the fifth switch 246 forces the button cap 244 into an upright position via a spring element similar to the other switches 238.
It should be noted that the particular implementation described in
The media device 700 also includes one or more user input devices 708 that allow a user of the media device 700 to interact with the media device 700. For example, the user input devices 708 can take a variety of forms, such as buttons, keypads, dials, switches, etc. A data bus 711 can facilitate data transfer between at least the file system 704, the cache 706, the processor 702, and the CODEC 712.
In one embodiment, the media device 700 serves to store a plurality of media assets (e.g., songs, photos, etc.) in the file system 704. When a user desires to have the media device 700 play a particular media asset, the user operates the user input device 708 to select a media player mode. Then, using the user input device 708, the user can play the next available media asset. The processor 702, upon receiving a selection of a particular media item, supplies the media data (e.g., audio file) for the particular media item to a coder/decoder (CODEC) 712. The CODEC 712 then produces analog output signals for a speaker 714. The speaker 714 can be a speaker internal to the media device 700 or external to the media device 700. For example, headphones or earphones that connect to the media device 700 would be considered an external speaker.
Additionally, the media player may be set to a specific media play mode, according to some embodiments of the invention. The mode selection is typically made using the user input device 708, such as a switch or button. Two typical media play modes are a continuous play mode and a shuffle play mode. Generally, in the shuffle play mode, the media player plays through a list of media assets in a random order, while in the continuous play mode, the media player plays through the list of media assets according to a default order. The default order for the list of media assets can, for example, be (i) alphabetically ordered by song name, (ii) ordered by track position on an album, or (iii) ordered by date loaded onto the media player. In one embodiment of the invention, the media play mode is selected using a three-position switch, which allows a user of the media player to select between off, continuous play mode, and shuffle play mode.
The media device 700 also includes a network/bus interface 716 that couples to a data link 718. The data link 718 allows the media device 700 to couple to a host computer. The data link 718 can be provided over a wired connection or a wireless connection. In the case of a wireless connection, the network/bus interface 716 can include a wireless transceiver. In one embodiment, the media device 700 can include a peripheral bus connector coupled to the network/bus interface. Examples of a peripheral bus connector are a USB connector or a FireWire® connector.
It should be noted that
In one embodiment, to facilitate user interaction with the media device 700 (which lacks a display), the user input device 708 can include at least a shuffle switch. The shuffle switch enables a user to shuffle the media assets (e.g., songs) being played by the media device 700. The user input device 708 can also include a control input device that allows a user to signal a request to play, pause, next forward, next back, disable control inputs temporarily, and reshuffle the media assets.
The media information pertains to characteristics or attributes of the media assets. For example, in the case of audio or audiovisual media, the media information can include one or more of: title, album, track, artist, composer and genre. These types of media information are specific to particular media assets. In addition, the media information can pertain to quality characteristics of the media assets. Examples of quality characteristics of media assets can include one or more of: bit rate, sample rate, equalizer setting, volume adjustment, start/stop and total time.
Further, in some embodiments, the management module 806 also interacts with the host computer 802 to transfer data files (i.e., non-media asset files stored on the host computer 802, typically on the host computer's hard drive) to and from media storage 808. Alternately, in some embodiments, data files may be transferred to and from optional data storage 809, which may be physically and/or logically combined with or separate from media storage 808. It is understood that a data file includes any data that is capable of being stored in a file system, which includes all file types. Typical data files include text documents, executable files, and graphics files. Alternately, in some embodiments, the management module 806 does not directly access data files. Rather, the user transfers files back and forth to/from or deletes files from the media player 804 using the file manager 815, on the host computer, where the media player appears, for example, as a disk drive or removable storage medium.
The data storage 809 and/or the media storage 808 can utilize one or more directories (e.g., folders) in the host computer's file system (e.g., on a hard drive, not shown). As is conventional, data stored on the data storage 809 can be assessed by a file manager 815. In addition, in one embodiment, media assets stored in the media storage 808 can also be accessed by the file manager 815. The file manager 815 can be, for example, a file explorer, such as a “Finder” application which is part of Apple Computer's operating system.
Still further, the host computer 802 includes a play module 812. The play module 812 is a software module that can be utilized to play certain media assets stored in media storage 808. In some embodiments, the play module 812 can also be used to play media assets stored outside of media storage 808, such as media assets stored in data storage 820 on the media player 804.
The host computer 802 also includes a communication module 814 that couples to a corresponding communication module 816 within the media player 804. A connection or link 818 removeably couples the communication modules 814 and 816. In one embodiment, the connection or link 818 is a cable that provides a data bus, such as a FIREWIRE® bus or USB bus, which is well known in the art. In another embodiment, the connection or link 818 is a wireless channel or connection through a wireless network. In still another embodiment, the connection or link 818 is a USB connection established by direct coupling of a USB connector on the media player 804 to a USB slot on the host computer 802. In this embodiment, the media player 804 is directly inserted into a USB slot on the host computer 802 without using a cable. Hence, depending on implementation, the communication modules 814 and 816 may communicate in a wired or wireless manner.
The media player 804 also includes media storage 820 that stores media assets within the media player 804. Optionally, media storage 820 can also store data files in data storage 821. The media assets or data files being stored to media asset storage 820 or data storage 821 are typically received over the connection or link 818 from the host computer 802. More particularly, the management module 806 sends all or certain of those media assets or data files residing in media storage 808 or file storage 809 over the connection or link 818 to media storage 820 or file storage 821 within the media player 804. Additionally, the corresponding media information for the media assets that is also delivered to the media player 804 from the host computer 802 can be stored in a media database 822. In this regard, certain media information from the media database 810 within the host computer 802 can be sent to the media database 822 within the media player 804 over the connection or link 818. Still further, playlists identifying certain of the media assets can also be sent by the management module 806 over the connection or link 818 to media storage 820 or the media database 822 within the media player 804.
Furthermore, the media player 804 includes a play module 824 that couples to media storage 820 and the media database 822. The play module 824 is a software module that can be utilized to play certain media assets stored in media storage 820.
Hence, in one embodiment, the media player 804 has limited or no capability to manage media assets or data files on the media player 804. However, the management module 806 within the host computer 802 can indirectly manage the media assets residing on the media player 804. For example, to “add” a media asset to the media player 804, the management module 806 serves to identify the media asset to be added to the media player 804 from media storage 808 and then causes the identified media asset or data to be delivered to the media player 804. As another example, to “delete” a media asset from the media player 804, the management module 806 serves to identify the media asset to be deleted from media storage 808 and then causes the identified media asset to be deleted from the media player 804. As still another example, if changes (i.e., alterations) to characteristics of a media asset were made at the host computer 802 using the management module 806, then such characteristics can also be carried over to the corresponding media asset on the media player 804. In one implementation, the additions, deletions and/or changes occur in a batch-like process during synchronization of the media assets on the media player 804 with the media assets on the host computer 802.
Alternately, in some embodiments, data storage on the media player 804 is designated file storage 821 and is combined with or physically and/or logically separate from media storage 820. As discussed above, in some embodiments, the management module 806 is normally not involved in transferring data between file storage 809 on the host computer 802 and file storage 821 on the media player 804. In these embodiments, the file manager 815 running on the host computer 802 can be used to manage the transfer of data between file storage 809 and file storage 821. For example, when using the file manager 815, the media player 804 appears as a USB drive and data files are accessed as if the media player 804 was a conventional USB drive.
In another embodiment, the media player 804 has limited or no capability to manage playlists on the media player 804. However, the management module 806 within the host computer 802 through management of the playlists residing on the host computer can indirectly manage the playlists residing on the media player 804. In this regard, additions, deletions or changes to playlists can be performed on the host computer 802 and then be carried over to the media player 804 when delivered thereto.
As previously noted, synchronization is a form of media management. The ability to automatically initiate synchronization was also previously discussed above and in the related application noted above. Still further, however, the synchronization between devices can be restricted so as to prevent automatic synchronization when the host computer and media player do not recognize one another.
In one implementation, the host computer can utilize an application resident on the host computer to permit utilization and provide management for playlists. One such application is iTunes®, produced by Apple Computer, Inc. of Cupertino, Calif.
Another embodiment of the invention relates to a portable media device, such as a portable media player, having one or more status indicators. The status indicators can provide useful user feedback, which is particularly useful when the portable device lacks a display screen (display), such as a LCD display. The status indicators can be audio or visual.
Additionally, one embodiment of the invention includes an integral peripheral bus connector 907 and a rechargeable battery (not shown). The rechargeable battery can be charged when the portable media device 900 is connected to a peripheral bus via the peripheral bus connector 907. As noted above, a USB connector or a FireWire® connector are examples of a peripheral bus connector. In some embodiments, a removable cap 909 can be used to protect and/or conceal the peripheral bus connector 907.
In one embodiment of the invention, two LEDs of different colors are used as the media device status indicator 903. In this embodiment, a first color LED is used to give a user visual feedback corresponding to the user operating one or more user controls. A second color is used to give the user visual feedback that the media device 900 is being charged. The first color LED can blink once each time a user operates a first user control (e.g., a volume control) on the user control panel 905. If a second user control (e.g., a play/pause control) on the user control panel 905 is operated, then the first color LED blinks steadily while the selected action continues. According to this embodiment, the second color LED, which emits a different color than the first color LED, blinks steadily while the media device 900 is charging, for example, when the media device 900 is plugged into a peripheral bus capable of supplying power to the media device 900.
In one embodiment of the invention, three LEDs of different colors are used to implement the media device status indicator 929. In this embodiment, each of the three colors of LED is used to give a user visual feedback corresponding to a different battery condition. In order to conserve battery life, in some embodiments, the media device status indicator 929 is activated by a user control (not shown), such that the media device indicator 929 operates for a short period of time (e.g., 5 seconds) after the user operates the user control.
For example, in one embodiment, the first color LED lights up to indicate that a battery that powers the media device 900 is mostly charged. Over time, as the media device 900 is operated, the battery discharges to a first predetermined voltage indicative of a partially charged battery. Accordingly, the first color LED switches off and second color LED lights up to indicate to the user that the battery has partially discharged. As the battery continues to discharge to a second predetermined voltage, the second color LEDs switches off and a third color LED lights up to indicate to the user that the battery is mostly discharged. Finally, when the battery is almost completely discharged, a single LED (of any color) blinks steadily to indicate to the user that the media device 900 is preparing to shut down because the battery level is insufficient to continue operating the media device 900. Thereafter, the media device status indicator ceases to give any indication (i.e., none of the LEDs light up) indicating to the user that the battery is substantially completely discharged and must be recharged before the media device 900 can be used again.
Another aspect of the invention relates to a portable media player with the capability of storing media player status information in persistent memory before powering down. Thereafter, when the portable media player is again powered up, the stored media player status information can be retrieved and utilized. In effect, the portable media player can remember where it was playing media assets when turned off, so that when later turned on it can play the media assets from where it left off.
The media player power-down process 1100 begins with a decision 1101 that determines if a power off request has been received. The power off request can originate from a user action or a system command. An example of a user action is operating an off switch. Alternatively, if the power off request comes from a system command, the command may be the result of a user-set preference, such as after a predetermined period of inactivity or a low battery condition.
Once a power off request has been received, the media player power off process 1100 determines 1102 media player status information from the media player. For example, the media player status information can be determined by a processor operating the media player, such as the processor 702 shown in
Next, media player status information is stored 1103 in persistent memory of the media player. For example, the media player status information can be stored in memory of the media player, such as FLASH memory or other non-volatile memory. Subsequently, the media player is powered off 1105. The media player power-down process 1100 is then complete and ends.
The media player power-on process 1200 begins with a decision 1201, which determines if a power on request has been made. The power on request can originate from a user action or a system command. An example of a user action is operation of an on switch to issue a power on request. If the power on request comes from a system command, the command can, for example, be the result of connection of the media player to a host computer.
Once the decision 1201 determines that the power on request has been made, media player status information is retrieved 1203 from persistent memory. For example, the media player status information can be retrieved 1203 from memory of the media player, such as FLASH memory or other non-volatile memory. According to one embodiment of the invention, the media player status information retrieved 1203 can be considered state information for the media player. The state information characterizes a state of the media player so that the media player can be returned to the same (or substantially the same) state it had when it was previously powered off. The media player status information includes, but is not limited to, one or more of a media asset pointer, a media asset position (e.g., elapsed time), a media player volume, a media player pause status, and a media asset playlist. In another embodiment, the media player status information includes status indicators. For example, the status indicators can be any one or more of the media player status information status indicators shown in Table 1 above. Typically, the retrieved media player status information was previously stored when the media player was previously powered off, but may also be default values or values previously set by a user. For instance, the media player volume indicator may automatically be set at a default value to prevent an unexpectedly loud volume level in a user's headphones when the media player starts. Further, in some embodiments, a media asset playlist validity indicator can also be retrieved 1203 as part of the media player status information.
After the media player status information has been retrieved 1203, the media player is configured 1205 according to the retrieved media player status information. In one embodiment, the media player is configured 1205 such that it is the same or substantially the same state as it was when the media player status information was stored in persistent memory. Finally, the media player presents 1207 one or more media assets according to the media player status information. Thereafter, the media player power-on process 1200 ends.
Still another aspect of the invention relates to a method for traversing a media asset playlist. The method includes the presentation of one or more media assets in one or more media asset playlists, including at least a media asset continuous playlist and a media asset shuffle playlist. Further, the method describes the circumstances under which a new media asset shuffle playlist is created. These methods are well suited for performance on portable media devices where resources or power is often limited.
The media asset shuffle playlist traversal process 1300 begins with a decision 1301 that determines if a presentation request has been received. The presentation request can be a user request or a system request. As noted above, a presentation operation is used by a media player to present (e.g., play) a media asset. Besides presenting a media asset, other common operations supported by a media player include fast forwarding or rewinding through a media asset, and skipping forward to a next media asset or backward to a previous media asset. If a presentation request has not been received, the media asset shuffle playlist traversal process 1300 waits until a presentation request is received. On the other hand, if a presentation request has been received, a decision 1303 determines if a shuffle playlist exists. If the decision 1303 determines that there is no existing shuffle playlist, a shuffle playlist is created 1311. Following the creation 1311 of the shuffle playlist, a media asset from the shuffle playlist is retrieved 1313. The retrieved media asset is typically the first media asset of the shuffle playlist, if the shuffle playlist has been newly created. Next, the retrieved media asset is presented 1315 (e.g., played) on the media asset player. After the retrieved media asset from the shuffle playlist is presented 1315, the media asset shuffle playlist traversal process 1300 returns to the decision 1303 and subsequent blocks. Note that, according to some embodiments of this invention, “presenting” a media asset means using the media device to output audio. However, presenting can also include at least operations commonly associated with a typical media player, including fast forwarding or rewinding through a media asset, and skipping forward to a next asset or backward to a previous media asset.
Alternatively, when the decision 1303 determines that a shuffle playlist does exist, the shuffle playlist is obtained 1307. For example, the shuffle playlist can be obtained 1307 can by retrieving a pointer to the shuffle playlist or a current media asset in the shuffle playlist. Next, decision 1309 determines if the obtained shuffle playlist is valid. In one embodiment, the validity of a shuffle playlist can be indicated by a flag or other indicator stored in the media player. If decision 1309 determines that the shuffle playlist is not valid, the media asset shuffle playlist traversal process 1300 creates 1311 a shuffle playlist and then continues to block 1313 and subsequent blocks as discussed above. On the other hand, if decision 1309 determines that the shuffle playlist is valid, the media asset shuffle traversal process 1300 continues directly to block 1313 and subsequent blocks.
Although the media asset shuffle playlist traversal process 1300 applies to a shuffle playlist, it should be understood that the media asset shuffle playlist traversal process 1300 can also be applied to other types of playlist. Additionally, in some embodiments of the invention, the status of the media asset shuffle playlist is stored upon a power-down process such as, for example, the media player power-down process 1100 of
The media asset list traversal process 1400 begins with decision 1401, which determines whether a media asset shuffle playlist is valid. For example, the decision 1401 can occur when a media asset shuffle playlist is accessed, for instance during operation 1307 of
Following the retrieval 1407 of the first or next media asset on the media asset shuffle playlist, the retrieved media asset is presented 1409 (e.g., played). Next, a decision 1411 determines if the media player has been switched to a continuous mode, where the continuous mode is associated with a media asset continuous playlist. For example, the media player can be switched to a continuous mode by using an input device, such as a switch. Typically, according to some embodiments, to activate the continuous mode, a user manually switches a switch of the media player to continuous mode setting, possibly because the user no longer wishes to listen to the currently selected shuffle playlist. A media asset continuous playlist according to one embodiment of the invention is described below in reference to
If decision 1411 determines that the media player has been switched to a continuous mode, then the media asset shuffle list creation process 1400 continues to other processing associated with traversal of a media asset continuous playlist. Otherwise, decision 1413 determines if a user of the media player makes a request that the media player create 1403 a new media asset shuffle playlist. The user request is, according to some embodiments of the invention, initiated by operating a media player control. A dedicated media player control can be used or an existing media player control can be overloaded so as to function to make the new media asset shuffle playlist request. In some embodiments of the invention, a media player control, for example the pause/play control 1026 of
If the decision 1413 determines that the user has made a request to create a new media asset shuffle playlist, the media asset playlist validity indicator is set 1417 to ‘invalid’. On the other hand, if the user does not request the creation of a new media asset shuffle playlist, then decision 1413 directs the media asset shuffle playlist creation process 1400 to decision 1415 and subsequent blocks. The decision 1415 determines if the end of the shuffle playlist has been reached, whereupon the media asset playlist validity indicator is set 1417 to ‘invalid’. Alternately, if the end of the shuffle playlist has not been reached, the media asset list traversal process 1400 returns to block 1407 and subsequent blocks. Next, regardless of how the block 1417 is reached, following the block 1417 the media asset shuffle list creation process 1400 returns to block 1401 and subsequent blocks.
More particularly, when decision 1411 determines that the media player has been switched to continuous mode, decision 1455 determines if a media player has reached a transition between media assets (e.g., the end of a song). If so, the media asset playlist validity indicator is set 1457 to ‘invalid’. Alternatively, if a transition is not reached while the media player is playing in continuous mode, then the media asset list traversal process 1400 continues to decision 1463 and subsequent blocks. At decision 1463, a determination is made whether the media player has been switched to continuous mode. If the media player has been switched to continuous mode, the media asset list traversal process 1450 returns to decision 1402 of the media asset shuffle playlist process 1400. On the other hand, if the media player has not been switched to shuffle mode, decision 1463 directs the media asset list traversal process 1450 to decision 1455 and subsequent blocks. Note that, according to this embodiment, if the user switches the media player back to shuffle mode before a media asset transition is reached, the media asset playlist validity indicator is not set to ‘invalid’.
Next, the first or next media asset on the media asset continuous playlist is retrieved 1459 and presented 1461. According to one embodiment of the invention, if the media player has just been switched to continuous mode from shuffle mode, for example before decision 1411 of
According to some embodiments of the invention, if the end of the media asset continuous list is reached, the media asset list traversal process 1400 starts over at the first media asset on the media asset continuous list. However, in other embodiments, an optional decision 1465 is added. If decision 1465 determines that the end of the media asset continuous list has been reached, then the media asset list traversal process 1400 ends. Otherwise, according to these embodiments, the media asset list traversal process 1400 continues to decision 1455 and subsequent blocks.
In the embodiment shown in
As noted above, the media asset pointer 1513 points to the currently selected media asset data entry 1503 (designated CPL_x in
One example of presenting a media asset 1507 using the media asset playlist arrangement 1500 involves a media player accessing the particular playlist media asset data entry 1503 that the media asset pointer 1513 is currently pointing to. Next, the pointer 1505 associated with the continuous playlist media asset data entry 1503 is followed to locate the media asset 1507.
As discussed above with reference to
Further, the media asset pointer 1513 points to the currently selected media asset data entry 1553 (designated SPL_y in
One example of presenting a media asset 1507 using the media asset playlist arrangement 1550 involves a media player accessing the particular shuffle playlist media asset data entry 1553 that the media asset pointer 1513 is currently pointing to. Next, the pointer 1555 associated with the shuffle playlist media asset data entry 1553 is followed to the continuous playlist media asset data entry 1503. Subsequently, the pointer 1505 associated with the continuous playlist media asset data entry 1503 is followed to the media asset 1507, which is presented according to the capabilities of the media player.
Note further, in a typical media asset shuffle playlist creation process such as, for example, the media asset shuffle playlist creation process 1400 of
Table 2 shows a list of state variables and associated abbreviations for each. Values for each state variable are shown on
Further, at each time Tn on the timeline, a media asset shuffle playlist 1603 is shown. The media asset shuffle playlist 1603 can have the features of the media asset shuffle playlist 1551 of
As noted above in reference to
The timeline begins at T0, with an initial media player state being ‘off’. At T0, all state variables are stored in persistent memory.
At T1, the media player is powered on and switched to shuffle mode. Upon loading the state variables in the snapshot 1601 shown for T1, the media player begins to traverse the shuffle playlist shown at T1. Specifically the media player starts at a point 30 seconds into media asset MA_d. This indicates that, at some TP before T0, the media player was powered off after playing 30 seconds of the media asset MA_d, and that the state variables indicating the media player status at TP were stored before the media player was powered off.
At T2, 30 seconds after T1, a user sets the media player to continuous mode. The value of the playlist pointer (pp) is changed to cont_PL, indicating that the continuous playlist 1609 is now selected. However, the media player continues to present (play) the media asset 1607 that the media asset pointer 1605 was pointing at (MA_d) on the shuffle playlist 1603 until the end of the media asset 1607 is reached.
At time T3, a transition is reached at the end of media asset MA_d. Hence, the current media shuffle playlist becomes invalid and the playlist validity indicator is set to ‘invalid’. Further, since the media player was set to continuous mode at T2, MA_e (the next media asset 1607 on the continuous playlist 1609), is presented, rather than MA_b, which was the next media asset 1607 on the now-invalid shuffle playlist.
Note that, if the media player remains in continuous mode, the continuous playlist is traversed sequentially (MA_f, MA_g, etc.).
One minute into playing of the media asset MA_e, at time T4, the user of the media player switches the media player back to shuffle mode. Accordingly, the playlist pointer is set back to shuffle_PL.
At time T5, a transition is reached at the end of media asset MA_e. Since the media player is in shuffle mode, the media player attempts to traverse the shuffle playlist. However, the playlist validity indicator was set to ‘invalid’ at T3, so a new shuffle playlist 1611 (shuffle_PL′) is created. Thus, the new shuffle playlist 1611 is created and the media asset pointer is moved to MA_c, which is a first media asset 1607 on the new shuffle playlist 1609.
Timeline 1600 continues on
At time T9, the user requests a new shuffle playlist. The new shuffle playlist request causes the shuffle playlist 1611 to be invalidated, as indicated by setting the validity indicator to ‘invalid’. When the next transition (between MA_i and MA_x) is reached at time T10, a new shuffle playlist 1613 (shuffle_PL″) is created and the media asset pointer 1605 is set point to MA_d, which is the first media asset 1607 on the new shuffle playlist 1613.
Finally, at time T11, the user powers off the media player. Before the media player powers off, it saves the current state variables as media asset status indicators in persistent memory (see
Examples of ornamental designs for a media device, such as those illustrated in
Although the media items (or media assets) of emphasis in several of the above embodiments were audio items (e.g., audio files or songs), the media items are not limited to audio items. For example, the media items can alternatively pertain to videos (e.g., movies) or images (e.g., photos).
The various aspects, features, embodiments or implementations of the invention described above can be used alone or in various combinations.
The methods of this invention can be implemented by software, hardware or a combination of hardware and software. The invention can also be embodied as computer readable code on a computer readable medium. The computer readable medium is any data storage device that can store data which can thereafter be read by a computer system, including both transfer and non-transfer devices as defined above. Examples of the computer readable medium include read-only memory, random-access memory, CD-ROMs, Flash memory cards, DVDs, magnetic tape, optical data storage devices, and carrier waves. The computer readable medium can also be distributed over network-coupled computer systems so that the computer readable code is stored and executed in a distributed fashion.
The many features and advantages of the present invention are apparent from the written description and, thus, it is intended by the appended claims to cover all such features and advantages of the invention. Further, since numerous modifications and changes will readily occur to those skilled in the art, the invention should not be limited to the exact construction and operation as illustrated and described. Hence, all suitable modifications and equivalents may be resorted to as falling within the scope of the invention.
This application is a Continuation of, and claims the benefit of priority under 35 U.S.C. §120 to, U.S. application Ser. No. 11/212,555, filed on Aug. 24, 2005, now U.S. Pat. No. 7,536,565, and entitled “TECHNIQUES FOR IMPROVED PLAYLIST PROCESSING ON MEDIA DEVICES” which is hereby incorporated herein by reference in its entirety and for all purposes. U.S. application Ser. No. 11/212,555 claimed priority to U.S. Provisional Patent Application No. 60/642,276, filed Jan. 7, 2005, and entitled “PORTABLE MEDIA DEVICE AND IMPROVED PLAYLIST PROCESSING ON MEDIA DEVICES”, which is hereby incorporated herein by reference in its entirety and for all purposes. This application is also related to: (i) U.S. patent application Ser. No. 11/212,313, filed Aug. 24, 2005, now U.S. Pat. No. 7,593,782, and entitled “HIGHLY PORTABLE MEDIA DEVICE,” which is hereby incorporated herein by reference; (ii) U.S. patent application Ser. No. 11/031,547, filed Jan. 7, 2005, now U.S. Pat. No. 7,525,216, entitled “PORTABLE POWER SOURCE TO PROVIDE POWER TO AN ELECTRONIC DEVICE VIA AN INTERFACE,” which is hereby incorporated herein by reference in its entirety and for all purposes; (iii) U.S. patent application Ser. No. 11/051,499, filed Feb. 3, 2005, entitled “ACCESSORY AUTHENTICATION FOR ELECTRONIC DEVICES,” which is hereby incorporated herein by reference in its entirety and for all purposes; (iv) U.S. patent application Ser. No. 11/031,288, filed Jan. 7, 2005, now U.S. Pat. No. 7,581,119, entitled “METHOD AND SYSTEM FOR DISCOVERING A POWER SOURCE ON A PERIPHERAL BUS,” which is hereby incorporated herein by reference in its entirety and for all purposes; (v) U.S. patent application Ser. No. 10/278,752, filed Oct. 22, 2002, now U.S. Pat. No. 6,995,963, issued Feb. 7, 2006, entitled “METHODS AND APPARATUS FOR CHARGING A BATTERY IN A PERIPHERAL DEVICE,” which is hereby incorporated herein by reference in its entirety and for all purposes; and (vi) U.S. patent application Ser. No. 10/125,893, filed Mar. 18, 2002, entitled “POWER ADAPTERS FOR POWERING AND/OR CHARGING PERIPHERAL DEVICES,” which is hereby incorporated herein by reference in its entirety and for all purposes.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4090216 | Constable | May 1978 | A |
| 4386345 | Narveson et al. | May 1983 | A |
| 4451849 | Fuhrer | May 1984 | A |
| 4589022 | Prince et al. | May 1986 | A |
| 4908523 | Snowden et al. | Mar 1990 | A |
| 4928307 | Lynn | May 1990 | A |
| 4951171 | Tran et al. | Aug 1990 | A |
| 5185906 | Brooks | Feb 1993 | A |
| 5293494 | Saito et al. | Mar 1994 | A |
| 5379057 | Clough | Jan 1995 | A |
| 5406305 | Shimomura et al. | Apr 1995 | A |
| 5559945 | Beaudet et al. | Sep 1996 | A |
| 5566337 | Szymanski et al. | Oct 1996 | A |
| 5583993 | Foster et al. | Dec 1996 | A |
| 5608698 | Yamanoi et al. | Mar 1997 | A |
| 5616876 | Cluts | Apr 1997 | A |
| 5617386 | Choi | Apr 1997 | A |
| 5670985 | Cappels, Sr. et al. | Sep 1997 | A |
| 5675362 | Clough | Oct 1997 | A |
| 5684513 | Decker | Nov 1997 | A |
| 5710922 | Alley et al. | Jan 1998 | A |
| 5712949 | Kato et al. | Jan 1998 | A |
| 5717422 | Fergason | Feb 1998 | A |
| 5721949 | Smith et al. | Feb 1998 | A |
| 5726672 | Hernandez et al. | Mar 1998 | A |
| 5739451 | Winksy et al. | Apr 1998 | A |
| 5740143 | Suetomi | Apr 1998 | A |
| 5760588 | Bailey | Jun 1998 | A |
| 5778374 | Dang et al. | Jul 1998 | A |
| 5803786 | McCormick | Sep 1998 | A |
| 5815225 | Nelson | Sep 1998 | A |
| 5822288 | Shinada | Oct 1998 | A |
| 5835721 | Donahue et al. | Nov 1998 | A |
| 5835732 | Kikinis et al. | Nov 1998 | A |
| 5838969 | Jacklin et al. | Nov 1998 | A |
| 5864868 | Contois | Jan 1999 | A |
| 5867163 | Kurtenbach | Feb 1999 | A |
| 5870710 | Ozawa et al. | Feb 1999 | A |
| 5918303 | Yamaura et al. | Jun 1999 | A |
| 5920728 | Hallowell et al. | Jul 1999 | A |
| 5923757 | Hocker et al. | Jul 1999 | A |
| 5952992 | Helms | Sep 1999 | A |
| 6006274 | Hawkins et al. | Dec 1999 | A |
| 6009237 | Hirabayashi et al. | Dec 1999 | A |
| 6011585 | Anderson | Jan 2000 | A |
| 6018705 | Gaudet et al. | Jan 2000 | A |
| 6041023 | Lakhansingh | Mar 2000 | A |
| 6052654 | Gaudet et al. | Apr 2000 | A |
| 6108426 | Stortz | Aug 2000 | A |
| 6122340 | Darley et al. | Sep 2000 | A |
| 6158019 | Squibb | Dec 2000 | A |
| 6161944 | Leman | Dec 2000 | A |
| 6172948 | Keller et al. | Jan 2001 | B1 |
| 6179432 | Zhang et al. | Jan 2001 | B1 |
| 6185163 | Bickford et al. | Feb 2001 | B1 |
| 6191939 | Burnett | Feb 2001 | B1 |
| 6208044 | Viswanadham et al. | Mar 2001 | B1 |
| 6216131 | Liu et al. | Apr 2001 | B1 |
| 6217183 | Shipman | Apr 2001 | B1 |
| 6248946 | Dwek | Jun 2001 | B1 |
| 6295541 | Bodnar et al. | Sep 2001 | B1 |
| 6297795 | Kato et al. | Oct 2001 | B1 |
| 6298314 | Blackadar et al. | Oct 2001 | B1 |
| 6332175 | Birrell et al. | Dec 2001 | B1 |
| 6336365 | Blackadar et al. | Jan 2002 | B1 |
| 6336727 | Kim | Jan 2002 | B1 |
| 6341316 | Kloba et al. | Jan 2002 | B1 |
| 6357147 | Darley et al. | Mar 2002 | B1 |
| 6377530 | Burrows | Apr 2002 | B1 |
| 6452610 | Reinhardt et al. | Sep 2002 | B1 |
| 6467924 | Shipman | Oct 2002 | B2 |
| 6493652 | Ohlenbusch et al. | Dec 2002 | B1 |
| 6536139 | Darley et al. | Mar 2003 | B2 |
| 6549497 | Miyamoto et al. | Apr 2003 | B2 |
| 6560903 | Darley | May 2003 | B1 |
| 6587403 | Keller et al. | Jul 2003 | B1 |
| 6587404 | Keller et al. | Jul 2003 | B1 |
| 6605038 | Teller et al. | Aug 2003 | B1 |
| 6606281 | Cowgill et al. | Aug 2003 | B2 |
| 6611607 | Davis et al. | Aug 2003 | B1 |
| 6611789 | Darley | Aug 2003 | B1 |
| 6617963 | Watters et al. | Sep 2003 | B1 |
| 6621768 | Keller et al. | Sep 2003 | B1 |
| 6623427 | Mandigo | Sep 2003 | B2 |
| 6631101 | Chan et al. | Oct 2003 | B1 |
| 6693612 | Matsumoto et al. | Feb 2004 | B1 |
| 6731312 | Robbin | May 2004 | B2 |
| 6760536 | Amir et al. | Jul 2004 | B1 |
| 6762741 | Weindorf | Jul 2004 | B2 |
| 6781611 | Richard | Aug 2004 | B1 |
| 6794566 | Pachet | Sep 2004 | B2 |
| 6799226 | Robbin et al. | Sep 2004 | B1 |
| 6801964 | Mahdavi | Oct 2004 | B1 |
| 6832373 | O'Neill | Dec 2004 | B2 |
| 6844511 | Hsu et al. | Jan 2005 | B1 |
| 6870529 | Davis | Mar 2005 | B1 |
| 6871063 | Schiffer | Mar 2005 | B1 |
| 6876947 | Darley et al. | Apr 2005 | B1 |
| 6882955 | Ohlenbusch et al. | Apr 2005 | B1 |
| 6886749 | Chiba et al. | May 2005 | B2 |
| 6898550 | Blackadar et al. | May 2005 | B1 |
| 6911971 | Suzuki et al. | Jun 2005 | B2 |
| 6918677 | Shipman | Jul 2005 | B2 |
| 6931377 | Seya | Aug 2005 | B1 |
| 6934812 | Robbin et al. | Aug 2005 | B1 |
| 6950087 | Knox et al. | Sep 2005 | B2 |
| 7010365 | Maymudes | Mar 2006 | B2 |
| 7028096 | Lee | Apr 2006 | B1 |
| 7046230 | Zadesky | May 2006 | B2 |
| 7062225 | White | Jun 2006 | B2 |
| 7076561 | Rosenberg et al. | Jul 2006 | B1 |
| 7084856 | Huppi | Aug 2006 | B2 |
| 7084921 | Ogawa | Aug 2006 | B1 |
| 7092946 | Bodnar | Aug 2006 | B2 |
| 7124125 | Cook et al. | Oct 2006 | B2 |
| 7131059 | Obrador | Oct 2006 | B2 |
| 7143241 | Hull | Nov 2006 | B2 |
| 7146437 | Robbin et al. | Dec 2006 | B2 |
| 7171331 | Vock et al. | Jan 2007 | B2 |
| 7191244 | Jennings et al. | Mar 2007 | B2 |
| 7213228 | Putterman et al. | May 2007 | B2 |
| 7234026 | Robbin et al. | Jun 2007 | B2 |
| 7277928 | Lennon | Oct 2007 | B2 |
| 7301857 | Shah et al. | Nov 2007 | B2 |
| 7356679 | Le et al. | Apr 2008 | B1 |
| 7508535 | Hart et al. | Mar 2009 | B2 |
| 20010013983 | Izawa et al. | Aug 2001 | A1 |
| 20010029178 | Criss et al. | Oct 2001 | A1 |
| 20010037367 | Iyer | Nov 2001 | A1 |
| 20010041021 | Boyle et al. | Nov 2001 | A1 |
| 20010042107 | Palm | Nov 2001 | A1 |
| 20020002413 | Tokue | Jan 2002 | A1 |
| 20020013784 | Swanson | Jan 2002 | A1 |
| 20020028683 | Banatre et al. | Mar 2002 | A1 |
| 20020045961 | Gibbs et al. | Apr 2002 | A1 |
| 20020046315 | Miller et al. | Apr 2002 | A1 |
| 20020055934 | Lipscomb et al. | May 2002 | A1 |
| 20020059440 | Hudson et al. | May 2002 | A1 |
| 20020059499 | Hudson | May 2002 | A1 |
| 20020090912 | Cannon et al. | Jul 2002 | A1 |
| 20020116082 | Gudorf | Aug 2002 | A1 |
| 20020116517 | Hudson et al. | Aug 2002 | A1 |
| 20020122031 | Maglio et al. | Sep 2002 | A1 |
| 20020123359 | Wei et al. | Sep 2002 | A1 |
| 20020152045 | Dowling et al. | Oct 2002 | A1 |
| 20020156833 | Maurya et al. | Oct 2002 | A1 |
| 20020161865 | Nguyen | Oct 2002 | A1 |
| 20020173273 | Spurgat et al. | Nov 2002 | A1 |
| 20020189426 | Hirade et al. | Dec 2002 | A1 |
| 20020189429 | Qian et al. | Dec 2002 | A1 |
| 20020199043 | Yin | Dec 2002 | A1 |
| 20030002688 | Kanevsky et al. | Jan 2003 | A1 |
| 20030007001 | Zimmerman | Jan 2003 | A1 |
| 20030018799 | Eyal | Jan 2003 | A1 |
| 20030037254 | Fischer et al. | Feb 2003 | A1 |
| 20030046434 | Flanagin et al. | Mar 2003 | A1 |
| 20030050092 | Yun | Mar 2003 | A1 |
| 20030074457 | Kluth | Apr 2003 | A1 |
| 20030076301 | Tsuk et al. | Apr 2003 | A1 |
| 20030076306 | Zadesky | Apr 2003 | A1 |
| 20030079038 | Robbin et al. | Apr 2003 | A1 |
| 20030095096 | Robbin et al. | May 2003 | A1 |
| 20030097379 | Ireton | May 2003 | A1 |
| 20030104835 | Douhet | Jun 2003 | A1 |
| 20030127307 | Liu et al. | Jul 2003 | A1 |
| 20030128192 | van Os | Jul 2003 | A1 |
| 20030133694 | Yeo | Jul 2003 | A1 |
| 20030153213 | Siddiqui et al. | Aug 2003 | A1 |
| 20030156503 | Schilling et al. | Aug 2003 | A1 |
| 20030167318 | Robbin et al. | Sep 2003 | A1 |
| 20030176935 | Lian et al. | Sep 2003 | A1 |
| 20030182100 | Plastina et al. | Sep 2003 | A1 |
| 20030221541 | Platt | Dec 2003 | A1 |
| 20030229490 | Etter | Dec 2003 | A1 |
| 20030236695 | Litwin, Jr. | Dec 2003 | A1 |
| 20040001395 | Keller et al. | Jan 2004 | A1 |
| 20040001396 | Keller et al. | Jan 2004 | A1 |
| 20040012556 | Yong et al. | Jan 2004 | A1 |
| 20040055446 | Robbin et al. | Mar 2004 | A1 |
| 20040066363 | Yamano et al. | Apr 2004 | A1 |
| 20040069122 | Wilson | Apr 2004 | A1 |
| 20040076086 | Keller | Apr 2004 | A1 |
| 20040086120 | Akins, III et al. | May 2004 | A1 |
| 20040094018 | Ueshima et al. | May 2004 | A1 |
| 20040103411 | Thayer | May 2004 | A1 |
| 20040125522 | Chiu et al. | Jul 2004 | A1 |
| 20040165302 | Lu | Aug 2004 | A1 |
| 20040177063 | Weber et al. | Sep 2004 | A1 |
| 20040198436 | Alden | Oct 2004 | A1 |
| 20040210628 | Inkinen et al. | Oct 2004 | A1 |
| 20040216108 | Robbin | Oct 2004 | A1 |
| 20040224638 | Fadell et al. | Nov 2004 | A1 |
| 20040242224 | Janik et al. | Dec 2004 | A1 |
| 20040246275 | Yoshihara et al. | Dec 2004 | A1 |
| 20040255135 | Kitaya et al. | Dec 2004 | A1 |
| 20040267825 | Novak et al. | Dec 2004 | A1 |
| 20050015254 | Beaman | Jan 2005 | A1 |
| 20050053365 | Adams et al. | Mar 2005 | A1 |
| 20050060240 | Popofsky | Mar 2005 | A1 |
| 20050060542 | Risan et al. | Mar 2005 | A1 |
| 20050108754 | Carhart et al. | May 2005 | A1 |
| 20050111820 | Matsumi et al. | May 2005 | A1 |
| 20050122315 | Chalk et al. | Jun 2005 | A1 |
| 20050123886 | Hua et al. | Jun 2005 | A1 |
| 20050146534 | Fong et al. | Jul 2005 | A1 |
| 20050149213 | Guzak et al. | Jul 2005 | A1 |
| 20050152294 | Yu et al. | Jul 2005 | A1 |
| 20050156047 | Chiba et al. | Jul 2005 | A1 |
| 20050160270 | Goldberg et al. | Jul 2005 | A1 |
| 20050166153 | Eytchison et al. | Jul 2005 | A1 |
| 20050216855 | Kopra et al. | Sep 2005 | A1 |
| 20050218303 | Poplin | Oct 2005 | A1 |
| 20050234983 | Plastina et al. | Oct 2005 | A1 |
| 20050245839 | Stivoric et al. | Nov 2005 | A1 |
| 20050246324 | Paalasmaa et al. | Nov 2005 | A1 |
| 20050248555 | Feng et al. | Nov 2005 | A1 |
| 20050257169 | Tu | Nov 2005 | A1 |
| 20050259064 | Sugino et al. | Nov 2005 | A1 |
| 20050259524 | Yeh | Nov 2005 | A1 |
| 20050270276 | Sugimoto et al. | Dec 2005 | A1 |
| 20060013414 | Shih | Jan 2006 | A1 |
| 20060025068 | Regan et al. | Feb 2006 | A1 |
| 20060026424 | Eto | Feb 2006 | A1 |
| 20060061563 | Fleck | Mar 2006 | A1 |
| 20060068760 | Hameed et al. | Mar 2006 | A1 |
| 20060071899 | Chang et al. | Apr 2006 | A1 |
| 20060088228 | Marriott et al. | Apr 2006 | A1 |
| 20060092122 | Yoshihara et al. | May 2006 | A1 |
| 20060094409 | Inselberg | May 2006 | A1 |
| 20060095502 | Lewis et al. | May 2006 | A1 |
| 20060098320 | Koga et al. | May 2006 | A1 |
| 20060135883 | Jonsson et al. | Jun 2006 | A1 |
| 20060145053 | Stevenson et al. | Jul 2006 | A1 |
| 20060152382 | Hiltunen | Jul 2006 | A1 |
| 20060155914 | Jobs et al. | Jul 2006 | A1 |
| 20060170535 | Watters et al. | Aug 2006 | A1 |
| 20060173974 | Tang | Aug 2006 | A1 |
| 20060190577 | Yamada | Aug 2006 | A1 |
| 20060190980 | Kikkoji et al. | Aug 2006 | A1 |
| 20060221057 | Fux et al. | Oct 2006 | A1 |
| 20060221788 | Lindahl et al. | Oct 2006 | A1 |
| 20060259758 | Deng et al. | Nov 2006 | A1 |
| 20060265503 | Jones et al. | Nov 2006 | A1 |
| 20060272483 | Honeywell | Dec 2006 | A1 |
| 20060277336 | Lu et al. | Dec 2006 | A1 |
| 20070014536 | Hellman | Jan 2007 | A1 |
| 20070028009 | Robbin et al. | Feb 2007 | A1 |
| 20070061759 | Klein, Jr. | Mar 2007 | A1 |
| 20070089057 | Kindig | Apr 2007 | A1 |
| 20070106660 | Stern et al. | May 2007 | A1 |
| 20070124679 | Jeong et al. | May 2007 | A1 |
| 20070129062 | Pantalone et al. | Jun 2007 | A1 |
| 20070135225 | Nieminen et al. | Jun 2007 | A1 |
| 20070248311 | Wice et al. | Oct 2007 | A1 |
| 20070255163 | Prineppi | Nov 2007 | A1 |
| 20080134287 | Gudorf et al. | Jun 2008 | A1 |
| 20100077338 | Matthews et al. | Mar 2010 | A1 |
| Number | Date | Country |
|---|---|---|
| 43 34 773 | Apr 1994 | DE |
| 44 45 023 | Jun 1996 | DE |
| 0 127 139 | May 1984 | EP |
| 0578604 | Jan 1994 | EP |
| 0 757 437 | Feb 1997 | EP |
| 0 813 138 | Dec 1997 | EP |
| 0 863 469 | Sep 1998 | EP |
| 0 917 077 | May 1999 | EP |
| 0 982 732 | Mar 2000 | EP |
| 1 028 425 | Aug 2000 | EP |
| 1028426 | Aug 2000 | EP |
| 1 076 302 | Feb 2001 | EP |
| 1 213 643 | Jun 2002 | EP |
| 1 289 197 | Mar 2003 | EP |
| 1 503 363 | Feb 2005 | EP |
| 1536612 | Jun 2005 | EP |
| 1 566 743 | Aug 2005 | EP |
| 1566948 | Aug 2005 | EP |
| 1 372 133 | Dec 2005 | EP |
| 1 686 496 | Aug 2006 | EP |
| 2 370 208 | Jun 2002 | GB |
| 2384399 | Jul 2003 | GB |
| 2399639 | May 2005 | GB |
| 59-023610 | Feb 1984 | JP |
| 03-228490 | Oct 1991 | JP |
| 04-243386 | Aug 1992 | JP |
| 6-96520 | Apr 1994 | JP |
| 8-235774 | Sep 1996 | JP |
| 9-50676 | Feb 1997 | JP |
| 9-259532 | Oct 1997 | JP |
| 2000-90651 | Mar 2000 | JP |
| 2000-224099 | Aug 2000 | JP |
| 2000-285643 | Oct 2000 | JP |
| 2000-299834 | Oct 2000 | JP |
| 2000-311352 | Nov 2000 | JP |
| 2000-339864 | Dec 2000 | JP |
| 2001-236286 | Aug 2001 | JP |
| 2001-312338 | Nov 2001 | JP |
| 2002-076977 | Mar 2002 | JP |
| 2002-175467 | Jun 2002 | JP |
| 2003-188792 | Jul 2003 | JP |
| 2003-259333 | Sep 2003 | JP |
| 2003-319365 | Nov 2003 | JP |
| 2004-021720 | Jan 2004 | JP |
| 2004-219731 | Aug 2004 | JP |
| 2004-220420 | Aug 2004 | JP |
| 20010076508 | Aug 2001 | KR |
| WO 9516950 | Jun 1995 | WO |
| 9817032 | Apr 1998 | WO |
| WO 9928813 | Jun 1999 | WO |
| WO 0022820 | Apr 2000 | WO |
| WO 0133569 | May 2001 | WO |
| WO 0165413 | Sep 2001 | WO |
| WO 0167753 | Sep 2001 | WO |
| WO 0225610 | Mar 2002 | WO |
| WO 03023786 | Mar 2003 | WO |
| WO 03036457 | May 2003 | WO |
| WO 03067202 | Aug 2003 | WO |
| 2004061850 | Jul 2004 | WO |
| WO 2004055637 | Jul 2004 | WO |
| WO2004084413 | Sep 2004 | WO |
| WO 2004104815 | Dec 2004 | WO |
| WO 2005031737 | Apr 2005 | WO |
| 2005048644 | May 2005 | WO |
| WO 2005008505 | Jul 2005 | WO |
| 2005109781 | Nov 2005 | WO |
| WO 2006040737 | Apr 2006 | WO |
| 2006071364 | Jun 2006 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 20090182445 A1 | Jul 2009 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60642276 | Jan 2005 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 11212555 | Aug 2005 | US |
| Child | 12406793 | US |
