Method and system for allowing a media player to determine if it supports the capabilities of an accessory

Information

  • Patent Grant
  • 8370555
  • Patent Number
    8,370,555
  • Date Filed
    Tuesday, December 20, 2011
    13 years ago
  • Date Issued
    Tuesday, February 5, 2013
    12 years ago
Abstract
A method and system for allowing a media player to determine if it supports the capabilities of an accessory are disclosed. The method and system comprise requesting information about the capabilities of the accessory by the media player and providing information about the capabilities of the accessory by the accessory to the media player. The method and system further include utilizing the information to determine if the capabilities of the accessory are supported by the media player. Accordingly, a method and system in accordance with the present invention provides a system that allows a media player to obtain information from an accessory about the accessory's capability. A media player can then utilize this information to allow for the maximum functionality of the accessory when connected to the media player.
Description
FIELD OF THE INVENTION

The present invention relates generally to electrical devices and more particularly to electrical devices such as media players that communicate with accessory devices.


BACKGROUND OF THE INVENTION

A media player stores media assets, such as audio tracks, videos, and photos that can be played or displayed on the media player. One example of a media player is the IPod® media player, which is available from Apple Computer, Inc. of Cupertino, Calif. Often, a media player acquires its media assets from a host computer that serves to enable a user to manage media assets. As an example, the host computer can execute a media management application to manage media assets. One example of a media management application is ITunes®, version 6.0, produced by Apple Computer, Inc.


A media player typically includes one or more connectors or ports that can be used to interface to the media player. For example, the connector or port can enable the media player to couple to a host computer, be inserted into a docking system, or receive an accessory device. There are today many different types of accessory devices that can interconnect to the media player. For example, a remote control can be connected to the connector or port to allow the user to remotely control the media player. As another example, an automobile can include a connector and the media player can be inserted onto the connector such that an automobile media system can interact with the media player, thereby allowing the media content on the media player to be played within the automobile.


Currently, the connectors or ports of a media player are open for use so long as a compatible connector or port is utilized. Consequently, numerous third-parties have developed accessory devices for use with other manufacturers' media players. One difficulty is that since a media player communicates with a variety of accessories it does not know the capabilities of the accessory and may not support the capabilities of the accessory.


Accordingly, it is desirable for the media player to know those capabilities and to know whether it supports the capabilities of an associated accessory. Therefore it is also desirable to provide a method and system for allowing a media player to efficiently and effectively determine the capabilities of an accessory and determine if the media player supports such capabilities. The present invention addresses such a need.


BRIEF SUMMARY OF THE INVENTION

A method and system for allowing a media player to determine if it supports the capabilities an accessory are disclosed. The method and system comprise requesting information about the capabilities of the accessory by the media player and providing information about the capabilities of the accessory by the accessory to the media player. The method and system further include utilizing the information to determine if the capabilities of the accessory are supported by the media player.


Accordingly, a method and system in accordance with the present invention allow a media player to obtain information from an accessory about the accessory's capability. A media player can then utilize this information to allow for the maximum functionality of the accessory when connected to the media player.





BRIEF DESCRIPTION OF THE DRAWINGS


FIGS. 1A and 1B illustrate a docking connector in accordance with the present invention.



FIG. 2A is a front and top view of a remote connector in accordance with the present invention.



FIG. 2B illustrates a plug to be utilized in the remote connector.



FIG. 2C illustrates the plug inserted into the remote connector.



FIG. 3A illustrates the connector pin designations for the docking connector.



FIG. 3B illustrates the connection pin designations for the remote connector.



FIG. 4A illustrates a typical FireWire connector interface for the docking connector.



FIG. 4B illustrates a reference schematic diagram for an accessory power source.



FIG. 4C illustrates a reference schematic diagram for a system for detecting and identifying accessories for the docking connector.



FIG. 4D is a reference schematic of an electret microphone that may be connected to the remote connector.



FIG. 5A illustrates a media player coupled to different accessories



FIG. 5B illustrates the media player coupled to a computer.



FIG. 5C illustrates the media player coupled to a car or home stereo system.



FIG. 5D illustrates the media player coupled to a dongle that communicates wirelessly with other accessories.



FIG. 5E illustrates the media player coupled to a speaker system.



FIG. 6 is a simple flow chart illustrating a process for allowing a media player to determine the capabilities of an accessory.



FIG. 7 is a chart of all the accessory information types requested by the media player.





DETAILED DESCRIPTION OF THE INVENTION

The present invention relates generally to electrical devices and more particularly to electrical devices such as media players that communicate with accessory devices. The following description is presented to enable one of ordinary skill in the art to make and use the invention and is provided in the context of a patent application and its requirements. Various modifications to the preferred embodiment and the generic principles and features described herein will be readily apparent to those skilled in the art. Thus, the present invention is not intended to be limited to the embodiment shown but is to be accorded the widest scope consistent with the principles and features described herein.


A method and system in accordance with the present invention allow a media player to obtain information from an accessory. A media player can then utilize this information to allow for the maximum functionality of the accessory when connected to the media player. In one embodiment commands are utilized to facilitate communication of this information between the media player and the accessory.


These commands could be utilized in a variety of environments. One such environment is within a connector interface system environment such as described in detail hereinbelow.


Connector Interface System Overview


To describe the features of the connector interface system in accordance with the present invention in more detail, refer now to the following description in conjunction with the accompanying drawings.


Docking Connector



FIGS. 1A and 1B illustrate a docking connector 100 in accordance with the present invention. Referring first to FIG. 1A, the keying features 102 are of a custom length 104. In addition, a specific key arrangement is used, where one set of keys separated by one length are at the bottom and another set of keys separated by another length are at the top of the connector. The use of this key arrangement prevents noncompliant connectors from being plugged in and causing potential damage to the device. The connector for power utilizes a Firewire specification for power [the connector also can accept power from USB]. The connector includes a first make/last break contact to implement this scheme. FIG. 1B illustrates the first make/last break contact 202 and also illustrates a ground pin and a power pin related to providing an appropriate first make/last break contact. In this example, the ground pin 204 is longer than the power pin 206. Therefore, the ground pin 204 would contact its mating pin in the docking accessory before the power pin 206. Therefore internal electrical damage of the electronics of the device is minimized.


