USOO8799496 B2
`
`(12) United States Patent
`Phillips et al.
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 8,799.496 B2
`Aug. 5, 2014
`
`(54) SYSTEMAND METHOD FOR VIDEO
`DISPLAY TRANSFER BETWEEN VIDEO
`PLAYBACKDEVICES
`
`(75) Inventors: Andrew V. Phillips, Raleigh, NC (US);
`Scott Curtis, Durham, NC (US)
`(73) Assignee: Eloy Technology, LLC, Wilmington, DE
`(US)
`
`(*) Notice:
`
`-
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 778 days.
`
`1/2007 Thornton
`7,161,557 B2
`7.277.559 B2 * 10/2007 Matsunaga et al. ........... 382,103
`7,324,857 B2
`1/2008 Goddard
`7,457,511 B2 11/2008 Putterman et al.
`7,650,621 B2
`1/2010 Thomas et al.
`7,983,614 B2 * 7/2011 Dunko et al. ................ 455,411
`2003/0068.155 A1
`4/2003 Vasilevsky et al.
`2005, OO15805 A1
`1/2005 Iwamura
`2005/0221829 A1* 10/2005 Nishida et al. ................ 455,440
`2005/0283344 A1 12/2005 Moscovitch
`2005/0286546 A1 12/2005 Bassoli et al.
`2006/0256959 A1 * 1 1/2006 Hymes ..................... 379,433.04
`2007/0093199 A1
`4/2007 Bowen et al. ................ 455,302
`2007/O123308 A1* 5/2007 Kim et al. ..................... 455,566
`(Continued)
`
`(21) Appl. No.: 12/838,532
`
`(22) Filed:
`(65)
`
`Jul.19, 2010
`Prior Publication Data
`US 2012/O 1171.93 A1
`May 10, 2012
`
`Related U.S. Application Data
`(60) Provisional application No. 61/227,189, filed on Jul.
`21, 2009.
`
`(2006.01)
`(2009.01)
`(2009.01)
`(2006.01)
`
`(51) Int. Cl.
`G06F 15/16
`H4W36/
`H04.736/36
`H04N L/327
`(52) U.S. Cl.
`CPC ........... H04 W 36/36 (2013.01); H04N 1/32767
`(2013.01)
`USPC ........................................... 709/231; 455/439
`(58) Field of Classification Search
`USPC . .
`. .
`.
`. . . . . . .
`. . . . 709/231; 455/440
`See application file for complete search history.
`References Cited
`
`(56)
`
`U.S. PATENT DOCUMENTS
`
`OTHER PUBLICATIONS
`
`<http://en.wikipedia.org/wiki/
`at
`Wikipedia,
`"Streamium.”
`Streamium- from the Internet Archive, dated Sep. 16, 2008, last
`modified Jul. 15, 2008, printed Sep. 20, 2012, 6 pages.
`(Continued)
`
`Primary Examiner — Shirley Zhang
`
`(57)
`ABSTRACT
`Systems and methods are disclosed for transferring video
`display between video playback devices. In one embodiment,
`a mobile, or handheld, device receives user input that initiates
`transfer of display of video content to the mobile device from
`a desired renderer located proximate to the mobile device.
`The mobile device then causes transfer of display of the video
`content to the mobile device from the desired renderer. In
`another embodiment, a mobile, or handheld, device receives
`USC input that initiates transfer of display of video content
`from the mobile device to a desired renderer located proxi
`mate to the mobile device. The mobile device then causes
`transfer of display of the video content from the mobile
`device to the desired renderer.
`
`5,565,910 A
`6,037,981 A *
`
`10, 1996 Rowse et al.
`3/2000 Wilson et al. ............ 375,240.12
`
`22 Claims, 12 Drawing Sheets
`
`MOBILE
`DEVICE
`20
`
`200. INITIATETRANSFER
`
`
`
`D 202. DETECT PROXIMATERENDERER
`
`204, TRANSFER REQUEST
`
`--
`
`
`
`D 206. IDENTIFY DESIRED
`RENDERERFOR
`THE TRANSFER
`
`D 208, EFFECT DISPLAY
`TRANSFERTO THE
`MOBILEDEVICE
`
`Page 1 of 24
`
`GOOGLE EXHIBIT 1006
`
`

