AU2015252154B2 - Techniques for facilitating interoperation between an accessory and multiple devices - Google Patents

Abstract

Techniques that facilitate interoperation between an accessory and multiple devices. In one set of embodiments, a device can receive, over a first communication channel of a first type, information from an accessory identifying communication channels of a second type supported 5 by the accessory. The device can further establish a connection with the accessory on a second communication channel of the second type. Upon establishment of the connection, the device can transmit over the first communication channel a notification identifying the connection on the second communication channel. Based on the notification, the accessory can determine that it is connected to the same device on the first and second communication channels and can operate 10 accordingly.

Description

2015252154 06 Nov 2015 ρ/00/011 Regulation 3.2 Australia

Patents Act 10ةة

COMPLETE SPECIFICATION STANDARD PATENT

Invention Title:

Techniques Or facilitating interoperati.n between an access.ry and multiple devices

Thef.ll.wing statement is a full description of this invention, including the best method of performing it known to us: 1

TECHNIQUES FOR FACniTATING INTEROPERATION BETWEEN AN ACCESSORY AND MULTIPLE DEVICES 2015252154 06 Nov 2015

BACKGROUND 5 1..01) The present disclosure relates in general to electronic devices that can interoperate with accessories, and in particular to techniques for resolving issues that may arise when multiple devices interact with one accessoty. 00.2؛] A portable media device generally refers to a handheld device that is capable of managing and/or playing back media assets such as audio, video, and still image files. Some 10 portable media devices, such as the iPod®, iPhone’", and iPad™ available from Apple Inc. of Cupertino, CA, can provide usere a variety of services in addhion to media management and playback. Examples of such services .include the storage of pereonal data such as calendar, contacts, and notes; Internet access: mobile telephony and videoconferencing; and the ability to selectively download and run various application programs. 15 0003؛] A portable media device typically includes a number of connectors or ports that can be used to interface witli otlier devices. For instance, one connector or port can be used to establisli a connection between the portable media device and a host computer for transferring data to/from the host computer. Another (or the same) connector or port can be used to establish a connection between the portable media device and an accessoiy device 20 (referred to herein as an accessory) for, e.g.j playing back or presenting media assets stored on the portable media device. 0004؛] Certain types of accessories are capable of (1) interfacing with a single portable media device via multiple communication cliannels and (2) interfacing with multiple portable media devices simultaneously, each via a separate communication channel. For example, one 25 type of conventional car head unit includes a physical connector for connecting with a portable media device over a wired communication channel (e.g., 30 pin serial, USB, etc.), as well as a wireless port -for connecting with the same, or a different, portable media device over a wireless communication channel (e.g., Bluetooth). 0005؛] In situations where an accessoty can potentially interface with one or several 30 portable media devices simultaneously, the accessoty may be unable to distinguish between scenarios (!) and (2) described above. For instance, in the car head unit example, when the 1Α 1001876288 2015252154 19Jul2017 including: establishing a connection to the first device over a first communication channel, ofa first type؛ transmitting, to the first device overthe first communication channel, information identifying a e.ommunication channel ofa second type and while the accessoty remains connected to the first device over the first, communication channel: supported by the acces'Sory؛ 5 transmitting, to the first device ov'er the first co'mmunication channel, an indication that the .accessory is interested in receiving notifications when the first device connects or disconnects with the accessory over the communication channel of the second type؛ detecting a connection on the communication channel of the second type؛ ..and ifa notification that the first device has connected with the accessory .over'the communication channel of the second type over the first 10 communication ch.annel has b:een received, then determining, on the basis that the notification was received, that'the accessory is connected, to the 'first device over the communication channel ofthe second typ'e, otherwise, ifa notific-ation that the first device has connected with the accessory over'the communication channel ofthe. second type over the firs.t communication channel has been'.'not been received, then determining, on the basis that n.o notification was 15 received, that the accessory .is connected to the second device over the communication channel of the second type..