In addition, a connector interface system in accordance with the present invention uses both USB and Firewire interfaces as part of the same docking connector alignment, thereby making the design more compatible with different types of interfaces, as will be discussed in detail hereinafter. In so doing, more remote accessories can interface with the media player.


Remote Connector


The connection interface system also includes a remote connector which provides for the ability to output audio, input audio, and output video, and which also provides I/O serial protocol. FIG. 2A is a front and top view of a remote connector 200 in accordance with the present invention. As is seen, the remote connector 200 includes a top headphone receptacle 202, as well as a second receptacle 204 for remote devices. FIG. 2B illustrates a plug 300 to be utilized in the remote connector. The plug 300 allows the features to be provided via the remote connector. FIG. 2C illustrates the plug 300 inserted into the remote connector 200. Heretofore, all these features have not been implemented in a remote connector. Therefore, a standard headphone cable can be plugged in but also special remote control cables, microphone cables and video cables could be utilized with the remote connector.


To describe the features of the connector interface system in more detail, please find below a functional description of the docking connector, remote connector and a command set in accordance with the present invention.


Docking and Remote Connector Specifications


For an example of the connector pin designations for both the docking connector and for the remote connector for a media player such as an iPod device by Apple Computer, Inc., refer now to FIGS. 3A and 3B. FIG. 3A illustrates the connector pin designations for the docking connector. FIG. 3B illustrates the connection pin designations for the remote connector.


Docking Connector Specifications



FIG. 4A illustrates a typical Firewire connector interface for the docking connector:


Firewire Power:


a) 8V-30V DC IN


b) 10 W Max


Firewire:


a) Designed to IEEE 1394 A Spec (400 Mb/s)


USB Interface


The media player provides two configurations, or modes, of USB device operation: mass storage and media player USB Interface (MPUI). The MPUI allows the media player to be controlled using a media player accessory protocol (MPAP) which will be described in detail later herein, using a USB Human Interface Device (HID) interface as a transport mechanism.


Accessory 3.3 V Power



FIG. 4B illustrates the accessory power source. The media player accessory power pin supplies voltages, for example, 3.0 V to 3.3V+/−5% (2.85 V to 3.465 V) over the 30-pin connector and remote connector (if present). A maximum current is shared between the 30-pin and Audio/Remote connectors.


By default, the media player supplies a particular current such as 5 mA. Proper software accessory detect is required to turn on high power (for example, up to 100 mA) during active device usage. When devices are inactive, they must consume less than a predetermined amount of power such as 5 mA current.


Accessory power is grounded through the DGND pins.



FIG. 4C illustrates a reference schematic diagram for a system for detecting and identifying accessories for the docking connector. The system comprises:


a) A resistor to ground allows the device to determine what has been plugged into docking connector. There is an internal pullup on Accessory Identify.


b) Two pins required (Accessory Identify & Accessory Detect)



FIG. 4D is a reference schematic of an electret microphone that is connected to the remote connector.


Serial Protocol Communication:


a) Two pins used to communicate to and from device (Rx & Tx)


b) Input & Output (0V=Low, 3.3V=High)


As before mentioned, media players connect to a variety of accessories. FIGS. 5A-5E illustrates a media player 500 coupled to different accessories. FIG. 5A illustrates a media player 500 coupled to a docking station 502. FIG. 5B illustrates the media player 500′ coupled to a computer 504. FIG. 5C illustrates the media player 500″ coupled to a car or home stereo system 506. FIG. 5D illustrates the media player 500′ coupled to a dongle 508 that communicates wirelessly with other devices. FIG. 5E illustrates the media player 500″″ coupled to a speaker system 510. As is seen, what is meant by accessories includes but is not limited to docking stations, chargers, car stereos, microphones, home stereos, computers, speakers, and accessories which communicate wirelessly with other accessories.


As before mentioned, this connector interface system could be utilized with a command set for allowing a media player to obtain information from an accessory about its capabilities to allow the media player to determine if it supports the capabilities of the accessory. It should be understood by one of ordinary skill in the art that although the above-identified connector interface system could be utilized with the command set a variety of other connectors or systems could be utilized and they would be within the spirit and scope of the present invention. To describe the utilization of the command set in more detail refer now to the accompanying description in conjunction with the accompanying Figure.



FIG. 6 is a simple flow chart illustrating a process for allowing a media player to utilize information obtained from an accessory. First, the media player requests information from the accessory about the accessory's capabilities, via step 602. Next, the accessory responds with the accessory information, via step 604. Finally, the media player will utilize the information to determine if it supports the accessory's capabilities, via step 606. For example, the information gathered will be used by the media player to:

    • Post accessory information on a display on the media player,
    • Post a message on the display if the media player firmware needs to be updated to support the accessory,
    • Post a UI message if the media player firmware does not support the accessory.


To allow for the determination of the capabilities of the accessory by the media player two commands are passed therebetween. They are a get accessory information (GetAccessoryInfo) command and a return accessory information (RetAccessoryInfo) command. These commands will be described in more detail hereinbelow.


GetAccessoryInfo Command


This command requests a plurality of accessory information from the accessory. An example of a list of requested accessory information types is shown in the table of FIG. 7. The media player may for example request the parameters in the order they are listed in the Table of FIG. 7.


When the GetAccessoryInfo command is sent with an accessory minimum supported media player firmware version info type, the media player model number and the media player firmware version are sent as parameters.


When the GetAccessoryInfo command is sent with an accessory minimum supported command set info type, the command set number for which the media player is requesting the minimum supported version is sent as a parameter. What is meant by a command set is one or more commands that are related to a particular accessory's functionality. For example a microphone command set is related to a microphone functionality, a simple remote command is related to a remote control functionality. Therefore there are a variety of command sets that could be utilized with a particular accessory based upon the accessory's functionality. The media player will send the GetAccessoryInfo command for every command set the accessory indicates it supports.


In one embodiment, the media player will begin sending commands as soon as an accessory identifies successfully. If the accessory does not respond, the media player will wait a predetermined time period for a response before timing out and retrying.


RetAccessoryInfo Command


The accessory sends this command in response to the GetAccessoryInfo command. Utilizing this command the accessory returns accessory information to the media player.


In one embodiment, if an unknown or unsupported media player Model ID is sent to the accessory when requesting the accessory's minimum supported media player firmware version for that particular Model ID, the accessory should return a RetAccessoryInfo command with the media player Model ID and a payload indicating that the accessory does not recognize that particular media player Model ID.


