US 7,779,185 B2Grant

Communication between a media player and an accessory using a protocol with multiple lingoes

Issue Date:2010-08-17

•22 Claims

•15 Drawing Sheets

Abstract

An interface and protocol allow a media player to communicate with external accessories over a transport link. The protocol includes a core protocol functionality and a number of accessory lingoes. Examples of accessory lingoes include a microphone lingo, a simple remote lingo, a display remote lingo, an RF transmitter lingo, and an extended interface lingo.

Metadata

Assignee

Apple Inc.

Inventors

Emily Clark Schubert
Wang Chun Leung
Gregory T. Lydon
Scott Krueger
Paul Philip Holden
John Archibald
Lawrence G. Bolton
Donald J. Novotney
John Benjamin Filson
David Tupman

Application Information

Application Number:US 12/424,426

Filing Date:2009-04-15

Priority Date:2004-04-27

Art Unit:2111

Classifications

IPC:

G06F13/42

Patent Drawings (15 sheets)

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is a continuation of U.S. application Ser. No. 11/479,894, filed Jun. 30, 2006, entitled “Connector Interface System”, which is a continuation-in-part of U.S. application Ser. No. 10/833,689, filed Apr. 27, 2004, entitled “Connector Interface System from a Multi-Communication Device,” and which also claims the benefit of U.S. Provisional Patent Application No. 60/784,306, filed Mar. 20, 2006, entitled “Connector Interface System.” The disclosures of each of these applications are incorporated herein by reference in their entirety.

FIELD OF THE INVENTION

[0002] The present invention relates generally to connector interfaces and more particularly to a connector interface system which is utilized in conjunction with media players and their accessories.

BACKGROUND OF THE INVENTION

[0003] A media player stores media assets, such as audio tracks or 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.

[0004] 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.

[0005] 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.

[0006] In a typical connector interface, there is a docking connector that allows for the docking of the media player device to a docking station for another type of communication for the device. A media player also typically includes a remote connector with the ability to output audio. As more multi-media content becomes available (i.e., digital, video graphics, etc.) it is desirable to have a media player which can effectively input and output such data.

[0007] Finally, a media player must be able to identify a particular device's functionality to which it is associated. Heretofore, there is no device that includes features that overcome many of the above-stated problems. What is desired is a connector interface system which is utilized in such a device to address all the above-identified issues. The present invention addresses such a need.

SUMMARY OF THE INVENTION

[0008] A connector interface system is disclosed. The connector interface system includes an interface and a protocol in communication with the interface which allows a media player to communicate with external devices over a transport link. The protocol includes a core protocol functionality and a plurality of accessory lingoes. The accessory lingoes comprise a microphone lingo, a simple remote lingo, a display remote lingo, a RF transmitter lingo and an extended interface lingo.

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] FIGS. 2A-2C illustrate the remote connector in accordance with the present invention.

[0011] FIG. 3A illustrates the connector pin designations for the docking connector.

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

[0013] FIG. 4A illustrates the Firewire connector interface.

[0014] FIG. 4B illustrates the USB connector interface.

[0015] FIG. 4C illustrates a reference schematic diagram for accessory detect and identify system for detecting and identifying accessories for the docking connector.

[0016] FIG. 4D is a reference schematic of an electret microphone that is within the remote connector.

[0017] FIGS. 5A-5E illustrate a media player coupled to a plurality of accessories.

[0018] FIG. 6 illustrates the sequence of events that can be utilized to test for the full set of general lingo commands.

[0019] FIG. 7 illustrates a single lingo accessory command flow.

[0020] FIG. 8 illustrates a multiple lingo command flow.

[0021] FIG. 9 illustrates an exemplary system using the connector interface system described herein.

DETAILED DESCRIPTION

Definitions

Device

[0022] An external electronic component connected to the media player using the 30-pin connector or the audio/remote connector.

HID

[0023] Human Interface Device. HID is a standard USB class of functionality and interface. A USB host such as a PC or Macintosh will recognize any attached USB device that supports a HID interface and makes it available to the application layers of the operating system via a set of programming interfaces. A common application of a HID interface is a USB mouse or joystick.

HID Report

[0024] A single unit of data that is used to send data to the HID interface of the media player or from the media player to the host. MPAP packets are broken into HID reports before being sent across the transport link and are reassembled on the receiving side.

MPUI

[0025] Media player USB Interface. This is a configuration of the media player when attached as a device over USB. This configuration allows the media player to be controlled using MPAP, using a USB Human Interface Device (HID) interface as a transport mechanism.

Lingo

[0026] The command category used by a device. There is a general lingo that must be supported by all devices. Other lingoes are designed for use by specific devices.

Link

[0027] The logical connection between an external device and the media player via serial port or other physical connection.

[0028] The present invention relates generally to media players and more particularly to a connector interface system for such 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.

Connector Interface System Overview

[0029] 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

[0030] 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 keys are separated by one length are at the bottom and another set of keys are separated by another length at the top of the connector. The use of this key arrangement prevents noncompliant connectors from being plugged in and potentially causing damage to the device. The connector for power utilizes a Firewire specification for power. 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.

[0031] 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 systems and devices can interface with the multi-communication device.

Remote Connector

[0032] The connection interface system also includes a remote connector which provides for the ability to output audio and, input audio, provides I/O serial protocol, and an output video. 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, or video cables could be utilized with the remote connector.

[0033] 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 protocol in accordance with the present invention.

Docking and Remote Connector Specifications

[0034] For an example of the connector pin designations for both the docking connector and the remote connector for a multi-communication device such as a media player 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

[0035] FIG. 4A illustrates a typical FireWire connector interface for the docking connector. FireWire Power has the following characteristics: 8V-30V DC IN, 10 W Max. FireWire communication is designed to IEEE 1394 A Spec (400 Mb/s).

USB Interface

[0036] 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 herein, using a USB Human Interface Device (HID) interface as a transport mechanism.

Accessory 3.3 V Power

[0037] FIG. 4B illustrates the USB connector interface. 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. A maximum current is shared between the 30-pin and Audio/Remote connectors.

[0038] 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 5 mA current.

[0039] Accessory power is switched off for a period of, for example, approximately 2 seconds during the media player bootstrap process. This is done to ensure that accessories are in a known state and can be properly detected. All accessories are responsible for re-identifying themselves after the media player completes the bootstrap process and transitions accessory power from the off to the on state.

[0040] Accessory power is grounded through the DGND pins.

[0041] FIG. 4C illustrates a reference schematic diagram for accessory detect and identify system for detecting and identifying accessories for the docking connector. The system comprises a resistor to ground that allows the device to determine what has been plugged into docking connector. There is an internal pullup on Accessory Identify. Two pins are required (Accessory Identify & Accessory Detect)

[0042] FIG. 4D is a reference schematic of an electret microphone that is within the remote connector.

[0043] Serial Protocol Communication is provided using two pins to communicate to and from device (Rx & Tx). Input and Output levels are 0V=Low, 3.3V=High.

Media Player Accessory Protocol (MPAP)

[0044] 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 docking stations, chargers, car stereos, microphones, home stereos, computers, speakers, and devices which communicate wirelessly with other devices.

[0045] Accordingly a single media player must be able to communicate with different devices having varying functionality. To allow for this communication to be handled efficiently in a system and method in accordance with the present invention, a protocol is provided. As part of the connector interface system and in conjunction with the connectors, the protocol allows for the media player to identify the type of accessory that the media player is connected to and also allows the media player to identify the functionality of the accessory. In so doing the media player can efficiently and effectively interact with the accessory in the appropriate manner.

[0046] The Media Player Accessory Protocol (MPAP) allows the media player to communicate with a functional range of external devices. The protocol can be broken into three logical components: the protocol transport link, the protocol core, and the individual accessory lingoes. Devices can use USB and UART serial interfaces as channels to transfer MPAP packets. The protocol core describes the components necessary for communication with all external devices. It includes the basic packet definition and the general lingo, which allows for accessory identification, authentication, and retrieval of media player information. The accessory lingoes comprise the individual dialect commands. Each accessory lingo corresponds to a functional class of external devices.

[0047] Every external device must support a protocol transport link, the protocol core, and one or more lingoes, as required for its function. For example, the media player standard in-line remote control is a UART serial device that uses the general lingo and the simple remote lingo. To describe these features in more detail refer now to the following.

Protocol Transport Links

[0048] Accessories may communicate with the media player, using MPAP over the serial port link or the USB port link. Those links are described below.

UART Serial Port Link

[0049] Accessories using the Media Player Accessory Protocol (MPAP) over the UART serial port link use two pins, RX and TX, to communicate to and from the media player.

[0050] A device coupled to the docking connector allows for a standard serial protocol to be utilized. Attaching a serial dock accessory makes any top-attached (remote connector) accessories inactive.

[0051] The MPAP builds upon an existing serial specification such as the RS-232 serial specification. However, the signaling levels are non-standard. The RS-232 specification states that a mark is −7V and a space is +7V. In MPAP protocol, for example, a mark may be 2.85 V through 3.465 V and a space is 0 V through 0.9 V.

USB Port Link

[0052] The media player, for example, may be a USB 2.0-compliant device that supports two mutually exclusive modes of operation:

[0053] Mass storage device. This is the default configuration when attached to a typical USB host such as a PC or Macintosh. This mode is used for synching music and content, transferring files, and so forth.

[0054] MPAP enabled device. This is the configuration needed to support MPAP using the Media Player USB Interface (MPUI). This mode must be selected by the USB host before it can be used.

[0055] These two mutually exclusive modes of operation are each represented by a USB configuration. When the media player is attached to USB, the USB host (the accessory) must select one of the configurations and set it as the active configuration during the bus initialization.

Accessory Identify Resistor and MPUI

[0056] There are two types of media player accessories: serial accessories that communicate with the media player using MPAP and resistor-based accessories that need access to specific media player behaviors.

[0057] Resistor-based accessories use an Accessory Identify resistor (RID) to get access to a specific media player behavior. These devices tend to be simple accessories, such as battery packs and car chargers, and have one specific purpose. When attached, these accessories unlock media player features based on the RID used. Accessories that communicate with the media player using MPAP are serial accessories. Serial-based accessories may use the other R_IDvalues if they are to be utilized for unlocking a particular resistor-based behavior.

[0058] The presence of a R_IDof one resistance value on USB attachment triggers the media player to present the MPUI configuration as the first, or default, configuration. The second configuration becomes media player as a Mass Storage class disk device.

[0059] For instance, connecting a media player to a standard host, such as a PC or a Macintosh, along with the R_IDcauses the media player to be set up as a HID device (the HID interface being a component of the MPUI configuration) and not as a disk device. With no resistor, the media player is set up as a disk device.

[0060] It is possible to create an accessory that supports both MPAP over USB and the older UART serial-only media players using the same connector.

Media Player USB Interface (MPUI) Configuration

[0061] The MPUI configuration allows the media player to communicate using MPAP over USB. The USB Human Interface Device (HID) interface is the transport link and uses two endpoints for communication: the control endpoint is used for OUT data, while the HID interrupt endpoint is used for IN data.

[0062] The media player HID interface utilizes several vendor-specific HID reports, some of which are used to transport data from the host and some of which are used to transport data to the host. The HID report sizes range from a few bytes to several hundred KB and each one has a unique identifier. In order to send data to the media player, a host chooses one or more appropriately-sized HID reports in which to embed the MPAP packet and sends this to the media player HID interface with USB Set-Report command. The media player reassembles the MPAP packed and processes it. The process is repeated in reverse when the media player sends responses or MPAP packets to the host.

HID as a Transport

[0063] As mentioned earlier, the HID interface breaks MPAP packets up into a stream of vendor-specific HID reports and transports them across USB in either direction. To help manage this, it breaks this stream up into logical sets of reports, where a set of reports encompasses one or more complete MPAP packets. For instance, a set could be a single HID report containing one MPAP packet or a set of HID reports containing a total of 3 MPAP packets.

[0064] The HID Report ID indicates the type of report and implies the size of the report. Every report of a given type is the same size. The media player specifies several different report types. The USB host should analyze the HID report descriptor of the media player at runtime to determine which Report ID corresponds to the most appropriate report type for each transfer.

[0065] A representative group of lingoes for the media player are listed below.

Lingo Specifications

Lingo

General

Microphone

Simple Remote

Display Remote

Extended Interface

RF transmitter

[0066] The general lingo is shared for housekeeping commands across all devices. In addition to the general lingo, an accessory will implement a function specific lingo. The microphone lingo is used by the remote connector on the multi-communication device. The simple remote lingo is used by a standard in-line remote control. The display remote lingo is reserved for a device with similar functionality to the standard remote but with a display for status. The RF transmitter lingo is used for devices that transmit the device analog audio over radio frequencies. To describe the lingoes in more detail, refer now to the following discussion in conjunction with the accompanying figures.

General Lingo Command Summary

[0067] Table 1 provides a summary of all commands in the general lingo, including whether or not device authentication is required for use of the command.

[0068]

	TABLE 1

		Authentication
	Command	Required

	Request Identify	No
	RequestMediaPlayerName	No
	RequestMediaPlayerSoftwareVersion	No
	RequestMediaPlayerSerialNum	No
	RequestMediaPlayerModelNum	No
	RequestLingoProtocolVersion	No
	Identify	No
	IdentifyAccessoryLingoes	No
	ACK	No
	AckDevAuthenticationInfo	No
	AckDevAuthenticationStatus	No
	AckMediaPlayerAuthenticationInfo	No
	AckMediaPlayerAuthenticationStatus	N/A
	ReturnMediaPlayerName	No
	ReturnMediaPlayerSoftwareVersion	No
	ReturnMediaPlayerSerialNumber	No
	ReturnLingoProtocolVersion	No
	RetDevAuthenticationInfo	No
	RetDevAuthenticationSignature	No
	RetMediaPlayerAuthenticationInfo	No
	RetMediaPlayerAuthenticationSignature	No
	GetDevAuthenticationInfo	No
	GetDevAuthenticationSignature	No
	GetMediaPlayerAuthenticationInfo	No
	GetMediaPlayerAuthenticationSignature	No
	NotifyMediaPlayerStateChange	No