[0005.1 In a fourth a.spect'.o.f the present invention there is..provided an accessory including: a fir.st communication interface of-a first fype؛. a S'econd conrmunication interface ofa second type distinct .from the first type; and a control 'Component configmed to: establish a connection to a. .20 first device via the first communication interface; transmit, to the first device via the first communication interface, a list including the second communication interface؛ teansmit, to the first device., via the first communication interface., an i'ndication that the accessory .is. interested ئ receiving notifications when the first. devi.ce. establishes or closes a connection with .the accessory via the second communication interface: detect, while the first communication interface remains 25 connected to the first deviCe, a connection on -a second .communication, 'interfac'e.' ofthe s-econd type؛' and if a notification that the .first'. devic.e has connected, with the accessory over the communication channel ofthe se.cond type overthe first communicatio'n channel has been received, then determine, on the b'asis' that a no'tification was received that the accessory is connected with the first device over the. .se'Cond .communication, inte-rface. 0.fthe second type, 30 otherwise'.', if a notification that the first devi'ce has connected with.he accessory over he communication channel ofthe seco.nd type over the fi.rst communication channel has been not been received, then determine., on the b'asis hat no notification'was recei.ved, that the accessory is connected to the second d'evi'ce over the. communication channel ofthe second type. 2Α 10.1876288 2015252154 19Jul2017 [0006] Embodiments of the present invention provide techniques that facilitate .interoperation between an accessory and multiple devices. In one set of embodiments, a device can receive., 0'ver a first communication channel ofa first type, information from an accessory identifying communication channels ,ofa second type .supported, by the .accessory. The device can firrther 5 establish a connection with tire accessory on a second communication channel of tire second type. Upon establishment oftire connection, the device can transmit over-tire firs't conrmunication channel, a notificatio.n identifyi'ng tire, connection on the second communication channel. Based on the notification,, the accessoty can detemine that it is connected to the same device on.tire first and second communication .channels and can operate accordingly. 1.0' [0007] In a further .set of embodiments, upon closure, of the connection on he second communication channel,, the device can transmit over the first conrmunication -channel a second notification to tire accessory. :Based on he second notification, he accessoty can determine that the device is. no longer connected via the second conrmunication channel..

[0008] In certain embodiments, the .accessory can detect a. connection on a second 15 communication channel of the secO'nd type. witho'Ut having received any notification's from 'the device connected via the fir.st coramunication channel. In these embodiments, tire accessoty can determine that it. is connected to 'two different devices on tire first and second communication channels- respectively. 0009] A firrther understanding of tire nature and advantages of the embodiments 'disclosed 20 Irerein can 'be realized by reference, to tire remaining portions of the specification and the: attached drawings.

BRIEF DESCRIPTION OF THE DRAWINOS

[0010] FIG. 1 is a simplified illusfration of a .system according' to an embodiment of the present, invention. 2.5' 2Β 11هها] FIG. 2 is a simplified block diagram of a system according to an embodiment ofthe present invention. 2015252154 06 Nov 2015 30 [O012J FIGS. 3 and 4 are flow diagrams of processes performed by a device configured to interoperate with an accessory accortling to an emliodiment oftlie ؛,resent invention.

[0013] FIGS. 5-7 are flow diagrams of processes perfortned by an accessory configured to interoperate W'ith a device according to an embodiment ofthe present invention.

DETAILED DESCRIPTION

[0014] In the following description, for the purposes of explanation, numerous details are set forth in order to provide an understanding of various embodiments ofthe present invention. It will be apparent, however, to one skilled in the ait that certain embodiments can be practiced without some of these details.

[0015] Embodiments ofthe present invention provide techniques that focil itete interoperation between an accessory and multiple devices. In one set of embodiments, a device can receive, over a first communication channel ofa first type, infonnation from an accessory identifying communication channels ofa second type supported by the accessoiy. The device can further establish a connection with the accessory on a second communication channel ofthe second type. Upon establishment ofthe connection, the device can bansmit over the first communication channel a notification identifying tlie connection on the second communication channel. Based on tlie notification, tlie accessory can determine that it is connected to the same device on the first and second communication channels and can operate accordingly.

[0016] In a further set ofembodiments, upon closure ofthe connection on the second communication channel, the device can transmit over the first communication channel a second notification to the accessory. Based on the second notification, the accessory can determine that the device is no longer connected via the second communication cliannel.

[0017] In certain embodiments, the accessoiy can detect a connection on a second communication cliannel oftlie second type witliotit liaving received any notifications from the device connected via tlie first communication channel. In these embodiments, tlie accessoiy can determine that it is connoted to two different devices on the first and second communication channels respectively. 3 [0018) FIG. 1 is a simplified illustration ofa system 100 according to an embodiment of the present invention. As shown, system 100 can include at least two portable media devices (PMDs) 102 and 104 and an accessoiy 106. PMDs 102 and 104 can be any type ofhandheld device that is capable of storing and playing back digital media assets such as audio, video, and/or still image files. In a particular embodiment, PMDs 102 and 104 can be an iPod , iPhone‘“, or iPad™ (available from Apple Inc. of Cupertino, CA). PMDs 102 and 104 can include a user interface comprising user input and/or output devices such as touch-screen displays 108 and 110. PMDs 102 and 104 can also include any number of other user input and/or output devices such as scroll wheels, buttons, keyboards, trackballs, touchpads, microphones, speakers, and the like. 2015252154 06 Nov 2015 [0019) PMDs 102 and 104 can provide a variety of services to a user, such as the management and playback of media assets, mobile telephonj, and Internet access (e.g., via wireless conniptions sucli as Wi-Fi and/or wireless data networks using EDGE, 3G, or LTE technology), and execution of various application programs tlrat can be install«! on PMDs 102 and 104 by the user. In certain embodiments, PMDs 102 and 104 can provide one or more services hat allow for interoperation with an accessory such as accessoiy 106.

[0020) Accessoty 106 can be any type of electronic device that is capable of communicating with PMDs 102 and 104. In FIG. 1, accessoiy 106 is depicted as a car head unit. Alternatively, accessoiy 106 can be a speaker dock, an audio/video receiver, a computing device, and/or the like. In certain embodiments, accessoiy 106 can interface with a single PMD via multiple communication channels. For instance, as shown in FIG. 1, accessoiy 106 can interface witli PMD 102 via a wired (e.g-, 30 pin serial, USB, etc.) communication channel 112 between a media device connector 114 ofPMD 102 and an accessoiy connector 116 of accessoiy 106, as well as via a wireless (e.g., Bluetooth) communication channel 118 between a wireless port/antenna 120 ofPMD 102 and a wireless port/antenna 122 of accessoiy 106. )0021) In filrther embodiments, accessoiy 106 can interface witli multiple PMDs simultaneously, each via a .separate communication channel. For instance, while accessoty 106 and PMD 102 are connected via wired communication cliannel 11.2, accessoty 106 can concurrently interface with PMD 104 via a wireless (e.g., Bluetootli) communication cliannel 124 between a wireless port/antenna 126 ofPMD 104 and wireless port/antenna 122 of accessoty 106. Although only two PMDs are depicted in FIG. 1, accessoty 106 can be c.onfigured to simultaneously interface with any number of PMDs. 4 ]0.22] In the pri.r art, accessories such as accessoty' 106 are generally unable to determine 2015252154 06 Nov 2015 whether they are connected with a single PMD via multiple communication channels (e.g.١ PMD 102) or with multiple PMDs simultaneously (e.g., PMDs 102 and 104). This can, in certain circumstances, compromise the functionality of the accessoty. For example, assume tliat accessory 106 has initially established a connection with PMD 102 on wired communication channel 112, This connection can include a control path (eg., an iPod Accessoty Protocol (iAP) path) that allows PMD 102 to transmit a user interfare to accessoty' 106 for display on an output device (e.g., output devire 128), as well as receive conttol signals (e.g. call answer, play, pause, fast forward, etc.) from accessoty 106. ]..23] Further, assume that accessoty 106 is capable of establishing (concunently with the connection over wired communication channel 112) a Bluetooth Hands-Free Profile (HFP) connection witlt eitlter PMD 102 or 104 on wireless communication channels 118 or 124 respectively. Such connections may be made to handle incoming phone calls fiom PMDs 102 or 104. Ifa Bluetootli connection is established with PMD 102 on wireless communication channel 118, it may be desirable for accessoty 106 to requesl/receive a "call answer" ttser interface from PMD 102 over wired communication channel 112 when an incoming call is detected on channel 118. Tliis would allow an end-user of accessoty 106 to answer (or reject) the call using a customized UI provided by PMD 102. If a Bluetooth connection is establislied with PMD 104 on wireless communication channel 124, it may be desirable for accessoty 106 to render its own "call answer" user interface when an incoming call is detected on channel 124, since any user interface received over wired cojnmunication channel 112 would apply solely to PMD 102 (rather tlian PMD 104).

