BLUETOOTH™
`Documentation
`Prepared
`Bluetooth SIG
`Imaging Working Group
`
`Date / Year-Month-Day
`2003-07-25
`
`Document No
`BIP_SP_D10_r01
`
`e-mail address
`Bt-imaging-feedback@bluetooth.org
`
`N.B.
`Confidential
`
`Page 1 of 99
`
`BASIC IMAGING PROFILE
`Interoperability Specification
`
`
`
`
`
`
`Abstract:
`This profile defines the requirements necessary
`for Bluetooth™ devices to support the Basic
`Imaging Profile usage models. The requirements
`are expressed by defining the features, functions,
`and underlying profiles which are required for
`interoperability among Bluetooth devices in the
`Basic Imaging Profile usage models.
`
`
` 30 July 2003
`
`1
`
`CELLSPIN
`EX. 2023, Page 1
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`
`Special Interest Group (SIG)
`
`Page 2 of 99
`
`
`The following companies are represented in the Bluetooth Special Interest
`Group:
`
`3Com Corporation
`Ericsson Mobile Communications AB
`IBM Corporation.
`Intel Corporation.
`Agere Systems, Inc
`Microsoft Corporation.
`Motorola Inc.
`Nokia Corporation
`Toshiba Corporation.
`
`Revision History
`
`
`Revision
`0.5
`0.7
`0.9
`0.95
`
`Date
`26-Sep-2000
`27-Jan-2001
`18-May-2001
`25-Sep-2001
`
`1.0 Draft
`
`05-Feb-2002
`
`15-Nov-2002
`1.0 Final
`1.0 Final_a 25-Jul-2003
`
`
`
`Contributors
`
`
`
`
`
`
`
`
`
`
`
`
`Tatsuo Arai
`Ryohei Yamamoto
`Maria Rang
`Erwin Weinans
`Marcel Wong
`Hiroshi Tanaka
`Mikio Watanabe
`Paolo Fontani
`Holt Mebane
`Franc Camara
`
`Comments
`Major document structure enhancement
`Features finalization
`Functions finalization
`Feedback from prototypes implementation and testing
`included
`Feedback from first open interoperability testing event
`and correction of remaining typos
`Final draft
`Further changes after BQRB review
`
`Casio Computer
`Casio Computer
`Ericsson
`Ericsson
`Ericsson
`Fujifilm
`Fujifilm
`HP
`HP
`Microsoft
`
`Introduction
`
`30 July 2003
`
`2
`
`CELLSPIN
`EX. 2023, Page 2
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`
`
`
`
`
`
`
`
`Karl Heubaum
`Stephane Bouet
`Martin Roter
`Takayasu Sanada
`Yosuke Tajika
`Patric Olsson
`
`Page 3 of 99
`
`
`Microsoft
`Nokia Mobile Phones
`Nokia Mobile Phones
`Toshiba
`Toshiba
`(curretly connectBlue AB)
`
`Prototyping and Profile Validation
`Akane Yokota
`Canon
`
`Kenichi Fujii
`
`Kazuaki Abe
`
`Matsunaga Kazuhisa
`
`Akinori Yoshioka
`
`Takuya Kawamura
`
`
`
`Canon
`
`Casio Computer
`
`Casio Computer
`
`Fujifilm software
`
`Toshiba
`
`
`DISCLAIMER AND COPYRIGHT NOTICE
`
`The copyright in these publications is owned by the Promoter Members of Bluetooth
`SIG, Inc. (“Bluetooth SIG”). Use of these publications and any related intellectual
`property (collectively, the “Publication”), 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 special interest group 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 Publication 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 Publication 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
`
`Introduction
`
`30 July 2003
`
`3
`
`CELLSPIN
`EX. 2023, Page 3
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`by the applicable agreement or by applicable law to Bluetooth SIG or any of its
`members for patent, copyright and/or trademark infringement.
`
`Page 4 of 99
`
`
`THE PUBLICATION 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™
`wireless 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 Publication provides any information or assistance in connection with
`securing such compliance, authorizations or licenses.
` NOTHING IN THE
`PUBLICATION 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 PUBLICATION IS EXPRESSLY
`DISCLAIMED. BY USE OF THE PUBLICATION, EACH MEMBER
`EXPRESSLY WAIVES ANY CLAIM AGAINST BLUETOOTH SIG AND ITS
`PROMOTER MEMBERS RELATED TO USE OF THE PUBLICATION.
`
`Bluetooth SIG reserve the right to adopt any changes or alterations to the Publication
`as it deems necessary or appropriate and to adopt a process for adding new
`Bluetooth™ profiles after the release of the Publication.
`
`
`
`Introduction
`
`30 July 2003
`
`4
`
`CELLSPIN
`EX. 2023, Page 4
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`
`Contents
`
`Page 5 of 99
`
`
`1
`
`2
`
`INTRODUCTION...........................................................................................................................8
`1.1
`PROFILE DEPENDENCIES.............................................................................................................8
`1.2
`BLUETOOTH OBEX-RELATED SPECIFICATIONS.........................................................................8
`1.3
`SYMBOLS AND CONVENTIONS....................................................................................................9
`1.3.1
`Requirement Status Symbols..............................................................................................9
`1.3.2
`Signaling Diagram Conventions......................................................................................11
`PROFILE OVERVIEW................................................................................................................12
`2.1
`PROTOCOL STACK....................................................................................................................12
`2.2
`CONFIGURATIONS AND ROLES .................................................................................................13
`2.3
`USER REQUIREMENTS AND SCENARIOS....................................................................................13
`2.4
`PROFILE FUNDAMENTALS ........................................................................................................14
`2.5
`CONFORMANCE........................................................................................................................14
`3 USER INTERFACE ASPECTS...................................................................................................15
`3.1 MODE SELECTION ....................................................................................................................15
`3.2
`FEATURES ................................................................................................................................15
`3.3
`EXAMPLE FEATURE SEQUENCES ..............................................................................................16
`3.3.1
`Example Image Push Sequence .......................................................................................17
`3.3.2
`Example Image Pull Sequence.........................................................................................17
`3.3.3
`Example Advanced Image Printing Sequence .................................................................18
`3.3.4
`Example Automatic Archive Sequence ............................................................................18
`3.3.5
`Example Remote Camera Sequence ................................................................................19
`3.3.6
`Example Remote Display Sequence.................................................................................19
`4 APPLICATION LAYER..............................................................................................................21
`4.1
`IMAGING DEVICES CLASSIFICATION.........................................................................................21
`4.2
`IMAGING FEATURES OVERVIEW...............................................................................................22
`4.3
`IMAGING FEATURES .................................................................................................................23
`4.3.1
`Image Push Feature ........................................................................................................23
`4.3.2
`Image Pull Feature..........................................................................................................25
`4.3.3
`Advanced Image Printing Feature...................................................................................26
`4.3.4
`Automatic Archive Feature..............................................................................................29
`4.3.5
`Remote Camera Feature..................................................................................................32
`4.3.6
`Remote Display Feature ..................................................................................................33
`4.4
`IMAGING PROFILE FORMATS, OBJECTS, AND PARAMETERS .....................................................35
`4.4.1
`Storage Formats Support.................................................................................................35
`4.4.2
`Imaging File Formats Support ........................................................................................36
`4.4.3
`Imaging Thumbnail .........................................................................................................36
`4.4.4
`Imaging Handles .............................................................................................................37
`4.4.5
`Imaging Attachments.......................................................................................................37
`4.4.6
`XML Headers and Objects ..............................................................................................37
`4.4.7
`Imaging Descriptors........................................................................................................49
`4.5
`IMAGING FUNCTIONS ...............................................................................................................55
`4.5.1
`GetCapabilities Function ................................................................................................55
`4.5.2
`PutImage Function ..........................................................................................................56
`4.5.3
`PutLinkedThumbnail Function ........................................................................................57
`4.5.4
`PutLinkedAttachment.......................................................................................................57
`4.5.5
`RemoteDisplay Function .................................................................................................58
`4.5.6
`GetImagesList Function ..................................................................................................59
`4.5.7
`GetImageProperties Function .........................................................................................62
`4.5.8
`GetImage Function..........................................................................................................62
`4.5.9
`GetLinkedThumbnail Function........................................................................................63
`
`Introduction
`
`30 July 2003
`
`5
`
`CELLSPIN
`EX. 2023, Page 5
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`
`Page 6 of 99
`
`
`6
`
`4.5.10 GetLinkedAttachment Function.......................................................................................63
`4.5.11 DeleteImage Function .....................................................................................................64
`4.5.12
`StartPrint Function..........................................................................................................65
`4.5.13 GetPartialImage Function...............................................................................................65
`4.5.14
`StartArchive Function......................................................................................................67
`4.5.15 GetStatus Function ..........................................................................................................67
`4.5.16 GetMonitoringImage Function........................................................................................68
`5 OBEX .............................................................................................................................................70
`5.1
`OBEX OPERATIONS USED .......................................................................................................70
`5.2
`OBEX HEADERS......................................................................................................................70
`5.2.1
`Application Parameters Header......................................................................................71
`5.2.2
`User-Defined Headers.....................................................................................................71
`5.2.3
`OBEX Headers in Multi-Packet Responses.....................................................................71
`5.3
`OBEX ERROR CODES ..............................................................................................................74
`5.4
`INITIALIZING OBEX.................................................................................................................75
`5.5
`ESTABLISHING AN OBEX SESSION...........................................................................................76
`5.5.1
`Primary and Secondary Sessions.....................................................................................76
`5.5.2
`Primary Session Establishment .......................................................................................76
`5.5.3
`Secondary Session Establishment....................................................................................76
`5.6
`DISCONNECTING.......................................................................................................................77
`SERVICE DISCOVERY ..............................................................................................................79
`6.1
`SERVICE DISCOVERY SERVICE RECORDS .................................................................................79
`6.1.1
`Imaging Responder Service.............................................................................................79
`6.1.2
`Referenced Objects Service .............................................................................................82
`6.1.3
`Archived Objects Service.................................................................................................83
`6.2
`SERVICE DISCOVERY PROCEDURE............................................................................................83
`7 MANAGEMENT ENTITY PROCEDURES ..............................................................................85
`7.1
`INITIALIZATION ........................................................................................................................85
`8 ANNEX A: TYPICAL MESSAGE SEQUENCE CHARTS......................................................86
`8.1
`IMAGE PUSH FEATURE .............................................................................................................86
`8.2
`IMAGE PULL FEATURE .............................................................................................................87
`8.3
` ADVANCED IMAGE PRINTING FEATURE...................................................................................88
`8.4
` AUTOMATIC ARCHIVE FEATURE .............................................................................................89
`8.5
`REMOTE CAMERA FEATURE.....................................................................................................90
`8.6
` REMOTE DISPLAY....................................................................................................................91
`9 ANNEX B: IMPLEMENTATION GUIDELINES FOR DCF DEVICES................................92
`10
`ANNEX C: SYNOPSIS OF THE OBEX FRAME STRUCTURES IN THE BASIC
`IMAGING PROFILE, PHASE 1 .........................................................................................................94
`11
`ANNEX D: REFERENCES......................................................................................................97
`11.1 NORMATIVE REFERENCES........................................................................................................97
`12
`ANNEX E: ACRONYMS AND ABBREVIATIONS .............................................................99
`
`
`
`Introduction
`
`30 July 2003
`
`6
`
`CELLSPIN
`EX. 2023, Page 6
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`
` Foreword
`
`Page 7 of 99
`
`
`The File Transfer Profile defines a mechanism enabling Bluetooth devices to
`exchange files in a generic fashion. The foundation of the Basic Imaging
`Profile is a series of constructs that enable Bluetooth devices to negotiate the
`size and encoding of imaging data to be exchanged. Given the variety of
`image formats currently in use, it is impossible – without using a negotiation
`mechanism – to guarantee that images transferred via Bluetooth (even when
`correctly received) can actually be used by a receiving device.
`
`Interoperability cannot be guaranteed unless all Bluetooth imaging devices
`support at least one common image format. Therefore, this profile requires
`that all Bluetooth imaging devices be capable of receiving JPEG thumbnail
`images and/or providing JPEG thumbnail versions of their stored images
`(either by performing format conversions or by using a thumbnail image
`created when the image is stored). Built on this negotiation mechanism and
`required imaging format are six features, ranging from very basic image
`transfer to remote control operations, that enable the usage scenarios
`described in the Bluetooth Imaging Market Requirements Document.
`
`Introduction
`
`30 July 2003
`
`7
`
`CELLSPIN
`EX. 2023, Page 7
`
`

`

`Page 8 of 99
`
`
`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
` 1
`
` Introduction
`
`1.1 Profile Dependencies
`
`In the figure below, the Bluetooth profile structure and the dependencies of the
`profiles are depicted. A profile is dependent upon another profile if it re-uses
`parts of that profile by implicitly or explicitly referencing it. Dependency is
`illustrated in the figure: a profile has dependencies on the profile(s) in which it
`is contained – directly or indirectly. For example, the Basic Imaging profile is
`dependent on the Generic Object Exchange, Serial Port, and Generic Access
`profiles.
`
`Generic Access Profile
`
`TCS-BIN-based Profiles
`
`Service Discovery
`Appl. Profile
`
`Cordless
`Telephony Profile
`
`Intercom Profile
`
`Serial Port Profile
`
`Dial-up Networking
`Profile
`
`Fax Profile
`
`Headset Profile
`
`LAN Access Profile
`
`Generic Object Exchange
`Profile
`
`File Transfer
`Profile
`
`Object Push Profile
`
`Synchronization
`Profile
`
`Basic Imaging
`Profile
`
`1.2 Bluetooth OBEX-Related Specifications
`
`The Bluetooth Specification includes six separate specifications for OBEX and
`applications using OBEX:
`
`
`
`1. Bluetooth IrDA Interoperability Specification [7]
`(cid:31) Defines how applications can function over both Bluetooth and IrDA.
`(cid:31) Specifies how OBEX is mapped over RFCOMM and TCP.
`(cid:31) Defines the application profiles using OBEX over Bluetooth.
`2. Bluetooth Generic Object Exchange Profile Specification [9]
`
`Introduction
`
`30 July 2003
`
`8
`
`CELLSPIN
`EX. 2023, Page 8
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`Page 9 of 99
`
`
` (cid:31)
`
` Generic interoperability specification for the application profiles using
`OBEX.
`(cid:31) Defines the interoperability requirements of the lower protocol layers (e.g.,
`Baseband and LMP) for the application profiles.
`3. Bluetooth Synchronization Profile Specification [13]
`(cid:31) Application profile for synchronization applications.
`(cid:31) Defines the interoperability requirements for applications within the
`Synchronization Profile.
`(cid:31) Does not define the requirements for the Baseband, LMP, L2CAP, or
`RFCOMM layers.
`4. Bluetooth File Transfer Profile Specification [11]
`(cid:31) Application profile for file transfer applications.
`(cid:31) Defines the interoperability requirements for applications within the File
`Transfer Profile.
`(cid:31) Does not define the requirements for the Baseband, LMP, L2CAP, or
`RFCOMM layers.
`5. Bluetooth Object Push Profile Specification [12]
`(cid:31) Application profile for object push applications.
`(cid:31) Defines the interoperability requirements for applications within the Object
`Push Profile.
`(cid:31) Does not define the requirements for the Baseband, LMP, L2CAP, or
`RFCOMM layers.
`6. Bluetooth Basic Imaging Profile (this specification)
`(cid:31) Application profile for transfer of still images.
`(cid:31) Defines the interoperability requirements for applications within the Basic
`Imaging Profile.
`(cid:31) Does not define the requirements for the Baseband, LMP, L2CAP, or
`RFCOMM layers.
`1.3 Symbols and Conventions
`1.3.1 Requirement Status Symbols
`
`In this document (especially in the features and functions tables in Section
`4.3), 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 can be used in the profile)
`
`Introduction
`
`30 July 2003
`
`9
`
`CELLSPIN
`EX. 2023, Page 9
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`"C" for conditional support (used for capabilities that shall be used in case a
`certain other capability is supported)
`
`Page 10 of 99
`
`
`"X" for excluded (used for capabilities that may be supported by the device but
`shall never be used in the profile)
`
`"N/A" for not applicable (in the given context it is impossible to use this
`capability)
`
`Some excluded capabilities are capabilities that, according to the relevant
`Bluetooth specification, are mandatory to support. These are capabilities that
`may, however, degrade the operation of devices following this profile.
`Therefore these features shall not be activated in the context of an OBEX
`session within this profile.
`
`In this specification, the word ‘shall’ or ‘must’ is used for mandatory
`requirements, the word ‘should’ is used to express recommendations and the
`word ‘may’ is used for options.
`
`The conformance requirements of a profile relate to the conformance
`requirements in the base standards in the following ways:
`(cid:31) Unconditional mandatory requirements in a base standard shall remain
`mandatory in the profile. (Base standard requirements to support a certain
`procedure do not mean it has to be used in a profile.)
`(cid:31) Unconditional options in a base standard may remain options or may be
`changed within the profile to become: mandatory, conditional, out of scope
`(unused), or prohibited.
`(cid:31) If conditional requirements in a base standard can be fully evaluated in the
`context of the profile, they become unconditional mandatory, unconditional
`options, out of scope, or prohibited. Otherwise, conditional requirements
`remain conditional, possibly with evaluated conditions.
`
`Introduction
`
`30 July 2003
`
`10
`
`CELLSPIN
`EX. 2023, Page 10
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`1.3.2 Signaling Diagram Conventions
`
`Page 11 of 99
`
`
`A
`
`B
`
`Mandatory signal sent by A
`
`Optional signal sent by B
`
`Mandatory procedure initiated by A
`
`Mandatory procedure initiated by either A or B
`
`Optional procedure initiated by either A or B
`
`
`
`Figure 1-1: Signaling Diagram Conventions
`
`In the figure above, the following cases are shown:
`
`A thin arrow represents a signal or individual message. When dotted, the
`representation indicates that the signal or message is optional. The arrow
`points from the issuer of the signal/message to its destination.
`
`A procedure (i.e. a set of messages) is represented with a wide arrow that
`points from the initiator of the procedure toward the responder. If both sides
`can initiate the procedure, the wide arrow is double-headed. A dotted
`representation indicates that the procedure is optional.
`
`Introduction
`
`30 July 2003
`
`11
`
`CELLSPIN
`EX. 2023, Page 11
`
`