[0069] To identify itself, an accessory should send either an Identify command or an IdentifyAccessoryLingoes command. Accessory devices that support more than one lingo, not including the general lingo, should use the IdentifyAccessoryLingoes command.

[0070] The media player may send a RequestIdentify command to the device to ask to re-identify itself.

[0071] The remaining general lingo commands can be used to obtain general information from the media player. These commands allow the device to request the name, serial number, model number, and software version number of the media player. The RequestLingoProtocolVersion command allows a device to query the media player for the lingo protocol versions of all supported lingoes on the media player. The ACK command is used by the media player to report command error conditions and has an ACK pending feature to notify the requesting device how long to wait for responses to certain commands.

[0072] An accessory may send a RequestLingoProtocolVersion command, to determine which features the connected media player supports. If the media player does not respond to the RequestLingoProtocolVersion command, the device should try the command once more. If no response is received the second time, the device should assume that the connected media player supports the only RequestIdentify and Identify General Lingo commands.

[0073] FIG. 6 shows the sequence of the events that can be used to test for the full set of general lingo commands. As is seen, first a sync byte is sent to wake up the media player, then allow the media player allowed to wake from sleep. If the media player returns the ReturnLingoProtocolVersion command, then the general lingo version information can be used to check the commands supported by the media player, Next, wait for return packet and the device should retry the command if there is no reply to the first command send. If the ReturnLingoProtocolVersion command is not received during the retry, the device should assume that the connected media player supports only the RequestIdentify and Identify commands. This assumes the accessory device is connected and has already been through the identification process.

General Lingo Command Details

[0074] This section describes the general lingo commands and their packet formats.

[0075] Request Identify Command

[0076] Direction: media player→accessory

[0077] The media player sends this command to prompt accessories to re-identify themselves. If an accessory receives this command, it should respond with either the IdentifyAccessoryLingoes command or the Identify command. Accessories that require authentication or use the USB transport link, or support multiple lingoes should respond using the IdentifyAccessoryLingoes command.

[0078] Identify Command

[0079] Direction: accessory→media player

[0080] The accessory must send this command to notify the media player that an accessory has been attached and to register the lingo it supports. Accessories should identify at boot time and any time they receive a RequestIdentify command from the media player.

[0081] The Identify command has facilities for RF Transmitter devices to draw more than a predetermined amount of power (such as 4 mA) from the media player.

ACK Command

[0082] Direction: media player→accessory

[0083] The media player sends the ACK command to notify the device of command completion status and errors.

[0084] RequestMediaPlayerSoftware Version Command

[0085] Direction: media player→accessory

[0086] Retrieves the software version for the media player. The media player responds with a ReturnMediaPlayerSoftwareVersion command containing the major, minor, and revision version numbers.

[0087] ReturnMediaPlayerSoftware Version Command

[0088] Direction: media player→accessory

[0089] The media player sends this command in response to the RequestMediaPlayerSoftwareVersion command message from the accessory. The media player returns each version number as an individual byte, with the major version number sent first.

RequestMediaPlayerName Command

[0090] Direction: accessory→media player

[0091] Retrieves the name of the media player. The media player responds with a ReturnMediaPlayerName command containing the name of the media player.

[0092] ReturnMediaPlayerName Command

[0093] Direction: media player→accessory

[0094] The media player sends this command in response to the RequestMediaPlayerName command message from the accessory.

RequestMediaPlayerSerialNum Command

[0095] Direction: accessory→media player

[0096] Retrieves the serial number string of the media player. The media player responds with a ReturnMediaPlayerSerialNumber command containing the serial number.

[0097] ReturnMediaPlayerSerialNum Command

[0098] Direction: media player→accessory

[0099] The media player sends this command in response to the RequestMediaPlayerSerialNumber command message from the accessory.

[0100] RequestMediaPlayerModelNum Command

[0101] Direction: accessory→media player

[0102] Retrieves information for the media player. The media player responds with a ReturnMediaPlayerModelNum command containing the model number of the media player.

[0103] ReturnMediaPlayerModelNum Command

[0104] Direction: media player→accessory

[0105] The media player sends this command in response to the RequestMediaPlayerModelNum command message from the accessory.

[0106] IdentifyAccessoryLingoes Command

[0107] Direction: accessory→media player

[0108] The accessory sends this command to signal its presence and to identify its supported lingoes. In response, the media player sends an ACK command. The IdentifyAccessoryLingoes command is used by multi-lingo accessories to report all supported lingoes and should be used in place of the Identify command.

[0109] GetDevAuthenticationInfo Command

[0110] Direction: media player→accessory

[0111] The media player sends this command to obtain authentication information from the accessory. The command is sent if and only if the accessory has indicated that it supports authentication in its IdentifyAccessoryLingoes Options bits and has passed a valid, non-zero accessory ID. In response, the accessory sends a RetDevAuthenticationInfo command.

[0112] RetDevAuthenticationInfo Command

[0113] Direction: accessory→media player

[0114] The accessory indicates the MPAP authentication version that it supports by returning this command in response to a GetDevAuthenticationInfo command from the media player.

[0115] AckDevAuthenticationInfo Command

[0116] Direction: media player→accessory

[0117] The media player sends this command in response to RetDevAuthenticationInfo command. It indicates the current state of the accessory authentication information.

[0118] RequestLingoProtocolVersion Command

[0119] Direction: accessory→media player

[0120] Retrieves version information for any of the lingoes supported by the media player.

[0121] The media player responds with a ReturnLingoProtocolVersion command containing the major and minor version information of the requested media player lingo.

ReturnLingoProtocolVersion Command

[0122] Direction: media player→accessory

[0123] The media player sends this command in response to the RequestLingoProtocolVersion command message from the accessory. The major and minor version information for the requested lingo are returned.

[0124] GetDevAuthenticationSignature Command

[0125] Direction: media player→accessory

[0126] The media player sends this command to authenticate a accessory that has identified itself as requiring authentication. Authentication occurs either immediately upon identification or when the accessory attempts to use a restricted lingo or command. The accessory calculates its digital signature based on the challenge offered by the media player and sends the results back to the media player using a RetDevAuthenticationSignature command.

[0127] If the returned signature cannot be verified, the media player responds with a non-zero AckDevAuthenticationStatus command, followed immediately by another GetDevAuthenticationSignature command.

[0128] RetDevAuthenticationSignature Command

[0129] Direction: accessory→media player

[0130] The accessory sends this command to the media player in response to GetDevAuthenticationSignature command. The media player verifies the digital signature, calculated by the accessory based on the offered challenge. If verification passes, the media player authenticates the accessory and updates its lingo and command access permissions accordingly. The authentication status is sent to the accessory using AckDevAuthenticationStatus command.

[0131] AckDevAuthenticationStatus Command

[0132] Direction: media player→accessory

[0133] The media player sends this command to the accessory in response to the RetDevAuthenticationSignature command. It indicates the current accessory authentication state. If the accessory receives a non-zero status, the accessory has failed authentication and will only be able to use unauthenticated lingo commands.

[0134] If the accessory receives a zero status, the media player has successfully authenticated the accessory. The accessory may then use the requested authenticated lingoes and commands. Optionally, the accessory may begin the process of authenticating the media player, by sending a GetMediaPlayerAuthentication command.

[0135] GetMediaPlayerAuthenticationSignature Command

[0136] Direction: accessory→media player

[0137] The accessory uses this command to send an offered challenge to the media player for digital signature. In response, the media player returns its signed challenge to the accessory using RetMediaPlayerAuthenticationSignature command. Accessories should implement the authentication retry feature described in GetDevAuthenticationSignature command.

[0138] RetMediaPlayerAuthenticationSignature Command

[0139] Direction: media player→accessory

[0140] The media player sends this command to the accessory in response to a Get MediaPlayerAuthenticationSignature command. The accessory verifies the digital signature, calculated by the media player based on the offered challenge, and, if verification passes, authenticates the media player. The accessory sends the authentication status to the media player.

[0141] AckMediaPlayerAuthenticationStatus Command

[0142] Direction: accessory→media player

[0143] The accessory sends this command to the media player in response to RetMediaPlayerAuthenticationSignature command. It indicates the current media player authentication state. The accessory should return a non-zero ACK for each failed authentication attempt.

GetMediaPlayerAuthenticationInfo Command

[0144] Direction: accessory→media player

[0145] The accessory sends this command to obtain authentication information from the media player. The media player should send this command only if the accessory has indicated that it supports authentication in its IdentifyAccessoryLingoes command options bits and the media player has successfully completed the authentication process. In response, the media player sends RetMediaPlayerAuthenticationInfo command.

[0146] AckMediaPlayerAuthenticationInfo Command

[0147] Direction: accessory→media player

[0148] The accessory sends this command to the media player in response to RetMediaPlayerAuthenticationInfo command. It indicates the current state of the media player information version. If the accessory sends a non-zero status, it indicates that it will not be able to authenticate the media player due to a protocol version or authentication index mismatch.

[0149] NotifyMediaPlayerStateChange Command

[0150] Direction: media player→accessory

[0151] The media player sends this notification command when the media player state is about to change to accessories that identify using IdentifyAccessoryLingoes command. If the accessory identifies using Identify command, this notification is not sent. The state change byte indicates the specific media player state transition. If the media player is switching from a power on state to a light sleep state, accessories must immediately reduce their power consumption below the maximum current such as 5 mA. When the media player has transitioned to a deep sleep or hibernate state, self-powered accessories are expected to automatically re-identify themselves when accessory power is restored.

Microphone Lingo Command

[0152] The microphone lingo enables combination microphone and speaker accessory devices to record and playback audio. Media player mass storage disk capacities enable the option of supporting a stereo input mode and higher audio sample rates. Media players may therefore be used for high-quality mobile audio recording.

[0153] When the media player detects a device speaking the microphone lingo, it may transition into a recorder application where it can create and manage recordings. Based on the microphone device capabilities, the media player recording application may choose to change its appearance based on the presence or absence of certain microphone features. The device should indicate its capabilities to the media player on request. These capabilities may include:

- [0154] Stereo line input source
- [0155] Stereo/mono control
- [0156] Recording level control
- [0157] Recording level limiter

[0158] Microphone accessories can draw power from the media player or supply power to the media player. Accessory device power management is important as media players transition to a smaller physical size at the same time as trying to extend battery life. As an accessory using the microphone lingo, the microphone accessory will be notified of media player state changes, such as transitioning to the power on, light sleep, hibernate, and deep sleep states. Accessory power is in low mode by default and is raised to high power mode only during recording and playback states.

[0159] The microphone accessory is responsible for keeping the power consumption below the maximum allowed limits for each media player state. Note that accessory power is completely shut off when the media player enters the hibernate and deep sleep states. When waking from a light sleep state, the microphone accessory is required to re-identify and re-authenticate itself, as with other accessories using authenticated lingoes or commands. On reset or power up, the accessory device should be in low power state (for example, consuming less than 5 mA) with the amplifier off (audio input and output disabled).

[0160] Microphone state information is typically retained locally by the accessory player while uninterrupted accessory power (either high or low power) is available. If accessory power is turned off, device state information may be lost. Accessories are not expected to retain state information across accessory power down cycles (hibernate or deep sleep modes).

[0161] Media player playback volume level changes may require the accessory to support display remote lingo functionality.

[0162] Table 2 lists the commands available as part of the microphone lingo.

[0163]

TABLE 2

		Authentication
Command	Connector	Required

BeginRecord	Audio/Remote	No
EndRecord	Audio/Remote	No
BeginPlayback	Audio/Remote	No
EndPlayback	Audio/Remote	No
ACK	30-pin	Yes
GetDevAck	30-pin	Yes
MediaPlayerModeChange	30-pin	Yes
GetDevCaps	30-pin	Yes
RetDevCaps	30-pin	Yes
GetDevCtrl	30-pin	Yes
RetDevCtrl	30-pin	Yes
SetDevCtrl	30-pin	Yes

[0164] BeginRecord Command

[0165] Direction: media player→accessory

[0166] The media player sends this command to notify the accessory that audio recording has started. The accessory does not return a packet to the media player in response to this command.

[0167] EndRecord Command

[0168] Direction: media player→accessory

[0169] The media player sends this command to notify the accessory that audio recording has ended. The accessory does not return a packet to the media player in response to this command.

[0170] BeginPlayback Command

[0171] Direction: media player→accessory

[0172] The media player sends this command to notify the accessory that audio playback has started. The accessory does not return a packet to the media player in response to this command.

EndPlayback Command

[0173] Direction: media player→accessory

[0174] The media player sends this command to notify the accessory that audio playback has ended. The accessory does not return a packet to the media player in response to this command.

[0175] ACK Command

[0176] Direction: accessory→media player

[0177] The microphone accessory sends this command in response to a command sent from the media player. Note that some commands do not require an ACK response. The accessory sends an ACK response when a command that does not return any data has completed, a bad parameter is received, or an unsupported or invalid command is received.

[0178] GetDevAck Command

[0179] Direction: media player→accessory

[0180] The media player sends this command to get an ACK response from a microphone accessory. The media player uses this command to “ping” the accessory and determine that it is present and ready to accept commands. In response, the accessory sends the ACK command with command status OK.

[0181] MediaPlayerModeChange Command

[0182] Direction: media player→accessory

[0183] The media player sends this command to the microphone accessory when an audio recording or playback event occurs. The microphone accessory uses the MediaPlayerModeChange command to configure its inputs or outputs and power consumption level for the specified mode. In response, the accessory sends the ACK command with the command status OK. The accessory sends the ACK command when the accessory has completed its mode change.

GetDevCaps Command

[0184] Direction: media player→accessory

[0185] The media player sends this command to the microphone accessory to determine the features present on the accessory. In response, the accessory sends RetDevCaps command with the payload indicating the capabilities it supports.

[0186] RetDevCaps Command

[0187] Direction: accessory→media player

[0188] The accessory sends this command in response to the command GetDevCaps command sent by the media player. The microphone accessory returns the payload indicating which capabilities it supports.

GetDevCtrl Command

[0189] Direction: media player→accessory

[0190] The media player sends this command to get the accessory control state for the specified control type. In response, the accessory sends RetDevCtrl command with its current control state. If this command is not supported by the accessory—that is, if the microphone does not have any configurable controls—it should return an ACK command with a bad parameter error status.