`

`US 8,799.496 B2
`Page 2
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`2007/0136488 A1* 6/2007 Cho et al. ...................... TO9,231
`2007/0271514 A1 11, 2007 O'Neal et al.
`2008, OO52606 A1
`2/2008 Alstrup et al.
`2008/008 1558 A1* 4/2008 Dunko et al. ................ 455,411
`2008. O141316 A1
`6/2008 Igoe et al.
`2008, 0231546 A1
`9, 2008 Li
`2009/002842 A1
`1/2009 Schmidt et al.
`2009/0070840 A1
`3f2009 Kamimaki et al. ........... T25,114
`2009.0102983 A1
`4/2009 Malone et al.
`2009,0295679 A1 12, 2009 Lida et al.
`2009,0295680 A1 12, 2009 Lida et al.
`2009,0296002 A1 12, 2009 Lida et al.
`2010 OO60549 A1
`3/2010 Tsern
`2010.0060572 A1
`3/2010 Tsern
`2010, 0161822 A1* 6, 2010 Palmet al. .................... TO9,231
`2010, 0180.055 A1
`7/2010 Lyon et al.
`2012/0114313 A1
`5/2012 Phillips et al.
`
`OTHER PUBLICATIONS
`
`"Annual Report 2007,” copyright 2007, Plantronics, Inc., Santa Cruz,
`California, 120 pages.
`"Apple iPhone App Reviews—iFones.com.” at <http://ifones.com/
`applie-Sck-native-orb-app-brings-live-tv-to-your-iphone-3/>, dated
`May 19, 2009, printed Jul. 31, 2009, 5 pages.
`“Composite Capability / Preference Profiles.” Wikipedia, found at
`<http://en.wikipedia.org/wiki/Composite Capability/Preference
`
`Profiles from InternetArchive, dated Oct. 9, 2008, last modified Jan.
`9, 2008, printed Nov. 1, 2011, 1 page.
`Herman, Ivan, World WideWeb Consortium (W3C), “CC/PP” Aug.
`22, 2005, slide show about Composite Capabilities / Preference Pro
`files, found at <http://www.w3.org/Consortium/Offices/Presenta
`tions/CCPP #(1)>, printed Nov. 1, 2011, 14 pages.
`“ICA Positioning Paper.” Mar. 16, 1996, at <http://www.citrix.com/
`technology/icatech.htm>, found on Internet Archive dated Oct. 24.
`1997, copyright 1996, Citrix Systems, printed Sep. 4, 2009, 6 pages.
`“ICA Technical Paper.” Mar. 16, 1996, at <http://www.citrix.com/
`technology/icatech.htm>, found on the Internet Archive, copyright
`1997, Citrix Systems, Inc., printed Jul. 6, 2010, 8 pages.
`"Monsoon Hava.” Wikipedia, at <http://en.wikipedia.org/wiki/Mon
`soon HAVA, page last modified Jun. 4, 2009, printed Jun. 12,
`2009, 4 pages.
`Scherer, B. and Klaben, G., “Company Overview.” Plantronics Pre
`sentation, Jan. 22, 2008, Plantronics, Inc., 38 pages.
`“Wireless PC(a)TVtm-Enjoy the Internet, PC Games and more, all
`on your TV.” Dec. 15, 1997, at <http://www.rfinktech.com/pctv.
`htm>, found on the Internet Archive dated Dec. 6, 1998, printed Jun.
`28, 2010, 4 pages.
`“Word Spy placeshift” at <http://www.wordspy.com/words/
`placeshift.asp. posted Nov. 14, 2005, printed Jul. 31, 2009, 1 page.
`Zahariadis, Theodore et al., “Scalable Content Delivery Over P2P
`Convergent Networks.” IEEE International Symposium on Con
`Sumer Electronics, Apr. 14-16, 2008, Vilamoura, Portugal, 4 pages.
`"Streamium Philips Wireless Audio.” at <http://www.streamium.
`philips.com/>, copyright 2004-2012, Koninklijke Philips Electronics
`N.V., printed Jul. 3, 2012, 1 page.
`
`* cited by examiner
`
`Page 2 of 24
`
`

`

`U.S. Patent
`
`Aug. 5, 2014
`
`Sheet 1 of 12
`
`US 8,799,496 B2
`
`FOIAAG
`FT1gOW
`
`02
`
`VIGAN
`YATIOUNLNOS
`
`ecb
`
`vl
`
`YsaysaNsay
`
`VIGSW
`YATIOYNLNOS
`
`YATIONLNOO
`
`Veh
`
`YsysaqNay
`
`cyl
`
`YsysaqNay
`
`ol
`
`Ysy0us
`VIGSN
`
`Page 3 of 24
`
`VIGSW
`
`Page 3 of 24
`
`
`
`