[0024] However, since accessoty 106 cannot distinguisli bertveen a Bluetooth connection that is established on communication channel 118 versus a Bluetooth connection tlrat is established on communication cliannel 124, accessoty 106 cannot properly determine which course of action to take (and accordingly may take the wong course of action). For instance, ifa Bluetooth connection is established on wireless communication channel 124 (thereby connreting accessoty 106 to PMD 104) and an incoming call is detected on the connection, the accessoty may erroneously assume that the call originated from PMD 102 and request/waitfora "call answer” UI from PMD 102 over wired communication channel 112 (rather than rendering its own user interfece for liandling the call with respect to PMD 104).

[0025] Embodiments oftlie present invention address the foregoing issue (and other issues) by enabling accessoty 106 and PMD 102 to exchange infornration over a first communication clramrel of a first type (e.g., wired communication channel 112) that notifies accessoty 106 5 whenever PMD 102 connects with accessoiy 106 on a second communication channel of a second type (eg, wireless communication cliannel 118). For instance, upon esteblishing a connection with PMD 102 on wired communication channel 112, acccssoiy 106 can transmit to PMD 102 (over channel 112) inforjnation identifying Bluetooth channels supported by accessory 106. In one set of embodiments, the information can include, e.g.١ a list of Bluetooth MAC addresses, where at least one address in the list is associated with wireless communication channel 118- PMD 102 can then transmit a notification to accessory 106 over wired communication channel 112 whenever it establishes a Bluetooth connection with accessory 106 on wireless communication cliannel 118. Based on this infomation, accessory 106 can determine that communication channels 112 and 118 lead to the same device (PMD 102) and can make informed decisions about how to interoperate with PMD 102. 2015252154 06 Nov 2015 0026؛] In certain embodiments, if PMD 102 subsequently closes the Bluetooth connection on wireless communication channel 118, PMD 102 can transmit a second notification to accessory 106 over wired communication channel 112 indicating that the connection has been closed. Accessoiy 106 can then detennine that it is no longer connected to PMD 102 on wireless communication channel 118. ؛0027؛ In embodiments where PMD 104 (ratlrer tlian PMD 102) esteblishes a Bluetooth connection with accessoiy 106 (on, e.g., wireless communication channel 124), accessoiy 106 wil.1 not receive any notifications from PMD 102 over wired communication channel 112. In tliese situations, accessory 106 can determine, based on the absence of notifications over wired communication channel 112, that it is connected to two different devices on communication channels 112 and 124 respectively, and can interoperate with tlie devices accordingly. Additional details regarding the processing that can be perfomed by PMD 102 and/or accessoiy 106 to achieve the foregoing fiinctionalify is described with respect to FIGS. 3-7 below. 0028؛] It sliould be appreciated tliat system 100 is illustrative and not intended to limit embodiments of the present invention. ,For example, although communication channels 112 and 118 are described as wired and wireless clianriels respectively', in various embodiments they botli can be wired or wireless. Furtlier, a variety of different types ofPMDs and accessories can be used. One of ordinary skill in the art will recognize other variations, modifications, and alternatives. 0029؛] FIG. 2 is a simplified block diagram of a system 200 according to an embodiment of tlie present invention. As shown, system 200 can incltide at least two PMDs 202 and 204 and 6 an accessoiy 206. In one set of embodiments, system 200 can implement system 100 ofFIG. 2015252154 06 Nov 2015 1. For example, PMD 202 can implement PMD 102, PMD 204 can implement PMD 104, and accessoiy 206 can ijnplement accessoty 106.

[.030) PMDs 202 and 204 can each include a processor 208,216, user input/output devices 210, 218, a storage device 212, 220, and an accessoiy 1/0 (input/output) interface 214, 222. [0031] Processors 208 and 216 can be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. In a particular embodiment, processors 208 and 216 can be microprocessors that use the ARM architeture (a RISC architecttire designed by .ARM Limited). Processors 208 and 216 can be responsible for cariying out one or more operations of PMDs 202 and 204 respectively- For example, processors 208 and 216 can select and play media assets or execute various application programs stored in storage devices 212 and 220. Processors 208 and 216 can also manage communication with accessories (e.g., accessoiy 206) via accessoiy I/O interfaces214and 222.