If the accessory's minimum supported media player firmware version is higher than the media player firmware version, and one or more of the command sets are not supported by the media player, the media player will post a message indicating that the media player firmware should be updated.


If the accessory's minimum supported media player firmware version is smaller or equal to the media player firmware version, and one or more of the command sets is higher than that supported by the media player, the media player will post a message indicating that the media player does not support the accessory.


Accordingly, a method and system in accordance with the present invention provides a system that allows a media player to obtain information from an accessory. In so doing, a media player can then utilize this information to allow for the maximum functionality of the accessory when connected to the media player.


Although the present invention has been described in accordance with the embodiments shown, one of ordinary skill in the art will readily recognize that there could be variations to the embodiments and those variations would be within the spirit and scope of the present invention. For example, the present invention can be implemented using hardware, software, a computer readable medium containing program instructions, or a combination thereof. Software written according to the present invention is to be either stored in some form of computer-readable medium such as memory or CD-ROM, or is to be transmitted over a network, and is to be executed by a processor. Consequently, a computer-readable medium is intended to include a computer readable signal, which may be, for example, transmitted over a network. Accordingly, many modifications may be made by one of ordinary skill in the art without departing from the spirit and scope of the appended claims.

Claims
  • 1. A method for use in a portable media player, the method comprising: establishing communication with an accessory; andreceiving capability information from the accessory,wherein the capability information includes a plurality of information items, the plurality of information items including at least: a minimum media player firmware version supported by the accessory;an indication of one or more command sets supported by the accessory; andfor each command set supported by the accessory, a minimum command set version supported by the accessory.
  • 2. The method of claim 1 further comprising: sending a request for capability information to the accessory,wherein receiving the capability information from the accessory is performed in response to sending the request.
  • 3. The method of claim 1 further comprising: sending a media player model identifier to the accessory,wherein the accessory selects the capability information to be sent to the media player based at least in part on the media player model identifier.
  • 4. The method of claim 1 wherein the plurality of information items further includes: an accessory name;an accessory firmware version; andan accessory hardware version.
  • 5. The method of claim 1 wherein the plurality of information items further includes: an accessory manufacturer; andan accessory model number.
  • 6. The method of claim 1 wherein the plurality of information items further includes a maximum incoming packet size supported by the accessory.
  • 7. The method of claim 1 wherein establishing communication with the accessory includes establishing a physical connection to the accessory.
  • 8. The method of claim 2 wherein the request for capability information includes a parameter specifying a requested information item.
  • 9. The method of claim 3 further comprising: in the event that the media player model identifier is not supported by the accessory, receiving from the accessory a notification that the media player model identifier is not recognized.
  • 10. A portable media player for use with an accessory, the portable media player comprising: an interface configured to communicably couple the portable media player to an accessory; andcontrol logic coupled to the interface and configured to exchange commands and associated data with the accessory via the interface,wherein the commands include a first command receivable by the portable media player from the accessory, the first command providing one of a plurality of information items, wherein the plurality of information items includes at least one item selected from a group consisting of: a minimum media player firmware version supported by the accessory;an indication of one or more command sets supported by the accessory; andfor each command set supported by the accessory, a minimum command set version supported by the accessory.
  • 11. The portable media player of claim 10 wherein the plurality of information items further includes: an accessory name;an accessory firmware version; andan accessory hardware version.
  • 12. The portable media player of claim 10 wherein the plurality of information items further includes: an accessory manufacturer; andan accessory model number.
  • 13. The portable media player of claim 10 wherein the plurality of information items further includes a maximum incoming packet size supported by the accessory.
  • 14. The portable media player of claim 10 wherein the commands further include a second command sendable to the accessory by the portable media player, the second command requesting information from the accessory and specifying one of the plurality of sendable information items as being requested.
  • 15. The portable media player of claim 10 wherein the commands further include a second command sendable to the accessory by the portable media player, the second command providing a media player model identifier to the accessory.
  • 16. The portable media player of claim 10 wherein the interface comprises a connector having a plurality of pins and wherein at least two of the pins are configured to provide communication according to a serial protocol.
  • 17. The portable media player of claim 15 wherein the control logic is further configured to detect a non-recognition signal sent by the accessory to the portable media player, wherein the non-recognition signal indicates that the portable media player is not supported by the accessory.
  • 18. The portable media player of claim 17 wherein the non-recognition signal is one of the plurality of information items of the first command.
  • 19. A method for use in a portable media player, the method comprising: establishing communication with an accessory; andreceiving capability information from the accessory, wherein the capability information includes a plurality of information items selected from a group consisting of: an information item identifying information capabilities of the accessory;an accessory name;a minimum version of media player firmware supported by the accessory;a minimum version of a command set supported by the accessory;an accessory firmware version;an accessory hardware version;an accessory manufacturer;an accessory model number;an accessory serial number; anda maximum incoming packet size supported by the accessory.
  • 20. The method of claim 19 further comprising sending a request for capability information to the accessory.
  • 21. The method of claim 19 further comprising: sending a media player model identifier to the accessory,wherein the accessory selects the capability information to be sent to the media player, the selection being based at least in part on the media player model identifier.
  • 22. The method of claim 19 wherein establishing communication with the accessory includes establishing a physical connection to the accessory.
  • 23. The method of claim 20 wherein the request for capability information specifies one of the plurality of information items as being requested.
  • 24. The method of claim 21 further comprising: in the event that the media player model identifier is not supported by the accessory, receiving from the accessory a notification that the media player model identifier is not recognized.
  • 25. A portable media player for use with an accessory, the portable media player comprising: an interface configured to communicably couple the portable media player to an accessory; andcontrol logic coupled to the interface and configured to exchange commands and associated data with the accessory via the interface,wherein the commands include a first command receivable by the portable media player from the accessory, the first command providing one of a plurality of information items, wherein the plurality of information items includes at least two items selected from a group consisting of: an information item identifying information capabilities of the accessory;an accessory name;a minimum version of media player firmware supported by the accessory;a minimum version of a command set supported by the accessory;an accessory firmware version;an accessory hardware version;an accessory manufacturer;an accessory model number;an accessory serial number; anda maximum incoming packet size supported by the accessory.
  • 26. The portable media player of claim 25 wherein the commands further include a second command sendable by the portable media player to the accessory, the second command requesting information from the accessory and specifying one of the plurality of sendable information items as being requested.
  • 27. The portable media player of claim 25 wherein the commands further include a second command sendable by the portable media player to the accessory, the second command providing a media player model identifier to the accessory.
  • 28. The portable media player of claim 25 wherein the interface comprises a connector having a plurality of pins and wherein at least two of the pins are configured to provide communication according to a serial protocol.
  • 29. The portable media player of claim 27 wherein the control logic is further configured to detect a non-recognition signal sent by the accessory to the portable media player, wherein the non-recognition signal indicates that the portable media player is not supported by the accessory and wherein the accessory determines whether to send the non-recognition signal based on the media player model identifier.
  • 30. The portable media player of claim 29 wherein the non-recognition signal is one of the plurality of information items of the first command.