`

`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 2 of 12
`Sheet 2 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`Ysy0us
`VIGAW
`INAINOS
`
`
`
`
`ol
`
`ve
`
`AYSAOODSIO
`
`é O
`
`ld
`
`92
`
`ANIONS
`
`NOILLWSAYSOV
`
`Isanoay
`
`3YOSSs90ud
`
`4 of 24
`
`Page
`
`Page 4 of 24
`
`

`

`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 3 of 12
`Sheet 3 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`€ ‘
`
`Old
`
`NOILOSLAG
`YSYSONsy
`
`INANOdWO9
`ONITEVNA
`
`ve
`
`AOIAAC
`F1GOW
`
`0¢
`
`YsASNVaL
`AVIdSI0
`
`9€
`
`NOILONNA
`
`ce
`
`NOILONNA
`
`YsysaqNsay
`
`
`
`5 of 24
`
`Page
`
`Page 5 of 24
`
`
`

`

`U.S. Patent
`
`Aug. 5, 2014
`
`Sheet 4 of 12
`
`US 8,799.496 B2
`
`
`
`
`
`
`
`
`
`>HERHEIGINE}}
`
`F?
`
`Page 6 of 24
`
`

`

`US 8,799.496 B2
`US 8,799,496 B2
`
`AHLOL
`YSASNVYL
`
`FOIAAG
`ATgOW
`
`AW1dSIC
`LOASSAA
`“802
`
`S ‘
`
`Sl4
`
`Cl
`
`Sheet 5 of 12
`Sheet 5 of 12
`
`QauYISAG
`‘902
`AsILNACI
`
`YO
`YSYSCNaY
`
`YAASNVYLAHL
`
`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`YAYSONSAY
`ALVWIXONd
`LOALAC
`°c02Cc
`
`LSANDAY
`“7Oe
`YSASNVUL
`
`memeeee=YsAASNVAL
`
`ALVILINI002!
`
`0¢
`
`A1gOW
`
`AOIAAG
`
`oe
`
`
`
`IIlIIIlIIIlIIlIIIl
`
`---- | | | | | | | | | | | | | | | | | |
`T
`
`7 of 24
`
`Page
`
`Page 7 of 24
`
`
`
`

`

`cb
`0¢
`‘90€
`A1gOW
`YsesaqNsad ALVWIXOdd
`eeeeeee
`'20€
`22
`ee4YAASNVYL
`ALVILINI
`“OO€
`
`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 6 of 12
`Sheet 6 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`9 ‘
`
`S/d
`
`LSANO3Y
`‘ZLe
`LNALNOO
`
`INALNOO
`WVSYLSPLE
`
`YO
`YAYNSACNAY
`
`YAsASNVaLAHL
`
`MOVEAVTd
`NIVLEO80€
`
`AHLAO
`S1VLS
`
`<
`
`YsYsONaY
`GauIS3ad
`H.LIM
`‘OLE
`ASNOdS3Y
`
`ALVIS
`MOVEAVId
`
`QauIS30
`ASILNAI
`
`LSANODAY
`“OE
`YAASNVUL
`
`LOALAG
`
`
`
`VIGAW
`
`YATIONLNOS
`
`AOIASG
`
`8 of 24
`
`Page
`
`
`
`
`
`
`
`
`
`
`
`
`
`----------------------------
`---------------------------4
`
`Page 8 of 24
`
`
`
`
`

`

`Sheet 7 of 12
`Sheet 7 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`AHLOL
`YSASNVEL
`
`YsaYsON3aY
`GayIS3d
`
`AW1dSI0
`LOASsq
`'80V
`
`QauIS3d
`“907
`ASILNAI
`
`YO
`YSYsCNaY
`
`YAsSNVaLAHL
`
`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`YSAYSONAY
`ALVWIXOd
`LOALAC
`‘corCl
`
`
`
`meeeeee—YSASNVAL
`
`ALVILINI
`“O07
`
`02
`
`A1gOW
`
`AOIAAG
`
`GG
`
`
`
`Z ‘
`
`Sid
`
`cr:
`Cl
`
`LSANDAY
`‘VOv
`YSASNVUL
`
`lIIIlIIIlIIlIIIlII
`
`TT
`
`9 of 24
`
`Page
`
`Page 9 of 24
`
`
`
`

`