[«132] User input/output devices 210 and 218 can be any ofa number of devices that allow a user to interact with PMDs 202 and 204. For example, as discussed with respect to FIG. 1, such user input/output devices can include scroll wheels, buttons, keyboards, trackballs, microphones, speakere, touch-screen displays, and so on. In various embodiments, a user can operate a particular user input device 210 or 218 to invoke tlie functionality ofPi 202 or 204. In addition, a user can view and/or hear output from PMD 202 or 204 via a particular user output device 210 or 218.

[0033] Storage devices 212 and 220 can be implemented, for example, using magnetic disk, flash memoiy, and/or any other non-volatile storage medium. In some embodiments, storage devices 212 and 220 can include non-removable storage components such as a non-removable hard disk drive or flaslt memory drive. In otlier embodiments, storage devices 212 and 220 can include removable storage media such as flash memory cards. Storage devices 212 and 220 can provide storage for any programs and/or data used by PMDs 202 and 204. For example, storage devices 212 and 220 can store media assets such as audio, video, still images, or the like, and associated metadata (e.g.j asset name, artist, title, genre, playlists, etc.). Storage devices 212 and 220 can also store information other titan media assets, such as information about a user’s contacts (names, addresses, phone numbers, etc.); scheduled appointments and events; notes; and/or other personal information. In still otlier embodiments, storage devices 212 and 220 can store one or more programs to be executed by processors 208 and 216, such as video game programs, personal information management 7 programs, programs for playing media assets and/or navigating a media asset database, and so on. 2015252154 06 Nov 2015 0034؛] Accessoiy 1/0 interfaces 214 and 222 can include a number of signal paths configured to carry various signals between PMDs 202,204 and accessoiy 206. In one set of embodimente, accessoiy I/O interfaces 214 and 222 can each include one or more wired interfaces such as the 30-pin serial connector used on die iPod®, iPhone™, and iPad . Alternatively or additionally, accessoiy I/O interfaces 214and 222 can each include one or more wireless interfaces (e.g., Bluetooth or the like). In certain embodiments, accessoty I/O interfaces 214 and 222 can each support multiple concurrent connections between PMDs 202, 204 and accessoiy 206. For example, as shown in FIG. 2, PMD 202 can connect with accessory 206 via communication channels 224 and 226, and PMD 204 can connect with accessoty 206 via communication channel 228. Although only three ctiannels are depicted, any number of communication cliannels between PMDs 202, 204 and accessor 206 can be supported. 0.35؛] Accessoiy 206 can include a controller 230, a PMD I/O interface 232, and user input/output devices 234. 0036؛] Controller 230 can be implemented as one or more integrated circuits, such as a microprocessor or microcontroller. In various embodiments, controller 230 can control the operation of accessoiy 206. Controller 230 can also manage communication with PMDs 202 and 204 via PMD I/O interface 232.

[0037؛ User input/output devices 234 can be any ofa number of devices that allow a user to interact with accessoiy 206. Such user input/output devices can include scroll wheels, buttons, keyboards, trackballs, microplrones, speakers, touch-screen displays, and so on. Ι,η various embodiments, the user can view and/or hear output ftom PMDs 202, 204 that is routed to accessoiy 206 via a particular user output device 234. 0038؛] PMD I/O interface 232 can include a number of signal patlis configured to carry various signals between accessoiy 206 and PMDs 202, 204. In one set of embodiments, PMD I/O interface 232 can include one or more wired interfaces such as tlie 30-pin serial connector used on tlie iPod®, iPhone'M, and iPad . Alternatively or additionally, PMD 1/0 interface 232 can include one or more wireless interfaces (e.g.١ Bluetootli or the like). 0039؛] In various embodiments, PMD 1/0 interface 232 and accessory I/O interlaces 214, 222 can allow accessoty 206 and PMDs 202, 204 to be in a “connected” or “disconnected” 8 state. As used herein, accessory 206 and PMD 202/204 are connected whenever a connection between PMC 1/0 interface 232 and accessory 1/0 interface 214/222 is established (over, e.g.j communication channel 224/226/228). Conversely, accessoiy 206 and PMD 202/204 are disconnected whenever the connection is closed. Connection can be achieved by physical attachment (e.g., bettveen respective mating connectors of accessoiy 206 and PMC 202/204), by an indirect connection such as a cable, or by establishment of a wiieless connection. Similarly, disconnection can be acliieved by physical detachment, disconnecting a cable, powering down accessoty 206 or PMD 202/204, or closing the wireless connection. 2015252154 06 Nov 2015 [0040] A variety of connections bettveen PMD I/O interface 232 and accessoiy 1/0 interfaces 214 and 222 can be used, including wiled connections such as 30 pin serial, USB, FireWire, or universal asynchronous receiver/transmitter (“HART”), and wireless connections such as Bluetootli, WiFi, infrared, or tlie like. As noted above, in certain embodiments multiple connections can be established concurrently between accessoiy 206 and PMDs 202 and 204 (over, e.g., communication channels 224, 226, and 228).

[0041] It should be appreciated tliat system 200 is illustrative and not intended to limit embodiments oftlie present invention. For example, PMDs 202, 204 and accessory 206 may each have other capabilities or include other components that are not specifically described. One ofoidinaiy/ skill in tlie art will recognize other variations, modifications, and alternatives.