[0191] RetDevCtrl Command

[0192] Direction: accessory→media player

[0193] The accessory sends this command in response to the command GetDevCtrl command received from the media player. The accessory returns the current control state for the specified control type. Control types are only supported if the associated capabilities bits are set in the command RetDevCaps command.

[0194] SetDevCtrl Command

[0195] Direction: media player→accessory

[0196] The media player sends this command to set the accessory control state for the specified control type. In response, the accessory sends the ACK command with the command status. If this command is not supported by the accessory—that is, if the microphone does not have any configurable controls—it should return an ACK command with a bad parameter error status.

Simple Remote Lingo

[0197] A simple remote accessory sends a buttons status command to indicate an updated status of which buttons are held down. The data of the packet is a number of bytes indicating which buttons are currently held down. In one embodiment, the bytes are made up by ORing the masks of the buttons together. The accessory will send a command to indicate all buttons are released. While any buttons are held down the accessory should repeat this packet on a predetermined interval. If no packet of this sort is received by the host for a predetermined time period, the host may assume a packet was lost and go to “all buttons up” mode.

[0198] When the user presses and holds down a button, a simple remote accessory should generate the button status packet immediately and repeat it for as long as the button is pressed. If a second button is pressed while the first button is down, the button status packet sent by the accessory should include status for both buttons, and this packet should be repeated for as long as both buttons are held down. Table 3 lists the possible media player button states.

Simple Remote Button Map

[0199]

	TABLE 3

	Button	Number


	Play/Pause	0
	Volume Up	1
	Volume Down	2
	Next Track	3
	Previous Track	4
	Next Album	5
	Previous Album	6
	Stop	7
	Play/Resume	8
	Pause	9
	Mute toggle	10
	Next Chapter	11
	Previous Chapter	12
	Next Playlist	13
	Previous Playlist	14
	Shuffle setting advance	15
	Repeat setting advance	16
	Power On	17
	Power Off	18
	Backlight for 30 seconds	19
	Begin FF	20
	Begin REW	21
	Menu	22
	Select	23
	Up Arrow	24
	Down Arrow	25

[0200] Some media player button states are interpreted differently by the media player when pressed and held down. These are as follows:

- [0201] The Next Track button is treated as a Scan Forward button when pressed and held while a track is playing.
- [0202] The Previous Track button is treated as a Scan Backward button when pressed and held while a track is playing.
- [0203] The Play/Pause button is treated as a Power Off button when pressed and held.
- [0204] The Menu button is treated as a Display Backlight On/Off button when pressed and held.
- [0205] If the media player is in Browse mode, the Select button is treated as an Add Track to On-The-Go Playlist button when pressed and held.

[0206] Repeated Next Track and Previous Track commands (see Table 3) without an intervening button status packet indicating all buttons are up, are interpreted as Fast Forward and Rewind commands. For a locking Fast Forward or Rewind button, use the Begin Fast Forward or Begin Rewind commands to start the operation and a Play/Resume command to return to the play state.

[0207] The Next and Previous Album commands (see Table 3) have no effect if there is no next or previous album to go in to the Now Playing list.

[0208] Below is the command for the simple remote lingo.

[0209] ContextButtonStatus Command

[0210] Direction: Accessory→media player

[0211] The accessory sends this command to the media player when a button event occurs. When all buttons are released, the accessory should send a button status packet with a 0x0 payload to indicate that no buttons are pressed. The media player does not return a packet to the accessory in response to this command.

Display Remote Lingo

[0212] The display remote lingo is for accessories that need to control the state of the media player, recreate a portion of the media player UI on a remote display, or control the state of the media player equalizer (EQ). The display remote protocol can be used by simple inline-display remotes (remotes that have single-line display and play control buttons) and more complex accessories that have full multi-line graphical displays to show information about the track, artist, or album; current play or pause state; track position; battery; shuffle and time. By supporting multiple lingoes, an accessory can use the display remote lingo in combination with other lingoes to create a fully functional product. Accessories can also use this lingo to control the state of the media player equalizer. The display remote lingo supports serial accessories attached to the Audio/Remote or 30-pin connector.

[0213] The display remote command set uses a single byte command format similar to the general and simple remote lingoes. Accessories using the display remote lingo can identify using the general lingo, with either the identify single lingo or IdentifyAccessoryLingoes multiple lingo commands.

[0214] Table 4 illustrates the commands for the display remote lingo.

[0215]

TABLE 4

Command


	ACK
	GetCurrentEQProfileIndex
	RetCurrentEQProfileIndex
	SetCurrentEQProfileIndex
	GetNumEQProfiles
	RetNumEQProfiles
	GetIndexedEQProfileName
	RetIndexedEQProfileName
	SetRemoteEventNotification
	RemoteEventNotification
	GetRemoteEventStatus
	RetRemoteEventStatus
	GetMediaPlayerStateInfo
	RetMediaPlayerStateInfo
	SetMediaPlayerStateInfo
	GetPlayStatus
	RetPlayStatus
	SetCurrentPlayingTrack
	GetIndexedPlayingTrackInfo
	RetIndexedPlayingTrackInfo
	GetNumPlayingTracks
	RetNumPlayingTracks
	GetPowerBatteryState
	RetPowerBatteryState
	GetSoundCheckState
	RetSoundCheckState
	SetSoundCheckState

[0216] The commands, their direction and their functions are described in detail hereinbelow.

[0217] ACK Command

[0218] Direction: media player→accessory

[0219] The media player sends this command to acknowledge the receipt of a command from the accessory and return the command status. The command ID field indicates the accessory command for which the response is being sent. The command status indicates the result of the command (success or failure).

GetCurrentEQProfileIndex Command

[0220] Direction: accessory→media player

[0221] Requests the current equalizer (EQ) profile setting index. In response, the media player sends the RetCurrentEQProfileIndex command packet.

[0222] RetCurrentEQProfileIndex Command

[0223] Direction: media device→accessory

[0224] The media accessory sends this command, returning the current equalizer profile setting index, in response to the GetCurrentEQProfileIndex command packet sent by the accessory.

[0225] SetCurrentEQProfileIndex Command

[0226] Direction: accessory→media player

[0227] Set the current equalizer profile setting index and optionally restores the original equalizer setting on accessory detach. The valid equalizer index range can be determined by sending a GetNumEQProfiles command. In response to this command, the media player returns an ACK packet with the status of this command.

[0228] GetNumEQProfiles Command

[0229] Direction: accessory→media player

[0230] Requests the number of media player equalizer profile settings. In response, the media player sends the RetNumEQProfiles command packet.

[0231] RetNumEQProfiles Command

[0232] Direction: media player→accessory

[0233] Returns the number of equalizer profiles. The media player sends this command in response to the GetNumEQProfiles command packet sent by the accessory.

[0234] GetIndexedEQProfileName Command

[0235] Direction: accessory→media player Requests the media player equalizer profile setting name for a given equalizer profile index. In response, the media player sends the RetIndexedEQProfileName command packet. The valid profile index range can be obtained by sending the GetNumEQProfiles command.

[0236] RetIndexedEQProfileName Command

[0237] Direction: media player→accessory

[0238] Returns the media player equalizer profile setting name for the specified equalizer profile index in response to the GetIndexedEQProfileName command.

[0239] SetRemoteEventNotification Command

[0240] Direction: accessory→media player

[0241] Enables asynchronous remote event notification for media player events. On accessory detach, event notification is reset to the default disabled state.

[0242] RemoteEventNotification Command

[0243] Direction: media player→accessory

[0244] The media player sends this command asynchronously whenever an enabled event change has occurred. Use the SetRemoteEventNotification command to control which events are enabled.

[0245] GetRemoteEventStatus Command

[0246] Direction: accessory→media player

[0247] Gets the status of state information that has changed on the media player. In response, the media player sends a RetRemoteEventStatus command, containing a bitmask of event states that changed since the last GetRemoteEventStatus command and clears all the remote event status bits. This command may be used to poll the media player for event changes without enabling asynchronous remote event notification.

[0248] RetRemoteEventStatus Command

[0249] Description: media player→accessory

[0250] The media player sends this command in response to the GetRemoteEventStatus command.

[0251] GetMediaPlayerStateInfo Command

[0252] Direction: accessory→media player

[0253] Obtains media player state information. In response, the media player sends a RetMediaPlayerStateInfo command with the requested state information.

[0254] RetMediaPlayerStateInfo Command

[0255] Direction: media player→accessory

[0256] The media player sends this command in response to the GetMediaPlayerStateInfo command.

[0257] SetMediaPlayerStateInfo Command

[0258] Direction: accessory→media player

[0259] Set the media player state. The information type specifies the type of information to update. In response, the media player sends an ACK command with the results of the operation.

[0260] GetPlayStatus Command

[0261] Direction: accessory→media player

[0262] Gets the current media player play status information. In response, the media player sends a RetPlayStatus command with the current play state, track index, track position, and track length.

[0263] RetPlayStatus Command

[0264] Direction: media player→accessory

[0265] The media player sends this command in response to the GetPlayStatus command and returns the current media player play status information.

[0266] SetCurrentPlayingTrack Command

[0267] Direction: accessory→media player

[0268] Sets the currently playing track to the track at the specified index. The total number of playing tracks can be obtained by sending a GetNumPlayingTracks command.

[0269] GetIndexedPlaying TrackInfo Command

[0270] Direction: accessory→media player

[0271] Gets track information for the specified playing track index. The infoType field specifies the type of information to be returned, such as track title, artist title, artist name, album name, track genre, and track chapter information. In response, the media player sends a RetIndexedPlayingTrackInfo command with the requested track information.

[0272] RetIndexedPlayingTrackInfo Command

[0273] Direction: media player→accessory

[0274] The media player sends this command in response to the GetIndexedPlayingTrackInfo command. It returns the requested type of information and data for the specified playing track.

[0275] RetNumPlayingTracks Command

[0276] Direction: media player→accessory

[0277] The media player sends this command in response to the GetNumPlayingTracks command received from the accessory. It returns the total number of tracks queued in the playback engine.

[0278] GetPowerBatteryState Command

[0279] Direction: accessory→media player

[0280] Gets the power and battery level state of the media player. In response, the media player sends a RetPowerBatteryState command with the power and battery information.

[0281] RetPowerBatteryState Command

[0282] Direction: media player→accessory

[0283] The media player sends this command in response to the GetPowerBatteryState command and returns the current media player power state and battery level.

[0284] GetSoundCheckState Command

[0285] Direction: accessory→media player

[0286] Gets the current sound check setting. When enabled, sound check adjusts track playback volume to the same level. In response, the media player sends a RetSoundCheckState command with the current sound check state.

[0287] RetSoundCheckState Command

[0288] Direction: media player→accessory

[0289] The media player sends this command in response to the GetSoundCheckState command and returns the current state of the sound check setting.

[0290] SetSoundCheckState Command

[0291] Direction: accessory→media player

[0292] Sets the state of the sound check setting and optionally saves the previous sound check state to be restored on accessory detach. In response to this command, the media player sends an ACK packet with the status of the command.

Extended Interface Lingo Specification

Operating Modes

[0293] The media player can be considered to operate in two major modes, standard UI mode and extended Interface mode.

Standard UI Mode

[0294] This is the standard user interface mode and allows the media player to be driven by its front panel display and buttons.

Extended Interface Mode

[0295] The media player transitions into the Extended Interface mode when either of the following occurs:

[0296] (1)—A single-lingo accessory is connected to the media player and issues the Identify command, specifying the Extended Interface lingo as its supported lingo.

[0297] (2)—A multi-lingo accessory is connected to the media player and issues a General Lingo Command EnterRemoteUIMode command.

[0298] If the media player is playing a track during this transition, the playback is automatically paused.

[0299] The extended interface protocol allows accessories to replace the graphic with a downloaded image set through a SetDisplayImage command. Removing power from the media player while a connection remains results in the media player going into a light sleep state after a predetermined amount of inactivity. The controls of the media player are disabled when in extended interface mode.

[0300] The media player transitions back to standard UI mode when any of the following occurs:

[0301] (1)—The accessory is disconnected from the media player.

[0302] (2)—A multi-lingo accessory issues the General Lingo Command: ExitRemoteUIMode.

[0303] The accessory re-identifies itself, using either of the general lingo commands Identify or IdentifyAccessoryLingoes.

[0304] If the media player is playing a track during this transition, the playback is automatically paused. Any media player settings with the restore on exit feature state are restored when the media player is disconnected.

Light Sleep State

[0305] The media player screen, playback, and most major parts of the media player are off while the media player is in the light sleep state. The media player transitions from extended interface mode to the light sleep state when power is detached and playback is idle. A period of inactivity is required before the media player transitions into the light sleep state. When power is restored, the media player returns to the extended interface mode.

[0306] A media player will not sleep while it remains attached to an active USB host. The USB host must switch off its host controller to force a media player in extended interface mode into the light sleep state. If the media player is not currently in extended interface mode, playback must be paused before the host controller is turned off. In extended interface mode, there is no need to pause media playback before turning off the host controller because this action generates a disconnect event that causes the media player to exit the extended interface mode and allows the media player to transition into the light sleep state. Attaching USB power to a media player in light sleep state will wake it up.

Switching Between Standard UI and Extended Interface Modes

[0307] There are four general lingo commands that allow accessories to determine what mode the media player is in and to switch between the two major modes, Standard UI and Extended Interface. These commands were implemented to allow a device to switch between modes without having to unplug the accessory. Multi-lingo accessories must use these commands to switch into and out of the extended interface mode.

[0308] Table 5 lists the general lingo command codes for querying, entering, and exiting the extended interface protocol.

[0309]

TABLE 5

	Requires
	authentication	Requires
General Lingo	UART serial port	authentication
command	link	USB port link

RequestRemoteUIMode	No	Yes
ReturnRemoteUIMode	No	Yes
EnterRemoteUIMode	No	Yes
ExitRemoteUIMode	No	Yes

[0310] RequestRemoteUIMode Command

[0311] Direction: accessory→media player Requests the Extended Interface mode from the media player. The media player responds with a ReturnRemoteUIMode command.

[0312] ReturnRemoteUIMode Command

[0313] Direction: media player→accessory