`U.S. Patent
`
`Aug. 5, 2014
`
`Sheet 8 of 12
`
`US 8,799.496 B2
`
`>HERHEIGINE}}
`
`F?
`
`
`
`----------------------------
`
`Page 10 of 24
`
`

`

`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 9 of 12
`Sheet 9 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`
`
`12
`
`
`INTERFACE
`USER
`
`MEMORY 40
`SECONDARYSTORAGE 42
`INTERFACE(S)44
`COMPONENT(S)
`COMMUNICATION
`
`9
`FIG.
`
`N
`MRR
`
`48
`
`ow
`LU
`
`eala
`Zz
`Oo
`©
`
`
`
`— 5i
`
`11 of 24
`
`Page
`
`Page 11 of 24
`
`

`

`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 10 of 12
`Sheet 10 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`
`
`10
`FIG.
`
`N
`MRR
`
`3
`60
`
`
`
`
`Sg
`S
`MEMORY 52
`SPEAKER(S) 58
`INTERFACE(S)54
`
`
`COMMUNICATION
`
`
`
`
`
`1.
`ow
`LU
`-
`
`— 5Y
`
`c 2 3 H
`
`e
`ola
`21
`Zz
`O
`Oo
`O
`©
`
`
`
`
`
`
`
`
`
`
`
`N
`14
`
`12 of 24
`
`Page
`
`Page 12 of 24
`
`

`

`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 11 of 12
`Sheet 11 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`
`
`62
`
`>
`uw
`<tc
`OAL eog
`Zzre9
`OO
`OF
`LUG
`“”
`
`=
`5
`Ee
`=
`s
`Zz
`>
`S
`=
`Oo
`
`INTERFACE(S)70
`
`INTERFACE
`USER
`
`COMPONENT(S)
`
`11
`
`% Z % % % % % % % % % % % % % % % % % % Z Z
`MRR
`
`74
`
`oO FIG.
`
`
`ow
`LU
`
`— 5r
`
`v
`ala
`Zz
`Oo
`©
`
`Page 13 of 24
`
`Page 13 of 24
`
`

`

`U.S. Patent
`U.S. Patent
`
`Aug. 5, 2014
`Aug. 5, 2014
`
`Sheet 12 of 12
`Sheet 12 of 12
`
`US 8,799.496 B2
`US 8,799,496 B2
`
`os
`
`BL
`
`AYXOWSAN
`
`08
`
`ADVYOLS
`
`AYVONOOAS
`
`v8
`
`WLSIG
`
`VYANVO
`
`98
`
`WLSIG
`
`SSVdNOO
`
`co
`
`(S)SOVIYSLNI
`
`NOLLVOINNWWOD
`
`FOVAYSLNI
`YSSN
`
`38
`
`(S)LNANOdWOD
`
`ck
`Ola
`
`N
`ERR
`
`06
`06
`
`57
`9Z
`
`YATIONLNOD
`
`14 of 24
`
`Page
`
`
`
`
`
`Page 14 of 24
`
`
`
`

`

