US007865927B2
`
`(12) Unlted States Patent
`(10) Patent No.:
`US 7,865,927 B2
`
`Brodersen et al.
`(45) Date of Patent:
`Jan. 4, 2011
`
`(54) ENHANCING MEDIA SYSTEM METADATA
`
`(75)
`
`InVemorS: Emilia: 30016261: san 353: CA (SS);
`CZCGES)’ fifhn; 5:11;] Pgflfgiul‘ivgs
`Gatos CA (US) Jeffrey Ma RCdW00d
`City, CA (US)
`’
`’
`
`............. 725/92
`............ 725/108
`
`4/2002 Asmussen et a1.
`2002/0042923 A1 *
`5/2002 Harkness et a1.
`2002/0059633 A1*
`6/2002 Jeannin et a1.
`2002/0083469 A1
`2002/0162118 A1 * 10/2002 Levy et a1.
`.................. 725/110
`2002/0178447 A1
`11/2002 Plotnick et a1.
`2003/0005445 A1
`1/2003 Schein et a1.
`2003/0070167 A1
`4/2003 HoltZ et a1.
`
`(73) Assigneei Apple Inc, C11138111110a CA (US)
`.
`.
`.
`.
`.
`( * ) Notice:
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 15403) by 111 days.
`
`2003/0149975 A1
`2004/0221243 A1
`/
`2004 0221308 A1
`2004/0250217 A1
`
`8/2003 Eldering et a1.
`11/2004 T
`dahl
`t
`l.
`/
`wer
`e la
`11 2004 chtner eta'
`0 0 e a.
`.
`12/2004 T]
`t
`l
`
`(21) Appl.No.: 11/549,103
`
`(22)
`
`Filed:
`
`Oct. 12, 2006
`
`(Continued)
`
`(65)
`
`Prior Publication Data
`US 2008/0066100 A1
`Mar. 13, 2008
`
`GB
`
`FOREIGN PATENT DOCUMENTS
`EP 1289287
`3/2003
`
`Related US. Application Data
`
`(60)
`
`(51)
`
`ll’rogggogal application No. 60/825,242, filed on Sep.
`n .
`.
`I t C1
`(2006.01)
`H04N 7/173
`(52) US. Cl.
`............................ 725/109; 725/19; 725/53
`(58) Field of Classification Search ................... 725/24,
`725/32, 37761, 1057142, 19; 348/161, 526
`See application file for complete search history.
`References Cited
`US. PATENT DOCUMENTS
`
`(56)
`
`(Continued)
`
`OTHER PUBLICATIONS
`International Search Report and Written Opinion, PCT/US2007/
`076076; Dated Apr. 27, 2009.
`
`.
`(Commued)
`Primary ExamineriScott Beliveau
`Assistant ExamineriMichael Telan
`(74) Attorney, Agent, or FirmiFish & Richardson PC.
`
`(57)
`
`ABSTRACT
`
`348/14 03
`'
`
`.....
`
`.
`.
`Systems and methods for prov1d1ng enhanced metadata to a
`user. Systems and methods can include extraction of data
`from metadata and searching for related metadata based upon
`the the ”traded dam
`
`5,621,456 A
`5,880,768 A
`5,933,811 A
`6 216 264 B1
`7,240,075 B1*
`7’340,760 B2
`7,363,591 132
`7,367,042 B1
`2002/0042920 A1 *
`
`4/1997 Florin et a1.
`3/1999 Lemmons et a1.
`8/1999 An 1
`t
`l.
`4/2001 MaieeZte3:
`7/2007 Nemirofsky et al
`3/2008 Wachtfogel et a1 '
`4/2008 Goldthwaite et al.
`4/2008 Dakss et a1.
`4/2002 Thomas et a1.
`
`................ 725/87
`
`28 Claims, 11 Drawing Sheets
`
`500
`
`(—
`
`[505
`
`635
`
`RECEIVE
`SELECTION FR
`CM
`
`USER
`
`
`
`
`
`
`
`
`
` ( 675
`
`PRESENT NON-
` ENHANCED
`ENHANCED
`METADATA
`METADATA’I
`
`
`CONTENT
`
`
`,
`f” 63°
`"""" {2665
`PRESENT
`I
`SYNCHRDNIZE
`ENHANCED
`METADATA WITH
`METADATA
`ENHANCED
`CONTENT
`PRESENTATION
`
`
`
`é
`
`Apple Exhibit 4446
`
`Apple V. SightSound Technologies
`CBM2013-00023
`
`Page 00001
`
`645
`PRESENT
`SUPPLEMENTAL
`METADATA
`CONTENT
`
`840
`
`SUPPLEMENTAL Ya
`NO
`
`65-0
`PRESENT BONUS
`METADATA
`
`CONTENT
`
`510
`.L
`I RECEIVE REQUEST
`FOR ENHANCED
`METADATA
`CONTENT
`
` ; 90'ch OR
`; DEVELOP DATA
`4, FROM METADATA
`I ASSOCIATED WITH
`CURRENT soggy;620
`SEARCH FOR
`RELATED
`METADATA
`CONTENT
`
`
`"
`630
`w—J—Lw
`PROVIDE Rssms I
`TO USER VIA USER 1
`INTERFACE
`
`
`
`
`
`Apple Exhibit 4446
`Apple v. SightSound Technologies
`CBM2013-00023
`Page 00001
`
`

`

`US 7,865,927 B2
`Page 2
`
`U.S. PATENT DOCUMENTS
`
`OTHER PUBLICATIONS
`
`................. 725/32
`3/2005 Tsutsuietal.
`2005/0060741 A1*
`6/2005 Jung etal.
`.................... 710/29
`2005/0120148 A1*
`9/2005 Danker
`2005/0216932 A1
`1/2006 Stark etal.
`2006/0020962 A1
`4/2006 Looney et a1.
`2006/0074769 A1
`4/2006 Zito et a1.
`2006/0090185 A1
`2006/0265409 141* “/2006 Neumann et 31~
`2007/0174872 A1
`7/2007 Jing et al.
`..................... 725/46
`2008/0065638 A1
`3/2008 Brodersen et al.
`2008/0066099 A1
`3/2008 Brodersen et 3L
`
`FOREIGN PATENT DOCUMENTS
`
`Mysmmdsa 111°» Mystmnds DiSCOVerY fOTWindOWSI Internet Cita-
`$g$f§?0239.1686s; WWW~mylsjtr§nis~°Tn§“11'12/‘5‘5306265 fil dA
`PL
`28 2009nterv1ew mummy,
`'
`' PP'
`0'
`,
`,
`6
`’
`'
`.
`.
`.
`USPTO Non-F1nal Office Action in US. Appl. No. 11/530,643,
`mailed Nov. 14, 2008.
`Fish & Richardson P.C., Amendment in Reply to Action dated Nov.
`14, 2008 in U.S.App1. No. 11/530,643 filed Mar. 16, 2009.
`USPTO Intervew Summary, U.S. Appl. No. “549,092, filed Apr.
`21, 2009.
`USPTO Non-Final Office Action in US. Appl. No. 11/549,092
`mailed Feb. 9, 2009.
`Fish & Richardson P.C., Amendment in Reply to Action dated May
`11, 2009 in U.S.App1.No. 11/549,092.
`
`W0
`
`WO 00/33573
`
`6/2000
`
`* cited by examiner
`
`Page 00002
`
`Page 00002
`
`

`

`US. Patent
`
`Jan. 4, 2011
`
`Sheet 1 of 11
`
`US 7,865,927 B2
`
`«we
`«5”
`
`139
`
`~vvvvvan~~vvvnm~~~m~nmnv;
`
`{ZONTROL
`
`
`E NGiN E
`I
`REMOTE
`
`
`
`PROCESSENG
`DEWCE
`
`*
`
`‘
`we ML
`BAR
`f
`,
`.
`H
`NODEVECE
`EENFERFACE
`““““““““““““
`
`
`
`F115
`
`.JWEiE-PLAY
`f ,3 Q5 --------
`EEvscE
`
`
`\fi‘«««ww«.~_«
`g INTERFACE
`
`“£23
`
`
`
`1E1:
`w
`METAIDA“?A
`
`/
`REmsEVALf
`
`ENGiNE
`WWW“ N
`EXTRACTEON
`
`ENE-WE
`,,,,,,,,f
`
`n»»»»»»»»»».“i,
`E Nun's
`{Mm——»»»»»»»»»»»»
`
`-
`i
`;
`
`
`SEARCH
`i USEREE ANNEL BROWSE P‘ffigfifi RECDRD
`
`
`
`..
`a
`.
`ENGINE
`
`we
`150*“;
`14.15%
`150»?
`155%!
`155
`
`SPEAKER
`DEVKCE
`iNTERFACE
`
`ENGWE
`
`ENGiNE
`
`ENGiNE
`
`ENGINE
`
`ENEiNE
`
`FIG. 1
`
`Page 00003
`
`Page 00003
`
`

`

`US. Patent
`
`Jan. 4, 2011
`
`Sheet 2 of 11
`
`US 7,865,927 B2
`
`f~296
`
`/E»22a
`
`1111111111111111L11w
`0
`{ZQNTENT
`,
`PRGWDER
`............MW
`
`24$
`
`,.w......,.,_,,,,,.,.,.,.,.,,,,{f::,T
`METAQMA
`I
`PROWDER
`!
`.m“.........._,-.,
`
`332 3
`"
`3’
`\“K
`
`
`‘
`NéfifibRK
`METAQATA
`
`inJ§§§§§§R€Q
`
`rWN
`V
`
`NEWNQRK'
`
`ff“. I308?
`rmmmmmmwwmwiwwwm
`>>>>>>>>>>>>>>>>1 M58013¥373M
`
`
`
`
`
`
`Fflii,2
`
`Page 00004
`
`Page 00004
`
`

`

`US. Patent
`
`Jan. 4, 2011
`
`Sheet 3 of 11
`
`US 7,865,927 B2
`
`3213
`
`f” 330
`
`303r
`1?
`
`CONTENT
`PROWDER
`
`
`
`
`
`"""
`~
`L§§§ijgDEE“
`(mm...
`!lIIi
`I
`MCQNTENT
`MEYAQATN.
`
`PRODUCER}
`3
`f”
`.
`PRQVZQER
`:
`NISTNNNTQN
`KWWANX
`MW
`“““NETWQNN
`N“
`
`
`
`mW NNTNNNTN
`NETWONN W
`NNNvaNENqs.)
`
`
`
`
`SEARCH
`ENGiNE
`
`
`
`NETWGRK
`
`FIG. 3
`
`'
`
`i
`j
`
`Page 00005
`
`Page 00005
`
`

`

`US. Patent
`
`Jan. 4, 2011
`
`Sheet 4 of 11
`
`US 7,865,927 B2
`
`M 4313
`if
`
`
`
`REC-ENE WEE-C!
`
`CGNTENT RND
`
`METfiDATA
`‘--._u‘--a—-..u_...._
`
`
`
`
`
`EXTRMT QR
`
`
`BEVELQP mm
`
`
`
`
`FRQM ME‘T‘ADATA
`
`ASSQCSATED WiTH
`
`
`
`
`
`£URRENT co-N'nggl
`
`
`
`
`ua-wu ”L --‘--“m‘
`
`SEARCH FER
`
`RELAYED
`
`METAQATA
`
`CENTENT
`
`
`
`
`
`REC-ENE RELATEE}
`
`METRDATA
`
`EQNTENT
`
`
`
`FIG. 4
`
`Page 00006
`
`Page 00006
`
`

`

`U.S. Patent
`
`Jan. 4, 2011
`
`Sheet 5 of 11
`
`US 7,865,927 B2
`
`f 510
`‘ RECEE‘VE REQUES?
`FOR fis. TYPE. cw:
`
`
`
`.mnn.
`
`rm“
`
`ABQWGNAL
`“HEZWMA
`.
`.A..__.W
`K” 520
`I
`{““E‘Sffmm 0R “”1
`g
`{325mm mm ‘
`' FRQM mmmm
`
`ASSOCEATEB mm
`
`
`
`
`
`
`Efifififlf WWENT
`[
`x,» $39
`
`
`
`
`SEfiRCH FGR TYPE
`
`GSNTENT
`
`{33: METADATA
`
`
`
`
`
`
`f.»- 54$:
`
`
`EREGENE METMJATJ
`f
`cemgm
`J
`
`
`
`
`I
`
`i
`
`
`PRESENT
`
`
`METABATA
`
`L“
`
`FIG. 5
`
`Page 00007
`
`Page 00007
`
`

`

`US. Patent
`
`Jan. 4, 2011
`
`Sheet 6 of 11
`
`US 7,865,927 B2
`
`f‘ 535
`
`.......
`RECEWE
`
`
`SELECTEGN FROM
`
`
`
`809
`
`/
`
`.
`
`
`
`E
`
`i
`
`E
`
`*
`
`f,» 845
`
`“‘“‘“‘“ ““““J‘"“"""""‘"“‘,
`
` PRESENT
`
`RECEWE REQUEST
`EUEELEMENTAL
`FOR ENHANCED E
`METAEATA
`METADATA
`
`CONTENT
`‘
`CEMENT
`
`
`E
`«1350
`,1 E15
`
`
`
`
`
`_
`BQNUS
`PRESENTEQNEE
`
`
`CQNTENT
`METAEATA
`
`11—"
`CQNTENT
`
`EXTRACT 1:311
`EEVELEE EATA
`1:110:11 METAEATA
`ASSQETATEE WETH
`
`CEREEN T Cfifijgfi:
`3
`.11“ 11211
`
`
`‘
`
`
`
`SEARCH EOE
`EELATEE
`METADATA
`CEMENT
`
`
`m
`
`,1”;
`,1” ETE
`E
`Y
`
`,,,,,,,,,,,,,,,,,,,,,,,,,,,,{1_________________
`
`PRESENT 1101111
`114"“/
`'
`METAEATA
`EEcgg§UEE1§ECH
`\METABATA?
`
`E
`CENTENT
`‘
`\‘w
`
`881}
`#113115
`YES 1
` SYNCHRONEE
`
`
`PRESENT
`
`PEEVIEE EEEETTE E
`ENHANCED
`ENHANCEQ
`i
`
`
`METAQATA
`METABATA WETH
`;
`T13 usgg V5331 {3-3512
`
`
`
`INTERFACE
`E
`PRESENTANQN
`CGNTE-ZNT
`;
`
`
`
`
`
`-----------------------1
`
`
`fem
`
`ENHANCED
`
`ENHANCEE
`
`FIG. 6
`
`E
`
`1
`
`1
`E
`é
`
`Page 00008
`
`Page 00008
`
`

`

`U.S. Patent
`
`Jan. 4, 2011
`
`Sheet 7 of 11
`
`US 7,865,927 B2
`
`m
`
`mEm.9%gmin”,
`
`Gm?S
`
`
`
`
`
`
`
`
`
`«@sz>Qz<mJmfiw‘yuwmwmmMEIER,.wmAmDmZefiihm,wwg£9.wai
`
`
`
`
`
`
`
`
`
`:mQEhmEIQm3wimp?
`
`gmflmmmwfidzmag
`
`mtmgfiW
`
`
`
`
`swimQM#9..mOuKim§mz<ENSmayFWWMEDU03%w...mwhfimdzfigfigdu x93m<EmEmma. Qmwxmg‘Ewwwgwhit“.wa§>GwmxgmummmwzmwmmawwM4hImuDQIHmemQ3m“MawWszfid‘Eda“
`
`
`
`
`
`
`Page 00009
`
`Page 00009
`
`

`

`U.S. Patent
`
`Jan. 4, 2011
`
`Sheet 8 of 11
`
`US 7,865,927 B2
`
`
`
`m§w$mfiJQDEEQ
`
`
`
`.mvmfixmfimflmumm.
`
`$3,ka
`
`wwwmihzmfiwaflw
`
`ma.£25mmozimzw
`
`
`
`mwihfifimm33n§
`
`mmm
`
`
`
`szEEummmmmmg
`
`
`
`miflfismzQfiaanmm
`
`9mm
`
`w.0...”—
`
`\.mam
`
`6mm
`
`Page 00010
`
`Page 00010
`
`
`
`

`

`U.S. Patent
`
`Jan. 4, 2011
`
`Sheet 9 of 11
`
`US 7,865,927 B2
`
`
`
`:rfigwmamamafine?8.8mEmMS“was.mmmuiufi.
`
`
`
`
`
`
`
`-mafia”Swag,w.§5mEmagma?$.38deEmME
`
`
`
`
`
`
`
`E31“E3%,:m3x33may.”fig”:baa9%Mm.mfifimmm
`
`Eng,EmmagmaESE.m2%P5,#5»?Emma.Romans
`
`
`
`mmgugfig3%SEma.3mama?“{Emcm?3%
`
`
`
`
`
`weasewmaufiflawmwggfifim989%3&mequ
`
`
`
`3mggas.“a.vamfimmmmwmflmwmmémaflamwfiumagma“.
`
`
`
`
`
`
`
`wM333%.»fisfiwmkmwsfifiwfiu.EmmmEcwE3mg»ES50m
`
`
`
`
`
`
`
`
`
`wufiafian85%.439%wEEmgfifimmwfidfimfifim
`
`
`
`
`
`«3.3weM3,;Em:mm.,3mmmwmmmfiwaafimmman.
`
`N
`
`mmfifimfi393$$2.2332E“asmumEQa.
`
`
`wwimdmmuQm
`
`,mmmfimamm
`
`
`
`as3th“Emmg.3w«5.afignxmfiNE353%
`
`
`
`
`
`as“$53,asmay?«as?»«was2%mfimfimwfiwgm
`
`MN“
`
`mmflvaby
`
`
`
`EOFOQ,hfimz&EEQEEV
`
` an?»mmmwumw3$3fimfim.wufimfivgm$34qu
`
`
`
`33ESEmwmfiwfiAmmwgmEwwmflmuuw4533?,Via
`
`
`wing3%.me«5&3?33«mausmmmmmfiefims3.35m
`
`
`
`
`“33%...3ESmfiNewmammumwmwwasmagmaEfim
`EEEEEA44
`mm].20mg;g
`
`
`
`mm_
`
`mwmsonmrm
`
`\umam
`
`Page 00011
`
`Page 00011
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Jan. 4, 2011
`
`Sheet 10 0f 11
`
`US 7,865,927 B2
`
`
`
`
`
`6....QE\Efi
`
`
`
`
`
`ufififiufi,MAEQESEU.
`
`
`
`Euuufifinmgmmwman
`
`
`
`EggwhenEmafiugmmama».ufiwmmwmwegamma.
`
`
`
`
`
`.Ovow
`
`Page 00012
`
`Page 00012
`
`
`

`

`U.S. Patent
`
`Jan. 4, 2011
`
`Sheet 11 0f 11
`
`US 7,865,927 B2
`
`
`
`
`
`“\\‘\\\\1mllxl§lx}€:iil...........................
`
`
`
`3.muE“,3:
`
`aamfiméEmmamaEM3
`RES:mam:mg3mugmmmama
`
`
`
`3;,
`
`Page 00013
`
`Page 00013
`
`

`

`US 7,865,927 B2
`
`1
`ENHANCING MEDIA SYSTEM METADATA
`
`BACKGROUND
`
`This disclosure relates to providing metadata to a media
`device.
`
`Historically, Video content for television was free broad-
`cast Video content. The revenue model for content providers
`was to sell advertising during the free broadcast content. The
`advent of cable television systems has significantly changed
`the business mode for content providers in many instances.
`For example, content providers such as Home Box Oflice
`(HBO), available from Home Box Office, Inc. of New York,
`N.Y., provide broadcast content by subscription service and
`reduce (or altogether eliminate) advertising. Thus, the pri-
`mary source of revenue for such providers are subscription
`services. Such subscription content can be broadcast to
`numerous set-top boxes, and the set-top box can be provided
`keys for decrypting the subscription broadcast signal.
`Further, with the implementation of digital technology in
`most cable and satellite systems, the broadcast content is
`supplemented by metadata content. The metadata content can
`be provided by a metadata content provider on a sideband
`signal to the digital video content signal, or by another alter-
`native mechanism. The metadata content can enable elec-
`
`tronic program guides, which can provide media system 100
`users with programming schedules and detailed program
`information, such as, for example, actors, directors, ratings,
`reviews, etc. In conventional systems, such metadata content
`is limited.
`
`SUMMARY
`
`In one aspect systems, methods, apparatuses, and com-
`puter program products are disclosed for media systems.
`Such systems can include a video input, a metadata input, a
`network interface and a search engine. The video input can be
`configured to receive video content, while the metadata input
`can be configured to receive metadata from a metadata pro-
`vider, the metadata being associated with the video content.
`The search engine interface can be configured to extract or
`automatically develop data from the metadata based upon
`input (e.g., user imputer), search a network using the network
`interface for data related to the extracted data, and to use the
`network interface to pull supplemental program data from the
`network.
`
`In one aspect, methods are disclosed which provide supple-
`mental metadata, for example: receiving metadata associated
`with currently selected video content; extracting search
`parameters from the received metadata; and, searching a net-
`work for supplemental program data based upon the extracted
`search parameters.
`Media systems and methods described herein can provide
`supplemental information to content being presented either
`automatically or based upon user input, thereby allowing the
`user to locate information about the content that may be of
`interest.
`
`Media systems and methods can also provide entertain-
`ment to users in the form of, for example, commentaries,
`bonus footage, interactive trivia, pop-up trivia tidbits about
`content being presented to the user, and other data.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a block diagram of an exemplary media system
`having a network search interface used to search for related
`metadata.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`2
`
`FIG. 2 is a block diagram illustrating an exemplary net-
`work including a media system.
`FIG. 3 is a block diagram illustrating another exemplary
`network including a media system.
`FIG. 4 is a flowchart illustrating an exemplary method for
`retrieving data for a media system.
`FIG. 5 is a flowchart illustrating an alternative exemplary
`method for retrieving data for a media system.
`FIG. 6 is a flowchart illustrating an exemplary method for
`retrieving data for a media system.
`FIG. 7 is a screen shot illustrating an example of a user
`interface for a media system having a related content search
`option.
`FIG. 8 is a screen shot illustrating an example of a user
`interface having a number of search templates which the user
`can select to cause the media system to perform a search.
`FIG. 9 is a screen shot illustrating an example of a user
`interface displaying biographical content to the user upon
`receiving a request from the user.
`FIG. 10 is a screen shot illustrating an example of a user
`interface displaying interactive trivia content to the user upon
`receiving a request from the user.
`FIG. 11 is a screen shot illustrating an example of a user
`interface displaying pop-up trivia content to the user upon
`receiving a request from the user.
`
`DETAILED DESCRIPTION
`
`FIG. 1 is a block diagram ofa media system 100. Media
`systems 100 ofvarious implementations can include a set-top
`box with or without a digital video recorder (DVR) (or, per-
`sonal video recorder (PVR)). In other example implementa-
`tions, a display with built-in functionality (e.g, a television),
`a computer system, a phone, a PDA, an iPOD® (available
`from Apple Computers, Inc. of Cupertino, Calif.), or any
`other media environment. In other implementations, subsets
`of the functionality shown in FIG. 1 could be included in a
`media card for insertion into a display device. Media systems
`100 can be used to connect a media environment to a video
`
`for
`
`content provider, such as a cable service provider,
`example.
`In the example of FIG. 1, the media system 100 includes
`DVR functionality. The media system 100 can include, for
`example, a processing device 105, a data store 110, a display
`interface 115, a speaker interface 120, and other input/output
`(I/O) device interfaces 125, through which I/O data can be
`received or transmitted. I/O devices of various examples can
`include a network interface from an intemet service provider
`(ISP) for example, an external hard drive, a power supply, a
`keyboard, a DVD player and/or recorder, a receiver, etc. The
`above list is not intended to be exhaustive, but merely provide
`a few examples ofthe functionality that can be provided using
`various I/O devices. In various examples, the media system
`100 can include network storage of an alternative data feed in
`place of, or in addition to the data store 110.
`In one implementation, the functionality of the media sys-
`tem 100 is distributed across several engines. For example,
`the media system 100 may include a remote control engine
`130, a user interface (UI) engine 145, a channel engine 150, a
`browse engine 155, a presentation engine 160, a recording
`engine 165, a search engine 170, an extraction engine 175,
`and a metadata retrieval engine 180. The engines may be
`implemented in software as software modules or instructions,
`hardware, or in a combination of software and hardware. The
`software can be stored in a data store (e.g., data store 110,
`flash memory, external memory, read-only memory (ROM),
`nominally powered volatile memory, etc.) during periods in
`
`Page 00014
`
`Page 00014
`
`

`

`US 7,865,927 B2
`
`3
`which the media system 100 is in a standby mode. Upon
`power up, the software is communicated to the processing
`device. 105. The processing device 105 then executes the
`software by performing the commands implicated by the
`software.
`
`In some implementations of media systems 100, the I/O
`device interface 125 operates a hardware component operable
`to receive signals from a remote control 135, which can be
`routed through the remote control engine 130 to process the
`received signals. However, for clarity, FIG. 1 shows the
`remote control 135 being connected to the system using the
`remote control engine. As such, the remote control engine
`130 of FIG. 1 can include hardware which enables the media
`
`system 100 to communicate with the remote control 135. The
`remote control engine 130 can also include software used to
`decode signals and provide commands from the user to any of
`a number of other engines being executed by the processing
`device 105.
`
`10
`
`15
`
`Numerous types of protocols and physical media can pro-
`vide a communication link between the remote control 135
`
`20
`
`and the remote control engine 130, including, among others,
`radio frequency (RF) media, infrared (IR) media, and wired
`media.
`
`Some media system 100 implementations can include a
`docking port 140. The docking port can provide a wired or
`wireless communication connection between the remote con-
`
`25
`
`In some
`trol 135 and the remote control engine 130.
`examples, the remote control 135 itself is a handheld personal
`media device operable to receive, store and playback audio
`and/or video, such as, for example, an iPOD®, available from
`Apple Computer, Inc., of Cupertino, Calif. As such, the dock-
`ing port can provide a mechanism by which a user can man-
`age any downloaded content (e.g., audio and/or video con-
`tent) stored in volatile or non-volatile memory of the
`handheld personal media device.
`The user interface engine 145 operates in conjunction with
`the processing device and provides a graphical user interface
`to the user through a display device interface. The graphical
`user interface can provide the user with a number of interac-
`tive menus that can be selectively navigated by a user. An
`example of a menu implementation can include an electronic
`program guide or interactive program guide. Electronic pro-
`gram guides can offer a user the ability to view a list of
`scheduled programs, as well as read information about the
`programs, set a DVR to record various programs, set remind-
`ers for programs, search for upcoming programs, etc. Other
`menu implementations can include program information
`which can be accessed while watching a program.
`Program information can be obtained using a metadata
`content provider, such as for example, Tribute TV Data, avail-
`able from Tribune Media Services, Inc., of Chicago, III, or
`Gemstar TV guide, available from Gemstar-TV Guide Inter-
`national, Inc., of Los Angeles, Calif. The metadata can be
`pushed or pulled from the metadata content provider. Many
`DVR systems operate using a system whereby the metadata is
`periodically sent to the DVR using the same broadcast trans-
`port stream as the video content data or on a data stream
`alongside the broadcast transport stream. However, there are
`many ways to disseminate the metadata information, includ-
`ing using an internet connection, which can be a dedicated
`connection or multi-purpose connection.
`A channel engine 150 operates in conjunction with the
`processing device 105 and the user interface engine 145 to
`provide information (e.g., an electronic program guide or
`channel information) to a user. The channel engine 150 can
`collect metadata information and associate the metadata
`
`information with a particular channel or program.
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`
`The media system 100 further includes a browse engine
`155. The browse engine 155 in conjunction with the process-
`ing device 105, the user interface engine 145 and the channel
`engine 150 operate to enable the user to browse through an
`electronic program guide or a reduced program guide. The
`browse engine 155 can interact with the channel engine 145 to
`locate metadata for currently browsed channels. The browse
`engine 155 can provide the framework, including for example
`channel slots and time slots, into which metadata from the
`channel engine 150 can be inserted. This framework can then
`be sent to an output display using the user interface engine
`145.
`
`The media system 100 of FIG. 1 can also include a presen-
`tation engine 1 60. The presentation engine 1 60 in conjunction
`with the processing device 105 controls the presentation of a
`content to the user. The presentation engine 160 can decode a
`broadcast data stream and provide the content to a display
`device interface 115, a speaker device interface 120, or com-
`binations thereof. The presentation engine 160 can provide
`the content in a number of formats. For example, the presen-
`tation engine 160 can provide a component video stream to
`the display device interface 115, a composite video stream to
`the display device interface 115, a 5.1 channel signal in Dolby
`Digital or DTS format, or other video or audio streams.
`The media system 100 of FIG. 1 also includes a recording
`engine 1 65. The recording engine 1 65 in conjunction with the
`processing device 105 operates to manage recording of audio
`and/or video content. In some implementations the recording
`engine 165 can include various routines used to interface with
`the user to schedule recordings, track disk space, automati-
`cally maintain and delete recordings based on user input
`received using the user interface. In some implementations,
`recording engine 165 includes tools to erase programs when
`more space is needed, or to alert the user when space is low.
`These and other types of features can be facilitated by the
`recording engine 165.
`The media system 100 of FIG. 1 also includes a search
`engine 170. The processing device 105 executes the search
`engine 170 and thereby enables users to search, for example,
`among the metadata content received from the metadata pro-
`vider, as described above. The search engine 170 can allow
`users to enter search parameters using the user interface
`engine 145. The search engine 170 can use the input param-
`eters to search from among the metadata content stored in the
`data store. There are many searching algorithms that can be
`used to perform a search from among a collection of data,
`including list searches, tree searches, etc. Selection of a par-
`ticular search algorithm can be, for example, dependant on
`the data structure used to store the metadata or by the pro-
`cessing power included in the processing device.
`The media system 100 can also include an extraction
`engine 175. The extraction engine 175 is executed by the
`processing device 105 and extracts data from the metadata
`content either automatically or based upon various param-
`eters requested by the user. The extracted data can be used to
`perform a search for metadata content related to video content
`or audio content currently being presented to the user, or
`related to selected metadata or customized requests received
`from the user. In some implementations, the search can be
`executed using a network such as the internet.
`In some implementations, the user can choose a predefined
`search template to determine which of the data is to be
`extracted from the metadata content. The predefined search
`template, in various example, can cause the extraction engine
`175 to extract data such as actors, artists, directors, producers,
`writers, genre, or combinations thereof, among others.
`
`Page 00015
`
`Page 00015
`
`

`

`US 7,865,927 B2
`
`5
`The media system 100 can also include a metadata content
`retrieval engine 180. The metadata content retrieval engine
`180 is executed by the processing device 105 and receives the
`extracted data from the extraction engine 175. The metadata
`content retrieval engine 180 uses the extracted metadata to
`search for additional metadata content using, for example, a
`network interface. For example, additional metadata can
`include supplemental program descriptions. expounding
`upon the summary description provided by conventional
`metadata providers, reviews, or other related metadata con-
`tent. Other types of metadata that can be retrieved can
`include, among many others: outtakes; biographical informa-
`tion about the actors, director(s), etc.; commentaries from
`actors, director(s), producer(s), etc.; bonus footage (e.g.,
`deleted scenes, alternative endings, etc.); and trivia content.
`In some example implementations, advertising content can
`have associated metadata. In such implementations, media
`systems 100 can examine metadata associated with the adver-
`tising content and cause a search to be performed for metadata
`related to the advertising content.
`In various implementations, metadata content providers
`can include formal metadata libraries such as iTunes, avail-
`able from Apple, Inc., of Cupertino, Calif., imdb.com and/or
`amazon.com, both available from Amazon.com,
`Inc., of
`Seattle, Wash., or netflix.com, available from NetFlix, Inc., of
`Los Gatos, Calif., among many others, and combinations
`thereof. In other implementations, metadata content provid-
`ers can include informal metadata libraries, such as peer-to-
`peer networks, central servers housing user submitted meta-
`data (e. g., wiki sites), social networking sites, etc. Using these
`informal sites, users may choose to communicate recommen-
`dations, ratings, reviews, trivia, etc. to other users. Informal
`and formal sites may also include content recommendations
`and/or ratings from celebrities, critics, etc. Moreover, the
`content recommendations, in some examples, can be tailored
`based upon the user’s previously stated preferences (e.g.,
`stored content ratings).
`The media processing system 100 ofFIG. 1 can also imple-
`ment different functional distribution architectures that have
`additional functional blocks or fewer functional blocks. For
`
`example, the channel and recording engines 150 and 165 can
`be implemented in a single functional block, and the browse
`and search engines 155 and 170 can be implemented in
`another functional block. Alternatively, all of the engines can
`be implemented in a single monolithic functional block.
`FIG. 2 is a network diagram, showing an example imple-
`mentation 200 of a media system 100. The media system(s)
`100 can receive video content broadcast from a content pro-
`vider 220 using a network 230. The media system 100 can
`also receive metadata from a metadata provider 240 using the
`network 230. The metadata received from the metadata con-
`
`tent provider 240 can include a schedule for the content
`received from the content provider 220, as well as informa-
`tion about the content received from the content provider 220.
`The schedule received from the metadata provider 240 can
`include a list of program titles associated with time slots for
`numerous channels received from the content provider 220.
`In some implementations schedule information can be pro-
`vided, for example, for up to three weeks of future broadcast
`content, or up to any future period of time provided by a
`metadata provider 240.
`The information about the broadcast content can include a
`
`number of information fields associated respectively with the
`various program titles. For example, information fields can
`include a rating (e.g., a Motion Picture Association of
`America (MPAA) rating), actors/actresses appearing in the
`movie, director, a summary description of the content, a criti-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`cal rating. The information fields and an associated program
`title can be displayed to the user using the media system.
`In some implementations,
`the media system 100 can
`receive input from a user to retrieve additional metadata con-
`tent from a network metadata provider 250 based upon the
`user’s input. In particular, the media system 100 can retrieve
`related metadata content based upon currently selected con-
`tent (e.g., content currently being presented, title selected
`from an interactive program guide or condensed program
`guide, etc.). In other examples, the media system 100 can
`retrieve metadata based upon user input. The related metadata
`content can be retrieved by extracting or developing search
`terms from the metadata received from the metadata provider
`240. Upon extracting/developing the search terms, the media
`system 100 can communicate with a search engine 260 to
`provide the search terms to the search engine 260. The search
`engine 260 can respond by, for example, sending a link to any
`related metadata content
`fund. Alternatively,
`the search
`engine 260 can be part of a metadata provider 250, or a web
`crawler built into the media system 100. The network meta-
`data provider 250 can offer a user the opportunity to view
`additional metadata content using the media system 100.
`The network 230 can take various forms, such as, for
`example, a cable television network, a packet switched net-
`work, a circuit switched network, etc. Further, the network
`230 in various examples can include a number of sub-net-
`works. Moreover, it is not necessary that the sub-networks
`have the ability to communicate with each other. For example,
`one of the sub-networks can be a public switched telephone
`network (PSTN), while another sub-network can be a cable
`television network, or a wireless communication network
`(e.g., a network under any of the Institute of Electrical and
`Electronics Engineers (IEEE) 802.11, cellular networks,
`microwave networks, etc .).
`As a further illustration ofthe broad disclosure of the types
`of networks that can be included in systems and methods
`disclosed herein, FIG. 3 is a block diagram illustrating
`another exemplary network including a media system 100.
`Media system 100 can be connected to a content provider 320
`using a content provider network 330, and to commercial and
`other services 340-360 using a separate network 370.
`In this implementation, the content provider 320 provides
`broadcast content to the media system 100 using the content
`provider network 330. The content provider network can be
`alternatively implemented using a number of different net-
`works or network configurations, including a cable television
`network, a satellite network (such as direct broadcast satellite
`(DBS)), wireless networks, among many others. The broad-
`cast content can be provided in a variety of different formats
`(analog or digital), including various coding schemes.
`While the content provider 320 can produce and distribute
`original content, the content provider 320 typically operates
`as a last mile distribution agent for content producers/dis-
`tributors 380. The content producers/distributors 380 can
`include, for example, various production companies that
`operate to produce and/or distribute television, movie or other
`video or audio content. The content producers/distributors
`380 can use a variety of mechanisms to distribute content to
`various content providers.
`The metadata provider 340 can be connected to the content
`provider 320 to receive schedule data for dissemination.
`Alternatively,
`the metadata provider 340 can receive the
`schedule information directly from the content producers/
`distributors 380 such as traditional network television pro-
`ducers/distributors (e.g., American Broadcasting Company
`(ABC), NBC, CBS, Fox, etc), or cable networks (e. g., ESPN,
`MTV, CNN, Comedy Central, HBO, Showtime, etc.) to
`
`Page 00016
`
`Page 00016
`
`

`

`US 7,865,927 B2
`
`7
`receive schedule information. In some implementations, the
`metadata can be provided using the content provider 320
`using the content provider network 330. In other implemen-
`tations, the metadata can be provided to the media system 1 00
`using a separate network 370, such as, for example, the inter-
`net.
`
`The metadata content provider 350 operates to, among
`other things, provide metadata to users over the network 370.
`In some implementations, the network metadata provider 350
`can provide the metadata content over a network 370 such as
`the internet. In other examples, the network metadata content
`provider 250 can provide content over a proprietary network,
`a phone network, a wireless network, etc., and combinations
`thereof. In some implementations, the network metadata con-
`tent provider 350 can be user driven. For example, users can
`provide metadata content (e.g., facts about filming, actors,