[0314] Returns the current operating mode of the media player UI

[0315] EnterRemoteUIMode Command

[0316] Direction: accessory→media player

[0317] The accessory sends this command to the media player to force it to enter the Extended Interface mode. If the media player is already in the extended interface mode, it immediately returns a general lingo ACK command packet, notifying the user that the command was successful.

[0318] ExitRemoteUIMode Command

[0319] Direction: accessory→media player

[0320] The accessory sends this command to the media player to force it to exit the Extended Interface mode. If the media player is already in the standard UI mode, it immediately returns a general lingo ACK command packet, notifying the user that the command was successful.

[0321] Using the Extended Interface Protocol

[0322] In order to effectively use the extended interface protocol, there are two logical entities that need to be managed while browsing and playing content: the content database engine and the playback engine. The following describes those engines and gives an example of command traffic between an extended interface accessory and a media player.

[0323] The Playback Engine

[0324] The playback engine is active when the media player is in a playback state, such as play, fast forward, and rewind. It has a special play list, called the Now Playing playlist, that is used to determine what track or content item will be played next. The PlayCurrentSelection command is used to transfer the currently selected database items to the Now Playing Playlist and start the player at a specified item within that list. Changes to the database selection before or after this PlayCurrentSelection command have no effect on the current playback.

[0325] The Database Engine

[0326] The database engine is always accessible when the unit is awake. It can be manipulated remotely and allows groups of content items to be selected, independently of the playback engine. This allows the user to listen to an existing track or playlist while checking the media player database for another selection. Once a different database selection is made, the user selection (the track or content playlist) is sent to the playback engine. The commands such as ResetDBSelection and GetNumberCategorizedDBRecords are examples of commands that are used to manipulate the Database Engine.

[0327] Database Category Hierarchies

[0328] The database engine uses categories to classify music and other records stored in the database. Possible categories are playlist, genre, artist, album, track, composer and audiobook. A list of records can be assembled, based on the various selected categories, to create a user list of records (a playlist).

[0329] The database categories have a hierarchy by which records are sorted and retrieved. This category hierarchy has an impact on the order in which records should be selected. For example, if a low category, such as album, is selected first, followed by a higher relative category such as genre, the album selection is invalidated and is ignored. When creating a new set of database selections, the accessory should begin by resetting all database selections, using the ResetDBSelection command, and selecting the desired database categories from highest to lowest relative category. A representation of the database hierarchy is shown in Table 6.

[0330]

	TABLE 6

	Category	Notes

	All (highest	This is the state after a ResetDBSelection
	level)	command. No database categories are
		selected. If the
		GetNumberCategorizedDBRecords
		command is sent while in this state, it
		returns the total number of records for the
		requested category.
	Playlist	When the SelectDBRecord command
		selects a playlist, all lower database
		category selections (genre, artist or
		composer, album, and track) are
		invalidated.
	Genre	When the SelectDBRecord command
		selects a genre, all lower database category
		selections (artist or composer, album, and
		track) are invalidated.
	Artist or	When the SelectDBRecord command
	Composer	selects an artist or composer, all album and
		track category selections are invalidated.
	Album	When the SelectDBRecord command
		selects an album, all track category
		selections are invalidated.
	Song/Audiobook	When the Select DBRecord command
	Track	selects a track, either a song or an
	(lowest level)	audiobook, it is automatically transferred
		from the Database Engine to the Playback
		Engine.

[0331] Extended Interface Mode Commands

[0332] Table 7 lists the command for the Extended Interface protocol.

[0333]

	TABLE 7

	Command	Target engine

	Acknowledge	N/A
	GetCurrentPlaying-	Playback Engine
	TrackChapterInfo
	GetCurrentPlaying-	Playback Engine
	TrackChapterInfo
	GetCurrentPlaying-	Playback Engine
	TrackChapterName
	GetAudiobookSpeed	N/A
	GetIndexedPlaying-	Playback Engine
	TrackInfo
	GetNumberCategorized-	Database Engine
	DBRecords
	GetPlayStatus	Playback Engine
	GetCurrentPlaying-	Playback Engine
	TrackIndex
	GetIndexedPlaying-	N/A
	TrackTitle
	GetIndexedPlaying-	Playback Engine
	TrackArtistName
	GetIndexedPlaying-	Playback Engine
	TrackAlbumName
	GetShuffle	N/A
	GetRepeat	N/A
	GetMonoDisplay-	N/A
	ImageLimits
	GetNumPlayingTracks	Playback Engine
	GetColorDisplay-	N/A
	ImageLimits
	ReturnCurrentPlaying-	Playback Engine
	TrackChapterInfo
	ReturnCurrentPlaying-	Playback Engine
	TrackChapterPlayStatus
	ReturnCurrentPlaying-	Playback Engine
	TrackChapterName
	ReturnAudiobookSpeed	N/A
	ReturnIndexedPlaying-	N/A
	TrackInfo
	ReturnProtocolVersion	N/A
	ReturnMediaPlayerName	N/A
	ReturnNumber-	N/A
	CategorizedDBRecords
	ReturnCategorized-	N/A
	DatabaseRecord
	ReturnPlayStatus	N/A
	ReturnCurrentPlaying-	N/A
	TrackIndex
	ReturnIndexedPlaying-	N/A
	TrackTitle
	ReturnIndexedPlaying-	N/A
	TrackArtistName
	ReturnIndexedPlaying-	N/A
	TrackAlbumName
	ReturnShuffle	N/A
	ReturnRepeat	N/A
	ReturnMonoDisplay-	N/A
	ImageLimits
	ReturnNumPlayingTracks	N/A
	ReturnColorDisplay-	N/A
	ImageLimits
	SetCurrentPlaying-Track	Playback Engine
	Chapter
	SetAudiobookSpeed	N/A
	SetPlayStatusChange-	Playback Engine
	Notification
	SetShuffle	N/A
	SetRepeat	N/A
	SetDisplayImage	N/A
	SetCurrentPlayingTrack	Playback Engine
	RequestProtocolVersion	N/A
	RequestMediaPlayerName	N/A
	ResetDBSelection	Database Engine
	RetrieveCategorized-	Database Engine
	DatabaseRecords
	PlayStatusChange-	N/A
	Notification
	PlayCurrentSelection	Database and Playback
		Engines. This command
		copies items from the
		database to the Playback
		Engine.
	PlayControl	Playback Engine
	SelectSortDBRecord	Database Engine

[0334] Each of these commands, their direction and function are described hereinbelow.

[0335] ACK Command

[0336] Direction: media player→accessory

[0337] The media player sends this telegram to acknowledge the receipt of a command and return the command status. The command ID field indicates the accessory command for which the response is being sent. The command status indicates the results of the command (success or failure).

[0338] GetCurrentPlayingTrackChapterInfo Command

[0339] Direction: accessory→media player

[0340] Applies to: playback engine

[0341] Requests the chapter information of the currently playing track. In response, the media player sends a ReturnCurrentPlayingTrackChapterInfo telegram to the accessory.

[0342] ReturnCurrentPlagingTrackChapterInfo Command

[0343] Direction: media player→accessory

[0344] Returns the chapter information of the currently playing track. The media player sends this telegram in response to the GetCurrentPlayingTrackChapterInfo telegram from the accessory. The chapter information includes the currently playing track's chapter index, as well as the total number of chapters.

[0345] SetCurrentPlayingTrackChapter Command

[0346] Direction: accessory→media player

[0347] Applies to: playback engine

[0348] Sets the currently playing track chapter. In response to the SetCurrentPlayingTrackChapter command, the media player sends an ACK telegram with the command status.

[0349] GetCurrentPlayingTrackChapterPlayStatus

[0350] Direction: accessory→media player

[0351] Applies to: playback engine

[0352] Requests the chapter playtime status of the currently playing track. In one embodiment the status includes the chapter length and the time elapsed within that chapter. In response to a valid telegram, the media player sends a ReturnCurrentPlayingTrackChapterPlayStatus telegram to the accessory.

[0353] ReturnCurrentPlayingTrackChapterPlayStatus Command

[0354] Direction: media player→accessory

[0355] Returns the play status of the currently playing track chapter. The media player sends this telegram in response to the GetCurrentPlayingTrackChapterPlayStatus telegram from the accessory.

[0356] GetCurrentPlayingTrackChapterName Command

[0357] Direction: accessory→media player

[0358] Applies to: playback engine

[0359] Requests a chapter name in the currently playing track. In response to a valid telegram, the media player sends a ReturnCurrentPlayingTrackChapterName telegram to the accessory.

[0360] ReturnCurrentPlayingTrackChapterName Command

[0361] Direction: media player→accessory

[0362] Returns a chapter name in the currently playing track. In response to a valid telegram, the media player sends a ReturnCurrentPlayingTrackChapterName telegram to the accessory.

[0363] ReturnCurrentPlayingTrackChapterName Command

[0364] Direction: media player accessory

[0365] Returns a chapter name in the currently playing track. The media player sends this telegram in response to a valid GetCurrentPlayingTrackChapterName telegram from the accessory.

[0366] GetAudiobookSpeed Command

[0367] Direction: accessory→media player

[0368] Requests the current media player audiobook speed state. The media player responds with the ReturnAudiobookSpeed telegram indicating the current audiobook speed.

[0369] ReturnAudiobookSpeed Command

[0370] Direction: mediaplayer→accessory

[0371] Returns the current audiobook speed setting. The media player sends this telegram in response to the GetAudiobookSpeed command from the accessory.

[0372] Table 8 shows the possible audiobook speed states returned by this command.

[0373]

	TABLE 8

	Value	Meaning

	0xFF	Slow (−1)
	0x00	Normal
	0x01	Fast (+1)
	0x02-0xFE	Reserved

[0374] SetAudiobookSpeed Command

[0375] Direction: accessory→media player

[0376] Sets the speed of audiobook playback. The media player audiobook speed states are listed in Table 8. This telegram has two modes: one to set the speed of the currently playing audiobook and a second to set the audiobook speed for all audiobooks.

[0377] GetIndexedPlayingTrackInfo Command

[0378] Direction: accessory→media player

[0379] Applies to: playback engine

[0380] Gets track information for the track at the specified index. The track info type field specifies the type of information to be returned, such as song lyrics, podcast name, episode date, and episode description. In response, the media player sends the ReturnIndexedPlayingTrackInfo command.

[0381] ReturnIndexedPlayingTrackInfo Command

[0382] Direction: media player→accessory

[0383] Returns the requested track information type and data. The media player sends this command in response to the GetIndexedPlayingTrackInfo command.

[0384] RequestProtocolVersion Command

[0385] Direction: accessory→media player

[0386] Requests the version of the running Extended Interface protocol from the media player. The media player responds with a ReturnProtocolVersion command.

[0387] ReturnProtocol Version Command

[0388] Direction: media player→accessory

[0389] Returns the media player Extended Interface protocol version number. The media player sends this command in response to the RequestProtocolVersion command from the accessory.

[0390] RequestMediaPlayerName Command

[0391] Direction: accessory→media player

[0392] Returns the name of the user's media player or “media player” if the media player name is undefined. This allows the media player name to be shown in the human-machine interface.

[0393] ReturnMediaPlayerName Command

[0394] Direction: media player→accessory

[0395] The media player sends this command in response to the RequestMediaPlayerName telegram from the accessory.

[0396] ResetDBSelection Command

[0397] Direction: accessory→media player

[0398] Applies to: database engine

[0399] Resets the current database selection to an empty state and invalidates the category entry count. That is, it sets the count to 0 for all categories except the playlist category.

[0400] SelectDBRecord Command

[0401] Direction: accessory→media player

[0402] Applies to: database engine. Selecting a single track automatically passes it to the playback engine.

[0403] Selects one or more records in the database engine, based on a category relative index.

[0404] GetNumberCategorizedDBRecords Command

[0405] Direction: accessory→media player

[0406] Applies to: database engine

[0407] Retrieves the number of records in a particular database category.

[0408] ReturnNumberCategorizedDBRecords Command

[0409] Direction: media player→accessory

[0410] Returns the number of database records matching the specified database category.

[0411] RetrieveCategorizedDatabaseRecords Command

[0412] Direction: accessory→media player

[0413] Applies to: database engine

[0414] Retrieves one or more database records from the media player, typically based on the results from the GetNumberCategorizedDBRecords command query.

[0415] ReturnCategorizedDatabaseRecord Command

[0416] Direction: media player→accessory

[0417] Contains information for a single database record.

[0418] GetPlayStatus Command

[0419] Direction: accessory→media player

[0420] Applies to: playback engine

[0421] Requests the current media player playback status, allowing the accessory to display feedback to the user.

[0422] ReturnPlayStatus Command

[0423] Direction: media player→accessory

[0424] Returns the current media player playback status.

[0425] GetCurrentPlayingTrackIndex Command

[0426] Direction: accessory→media player

[0427] Applies to: playback engine

[0428] Requests the playback engine index of the currently playing track.

[0429] ReturnCurrentPlayingTrackIndex Command

[0430] Direction: media player→accessory

[0431] Returns the playback engine index of the current playing track in response to the GetCurrentPlayingTrackIndex telegram from the accessory.

[0432] GetIndexedPlayingTrackTitle Command

[0433] Direction: accessory→media player

[0434] Applies to: playback engine

[0435] Requests the title name of the indexed playing track from the media player. In response to a valid telegram, the media player sends a ReturnIndexedPlayingTrackTitle telegram to the accessory.

[0436] ReturnIndexedPlayingTrackTitle Command

[0437] Direction: media player→accessory

[0438] Returns the title of the indexed playing track in response to a valid GetIndexedPlayingTrackTitle telegram from the accessory.

[0439] GetIndexedPlayingTrackArtistName Command

[0440] Direction: accessory→media player

[0441] Applies to: playback engine

[0442] Requests the name of the artist of the indexed playing track. In response to a valid telegram, the media player sends a ReturnIndexedPlayingTrackArtistName telegram to the accessory.

[0443] ReturnIndexedPlayingTrackArtistName Command

[0444] Direction: media player→accessory

[0445] Returns the artist name of the indexed playing track in response to a valid GetIndexedPlayingTrackArtistName telegram from the accessory.

[0446] GetIndexedPlayingTrackAlbumName Command