[0042] In one set of embodiments, PMDs 202, 204 and accessory 206 can communicate by exchanging commands and data according to a communications protocol. An example of such a protocol is the iPod® Accessory Protocol (iAP) developed by Apple Inc. According to one aspect, the protocol can define a format for messages transmitted bettveen PMD 202/204 and accessoiy 206. For instance, the protocol can specify that each message is sent in a packet witli a lieadei' and an optional payload. The header can provide basic inlOrmation such as a start indicator, lengtli ofthe packet, and a command to be processed by the recipient.

The payload can provide data associated with the command. In some embodiments, tlie amount of associated data can be different for different coirunands, and some commands can provide for variable-length payloads.

[0043] According to anotlier aspect, tlie protocol can define a number of “lingoes,” where a "lingo" refers generally to a group of related commands. In one embodiment, a command can be uniquely identified by a first byte identifying the lingo to which the command belongs and a second byte identifying the particular command within the lingo. Other command 9 structures may also be used. It is not required that all accessories, or all PMDs to which an accessory can be connected, support every lingo defined within the protocol or eveiy command ofa particular lingo (for instance, different devices might use different versions of a given lingo). 2015252154 06 Nov 2015 [.044] In one set of embodiments, the protocol carr include a general lingo that enables certain core communication functions between PMD 202/204 and accessory 206. For example, the general lingo can include commands enabling PMD 202/204 and accessory 206 to identify themselves to each other and to provide information about their respective capabilities, including which (if any) otlier lingoes each supports and which capabilities of the other device eacli intends to use while connected. The general lingo can also include authentication commands that PMD 202/204 can use to verify the purported identify and capabilities ofaccessofy 206 (or vice versa). In some cases, accessofy 206 (or PMD 202/204) can be blocked from invoking certain commands or lingoes if file authentication is unsuccessful.

[0045] In further embodiments, the protocol can include one or more accessofy lingoes that are used to support communication between a PMD anil va.rious different clasps of accessories. Examples of such accessofy lingoes include an RE tuner lingo, a remote control lingo, an extended interface lingo, and so on.

[0.46] In certain embodiments, the general lingo described atove can يخل extended to facilitate interoperation between accessofy 206 and multiple PMDs (e.g., 202 and 204) according to various embodiments disclosed herein. Tlie commands that can be part of til is extension are discussed in greater detail with respect to FIGS. 3-7 below.

[0047] It should be appreciated that the protocol and associated lingoes/commands described above are illustrative and not intended to limit embodiments of the present invention. For example, some ofthe commands, can be replaced witli other commands or a combination of commands. Further, some oftlie lingoes and/or commands may not be supported by particular PMDs or accessories. One of ordinaiy skill in the art will recognize other variations, modifications, and alternatives.

[0048] Furtlier it should be appreciated that tlie phrases ‘‘sending a cominaiid” and “receiving a command" can be interpreted broadlj, to include any exchange of commands. Tlius, wliile the term “command" is sometimes used for a low-level atomic transaction, it can also be used to refer to liigh-level operations that include multiple low-level commands. 10 1..49] As described above, embodiments of the present invention provide techniques for facilitating interoperation between an accessofy (e.g., accessoty 206 ofFIG. 2) and multiple PMDs (e.g., PMDs 202 and 204 ofFIG. 2). In one set of embodiments, a PMD can receive, over a first communication channel ofa first type, information from an accessory identifying communication channels ofa second type supported by tlie accessoiy. Tlie PMD can fijrther establish a connection with the accessoiy on a second communication channel of the second type. Upon establishment ofthe connection, the PMD can transmit over the first communication channel a notification identifying the second communication channel. Based on the notification, tlie accessoiy can determine that it is connected to the same PMD on the first and second communication channels and can operate accordingly. 2015252154 06 Nov 2015 [0050] If the accessory detects a connection on a second communication channel O'fthe second fype without having received any notifications from the PMD connected via the first communication channel, the accessoiy can determine tliat it is connected to two different PMDs on tlie first and second communication channels respectively.

[0051] FIG. 3 is a flow diagram ofa process 300 that can be performed by PMD 202 upon connecting with accessoiy 206 via a first communication cliannel ofa first fype according to an embodiment of tlie present invention. In a particular embodiment, portions of process 300 can be performed by PMD 202 as part of an initialization sequence prior to engaging in normal operation with accessory 206. Process 300 can be implemented by PMD 202 in hardware, software, or a combination thereof. As software, process 300 can be encoded as program code stored on a machine-readable storage medium. 1.052] At block 302, PMD 202 can establisli communication with accessofy 206 on a first communication channel ofa first fype. In various embodiments, tlie first cliannel fype can be a wired channel fype (e.g., 30 pin serial, USB, etc.) or a wireless (e.g., WiFi, infrared, radio frequency, etc.) channel fype. In a particular embodiment, the first cliannel type can be configured to pass control signals between PMD 202 and accessoiy 206 according to an accessoiy control protocol, such as iAP. ]0053] At block 304, PMD 202 can receive, over the first communication channel, accessofy capability information from accessofy 206. For example, PMD 202 can receive information indicating whether accessofy 206 is capable of providing status information identifying communication channels ofa second fype suppoited by the accessofy. In various embodiments, the second channel fype can be distinct from the first channel fype described 11 with respect to block 302. In a particular embodiment, the second channel type can be a wireless channel type that uses Bluetooth protocol. 2015252154 06Nov2015 [0054] If the capability information rereived at blrek 304 indicates that accessory 206 is capable of providing status information identitying communication channels of a second type supported by the accessoty, PMD 202 can transmit an indication over the first communication channel that PMD 202 is interested in receiving the status information (block 306). In one set of embodiments, this can include sending a SetAccStatusNotification command that includes a parameter specifying that PMD 202 is interested in receiving notification about Bluetooth connretions from accessoty 206.

