(19) United States
`(12) Patent Application Publication (10) Pub. N0.: US 2006/0041655 A1
`(43) Pub. Date:
`Feb. 23, 2006
`Holloway et al.
`
`US 20060041655A1
`
`(54)
`
`BI-DIRECTIONAL REMOTE CONTROL FOR
`REMOTELY CONTROLLABLE APPARATUS
`
`Publication Classi?cation
`
`(76) Inventors: Marty Holloway, Sacramento, CA
`(US); David Smith, El Dorado Hills,
`CA (US)
`
`(51) Int. Cl.
`(2006.01)
`G06F 15/173
`(52) US. Cl. ............................................................ ..709/223
`
`Correspondence Address:
`DLA PIPER RUDNICK GRAY CARY US, LLP
`2000 UNIVERSITY AVENUE
`E. PALO ALTO, CA 94303-2248 (US)
`
`(57)
`
`ABSTRACT
`
`Appl. No.:
`
`(21)
`(22) Filed:
`
`11/030,667
`
`Jan. 5, 2005
`
`Related US. Application Data
`
`(60) Provisional application No. 60/569,123, ?led on May
`6, 2004.
`
`Disclosed is a system for controlling a host using a remote
`control Whose functions are de?ned by that host. Functions
`on the remote control are arranged by the host and grouped
`logically for easy navigation. The communication betWeen
`the remote and host is bi-directional, and can occur in real
`time. The controlled devices can be devices for controlling
`applications Within a home or Within a commercial building.
`
`1015
`
`1016
`
`1022
`
`llhnnlnmlm
`on; remule
`isms sum as 1
`when luunimtim
`mm Ml
`
`Page 1 of 55
`
`Unified Patents Exhibit 1006
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 1 0f 27
`
`US 2006/0041655 A1
`
`10
`
`50/
`
`l
`
`1
`
`
`
`M, @414 > \i
`
`Page 2 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 2 0f 27
`
`US 2006/0041655 A1
`
`10
`
`15
`
`Page 3 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 3 0f 27
`
`US 2006/0041655 A1
`
`_\ an
`
`
`
`25 omwmw 20., mg 61
`
`> >
`
`gm .50 063 r "S
`
`mg 50 89> m3 2. 89>
`
`
`
`2" 25 z_ 053
`
`m2
`
`lll.\|i \ an
`
`m5 -\
`
`m .9
`
`whim-.55
`
`
`
`Allkniill/ m5
`
`n;
`
`Page 4 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 4 of 27
`
`US 2006/0041655 A1
`
`
`
`
`
`«avluau.»uuuuuuuvvu.u¢
`
`O¢(DZ<hn
`
`kZmZOL2OU
`
`4<zo_Eo
`
`rzwzomzou
`
`
`
`>,o._m.zmfijm5
`
`E2.
`
`
`
`
`
`A..,..................:.o_mzw>zou(5.mmmohmzzou$2dzzéoS_«Em.Sm.¢:.E..
`
`
`I.zo_mzw>zcu(R:-maofiwzzoo
`
`ozauuuofio_o:<
`
`2.
`
`_..1
`
`
`
`....‘‘..................L‘&2<0_D3<.._.XmOn
`
`
`
`I..u_.é.o_n_3<pxmo._
`
`(umm:m.¢I.E._
`
`2.
`
`\..
`
`I
`
`32595.0:mom
`
`
`
`
`
`muwzauimwflmommwoozuowo_>
`
`8.:8_=.xza»
`
`A..............:.zo_u$Ezoo
`A:.\.zo_wE>zoo.a
`
`zotzozSoca9.
`mozzoz<o>ea9<3.E<9
`
`.._<:u_a.zwnouzm_>o
`
`'
`
`Ev
`
`
`zotzozorHxmO...(E.Nzmooozwowns
`.zo_mzm>zou‘-
`
`5SA.zo_mmm>zou
`
`zoczosEm._.xm9(E._zwaoozmowns2.
`
`2.
`
`8.
`
`man.8
`
`Eu
`
`Gzzmxfi
`
`..wn.‘
`
`xmfiua.~mm:
`
`
`
`_Eo:.m:mu<uEm:.z_
`
`mama92:
`
`mum:mum.
`
`Emiuuam
`
`a>Qou
`
`Kmzz:mEm><._a
`
`
`
`Eoxmzizmmhxu
`
`mo_>mo
`
`
`
`_.:<mEmo_o.._<._<_._o_o
`
`
`
`
`
`
`
`
`
`Nz<u¢._.mo_o:<..<.:o_a
`
`
`
`
`
`ms_<m5mo_o:<..<.:u_o
`
`RafiiE:m5>m2_(§
`
`zmzmowzz_
`
`FanSod.
`
`..¢o9.m3m
`
`.E.Eozmz
`
`G3399
`
`
`
`mzotaa$2....E05.
`
`
`
`E2.sod.
`
`
`
`v:<mEmO_oD(._<.:o_o
`
`
`
`zmuzéao_o:<
`
`D2.
`
`.zo_mmm>zou
`
`o_a:<Emu
`
`
`
`—#22.(um
`
`.zo_mmm>zou
`
`¢u~:_u_ooa:<oa:<50E
`n=$:.Kz_<0:
`
`
`
`063«(mm
`
`
`
`N._.:..._z_(oz
`
`
`
`...I..............J
`
`5.:Wm.
`
`mo(uEm»z_
`
`91%
`
`Emzoaiou
`
`
`
`oz.zmooumo
`
`,zo_mmw>zou
`
`zwoouma89>Ema
`
`
`
`.zo_m¢m>zou5%..
`
`Q5wcmoniou
`
`EOE
`
`m:moa:ou
`
`.Smz_
`
`Page 5 of 55
`
`Page 5 of 55
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 5 of 27
`
`US 2006/0041655 A1
`
`8:
`
`m~..
`
`motzozaka0»Emooozw39>
`
`
`
`.zo_mzm>zou(R:
`
`E:
`
`
`
`motzozor0..nzmuoozmown;
`
`
`
`.zo_mmu>zoo(B.
`
`5:20:<o>2.so.as46>
`
`.zo_mmu>zou
`
`mt.\
`
`.2299_A,_2_z§.2.2.m.n_m..u...ms.n_......m
`
`
`.zo,nmmE:oom.............
`
`az<o_u:<.ea0»
`
`
`
`‘.2....50._<u:...o
`
`.L.22....
`
`
`
`$2O_DD(.._.xmOh.2:
`
`(ozmDm.KR.¢D
`
`
`
`33.zo_mE>zou‘Sn:2mumOEohmzzoooo__a:<oE
`
`2.
`
`
`
`
`
`Simm3m.zt.E........................
`
`
`
`
`
`azowumzzoon_E<._mzz<xu.6
`
`
`
`E<KOSnxUO._m—>(
`
`
`
`0....dfisim53a0..
`
`.a__...§._.oo
`
`Bout.
`
`9wmaca
`
`ma3
`
`.zo_mzm>zoo
`
`
`I]E:$~_:o_oT|I.|.._
`Mo_E._<"
`W_mmzi
`
`
`
`.IE!(
`
`_
`
`_
`
`.
`
`_
`
`._
`
`_
`
`owns
`
`ozammouxa
`
`4<z¢E.z_
`
`omn__>
`
`moxaom
`
`zo5w._mm
`
`O_o:<
`
`ozammuoxm
`
`3:
`
`4<zzm._.z_
`
`o_a:<
`
`mozaom
`
`zofimzwm
`
`E?
`
`:|..25um~:._o_o
`
`_.zo_m¢w>zoo
`
`o§._<
`
`.
`
`
`
`.zo_m¢u>zoo:.Ez_
`
`
`
`D\$¢m~:._o_a.(umOE:(
`
`
`
`0.9.2._.ZO¢u
`
`o_o.._<Emu
`
`«.Smz_<9.
`
`0.9.7.«fix
`
`_Smz_<2.
`
`
`
`mommmooxuouo_>
`
`V
`
`
`
`SE8“txzm
`
`
`
`
`
`¢mxm.E__.._:zEoBmdmwuzaomOmO_\(O_DD(
`
`.2o_mmw>zoo.5%.Q:zmaoomn.Eaoaxoo
`
`
`
`
`
`
`
`
`Qszmooumozwéuwrwu.
`.zo_mmm>zou..
`EmzoazooT3.1......
`
`._.z0¢u
`
`mtmoazoo
`
`.S..z_
`
`
`
`89>.«Em
`
`Page 6 of 55
`
`Page 6 of 55
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 6 0f 27
`
`US 2006/0041655 A1
`
`m .5
`
`Page 7 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 7 0f 27
`
`US 2006/0041655 A1
`
`
`
`E? iviiif
`
`a
`
`Page 8 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 8 0f 27
`
`US 2006/0041655 A1
`
`Fig 7
`
`Page 9 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 9 0f 27
`
`US 2006/0041655 A1
`
`801
`HOST IDENTIFIES rrs
`MVOOULESAND ‘ [5
`
`REMOTE CONTROL IS IDENTIFIED /"‘\ 803
`VIA WIRELESS COMMUNICATION
`
`- HOST Lbnié ~ I
`CORRECT MENU OF
`
`HOST DETERMINES
`INFORMAYICN To BE
`' DISPLA ED
`
`REMOITE '
`
`B95
`
`t
`HOST DETERMINES
`INFORMATION TO BE
`’ DISPLAYED BY
`
`~» REMOTE x
`
`\
`B17
`
`HOST oereammss INFORMATION
`TO as DISPLAYED ON ‘ "‘\ 506
`susseyouem s‘cggeus
`i
`
`HOST ARRANGES 2 /"\~ 807
`DISPLAY SCREENS ‘
`
`USER INPUTS ‘rd .
`REMOTE BY PUS'IING
`TOUCH- RFFN
`
`,/——_\_
`513'
`
`os'r PERFORMS
`APPROPRIATE ACTION
`
`A
`
`‘
`i
`l"
`nos'rmmswrssmsmv V ,/—\\ 80a
`SCREENS mm COMPACT‘ .
`I LANGUAGESUCHASH'I’MI.
`
`t
`
`,IfIOST‘SENDSE
`
`‘commcyglsmv
`INFORMATION _TO
`
`809
`
`I
`
`REMOTEDISPLA
`
`'
`
`~$CREEN .
`
`USER INPUTS TO REMOTE BY PRESSING
`'rou H"
`~
`
`>
`
`510
`
`I
`_,E_\
`7 REMOTE SENDS RESPONSE TO HOST
`AND DISPLAYS APPROPRIATE SCREEN /
`FROM STORED LOCATION
`
`‘
`
`81 1
`
`' BE SENT av HOST TO REMO
`
`' HOST PERFORMS
`APPROPRIATE ACTION
`
`Fig. 8
`
`Page 10 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 10 0f 27
`
`US 2006/0041655 A1
`
`UNIT [5 PGNERED
`
`aeemmvémfbnvps
`INSTALLED uoouugs
`
`V
`
`uurr gusmss MODULE
`SLOTIBAY TO DETERMINE u= A 905
`V
`MODULE l§ l-‘fRESENT .
`‘
`
`909
`
`911
`
`Fig. 9
`
`was égewqus BAY LAST 10
`
`- BE ousmzm .
`
`-
`
`_ Lozid an‘y
`standalone .
`software modules
`
`L
`END MODULE INITIALIZATION PROCESS
`
`Page 11 of 55
`
`

`
`Patent Application Publication
`
`Feb. 23, 2006 Sheet 11 0f 27
`
`US 2006/0041655 A1
`
`“J04
`
`User antsn ‘
`sswurd
`
`Add passwqd
`_ based access ?lter
`an all subsequénl 1
`
`l Ste
`
`\
`
`1005
`
`: multiple lio'ns lha
`‘
`the remote mn qantml
`l‘dyezeaem' ;‘
`
`1007
`
`1‘
`Display list of
`hosts suppoded
`t
`mwlgm
`
`1005
`
`I
`Use! selects host
`tocommll'rbmlisl
`
`I011
`
`ppm
`device lsadive in
`
`‘area '
`
`‘
`
`Host tells rpmmg
`pmper screen to
`msplay bg‘sed bn
`cumarn fucnlion
`
`1015
`
`//
`
`t
`Applymwss '
`
`'~ ~
`
`'
`~
`'
`v
`'
`User navl ales fundlons and
`lssues gammaml to has:
`
`‘
`
`Cm‘lml Panmgm
`
`'
`
`(Fgure xx)
`
`Host responds
`apmp?ately basedon
`
`access
`'
`I
`r
`w ‘
`wit-M98 and Man
`
`. pressed
`
`1015
`
`1°17
`
`1016
`
`1022
`
`Illumination lurns
`On; remote ls on
`same smaen as
`wheri Illumination
`lumed off
`
`Yes
`‘m screen or mote
`-- er wlmin speci?ed
`llme llmil'?
`
`.
`Timer turns LCD
`lllumlnamn' off
`i
`
`HOS! oon?
`adlm‘akngg‘e
`i Mme
`“
`
`‘I020
`
`1019
`
`v
`
`1023
`
`Socomlimemms
`’ namotaoff
`
`‘
`
`1024
`
`P \O
`
`\
`
`.
`
`Page 12 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 12 0f 27
`
`US 2006/0041655 A1
`
`m1 A11“ 1 ll’main Menu
`
`WATCH
`
`STEN
`
`RECORD
`
`Figure 11A
`
`1108 \
`
`1103
`
`f 1109
`
`1102/
`
`WATCH
`
`,LISTEN
`
`1105/
`
`MOVE DATA
`
`GOODIES ~‘
`
`_
`
`SETUP ‘
`
`1104
`
`1107
`
`1106
`
`Figure 118
`
`Page 13 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 13 of 27
`
`US 2006/0041655 A1
`
`.2.
`
`Eu.
`
`
`
`mxoxoaoommEu:
`
`
`
`>E._o_EGmmmzaxoommH_._n_m:um
`
`
`
`muzfiunoumwrfimo
`
`
`
`noz_nzoomx02.5001:
`
`
`
`525..n_:._.WwEm:
`
`
`
`
`
`
`
`muz_Cmmomu:<oE:(nozrfimww6:mm305200.Z.Emm<m
`
`
`
`
`
`
`
`m:»<»m.><aapmmzmfifimm»<_un_._momzumxu
`
`
`
`
`
`Eur
`
`3Eamt
`
`
`xmfi05:udztumo
`
`ownsEm>>oxmwn_dmbmmu
`
`
`
`mumaomizmmbflWE:0.9.2nmumoowm
`
`
`
`
`
`mic:
`
`mw_z<u
`
`59
`
`.::ww
`
`munoou
`
`<.—<aw>a:
`
`mu<Lmzo:
`
`Em;fl:\_.
`
`wxox
`
`xu.:=s
`
`
`
` Sm. pzwrzbunwnmouwm m:._._m._.<mm._m.-d
`
`fi¢uo<a¢m
`
`
`H0:mm:D>oBum>En
`
`
` am<xTmic:..:ozuSkam>o:Em:
`
`fix...
`
`
`
`xzozcmzxmntmmn5055¢59
`
`
`
`
`
`
`
`
`35:non.zoo.2255n_m_..:mom23.10.55Boxmom28.xuzsm
`
`
`
`>.E<m.musmuEm3<zo_Eo.7220.E0.wusmnumusmo
`mic:zwfi:Em:
`
`
`
`
`
`
`use:.6523mwzoaEu:
`
`near
`
`~S.2Eu)ison.23
`
`z_u=<z<.ExmEm:mac:
`
`Em:min:
`
`
`
`
`
`no065.mcjmimo_D<mzuia
`
`Page 14 of 55
`
`Page 14 of 55
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 14 0f 27
`
`US 2006/0041655 A1
`
`wee
`
`@IEJ@ @@@
`5% N m l
`
`ELF l W
`
`K
`
`MOVEDATA GO ES
`
`HUME
`
`
`
`
`
`
`
`FRONY ANALOG INPUT REAR ANALOG INPUT 1 REAR ANALOG INPUT 2
`
`
`
`
`
`
`
`
`
`:94 P0
`
`SBPD
`
`CABLEBATELLIYE
`
`PiCTURES
`
`
`
`BRONJCAST CABLEISA
`
`mcmnes
`
`F 9 re 13
`
`CH
`
`Brrlmatbn
`
`WA 00 OUWAN‘ITUW
`
`BR NJ AS TV
`
`TE
`
`:02
`
`:0
`
`5w CONTENT
`
`Page 15 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 15 0f 27
`
`US 2006/0041655 A1
`
`Page 16 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 16 0f 27
`
`US 2006/0041655 A1
`
`Page 17 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 17 0f 27
`
`US 2006/0041655 A1
`
`Figure 16-Rendering of basic IOD remote control. The touchscreen renders
`buttons unnecessary.
`
`Page 18 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 18 of 27
`
`US 2006/0041655 A1
`
`.<§$50:§5%.E%asH32Ensfim3.88“E:
`mi58:
`
`
`
`nmnummQmaummzmhmj zmmmamZZZ.zflmam23:
`
`C339:
`
`
`
`wwoiwmgOCO_PUAw(__@|_m
`
`
`
`65.50”.Bauum
`
`zflwam23:
`
`
` Dn_D>n=a_IUiQQ mmaaao
`zn._a>>E>755
`
`QCH.550:
`
`Page 19 of 55
`
`Page 19 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 19 0f 27
`
`US 2006/0041655 A1
`
`Figure 1B
`Setup of third party
`hardware
`
`Begin
`
`1301
`
`7
`
`Get desired third party boxes
`to work routing through AV1
`and using traditional remote
`controls
`
`1802
`
`Connect IIR blasters to power
`strip and place on or near lR
`receiver on appropriate
`device
`
`1803
`
`be added
`
`Identify device to be
`controlled by type,
`manufacturer, and model #
`(See Figure 31)
`
`1 805
`
`Update remote
`‘Power’ display
`screen to add new
`device
`
`1805
`
`l
`
`User tests power
`cyding for each
`device
`
`1507
`
`1 808
`
`Pass Power
`Test?
`
`1 609
`
`Update remote
`display to support
`added
`oomponent(s)
`
`1810
`
`User tests function
`for each device
`
`Enter Diagnostic
`> Mode (See Figure
`33)
`
`1812
`
`1813
`
`Page 20 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 20 of 27
`
`US 2006/0041655 A1
`
` 1901
`User Selects from a list of types of devices
`to control:
`
`
`
`Display (TV SelIMonitor)
`External Audio Amplifier
`
`
`Satellite/Cable Box
`VCR
`Other
`
`
`
`
`
`
`
`User Defines Device Inputloutput Connections
`Device is an AIV Input and Output device for host
`Device is an audio Input and Output device
`User defines device type from a list of
`
`Device inputs AN to host
`device types based on previous response
`Device inputs audio only to host
`
`
`Device only accepts AN input from host
`
`Device only accepts audio input from host
`
`
`
`known device
`type?
`
`
`
`Enter Teach Mode
`(Fig 20)
`
`,
`
`,,
`
`..............
`
`.........._
`
`..
`
`.
`
`,
`
`1 905
`
`User is prompted
`for Manufacturer
`based on device
`
`
`
`
`
`User Enters or
`
`selects model #
`
`
`
`Send
`manufacturer and
`model number to
`host AV1
`
`
`
`
`
`
`1913
`
`If device is an input to —-——~-——> Return to 1805
`AV1, prompt user for
`input pon
`
`1914
`
`Figure 19
`Third Party Hardware
`Identification
`
`Page 21 of 55
`
`Page 21 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 21 of 27
`
`US 2006/0041655 A1
`
`2°°‘
`
`2005
`
`2oo4
`2003
`zooz
`ser pom s remo e
`control at host and
`Host ‘|eams"
`control at host and
`.
`'OFF'
`d l
`lrea
`I
`‘0N'
`
`
`Praia: on
`‘
`505;.
`-—--
`prebsusfgn on
`datastzeeavlrrgor lhls
`
`appropriate remote
`appropriate remote
`device
`
`ways.
`-
`
`T
`
`lgguzemitrod P
`each TM ‘
`He
`are
`
`any
`
`Host 'Ieams'
`
`
`
`Host power wdes 2003
`
`
`
`Start Teach Mode ——~-——~—
`
`
`
`
`Does device
`output to AV1?
`
`
`
`
`
`2009
`
`Enter AV1 input port to be
`associated with this device
`
`
`2011
`
`Ofler user
`standard sets of
`functions to teach
`host
`
`.
`
`Generate standard
`command set for
`device
`
`Teach host an
`
`individual
`command in
`command in set
`tandem -
`
`
`
`
`User teaches host
`
`
`from standard
`commands
`
`
`
`2012
`
`2016
`
`Test command
`
`yes
`
`2017
`id comman
`
`
`
`
`
`
`Host issues
`lunclian command
`
`to device to be
`
`cantmlled
`
`
`2019
`
`2020
`
`
`
`
`User paints remote
`control at host and
`
`presses function button
`
`
`
`
`
`-------—-—
`User enters
`
`function name
`
`
`1 805
`
`Return to Step
`
`Page 22 of 55
`
`Page 22 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 22 of 27
`
`US 2006/0041655 A1
`
`HOME
`BACK
`
`D E 3
`AD
`DVD
`4
`5
`6
`BRO CAST
`
`RECORDED coN'rEN-r
`
`PICTURES
`
`EXTERNAL SOURCE
`
`Figure 21A-Walsh Screen
`for System wilhoul Cable!
`Salellile Option Installed
`
`I v I
`
`I e I
`
`9
`
`'3
`PLAYIPAUSE
`
`CABLEISATELLITE
`
`HOME
`
`
`
`ALTERNATE
`AUDIO
`SOURCE
`
`Figure 213-Expected
`cummand set for external
`cable or salsllils box
`
`BACK
`
`
`
`cA5,_E,SATE,_,_,TE
`
`HOME
`
`HELP
`
`CABLE/SATELLITE TEACH SCREEN
`
`EXIT
`
`A
`S
`
`
`
`ALTERNATE
`AUDIO
`
`SOURCE
`
`P‘-"Y’P’“-'55
`
`T
`
`RETURN
`
`GUIDE
`
`REW
`
`F FWD
`
`| MUTE 1
`
`Figuru 21C-Comrnands
`that has! device already
`knows
`
`=
`5
`
`9
`
`2
`5
`
`8
`'3
`
`4
`
`7
`
`~
`
`@
`
`
`
`Fifi“ 2‘D*Di5P'9¥ °'
`°°""’T'a"d5 "'3' "°5'
`device must Ieam
`
`HELP
`
`CABLE/SATELLITE TEACH SCREEN
`
`EXIT
`
`HELP
`
`cAB,_E,5A-,E,_,_,-I-E TEACH SCREEN
`
`Em
`
`’
`5
`
`3
`6
`
`4
`
`@
`I
`
`7
`B
`9
`
`
`
`H9‘-"'9 2‘_E'Di5P'5Y ‘Pf’
`
`‘-'59’ '19‘ '5‘-'9'“ ‘"9 ‘command
`
`Q
`
`
`
`B
`D
`
`9
`
`Figure 21E-Dlsplay afler
`user has laughl the '1'
`though '7' mmrnands
`
`VOI
`
`Page 23 of 55
`
`Page 23 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 23 of 27
`
`US 2006/0041655 A1
`
`2203
`
`IR receiver on aarrect
`piece of equipment?
`
`Correctly position
`IR blasters:
`continue lrom step
`1804
`
`
`
`Pmblem 01'
`output
`- rcblem
`
`
`
`2201
`
`Enter correct make
`and model
`number‘. continue
`from step 1804
`
`
`
`Figure 22
`Diagnostic Loop for
`installing third party
`hardware
`
`number at device aorred’?
`(ior devices using stored
`library)
`
`
`
`
`.
`Does system work
`
`using conventional
`remote?
`
`Get system
`working using
`conventional
`remote: continue
`from step 1803
`
`Enter Identification
`mode (Figure 19)
`
`2206
`
`Connect device to
`correct input;
`continue from step
`1805
`
`to con'ect input?
`
`
`
`Yes
`
`
`
`
`
`
` Is signal detected
`on specified input?
`
`
`
`Turn on 3'“ party
`device; continue
`from step 1305
`
`Contact technical
`support
`
`N0
`
`Is signal detected on
`
`any undefined input?
`
`Host switdies to
`input with signal
`on it
`
`End Diagnostic
`loop
`Relum to 1811
`
`2217
`
`Page 24 of 55
`
`Page 24 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 24 of 27
`
`US 2006/0041655 A1
`
`MULTIPLE HOSTS DETECTED-SELECT ONE
`
`LAST
`DEVICE
`
`ROOM
`
`BIG SCREEN SOUTH
`WALL
`
`SW CORNER OF MAIN
`ROOM
`
`NW CORNER OF MAIN
`
`NE CORNER OF BAR
`
`SHE CORNER OF BAR
`
`BIG SCREEN NORTH
`WALL
`
`FIGURE 23A-MULTIPE
`HOSTS DETECTED
`
`
`
`
`
`CEg';$E
`
`HOME
`
`HELP
`
`WATCH NE CORNER 0? BAR
`
`
`
`BROADCAST
`
`CABLE/SATELLITE
`
`PICTURES EXTERNAL SOURCE
` RECORDED CONTENT
`
`
`
`FIGURE 23A-TYPICAL
`SCREEN LAYOUT
`LAYOUT FOR CASE OF
`MULTIPLE HOSTS
`
`Page 25 of 55
`
`Page 25 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 25 of 27
`
`US 2006/0041655 A1
`
`8%
`
`
`
`ozoomm5.5:Io._.(>>
`
`8§ENcmwbm
`
`Bx
`
`
`
`$83Eozamau
`
`.SumE_:2.5
`
`
`
`53:8_u=:uE
`
`
`
`
`
`n_:._.mmmmaooo<._.<om>os_
`
`
`
`mzo_.5zE.fi(
`
`Smmficmm
`
`
`
`omo>>mm<n_.mmaooo
`
`8%
`
`
`
`coobwn.§um_u§u_um_u92:9
`
`
`
`
`
`movnIf
`
`Ben
`
`
`
`Eciwnma.mEw
`
`:83new.258
`
`1/NEm:r.3:
`
`5%
`
`
`
`
`
`m::=:oU:3:43E3:2oEmm_
`
`
`
`
`
`22:2fioammmn_.._o_.oo_wmBfin:
`
`«N23?.
`
`
`
`
`
`EOEUE.3:o_n==..2
`
`«ova
`
`Page 26 of 55
`
`Page 26 of 55
`
`
`
`
`
`
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 26 of 27
`
`US 2006/0041655 A1
`
`Level 1: Full access and
`control
`
`2510
`
`Level 2: Access to
`Parental Control Settings
`and Content Based on
`Password
`
`2501
`
`2502
`
`
`
`Administrator ID
`and Password
`
`Technical Support
`
`Access to
`parental control
`settings and
`content based on
`Password
`
`2511
`
`Access to content
`only based on,
`password
`
`2512
`
`Access based on
`“One Time“
`settings
`
`2521
`
`2520
`
`Access based on
`“Time of Day‘
`settings
`
`2522
`
`Level 3‘ Access to content
`only based on internal
`settings of host machine
`
`Access based on
`Global Settings
`
`2523
`
`Figure 25
`Parental Control Access
`Hierarchy
`
`Page 27 of 55
`
`Page 27 of 55
`
`

`
`Patent Application Publication Feb. 23, 2006 Sheet 27 of 27
`
`US 2006/0041655 A1
`
`E250.
`
`
`
`>m_%_u_o.._32.$5..
`
`.3:
`
`_m.En:c_.5639.322:8229.82
`
`5..Scan2.ma.E25fimouuoa
`
`.9232.583m_
`
`.lccuwmmn¢_n£n_3uu
`
`9:0Exec.
`
`
`
`$_e.Eu.320
`
`E£:8m_
`
`ozoz
`
`
`
`$>_6n._eEou
`
`oazum
`
`.30.0aEF.m_
`
`._oh:oUE5...26.m.
`
`uc_._o._uxamn
`
`
`
`financemo:«Bu:
`
`Eesmmmn
`
`.12_mm»
`
`M_m.....2.__ooan7|Eeaou
`I.|1‘14l1x_\BoE_._...3EMSwE_._.wco.coEmma
`
`
`
`
`
`uo._._Euanoouw2v2.55nanoumm_
`
`
`
`
`
`nnvz.02tumtooEninmnn2
`
`v_a.3mm»3.3:oz2E
`
`EGEOQ
`
`
`
`28.38:s..aE_
`
`_uc_..an_mEr_.
`
`2.533Ysa=_c_£_._E
`
`:.$bEBo_
`
`
`
`ozm
`
`
`
`29.582230
`
`.z..6.338
`
`mosse
`
`
`
`:m5z6_...mmw3<
`
`Sam—.N_.
`
`
`
`
`
`r><8swam__E=._o0_5c2wn
`
`EmucsuMSamm.€_n_m_ufie:mm».
`
`
`
`
`
`
`
`_mEEwnas523a5cucmfi<
`
`SE:SE23:00
`
`umtquoo
`
`
`~._2.cB
`
`c3333Eua.:Eummaoa<2
`
`98
`
`Page 28 of 55
`
`Page 28 of 55
`
`
`
`
`
`
`
`
`
`

`
`US 2006/0041655 A1
`
`Feb. 23, 2006
`
`BI-DIRECTIONAL REMOTE CONTROL FOR
`REMOTELY CONTROLLABLE APPARATUS
`
`RELATED APPLICATIONS
`
`[0001] Priority is claimed to Provisional Application Ser.
`No. 60/569,123 filed on May 6, 2004, U.S. patent applica-
`tion Ser. No. 10/841,581 filed on May 6, 2004 and U.S.
`patent application Ser. No. 10/840,925 filed on May 6, 2004.
`
`TECHNICAL FIELD
`
`[0002] The present invention relates generally to the field
`of remote control devices and, more particularly, to a hand-
`held remote control for a modular audio/video (A/V) appa-
`ratus or for other remotely controllable apparatus.
`
`BACKGROUND
`
`In recent years, there has been a vast proliferation
`[0003]
`of the amount of consumer oriented audio and/or video
`equipment for use mainly in private residences. There has
`also been a proliferation of other controllable systems, both
`for private residences and for commercial enterprises.
`
`[0004] Remote control devices for these remotely control-
`lable systems are diflicult to use because the remotes require
`updating when new components are added to the control-
`lable system. The current state of the art can be described as
`either one remote control per device; or a universal remote
`control that must be taught the correct command sequence
`for a particular controllable system or device. The remote
`control device of this patent supports the features that are
`contained within a controllable system even as those fea-
`tures are updated or added to, simplifying user control
`considerably. These controllable systems will sometimes be
`referred to as the controllable “host” or the “device.” Also,
`the processor or other computational component or a par-
`ticular other module within the modular entertainment cen-
`
`ter or other controlled system may actually be the “host” or
`“device.”
`
`SUMMARY
`
`[0005] Remote control devices currently fall into the cat-
`egory of “necessary evil” for most users. Users either have
`multiple remote controls for one remotely controllable sys-
`tem, or a universal remote that they have had to teach to
`perform multiple functions, a time consuming and tedious
`process. The bi-directional remote control of this patent will
`receive control
`information from the host. The control
`
`information identifies the controllable the components in the
`host and provides information for controlling those compo-
`nents. The remote can store that information and display it
`on a touch screen on the remote control. The user then
`
`navigates the touch screen, sending control information back
`to the home entertainment center, which then operates in
`accordance with the control information sent by the remote
`control.
`
`[0006] We also disclose a bi-directional remote control
`method for controlling the controllable system in an intuitive
`manner using the remote control. The remote control can be
`simplified from the traditional maze of buttons to a simple
`touch screen, with nested display screens organized by
`logical functions, based on the controllable modules that are
`contained in the host. This is made possible by the modular
`nature of the device or system being controlled; the con-
`
`Page 29 of 55
`
`trollable system can determine which functions are installed
`in it, and can efficiently communicate what those functions
`are to the remote control, which the user then uses to control
`the functions of the controllable host. Stated another way,
`the remote will communicate with the host, which “knows”
`what features it, the host, contains and can support. The host
`will then communicate with the remote control to cause the
`
`remote to be reconfigured based on the available, control-
`lable components and features of the host. The user then
`manipulates the reconfigured remote control to control the
`components or functions of the controllable system. This
`will result
`in a simple to use, self-configurable remote
`control. The control information for the remote control can
`
`be arranged principally in terms of logical function. By
`“principally” is meant
`the “Watch,”“Listen” (and other
`functions) paradigm described in this patent. Current
`:74:
`remotes are based on device, such as “control your DVD
`player,”“control your TV set,
`control your amplifier”—
`each as a device. The information for our novel remote
`
`ultimately gets down to devices but the top level, or prin-
`cipal, organization is by logical function-watch, listen, etc.
`Further, there could be various levels of abstraction of the
`functional information. For example, “live TV” could be a
`combination of local broadcast channels and satellite TV,
`which can exclude local channels.
`
`[0007] The concept of the remote control device is flex-
`ible, also. A cell phone or Personal Digital Assistant (PDA)
`could be programmed to recognize a host. This leads to the
`situation where a single host can recognize multiple con-
`trolling devices. Conversely, multiple hosts,
`including
`devices outside of the field of home entertainment, could be
`recognized by a single remote. A methodology for ensuring
`that each available host is properly controlled is described in
`detail.
`
`[0008] As described above and below, the host serves the
`function of a traditional multi-box home entertainment sys-
`tem, and the remote is a display device for that system. This
`system integration enables novel features not currently sup-
`ported by a traditional home entertainment system. Asimple
`example is changing surround modes in an amplifier auto-
`matically based on the genre of music being played. When
`a “Jazz” song is played, the amplifier changes to “Jazz”
`mode setting automatically; when a DVD is played, the
`amplifier would change to “Movie Theater” setting.
`
`[0009] A more complicated example of an enabling tech-
`nology described below is the application of parental con-
`trols across all content sources controlled by this device. For
`example, based on settings contained within the host, an
`individual teenaged user would not be able to watch “R” or
`“NC17” rated DVDs, watch live or recorded TV shows rated
`“TV-MA”, listen to CDs, MP3s, or satellite radio labeled as
`“Mature”, play games rated as “Mature,” or order Pay per
`View or video on demand services.
`
`[0010] Finally, it is recognized that individual users may
`wish to integrate their host device with third party hardware,
`such as a TV monitor, Video Cassette Recorder, external
`audio amplifier, or other device. A method to integrate third
`party hardware within the paradigm of the described remote
`control method is discussed in detail, ensuring ease of use
`for the consumer.
`
`Page 29 of 55
`
`

`
`US 2006/0041655 A1
`
`Feb. 23, 2006
`
`BRIEF DESCRIPTION OF DRAWINGS
`
`[0011] These and further features of the present invention
`will be apparent with reference to the following description
`and drawings, wherein:
`
`[0012] FIG. 1 is schematic representation of a modular
`A/V assembly.
`
`[0013] FIG. 2 is a block diagram of a modular A/V
`assembly.
`
`[0014] FIG. 3 is a generalized block diagram of the bus
`structure of the A/V assembly.
`
`[0015] FIG. 4A is a more specific block diagram for an
`embodiment of the A/V assembly using the Philips PNX
`1500 or 1700 series processor as an example of the CPU
`used.
`
`[0016] FIG. 4B is a more specific illustration of FIG. 4A
`showing components of the video processor that can be used
`as the audio/video source selector/multiplexer of FIG. 3.
`
`[0017] FIG. 5 shows the appearance of the front of the
`modular A/V assembly.
`
`[0018] FIG. 6 shows the appearance of the rear of the
`modular A/V assembly.
`
`[0019] FIG. 7 demonstrates one embodiment of the modu-
`larity aspect of the modular A/V assembly.
`
`[0020] FIG. 8 illustrates the control portion of the remote
`control by the modular A/V assembly.
`
`[0021] FIG. 9 illustrates the initialization and sequence
`that the host performs on power up.
`
`[0022] FIG. 10 is a basic flowchart for the communication
`between the remote and the home entertainment center or
`
`other controllable system.
`
`[0023] FIG. 11 is a representation of the “Home” screen
`for the remote.
`
`[0024] FIG. 12 illustrates the screens that would be loaded
`from the “Home” screen selection of FIG. 11.
`
`[0025] FIG. 13 illustrates the screens that would be loaded
`from the “Watch” page shown in FIG. 12.
`
`[0026] FIG. 14 shows the detail of a sample control
`screen, in this case the “Broadcast TV” page.
`
`[0027] FIGS. 15A and 15B demonstrate the differences in
`configuration based on the installed components in a host
`device.
`
`[0028] FIG. 16 is one simple rendering of the remote
`control’s appearance.
`
`[0029] FIG. 17A through FIG. 17C illustrate several
`variations on the fundamental design of the remote control
`device.
`
`[0030] FIG. 17A, illustrates the touch screen as the only
`interface to the user or the host.
`
`[0031] FIG. 17B illustrates the addition of common com-
`mands such as channel up-down, volume up-down, mute
`and power, located across the bottom of the screen of FIG.
`17A.
`
`Page 30 of 55
`
`the commonly
`[0032] FIG. 17C illustrates, as buttons,
`used functions that were introduced in FIG. 17B.
`
`[0033] FIG. 18 describes how to set up third party hard-
`ware to be controlled by the host device.
`
`[0034] FIG. 19 describes how the host identifies third
`party hardware from a library of known devices.
`
`[0035] FIG. 20 describes how to teach the host commands
`for third party devices for devices not contained in the
`standard library.
`
`[0036] FIG. 21 details specific screens displayed on the
`remote while learning commands for third party devices.
`
`[0037] FIG. 22 is a diagnostic flowchart to aid in trouble-
`shooting if installation of third party hardware is not suc-
`cessful.
`
`[0038] FIG. 23 shows the appearance of display screens
`when the remote recognizes multiple devices that it can
`control.
`
`[0039] FIG. 24 describes the procedure for multiple users
`of the same remote, enabling parental controls based on user.
`
`[0040] FIG. 25 details the hierarchy of access controls to
`the device.
`
`[0041] FIG. 26 details the decision making process in
`determining whether content should be displayed based on
`the current settings of the host.
`
`DISCLOSURE
`
`Modular A/V Apparatus as the Controllable System
`
`[0042] Referring to both of FIGS. 1 and 2, shown is an
`example embodiment of a modularA/V apparatus or assem-
`bly 10. FIG. 1 depicts a schematic representation of the
`assembly 10 and FIG. 2 depicts a functional block diagram
`of the assembly 10. Accordingly, FIGS. 1 and 2 are func-
`tionally consistent with each other, but the size, location and
`arrangement of corresponding components may not be
`shown with consistency from view to view.
`
`[0043] As used herein, the term A/V is intended to refer to
`audio and/or video content, such as in the form of one or
`more of audio files, audio signals, video files, video signals,
`combined audio and video files, combined audio and video
`signals and combinations thereof. Therefore, the term A/V
`assembly refers to an apparatus capable of performing at
`least one A/V management function or task, such as the
`examples of storing, playing, editing, receiving, decoding,
`encoding, amplifying and transmitting A/V files and/or
`signals.
`
`[0044] The modular A/V assembly 10 is a user upgrade-
`able, modular platform for managing A/V content, including
`without limitation audio files and signals and/or video files
`and signals. It is noted that most video files and signals
`contain both a video component and an audio component,
`but will be referred to herein simply as video files and
`signals.
`
`[0045] The assembly 10 has a main board 12 with a set of
`standardized interface features. In one embodiment, one or
`more modules 14 are provided. The modules 14 can be
`operatively coupled to the assembly 10 by the standardized
`interfaces of the main board 12. Each module 14 can
`
`Page 30 of 55
`
`

`
`US 2006/0041655 A1
`
`Feb. 23, 2006
`
`perform one or more dedicated A/V tasks and can be added,
`removed or replaced as desired by a user of the assembly 10.
`In this manner,
`the assembly 10 and the A/V functions
`performed by the assembly 10 can be configured and recon-
`figured with a high level of flexibility.
`
`[0046] The main board 12 can comprise a circuit board
`that is mounted in a housing, or chassis 16. For example, the
`chassis 16 can include an internal rack 18 to which the main
`
`board 12 is mounted with any suitable fastener, such as
`screws 20.
`
`[0047] The main board 12 can include a video processor
`22, such as a NEXPERIA PNX 1500 available from Philips
`Semiconductor, or any other suitable processing device for
`executing programmed logic instructions. In other embodi-
`ments, the processor can be a commercially available gen-
`eral use processor or an application specific integrated
`circuit (ASIC). The processor 22 can execute software
`routines to facilitate interaction with and among the modules
`14.
`In addition,
`the processor 22 can execute software
`routines to carry out A/V management functions, to edit A/V
`files and signals, transcode A/V files and signals, convert
`video files and signals from 2D representations to 3D
`representations, and any other A/V processing.
`
`[0048] Support circuitry and devices for the processor 22
`can be included on the main board 12. Support circuitry and
`devices can include, for example, a memory 24 (e.g., RAM
`and/or ROM components), an A/V multiplexer 26 and/or a
`local interface 28 to operatively connect components of the
`main board 12. The memory 24 can store operating instruc-
`tions in the form of code for execution by the processor 22.
`The code can comprise a set of operating system instructions
`and/or specified logic routines for carrying out specific
`functionality of the assembly 10. The memory 24 can also
`store data, various software programs and/or logic routine
`instructions, files and the like. In some embodiments, the
`memory 24 can also store A/V files and signals. Although
`illustrated with a single block, the memory 24 can comprise
`several devices and includes, for example, volatile and
`non-volatile memory components. Accordingly, the memory
`24 can include,
`for example,
`random access memory
`(RAM), read-only memory (ROM), a hard disk, a floppy
`disk, a compact disk (e.g., CD, DVD, etc.), a tape, and/or
`other memory components, plus associated drives, writers
`and players for these memory types.
`
`[0049] The processor 22 and the memory 24 can be
`coupled using the local interface 28, which can be comprised
`of a data bus with an accompanying control bus, a network,
`or other subsystem. The A/V multiplexer 26 can switch a
`desired video signal and/or audio signal from one of a
`plurality of sources to the video processor 22 over the local
`interface 28. The main board 12 can further include a video
`
`encoder (not shown) to encode signals output by the pro-
`cessor 22 and/or a video decoder (not shown) to decode
`signals transmitted to the processor 22.
`
`[0050] The main board 12 can include a plurality of
`interfaces 30 for physically connecting the modules 14 to the
`main board 12 and operatively connecting the modules 14 to
`the local interface 28 and processor 22. In one embodiment,
`the interfaces 30 are physically and functionally based on a
`standardized format, such as peripheral component inter-
`connect (PCI), industry standard architecture (ISA), or other
`peripheral interface standard adopted from the general pur-
`
`Page 31 of 55
`
`pose computing arts. Some of the interfaces 30:1 can be
`configured to physically connect to cables or wiring har-
`nesses associated with the modules 14. Other interfaces 30b
`
`can be configured to physically connect to edge connectors
`of a card or board of the modules 14. For instance, the
`interfaces 30b can be embodied as PCI slots. It should be
`
`appreciated that the interfaces can be embodied with any
`suitable industry standard interface or a proprietary