[0447] Direction: accessory→media player

[0448] Applies to: playback engine Requests the album name of the indexed playing track.

[0449] ReturnIndexedPlayingTrackAlbumName Command

[0450] Direction: media player→accessory

[0451] Returns the album name of the indexed playing track in response to a valid GetIndexedPlayingTrackAlbumName telegram from the accessory.

[0452] SetPlayStatusChangeNotification Command

[0453] Direction: accessory→media player

[0454] Applies to: playback engine

[0455] Sets the state of play status change notifications from the media player to the accessory.

[0456] PlayStatusChangeNotification Command

[0457] Direction: media player→accessory

[0458] The media player sends this telegram to the accessory when the media player play status changes, if the accessory has previously enabled notifications using the SetPlayStatusChangeNotification command. This telegram contains details about the new play status.

[0459] PlayCurrent Selection Command

[0460] Direction: accessory→media player

[0461] Applies to: playback engine and database engines. This command copies items from the database engine to the playback engine.

[0462] Requests playback of the currently selected track or list of tracks.

[0463] PlayControl Command

[0464] Direction: accessory→media player

[0465] Applies to: playback engine

[0466] Sets the new play state of the media player.

[0467] GetShuffle Command

[0468] Direction: accessory→media player

[0469] Requests the current state of the media player shuffle setting.

[0470] ReturnShuffle Command

[0471] Direction: media player→accessory

[0472] Returns the current state of the shuffle setting.

[0473] SetShuffle Command

[0474] Direction: accessory→media player

[0475] Sets the media player shuffle mode.

[0476] GetRepeat Command

[0477] Direction: accessory→media player

[0478] Requests the track repeat state of the media player.

[0479] ReturnRepeat Command

[0480] Direction: media player→accessory

[0481] Returns the current media track repeat state to the accessory.

[0482] SetRepeat Command

[0483] Direction: accessory→media player

[0484] Sets the repeat state of the media player.

[0485] SetDisplayImage Command

[0486] Direction: accessory→media player

[0487] Sets a bitmap image that is shown on the media player display when it is connected to the accessory.

[0488] GetMonoDisplayImageLimits Command

[0489] Direction: accessory→media player

[0490] Requests the limiting characteristics of the monochrome image that can be sent to the media player for display while it is connected to the accessory.

[0491] ReturnMonoDisplayImageLimits Command

[0492] Direction: media player→accessory

[0493] Returns the limiting characteristics of the monochrome image that can be sent to the media player for display while it is connected to the accessory.

[0494] GetNumPlayingTracks Command

[0495] Direction: accessory→media player

[0496] Applies to: playback engine

[0497] Requests the number of tracks in the list of tracks queued to play on the media player.

[0498] ReturnNumPlayingTracks Command

[0499] Direction: media player→accessory

[0500] Returns the number of tracks in the actual list of tracks queued to play, including the currently playing track (if any).

[0501] SetCurrentPlayingTrack Command

[0502] Direction: accessory→media player

[0503] Applies to: playback engine

[0504] Sets the index of the track to play in the Now Playing playlist on the media player.

[0505] SelectSortDBRecord Command

[0506] Direction: accessory→media player

[0507] Applies to: database engine

[0508] Selects one or more records in the media player database, based on a category-relative index.

[0509] GetColorDisplayImageLimits Command

[0510] Direction: accessory→media player

[0511] Requests the limiting characteristics of the color image that can be sent to the media player for display while it is connected to the accessory.

[0512] ReturnColorDisplayImageLimits Command

[0513] Direction: media player→accessory

[0514] Returns the limiting characteristics of the color image that can be sent to the media player for display while it is connected to the accessory.

[0515] RF Transmitter Lingo

[0516] The RF Transmitter Lingo is used for accessories that transmit the media player analog audio over radio frequencies (typically an unused frequency in the FM band). The Begin Transmission command packet notifies the external RF transmitter accessory that the media player is entering playback mode. The End Transmission command packet notifies the RF transmitter that the media player is exiting playback mode (that is, it is stopped, entering light sleep mode, and so forth).

[0517] Begin Transmission Command

[0518] Direction: media player→accessory

[0519] The media player sends this command to notify the accessory that high power may be used and that it should begin transmitting.

[0520] End Transmission Command

[0521] Direction: media player→accessory

[0522] The media player sends this command to notify the accessory to stop transmitting and to stop using accessory high power.

Single Lingo Accessory Identification

[0523] Accessories should use the general lingo identify command to identify themselves as supporting a single accessory lingo. FIG. 7 illustrates a single-lingo accessory command flow. In this command flow, first the accessory waits for media player internal bootstrap/wakeup and allows the media player to synchronize to the accessory rate. Next, the media player is informed that accessory is present and supports the Extended Interface lingo. Thereafter, the accessory gets (requests) the version of the extended interface lingo protocol supported by the media player and the media player sends the protocol version for verification. If received, the accessory has successfully forced the media player into extended interface mode. The accessory should use the returned lingo version to determine which features are available from the media player.

Multiple Lingo Accessory Identification

[0524] Accessories should use the general lingo IdentifyAccessoryLingoes command to identify themselves as supporting multiple accessory lingoes (not including the general lingo), or when they are communicating with the media player over the USB port link.

[0525] Accessories that support the extended interface mode and identify as a multi-lingo accessory do not automatically switch into the extended interface mode after the identification process completes. These accessories must explicitly switch into and out of the extended interface mode, using the general lingo commands.

[0526] Accessories that identify themselves as supporting multiple lingoes should use the steps shown in FIG. 8. FIG. 8 illustrates a multiple lingo command flow. In this flow, first the accessory waits for the media player bootstrap/wakeup and allows the media player to synchronize to the accessory rate. Next, the media player is informed that the accessory is present, and the bit field of supported lingoes is sent. The media player acknowledges the IdentifyAccessoriesLingos command. Next, the media player general lingo version information is requested, and the media player sends the general lingo protocol version. This information is used to determine which features are available from the media player. The accessory is then switched into the extended interface mode, sending the EnterExtendedInterfaceMode Command, and the media player sends a first ACK indicating how long it will take the media player to switch modes. The media player sends a second ACK notifying the accessory of the mode switch, and the media player sends an extended interface protocol version for verification. If received, the accessory has successfully forced the media player into extended interface mode. The accessory should use the returned information to determine which features are available from the media player. This figure assumes the accessory is using the UART serial port link.

[0527] A connector interface system for a communication accessory is disclosed. The interface includes a docking connector. The docking connector includes first make/last break contacts that minimize internal damage to the internal electronics. The docking connector also includes a specific keying arrangement to prevent noncompliant connectors from being plugged in, and thereby minimizes potential damage to the multi-communication accessory. The remote connector provides for the ability to output audio, input audio, and output video. The connector system interface also includes a media player protocol to control accessory features. These controls allow for a user to control the functionality of media player in a variety of modes.

[0528] It will be clear that the invention described herein provides significant functional enhancements when incorporated into prior art systems. FIG. 9 shows an exemplary system 900 using the connector described herein. The system includes at least two accessories 902 and 904 to be connected together. Each accessory 902 and 904 contains an enhanced connector system interface 902a and 902b as described herein. They can be connected together either wirelessly or via a cable. Alternatively, one of the accessories can be itself constructed integrally with the connector so that it can be docked in place when mated with the other accessory, for example, as is done with flash-backed memory sticks, or similar accessories that include an integral connector. When connected together, the accessories can exchange data via the connector interface system signals that would not be conveniently possible but for the existence of the connector pins and the protocol.

[0529] The connection interface system can be utilized with a plurality of accessory devices interfaces including, but not limited to, car stereo interface, home stereo interfaces, remote controls, radio interfaces, microphones, voice recorders, wireless accessories which allow for communications to other accessories and speakers.

[0530] 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. 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

Certificate of Correction present

The claims shown below may not include correction changes. Use the corrected PDF for authoritative text.

What is claimed is:

1. A method of operating a media player, the method comprising:

receiving an identification command of the general lingo from the accessory via the communication link, wherein the identification command identifies at least one of the accessory lingoes supported by the media player as being supported by the accessory; and

communicating with the accessory using the general lingo and the at least one of the accessory lingoes identified as being supported by the accessory.

2. The method of claim 1 wherein the identification command indicates that the accessory supports exactly one of the accessory lingoes and identifies the one accessory lingo that the accessory supports.

3. The method of claim 1 wherein the identification command indicates that the accessory supports one or more of the accessory lingoes and identifies each of the accessory lingoes that the accessory supports.

4. The method of claim 1 wherein the plurality of accessory lingoes supported by the media player includes at least one lingo from a group consisting of a microphone lingo, a simple remote lingo, a display remote lingo, an extended interface lingo, and an RF transmitter lingo.

5. A media player comprising:

a storage device capable of storing media assets;

a playback engine capable of playing media assts stored on the storage device; and

an interface capable of communicating with an accessory in accordance with a media player accessory protocol, the media player accessory protocol comprising a general lingo and a plurality of accessory lingoes supported by the media player;

wherein the interface is configured to receive an identification command of the general lingo from the accessory, the identification command identifying at least one of the accessory lingoes as being supported by the accessory.

6. The media player of claim 5 wherein the general lingo includes a plurality of different identification commands receivable by the medial player from the accessory, the plurality of different identification commands including at least:

a first identification command indicating that the accessory supports exactly one of the plurality of accessory lingoes supported by the media player and identifying the one accessory lingo that the accessory supports; and

a second identification command indicating that the accessory supports one or more of the plurality of accessory lingoes supported by the media player and identifying each of the accessory lingoes that the accessory supports,

wherein the interface is configured to receive any one of the plurality of different identification commands from an accessory.

7. The media player of claim 5 wherein the plurality of accessory lingoes supported by the media player includes a microphone lingo and wherein the microphone lingo includes at least one command from a group consisting of:

a first command sendable by the media player and signaling a beginning of recording of audio input;

a second command sendable by the media player and signaling an ending of recording of audio input;

a third command sendable by the media player and signaling a beginning of playback of recorded audio input; and

a fourth command sendable by the media player and signaling an ending of playback of recorded audio input.

8. The media player of claim 5 wherein the plurality of accessory lingoes supported by the media player includes a simple remote lingo and wherein the simple remote lingo includes a button status command receivable by the media player, the button status command indicating a status of a user-operable control of the accessory.

9. The media player of claim 5 wherein the plurality of accessory lingoes supported by the media player includes a display remote lingo and wherein the display remote lingo includes one or more commands from a group consisting of:

a first command receivable by the media player, the first command specifying an equalizer setting to be applied by the media player;

a second command receivable by the media player, the second command requesting information about one or more media assets queued for playback by the media player;

a third command sendable by the media player, the third command providing information about one or more media assets queued for playback by the media player;

a fourth command receivable by the media player, the fourth command requesting information about a state of the media player;

a fifth command sendable by the media player, the fifth command providing information about the state of the media player; and

a sixth command receivable by the media player, the sixth command instructing the media player to change a state of the media player.

10. The media player of claim 5 wherein the plurality of accessory lingoes supported by the media player includes a radio-frequency (RF) transmitter lingo and wherein the RF transmitter lingo includes at least one command from a group consisting of:

a first command sendable by the media player to indicate when the accessory should begin an RF transmission; and

a second command sendable by the media player to indicate when the accessory should end an RF transmission.

11. The media player of claim 5 wherein the plurality of accessory lingoes supported by the media player includes an extended interface lingo and wherein the extended interface lingo includes at least one command from a group consisting of:

a first command receivable by the media player, the first command requesting information about a currently playing media asset;

a second command sendable by the media player, the second command providing information about the currently playing media asset;

a third command receivable by the media player, the third command requesting information about a media asset queued for playback by the media player;

a fourth command sendable by the media player, the fourth command providing information about the media asset queued for playback by the media player;

a fifth command receivable by the media player, the fifth command requesting information from a database of media assets stored on the media player;

a sixth command sendable by the media player, the sixth command providing information from the database of media assets stored on the media player; and

a seventh command receivable by the media player, the seventh command instructing the media player to select a media asset for playback.

12. The media player of claim 11 wherein the general lingo further includes a mode controlling command receivable by the media player, the mode controlling command indicating when the media player should enter an extended interface operating mode.

13. The media player of claim 5 wherein the interface includes a connector having a plurality of signal contacts arranged to be connectable to a plurality of signal contacts of a mating connector that is connected to the accessory.

14. The media player of claim 5 wherein the interface includes a wireless communication interface.

15. A computer program product comprising a computer readable storage medium encoded with program instructions, which when executed by a processor in a media player cause the processor to execute a method comprising:

establishing a communication link to an accessory, wherein the media player is configured to communicate with the accessory via the communication link using a media player accessory protocol comprising a general lingo and a plurality of accessory lingoes supported by the media player, the plurality of accessory lingoes including at least one lingo from a group consisting of a microphone lingo, a simple remote lingo, a display remote lingo, and extended interface lingo, and an RF transmitter lingo; and

16. The computer program product of claim 15 wherein the identification command indicates that the accessory supports exactly one of the accessory lingoes supported by the media player and identifies the one accessory lingo that the accessory supports.

17. The computer program product of claim 15 wherein the identification command indicates that the accessory supports one or more of the accessory lingoes supported by the media player and identifies each of the accessory lingoes that the accessory supports.

18. The computer program product of claim 15 wherein the method further comprises, in the event that the received identification command identifies a restricted one of the plurality of accessory lingoes as being supported by the accessory:

sending a first authentication command of the general lingo to the accessory; and

receiving a second authentication command from the accessory, the second authentication command including authentication information for the accessory.

19. A computer program product comprising a computer readable storage medium encoded with program instructions, which when executed by a processor in a media player cause the processor to execute a method comprising:

establishing communication with an accessory, wherein the media player is configured to communicate with the accessory using a media player accessory protocol comprising a general lingo including a plurality of identification commands and at least one accessory lingo;

receiving one of the plurality of identification commands of the general lingo from the accessory, wherein the received identification command identifies an accessory lingo of the media player accessory protocol as being supported by the accessory; and

obtaining authentication information from the accessory using one or more accessory-authentication commands of the general lingo.

20. The computer program of claim 19 wherein the method further comprises:

