BLUETOOTH DOC
`Prepared
`Audio Video WG
`
`
`
`Approved
`Date / Year-Month-Day
`Adopted
`2007-04-16
`e-mail address
`avv-feedback@bluetooth.org
`
`Revision
`V13
`
`Document No
`AVRCP_SPEC
`N.B.
`
`
`AUDIO/VIDEO REMOTE CONTROL PROFILE
`
`Abstract
`This profile defines the requirements for Bluetooth® devices
`necessary for the support of the Audio/Video Remote Control
`usage case. The requirements are expressed in terms of end-
`user services, and by defining the features and procedures that
`are required for interoperability between Bluetooth devices in
`the Audio/Video Remote Control usage case.
`
`
`
`Exhibit 1029
`Page 01 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 2 of 93
`
`March 2002
`0.95b
`May 2002
`Voting Draft 1.00
`Voting Draft 1.00 a February 2003
`Version 1.0
`May 2003
`Version 1.1 RC1
`August 2003
`Version 1.1 RC2
`August 2003
`Version 1.1 RC3
`October 2003
`Version 1.1 RC4
`October 2003
`D13r00
`15 Aug 2005
`D13r01
`18 April 2006
`D13r02
`15 May 2006
`
`16th May 2006
`
`12th June 2006
`23rd June 2006
`05 October 2006
`
`D13r03
`
`D13r04
`D13r05
`D13r06
`
`D13r07
`
`Revision History
`Comments
`Revision
`Date
`Release to Associates
`0.5
`April 2001
`Release to Associates
`0.7
`June, 2001
`0.9
`September, 2001 Release to Associates and Early Adopters
`Voting Draft 0.95
`October, 2001
`Release to Associates and Early Adopters
`Voting Draft 0.95 a February 11, 2002 Release to Associates and Early Adopters, small clarifications
`based on IOP and feedback.
`Adopted 0.95
`Release for Voting Draft
`Release for Voting Draft
`Title and header changed
`Updated to support and use Bluetooth Core 1.2
`Chapter 2.4 identifies useful services in BT 1.2
`Contributor list updated
`AV/C reference updated
`Updated for core release v1.2 or later
`Updated with Metadata Transfer FIPD content
`Updated
`SDP
`record,
`InformDisplayableCharacterSet
`comments and specific Metadata Transfer
`introduction
`comments from the AV WG members
`Updated with Patric’s description of Basic Group Navigation.
`Misc. editorial comments
`Updated with Laurent’s PDU examples and Section 5.5
`Updated with new timers for metadata transfer and minor edits
`Converted into a Voting Draft for Metadata Transfer; included
`Issues 1894, 1895, 1896, 1897, 1898, 1899, 1900, 1901,
`1902, 1903, 1904
`14th October 2006 Updates during F2F meeting: included issues on interleaving
`commands and clarified RequestContinue PDU ID usage;
`included Assigned Numbers dependencies and Reference;
`repaired the Reference section; some editorial and cosmetic
`updates; updated contributor list; reformatted and added
`captions to tables in chapter 5; repaired links within document
`30th October 2006 Update after comment from BARB: Included reference to AV/C
`31st October 2006 Update after further comments from BARB: removed last
`paragraph in section 1.1; corrected spellings
`Incorporate errata 2077 and 2079
`Prepare for adoption
`
`28 February 2007
`16 April 2007
`
`D13r08
`D13r09
`
`D13r10
`V13
`Contributors
`Name
`Alexander Hanke
`Ash Kapur
`Rüdiger Mosig
`Gordon Downie
`Souichi Saito
`Morgan Lindqvist
`Wim Koster
`Rene Kuiken
`
`Company
`Audi
`Broadcom
`BMS
`CSR
`Denso
`Ericsson
`Ericsson
`Ericsson
`
`16 April 2007
`
`Exhibit 1029
`Page 02 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 3 of 93
`
`Masahiko Nakashima
`Baskar Subramanian
`K.A Srinivasan
`Ilya Goldberg
`Tsuyoshi Okada
`Thomas Karlsson
`Jurgen Schnitzler
`Kalervo Kontola
`Martti Niska
`Thomas Block
`Vesa Lunden
`Sebastien Henrio
`Erik Schylander
`Shaun Barrett
`Christian Bouffioux
`Geert Knapen
`Emmanuel Mellery
`Laurent Meunier
`Scott Walsh
`Dmitri Toropov
`Masakazu Hattori
`Harumi Kawamura
`Rudiger Mosig
`Yoshiyuki Nezu
`Hiroyasu Noguchi
`Tomoko Tanaka
`Atsushi Ichise
`Wilhelm Hagg
`Masahiko Seki
`Dick de Jong
`Patric Lind
`Siân James
`Junko Ami
`Yoshiaki Takabatake
`Ichiro Tomoda
`Makoto Kobayashi
`Shuichi Sakurai
`Makoto Yamashita
`
`Fujitsu
`Impulsesoft
`Impulsesoft
`Matsushita
`Matsushita
`Mecel
`Nokia
`Nokia
`Nokia
`Nokia
`Nokia
`Parrot
`Philips
`Philips
`Philips
`Philips
`Philips
`Philips
`Plantronics
`Siemens
`Sony
`Sony
`Sony
`Sony
`Sony
`Sony
`Sony
`Sony
`Sony
`Sony Ericsson
`Sony Ericsson
`Symbian
`Toshiba
`Toshiba
`Toshiba
`Toshiba
`Toshiba
`Toshiba
`
`16 April 2007
`
`Exhibit 1029
`Page 03 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 4 of 93
`
`Disclaimer and Copyright Notice
`The copyright in this specification is owned by the Promoter Members of Bluetooth® Special Interest Group
`(SIG), Inc. (“Bluetooth SIG”). Use of these specifications and any related intellectual property (collectively, the
`“Specification”), is governed by the Promoters Membership Agreement among the Promoter Members and
`Bluetooth SIG (the “Promoters Agreement”), certain membership agreements between Bluetooth SIG and its
`Adopter and Associate Members (the “Membership Agreements”) and the Bluetooth Specification Early
`Adopters Agreements (1.2 Early Adopters Agreements) among Early Adopter members of the unincorporated
`Bluetooth SIG and the Promoter Members (the “Early Adopters Agreement”). Certain rights and obligations of
`the Promoter Members under the Early Adopters Agreements have been assigned to Bluetooth SIG by the
`Promoter Members.
`Use of the Specification by anyone who is not a member of Bluetooth SIG or a party to an Early Adopters
`Agreement (each such person or party, a “Member”), is prohibited. The legal rights and obligations of each
`Member are governed by their applicable Membership Agreement, Early Adopters Agreement or Promoters
`Agreement. No license, express or implied, by estoppel or otherwise, to any intellectual property rights are
`granted herein.
`Any use of the Specification not in compliance with the terms of the applicable Membership Agreement, Early
`Adopters Agreement or Promoters Agreement is prohibited and any such prohibited use may result in
`termination of the applicable Membership Agreement or Early Adopters Agreement and other liability permitted
`by the applicable agreement or by applicable law to Bluetooth SIG or any of its members for patent, copyright
`and/or trademark infringement.
`THE SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER, INCLUDING ANY
`WARRANTY OF MERCHANTABILITY, NONINFRINGEMENT, FITNESS FOR ANY PARTICULAR
`PURPOSE, SATISFACTORY QUALITY, OR REASONABLE SKILL OR CARE, OR ANY WARRANTY
`ARISING OUT OF ANY COURSE OF DEALING, USAGE, TRADE PRACTICE, PROPOSAL,
`SPECIFICATION OR SAMPLE.
`Each Member hereby acknowledges that products equipped with the Bluetooth technology ("Bluetooth
`products") may be subject to various regulatory controls under the laws and regulations of various governments
`worldwide. Such laws and regulatory controls may govern, among other things, the combination, operation,
`use, implementation and distribution of Bluetooth products. Examples of such laws and regulatory controls
`include, but are not limited to, airline regulatory controls, telecommunications regulations, technology transfer
`controls and health and safety regulations. Each Member is solely responsible for the compliance by their
`Bluetooth Products with any such laws and regulations and for obtaining any and all required authorizations,
`permits, or licenses for their Bluetooth products related to such regulations within the applicable jurisdictions.
`Each Member acknowledges that nothing in the Specification provides any information or assistance in
`connection with securing such compliance, authorizations or licenses. NOTHING IN THE SPECIFICATION
`CREATES ANY WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING SUCH LAWS OR
`REGULATIONS.
`ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY
`RIGHTS OR FOR NONCOMPLIANCE WITH LAWS, RELATING TO USE OF THE SPECIFICATION IS
`EXPRESSLY DISCLAIMED. BY USE OF THE SPECIFICATION, EACH MEMBER EXPRESSLY WAIVES
`ANY CLAIM AGAINST BLUETOOTH SIG AND ITS PROMOTER MEMBERS RELATED TO USE OF THE
`SPECIFICATION.
`Bluetooth SIG reserve the right to adopt any changes or alterations to the Specification as it deems necessary
`or appropriate.
`Copyright © 2001, 2002, 2003, 2004, 2005 2006 2007. Bluetooth SIG Inc. All copyrights in the
`Bluetooth Specifications themselves are owned by Agere Systems Inc., Ericsson AB, Lenovo,
`Microsoft Corporation, Motorola, Inc., Nokia Corporation, and Toshiba Corporation. *Other third-
`party brands and names are the property of their respective owners.
`
`16 April 2007
`
`Exhibit 1029
`Page 04 of 93
`
`

`

`Page 5 of 93
`
`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`Document Terminology
`The Bluetooth SIG has adopted Section 13.1 of the IEEE Standards Style Manual,
`which dictates use of the words ``shall’’, ``should’’, ``may’’, and ``can’’ in the
`development of documentation, as follows:
`• The word shall is used to indicate mandatory requirements strictly to be followed in
`order to conform to the standard and from which no deviation is permitted (shall
`equals is required to).
`• The use of the word must is deprecated and shall not be used when stating
`mandatory requirements; must is used only to describe unavoidable situations.
`• The use of the word will is deprecated and shall not be used when stating mandatory
`requirements; will is only used in statements of fact.
`• The word should is used to indicate that among several possibilities one is
`recommended as particularly suitable, without mentioning or excluding others; or
`that a certain course of action is preferred but not necessarily required; or that (in the
`negative form) a certain course of action is deprecated but not prohibited (should
`equals is recommended that).
`• The word may is used to indicate a course of action permissible within the limits of
`the standard (may equals is permitted).
`• The word can is used for statements of possibility and capability, whether material,
`physical, or causal (can equals is able to).
`
`16 April 2007
`
`Exhibit 1029
`Page 05 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 6 of 93
`
`1.1
`1.2
`1.3
`
`2.1
`2.2
`2.3
`
`2.4
`2.5
`3.1
`3.2
`4.1
`
`2
`
`3
`
`4
`
`Contents
`1
`Introduction ...................................................................................................................................... 9
`Scope......................................................................................................................................... 9
`Profile Dependencies ................................................................................................................ 9
`Symbols and Conventions....................................................................................................... 10
`1.3.1 Requirement Status Symbols ........................................................................................... 10
`1.3.2 Definition ........................................................................................................................... 10
`1.3.3 Conventions ...................................................................................................................... 11
`1.3.4 Notation for Timers............................................................................................................ 12
`Profile Overview ............................................................................................................................. 13
`Profile Stack............................................................................................................................. 13
`Configuration and Roles.......................................................................................................... 13
`User Requirements.................................................................................................................. 14
`2.3.1 Scenarios .......................................................................................................................... 14
`2.3.2 User Expectations............................................................................................................. 16
`Profile Fundamentals............................................................................................................... 17
`Conformance ........................................................................................................................... 18
`Application Layer............................................................................................................................ 19
`Feature Support....................................................................................................................... 19
`Feature Mapping ..................................................................................................................... 19
`Control Interoperability Requirements ........................................................................................... 21
`Procedure ................................................................................................................................ 21
`4.1.1 Connection for Control ...................................................................................................... 21
`4.1.2 Release Connection for Control........................................................................................ 22
`4.1.3 Procedure of AV/C Command .......................................................................................... 22
`4.1.4 AV/C Command Operation ............................................................................................... 23
`4.1.5 Procedure of Metadata Transfer....................................................................................... 24
`AVCTP Interoperability Requirements .................................................................................... 24
`4.2.1 Transaction Labels............................................................................................................ 24
`4.2.2 Message Fragmentation ................................................................................................... 24
`4.2.3 Profile Identifier of AVCTP Message Information ............................................................. 25
`AV/C Command and Response .............................................................................................. 25
`4.3.1 AV/C Transaction Rules.................................................................................................... 25
`4.3.2 AV/C Command Frame..................................................................................................... 26
`4.3.3 AV/C Response Frame ..................................................................................................... 26
`4.3.4 AV/C Frame Fields............................................................................................................ 27
`Supported Unit Commands ..................................................................................................... 27
`4.4.1 UNIT INFO Command....................................................................................................... 28
`4.4.2 SUBUNIT INFO Command ............................................................................................... 28
`Supported Common Unit and Subunit Commands ................................................................. 28
`4.5.1 VENDOR DEPENDENT Command.................................................................................. 28
`Supported Subunit Command ................................................................................................. 29
`4.6.1 PASS THROUGH Command............................................................................................ 29
`Metadata Transfer Data Representation................................................................................. 30
`4.7.1 Transfer Byte Order .......................................................................................................... 30
`4.7.2 Protocol Data Unit Format ................................................................................................ 30
`4.7.3 Capabilities........................................................................................................................ 31
`4.7.4 Target player application settings ..................................................................................... 31
`4.7.5 Media track metadata attributes transfer .......................................................................... 32
`4.7.6 Event notifications from target device............................................................................... 32
`4.7.7 Continuation...................................................................................................................... 33
`4.7.8 Group navigation............................................................................................................... 33
`4.7.9 Metadata Transfer PDUs .................................................................................................. 33
`Categories ............................................................................................................................... 35
`
`4.2
`
`4.3
`
`4.4
`
`4.5
`4.6
`4.7
`
`4.8
`
`16 April 2007
`
`Exhibit 1029
`Page 06 of 93
`
`

`

`Page 7 of 93
`
`5
`
`5.1
`5.2
`
`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`4.8.1 Category 1: Player/Recorder ............................................................................................ 35
`4.8.2 Category 2: Monitor/Amplifier ........................................................................................... 35
`4.8.3 Category 3: Tuner ............................................................................................................. 35
`4.8.4 Category 4: Menu.............................................................................................................. 35
`4.8.5 Support Level in TG .......................................................................................................... 36
`4.8.6 Support Level in CT .......................................................................................................... 37
`Detailed Description....................................................................................................................... 40
`Capabilities PDUs.................................................................................................................... 40
`5.1.1 GetCapabilities (PDU ID: 0x10) ........................................................................................ 40
`Player application settings PDUs ............................................................................................ 41
`5.2.1 ListPlayerApplicationSettingAttributes (PDU ID: 0x11)..................................................... 41
`5.2.2 ListPlayerApplicationSettingValues (PDU ID: 0x12)......................................................... 42
`5.2.3 GetCurrentPlayerApplicationSettingValue (PDU ID: 0x13) .............................................. 43
`5.2.4 SetPlayerApplicationSettingValue (PDU ID: 0x14)........................................................... 43
`5.2.5 GetPlayerApplicationSettingAttributeText (PDU ID: 0x15) ............................................... 44
`5.2.6 GetPlayerApplicationSettingValueText (PDU ID: 0x16) ................................................... 45
`5.2.7
`InformDisplayableCharacterSet (PDU ID: 0x17) .............................................................. 46
`5.2.8
`InformBatteryStatusOfCT (PDU ID: 0x18) ........................................................................ 47
`Media Information PDUs ......................................................................................................... 48
`5.3.1 GetElementAttributes (PDU ID: 0x20) .............................................................................. 49
`Notification PDUs .................................................................................................................... 50
`5.4.1 GetPlayStatus (PDU ID: 0x30).......................................................................................... 50
`5.4.2 RegisterNotification (PDU ID: 0x31) ................................................................................. 50
`Continuation PDUs .................................................................................................................. 54
`5.5.1 RequestContinuingResponse (PDU ID: 0x40).................................................................. 54
`5.5.2 AbortContinuingResponse (PDU ID: 0x41) ...................................................................... 55
`Basic Group Navigation........................................................................................................... 56
`5.6.1 Next Group (vendor unique id: 0x00)................................................................................ 56
`5.6.2 Previous Group (vendor unique id: 0x01) ......................................................................... 56
`Error handling for Metadata Transfer Commands................................................................... 56
`5.7.1 Error Status Code ............................................................................................................. 56
`Service Discovery Interoperability Requirements .......................................................................... 58
`L2CAP Interoperability Requirements............................................................................................ 61
`Channel Types ........................................................................................................................ 61
`Signaling.................................................................................................................................. 61
`Configuration Options.............................................................................................................. 61
`7.3.1 Maximum Transmission Unit............................................................................................. 61
`7.3.2 Flush Timeout ................................................................................................................... 61
`7.3.3 Quality of Service.............................................................................................................. 62
`Link Manager (LM) Interoperability Requirements......................................................................... 63
`Link Controller (LC) Interoperability Requirements........................................................................ 64
`Class of Device........................................................................................................................ 64
`9.1
`Generic Access Profile Requirements ........................................................................................... 66
`10.1 Modes...................................................................................................................................... 66
`10.2
`Security Aspects...................................................................................................................... 66
`10.3
`Idle Mode Procedures ............................................................................................................. 66
`Timers and Counters...................................................................................................................... 67
`Testing ........................................................................................................................................... 68
`References..................................................................................................................................... 69
`List of Figures................................................................................................................................. 70
`List of Tables.................................................................................................................................. 71
`Appendix A (Informative): Example of Latency.............................................................................. 73
`Appendix B (Informative): Example of A/V Devices....................................................................... 74
`Appendix C (Informative): Multiple applications use of AVCTP.................................................... 75
`Appendix D (Informative): Example of AV/C Commands and Responses................................... 76
`19.1 UNIT INFO command.............................................................................................................. 76
`
`11
`12
`13
`14
`15
`16
`17
`18
`19
`
`5.3
`5.4
`
`5.5
`
`5.6
`
`5.7
`
`7.1
`7.2
`7.3
`
`6
`7
`
`8
`9
`10
`
`16 April 2007
`
`Exhibit 1029
`Page 07 of 93
`
`

`

`Page 8 of 93
`
`20
`21
`22
`23
`24
`25
`
`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`19.2
`SUBUNIT INFO command ...................................................................................................... 77
`19.3
`PASS THROUGH command................................................................................................... 77
`Appendix E: List of Media Attributes............................................................................................. 79
`Appendix F: List of defined Player Application Settings and Values ............................................ 80
`Appendix G (Informative): Example MSC for extracting metadata transfer information from TG . 82
`Appendix H: List of defined metadata transfer events................................................................... 83
`Appendix I: Examples of PDUs for different command and responses......................................... 84
`Appendix J: List of Example MSC of different Metadata Transfer Commands ............................. 90
`25.1
`InformDisplayableCharacterSet............................................................................................... 90
`25.2 RegisterNotification ................................................................................................................. 90
`25.3 RequestContinuingResponse.................................................................................................. 91
`25.4
`AbortContinuingResponse....................................................................................................... 92
`Appendix K: Acronyms and Abbreviations..................................................................................... 93
`
`26
`
`16 April 2007
`
`Exhibit 1029
`Page 08 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 9 of 93
`
`1 Introduction
`1.1 Scope
`The Audio/Video Remote Control Profile (AVRCP) defines the features and procedures
`required in order to ensure interoperability between Bluetooth devices with audio/video
`control functions in the Audio/Video distribution scenarios. This profile specifies the
`scope of the AV/C Digital Interface Command Set (AV/C command set, defined by the
`1394 Trade Association) to be applied, and it realizes simple implementation and easy
`operability. This profile adopts the AV/C device model and command format for control
`messages, and those messages are transported by the Audio/Video Control Transport
`Protocol (AVCTP).
`In this profile, the controller translates the detected user action to the A/V control signal,
`and then transmits it to a remote Bluetooth device. The functions available for a
`conventional infrared remote controller can be realized in this profile. In addition to this
`the profile uses Bluetooth specific extensions to support transfer of metadata related to
`content to be transferred between Bluetooth devices. The remote control described in
`this profile is designed specific to A/V control. Other remote control solutions using
`Bluetooth wireless technology may be applied for general Bluetooth devices including
`A/V devices.
`Note that the Audio/Video Remote Control Profile does not handle the audio/video
`streaming. Devices that support this profile may support audio/video streaming by also
`implementing the Advanced Audio Distribution Profile and/or Video Distribution Profile.
`1.2 Profile Dependencies
`In Figure 1.1, the structure and dependencies of the Audio/Video Remote Control
`Profile are depicted. A profile is dependent upon another profile if it re-uses parts of that
`profile, by implicitly or explicitly referencing it.
`As indicated in the figure, the Audio/Video Remote Control Profile is dependent upon
`the Generic Access Profile. The details regarding the profile are provided in Section 10,
`Generic Access Profile Requirements.
`
`
`16 April 2007
`
`Exhibit 1029
`Page 09 of 93
`
`

`

`Page 10 of 93
`
`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`
`
`Generic Access Profile
`
`Generic Audio/Video Distribution Profile
`
`Advanced Audio Distribution Profile
`
`Audio/Video Remote Control Profile
`
`
`
`Figure 1.1: Audio/Video Remote Control Profile Dependency
`1.3 Symbols and Conventions
`1.3.1 Requirement Status Symbols
`In this document, the following symbols are used:
`‘M’ for mandatory to support (used for capabilities that shall be used in the profile).
`‘O’ for optional to support (used for capabilities that may be used in the profile).
`‘X’ for excluded (used for capabilities that may be supported by the unit but that shall
`never be used in the profile).
`‘C’ for conditional to support (used for capabilities that shall be used in case a certain
`other capability is supported).
`‘N/A’ for not applicable (in the given context it is impossible to use this capability).
`Some excluded capabilities are the ones that, according to the relevant Bluetooth
`specification, are mandatory. These are features that may degrade the operation of
`devices following this profile. Even if such features exist, which can occur when the
`device supports different profiles, they should never be activated while the device is
`operating within this profile.
`
`1.3.2 Definition
`1.3.2.1 RFA
`Reserved for Future Additions. Bits with this designation shall be set to zero. Receivers
`shall ignore these bits.
`
`16 April 2007
`
`Exhibit 1029
`Page 10 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 11 of 93
`
`1.3.2.2 RFD
`Reserved for Future Definition. These bit value combinations or bit values are not
`allowed in the current specification but may be used in future versions. The receiver
`shall check that unsupported bit value combination is not used.
`
`1.3.3 Conventions
`In this profile, protocol signals are exchanged by initiating procedures in communicating
`devices and by exchanging messages. Signaling diagrams use the conventions of
`Figure 1.2: Signaling Conventions. Both A and B represent devices playing specific
`roles, as defined in Section 2.2, Configuration and Roles. Specific arrow styles are used
`in the diagrams to indicate the relevant procedures initiated by the participant devices
`and the exchanged messages.
`
`A
`
`B
`
`Mandatory Signal Sent by A
`
`Optional Signal Sent by B
`
`Mandatory Procedure initiated by B
`
`Optional Procedure initiated by A
`
`Mandatory Procedure initiated by either A or B
`
`Optional Procedure initiated by either A or B
`
`Figure 1.2: Signaling Conventions
`
`
`
`16 April 2007
`
`Exhibit 1029
`Page 11 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 12 of 93
`
`1.3.4 Notation for Timers
`Timer is introduced, specific to this profile. To distinguish them from timers used in the
`Bluetooth protocol specifications and other profiles, these timers are named in the
`following format:
`•
`“Tmmm (nnn)” for timers, where mmm specifies the different timers used and nnn
`specifies time in milliseconds.
`
`
`
`16 April 2007
`
`Exhibit 1029
`Page 12 of 93
`
`

`

`BLUETOOTH SPECIFICATION
`Audio/Video Remote Control Profile (AVRCP)
`
`Page 13 of 93
`
`2 Profile Overview
`2.1 Profile Stack
`
`Application
`(Controller)
`
`AV Control
`
`Application
`(Target)
`
`AV Control
`
`AVCTP
`
`SDP
`
`AVCTP
`
`SDP
`
`LMP
`
`L2CAP
`
`LMP
`
`L2CAP
`
`Baseband
`
`Controller Side
`
`Baseband
`
`Target Side
`
`
`
`Figure 2.1: Protocol Model
`The Baseband, LMP, and L2CAP are the OSI layer 1 and 2 Bluetooth protocols. AVCTP
`defines the procedures and messages to be exchanged for controlling A/V devices.
`SDP is the Bluetooth Service Discovery Protocol [10]. AV control is the entity
`responsible for A/V device control signaling; this signaling is AV/C command