|||||||||||||||||||||||||||||||||||l|l||||||||||||||||||||||||l||||||||||||||l|||||||||l|l
`
`US 20110289II3A1
`
`(19) United States
`
`(12; Patent Application Publication (10) Pub. No.: US 2011/0289113 A1
`(43) Pub. Date: NOV. 24, 2011
`
`Arling et at.
`
`(54} SYSTEM AND METHOD FOR CONFIGURING
`THE REMOTE CONTROL FUNCTIONALITY
`OF A PORTABLE DEVICE
`
`Publication Classification
`
`[51]
`
`Int. (II.
`00617 172630
`
`(2006.01)
`
`(75}
`
`Inventors:
`
`(73)
`
`Assignec:
`
`Paul I). Arling. Irvine. (TA (US):
`Brian Barnett. Oakland. CA (U S);
`Norman C. Sheridan, Fremont.
`CA (US): Patrick I]. Hayes.
`Mission Viejo, CA (US)
`
`UNIVERSAL ELECTRONICS
`INC. Cypress. CA (US)
`
`{21}
`
`Appl. No .:
`
`l 31" [98,072
`
`(22}
`
`i’iled:
`
`Aug. 4, 2011
`
`Related US. Application Data
`
`(63)
`
`(‘ontintlntion-in-part of application No. 13148.444.
`filed on Apr. 18. 2008.
`
`(52} U.S.CI.
`
`707/769; 7070311014
`
`{5?}
`
`ABSTRACT
`
`A server device receives identit}r data retrieved from an appli—
`ance through use ofa physical and logical interconnection
`referenced to a standard. The identity data is used at the server
`device to identify within a database having a pluralityr of
`appliance records. each ol‘ which is cross-referenced to an
`appliance. an appliance record having data in one or more
`record fields which matches the identityr data retrieved from
`the appliance. A codesct identilier associated with the iden-
`ti lied appliance record is then used to select from a plurality of
`codesets a codeset for use in configuring the portable device
`to command liinclional operations ot'the appliance.
`
`300
`
`Dal: HDMI
`
`inlettace {or
`
`
`CEC dances
`
`
`
`Retrieve
`
`
`device Va noor
`
`data
`
`
`
`Submit
`
`
`retrieved data
`
`to codesel ID
`
`service
`
`
`Retrieve
`
`
`additional data
`from device
`
`N
`
`
`
`Set srrart
`denim app to
`use identified
`nndcset
`
`
`
`
`
`Allow any
`
`
`additionai USC"
`setup
`
`
`
`- 320
`
`Roku EX1009
`
`US. Patent No. 9,716,853
`
`Roku EX1009
`U.S. Patent No. 9,716,853
`
`

`

`Patent Application Publication
`
`Nov. 24, 2011 Sheet 1 of 4
`
`US 2011110289113 A1
`
`
`
`102
`
`
`
`
`
`
`104 V
`
`Figure 1b
`
`

`

`Patent Application Publication
`
`Nov. 24, 2011 Sheet 2 of 4
`
`US 2011(0289113 Al
`
`
`
`Figure 2
`
`

`

`Patent Application Publication
`
`Nov. 24, 2011 Sheet 3 of 4
`
`US 201110289113 Al
`
`Start setup
`
`Poll HDMI
`interface for
`
`CEC devices 300
`
` Retrieve
`device Vendor
`data
`
`Submit
`retrieved data
`to codeset ID
`service
`
`Retrieve
`additional data
`
`from device
`Codeset
`
`'dentified?
`
`device app to
`use identified
`codeset
`
` Set smart
`
`Allow any
`additional user
`
`setup
`
`Figure 3
`
`

`

`Patent Application Publication
`
`Nov. 24, 2011 Sheet 4 of 4
`
`US 201110289113 Al
`
`' 400
`
`Appliance type
`
`402
`
`406
`
`408
`
`410
`
`412 --
`
`414
`
`416 -
`
`-
`
`-
`
`.
`
`420
`
`422
`
`424
`
`426
`428
`
`430
`
`432
`
`432'
`
`434
`
`434
`
`__
`
`-
`
`-
`
`Model number
`
`.
`Serial number range low
`
`-
`‘
`Serial number range hIgh
`Codesetidentifier
`
`Region code(5)
`
`CEC vendorlD
`
`CEC OSD name
`
`EDID manufacturer ID
`
`5010 product 10 code
`
`EDID versioni’revision number
`SPD vendor name
`
`
`
`440
`
`450
`
`436
`
`__ 436'
`
`C
`g
`'5U
`
`g
`3D.
`to
`
`%(U
`m
`
`.52"
`”E
`
`5C
`
`D
`L)
`
`.3
`E.
`%
`O
`
`g0
`(D
`E
`
`_
`
`_
`
`.
`
`_
`
`__
`
`_.
`..
`
`-
`
`--
`
`SPD product description
`
`EDID additional parameter 1
`
`--
`EDID additional parameter n
`
`z
`
`'
`
`-- CEC challenge 1
`
`Expected response
`
`" "CEC challengen
`
`Expected response
`
`Appliance data record
`
`Figure 4
`
`

`

`US 2011/0289113 Al
`
`Nov. 24, 2011
`
`SYSTEM AND METHOD FOR CONFIGURING
`THE REMOTE CONTROL FUNCTIONALITY
`OFA PORTABLE DEVICE
`
`RI.EI..A‘I‘[.EIJ APPI .ICA’I'ION INFORMATION
`
`[0001] This application is a continuation-in-part and claims
`the benefit of U.S. patent application Ser. No. 1211485144,
`filed Apr. 18. 2008. The disclosure within that application is
`incorporated herein by reference in its entirety.
`
`BACKGROUN I)
`
`Personal communication. productivity. and enter-
`[0002]
`tainment devices such as tablet computers, smart phones,
`portable entail devices. e-books. hand-held games auditor
`game controllers, portable media players. etc. (all referred to
`hereafter as “sman devices”) are known to include features
`such as graphical user interfaces on colortouch screens. wire-
`less Internet capability, support for ancillary applications
`[sometimes referred to as “apps") such as. for exzunple, cal-
`endars. email. maps and navigation. etc. Such ancillary appii-
`cations may be pro-installed in a smart device ormay be made
`available for download by a user. Certain such apps may
`comprise an ability to issue commands to entertainment and
`other appliances. for example in conjunction with a GUI
`offering the features and functionality of a universal remote
`control as known in the art. in conjunction with a TV guide
`display to enable channel selection. etc.
`'l‘ypically such
`remote control apps may be provisioned with a library of
`command data and protocols suitable for controlling a plu-
`rality of appliances of different type auditor manufacture (a
`so-called “universal remote"). Such a command library and
`the hardware necessary to transmit operational cotnmands to
`appliances may be incorporated into or made available to the
`smart device itself. or may take the form ofa separateexternal
`device which is placed in conununication with the smart
`device (i.e.. a relay device or so-called “blaster"J. Regardless.
`upon initial installation or subsequent replacement ofa con-
`trolled appliance such universal remote control apps must
`generally be configured to match each particular appliance to
`be controlled to an appropriate set of command data and a
`protocol in the library. Disclosed herein are user-friendly and
`convenient methods for conducting such a configuration pro-
`cess.
`
`SUMMARY OF "II-113'} INVENTION
`
`[0003] This invention relates generally to remote control
`systems and, more particularly. to a system and method for
`facilitating the set up and configuration ot'a portable device.
`e.g., a smart device which may incorporate universal remote
`control functionality. to command operation of one or more
`types of remotely controllable appliances of one or more
`manufacturers. Exemplary smart devices include but are not
`limited to Apple‘s “iPhone’ and “ii-’ad.” (ioogle’s “Android”
`platform, Nintendo‘s “Wii U" controller. Blackbeny‘s
`“Torch“ or “PlayBook.” etc. Exemplary types of appliances
`include. but are not limited to televisions. digital video disc
`players [DVDs]. cable or satellite set top boxes (STBst. digi-
`tal video recorders (DVRs). audio video (AV) receivers. ther-
`mostats, game consoles, lighting systetns, etc.
`[0004]
`In order to rapidly and conveniently configure a
`smart device app and associated command library to match
`the appliances to be controlled, in accordance with the teach-
`ings of the instant invention the smart device may be tempo-
`
`rarily contracted to an appliance to ascertain that appliance's
`identity and thereby determine appropriate command data
`and protocol for control of that appliance. When said appli-
`ance is in communication with other remotely controllable
`appliances to form part of a local entertainment auditor envi-
`romnental system. the identities of those other appliances
`may also be determined by the smart device. using the con-
`nected appliance as an agent. Additionally. in seine embodi-
`ments configuration intonnalion regarding said local system
`may be communicated to the smart device by the agent appli-
`ance for use in the creation of activity macros: for use in
`localization of smart app displayed labels and menus: etc.
`Such information may comprise. by way of example. data
`regarding which media source appliances are attached to
`which input ports ofa rendering device such as a TV monitor
`or AV receiver. thereby facilitating the creation of pre-con-
`figured smart device command sequences for use in initiating
`activities such as “Watch TV”. “Listen to Music": language
`and merit] settings of the corniectcd appliance(s): etc.
`[0005]
`In a preferred exemplary embodiment, the physical
`and logical interconnections between smart device and appli-
`ance. and amongst appliances, may be in accordance with the
`High Definition Media Interface (I-IDMI) specification and
`appliance identities may be derived from. inter alia. Con-
`sumer Electronic Control (CEC } or Extended Display Iden—
`tification Data (EDID) data retrievable from appliances in
`compliance with that specification andtor from Source Prod-
`uct Description (SPD) infomtation frames embedded in a
`source appliance digital video stream in accordance with the
`Consumer Electronics Association specification CISA-861.
`However. it will be appreciated that other interconnection
`methods auditor protocols such as, by way olexamplc without
`limitation 1151?. 113131394 “liirewire”. III’HR (Ilihus, etc. may
`be utilized to the same end. when appropriate fora particular
`embodiment.
`
`[0006] A better understanding of the objects. advantages.
`features. properties and relationships ofthe invention will be
`obtained from the following detailed description and accom-
`panying drawings which set forth illustrative embodiments
`and which are indicative of the various ways in which the
`principles ofthe invention may be employed.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`For a better understanding of the various aspects of
`[0007]
`the invention. reference may he had to preferred embodi-
`ments shown in the attached drawings in which:
`[0008]
`FIGS. la and 1!; illustrate exemplary systems in
`which a smart device app configured in accordance with the
`instant invention may be utilized;
`[0009]
`FIG. 2 illustrates exemplary interconnections which
`may be used during configuration of the smart device(s} of
`FIG. 1:
`
`FIG. 3 illustrates a series of steps which may be
`[0010]
`performed by a smart device during an IIDMI-bascd enabled
`process; and
`[0011]
`FIG. 4 illustrates an exemplary appliance identity
`database record which may be utilized in configuring a smart
`device app in accordance with this invention.
`
`DEM] [JED DESCRIPTION
`
`[0012] By way of example. FIGS. 1a and lb illustrate
`exemplary systems 102 and 104 wherein a smart device 100
`may be adapted to issue commands to controllable appliances
`
`

`

`US 2011/0289113 Al
`
`Nov. 24, 2011
`
`such as a TV 106. set top box (STE) 108. DVD player 110.
`etc. While illustrated in the context of a home entertaimnent
`
`system comprising a TV. STD, and DVD player, it is to be
`understood that controllable appliances may include. but
`need not be limited to. televisions. VCRs. DVRs. DVD play-
`ers. cable or satellite converter set-top boxes (“S'lBs”).
`amplifiers. AV receivers. CD players. game consoles. home
`lighting. drapery, farts, I-IVAC systems, thermostats, personal
`computers. etc. In the illustrative example of FIG. la, a smart
`device 100 may include both a universal remote control app
`and the necessary hardware to enable direct transmission of
`conunands to appliances 106 through 110. Appliance com-
`mands may be issued in the form of infrared signals 112 as
`illustrated, or in any other suitable format. c.g.. via an lil’
`signal such as contemplated by RF4CE. Zwave. Bluetooth.
`etc .: ultrasonic signal: visible light; etc. as appropriate for the
`control of each particular appliance. In the example of FIG.
`In these command signals may be issued directly by smart
`device 102 using. for example, the technology described in
`co-pending 11.3. patent application Ser. No.
`l3i’043.915
`which is incorporated herein by reference in its entirety. In an
`alternative embodiment illustrated itt FIG. lb. appliance com-
`mands 112 may be issued indirectly via a relay device 114
`which is responsive to wireless communications 116 received
`from the universal remote control app resident in smart device
`100, for example as described in co—pending U.S. patent
`application Ser. No. 131071.661. also incorporated herein by
`reference in its entirety.
`[0013]
`In either case. the remote control app andfor associ-
`ated relay device must be provisioned witlt the specific cont-
`mand data and protocol (“codeset“) to which each of the
`to—becontmlled appliances is responsive. As is known in the
`art. this may take the form ofa pointer or index into a library
`of codesets pre-stored locally in the memory of smart device
`100 or ol‘relay device 1 14: individual codesets downloaded to
`those devices during a configuration process; an item-by-item
`download of individual command codes on an as-required
`basis from a library stored locally on a PC or on an appliance
`such as STE 108 or TV 106. or stored remotely at a headend
`or internet accessible settler, etc. Regardless, since the meth-
`ods described herein to accomplish the identification ofsuit—
`able codesets for controlled appliances may be generally
`applied without regard to the exact mechanisms by which said
`codesets are finally provisioned. it is to be understood that the
`embodiment described hercalter is by way of example only.
`and the techniques presented may pertain, mtttatis mutandis.
`to any of the various possible equipment and code library
`configurations.
`[0014] With reference to FIG. 2. in an exemplary embodi-
`ment a remote control app resident on a smart device 100 may
`be matched to the appliances to be controlled. for example a
`TV set 106 auditor a cable STE 108 and DVD player 110 by
`temporarily contracting an [IDMI port 206 of smart device
`100 to an available III3MI port 210 of an appliance to be
`controlled. e.g.. 'IV‘ 106 in the illustrative example, via an
`HDM'l compatible cable 208. Once the connection is estab-
`lished. the remote app of smart device 100 may be placed into
`a setup mode in which mode the app may solicit device
`identification data from TV 106 such as. for example a CEC
`manufacturer ID auditor an EDID manufacturer number and
`
`product code. In a preferred embodiment, the data so obtained
`may be uploaded from the smart device to a server 200 via. for
`example a WiFi connection 204 to the Internet 202. Server
`200 may include a database 216 which cross-references CEC
`
`andfor EDID device identity data to appliance conunand
`codesets, which database may be referenced to determine an
`appropriate command codeset for control ofexemplary appli-
`ance 106. In alternate embodiments. the database in which
`appliance command codesets are cmss-relcrenced to data that
`is itself referenced according to a standard may be locally
`resident in the smart device itself: or may be resident in an
`appliance accessible as part of a WiFi network such as for
`example a local PC or STB. Regardless, once determined the
`desired codeset may then be provisioned to the remote control
`app of smart device 100. in the form ofa pointer or index into
`a local databa se: or in the form ofa downloaded codeset block
`from a codeset database 218 stored on server 200; etc.: as
`appropriate.
`[0015] Turning now to the flowchart presented in FIG. 3.
`once an exemplary smart device 100 has been attached to an
`appliance using HDMI cable 208. at step 300 a setup program
`which forms part ofa remote control app installed on that
`smart device may be initiated. for example from a configura-
`tion or settings menu as is well known in the art. At step 302,
`the setup program may continence by issuing successive C EC
`compatible <Polling Message) transmissions (as defined in
`the HDMI specification and accompanying CEC supplement)
`to each of the possible type-specific C 136‘ logical device
`addresses. By way of explanation. the CBC protocol may
`support up to 16 possible logical address values, with each
`value allocated to a particular appliance type: For example. a
`TV device may only assume logical address zero or 14; a
`playback device such as a DVD player may only use one of
`logical addresses 4. 8 or 1 l'. a tuning device may only use one
`of logical addresses 3. 6. T or 10: etc. For purposes ofreceiv-
`ing responses to a poll. the initiating device (smart device 100
`in this example) in accordance Willi one version of the (TI-1C
`specification may always assume addrc5s 15. Though smart
`device 100 is physically connected only to HDMI port 210 of
`TV 106. the CEC protocol allows for an appliance to act as a
`CEC Switch. i.e.. to transparently route CBC commtmica-
`lions toffrom appliances connected to its other I-IDMI ports.
`such as STB 108 or DVD player 106 in the illustrative
`example. Accordingly in those instances where this fitnction—
`ality is supported by the host appliance to which the smart
`device is tethered. the setup program may be thereby enabled
`to interrogate downstream appliances.
`[0016]
`If no device responses to the issued polling mes-
`sages are detected at step 304 the setup program continues at
`step 320 to allow manual configuration by a userofthe app. If.
`however. one or more responses are detected. at step 306 a
`(THC <(iivc Device Vendor ID> message is transmitted to the
`first responsive logical address value. In accordance with the
`CEC protocol. the appliance to which this message is directed
`may respond with a tlnique 24-bit vendor ID. which number
`is assigned to CEC-compliant manufacturers by the IEEE in
`accord with the standard. Upon receipt. at step 308 this ven-
`dor 11) number, together with the (.‘IEC logical address from
`which it originated (being indicative ofappliance type], may
`be forwarded by the setup program to a codeset identifier. for
`example a Web service resident on server 200.
`[0017] Upon receiving a response from the codeset identi-
`fier service. at steps 310 and 312 the setup program may
`determine if the response constitutes a positive identification
`of a codeset for use in issuing commands to the indicated
`appliance. or if it comprises a request for additional infomta—
`tion by way of disambiguation. If neither. it is assumed that
`the identifier service has failed to identify a suitable codeset,
`
`

`

`US 2011/0289113 Al
`
`Nov. 24, 2011
`
`and the setup program continues at step 318 to detemiine if
`additional appliances remain to be identified. If the received
`response comprises a request for additional disambiguation
`information, such information may be retrieved at step 316
`and forwarded to the codeset identification service for further
`processing. By way ofexarnple without limitation. such dis-
`ambiguation data requests may be for Extended Display Iden-
`tification Data (EDID) as specified by the Video Electronics
`Standards Association (VESA). retrievabic from display
`devices via the [113M] interface and which may for example
`includes data fields corresponding to a Microso ft-assigncd
`manufacturer 1D andr'or a manufacturer-assigned product
`code; for a response to a <Get Menu Language) C EC request
`[which may be indicative of a territorylmarket in which die
`appliance is currently installed]: for responses to (Give ()SD
`Name) or <Get CEC vcrsioIP (TEC requests; for retrieval of
`SPD data corresponding to an input l-lDMl port of the host
`appliance (ie. TV 106 ofthe illustrative example) where such
`retrieval is supported by the host appliance; etc.: as appropri-
`ate for a particular- embodiment or appliance. By way of
`explanation regarding SPD data. CEA standard (EA-861B
`specifies that a digital video source may optionally insert a
`periodic Source Product Description information frame into
`its output video stream. This “lnfoFrame” may comprise a
`seven byte ASCII vendor name. a sixteen byteASCIl product
`description such as a model number. and a one byte binary
`product type identifier [e.g.. 0111 is a digital STB. 02h is a
`DVD player. 0511 is digital video camera, etc.) Rendering
`devices such as TV 106 may optionally decode this data and
`use it to augment on-screcn menu displays. etc.
`[0018] Alternatively orin addition to the above. since CEC-
`compliant appliances are required to issue a <Feature Abort>
`response to any message relating to an unsupported feature. in
`some embodiments a codeset
`identification service may
`request that certain CBC transmissions be initiated to an
`appliance and the resulting responsels) reported.
`to allow
`exact identification of an appliance by verification of its sup-
`port for ccnain features (or lack tliereol).
`[0019]
`lithe received response is determined at step 310 to
`be indicative of the identity of an applianco control codeset,
`then at step 314 the remote control app of smart device 100
`may be configured accordingly. As is known in the art. such
`configuration may take the form of storing a pointer to, or
`index into a preloaded local library of conunand codesets.
`provision of the required codeset as a data download from a
`server based codeset library 218. etc.. as appropriate for a
`particular embodiment. Once configuration is completed. at
`step 318 the setup program next detennjnes whether addi-
`tional appliances remain to be identified. If so. processing
`retinas to step 306 to repeat the above identification process
`for the next appliance. Once all appliances which responded
`to the polling request of step 302 have been subjected to the
`identification process. the setup continues at step 320. where
`additional user input may be solicited as necessary. Such user
`input may comprise. for example. provision ofexplicit model
`number information andr‘or codeset numbers, etc.. to corri-
`plete the identification and configuration of any appliances
`which were not responsive to the CEC polling request. which
`could not be uniquely identified by the automated codeset
`identification service. etc.. after which the initial configura-
`tion of the remote control app of smart device 100 is com—
`plete. Since the various alternative methods for identification
`of appliance command codesets are well known in the art. for
`the sake of brevity these will be discussed further herein.
`
`[0020] With reference now to FlG. 4. an exemplary
`embodiment ofan appliance identification database 216 may
`comprise a group of records 400. one for each distinctly
`identifiable appliance. each record comprising a series of
`fields 402 through 436' as illustrated. In the example pre-
`sented, each appliance record 400 may include a basic appli-
`ance identity 440 which may comprise data fields such as
`appliance type 402. brand 404. model number 406. serial
`ntunber or date range 408.410 (where necessary to ensure
`unique identification. for example where a manufacturer has
`changed an appliance feature in the middle of a model run)
`and the identifier 412 of an appliance conunand codeset for
`use in connnanding operation of the appliance. In some
`instances. geographic or market region codes 414 may also
`form part of the basic appliance identity. The information
`comprising this basic appliance identity may be utilized in
`various prior art methods for configuring controlling devices
`to conmrand operation of the appliance. for example match-
`ing a user provided brand and mode] number. printing set up
`code lists to be published in manuals. sequentially testing
`codesets corresponding to a particular appliance type and
`brand (and sometimes region). etc.. all as well known in the
`art.
`
`In addition to the above basic appliance identity
`[0021]
`data. an exemplary appliance identification database record
`400 in accordance with the instant invention may include
`additional fields 416 through 436' which comprise a second.
`electronic, identity 450 for the same appliance. Such art elec-
`tronic identity may comprise a tabulation ofdata items which
`may be solicited electronically from the appliance.
`for
`example via the HDMI interconnection 208 of the illustrative
`embodiment. This data may include without limitation a (Tl-1C
`vendor ID 416. a CliC version 418. 3 CBC 05]) name 420. an
`EDID manufacturer ID 422. an EDID product code 424. an
`EDID versionr'revision number 426. an SPD vendor name
`428. and an SPD product description 430. In some embodi-
`ments. geographic region codes 414 may also form part of an
`electronic appliance identity. since these may be derivable
`from CEC <Get Menu Language) responses. It should also
`be noted that. due to practices such as private labeling. multi-
`sourcing. etc., the vendon’numnlitcturcr [D and name fields
`416. 422. and 428 are not necessarily synonymous with each
`other or with brand field 404.
`
`[0022] Where necessary to ensure a unique identity for an
`appliance. additional data fields may be part of an appliance
`identity record 400. These may include for example further
`l.il')llJ disccrnablc parameters 432 through 432'. such as video
`formats and resolutions supported. timing data. etc.. andfor
`CEC cltallengelresponse data fields 434.436. Such challenger“
`response fields may comprise an electronic command or
`query 434 to be issued to an appliance together with an
`expected response 436 to be returned by the appliance. By
`way of example without limitation, to distinguish between
`similar cable STBs which differ only by the presence or
`absence ofa DVR option. a CEC <Crive Deck Status> request
`may be issued in the expectation that the non-DVR STB
`response will be 3 CBC <Feature Abort> message. If neces-
`sary to ensure accurate identification of a particular appli-
`ance. multiple challengefresponse data fields 434'.436' may
`be provided.
`[0023]
`in the illustrative embodiment. with the exception of
`appliance type 402 and codeset identifier 412. data fields
`which are not applicable or not available for a specific appli-
`
`

`

`US 2011/0289113 Al
`
`Nov. 24, 2011
`
`ance mayr be set as “null”. For example. serial number range
`fields 408,410 may not be necessary, certain appliance types
`may not support EDlD. etc.
`[0024]
`in order to uniquely identify an appliance. an illus—
`trative appliance identification service resident on andfor
`associated with server 200. for example. implemented by
`instmctions stored on a non-transient. computer readable
`media accessible by the server 200. and interacting with an
`exemplary smart device set up app which operates generally
`in accordance with the logic previously described in connec-
`tion with the flowehafl of FIG. 3. may receive an initial
`communication from smart device 100 comprising a Cllt.‘
`vendor ID together with an indication ofappliance type (e.g..
`the CEC logical address fi'onr which that vendor ID was
`retrieved.) The appliance identification service may apply
`those values as a mask to select only those records 400 of
`database 216 which match the requested criteria, i.c.. a match
`in field 402 with the appliance type implied by the C EC
`logical address value retrieved from an appliance and a match
`in field 416 with the CBC vendor ll) retrieved from the appli-
`ance. It will be appreciated that in various embodiments the
`data content of this initial communication may comprise
`other values. such as for example an SPD vendor name and
`product description. in place of or in addition to the values
`mentioned above, in which case the selection mask may be
`adjusted accordingly. If only a single match results. the iden-
`tification is complete and the corresponding code set identifier
`value from field 412 of that record may be returned to the
`setup app resident in smart device 100. If. however. multiple
`records meet the selection criteria the appliance identification
`service may then examine the contents of these records to
`determine which data field in that remaining subset exhibits
`the greatest diversity. Once the determination is made. a
`request for the retrieval of that data item from the appliance
`may be forwarded to the setup app resident in smart device
`100. When the requested data item is returned by the app, this
`item may be added to the selection ntask and the selection
`process repeated. in event that a requested item is not avail-
`able. for example the current host appliance does not support
`SP1) decoding and SPD data has btx‘n requested. the smart
`device setup app may respond in the negative in which case
`the currently requested item may be eliminated front the
`appliance identification matching process and a new request
`issued for an alternative data item. These steps may be iter-
`ated until either a single database record remains and its
`codeset identifier 412 can be comintmicated to the setup app:
`or no fitrther selection criteria are available. i.e._. every field
`414 through 436‘ has either been utilized or been found to
`contain a null value, in which case a failure may be countin-
`nicatcd to the stnart device setup app. allowing it to initiate a
`user message suggesting that an alternative set up method be
`employed.
`[0025] Once fully provisioned with the command codesets
`necessary for control ol‘a consumer’s appliances. in certain
`embodiments a smart device remote control app in accor-
`dance with the instant invention may undergo additional cus-
`tomization while in physical conmtunication with the con-
`trolled appliances via the exemplary HDMI connection. In
`one embodiment. the responsels) to a CliC (Get Menu Lan-
`guage> request may be utilized to adjust the menus. key
`labels, etc. of the remote control app to match those in use by
`the controlled appliances. Conversely. upon consumer
`request the language to which the smart device is currently
`regionalixed may be conveyed to the controlled appliances
`
`via a CEC <Set Monti Language> request. thereby adapting
`the appliance displays to match the userpreference settings of
`the smart device.
`
`in instances where an appliance such as TV 106 is
`[0026]
`adapted to perform the beforemcntioned (IliC switching
`function and is equipped to support such a query, that switch-
`ing appliance may be requested to indicate which of its phy si-
`cal HDMI ports [e.g. 210 thru 214) are associated with which
`downstream (“EC logical addresses (e.g.. STE 108. DVD
`player 110. etc.) The data so acquired may then be utilired by
`a smart device remote control app to configure activity mac-
`ros. for example without litnitation “Watch TV" or “Watch a
`movie“. such that a conmtand to select the appropriate HDMI
`input of TV 106 will be automatically issued when the activ-
`ity is initiated. Such macro configuration may be completely
`automatic. or may require user input: For example where
`multiple media playback appliances are detected in a co nfiguv
`ration (e.g._. botlt a DVD player anqudu streaming video on
`demand box] a user may be prompted to select which appli-
`ance is to be used for a “Watch movie“ activity [it being
`understood that in cases such as this multiple “Watch movie“
`activities may also be configured). To facilitate user identifi-
`cation of the desired appliance. the prompt may inclttde the
`appliances self-provided identities retrieved using (Taf‘ <(iet
`()SI) nan1e> requests. appliance brand names auditor model
`numbers supplied by a codeset identification service. TV
`input port numbers. or any combination thereofas appropri-
`ate.
`
`[0027] While various concepts have been described in
`detail. it will be appreciated by those skilled in the art that
`various modifications and alternatives to those concepts
`could be developed in light of the overall teachings of the
`disclosure. For example. while the illustrative equipment
`configuration presented above utilizes a television set as the
`HDMI interconnection focal point and host appliance for
`attachment ol'a smart device. it will be appreciated that in
`alternate configurations another device such as an AV"
`receiver. a set top box. a PC. etc. may serve equally well as a
`focal point and hest appliance to which a smart device may be
`temporarily attached for set up purposes. Furthermore, in
`those instances where no appliance in the configuration is
`capable of supporting CEC switch fintctionality. it will also
`be appreciated that a smart device in accordance with the
`invention may nevertheless be individually attached to mul-
`tiple appliances in sequence in order to perform an electroni-
`cally«enabled setup. It will also be appreciated that in certain
`embodiments. for the sake of efficiency multiple appliance—
`identifying data items may be gathered andjointly forwarded
`to an appliance identification service as a single transaction,
`rather than in a step-by-step fashion as described above. Addi-
`tionally. while illustrated using an HDMI connection. CEC
`protocol. and EDID and SPD InfoFrame data values it will be
`appreciated that various other connectivity and appliance
`identification data gathering methods may be equally adapt-
`able to the purposes described herein: standards may evolve
`or be amended to support additional features: etc. and that
`accordingly the exemplary appliance identification database
`contents presented herein are by way of illustration only and
`not intended as art exhaustive tabulation of all possible iden-
`tification data points or parameters that are or may become
`available for utilization by the appliance identification meth~
`ods described herein.
`
`[0028] While described in the context of functional mod-
`ules and illustrated using block diagram andfor flowchart
`
`

`

`US 2011/0289113 Al
`
`Nov. 24, 2011
`
`formats. it is to be understood that. unless otherwise stated to
`the contrary. otte or ntore of the described functions andt'or
`features may be integrated in a single physical device andfor