providing authentication information to the accessory using one or more media-player-authentication commands of the general lingo.

21. The computer program product of claim 19 wherein the media player accessory protocol comprises a plurality of accessory lingoes and wherein the plurality of identification commands of the general lingo includes at least:

a single-lingo identification command receivable by the media player, the single-lingo identification command indicating that the accessory supports exactly one of the plurality of accessory lingoes and identifying the one of the plurality of accessory lingoes that the accessory supports; and

a multi-lingo identification command receivable by the media player, the multi-lingo identification command identifying one or more of the plurality of accessory lingoes supported by the media player as being supported by the accessory.

22. The computer program product of claim 21 wherein the plurality of accessory lingoes supported by the media player includes at least one lingo from a group consisting of a microphone lingo, a single remote lingo, a display remote lingo, and extended interface lingo and an RF transmitter lingo.

Patent Citations (331)

Patent	Date	Inventor	Cited By
US4673861(A)	1987-06-01	Dubovsky et al.	Applicant
US4850899(A)	1989-07-01	Maynard	Applicant
US4916334(A)	1990-04-01	Minagawa et al.	Applicant
US4924216(A)	1990-05-01	Leung	Applicant
US4938483(A)	1990-07-01	Yavetz	Applicant
US5041025(A)	1991-08-01	Haitmanek	Applicant
US5055069(A)	1991-10-01	Townsend et al.	Applicant
US5080603(A)	1992-01-01	Mouissie	Applicant
US5104243(A)	1992-04-01	Harding	Applicant
US5108313(A)	1992-04-01	Adams	Applicant
US5150031(A)	1992-09-01	James et al.	Applicant
US5186646(A)	1993-02-01	Pederson	Applicant
US5247138(A)	1993-09-01	Landmeier	Applicant
US5277624(A)	1994-01-01	Champion	Applicant
US5471128(A)	1995-11-01	Patino et al.	Applicant
US5525981(A)	1996-06-01	Abernethy	Applicant
US5586893(A)	1996-12-01	Mosquera	Applicant
US5592588(A)	1997-01-01	Reekes et al.	Applicant
US5618045(A)	1997-04-01	Kagan et al.	Applicant
US5648712(A)	1997-07-01	Hahn	Applicant
US5660558(A)	1997-08-01	Osanai et al.	Applicant
US5727866(A)	1998-03-01	Kraines et al.	Applicant
US5732361(A)	1998-03-01	Liu	Applicant
US5754027(A)	1998-05-01	Oglesbee et al.	Applicant
US5830001(A)	1998-11-01	Kinoshita	Applicant
US5835862(A)	1998-11-01	Nykanen et al.	Applicant
US5845217(A)	1998-12-01	Lindell et al.	Applicant
US5859522(A)	1999-01-01	Theobald	Applicant
US5901049(A)	1999-05-01	Schmidt et al.	Applicant
US5964847(A)	1999-10-01	Booth, III et al.	Applicant
US5975957(A)	1999-11-01	Noda et al.	Applicant
US6007372(A)	1999-12-01	Wood	Applicant
US6012105(A)	2000-01-01	Rubbmark et al.	Applicant
US6031797(A)	2000-02-01	Van Ryzint et al.	Applicant
US6053773(A)	2000-04-01	Wu	Applicant
US6078402(A)	2000-06-01	Fischer et al.	Applicant
US6078789(A)	2000-06-01	Bodenmann et al.	Applicant
US6125455(A)	2000-09-01	Yeo	Applicant
US6130518(A)	2000-10-01	Gabehart et al.	Applicant
US6139373(A)	2000-10-01	Ward et al.	Applicant
US6154773(A)	2000-11-01	Roberts et al.	Applicant
US6154798(A)	2000-11-01	Lin et al.	Applicant
US6161027(A)	2000-12-01	Poirel	Applicant
US6169387(B1)	2001-01-01	Kaib	Applicant
US6175358(B1)	2001-01-01	Scott-Jackson et al.	Applicant
US6178514(B1)	2001-01-01	Wood	Applicant
US6184652(B1)	2001-02-01	Yang	Applicant
US6184655(B1)	2001-02-01	Malackowski	Applicant
US6188265(B1)	2001-02-01	Liu et al.	Applicant
US6203345(B1)	2001-03-01	Roque et al.	Applicant
US6204637(B1)	2001-03-01	Rengan	Applicant
US6206480(B1)	2001-03-01	Thompson	Applicant
US6211581(B1)	2001-04-01	Farrant	Applicant
US6211649(B1)	2001-04-01	Matsuda	Applicant
US6224420(B1)	2001-05-01	Nishio et al.	Applicant
US6230205(B1)	2001-05-01	Garrity et al.	Applicant
US6234827(B1)	2001-05-01	Nishio et al.	Applicant
US6252380(B1)	2001-06-01	Koenck	Applicant
US6261109(B1)	2001-07-01	Liu et al.	Applicant
US6267623(B1)	2001-07-01	Hisamatsu	Applicant
US6268845(B1)	2001-07-01	Pariza et al.	Applicant
US6271605(B1)	2001-08-01	Carkner et al.	Applicant
US6272328(B1)	2001-08-01	Nguyen et al.	Applicant
US6280251(B1)	2001-08-01	Nishio et al.	Applicant
US6283789(B1)	2001-09-01	Tsai	Applicant
US6304764(B1)	2001-10-01	Pan	Applicant
US6314479(B1)	2001-11-01	Frederick et al.	Applicant
US6316916(B2)	2001-11-01	Bohne	Applicant
US6319061(B1)	2001-11-01	Chen et al.	Applicant
US6322396(B1)	2001-11-01	Kuan	Applicant
US6344727(B1)	2002-02-01	Desai et al.	Applicant
US6353894(B1)	2002-03-01	Pione	Applicant
US6354713(B1)	2002-03-01	Leifer et al.	Applicant
US6358089(B1)	2002-03-01	Kuroda et al.	Applicant
US6372974(B1)	2002-04-01	Gross et al.	Applicant
US6385596(B1)	2002-05-01	Wiser et al.	Applicant
US6394905(B1)	2002-05-01	Takeda et al.	Applicant
US6429879(B1)	2002-08-01	Sturgeon et al.	Applicant
US6431915(B1)	2002-08-01	Ko	Applicant
US6453371(B1)	2002-09-01	Hampson et al.	Applicant
US6454592(B2)	2002-09-01	Takagi	Applicant
US6461173(B1)	2002-10-01	Mizuno et al.	Applicant
US6464542(B1)	2002-10-01	Lee	Applicant
US6468110(B2)	2002-10-01	Fujino et al.	Applicant
US6478603(B1)	2002-11-01	Wu	Applicant
US6483428(B1)	2002-11-01	Fish et al.	Applicant
US6485328(B1)	2002-11-01	Wu	Applicant
US6489751(B2)	2002-12-01	Small et al.	Applicant
US6505160(B1)	2003-01-01	Levy et al.	Applicant
US6524119(B2)	2003-02-01	Kato et al.	Applicant
US6526287(B1)	2003-02-01	Lee	Applicant
US6558201(B1)	2003-05-01	Begley et al.	Applicant
US6577877(B1)	2003-06-01	Charlier et al.	Applicant
US6589076(B1)	2003-07-01	Davis et al.	Applicant
US6591085(B1)	2003-07-01	Grady	Applicant
US6608264(B1)	2003-08-01	Fouladpour	Applicant
US6608399(B2)	2003-08-01	McConnell et al.	Applicant
US6614232(B1)	2003-09-01	Mukai	Applicant
US6616473(B2)	2003-09-01	Kamata et al.	Applicant
US6629197(B1)	2003-09-01	Bhogal et al.	Applicant
US6642629(B2)	2003-11-01	DeLeeuw	Applicant
US6651138(B2)	2003-11-01	Lai et al.	Applicant
US6653813(B2)	2003-11-01	Khatri	Applicant
US6663420(B1)	2003-12-01	Xiao	Applicant
US6665803(B2)	2003-12-01	Lunsford et al.	Applicant
US6674995(B1)	2004-01-01	Meyers et al.	Applicant
US6687454(B1)	2004-02-01	Kuroiwa	Applicant
US6697944(B1)	2004-02-01	Jones et al.	Applicant
US6724339(B2)	2004-04-01	Conway et al.	Applicant
US6725061(B1)	2004-04-01	Hutchison, IV et al.	Applicant
US6728546(B1)	2004-04-01	Peterson et al.	Applicant
US6728729(B1)	2004-04-01	Jawa et al.	Applicant
US6747859(B2)	2004-06-01	Walbeck et al.	Applicant
US6754468(B1)	2004-06-01	Sieben et al.	Applicant
US6761635(B2)	2004-07-01	Hoshino et al.	Applicant
US6774939(B1)	2004-08-01	Peng	Applicant
US6776626(B2)	2004-08-01	Huang et al.	Applicant
US6776660(B1)	2004-08-01	Kubota et al.	Applicant
US6776665(B2)	2004-08-01	Huang	Applicant
US6799226(B1)	2004-09-01	Robbin et al.	Applicant
US6801964(B1)	2004-10-01	Mahdavi	Applicant
US6813528(B1)	2004-11-01	Yang	Applicant
US6816376(B2)	2004-11-01	Bright et al.	Applicant
US6830160(B2)	2004-12-01	Risolia	Applicant
US6859538(B1)	2005-02-01	Voltz	Applicant
US6859854(B2)	2005-02-01	Kwong	Applicant
US6879843(B1)	2005-04-01	Kim	Applicant
US6928295(B2)	2005-08-01	Olson et al.	Applicant
US6931266(B2)	2005-08-01	Miyoshi et al.	Applicant
US6931456(B2)	2005-08-01	Payne et al.	Applicant
US6939177(B2)	2005-09-01	Kato et al.	Applicant
US6991483(B1)	2006-01-01	Milan et al.	Applicant
US7004787(B2)	2006-02-01	Milan	Applicant
US7013164(B2)	2006-03-01	Lin	Applicant
US7050783(B2)	2006-05-01	Curtiss et al.	Applicant
US7054888(B2)	2006-05-01	LaChapelle et al.	Applicant
US7062261(B2)	2006-06-01	Goldstein et al.	Applicant
US7108560(B1)	2006-09-01	Chou et al.	Applicant
US7127678(B2)	2006-10-01	Bhesania et al.	Applicant
US7127879(B2)	2006-10-01	Zhu et al.	Applicant
US7167112(B2)	2007-01-01	Andersen et al.	Applicant
US7167935(B2)	2007-01-01	Hellberg	Applicant
US7187947(B1)	2007-03-01	White et al.	Applicant
US7187948(B2)	2007-03-01	Alden	Applicant
US7215042(B2)	2007-05-01	Yan	Applicant
US7281214(B2)	2007-10-01	Fadell	Applicant
US7293122(B1)	2007-11-01	Schubert et al.	Applicant
US7293227(B2)	2007-11-01	Plastina et al.	Applicant
US7299304(B2)	2007-11-01	Saint-Hilaire et al.	Applicant
US7303282(B2)	2007-12-01	Dwyer et al.	Applicant
US7304685(B2)	2007-12-01	Park et al.	Applicant
US7305254(B2)	2007-12-01	Findikli	Applicant
US7305506(B1)	2007-12-01	Lydon et al.	Applicant
US7362963(B2)	2008-04-01	Lin	Applicant
US7415563(B1)	2008-08-01	Holden et al.	Applicant
US7441058(B1)	2008-10-01	Bolton et al.	Applicant
US7441062(B2)	2008-10-01	Novotney et al.	Applicant
US7444388(B1)	2008-10-01	Svendsen	Applicant
US7454019(B2)	2008-11-01	Williams	Applicant
US7526588(B1)	2009-04-01	Schubert et al.	Applicant
US7529870(B1)	2009-05-01	Schubert et al.	Applicant
US7529871(B1)	2009-05-01	Schubert et al.	Applicant
US7529872(B1)	2009-05-01	Schubert et al.	Examiner
US7558894(B1)	2009-07-01	Lydon et al.	Applicant
US7587540(B2)	2009-09-01	Novotney et al.	Applicant
US7590783(B2)	2009-09-01	Lydon et al.	Applicant
US7634605(B2)	2009-12-01	Laefer et al.	Applicant
US7660929(B2)	2010-02-01	Novotney et al.	Applicant
US2001/0003205(A1)	2001-06-01	Gilbert	Applicant
US2001/0005641(A1)	2001-06-01	Matsumoto et al.	Applicant
US2001/0006884(A1)	2001-07-01	Matsumoto	Applicant
US2002/0002035(A1)	2002-01-01	Sim et al.	Applicant
US2002/0010759(A1)	2002-01-01	Hitson et al.	Applicant
US2002/0025042(A1)	2002-02-01	Saito	Applicant
US2002/0029303(A1)	2002-03-01	Nguyen	Applicant
US2002/0065074(A1)	2002-05-01	Cohn et al.	Applicant
US2002/0068610(A1)	2002-06-01	Anvekar et al.	Applicant
US2002/0072390(A1)	2002-06-01	Uchiyama	Applicant
US2002/0103008(A1)	2002-08-01	Rahn et al.	Applicant
US2002/0105861(A1)	2002-08-01	Leapman	Applicant
US2002/0108108(A1)	2002-08-01	Akaiwa et al.	Applicant
US2002/0115480(A1)	2002-08-01	Huang	Applicant
US2002/0116533(A1)	2002-08-01	Holliman et al.	Applicant
US2002/0132651(A1)	2002-09-01	Jinnouchi	Applicant
US2002/0151327(A1)	2002-10-01	Levitt	Applicant
US2002/0152874(A1)	2002-10-01	Vilcauskas et al.	Applicant
US2002/0156546(A1)	2002-10-01	Ramaswamy	Applicant
US2002/0156949(A1)	2002-10-01	Kubo et al.	Applicant
US2002/0173273(A1)	2002-11-01	Spurgat et al.	Applicant
US2002/0174269(A1)	2002-11-01	Spurgat et al.	Applicant
US2002/0194621(A1)	2002-12-01	Tran et al.	Applicant
US2003/0004934(A1)	2003-01-01	Qian	Applicant
US2003/0011608(A1)	2003-01-01	Wada	Applicant
US2003/0028664(A1)	2003-02-01	Tan et al.	Applicant
US2003/0041206(A1)	2003-02-01	Dickie	Applicant
US2003/0059022(A1)	2003-03-01	Nebiker et al.	Applicant
US2003/0067741(A1)	2003-04-01	Alfonso et al.	Applicant
US2003/0073432(A1)	2003-04-01	Meade	Applicant
US2003/0079038(A1)	2003-04-01	Robbin et al.	Applicant
US2003/0090988(A1)	2003-05-01	Sun et al.	Applicant
US2003/0097379(A1)	2003-05-01	Ireton	Applicant
US2003/0110403(A1)	2003-06-01	Crutchfield et al.	Applicant
US2003/0151621(A1)	2003-08-01	McEvilly et al.	Applicant
US2003/0172209(A1)	2003-09-01	Liu et al.	Applicant
US2003/0185395(A1)	2003-10-01	Lee et al.	Applicant
US2003/0198015(A1)	2003-10-01	Vogt	Applicant
US2003/0220988(A1)	2003-11-01	Hymel	Applicant
US2003/0236075(A1)	2003-12-01	Johnson et al.	Applicant
US2003/0237043(A1)	2003-12-01	Novak et al.	Applicant
US2004/0003300(A1)	2004-01-01	Malueg et al.	Applicant
US2004/0019497(A1)	2004-01-01	Volk et al.	Applicant
US2004/0039860(A1)	2004-02-01	Mills et al.	Applicant
US2004/0048569(A1)	2004-03-01	Kawamura	Applicant
US2004/0090998(A1)	2004-05-01	Chen	Applicant
US2004/0103223(A1)	2004-05-01	Gabehart et al.	Applicant
US2004/0116005(A1)	2004-06-01	Choi	Applicant
US2004/0162029(A1)	2004-08-01	Grady	Applicant
US2004/0164708(A1)	2004-08-01	Veselic et al.	Applicant
US2004/0172533(A1)	2004-09-01	DeMello et al.	Applicant
US2004/0186935(A1)	2004-09-01	Bel et al.	Applicant
US2004/0194154(A1)	2004-09-01	Meadors et al.	Applicant
US2004/0198436(A1)	2004-10-01	Alden	Applicant
US2004/0224638(A1)	2004-11-01	Fadell et al.	Applicant
US2004/0235339(A1)	2004-11-01	Sato et al.	Applicant
US2004/0249994(A1)	2004-12-01	Shapiro et al.	Applicant
US2004/0252966(A1)	2004-12-01	Holloway et al.	Applicant
US2004/0267812(A1)	2004-12-01	Harris et al.	Applicant
US2004/0267825(A1)	2004-12-01	Novak et al.	Applicant
US2005/0014119(A1)	2005-01-01	Rudakov	Applicant
US2005/0014531(A1)	2005-01-01	Findikli	Applicant
US2005/0014536(A1)	2005-01-01	Grady	Applicant
US2005/0015355(A1)	2005-01-01	Heller et al.	Applicant
US2005/0022212(A1)	2005-01-01	Bowen	Applicant
US2005/0047071(A1)	2005-03-01	Tse Chun Hin	Applicant
US2005/0135790(A1)	2005-06-01	Hutten	Applicant
US2005/0149213(A1)	2005-07-01	Guzak et al.	Applicant
US2005/0181756(A1)	2005-08-01	Lin	Applicant
US2005/0207726(A1)	2005-09-01	Chen	Applicant
US2005/0227612(A1)	2005-10-01	Helstrom et al.	Applicant
US2005/0239333(A1)	2005-10-01	Watanabe et al.	Applicant
US2005/0240705(A1)	2005-10-01	Novotney et al.	Applicant
US2005/0281185(A1)	2005-12-01	Kawasaki	Applicant
US2006/0015826(A1)	2006-01-01	Shiozawa et al.	Applicant
US2006/0031545(A1)	2006-02-01	Manders et al.	Applicant
US2006/0056796(A1)	2006-03-01	Nishizawa et al.	Applicant
US2006/0088228(A1)	2006-04-01	Marriott et al.	Applicant
US2006/0156415(A1)	2006-07-01	Rubinstein et al.	Applicant
US2006/0161621(A1)	2006-07-01	Rosenberg	Applicant
US2006/0163358(A1)	2006-07-01	Biderman	Applicant
US2006/0184456(A1)	2006-08-01	de Janasz	Applicant
US2006/0188237(A1)	2006-08-01	Watanabe et al.	Applicant
US2006/0224620(A1)	2006-10-01	Silverman et al.	Applicant
US2006/0236245(A1)	2006-10-01	Agarwal et al.	Applicant
US2006/0247851(A1)	2006-11-01	Morris	Applicant
US2006/0258289(A1)	2006-11-01	Dua	Applicant
US2006/0294209(A1)	2006-12-01	Rosenbloom et al.	Applicant
US2007/0018947(A1)	2007-01-01	Toro-Lira	Applicant
US2007/0056012(A1)	2007-03-01	Kwon et al.	Applicant
US2007/0056013(A1)	2007-03-01	Duncan	Applicant
US2007/0070856(A1)	2007-03-01	Tebele	Applicant
US2007/0080823(A1)	2007-04-01	Fu et al.	Applicant
US2007/0083750(A1)	2007-04-01	Miura et al.	Applicant
US2007/0083814(A1)	2007-04-01	Wilbrink et al.	Applicant
US2007/0086724(A1)	2007-04-01	Grady et al.	Applicant
US2007/0106760(A1)	2007-05-01	Houh et al.	Applicant
US2007/0173197(A1)	2007-07-01	Hsiung	Applicant
US2007/0173294(A1)	2007-07-01	Hsiung	Applicant
US2007/0206827(A1)	2007-09-01	Tupman et al.	Applicant
US2007/0226384(A1)	2007-09-01	Robbin et al.	Applicant
US2007/0233294(A1)	2007-10-01	Holden et al.	Applicant
US2007/0233295(A1)	2007-10-01	Laefer et al.	Applicant
US2007/0234420(A1)	2007-10-01	Novotney et al.	Applicant
US2007/0236482(A1)	2007-10-01	Proctor et al.	Applicant
US2007/0247794(A1)	2007-10-01	Jaffe et al.	Applicant
US2008/0025172(A1)	2008-01-01	Holden et al.	Applicant
US2009/0013096(A1)	2009-01-01	Novotney et al.	Applicant
US2009/0013110(A1)	2009-01-01	Novotney et al.	Applicant
US2009/0013253(A1)	2009-01-01	Laefer et al.	Applicant
US2009/0125134(A1)	2009-05-01	Bolton et al.	Applicant
US2009/0132076(A1)	2009-05-01	Holden et al.	Applicant
US2009/0198361(A1)	2009-08-01	Schubert et al.	Applicant
US2009/0204244(A1)	2009-08-01	Schubert et al.	Applicant
US2009/0204738(A1)	2009-08-01	Schubert et al.	Applicant
US2009/0249101(A1)	2009-10-01	Lydon et al.	Applicant
US2009/0292835(A1)	2009-11-01	Novotney et al.	Applicant
US2009/0299506(A1)	2009-12-01	Lydon et al.	Applicant
EP1104150(A2)	2001-05-01		Applicant
EP1367734(A1)	2003-03-01		Applicant
EP1498899(A1)	2005-01-01		Applicant
EP1594319(A1)	2005-11-01		Applicant
EP1672613(A2)	2006-06-01		Applicant
GB2405718(A)	2005-03-01		Applicant
JP7-176351(A)	1995-07-01		Applicant
JP10-321302(A)	1998-04-01		Applicant
JP10-334993(A)	1998-12-01		Applicant
JP11-288420(A)	1999-10-01		Applicant
JP2000-214953(A)	2000-08-01		Applicant
JP2000-223215(A)	2000-08-01		Applicant
JP2000-223216(A)	2000-08-01		Applicant
JP2000-223218(A)	2000-08-01		Applicant
JP2001-035603(A)	2001-02-01		Applicant
JP2001-069165(A)	2001-03-01		Applicant
JP2001-196133(A)	2001-07-01		Applicant
JP2001-230021(A)	2001-08-01		Applicant
JP2001-332350(A)	2001-11-01		Applicant
JP2002-025720(A)	2002-01-01		Applicant
JP2002-14304(A)	2002-05-01		Applicant
JP2002-203641(A)	2002-07-01		Applicant
JP2002245719(A)	2002-08-01		Applicant
JP2002-252566(A)	2002-09-01		Applicant
JP3090747(U)	2002-10-01		Applicant
JP2002-342659(A)	2002-11-01		Applicant
JP2002-374447(A)	2002-12-01		Applicant
JP2003-017165(A)	2003-01-01		Applicant
JP2003-032351(A)	2003-01-01		Applicant
JP2003-058430(A)	2003-02-01		Applicant
JP2003-274386(A)	2003-09-01		Applicant
JP2004-078538(A)	2004-03-01		Applicant
JP2004-259280(A)	2004-09-01		Applicant
WO99/26330	1999-05-01		Applicant
WO/39907	2000-07-01		Applicant
WO/060450(A1)	2000-10-01		Applicant
WO2/049314(A2)	2002-06-01		Applicant
WO3/036541(A1)	2003-05-01		Applicant
WO3/036957(A1)	2003-05-01		Applicant
WO3/073688	2003-09-01		Applicant
WO2004/084413(A2)	2004-09-01		Applicant
WO2004-095772(A1)	2004-11-01		Applicant
WO2004/112311(A1)	2004-12-01		Applicant
WO2005/119463(A2)	2005-12-01		Applicant
WO2006/080957(A2)	2006-08-01		Applicant