`US 8,799,496 B2
`
`1.
`SYSTEMAND METHOD FOR VIDEO
`DISPLAY TRANSFER BETWEEN VIDEO
`PLAYBACKDEVICES
`
`RELATED APPLICATIONS
`
`5
`
`This application claims the benefit of provisional patent
`application Ser. No. 61/227,189, filed Jul. 21, 2009, the dis
`closure of which is hereby incorporated herein by reference in
`its entirety.
`
`10
`
`FIELD OF THE DISCLOSURE
`
`The present disclosure relates to transferring display of
`video content from one device to another.
`
`15
`
`BACKGROUND
`
`As mobile devices having media playback capabilities
`become more prevalent, new opportunities are emerging for
`how these mobile devices can enhance video watching expe
`riences. For example, services such as Orb Live and Slingbox
`allow users to remotely view video content, such as live
`television, from their homes using their mobile devices. How
`ever, these services do little to improve the video watching
`25
`experience while the users are at their own homes. One issue
`with watching video content using conventional technology
`found in today's homes is that there is no good way to move
`video content from one display or renderer in the home to
`another without any delay in playback or fumbling through
`menus to pause and shift playback. As such, there is a need for
`a system and method that improves the video watching expe
`rience by enabling a user to quickly and easily transfer display
`of video content between devices.
`
`30
`
`35
`
`SUMMARY
`
`2
`BRIEF DESCRIPTION OF THE DRAWING
`FIGURES
`
`The accompanying drawing figures incorporated in and
`forming a part of this specification illustrate several aspects of
`the disclosure, and together with the description serve to
`explain the principles of the disclosure.
`FIG. 1 illustrates a system for transferring display of video
`content between a mobile device and a renderer located proxi
`mate to the mobile device according to one embodiment of
`the present disclosure;
`FIG. 2 is a functional block diagram of the media broker of
`FIG. 1 according to one embodiment of the present disclo
`Sure;
`FIG.3 is a functional block diagram of the mobile device of
`FIG. 1 according to one embodiment of the present disclo
`Sure;
`FIG. 4 illustrates the operation of the system of FIG. 1 to
`enable display or playback of video content on one of the
`renderers from one of the media controllers according to one
`embodiment of the present disclosure;
`FIG. 5 illustrates the operation of the system of FIG. 1 to
`transfer display of video content from a desired renderer to
`the mobile device according to one embodiment of the
`present disclosure;
`FIG. 6 illustrates the operation of the system of FIG. 1 to
`transfer display of video content from a desired renderer to
`the mobile device in more detail according to one embodi
`ment of the present disclosure;
`FIG. 7 illustrates the operation of the system of FIG. 1 to
`transfer display of video content from the mobile device to a
`desired renderer according to one embodiment of the present
`disclosure;
`FIG. 8 illustrates the operation of the system of FIG. 1 to
`transfer display of video content from the mobile device to a
`desired renderer in more detail according to one embodiment
`of the present disclosure;
`FIG.9 is a block diagram of one of the media controllers of
`FIG. 1 according to one embodiment of the present disclo
`Sure;
`FIG. 10 is a block diagram of one of the renderers of FIG.
`1 according to one embodiment of the present disclosure;
`FIG. 11 is a block diagram of a device hosting the media
`broker of FIG. 1 according to one embodiment of the present
`disclosure; and
`FIG. 12 is a block diagram of the mobile device of FIG. 1
`according to one embodiment of the present disclosure.
`
`40
`
`45
`
`Systems and methods are disclosed for transferring video
`display between video playback devices. In one embodiment,
`a mobile, or handheld, device receives user input that initiates
`transfer of display of video content to the mobile device from
`a desired renderer located proximate to the mobile device.
`The mobile device then causes transfer of display of the video
`content to the mobile device from the desired renderer. Dis
`play of the video content at the mobile device begins at a point
`in playback of the video content that is being displayed at the
`desired renderer at the time of the transfer. In one embodi
`ment, the mobile device automatically, or programmatically,
`detects the desired rendering device from which display of the
`video content is to be transferred.
`In another embodiment, a mobile, or handheld, device
`receives user input that initiates transfer of display of video
`content from the mobile device to a desired renderer located
`proximate to the mobile device. The mobile device then
`causes transfer of display of the video content from the
`mobile device to the desired renderer. Display of the video
`content at the desired renderer begins at a point in playback of
`the video content that is being displayed at the mobile device
`at the time of the transfer. In one embodiment, the mobile
`device automatically, or programmatically, detects the
`desired rendering device to which display of the video content
`is to be transferred.
`Those skilled in the art will appreciate the scope of the
`present disclosure and realize additional aspects thereof after
`reading the following detailed description of the preferred
`embodiments in association with the accompanying drawing
`figures.
`
`DETAILED DESCRIPTION
`
`50
`
`55
`
`60
`
`65
`
`The embodiments set forth below represent the necessary
`information to enable those skilled in the art to practice the
`embodiments and illustrate the best mode of practicing the
`embodiments. Upon reading the following description in
`light of the accompanying drawing figures, those skilled in
`the art will understand the concepts of the disclosure and will
`recognize applications of these concepts not particularly
`addressed herein. It should be understood that these concepts
`and applications fall within the scope of the disclosure and the
`accompanying claims.
`FIG. 1 illustrates a system 10 enabling transfer of video
`display from one device to another according to one embodi
`ment of the present disclosure. As illustrated, the system 10
`includes a number of media controllers 12-1 through 12-3 and
`renderers 14-1 through 14-3 and a media broker 16 connected
`via a Local Area Network (LAN) 18. The LAN 18 is prefer
`ably a wireless LAN such as, for example, a WiFi or IEEE
`
`Page 15 of 24
`
`