`

`Page 12 of 99
`
`
`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
` 2
`
` Profile Overview
`
`2.1 Protocol Stack
`The figure below shows the protocols and entities used in this profile.
`
`
`
`Imaging Application
`Client Device
`OBEX
`
`Imaging Application
`Server Device
`OBEX
`
`
`
`
`
`
`
`
`
`
`
`
`
`ME
`
`RFCOMM
`
`SDP
`
`RFCOMM
`
`SDP ME
`
`LMP
`
`L2CAP
`
`LMP
`
`L2CAP
`
`Baseband
`
`Baseband
`
`Imaging Initiator
`
`
`
`Figure 2-1: Protocol Model
`
` Imaging Responder
`
`The Baseband [1], LMP [2], and L2CAP [3] are the OSI layer 1 and 2
`Bluetooth protocols. RFCOMM [4] is the Bluetooth adaptation of GSM TS
`07.10 [5]. SDP is the Bluetooth Service Discovery Protocol [6]. OBEX [7] is the
`Bluetooth adaptation of IrOBEX [8].
`
`ME is the Management Entity which coordinates procedures during
`initialization and manages the state of the link.
`
`The RFCOMM, L2CAP, LMP, and Baseband interoperability requirements are
`defined in Section 6 in [10].
`
`Profile Overview
`
`30 July 2003
`
`12
`
`CELLSPIN
`EX. 2023, Page 12
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`2.2 Configurations and Roles
`
`Page 13 of 99
`
`
`Feature Request
`
`Feature Reponse
`
`Imaging Initiator
`
`
`Figure 2-2: The Imaging Initiator is the Initiator of a Basic Imaging Feature and the Imaging
`Responder is the Responder
`
`Imaging
`Responder
`
`The following roles are defined for this profile:
`
`Imaging Initiator: The Imaging Initiator is the device that initiates a Basic
`Imaging feature. The Imaging Initiator must provide at least an object
`exchange client and must comply with the interoperability requirements for the
`client of the GOEP if not defined in a different way in the present profile. To
`support some features, the Imaging Initiator must also provide an object
`exchange server and comply with the interoperability requirements for a server
`set in the GOEP. Features that require support for both the object exchange
`client and object exchange server on the Imaging Initiator are indicated in
`Section 4.3.
`
`Imaging Responder: The Imaging Responder is the device that responds to
`the initiation of a Basic Imaging feature by the Imaging Initiator. The Imaging
`Responder must provide at least an object exchange server. The Imaging
`Responder must comply with the interoperability requirements for the server of
`the GOEP if not defined in a different way in the present profile. To support
`some features, the Imaging Responder must also provide an object exchange
`client and comply with the interoperability requirements for a client set in the
`GOEP. Features that require support for both the object exchange client and
`object exchange server on the Imaging Responder are indicated in Section
`4.3.
`
`There is no mandatory mapping between the Imaging Initiator/Imaging
`Responder roles and baseband master/slave roles.
`
`2.3 User Requirements and Scenarios
`
`The scenarios covered by this profile are:
`(cid:31) Use of a mobile phone to send one or more images to a wristwatch.
`Scenarios involving imaging devices of different natures but forming a
`functionally equivalent combination are also enabled by this profile.
`(cid:31) Use of a mobile phone to browse and retrieve the images stored on a digital
`still camera. These images may then be stored locally or forwarded to a
`
`Profile Overview
`
`30 July 2003
`
`13
`
`CELLSPIN
`EX. 2023, Page 13
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`
`Page 14 of 99
`
`
`third party via a PLMN network. Scenarios involving imaging devices of
`different natures but forming a functionally equivalent combination are also
`enabled by this profile.
`(cid:31) Use of a PC to automatically download the content of a digital still camera
`as soon as the camera comes into the vicinity of the PC. Scenarios
`involving imaging devices of different natures but forming a functionally
`equivalent combination are also enabled by this profile.
`(cid:31) Use of a printer to print one or more images sent from a digital still camera.
`Scenarios involving imaging source devices of a different nature but with
`equivalent functionally could also be implemented.
`(cid:31) Use of a mobile phone to control the shutter of a digital still camera and
`immediately examine the result on the phone’s screen. In the present
`scenario, any other portable imaging device could play the role of the
`mobile phone.
`(cid:31) Use of a laptop computer to send and control the display of images by a
`projector device. Scenarios involving imaging source devices of a different
`nature but equivalent functionality can also be implemented. The role of the
`projector could potentially be played by any device with display capability.
`2.4 Profile Fundamentals
`
`The profile fundamentals are the same as those defined in the GOEP.
`
`This profile does not mandate that either the server or the client enter the
`discoverable or connectable mode automatically even if they are able to do
`so.
`
`User interaction is always needed to trigger one of the six features defined in
`Section 3.2, where “user interaction” includes both on-the-fly interaction and
`use of pre-configured settings.
`
`2.5 Conformance
`
`If conformance to this profile is claimed, all capabilities indicated as mandatory
`for this profile shall be supported in the specified manner (process
`mandatory). This also applies to all optional and conditional capabilities for
`which support is indicated. All mandatory capabilities and optional and
`conditional capabilities for which support is indicated are subject to verification
`as part of the Bluetooth Qualification program.
`
`Profile Overview
`
`30 July 2003
`
`14
`
`CELLSPIN
`EX. 2023, Page 14
`
`

`

`<Title Of Document>
`Confidential Bluetooth SIG, Inc.
`
`Page 15 of 99
`
`
` 3
`
` User Interface Aspects
`
`3.1 Mode Selection
`There is a mode associated with the Basic Imaging Profile. It affects how the
`Imaging Responder is configured.
`
`Bluetooth Imaging Mode enables the Imaging Responder to maintain a
`connection and receive commands from Imaging Initiators. As a result of
`entering Bluetooth Imaging Mode:
`(cid:31) Devices that wish to be discoverable for a limited period of time shall be in
`limited discoverable mode and in connectable mode. It is expected that
`most implementations will take this approach.
`(cid:31) Devices that wish to be discoverable all the time shall be in general
`discoverable mode and in connectable mode.
`(cid:31) Devices that wish to be hidden from devices they never talked to before
`shall be in non-discoverable mode and in connectable mode.
`
`The setting of the CoD bits – together