Non-Patent Literature (43)

Altec Lansing, “inMotion Users Guide,” Corp. Headquarters, 535 Rte.6 & 209, Milford, PA 18337.Applicant
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.Applicant
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.Applicant
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.Applicant
“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.Applicant
Belkin iPod Voice Recorder, Product Specification Sheet, printed Jun. 16, 2004.Applicant
Bindra, “Standard Turns Monitor into I/O Hub,” Electronic Engineering Times, vol. 918, Sep. 6, 1996, p. 14.Applicant
Brentrup, “Introduction to Public Key Cryptography Demystified,” Campus Technology, printed from http://www.campus-technology.com/article.asp?id=7626 on Oct. 6, 2004.Applicant
Brown, “Making UBS Work,” downloaded Oct. 16, 2001, PC Magazine: PC Tech wysiwyg:/155/http://www.zdnet.com/pcmag/pctech/content!18/04/tu1804.001.html.Applicant
“Cables to Go,” download Oct. 16, 2001 http://www.cablestoqo.com/product.asp?cat%5Fid=601&sku=27028.Applicant
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.Applicant
Derman, “Monitors Make Net Connections,” Electronic Engineering Times, vol. 933, 1996, pp. 60 and 69.Applicant
“ExpressBus™ F5U0l0,” User Guide Packing Checklist, Belkin Components Product Warranty.Applicant
“FireWire”, downloaded Oct. 16, 2001, si—wyg:/—/4—2/http://developer.apple.—comlhardwarelFire—Wire.Applicant
“Fire Wire Connector,” downloaded Oct. 16, 2001, wysiwyg://76/http://developerapple.com/...es/Macintosh—CPUs-G3/ibook/ibook-27.html.Applicant
Fried, “FireWire poised to become ubiquitous,” downloaded Oct. 16, 2001, CNET News.com, 1394 Trade Association: Press, wysiwg:/132/http:/—11394ta.org/Press/200—1—Press/august!8.2—7.—b.html.Applicant
Fried, “New Fire Wire to blaze faster trail,” downloaded Oct. 16, 2001, CNET News.com, http://news.cnet.com/news/0-l006-200-6021210.html.Applicant
“How to Connect Your Computer PC Hardware”, downloaded Oct. 16, 2001, http:///www.scar.utoronto.ca!˜ccweb/faculty/connect-howto.html.Applicant
“IEEE 1394/USB Comparison,” downloaded Oct. 16, 2001, www.genitech.com.aulLIBRARY/TechSupportiinfobits/firewirevsusb.html.Applicant
“Introduction to Public Key Cryptography,” Oct. 9, 1998, printed from http://developer.netscape.com/docs/manuals/security/pkin/contents.html on Oct. 6, 2004.Applicant
iPod Classic User's Guide, acquired from apple.com, 2002; 44 pages.Applicant
iPod nano Features Guide, acquired from apple.com, 2008; 72 pages.Applicant
iPod touch User's Guide, acquired from apple.com, 2008, 120 pages.Applicant
“iPodDock/iPod Cradle,” www.bookendzdocks.com/bookendz/dock—cradle.html, downloaded Feb. 27, 2003.Applicant
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.Applicant
Lewis, “On Technology” Fortune Magazine, Dec. 9, 2002, p. 240.Applicant
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.Applicant
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.Applicant
Menezes et al., “Handbook of Applied Cryptography,” Identification and Entity Authentication, pp. 385-424.Applicant
Microsoft, “Media Transport Protocol Implementation Details,” 2005, 18 pages.Applicant
“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.Applicant
Networking Tech Note, “1394 Standards and Specifications,” 3 pgs.Applicant
“Neuron MP3 Digital Audio Computer,” www.neurosaudio.com, downloaded Apr. 9, 2003, 6 pages.Applicant
“PMC FW2 IEEE1394 FireWire Controller”, downloaded Oct. 16, 2001, http://www.bvmltd.co.uk/PMCfw2ds.html.Applicant
Severance, “FireWire Finally Comes Home,” Michigan State University, Standards, Nov. 1998, pp. 117-118.Applicant
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.Applicant
Teener, “Understanding Fire Wire: The IEEE 1394 Standards and Specifications,” downloaded Oct. 16, 2001, wysiwyg:119/http:1 lwww.chipcenter.com/networking/ieee—1394/main.html.Applicant
“The Authoritative Dictionary of IEEE Standards Terms, Seventh Edition,” Published by Standards Information Network, IEEE Press, 2000, 3 pages.Applicant
“Universal Serial Bus Specification—Rev 2.0,” Chapter 6, Compaq Hewlett-Packard, Apr. 27, 2000, pp. 85, 99-100.Applicant
“Universal Serial Bus Specification—Rev 2.0,” XP002474828, Chapter 9, USB Device Framework, pp. 239-274.Applicant
Vitaliano, “Why FireWire is Hot!Hot!Hot!” downloaded Oct. 16, 2001, “Impact.FireWire.SideBar” http://www.vxm.com/21R.35.html.Applicant
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, 8 pages.Applicant
U.S. Appl. No. 12/610,966, filed Nov. 2, 2009, Laefer et al.Applicant