[.055] PMD 202 cn then receive, over the first communication channel, the status information identifying communication channels of the second type supported by accessoty 206 (blrek 308). In one set of embodiments, this can include receiving an AccessoryStatusNotification command dial includes a list of communication cliannel identifiers. In embodiments where tlie second channel type is Bluetooth, the status information received at block 308 can include, inter alia, one or more Bluetooth MAC addresses that are available for establisliing Bluetooth connections with accessoty 206. Alternatively, the status information can include any other type of information (e.g., names, identifiers, etc.) sufficient to uniquely identify communication channels of the second type.

[0056] In addition to receiving the status information at block 308, PMD 202 can, in certain embodiments, receive an indication over the first communication cliannel that the accessoty is interested in ]-eceiving notifications when PMD 202 connects or disconnects witli the accessoty over any communication channel of the second type. In one set of embodiments, tliis can include receiving a SetEventNotification command with a parameter (e.g., a bihnask) that identifies that the accessoty is interested in receiving notifications wlienever there is a connection 01. disconnection of the second channel type. In effect, tliis command is sent by accessoty 206 when it wishes to register with PMD 202 to receive connect/disconnect notifications regarding channels oftlie second type.

[0057] Subsequent to blocks 302 through 310, PMD 202 and accessoty 206 can interoperate over die first remmunication channel based on the functionality provided by the accessoty. At some point, PMD 202 can establish a connection with accessoty 206 on a second communication channel of die second type, while PMD 202 is still connected to tlie accessoty over the first communication channel (block 312). For example, tliis can include 12 establishing a Bluetooth HFP connection with accessory 206 over a Bluett»،! communication channel. 2015252154 06 Nov 2015 [.058] Upon establishing the connection on tile second communication channel, PMD 202 can transmit, over the firet communication channel, a notification indicating that the connection has been established (blwk 314). In one set of embodiments, this can include transmitting an iPodNotification comnrand with, e.g., a parameter that identifies the second channel type (e.g., Bluetooth), a parameter that identifies the connection on the second communication channel (e.g., a Bluetooth MAC address), and a parameter that specifies a “connect" event lias occurred. As described with respect to FIG. 6 below, accessoiy 206 can use this information to determine that the same PMD (i.e., PMD 202) is connected with the accessory over both the first and second communication channels.

[0059] FIG. 4 is a flow diagram ofa process 400 tliat can be performed by PMD 202 subsequent to process 300 ofFIG. 3 according to an embodiment of the present invention. Like process 300, process 400 can be implemented by PMD 202 in hardware, software, or a combination tliereof. As software, process 300 can be encoded as program code stored on a machine-readable storage medium.

[0060] At block 402, PMD 202 can close the connection established at block 312. PMD 202 can then transmit, over tlie first communication channel, a second notification indicating that the connection on the second communication channel has been closed (block 404). In one set of embodiments, this can include transmitting tlie same iPodNotification command sent at block 314, but witli a parameter specifying that a “disconnect" event (ratlier than a “connect" event) has occuired. Accessory 206 can use this information to determine that PMD 202 is no longer connected via the second communication channel.