CROSS-REFERENCES TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/176,920, filed Jul. 21, 2008, entitled “Method and System for Allowing a Media Player to Determine If it Supports the Capabilities of an Accessory,” which is a continuation of U.S. patent application Ser. No. 11/476,276, entitled “Method and System for allowing Media Player to Determine If it Supports the Capabilities of an Accessory,” filed Jun. 27, 2006 (now U.S. Pat. No. 7,415,563), both of which are incorporated herein by reference.

US Referenced Citations (381)
Number Name Date Kind
4673861 Dubovsky et al. Jun 1987 A
4850899 Maynard Jul 1989 A
4916334 Minagawa et al. Apr 1990 A
4924216 Leung May 1990 A
4938483 Yavetz Jul 1990 A
5041025 Haitmanek Aug 1991 A
5051606 Ikehara Sep 1991 A
5055069 Townsend et al. Oct 1991 A
5080603 Mouissie Jan 1992 A
5104243 Harding Apr 1992 A
5108313 Adams Apr 1992 A
5150031 James et al. Sep 1992 A
5186646 Pederson Feb 1993 A
5247138 Landmeier Sep 1993 A
5277624 Champion Jan 1994 A
5471128 Patino et al. Nov 1995 A
5525981 Abernethy Jun 1996 A
5546397 Mahany Aug 1996 A
5586893 Mosquera Dec 1996 A
5592588 Reekes et al. Jan 1997 A
5618045 Kagan et al. Apr 1997 A
5648712 Hahn Jul 1997 A
5660558 Osanai et al. Aug 1997 A
5675467 Nishimura et al. Oct 1997 A
5727866 Kraines et al. Mar 1998 A
5732361 Liu Mar 1998 A
5754027 Oglesbee et al. May 1998 A
5830001 Kinoshita Nov 1998 A
5835862 Nykanen et al. Nov 1998 A
5845217 Lindell et al. Dec 1998 A
5859522 Theobald Jan 1999 A
5884323 Hawkins et al. Mar 1999 A
5901049 Schmidt et al. May 1999 A
5964847 Booth, III et al. Oct 1999 A
5975957 Noda et al. Nov 1999 A
5991640 Lilja et al. Nov 1999 A
6007372 Wood Dec 1999 A
6012105 Rubbmark et al. Jan 2000 A
6031797 Van Ryzin et al. Feb 2000 A
6053773 Wu Apr 2000 A
6078402 Fischer et al. Jun 2000 A
6078789 Bodenmann et al. Jun 2000 A
6125455 Yeo Sep 2000 A
6130518 Gabehart et al. Oct 2000 A
6139373 Ward et al. Oct 2000 A
6154773 Roberts et al. Nov 2000 A
6154798 Lin et al. Nov 2000 A
6161027 Poirel Dec 2000 A
6169387 Kaib Jan 2001 B1
6175358 Scott-Jackson et al. Jan 2001 B1
6178514 Wood Jan 2001 B1
6184652 Yang Feb 2001 B1
6184655 Malackowski Feb 2001 B1
6188265 Liu et al. Feb 2001 B1
6192340 Abecassis Feb 2001 B1
6203345 Roque et al. Mar 2001 B1
6204637 Rengan Mar 2001 B1
6206480 Thompson Mar 2001 B1
6211581 Farrant Apr 2001 B1
6211649 Matsuda Apr 2001 B1
6224420 Nishio et al. May 2001 B1
6230205 Garrity et al. May 2001 B1
6230322 Saib et al. May 2001 B1
6234827 Nishio et al. May 2001 B1
6236395 Sezan et al. May 2001 B1
6247135 Feague Jun 2001 B1
6252380 Koenck Jun 2001 B1
6255961 Van Ryzin et al. Jul 2001 B1
6261109 Liu et al. Jul 2001 B1
6262723 Matsuzawa et al. Jul 2001 B1
6267623 Hisamatsu Jul 2001 B1
6268845 Pariza et al. Jul 2001 B1
6271605 Carkner et al. Aug 2001 B1
6272328 Nguyen et al. Aug 2001 B1
6280251 Nishio et al. Aug 2001 B1
6283789 Tsai Sep 2001 B1
6304764 Pan Oct 2001 B1
6314326 Fuchu Nov 2001 B1
6314479 Frederick et al. Nov 2001 B1
6316916 Bohne Nov 2001 B2
6319061 Chen et al. Nov 2001 B1
6322396 Kuan Nov 2001 B1
6336365 Blackadar et al. Jan 2002 B1
6344727 Desai et al. Feb 2002 B1
6353894 Pione Mar 2002 B1
6354713 Leifer et al. Mar 2002 B1
6358089 Kuroda et al. Mar 2002 B1
6372974 Gross et al. Apr 2002 B1
6377825 Kennedy et al. Apr 2002 B1
6385596 Wiser et al. May 2002 B1
6394905 Takeda et al. May 2002 B1
6418421 Hurtado et al. Jul 2002 B1
6429622 Svensson Aug 2002 B1
6429879 Sturgeon et al. Aug 2002 B1
6431915 Ko Aug 2002 B1
6453371 Hampson et al. Sep 2002 B1
6454592 Takagi Sep 2002 B2
6461173 Mizuno et al. Oct 2002 B1
6464542 Lee Oct 2002 B1
6468110 Fujino et al. Oct 2002 B2
6476825 Croy et al. Nov 2002 B1
6478603 Wu Nov 2002 B1
6483428 Fish et al. Nov 2002 B1
6485328 Wu Nov 2002 B1
6489751 Small Dec 2002 B2
6501441 Ludtke et al. Dec 2002 B1
6505160 Levy et al. Jan 2003 B1
6524119 Kato et al. Feb 2003 B2
6526287 Lee Feb 2003 B1
6535983 McCormack et al. Mar 2003 B1
6558201 Begley et al. May 2003 B1
6559773 Berry May 2003 B1
6577877 Charlier et al. Jun 2003 B1
6589076 Davis et al. Jul 2003 B1
6591085 Grady Jul 2003 B1
6608264 Fouladpour Aug 2003 B1
6608399 McConnell et al. Aug 2003 B2
6614232 Mukai Sep 2003 B1
6616473 Kamata et al. Sep 2003 B2
6629197 Bhogal et al. Sep 2003 B1
6642629 DeLeeuw Nov 2003 B2
6643777 Chu Nov 2003 B1
6651138 Lai et al. Nov 2003 B2
6653813 Khatri Nov 2003 B2
6663420 Xiao Dec 2003 B1
6665803 Osborn et al. Dec 2003 B2
6670997 Northrup Dec 2003 B1
6674995 Meyers et al. Jan 2004 B1
6687454 Kuroiwa Feb 2004 B1
6697944 Jones et al. Feb 2004 B1
6708283 Nelvin et al. Mar 2004 B1
6724339 Conway et al. Apr 2004 B2
6725061 Hutchison, IV et al. Apr 2004 B1
6728546 Peterson et al. Apr 2004 B1
6728729 Jawa et al. Apr 2004 B1
6747859 Walbeck et al. Jun 2004 B2
6754468 Sieben et al. Jun 2004 B1
6761635 Hoshino et al. Jul 2004 B2
6774939 Peng Aug 2004 B1
6776626 Huang et al. Aug 2004 B2
6776660 Kubota et al. Aug 2004 B1
6776665 Huang Aug 2004 B2
6799226 Robbin et al. Sep 2004 B1
6801964 Mahdavi Oct 2004 B1
6813528 Yang Nov 2004 B1
6816376 Bright et al. Nov 2004 B2
6830160 Risolia Dec 2004 B2
6859538 Voltz Feb 2005 B1
6859854 Kwong Feb 2005 B2
6879843 Kim Apr 2005 B1
6928295 Olson et al. Aug 2005 B2
6931266 Miyoshi et al. Aug 2005 B2
6931456 Payne et al. Aug 2005 B2
6939177 Kato et al. Sep 2005 B2
6944704 Brelin Sep 2005 B2
6991483 Milan et al. Jan 2006 B1
7004787 Milan Feb 2006 B2
7006793 Himmel et al. Feb 2006 B2
7013164 Lin Mar 2006 B2
7040919 Yao May 2006 B2
7046230 Zadesky May 2006 B2
7050783 Curtiss et al. May 2006 B2
7054888 LaChapelle et al. May 2006 B2
7062261 Goldstein et al. Jun 2006 B2
7108560 Chou et al. Sep 2006 B1
7120462 Kumar Oct 2006 B2
7127678 Bhesania et al. Oct 2006 B2
7127879 Zhu et al. Oct 2006 B2
7149543 Kumar Dec 2006 B2
7155545 Wang Dec 2006 B1
7167112 Andersen et al. Jan 2007 B2
7167935 Hellberg Jan 2007 B2
7187947 White et al. Mar 2007 B1
7187948 Alden Mar 2007 B2
7215042 Yan May 2007 B2
7281214 Fadell Oct 2007 B2
7293122 Schubert et al. Nov 2007 B1
7293227 Plastina et al. Nov 2007 B2
7299304 Saint-Hilaire et al. Nov 2007 B2
7303282 Dwyer et al. Dec 2007 B2
7304685 Park et al. Dec 2007 B2
7305254 Findikli Dec 2007 B2
7305506 Lydon et al. Dec 2007 B1
7324833 White et al. Jan 2008 B2
7362963 Lin Apr 2008 B2
7363129 Bamicle et al. Apr 2008 B1
7391963 Chen et al. Jun 2008 B2
7415563 Holden et al. Aug 2008 B1
7441058 Bolton et al. Oct 2008 B1
7441062 Novotney et al. Oct 2008 B2
7444388 Svendsen Oct 2008 B1
7450961 Heubel et al. Nov 2008 B1
7454019 Williams Nov 2008 B2
7493645 Tranchina Feb 2009 B1
7526588 Schubert et al. Apr 2009 B1
7529870 Schubert et al. May 2009 B1
7529871 Schubert et al. May 2009 B1
7529872 Schubert et al. May 2009 B1
7558894 Lydon et al. Jul 2009 B1
7587540 Novotney et al. Sep 2009 B2
7590783 Lydon et al. Sep 2009 B2
7610350 Abdulrahiman et al. Oct 2009 B2
7634605 Laefer et al. Dec 2009 B2
7660929 Novotney et al. Feb 2010 B2
7670263 Ellis et al. Mar 2010 B2
7673020 Rosenbloom et al. Mar 2010 B2
7673083 Laefer et al. Mar 2010 B2
7680849 Heller et al. Mar 2010 B2
7702833 Novotney et al. Apr 2010 B2
7757026 Novotney et al. Jul 2010 B2
7779185 Schubert et al. Aug 2010 B2
7791319 Veselic et al. Sep 2010 B2
7797471 Laefer et al. Sep 2010 B2
7853746 Novotney et al. Dec 2010 B2
7877532 Schubert et al. Jan 2011 B2
8095716 Holden et al. Jan 2012 B2
20010003205 Gilbert Jun 2001 A1
20010005641 Matsumoto et al. Jun 2001 A1
20010006884 Matsumoto Jul 2001 A1
20010042107 Palm Nov 2001 A1
20020002035 Sim et al. Jan 2002 A1
20020010759 Hitson et al. Jan 2002 A1
20020015362 Cowgill et al. Feb 2002 A1
20020025042 Saito Feb 2002 A1
20020029303 Nguyen Mar 2002 A1
20020065074 Cohn et al. May 2002 A1
20020068610 Anvekar et al. Jun 2002 A1
20020072390 Uchiyama Jun 2002 A1
20020103008 Rahn et al. Aug 2002 A1
20020105861 Leapman Aug 2002 A1
20020108108 Akaiwa et al. Aug 2002 A1
20020115480 Huang Aug 2002 A1
20020116533 Holliman et al. Aug 2002 A1
20020120850 Walker et al. Aug 2002 A1
20020132651 Jinnouchi Sep 2002 A1
20020151327 Levitt Oct 2002 A1
20020152874 Vilcauskas et al. Oct 2002 A1
20020156546 Ramaswamy Oct 2002 A1
20020156949 Kubo et al. Oct 2002 A1
20020161865 Nguyen Oct 2002 A1
20020173273 Spurgat et al. Nov 2002 A1
20020174269 Spurgat et al. Nov 2002 A1
20020194621 Tran et al. Dec 2002 A1
20030004934 Qian Jan 2003 A1
20030011608 Wada Jan 2003 A1
20030028664 Tan et al. Feb 2003 A1
20030041206 Dickie Feb 2003 A1
20030059022 Nebiker et al. Mar 2003 A1
20030067741 Alfonso et al. Apr 2003 A1
20030073432 Meade Apr 2003 A1
20030079038 Robbin et al. Apr 2003 A1
20030090988 Sun et al. May 2003 A1
20030097379 Ireton May 2003 A1
20030110403 Crutchfield et al. Jun 2003 A1
20030151621 McEvilly et al. Aug 2003 A1
20030167318 Robbin et al. Sep 2003 A1
20030172209 Liu et al. Sep 2003 A1
20030185395 Lee et al. Oct 2003 A1
20030198015 Vogt Oct 2003 A1
20030212895 Kisliakiv Nov 2003 A1
20030215102 Marlowe Nov 2003 A1
20030220988 Hymel Nov 2003 A1
20030236075 Johnson et al. Dec 2003 A1
20030237043 Novak et al. Dec 2003 A1
20040003300 Malueg et al. Jan 2004 A1
20040019497 Volk et al. Jan 2004 A1
20040039860 Mills et al. Feb 2004 A1
20040048569 Kawamura Mar 2004 A1
20040055446 Robbin et al. Mar 2004 A1
20040090998 Chen May 2004 A1
20040103223 Gabehart et al. May 2004 A1
20040116005 Choi Jun 2004 A1
20040151327 Marlowe Aug 2004 A1
20040162029 Grady Aug 2004 A1
20040164708 Veselic et al. Aug 2004 A1
20040172533 DeMello et al. Sep 2004 A1
20040186935 Bel et al. Sep 2004 A1
20040194154 Meadors et al. Sep 2004 A1
20040198436 Alden Oct 2004 A1
20040224638 Fadell et al. Nov 2004 A1
20040235339 Sato et al. Nov 2004 A1
20040249994 Shapiro et al. Dec 2004 A1
20040252966 Holloway et al. Dec 2004 A1
20040267812 Harris et al. Dec 2004 A1
20040267825 Novak et al. Dec 2004 A1
20040268397 Dunbar et al. Dec 2004 A1
20050001589 Edington Jan 2005 A1
20050014119 Rudakov Jan 2005 A1
20050014531 Findikli Jan 2005 A1
20050014536 Grady Jan 2005 A1
20050015355 Heller et al. Jan 2005 A1
20050018768 Mabey et al. Jan 2005 A1
20050022212 Bowen Jan 2005 A1
20050047071 Tse Chun Hin Mar 2005 A1
20050080915 Shoemaker et al. Apr 2005 A1
20050135790 Hutten Jun 2005 A1
20050138433 Linetsky Jun 2005 A1
20050149213 Guzak et al. Jul 2005 A1
20050149551 Fong et al. Jul 2005 A1
20050181756 Lin Aug 2005 A1
20050198189 Robinson et al. Sep 2005 A1
20050207726 Chen Sep 2005 A1
20050227612 Helstrom et al. Oct 2005 A1
20050239333 Watanabe et al. Oct 2005 A1
20050240705 Novotney et al. Oct 2005 A1
20050246375 Manders et al. Nov 2005 A1
20050251565 Weel Nov 2005 A1
20050281185 Kawasaki Dec 2005 A1
20060015826 Shiozawa et al. Jan 2006 A1
20060031545 Manders et al. Feb 2006 A1
20060056796 Nishizawa et al. Mar 2006 A1
20060088228 Marriott et al. Apr 2006 A1
20060116009 Langberg et al. Jun 2006 A1
20060143680 Adachi Jun 2006 A1
20060156415 Rubinstein et al. Jul 2006 A1
20060161621 Rosenberg Jul 2006 A1
20060163358 Biderman Jul 2006 A1
20060168298 Aoki et al. Jul 2006 A1
20060184456 de Janasz Aug 2006 A1
20060188237 Watanabe et al. Aug 2006 A1
20060205349 Passier et al. Sep 2006 A1
20060224620 Silverman et al. Oct 2006 A1
20060236245 Agarwal et al. Oct 2006 A1
20060247851 Morris Nov 2006 A1
20060258289 Dua Nov 2006 A1
20060277555 Howard Dec 2006 A1
20060294209 Rosenbloom et al. Dec 2006 A1
20070011138 Boucard Jan 2007 A1
20070018947 Toro-Lira Jan 2007 A1
20070056012 Kwon et al. Mar 2007 A1
20070056013 Duncan Mar 2007 A1
20070070856 Tebele Mar 2007 A1
20070077784 Kalayjian et al. Apr 2007 A1
20070080823 Fu et al. Apr 2007 A1
20070083750 Miura et al. Apr 2007 A1
20070083814 Wilbrink et al. Apr 2007 A1
20070086724 Grady et al. Apr 2007 A1
20070106760 Houh et al. May 2007 A1
20070130592 Haeusel Jun 2007 A1
20070173197 Hsiung Jul 2007 A1
20070173294 Hsiung Jul 2007 A1
20070206827 Tupman et al. Sep 2007 A1
20070209081 Morris Sep 2007 A1
20070226238 Kiilerich et al. Sep 2007 A1
20070226384 Robbin et al. Sep 2007 A1
20070230910 Welch et al. Oct 2007 A1
20070233294 Holden et al. Oct 2007 A1
20070233295 Laefer et al. Oct 2007 A1
20070234420 Novotney et al. Oct 2007 A1
20070236482 Proctor et al. Oct 2007 A1
20070244984 Svendsen Oct 2007 A1
20070247794 Jaffe et al. Oct 2007 A1
20070271387 Lydon et al. Nov 2007 A1
20070280489 Roman et al. Dec 2007 A1
20070291404 Morse et al. Dec 2007 A1
20070300155 Laefer et al. Dec 2007 A1
20080010014 Hess Jan 2008 A1
20080025172 Holden et al. Jan 2008 A1
20080034325 Ording Feb 2008 A1
20080055272 Anzures et al. Mar 2008 A1
20080065722 Brodersen et al. Mar 2008 A1
20080155129 Khedouri et al. Jun 2008 A1
20080188209 Dorogusker et al. Aug 2008 A1
20090013110 Novotney et al. Jan 2009 A1
20090013253 Laefer et al. Jan 2009 A1
20090125134 Bolton et al. May 2009 A1
20090132076 Holden et al. May 2009 A1
20090198361 Schubert et al. Aug 2009 A1
20090204244 Schubert et al. Aug 2009 A1
20090204738 Schubert et al. Aug 2009 A1
20090210079 Schubert et al. Aug 2009 A1
20090249101 Lydon et al. Oct 2009 A1
20090292835 Novotney et al. Nov 2009 A1
20090299506 Lydon et al. Dec 2009 A1
20100049350 Laefer et al. Feb 2010 A1
20100106879 Laefer et al. Apr 2010 A1
20100312931 Schubert et al. Dec 2010 A1
20100312932 Schubert et al. Dec 2010 A1
20110066775 Schubert et al. Mar 2011 A1
20110066776 Schubert et al. Mar 2011 A1
20120102236 Schubert et al. Apr 2012 A1
Foreign Referenced Citations (57)
Number Date Country
1104150 May 2001 EP
1150472 Oct 2001 EP
1367734 Dec 2003 EP
1498899 Jan 2005 EP
1594319 Nov 2005 EP
1672613 Jun 2006 EP
2405718 Mar 2005 GB
07-176351 Jul 1995 JP
10-321302 Apr 1998 JP
10-334993 Dec 1998 JP
11-288420 Oct 1999 JP
2000-214953 Aug 2000 JP
2000-223215 Aug 2000 JP
2000-223216 Aug 2000 JP
2000-223218 Aug 2000 JP
2001-035603 Feb 2001 JP
2001-069165 Mar 2001 JP
2001-196133 Jul 2001 JP
2001-230021 Aug 2001 JP
2001-332350 Nov 2001 JP
2002-025720 Jan 2002 JP
2002-140304 May 2002 JP
2002-203641 Jul 2002 JP
2002-245719 Aug 2002 JP
2002-252566 Sep 2002 JP
3090747 Oct 2002 JP
2002-342659 Nov 2002 JP
2002-374447 Dec 2002 JP
2003-017165 Jan 2003 JP
2003-032351 Jan 2003 JP
2003-058430 Feb 2003 JP
2003-274386 Sep 2003 JP
2004-078538 Mar 2004 JP
2004-259280 Sep 2004 JP
2008053955 Mar 2008 JP
2008071419 Mar 2008 JP
2009303001 Dec 2009 JP
530267 May 2003 TW
9926330 May 1999 WO
9948089 Sep 1999 WO
0039907 Jul 2000 WO
0060450 Oct 2000 WO
0249314 Jun 2002 WO
03036541 May 2003 WO
03036957 May 2003 WO
03056776 Jul 2003 WO
03073688 Sep 2003 WO
2004084413 Sep 2004 WO
2004095772 Nov 2004 WO
2004112311 Dec 2004 WO
2005109781 Nov 2005 WO
2005119463 Dec 2005 WO
2006071364 Jul 2006 WO
2006073702 Jul 2006 WO
2006080957 Aug 2006 WO
2007139660 Dec 2007 WO
2011031760 Mar 2011 WO
Non-Patent Literature Citations (46)
Entry
Altec Lansing, “inMOTION Users Guide,” Corp. Headquarters, 535 Rte.6 & 209, Milford, PA 18337. (8 pages).
Anonymous, “Future of Digital Music in Windows,” Microsoft Windows Hardware Developer Central Archive, Dec. 4, 2001[Online], [retrieved on Jan. 15, 2008].<URL:http://www.microsoft.com/whdc/archive/digitaudio.mspx> (3 pages).
Anonymous, “Introduction to Digital Audio,” Microsoft Windows Hardware Developer Central Archive, Dec. 4, 2001 [Online], [retrieved on Jan. 15, 2008].<URL:http://www.microsoft.com/whdc/archive/digitaudio.mspx>(2 pages).
Anonymous, “Windows and Red Book Audio,” Microsoft Windows Hardware Developer Central Archive, Dec. 4, 2001 [Online], [retrieved Jan. 15, 2008]. <URL:http://www.microsoft.com/whdc/archive/Dmfuture.mspx> (2 pages).
“A Serial Bus on Speed Diagram: Getting Connected with FireWire,” downloaded Oct. 16, 2001, PC Magazine: PC Tech (A Serial Bus on Speed) wysiwyg://51http://www.zdnet.com/pctech/content/18/10/tu1810.007.html p. 7. (2 pages).
Belkin iPod Voice Recorder, Product Specification Sheet, printed Jun. 16, 2004. (2 pages).
Bindra, “Standard Turns Monitor into I/O Hub,” Electronic Engineering Times, vol. 918, Sep. 6, 1996, p. 14. (1 page).
Brentrup, “Introduction to Public Key Cryptography Demystified,” Campus Technology, printed from http://www.campus-technology.com/article.asp?id=7626 on Oct. 6, 2004. (5 pages).
Brown, “Making USB Work,” downloaded Oct. 16, 2001, PC Magazine: PC Tech wysiwyq:/155/http://www.zdnet.com/pcmag/pctech/content?18/04/tu1804.001.html (2 pages).
“Cables to Go,” download Oct. 16, 2001 http://www.cablestogo.com/product.asp?cat%5Fid=601&sku=27028 (1 page).
Chen et al., “Design and Implemeation of a Hard Disk-Based Entertainment Device for Managing Media Contents On The Go,” Consumer Electonics, 1005. (ISCE 2005). Proceedings of the Ninth International Symposium on, pp. 328-333, Jun. 14-16, 2005. (6 pages).
Crawford et al., “Sample rate conversion and bit rate reduction in the studio,” IEEE Colloquium on Digital Audio Signal Processing, May 22, 1991, pp. 8/1-8/3. (3 pages).
Derman, “Monitors Make Net Connections,” Electronic Engineering Times, vol. 933, 1996, pp. 60 and 69. (2 pages).
“ExpressBus™ F5U0I0,” User Guide Packing Checklist, Belkin Components Product Warranty. (2 pages).
“FireWire”, downloaded Oct. 16,2001; si—wyg:/—/42/http://developer.apple.—com/hardware/Fire—Wire (2 pages).
“Fire Wire Connector,” downloaded Oct. 16, 2001, wysiwyg://76/http://developer.apple.com/...es/Macintosh—CPUs-G3/ibook/ibook-27.html (2 pages).
Fried, “FireWire poised to become ubiquitous,” downloaded Oct. 16, 2001, CNET News.com, 1394 Trade Association: Press, wysiwyq:/132/http:/—113—94ta.orq/Press/200—1—Press/august!8.2 7.b.html (3 pages).
Fried, “New Fire Wire to blaze faster trail,” downloaded Oct. 16, 2001, CNET News.com, http://news.cnet.com/news/0-I006-200-6021210.html (5 pages).
“How to Connect Your Computer PC Hardware”, downloaded Oct. 16, 2001, http:///www.scar.utoronto.ca!˜ccweb/faculty/connect-howto.html. (5 pages).
“IEEE 1394/USB Comparison,” downloaded Oct. 16, 2001, www.genitech.com.aulLIBRARY/TechSupportiinfobits/firewireysusb.html (4 pages).
“Introduction to Public Key Cryptography,” Oct. 9, 1998, printed from http://developer.netscape.com/docs/manuals/security/pkin/contents.html on Oct. 6, 2004. (21 pages).
iPod Classic User's Guide, acquired from apple.com, 2002. (44 pages).
iPod nano Features Guide, acquired from apple.com, 2008. (72 pages).
iPod touch User's Guide, acquired from apple.com, 2008. (120 pages).
“iPodDock/iPod Cradle,” www.bookendzdocks.com/bookendz/dock—cradle.html, downloaded Feb. 27, 2003. (2 pages).
Lambert, “Digital Audio Interfaces,” Journal of the Audio Engineering Society, Audio Engineering Society, New York, NY, vol. 38, No. 9, (Sep. 1, 1990), pp. 681-684, 686, 688, 690, 692 and 696, XP000175146 ISSN: 1549-4950 figures 9, 10. (10 pages).
Lewis, “On Technology” Fortune Magazine, Dec. 9, 2002, p. 240. (1 page).
LSI Logic's Broadcast PC Card Brings New Multimedia Capabilities to Personal Computing. (Nov. 16). PR Newswire, 1. Retrieved Jun. 26, 2010, from Business Dateline. (3 pages).
MAXTech Technology Ltd., CES 2000/Las Vegas, Jan. 6-9, 2000, [on line], [retrieved on Sep. 26, 2008]. Retrieved from the Internet <URL:http://web.archive.org/web/20000930170634/www.maxtech.com.hk/t-details.htm>. (2 pages).
MAXTech Technology Ltd., CES 2000/Las Vegas, Jan. 6-9, 2000, [online], [retrieved on Sep. 23, 2008]. Retrieved from the Internet <URL:http://web.archive.org/web/20010223230441/www.maxtech.com.hk/g-p06.htm>. (2 pages).
Menezes et al., “Handbook of Applied Cryptography,” Identification and Entity Authentication, Jan. 1, 1997, pp. 385-424. (41 pages).
Microsoft, “Media Transport Protocol Implementation Details,” 2005. (18 pages).
“MPV™ Music Profile Specification Revision 1.00” Internet Citation [online] (Jan. 7, 2004) URL:http//www.osta.org/mpv/public/specs/MPVMusic-Prof-Spec-1.00.pdf> [retrieved Jun. 20, 2006] the whole document. (70 pages).
Networking Tech Note, “1394 Standards and Specifications.” (3 pages).
“Neuros MP3 Digital Audio Computer,” www.neurosaudio.com, downloaded Apr. 9, 2003. (6 pages).
Nomad II Player Version 1.0 (CLI) (User's Manual), Creative Technology, Ltd., Jan. 2000. (46 pages).
“PMC FW2 IEEE1394 FireWire Controller”, downloaded Oct. 16, 2001, http://www.bvmltd.co.uk/PMCfw2ds.html (10 pages).
Severance, “FireWire Finally Comes Home,” Michigan State University, Standards, Nov. 1998, pp. 117-118. (2 pages).
Sinitsyn, “Synchronization Framework for Personal Mobile Servers,” Pervasive Computing and Communications Workshops (PERCOMW'04), Proceedings of the Second IEEE Annual Conference, Piscataway, NJ, USA, IEEE, Mar. 14, 2004, pp. 208-212. (3 pages).
Slay et al., “iPod Forensics: Forencically Sound Examination of an Apple iPod,” System Sciences, 2007. HICSS 2007. 40th Annual Hawaii Internation Conference on, pp. 1-9, Jan. 2007. (9 pages).
Teener, “Understanding Fire Wire: The IEEE 1394 Standards and Specifications,” downloaded Oct. 16, 2001, wysiwyg:119/http:1Iwww.chipcenter.com/networking/ieee 1394/main.html (5 pages).
“The Authoritative Dictionary of IEEE Standards Terms, Seventh Edition,” Published by Standards Information Network, IEEE Press, 2000. (3 pages).
“Universal Serial Bus Specification—Rev 2.0,” Chapter 6: Compaq Hewlett-Packard, Apr. 27, 2000, pp. 85, 99-100. (7 pages).
“Universal Serial Bus Specification—Rev 2.0,” XP002474828, Chapter 9: USB Device Framework, pp. 239-274. (36 pages).
Vitaliano, “Why FireWire is Hot!Hot!Hot!” downloaded Oct. 16, 2001, “Impact.FireWire.SideBar” http://www.vxm.com/21R.35.html (4 pages).
Whittle, “Public Key Authentication Framework: Tutorial,” First Principles Consulting, Jun. 2, 1996, downloaded Oct. 6, 2004, http://www.ozemail.com.au/˜firstpr/crypto/pkaftute.htm (7 pages).
Related Publications (1)
Number Date Country
20120096189 A1 Apr 2012 US
Continuations (2)
Number Date Country
Parent 12176920 Jul 2008 US
Child 13331446 US
Parent 11476276 Jun 2006 US
Child 12176920 US