US 7,779,185 B2Grant

Communication between a media player and an accessory using a protocol with multiple lingoes

Issue Date:2010-08-17

•22 Claims

•15 Drawing Sheets

Abstract

Metadata

Assignee

Apple Inc.

Inventors

Emily Clark Schubert
Wang Chun Leung
Gregory T. Lydon
Scott Krueger
Paul Philip Holden
John Archibald
Lawrence G. Bolton
Donald J. Novotney
John Benjamin Filson
David Tupman

Application Information

Application Number:US 12/424,426

Filing Date:2009-04-15

Priority Date:2004-04-27

Art Unit:2111

Classifications

IPC:

G06F13/42

Patent Drawings (15 sheets)

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

FIELD OF THE INVENTION

[0002] The present invention relates generally to connector interfaces and more particularly to a connector interface system which is utilized in conjunction with media players and their accessories.

BACKGROUND OF THE INVENTION

SUMMARY OF THE INVENTION

BRIEF DESCRIPTION OF THE DRAWINGS

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

[0010] FIGS. 2A-2C illustrate the remote connector in accordance with the present invention.

[0011] FIG. 3A illustrates the connector pin designations for the docking connector.

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

[0013] FIG. 4A illustrates the Firewire connector interface.

[0014] FIG. 4B illustrates the USB connector interface.

[0015] FIG. 4C illustrates a reference schematic diagram for accessory detect and identify system for detecting and identifying accessories for the docking connector.

[0016] FIG. 4D is a reference schematic of an electret microphone that is within the remote connector.

[0017] FIGS. 5A-5E illustrate a media player coupled to a plurality of accessories.

[0018] FIG. 6 illustrates the sequence of events that can be utilized to test for the full set of general lingo commands.

[0019] FIG. 7 illustrates a single lingo accessory command flow.

[0020] FIG. 8 illustrates a multiple lingo command flow.

[0021] FIG. 9 illustrates an exemplary system using the connector interface system described herein.

DETAILED DESCRIPTION

Definitions

Device

[0022] An external electronic component connected to the media player using the 30-pin connector or the audio/remote connector.

HID

HID Report

MPUI

Lingo

[0026] The command category used by a device. There is a general lingo that must be supported by all devices. Other lingoes are designed for use by specific devices.

Link

[0027] The logical connection between an external device and the media player via serial port or other physical connection.

Connector Interface System Overview

Docking Connector

Remote Connector

Docking and Remote Connector Specifications

Docking Connector Specifications

USB Interface

Accessory 3.3 V Power

[0040] Accessory power is grounded through the DGND pins.

[0042] FIG. 4D is a reference schematic of an electret microphone that is within the remote connector.

[0043] Serial Protocol Communication is provided using two pins to communicate to and from device (Rx & Tx). Input and Output levels are 0V=Low, 3.3V=High.

Media Player Accessory Protocol (MPAP)

Protocol Transport Links

[0048] Accessories may communicate with the media player, using MPAP over the serial port link or the USB port link. Those links are described below.

UART Serial Port Link

[0049] Accessories using the Media Player Accessory Protocol (MPAP) over the UART serial port link use two pins, RX and TX, to communicate to and from the media player.

USB Port Link

[0052] The media player, for example, may be a USB 2.0-compliant device that supports two mutually exclusive modes of operation:

[0054] MPAP enabled device. This is the configuration needed to support MPAP using the Media Player USB Interface (MPUI). This mode must be selected by the USB host before it can be used.

Accessory Identify Resistor and MPUI

[0060] It is possible to create an accessory that supports both MPAP over USB and the older UART serial-only media players using the same connector.

Media Player USB Interface (MPUI) Configuration

HID as a Transport

[0065] A representative group of lingoes for the media player are listed below.

Lingo Specifications

Lingo

General

Microphone

Simple Remote

Display Remote

Extended Interface

RF transmitter

General Lingo Command Summary

[0067] Table 1 provides a summary of all commands in the general lingo, including whether or not device authentication is required for use of the command.

[0068]

	TABLE 1

		Authentication
	Command	Required

	Request Identify	No
	RequestMediaPlayerName	No
	RequestMediaPlayerSoftwareVersion	No
	RequestMediaPlayerSerialNum	No
	RequestMediaPlayerModelNum	No
	RequestLingoProtocolVersion	No
	Identify	No
	IdentifyAccessoryLingoes	No
	ACK	No
	AckDevAuthenticationInfo	No
	AckDevAuthenticationStatus	No
	AckMediaPlayerAuthenticationInfo	No
	AckMediaPlayerAuthenticationStatus	N/A
	ReturnMediaPlayerName	No
	ReturnMediaPlayerSoftwareVersion	No
	ReturnMediaPlayerSerialNumber	No
	ReturnLingoProtocolVersion	No
	RetDevAuthenticationInfo	No
	RetDevAuthenticationSignature	No
	RetMediaPlayerAuthenticationInfo	No
	RetMediaPlayerAuthenticationSignature	No
	GetDevAuthenticationInfo	No
	GetDevAuthenticationSignature	No
	GetMediaPlayerAuthenticationInfo	No
	GetMediaPlayerAuthenticationSignature	No
	NotifyMediaPlayerStateChange	No

[0070] The media player may send a RequestIdentify command to the device to ask to re-identify itself.

General Lingo Command Details

[0074] This section describes the general lingo commands and their packet formats.

[0075] Request Identify Command

[0076] Direction: media player→accessory

[0078] Identify Command

[0079] Direction: accessory→media player

[0081] The Identify command has facilities for RF Transmitter devices to draw more than a predetermined amount of power (such as 4 mA) from the media player.

ACK Command

[0082] Direction: media player→accessory

[0083] The media player sends the ACK command to notify the device of command completion status and errors.

[0084] RequestMediaPlayerSoftware Version Command

[0085] Direction: media player→accessory

[0086] Retrieves the software version for the media player. The media player responds with a ReturnMediaPlayerSoftwareVersion command containing the major, minor, and revision version numbers.

[0087] ReturnMediaPlayerSoftware Version Command

[0088] Direction: media player→accessory

RequestMediaPlayerName Command

[0090] Direction: accessory→media player

[0091] Retrieves the name of the media player. The media player responds with a ReturnMediaPlayerName command containing the name of the media player.

[0092] ReturnMediaPlayerName Command

[0093] Direction: media player→accessory

[0094] The media player sends this command in response to the RequestMediaPlayerName command message from the accessory.

RequestMediaPlayerSerialNum Command

[0095] Direction: accessory→media player

[0096] Retrieves the serial number string of the media player. The media player responds with a ReturnMediaPlayerSerialNumber command containing the serial number.

[0097] ReturnMediaPlayerSerialNum Command

[0098] Direction: media player→accessory

[0099] The media player sends this command in response to the RequestMediaPlayerSerialNumber command message from the accessory.

[0100] RequestMediaPlayerModelNum Command

[0101] Direction: accessory→media player

[0102] Retrieves information for the media player. The media player responds with a ReturnMediaPlayerModelNum command containing the model number of the media player.

[0103] ReturnMediaPlayerModelNum Command

[0104] Direction: media player→accessory

[0105] The media player sends this command in response to the RequestMediaPlayerModelNum command message from the accessory.

[0106] IdentifyAccessoryLingoes Command

[0107] Direction: accessory→media player

[0109] GetDevAuthenticationInfo Command

[0110] Direction: media player→accessory

[0112] RetDevAuthenticationInfo Command

[0113] Direction: accessory→media player

[0114] The accessory indicates the MPAP authentication version that it supports by returning this command in response to a GetDevAuthenticationInfo command from the media player.

[0115] AckDevAuthenticationInfo Command

[0116] Direction: media player→accessory

[0117] The media player sends this command in response to RetDevAuthenticationInfo command. It indicates the current state of the accessory authentication information.

[0118] RequestLingoProtocolVersion Command

[0119] Direction: accessory→media player

[0120] Retrieves version information for any of the lingoes supported by the media player.

[0121] The media player responds with a ReturnLingoProtocolVersion command containing the major and minor version information of the requested media player lingo.

ReturnLingoProtocolVersion Command

[0122] Direction: media player→accessory

[0124] GetDevAuthenticationSignature Command

[0125] Direction: media player→accessory

[0128] RetDevAuthenticationSignature Command

[0129] Direction: accessory→media player

[0131] AckDevAuthenticationStatus Command

[0132] Direction: media player→accessory

[0135] GetMediaPlayerAuthenticationSignature Command

[0136] Direction: accessory→media player

[0138] RetMediaPlayerAuthenticationSignature Command

[0139] Direction: media player→accessory

[0141] AckMediaPlayerAuthenticationStatus Command

[0142] Direction: accessory→media player

GetMediaPlayerAuthenticationInfo Command

[0144] Direction: accessory→media player

[0146] AckMediaPlayerAuthenticationInfo Command

[0147] Direction: accessory→media player

[0149] NotifyMediaPlayerStateChange Command

[0150] Direction: media player→accessory

Microphone Lingo Command

- [0154] Stereo line input source
- [0155] Stereo/mono control
- [0156] Recording level control
- [0157] Recording level limiter

[0161] Media player playback volume level changes may require the accessory to support display remote lingo functionality.

[0162] Table 2 lists the commands available as part of the microphone lingo.

[0163]

TABLE 2

		Authentication
Command	Connector	Required

BeginRecord	Audio/Remote	No
EndRecord	Audio/Remote	No
BeginPlayback	Audio/Remote	No
EndPlayback	Audio/Remote	No
ACK	30-pin	Yes
GetDevAck	30-pin	Yes
MediaPlayerModeChange	30-pin	Yes
GetDevCaps	30-pin	Yes
RetDevCaps	30-pin	Yes
GetDevCtrl	30-pin	Yes
RetDevCtrl	30-pin	Yes
SetDevCtrl	30-pin	Yes

[0164] BeginRecord Command

[0165] Direction: media player→accessory

[0166] The media player sends this command to notify the accessory that audio recording has started. The accessory does not return a packet to the media player in response to this command.

[0167] EndRecord Command

[0168] Direction: media player→accessory

[0169] The media player sends this command to notify the accessory that audio recording has ended. The accessory does not return a packet to the media player in response to this command.

[0170] BeginPlayback Command

[0171] Direction: media player→accessory

[0172] The media player sends this command to notify the accessory that audio playback has started. The accessory does not return a packet to the media player in response to this command.

EndPlayback Command

[0173] Direction: media player→accessory

[0174] The media player sends this command to notify the accessory that audio playback has ended. The accessory does not return a packet to the media player in response to this command.

[0175] ACK Command

[0176] Direction: accessory→media player

[0178] GetDevAck Command

[0179] Direction: media player→accessory

[0181] MediaPlayerModeChange Command

[0182] Direction: media player→accessory

GetDevCaps Command

[0184] Direction: media player→accessory

[0186] RetDevCaps Command

[0187] Direction: accessory→media player

[0188] The accessory sends this command in response to the command GetDevCaps command sent by the media player. The microphone accessory returns the payload indicating which capabilities it supports.

GetDevCtrl Command

[0189] Direction: media player→accessory

[0191] RetDevCtrl Command

[0192] Direction: accessory→media player

[0194] SetDevCtrl Command

[0195] Direction: media player→accessory

Simple Remote Lingo

Simple Remote Button Map

[0199]

	TABLE 3

	Button	Number


	Play/Pause	0
	Volume Up	1
	Volume Down	2
	Next Track	3
	Previous Track	4
	Next Album	5
	Previous Album	6
	Stop	7
	Play/Resume	8
	Pause	9
	Mute toggle	10
	Next Chapter	11
	Previous Chapter	12
	Next Playlist	13
	Previous Playlist	14
	Shuffle setting advance	15
	Repeat setting advance	16
	Power On	17
	Power Off	18
	Backlight for 30 seconds	19
	Begin FF	20
	Begin REW	21
	Menu	22
	Select	23
	Up Arrow	24
	Down Arrow	25

[0200] Some media player button states are interpreted differently by the media player when pressed and held down. These are as follows:

- [0201] The Next Track button is treated as a Scan Forward button when pressed and held while a track is playing.
- [0202] The Previous Track button is treated as a Scan Backward button when pressed and held while a track is playing.
- [0203] The Play/Pause button is treated as a Power Off button when pressed and held.
- [0204] The Menu button is treated as a Display Backlight On/Off button when pressed and held.
- [0205] If the media player is in Browse mode, the Select button is treated as an Add Track to On-The-Go Playlist button when pressed and held.

[0207] The Next and Previous Album commands (see Table 3) have no effect if there is no next or previous album to go in to the Now Playing list.

[0208] Below is the command for the simple remote lingo.

[0209] ContextButtonStatus Command

[0210] Direction: Accessory→media player

Display Remote Lingo

[0214] Table 4 illustrates the commands for the display remote lingo.

[0215]

TABLE 4

Command


	ACK
	GetCurrentEQProfileIndex
	RetCurrentEQProfileIndex
	SetCurrentEQProfileIndex
	GetNumEQProfiles
	RetNumEQProfiles
	GetIndexedEQProfileName
	RetIndexedEQProfileName
	SetRemoteEventNotification
	RemoteEventNotification
	GetRemoteEventStatus
	RetRemoteEventStatus
	GetMediaPlayerStateInfo
	RetMediaPlayerStateInfo
	SetMediaPlayerStateInfo
	GetPlayStatus
	RetPlayStatus
	SetCurrentPlayingTrack
	GetIndexedPlayingTrackInfo
	RetIndexedPlayingTrackInfo
	GetNumPlayingTracks
	RetNumPlayingTracks
	GetPowerBatteryState
	RetPowerBatteryState
	GetSoundCheckState
	RetSoundCheckState
	SetSoundCheckState