[0.61] Once the second notification has been sent, PMD 202 can continue to monitor for connections/disconnections to accessoiy 206 on communication c.liannels of the second fype, and can transmit notifications to accessoiy 206 over the first communication channel as appropriate. This can continue indefinitely until, for example, the first communication channel becomes disconnected, or until PMD 202 is powered off or placed in a suspended/sleep state. 1.062] It should be appreciated that processes 300 and 400 are illustrative and that variations and modifications are possible. For example, in some embodiments, PMD 202 may already be connects with accessory 206 via a second communication channel of the second fype wlien the AccessoryStatusNotification command is received at block 310. In 13 ؛hese embodiments, PMD 202-can send the notification ofblock 314 immediately after block 310. Further, steps described as sequential may be executed in parallel, order of steps may be varied, and steps may be modified, combined, added, or omitted. One of ordinal skill in the art will recognize other variations, modifications, and alternatives. 2015252154 06 Nov 2015 [.063, FIG. 5 is a flow diagram of a process 500 that can be performed by accessory 206 upon connecting witlr PMD 202 via a first communication channel of a first type according to an embodiment ofthe present invention. In one set of embodiments, process 500 can be performed by accessory/ 206 while process 300 ofFIG. 3 is being performed by PMD 202. In a particular embodiment, process 500 can be performed by accessoty 206 as part of an initialization sequence prior to engaging in normal operatioir with PMD 202. Process 500 can be implemented by accessory/ 206 in hardware, sofovare, or a combinatiorr tliereofi As software, process 500 cair be encoded as program code stored on a macltine-readable storage medium.

[0064] At block 502, accessory 206 can establish communication wifti PMD 202 on a first commurrication charrnel of a first type. In various embodiments, the first channel type can be a wired channel type (e.g.١ 30 pin serial, USB, etc.) or a wireless (e.g., WiFi, infrared, radio frequency, etc.) channel type. In a particular embodiment, the first channel type can be configured to pass control signals between accessory/ '206 and PMD 202 according to an accessory confrol protocol, such as iAP.

[0065] At block 504, accesso^/ 206 can transmifl over the first communication channel, accessoty capability irrformation to PMD 202. For example, accessoty 206 can transmit information indicating whether accessoty 206 is capable of providing status information identifying communication channels of a second type supported by the accessory. In various embodiments, the second channel type can be distinct from the first channel type described with respect to block 502. In a particular embodiment, the second channel type can be a wireless channel type that uses Bluetooth protocol.

[0066] If accessoty 206 is capable of providing statrts information identifying communication channels of a second type supported by the accessoty, accessoty 206 can receive, over the first communication channel, an indication that PMD 202 is interested in receiving the stattrs information (block 506). In one set of embodiments, this can include receiving the SetAccStatusNotification command described with respect to block 306.

[0067] Accessory 206 can then transmit over the first communication cliannel the requested status information (block 508). In one set of embodiments, this can include transmitting the 14

AccessoryStaiiNotification command described with respect to block 308. In embodiments where the second channel type is Bluetooth, the status information sent at block 308 can include, inter alia, one or more Bluetooth MAC addresses that are available 'for establishing Bluetooth connections with accessoty 206. Alternatively, the status information can include any other type of infomration (e.g., names, identifiers, etc.) sufficient to uniquely' identify communication channels of the second type. 2015252154 06 Nov 2015 [0068] In addition to transmitting the stattis information at block 508, accessoty 206 can, in certain embodiments, transmit an indication over the first communication channel that tlie accessoty is interested in receiving notifications when PMD 202 connects or disconnects witli the accessoty over any communication channel of tire second type. In one set of embodiments, this can include transmitting the SetEventNotification command described with respect to block 310. In effect, this command is sent by accessoty 206 when it wishes to register with PMD 202 to receive connect/disconnect noti'fications regarding clrannels of the second type.

[0069] FIGS. 6 and 7 are flow diagrams of processes 600 and 700 that can be performed by accessoty 206 subsequent to process 500 of FIG. 5 according to an embodiment of the present inventioit. In particular, process 600 can be performed when a connection is established on a second communication channel of the second type between accessoty 206 and PMD 202, and process 700 can be performed when a connection is established on a second comtnunicatiotr channel of the second type between accessory 206 and a different PMD than PMD 202 (e.g., PMD 204). Like process 500, processes 600 and 700 can be implemented by accessoty' 206 in hardware, software, or a combination tliereof. As software, processes 600 and 700 can be encoded as program code.stored ott a machine-readable storage medium.

[0070] With respect to process 600, accessoty 206 can receive over the first c.ommunication channel a notification indicating that a connection has been established 0I١ a second communication channel ofttie second type between accessoty 206 and PMD 202 (block 602). Ill one set of embodiments, lliis can include receiviirg the iPodNotificatinn command described witti respect to block 314 ofFIG. 3.

[0.71] At block 604, accessoty 206 can use the information in the notification to determine diat the same PMD (i.e., PMD 202) is c.onnected with the accessoty over boll, die first and second communication channels. Accessoty 206 can then make intelligent decisions about its interoperation with the PMD. For instance, returning to the example ofFIG. I, accessoty 15 -106 can determine (using process 600) that it is connected with a singJe Pi (PMD 102) over both wired communication channel 112 and wireless (eg., Bluetooth) communication channel 118. Accordingly, when an incoming call is detected on channel 118, aecessoiy 106 can request/receive an appropriate "call answer" user interface from PMD 102 over wired 5 communication channel 112, and can present that UI on output device 128. 2015252154 06 Nov 2015 [0072J Alternatively, with respect to process 700, accessory 206 can detect a connection,on a second communication channel of the second type, without having received any notifications from PMD 202 over the first communication channel (block 702). For example, the connection may have been estoblished by a different PMD than 202 (eg., PMD 204). In 10 this scenario, accessory 206 determine tliat it is conne.cted to two different devices (e.g., 202 and 204) on the first and second communication channels respectively, and can make intelligent decisions about its interoperation with the two devices (block 704). For instance, returning to the example of FIG. 1, accessory 106 can determine (using process 700) that it is connected to PMD 102 over wired communication channel 112 and with a different PMD 15 (PMD 104) over wireless (e.g., Bluetooth) communicatiorr channel 124. Accordingly, when an incoming call is detected on channel 124, accessory 106 can render its own "call answeri’ user interface for handling the call with respect to PMD 104 (rather than requesting/receiving a user interface from PMD 102 over wired communication channel 112). 0073؛] It should be appreciated that processes 500, 600, and 700 are illustrative and that 20 variations and modifications are possible. For example, in certain embodiments of process 600, accessoty 206 can further receive a second notification over the first communication cliannel indicating that the connection on the second communication channel has been closed. Accessory 206 can then determine tliat PMD 202 is no longer connected via tire second communication channel. Further, steps described as sequential may be executed in parallel, 25 order of steps may be varied, and steps may be modified, combined, added, or omitted. One of ordinary skill in the art will recognize other variations, modifications, and alternatives. 1.074] While the invention has been described witli respect to specific embodiments, it should be appreciated that nirmerous modifications are possible. In some embodiments, 30 circuits, processors, and/or other components of a PMD and/or accessoty may be configured to perform various operations described lrerein. Those skilled in tire ait will appreciate that, depending on implementation, such configuration can be accomplished through design, setup, interconrrection, and/or programming of the particular components and that, again depending 16 on implementation, a configured component might or might not be reconfigurable for a different operation. For example, a programmable processor can be configured by providing suitable executable code; a dedicated logic circuit can be con-figured by suitably connecting logic gates and other circuit elements; and so on. Further, while the embodiments described above may make reference to specific hardware and software components, those skilled in the art will appreciate that different combinations of hardware and/or software components may also be used and that particular operations described as being implemented in hardware can also be implemented in software or vice versa. 2015252154 06Nov2015 [0075) Computer programs incorporating some or all features described lrerein may be encoded on various machine-readable storage media; suitable media include magnetic disk (including hard disk) or tape, optical storage media such as compact disk (CD) or DVD (digital versatile disk), fiash memoiy, and the like. Machine-readable storage media encoded with the program code may be packaged witli a compatible device or provided separately from other devices. In addition, program code may be encoded and transmitted via wired, optical, and/or wireless networks confoming to a variety of protocols, including the Internet, thereby allowing distribution, e.g., via Internet download.

[0.76] Thus, although the invention lias been described with respect to specific embodiments, it will be appreciated that the invention is intended to cover all modifications and equivalents within the. scope of the following claims. 17

Claims (20)

1. The claims defining the invention are as follows:

   1. A method performed by an accessory configured to interoperate with a first device and a second device, the method including: establishing a connection to the first device on a first communication channel of a first type; transmitting, to the first device over the first communication channel, information identifying a communication channel of a second type supported by the accessory; transmitting, to the first device over the first communication channel, an indication that the accessory is interested in receiving notifications over the first communication channel when the first device connects or disconnects with the accessory over the communication channel of the second type; and while the accessory remains connected to the first device over the first communication channel: detecting a connection on the communication channel of the second type, without having received a notification from the first device over the first communication channel; and determining, on the basis that no notification was received from the first device that the accessory is connected with the second device over the communication channel of the second type.
2. 2. The method of claim 1 further including: receiving, from the first device over the first communication channel, a first notification indicating that the device has established a connection with the accessory on the second communication channel of the second type.
3. 3. The method of claim 2 further including, subsequent to receiving the first notification: determining that a single device is connected to the accessory on both the first and second communication channels.
4. 4. The method of claim 2 further including, subsequent to receiving the first notification: receiving, from the first device over the first communication channel, a second notification indicating that the connection has been closed.
5. 5. The method of claim 1 further including, prior to transmitting the information identifying the communication channels of the second type: transmitting, to the first device over the first communication channel, an indication that the accessory is capable of providing the information identifying the communication channels of the second type; and receiving, from the first device over the first communication channel, an indication that the first device is interested in receiving the information.
6. 6. The method of claim 1 wherein the first type is a wired communication channel type and the second type is a wireless communication channel type.
7. 7. The method of claim 1 wherein the accessory is a car head unit.
8. 8. An accessory including: a first communication interface of a first type; a second communication interface of a second type distinct from the first type; and a control component configured to: establish a connection to a first device via the first communication interface; transmit, to the first device via the first communication interface, a list including the second communication interface; transmit, to the first device via the first communication interface, an indication that the accessory is interested in receiving notifications when the first device establishes or closes a connection with the accessory via any of the one or more second communication interfaces; detect, while the first communication interface remains connected to the first device, a connection on a second communication interface of the second type, without having received a notification from the first device over the first communication interface; and determine, on the basis that no notification was received from the first device that the accessory is connected with a second device over the second communication interface of the second type.
9. 9. The accessory of claim 8 wherein the control component is further configured to: receive, from the first device via the first communication interface, a notification indicating that the device has established a connection with the accessory on one of the one or more second communication interfaces.
10. 10. The accessory of claim 8 wherein the first type is a wired interface type and wherein the second type is a wireless interface type.
11. 11. The accessory of claim 8 wherein the accessory is a car head unit.
12. 12. A method performed by an accessory configured to interoperate with a first device and a second device, the method including: establishing a connection to the first device over a first communication channel of a first type; transmitting, to the first device over the first communication channel, information identifying a communication channel of a second type supported by the accessory; transmitting, to the first device over the first communication channel, an indication that the accessory is interested in receiving notifications when the first device connects or disconnects with the accessory over the communication channel of the second type; and while the accessory remains connected to the first device over the first communication channel: detecting a connection on the communication channel of the second type; and if a notification that the first device has connected with the accessory over the communication channel of the second type over the first communication channel has been received, then determining, on the basis that the notification was received, that the accessory is connected to the first device over the communication channel of the second type, otherwise, if a notification that the first device has connected with the accessory over the communication channel of the second type over the first communication channel has been not been received, then determining, on the basis that no notification was received, that the accessory is connected to the second device over the communication channel of the second type.
13. 13. The method of claim 12 further including, subsequent to receiving the first notification: determining that a single device is connected to the accessory on both the first and second communication channels.
14. 14. The method of claim 12 further including, subsequent to receiving the notification: receiving, from the first device over the first communication channel, a second notification indicating that the connection has been closed.
15. 15 . The method of claim 12 further including, prior to transmitting the information identifying the communication channels of the second type: transmitting, to the first device over the first communication channel, an indication that the accessory is capable of providing the information identifying the communication channels of the second type; and receiving, from the first device over the first communication channel, an indication that the first device is interested in receiving the information.
16. 16. The method of claim 12 wherein the first type is a wired communication channel type and the second type is a wireless communication channel type.
17. 17. The method of claim 12 wherein the accessory is a car head unit.
18. 18. An accessory including: a first communication interface of a first type; a second communication interface of a second type distinct from the first type; and a control component configured to: establish a connection to a first device via the first communication interface; transmit, to the first device via the first communication interface, a list including the second communication interface; transmit, to the first device via the first communication interface, an indication that the accessory is interested in receiving notifications when the first device establishes or closes a connection with the accessory via the second communication interface; detect, while the first communication interface remains connected to the first device, a connection on a second communication interface of the second type; and if a notification that the first device has connected with the accessory over the communication channel of the second type over the first communication channel has been received, then determine, on the basis that a notification was received that the accessory is connected with the first device over the second communication interface of the second type, otherwise, if a notification that the first device has connected with the accessory over the communication channel of the second type over the first communication channel has been not been received, then determine, on the basis that no notification was received, that the accessory is connected to the second device over the communication channel of the second type.
19. 19. The accessory of claim 18 wherein the first type is a wired interface type and wherein the second type is a wireless interface type,
20. 20. The accessory of claim 18 wherein the accessory is a car head unit.