`

`3
`802.11x network, but is not limited thereto. The system 10
`also includes a mobile, or handheld, device 20 having an
`associated user 22. Note that mobile device and handheld
`device are used interchangeably herein. In this embodiment,
`the system 10 is within a person’s home, where the media
`controller 12-1 and the renderer 14-1 are located in a first
`room of the home, the renderer 14-2 is located in a second
`room of the home, the media controller 12-2 is located in a
`third room of the home, and the media controller 12-3 and the
`renderer 14-3 are located in a fourth room of the home. Note
`that the media controllers 12-1 through 12-3 are generally
`referred to herein as media controllers 12, and a single one of
`the media controllers 12-1 through 12-3 is generally referred
`to herein as a media controller 12. Similarly, the renderers
`14-1 through 14-3 are generally referred to herein as render
`ers 14, and a single one of the renderers 14-1 through 14-3 is
`referred to herein as a renderer 14.
`The media controllers 12 are generally devices that operate
`as sources of video content within the system 10. Note, how
`ever, that the video content sourced by the media controllers
`12 within the system 10 may be stored locally at the media
`controllers 12 or may be obtained from remote sources such
`as, for example, Internet-based streaming video services
`(e.g., Hulu, Netflix, CBS.com, or the like) or terrestrial or
`satellite based television networks. The video content
`sourced by the media controllers 12 may be, for example,
`movies, television programs, video clips, home movies, or the
`like. In one specific embodiment, the media controllers 12 are
`devices that operate as Digital Living Network Alliance
`(DLNA) digital media servers. However, the present disclo
`sure is not limited thereto. Exemplary types of media control
`lers 12 are set-top boxes that have access to live and/or on
`demand television content from terrestrial or satellite
`television networks, personal computers that have access to
`stored video content and/or Internet-based streaming video
`content, Digital Video Recorders (DVRs) that have access to
`stored video content such as, for example, stored television
`content, Apple TV(R) devices, gaming consoles (e.g., PlaySta
`tion3(R) that have access to Internet based video content (e.g.,
`Netflix streaming video service, Hulu, or CBS.com), network
`storage devices (e.g., Network Attached Storage (NAS)
`device), or the like.
`The renderers 14 are generally devices that operate to
`provide playback or rendering from the media controllers 12.
`In one embodiment, video content may be streamed from any
`media controller 12 to any renderer 14 via the LAN 18. The
`video content may be streamed directly from the media con
`troller 12 to the renderer 14 or streamed through the media
`broker 16. In one specific embodiment, the renderers 14 are
`devices that operate as DLNA digital media players or digital
`media renderers. However, the present disclosure is not lim
`ited thereto. Exemplary types of renderers 14 are televisions,
`gaming consoles, set-top boxes, personal computers, or the
`like. Note that while the media controllers 12 and the render
`ers 14 are illustrated separately for clarity and ease of discus
`Sion, it should be appreciated that a single device may operate
`as both a media controller 12 and a renderer 14. For example,
`a personal computer may operates both as a media controller
`12 that operates as a source of video content for the renderers
`14 and as a renderer 14 that provides playback or rendering of
`video content from other media controllers 12.
`The media broker 16 is preferably implemented in soft
`ware and is hosted either by a separate device in the system 10
`or one of the existing devices in the system 10. For example,
`the media broker 16 may be hosted by a separate computer
`within the system 10. Alternatively, one of the media control
`lers 12 may be a personal computer, and the media broker 16
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`US 8,799,496 B2
`
`10
`
`15
`
`4
`may be hosted by that personal computer. As discussed below,
`in one embodiment, the media broker 16 operates to maintain
`a merged guide that includes a listing of all of the media
`content accessible to the media controllers 12 and therefore
`available for playback or rendering at the renderers 14. In
`addition, the media broker 16 operates to manage transfer of
`display of video content from the mobile device 20 to one of
`the renderers 14 and/or transfer of display of video content to
`the mobile device 20 from one of the renderers 14.
`FIG. 2 is a functional block diagram of the media broker 16
`according to one embodiment of the present disclosure. As
`illustrated, the media broker 16 includes a content discovery
`function 24, an aggregation engine 26, a merged guide 28, and
`a request processor 30. The content discovery function 24
`discovers video content accessible to the media controllers
`12. While any suitable discovery technique may be used, in
`one embodiment, the content discovery function 24 queries
`the media controllers 12 for lists of content accessible to the
`media controllers 12. These lists may be referred to herein as
`local guides of the media controllers 12. Updates may be
`obtained from the media controllers 12 as needed (e.g., peri
`odically). In another embodiment, the media controllers 12
`proactively send their local guides and corresponding updates
`to the content discovery function 24.
`The aggregation engine 26 operates to aggregate, or merge,
`the local guides of the media controllers 12 to form the
`merged guide 28. The merged guide 28 may be implemented
`as, for example, a list of video content items and, for each
`video content item, a list of media controllers 12 from which
`the video content item is accessible. In addition, for time
`restricted video content items such as television content, the
`merged guide 28 may include timing information that iden
`tifies times at which those video content items are accessible
`to the media controllers 12 (e.g., times at which the video
`content will be broadcast). The request processor 30 gener
`ally operates to serve merged guide and video content
`requests from the renderers 14 and server display transfer
`requests from the mobile device 20, as described below in
`detail.
`FIG. 3 is a functional block diagram of the mobile device
`20 of FIG. 1 according to one embodiment of the present
`disclosure. As illustrated, the mobile device 20 includes a
`renderer function 32 and a renderer detection enabling com
`ponent 34. The renderer function 32 may be implemented in
`software, hardware, or a combination thereof. In this embodi
`ment, the renderer function 32 enables playback or rendering
`of video content from the media controllers 12 at the mobile
`device 20 and, optionally, video content from local storage of
`the mobile device 20 and/or a remote content source (e.g., an
`Internet based streaming video source). In addition, the ren
`derer function 32 includes a display transfer function 36. As
`discussed below in detail, the display transfer function 36
`enables transfer of display of video content to the mobile
`device 20 from one of the renderers 14 located proximate to
`the mobile device 20, which in FIG. 1 is the renderer 14-3. In
`addition, the display transfer function 36 enables transfer of
`display of video content from the mobile device 20 to one of
`the renderers 14 located proximate to the mobile device 20,
`which again in FIG. 1 is the renderer 14-3.
`The renderer detection enabling component 34 may be
`implemented in Software, hardware, or a combination
`thereof. In general, the renderer detection enabling compo
`nent 34 enables detection of a desired renderer 14 that is
`proximate to the mobile device 20 and to which or from which
`display of video content is to be transferred. As discussed
`below in detail, the renderer detection enabling component 34
`may include a digital camera, a Bluetooth R transceiver, a
`
`Page 16 of 24
`
`

`

`US 8,799,496 B2
`
`10
`
`15
`
`5
`Global Positioning System (GPS) receiver, a digital compass,
`or the like. Using data obtained from the renderer detection
`enabling component 34 either the display transfer function 36
`or the media broker 16 is enabled to identify the desired
`renderer 14 that is proximate to the mobile device 20 to which
`or from which display of video content is to be transferred.
`FIG. 4 illustrates the operation of the media broker 16 to
`serve merged guide and video content requests according to
`one embodiment of the present disclosure. First, one of the
`renderers 14 sends a merged guide request to the media bro
`ker 16 via the LAN 18 (step 100). In response, the media
`broker 16 returns the merged guide 28, or some relevant
`portion thereof, to the renderer 14 (step 102). For example,
`the media broker 16 may obtain a merged list of video content
`items currently accessible to the media controllers 12 from
`the merged guide 28 and return this merged list of video
`content items to the renderer 14 rather than the entire merged
`guide 28. While not illustrated, the renderer 14 displays the
`merged guide 28 to an associated user, and the associated user
`is enabled to select a desired video content item for rendering
`at the renderer 14. In response to receiving the selection from
`the associated user, the renderer 14 sends a content request for
`the desired video content item to the media broker 16 (step
`104).
`The media broker 16 then identifies one of the media con
`trollers 12 that can serve the content request (step 106). Spe
`cifically, the media controller 12 identified to serve the con
`tent request is one of the media controllers 12 enabled to
`source the desired video content item at the time of the con
`tent request. The media broker 16 then returns a response to
`the renderer 14 that includes media controller information for
`the media controller 12 identified for serving the content
`request (step 108). The media controller information includes
`information that enables the renderer 14 to request the desired
`video content item from the media controller 12 such as, for
`example, an Internet Protocol (IP) address of the media con
`troller 12 and any credentials needed to access the media
`controller 12 (e.g., a password). Next, the renderer 14 sends a
`content request for the desired video content item to the media
`controller 12 via the LAN 18 (step 110). In response, the
`media controller 12 streams the desired video content item to
`the renderer 14 (step 112).
`In an alternative embodiment, the merged guide 28, or
`45
`portion thereof, returned to the renderer 14 in step 102 may
`include information identifying the media controllers 12 from
`which the video content items are accessible. Then, once the
`desired video content item is selected at the renderer 14, the
`renderer 14 may use the information in the merged guide 28
`to identify the media controller 12 from which the desired
`Video content item is accessible and then send a request for
`the desired video content item to that media controller 12. In
`this manner, the renderer 14 is not required to contact the
`media broker 16 to determine which media controller 12 is
`able to source the desired video content item.
`FIG. 5 is a general illustration of the operation of the
`system 10 of FIG. 1 to provide transfer of display of video
`content from one of the renderers 14 to the mobile device 20
`according to one embodiment of the present disclosure. As
`illustrated, the user 22 of the mobile device 20 first initiates
`transfer of display of video content from one of the renderers
`14 to the mobile device 20 (step 200). For example, the
`display transfer function 36 of the mobile device 20 may
`present a button or similar mechanism to the user 22 via a
`graphical user interface displayed at the mobile device 20.
`The user 22 may then initiate the display transfer process by
`
`55
`
`6
`selecting the button and, in Some embodiments, pointing the
`mobile device 20 toward the renderer 14 from which display
`is to be transferred.
`Next, the display transfer function 36 of the mobile device
`20 detects the renderer 14 located proximate to the mobile
`device 20 from which display of video content is to be trans
`ferred (step 202). This renderer 14 is also referred to hereinas
`the desired renderer 14. The detection of the desired renderer
`14 is preferably automatic in that detection does not require
`selection of the desired renderer 14 by the user 22 from a list
`of renderers 14. However, the present disclosure is not limited
`thereto. In one embodiment, the renderer detection enabling
`component 34 of the mobile device 20 includes a digital
`camera, and the digital camera is used to capture a digital
`image of the desired renderer 14. The desired renderer 14 may
`then be identified using fiduciary markers in the digital image.
`As discussed below, this identification process is preferably
`performed by the media broker 16, but is not limited thereto.
`As will be understood by one of ordinary skill in the art, a
`fiduciary marker is any visual characteristic of the desired
`renderer 14 that may be used to identify the desired renderer
`14 Such as, for example, a logo or brand name appearing on
`the renderer 14, the dimensions of the renderer 14, a bar code
`placed on the renderer 14, or the like. Other types of fiduciary
`markers may be used and are within the scope of the present
`disclosure.
`In another embodiment, the renderer detection enabling
`component 34 of the mobile device 20 includes a Bluetooth R.
`transceiver. In this embodiment, the desired renderer 14 is
`also equipped with a Bluetooth R) transceiver. A Bluetooth R.
`discovery process may then be utilized to obtain an identifier
`(e.g., a Bluetooth RID) of the desired renderer 14. As dis
`cussed below, this identifier may then be used by the media
`broker 16 to identify the desired renderer 14. If multiple
`renderers 14 are within the range of the Bluetooth R) trans
`ceiver, Received Signal Strength Indication (RSSI) or a simi
`lar technique may be used by the display transfer function 36
`to select the renderer 14 that is closest to the mobile device 20
`as the desired renderer 14. The Bluetooth RID of the desired
`renderer 14 may then be sent to the media broker 16 to be used
`to identify which renderer 14 in the system 10 is the desired
`renderer 14 for the display transfer, as discussed below. Alter
`natively, the desired renderer 14 may not necessarily be the
`closest renderer 14 to the mobile device 20. In this case, the
`renderer detection enabling component 34 of the mobile
`device 20 may also include a digital camera. The user 22 may
`point the digital camera at the desired renderer 14 when
`initiating the transfer of display of video content, and the
`digital camera may be used as a digital range finder to deter
`mine an approximate distance between the mobile device 20
`and the desired renderer 14. The approximate distance may
`then be used in combination with the RSSI values for each
`renderer 14 within the range of the Bluetooth R) transceiver of
`the mobile device 20 to select the desired renderer 14. The
`Bluetooth RID of the desired renderer 14 may then be sent to
`the media broker 16 to be used to identify which renderer 14
`in the system 10 is the desired renderer 14 for the display
`transfer, as discussed below.
`In yet another embodiment, the renderer detection
`enabling component 34 of the mobile device 20 includes a
`GPS receiver and a digital compass. The locations of the
`renderers 14 are known via, for example, GPS receivers asso
`ciated with the renderers 14, manual entry by associated
`user(s), or the like. When initiating the transfer, the user 22
`may point the mobile device 20 at the desired renderer 14. The
`
`25
`
`30
`
`35
`
`40
`
`50
`
`60
`
`65
`
`Page 17 of 24
`
`

`

`7
`location of the mobile device 20 and the direction that the
`mobile device 20 is pointing may the