throbber
EWS-005925
`
`Early Warning Services 1021
`IPR of U.S. Pat. No. 8,887,308
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 1 of 11
`
`US 7,526,650 B1
`
`89>
`
`Empzoo
`
`Ma
`
`Es:
`
`Er2:
`
`ozazém
`
`amz_ozm
`
`Omn=>
`
`szhzoo
`
`M3
`
`\.DMD—4.1mm
`
`pzwpzoo89>
`
`2:
`
`EWS—OO5926
`
`EWS-005926
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 2 of 11
`
`US 7,526,650 B1
`
`
`
`m0_>mDHZMEO
`
`com|\
`
`3Mzo_.r<o_._n_n_<
`
`
`
`NorPZMFZOO
`
`Omn=> aw.
`
`
`DZMDJQI
`
`Mam
`
`
`
`dmzazwOz_n_z<mm
`
`amoz<mm
`
`Emfizoo
`
`ma
`
`EWS—OO5927
`
`EWS-005927
`
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 3 of 11
`
`US 7,526,650 B1
`
`com|\
`
`
`
`woSmDsz30
`
`aim.
`
`
`
`Now(2255.
`
`A8276:5:00%:
`
`Dzmo<wI
`
`
`
`
`
`mamZO_.r<0_._n_n_<MGM
`
`omoz<mm
`
`EEon
`
`.84
`
`
`
`a3mzazwozazém
`
`
`
`NowszhZOOOmD_>
`
`EWS—OO5928
`
`EWS-005928
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 4 of 11
`
`US 7,526,650 B1
`
`N<hvm%n:
`
`szmEmm
`
`maxi
`
`
`
`#9.Q2695
`
`ézEEO
`
`89>
`
`mszem
`
`oiom
`
`
`
`
`
`mwnmomZmn—QI>44<UE>H
`
`Nov
`
`w.qu
`
`EWS—OO5929
`
`EWS-005929
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 5 of 11
`
`US 7,526,650 B1
`
`Qwoz<mm
`
`Own=>
`
` amOqumeO><I_mw>O
`
`
` a555mmoz<mm
`
`
`
`anmohémzmwozém
`
`gszkzoo89>
`
`aHZMFZOO
`
`
`
`
`
`amzazm02.Qz<mm
`
`
`
`
`
`mmz_02wZO_w_OmD02—02(1m
`
`
`
`025.255$59.”.on
`
`CIR5822
`
`555m:
`
`mun/mm
`
`Molm
`
`<H<o<52
`
`mmon
`
`Nlom
`
`
`
`
`
`mamwm<m<H<D0&2.4<ZOmme
`
`ammmEFzmQ“.0mmOkw
`
`>m0._.w_Imm:
`
`NH
`
`%ozmo<mI
`
`EWS—OO5930
`
`EWS-005930
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 6 of 11
`
`US 7,526,650 B1
`
`w>_mwmmwomn_
`EmsomwEm:
`
`”500—2mm0<mm
`
`am._300_>_OZ_DZ<w_m
`
`._m_>m_|_>m0._.w_I
`
`3dNola
`
`EWS—OO5931
`
`EWS-005931
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 7 of 11
`
`US 7,526,650 B1
`
`
`
`ism—40mm10:..—
`
`EEGOmn—
`
`oIEH
`
`
`
`Emaomw55.8.2
`
`2<mwoma
`
`mom
`
`\Emaomm2.3
`
`Eéoomn.
`
`ma
`
`g
`
`EWS—OO5932
`
`EWS-005932
`
`
`
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 8 of 11
`
`US 7,526,650 B1
`
`Now
`
`5me
`
`%.mfi
`
`Emmi
`
`4m>m4>FE30mw
`
`azoomm
`
`4m>m4>tm30mm
`
`mmfi.om§mo:»:<z:
`
`Pwmi
`
`mum:
`
`ma
`
`mum:
`
`ma
`
`m94nm§m0zks<23
`
`ozoomm
`
`DEIF
`
`
`
`4m>m4>tm30mW
`
`mmmD
`
`an
`
`EWS—OO5933
`
`EWS-005933
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 9 of 11
`
`US 7,526,650 B1
`
`mom
`
`#09
`
`81,
`
`.Fzmpzoo89>m>m6mm
`
`mum:".0BE._<zowmmn_mood;
`
`.hzmhzoo89>NT;2_
`
`EWS—OO5934
`
`EWS-005934
`
`
`
`

`

`U.S. Patent
`
`Apr. 28, 2009
`
`Sheet 10 0f 11
`
`US 7,526,650 B1
`
`moor
`
`voor
`
`moor
`
`moor
`
`05—,
`
`NE:
`
`m03._02_ .ZO_.r<_>_mOmZ_
`w>_m0mm
`
` how—mm d5...POMAMW szPZOO
`NIP“—0><._n_w_D«an.202.600:—
`
`
`ZO_._.<SEOH_Z_4<ZmemQ
`
`
`
`292582.._<20mmma55mm
`
`
`Dmhfimm<._.<D<._.m§mam—0mm
`Emsomfi2089.5
`
`.hZNHZOOOwn:>
`
`4m>m3>tm30ww
`4<Zmema
`
`
`
`szhZOOOmo_>MI._.2—
`
`Om0.>OF
`
`.<._.<D<._.m§ZODmm<m
`
`
`
`II!000—,
`
`Q
`
`EWS—OO5935
`
`EWS-005935
`
`

`

`US. Patent
`
`Apr. 28, 2009
`
`Sheet 11 0f 11
`
`US 7,526,650 B1
`
`NON-VOLATILE MEMORY
`
`
` 204
`
`CLIENT DEVICE
`
` TUNERS
`PROCESSOR(S) ,
`DISK DRIVE
`
`
`
`110
`1104
`
` 1112
`
`
`
`USER
`OPERATING
`INTERFACE
`SYSTEM
`
`
`
` 112 1114
`
`
` EPG
`
`APPLICATION
`
`
`1118
`WIRELESS
`
`INTERFACE
`
`
`APPLICATION PROGRAM(S) 1116
`
`
`
`
`NETWORK
`
`INTERFACE
`
`
`
`
`1132
`
`
`
`PARALLEL
`
`1130
`
`SERIAL/
`
`BRANDING
`
`ENGINE
`
`1m
`
`INTERFACE
`
`1 134
`
`
`
`EWS—OO5936
`
`EWS-005936
`
`

`

`1
`PERSONAL IDENTIFIERS FOR
`PROTECTING VIDEO CONTENT
`
`TECHNICAL FIELD
`
`The subject matter relates generally to multimedia security
`and more specifically to personal identifiers for protecting
`Video content.
`
`BACKGROUND
`
`Because software tools for downloading and copying Video
`content are now commonplace, it is easy to fall into an unau-
`thorized practice of inadvertently or purposely redistributing
`proprietary Video content. Although Various techniques haVe
`been implemented or proposed for discouraging unautho-
`rized redistribution of Video content, to such as encryption or
`copy protection schemes, such mechanisms are generally
`complex and relatiVely expensiVe to implement. As described
`in U.S. Pat. No. 6,574,348 to Venkatesan et al., for example,
`digital watermarking may use cryptographic techniques to
`subtly alter Video images so that they may later be identified
`as illicitly copied, eVen when the watermarking cannot be
`perceiVed by the human eye. A watermark typically hides
`information about the proprietor or copyright holder within
`the Video content itself. When the Video content is pirated, the
`watermark is proof that the content originated with the pro-
`prietor. Such digital watermarking schemata, howeVer, are
`“after-the-fact” measures designed to test whether an image is
`a duplicate of an original non-marked image. They constitute
`proofofillicit Video content dissemination after the infraction
`has occurred and typically require enforcement against an
`end user who redistributed the Video content without autho-
`rization.
`
`SUMMARY
`
`Subject matter includes personal identifiers for protecting
`Video content. In one implementation an exemplary branding
`engine receiVes metadata to assist in determining character-
`istics of a personal identifier to add to Video content as a
`deterrent against unauthorized redistribution.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`FIG. 1 is a graphic representation of Video content brand-
`mg.
`FIG. 2 is a block diagram of an exemplary Video content
`branding system.
`FIG. 3 is a block diagram of another exemplary Video
`content branding system.
`FIG. 4 is a graphic representation of an exemplary brand
`located on a rendered image of Video content.
`FIG. 5 is a block diagram on an exemplary branding
`engine.
`FIG. 6 is a block diagram of an exemplary progressiVe
`branding module 520.
`FIG. 7 is a graphic representation of scaling Various brands
`to Various program security leVels.
`FIG. 8 is a graphic representation of scaling Various brands
`to a user’s history of unauthorized dissemination of Video
`content.
`
`FIG. 9 is a flow diagram of an exemplary method of brand-
`ing Video content to deter unauthorized dissemination.
`FIG. 10 is a flow diagram of another exemplary method of
`branding Video content to deter unauthorized dissemination.
`
`US 7,526,650 B1
`
`2
`
`FIG. 11 is a block diagram of an exemplary set-top box
`deVice pr0Viding an enVironment suitable for practicing the
`subject matter.
`
`DETAILED DESCRIPTION
`
`OVerView
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`The subject matter presents techniques for branding Video
`content with an end user’s personal identity information
`(“personal
`identifier,” “mar ,” or “brand”) as a deterrent
`against unauthorized redistribution of the Video content by
`the user. A “user” is a person or personal entity that receiVes
`the Video content to be protected or the owner of a client
`deVice that receiVes the Video content to be protected. This
`branding of a user’s personal identity informationiinstead
`of information identifying the Video content’s original owner
`or copyright holderineed not be complex or subtle. Indeed,
`instead of stealthily hiding the brand, a user’s brand is pur-
`posely placed to be potentially or actually Visible and
`humanly-readable (“legible”) when the Video content is dis-
`played. The display of the brand acts as an effectiVe psycho-
`logical deterrent to remind unauthorized redistributors of
`Video content, both inadVertent and willful, that their dissemi-
`nation of the Video content is unauthorized or illegal. The
`subject matter thus aims to preVent redistribution of content
`before it happens rather than pr0Vide a tool for tracking down
`a user after an unauthorized redistribution of Video content
`
`has already been made. HoweVer, an exemplary brand could
`be used for the tracking purposes as well.
`The ab0Ve-mentioned personal identity information con-
`stituting a brand consists ofone or more pieces ofinformation
`that positiVely identify the user entity who receiVed from an
`owner, broadcaster, pr0Vider, etc., Video content to be pro-
`tected from unauthorized redistribution. A “user” may be an
`indiVidual person or a legal person, such as a corporation. If
`the user is a corporation, then “personal identity information”
`means information that identifies the corporation. Whether
`the user is an indiVidual or a corporation, a personal identifier
`can include a user’s name, address, phone number, email
`address, Internet Protocol (IP) address, account number, cus-
`tomer number, credit card number, set-top box number, driV-
`er’ s license number, social security number, alien registration
`number, tax number, etc.
`Branded Video content “threatens” to reVeal the identity of
`the indiVidual or corporate user redistributing the branded
`Video content to the Video content owner or pr0Vider, to the
`world at large, or to both. In one implementation, a user giVes
`personal identity information to a Video content pr0Vider for
`the purpose of branding Video content under an agreement,
`such as a contract. Thus, the personal identity information
`may be submitted in required fields of an agreement.
`Although the Video content pr0Vider may haVe access to a
`user’s personal identity information, for purposes of exem-
`plary branding described herein the personal identity infor-
`mation is stored at the user’s end, for example on a client
`deVice during installation%.g., on a set-top box during
`installation or actiVation of a cable TV serVice. This means
`
`that the Video content pr0Vider does not haVe to custom-brand
`Video content for eVery user in a Video distribution system.
`Rather, a Video content pr0Vider can just earmark a Video
`content, such as a program, for branding by using the same
`indicator, such as a key, a piece of metadata, an attribute in
`EPG data, etc., for all users. A different brand is then applied
`at each client deVice, identifying the user or owner associated
`with the client deVice. Once personal identity information is
`set up at the user’s end, a Video content pr0Vider can brand a
`
`EWS-OO5937
`
`EWS-005937
`
`

`

`US 7,526,650 B1
`
`3
`program with a personal identifier for each recipient of the
`program without receiving any information whatsoever from
`users beforehand.
`
`When a content provider, such as a multi-service operator
`(MSO), sends analog or digital video content
`typically
`including high premium subscription channel content to
`users, an identifiable mark or logo over the video content
`might block some of the content. Accordingly, in one imple-
`mentation of the subject matter an exemplary brand is added
`to the video content once received at the user’s set-top box
`and unobtrusively located on a border of a National Televi-
`sion System Committee (NTSC) screen format, which is not
`visible to a TV user when the video content is displayed on
`many types of television devices. The unobtrusive border can
`be the area outside the title safe zone. When the “marked” or
`
`“branded” video content is copied to a computer and/or Inter-
`net system, however, the brand is apparent and legible when
`the video content is displayed on a computer monitor. In
`another implementation, a brand is added to the video content
`when the video content is received at the user’s television-
`
`enabled software application. In this case, the brand may be
`apparent each time the video content is displayed. In either
`case, the brand provides a “fear factor” for users who wish to
`avoid having their personal identity information branded onto
`video content to be redistributed to a friend or neighbor, or
`uploaded into the public domain on the Internet.
`In one implementation, metadata, such as electronic pro-
`gram guide (EPG) information sent by a content provider or
`MSO, informs an exemplary branding engine to distinguish
`between video programs to brand with personal identifier
`information and video programs to leave unbranded. Alter-
`natively, metadata may inform an exemplary branding engine
`to distinguish between channels to brand and channels to
`leave unbranded. The metadata can also specify a level of
`security for a program so that a more intense brand can be
`applied.
`In one implementation of the subject matter, an exemplary
`branding engine progresses from visually subtle personal ID
`tagging to more visually obvious personal ID tagging based
`on an end user’s record of unauthorized video content redis-
`
`the exemplary branding engine
`tribution. Alternatively,
`progresses from subtle tagging to visually obvious tagging
`based on the sensitivity of the video content to be protected
`from redistribution.
`
`The described subject matter aims to deter mainstream
`copying and unauthorized redistribution ofvideo content, not
`provide a foolproof method of stopping unauthorized redis-
`tribution. It is always possible to work around most deterrent
`measures, and sophisticated editing could crop or overwrite
`an exemplary brand described herein. Alternatively, a video
`pirate could obtain a black market set-top box to circumvent
`an exemplary branding technique. However, such circumven-
`tion is cumbersome: black market equipment is not easily
`procured and removal of a brand might require dubbing over
`an entire movie. Such circumventing ofthe branding methods
`described herein would likely cost more than buying a copy of
`the video content or a subscription. That methods of deterring
`mainstream copying of proprietary content can be successful
`even though the methods themselves are defeatable is shown
`by recent action of the Recording Industry Association of
`America. By publicizing an intention to take action against
`heavy unauthorized downloading of music content, the mere
`publication ofthe intent resulted in a 15% reduction in pirated
`music over a measured period. Since filing lawsuits, unautho-
`rized traffic at a popular music trading website KAZAA has
`fallen 40% according to Nielsen/Net ratings (March 3-Au-
`gust 3).
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`4
`
`In is also worth noting that a potential unauthorized redis-
`tributor who knows of an exemplary brand on the video
`content he is about to pirate, may be additionally deterred by
`the thought of additional identifiers potentially hidden in the
`video content. In other words, a potential content pirate might
`fear that since the video content contains at least one known
`
`personal identifier, then like some types of paper money the
`video content might contain a plethora of anti-counterfeiting
`measures.
`
`As shown in FIG. 1, an exemplary video content protection
`engine (“branding engine”) 1 00 receives analog and/or digital
`video content 102 and adds a legible, human-readable, brand
`104 to create branded video content 108. A brand 104 is
`
`potentially visible when the video content 102 is displayed or
`otherwise rendered depending on the location of the brand
`within a video frame or scan pattern.
`The exemplary branding imparted by the subject matter
`can be used with many types of video content 102, and is
`particularly relevant for analog video, thereby providing a
`security solution for an unauthorized redistribution risk
`known as the “analog hole.” Often analog video content can
`be received in a format that has no built-in security mecha-
`nisms and is delivered unencrypted to most users. Thus, unau-
`thorized redistribution of analog video content that has been
`converted to a digital form is particularly difficult to control.
`An exemplary branding engine 100 can impart a brand 104 to
`digitized analog video content, thereby affording video con-
`tent 102 being received in an analog format the same protec-
`tion as video content 104 being received in a digital format.
`Video Content Branding Systems
`FIG. 2 shows a video content branding system 200 in which
`a headend 202 sends video content 102 to a client device 204,
`such as a user’s set-top box for television. The term “client
`device” 204 refers to an electronic device that receives, stores,
`or sends video content. Client devices may include televi-
`sions, television set-top boxes, personal computers (PCs),
`personal digital assistants (PDAs), digital versatile disk
`(DVD) players, personal video recorders (PVRs), and other
`video-enabled pieces of hardware and/or software, etc. An
`exemplary client device 204 shown as an example device
`suitable for practicing the subject matter described herein is
`illustrated in FIG. 11.
`
`In one implementation, an exemplary branding engine 100
`is associated with an application 206 in the client device 204,
`such as a software application in set-top box middleware. The
`application 206, including the branding engine 100, brands
`all or selected video content 102 with a user’s personal iden-
`tity information. The personal identity information may be
`subtle, such as a personal account number known only to an
`M80, or obvious, such as the user’s name. Use of private
`information, of course, may be agreed to by contract before
`video content is sent to a user.
`
`FIG. 3 shows another video content branding system 300 in
`which a headend 202 sends video content 102 and metadata
`
`302 about the video content 102, such as guide listings or
`other electronic program guide (EPG) information, to a client
`device 204, such as a user’s set-top box or television-enabled
`computer. An application 206 in the client device 204
`includes an exemplary branding engine 100 that uses the
`metadata 302 to decide which programs or channels associ-
`ated with the video content 1 02 to brand. The branding engine
`100 may also use the metadata to decide a degree of brand-
`ingithat is, a branding strength or intensity.
`As shown in FIG. 4, an original video frame or scan pattern
`400, after branding, may retain a brand 104 in a typically
`hidden border 402 of the video frame or scan pattern. On
`many types of television and video equipment, a user sees
`
`EWS-OO5938
`
`EWS-005938
`
`

`

`US 7,526,650 B1
`
`5
`only part of the image projected by a cathode ray tube, for
`instance, in a typically Viewable area 404. Video content
`displayed outside a title safe zone is normally not Visible to a
`user on conventional teleVision equipment. In many cases, the
`brand 104 can be placed in a location on one or more Video
`frames or within a scan pattern that results in an overlay that
`is not apparent when the branded Video content 108 is ren-
`dered on teleVision equipment but becomes Visible when the
`branded Video content 108 is readied for unauthorized distri-
`
`bution on personal computer equipment. To recapitulate, if an
`exemplary brand 104 is placed outside a title safe zone in
`some teleVision formats it will not show on many types of
`TVs, but when transferred to a personal computer, the exem-
`plary brand 104 is Visible because personal computers gen-
`erally do not crop or hide the borders of an image.
`An exemplary brand 104 may be a set of rewritten pixel
`Values that appear as the user’s information, such as an iden-
`tification (ID) number, set-top box number, name, address,
`account number, etc., to produce branded Video content 108.
`When Viewed in a personal computer and/or Internet context,
`the brand 104 is typically Visible to a human Viewer.
`In one implementation, an exemplary brand 104 does not
`need to be placed on eVery frame or scan of a sequence of
`Video images. For some types ofa client deVices 204 that haVe
`limited resources and/or limited processing power, an exem-
`plary brand 104 may be placed on eVery “nth” frame or
`included in eVery “nth” scan of analog Video content. At a
`display rate of 28 frames per second, perhaps only eVery 7‘11
`frame would receiVe an exemplary brand 1 04. The exemplary
`brand 104 would still appear on the displayed Video content
`and pr0Vide a deterrent to unauthorized redistribution.
`In one implementation, an exemplary branding engine 100
`can place an exemplary brand 104 as part of a pre-existing
`menu bar or 0Verlay mechanism. In other implementations,
`an exemplary branding engine 100 generates a fresh 0Verlay.
`Branding Engine
`FIG. 5 shows an exemplary branding engine 100 in greater
`detail than in preVious figures. A metadata reader 502, brand-
`ing decision engine 504, personal identity information data-
`base 506, and brand generator 508 are communicatiVely
`coupled as illustrated. The branding decision engine 504 may
`further include a progressiVe branding module 510. The per-
`sonal identity information database 506 may further include a
`use history 512 and a store of identifiers 514. The brand
`generator 508 may further include a brand selector 51 6 and an
`0Verlay generator 518. A person haVing ordinary skill in the
`Video arts will appreciate that an exemplary branding engine
`100 may include more, less, or different components than the
`illustrated branding engine 100, which is presented merely as
`one example.
`A brand generator 508 produces an exemplary brand 104
`that may haVe multiple characteristics. An exemplary brand
`104 can be just one piece of personal identity information
`about a user of the Video content, but in some circumstances
`may be multiple pieces of personal identity information.
`Thus, the brand generator 508 composes a brand, including
`the personal identity information to be placed in the brand, the
`number of locations within a Video content frame to place the
`brand 104 (a brand 104 could be repeated in multiple places
`within a Video frame or a single brand 104 could consist of
`different pieces of personal identity information, each placed
`in a different location within a Video frame), the size and color
`characteristics of the brand, etc.
`In one implementation, a metadata reader 502 receiVes
`metadata 302, e.g., directly from a headend 202 or from a
`local metadata store. Many client deVices 204 receiVe Video
`content in a stream, but receiVe EPG metadata 302 in a packet
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`6
`that may pr0Vide program listings for seVeral weeks of pro-
`gramming at a time, that is, the client deVice 204 may store
`seVeral weeks’ worth of EPG metadata locally. The metadata
`reader 502 sends the decoded or currently releVant metadata
`to the branding decision engine 504. In one implementation,
`the metadata reader 502 also interprets the metadata 302, but
`in another implementation the branding decision engine 504
`interprets the metadata 302. The metadata 302 may contain
`instructions for branding Video content 102. Certain pro-
`grams or channels may be marked for branding, e.g., with the
`same kind of marking that is used for other EPG attributes
`such as “stereo,” “rating,” “pay-per-View,” “dolby,” etc. This
`type of metadata 302 may indicate in a “yes-or-no” fashion
`whether the branding decision engine 504 should proceed
`with branding a giVen Video content 102.
`If metadata 302 releVant to the Video content 102 being
`receiVed exists, then the metadata 302 may also sometimes
`pr0Vides security information to the branding decision engine
`504 to be used by a progressiVe branding module 510 asso-
`ciated with the branding decision engine 504, as discussed
`below.
`
`The branding decision engine 504 receiVes the metadata
`302 or interpretation from the metadata reader 502 and may
`be employed to decide whichparts or programs within a Video
`content 102 are to receiVe a brand 104. When the branding
`decision engine 504 decides to brand a Video content 102 or
`program, an indication is sent to the brand generator 508 to
`brand the associated Video content 102.
`
`A progressiVe branding module 510 associated with the
`branding decision engine 504 may use security information
`receiVed Via metadata 302 to decide a security leVel for the
`brand 104 to be applied and accordingly, the degree or inten-
`sity of branding to use. SensitiVe Video content 102 (e.g., as
`designated by an MSO) can receiVe a stronger brand 104 than
`unimportant Video content 102. Public domain content may
`not receiVe any brand 104 at all. The decision, including a
`security leVel and/or an intensity of branding to use is sent to
`the brand generator 508.
`The branding decision engine 504 can also receiVe input
`from a personal identity information database 506, which
`includes personal identity information of or about the user.
`Some of the personal identity information may be identifiers,
`such as name, phone number, set-top box number, etc., kept in
`a store of identifiers 514. The progressiVe branding module
`510 can also use other personal identity information from a
`“use history” 512, which is a record of a user’s history of
`unauthorized Video redistribution, if any. The use history 512
`can be used like a “credit report” to assist the progressiVe
`branding module 51 0 to decide the intensity ofthe branding to
`apply, in the same way that security leVel information from
`the metadata 302 assisted the progressiVe branding module
`510 to decide branding intensity. If the user has a clean
`history, i.e., a high credit score, then only low intensity brand-
`ing may be needed. But ifthe user has a low credit score from
`seVeral incidents of unauthorized action, then the branding
`decision engine may inform the brand generator 508 to apply
`higher intensity branding.
`The brand generator 508 receiVes or has access to Video
`content 102 for potential branding, wherein the Video content
`102 may be receiVed directly from a headend 202 or may be
`receiVed from a local store of Video content 102. The brand
`
`generator 508 also receiVes decisions about whether or not to
`brand a program and the associated branding intensity to use
`from the branding decision engine 504, as described ab0Ve.
`Thus, a brand selector 516 associated with the brand genera-
`tor 508 can determine characteristics of the brand 104 based
`
`on the decision and security leVel information receiVed.
`
`EWS—OO5939
`
`EWS-005939
`
`

`

`US 7,526,650 B1
`
`7
`The brand selector 516 selects a format for the brand 104 or
`
`builds a brand 104 that may haVe characteristics, such as an
`amount of personal identity information about the user to use
`as a brand 104, the actual personal identity information about
`the user to use in or as the brand 104, a Visual size ofthe brand
`104 relative to a display size of the Video content 102, and a
`display location or locations for the brand 104 within a dis-
`played image of the Video content 102.
`An exemplary brand generator 508 may also include an
`0Verlay generator 518 to place or embed the brand 104 “in,”
`“on,” “0Ver,” or “with” the Video content 102. These Various
`terms are used to indicate a brand 104 being added to Video
`content 102. In other words, no matter what form the Video
`content 102 is in when it is output as branded Video content
`108 from a client deVice 204, e.g., a set-top box, the brand 104
`is combined “in” or “with” the Video content 102 so that when
`
`the branded Video content 108 is displayed on equipment, the
`brand 104 is Visually located “in,” “on,” or “0Ver” the dis-
`played Video content (eVen though the Visibility of the brand
`104 may be obscured by the TV set cabinet, for instance).
`In one implementation, the exemplary 0Verlay generator
`508 creates a title bar menu 0Verlying rendered Video content
`images on which the brand information can be displayed.
`AltematiVely, the 0Verlay generator 508 rewrites pixels of the
`Video content 102 without reference to creating a menu on
`which to post the brand 104.
`In some implementations, if the rendered Video content
`102 is a sequence of frames or scans, the brand 104 may only
`need to be placed on eVery “nt ” frame to be Visible for
`deterring the user from redistributing the Video content 102.
`For example, if a Video sequence plays at 28 frames per
`second, then displaying the brand eVery 7th frame may be
`sufficient to pr0Vide a humanly Visible brand.
`FIG. 6 shows the exemplary progressiVe branding module
`510 of FIG. 5 in greater detail. Since the progressiVe branding
`module 510 may receiVe information for deciding a branding
`intensity from one or both of the metadata 302 and the use
`history 512,
`the progressiVe branding module 510 may
`include a use history reader 602 and a security leVel module
`604 to interpret security information from the metadata 302
`and/or the use history 512.
`FIG. 7 shows Various brands 104, 702, 704 placed on Video
`content 102 according to a security leVel. A predetermined
`security leVel as such may be assigned to the Video content
`102 (or programs within the Video content 102) by certain
`types of EPG metadata 302 or, a security leVel may be deriVed
`from the metadata 302 by an exemplary branding engine 100.
`In a Variation, the security leVel module 604 may determine
`the security leVel of a program based on security cues in the
`Video content 102 itself (not using the metadata 302) or based
`on the manner of the reception of the Video content 102. For
`example, the security leVel module 604 may read the Video
`content 102 and assign a security leVel of “two” out of four to
`all programming that is receiVed as a “liVe” broadcast. Or
`again, a security leVel module 604 may be programmed to
`assign a security leVel of“two” to those programs whose EPG
`metadata 302 indicate they are m0Vies. In some implementa-
`tions, an extra layer of metadata 302 may be used,
`i.e.,
`included in EPG information receiVed from a headend 202,
`that indicates each particular program to be branded, and in
`some implementations, the security leVel to be assigned to
`each.
`
`WhateVer technique is used to animate an exemplary secu-
`rity leVel module 604, the security leVel module 604 or other
`parts of a branding engine 100 may assign different brands
`104 to different programs or Video contents 102. For example,
`a low security program 706 may be branded with a standard
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`(e.g., relatiVely low security) brand 104 that consists of a
`number that only indirectly identifies a user, displayed in an
`area of rendered Video content that is usually not Visible on a
`teleVision set. A medium security program 708 may be
`branded with a relatiVely medium security brand 702, for
`example, a multipart brand 702 haVing a relatiVely obscure ID
`number part that only indirectly identifies the user, and a
`user’ s name part, both placed in a border ofthe rendered Video
`content that in usually not Visible on a teleVision set. A high
`security program 710 may be branded with a relatiVely high
`security brand 704, for example, a multipart brand 704
`including a relatiVely large ID number part placed in a border
`of the rendered Video content that in usually not Visible on a
`teleVision set and a user’s name part, this time placed in a
`Viewable, but normally unobtrusiVe area of the rendered
`Video content.
`
`FIG. 8 shows security leVels assigned to Video content 102
`on the basis of a user’s history of unauthorized dissemination
`of Video content. Accordingly, in one implementation a user
`history reader 602 in the progressiVe branding module 510
`may read a use history 512, for example, in a personal identity
`information database 506 of a branding engine 100. A user
`802 with a use history 512 indicating no unauthorized uses
`may be assigned a type of brand 104 that is relatiVely innocu-
`ous, such as an indirect ID number hidden on a border of the
`rendered Video content.
`
`A first-time offending user 804 may haVe a use history 512
`that triggers a progressiVely larger, more obVious, and/or
`multipart brand 702. Likewise, a second-time offending user
`806 may be assigned an eVen larger, more obVious, and/or
`more “personal” brand 704 that more directly identifies the
`user. Hence, an exemplary progressiVe branding module 510
`may increase deterrent characteristics of brands, such as their
`size, brightness, position within an image, and degree of
`exposure of priVate personal identity information as the secu-
`rity of the Video content and/or the use history 512 of a
`particular user warrants.
`Exemplary Methods
`FIG. 9 shows an exemplary method 900 of branding Video
`content to deter unauthorized redistribution of the Video con-
`
`tent. In the flow diagram, the operations are summarized in
`indiVidual blocks. The operations of the exemplary method
`900 may be performed in hardware and/or as machine-read-
`able instructions (software or firmware) that can be executed
`by a processor or a deVice, such as a deVice that includes an
`exemplary branding engine 100.
`At block 902, Video content 102 is receiVed. The Video
`content 102 may contain indiVidual programs and/or chan-
`nels containing indiVidual programs. The Video content 102
`may be analog or digital and may be displayable as a scan
`pattern on teleVision equipment, or as one or more Video
`frames or images on digital Video display equipment.
`At block 904, personal identity information of a user is
`included in the Video content 102 for potentially Visible dis-
`play when the Video content 102 is displayed.
`FIG. 10 shows another exemplary method 1000 of brand-
`ing Video content 102 to deter unauthorized redistribution of
`the Video content 102. In the flow diagram, the operations are
`summarized in indiVidual blocks. The operations ofthe exem-
`plary method 1000 may be performed in hardware and/or as
`machine-readable instructions (software or firmware) that
`can be executed by a processor or a deVice, such as a deVice
`that has an exemplary branding engine 100.
`At block 1002, Video content 102 is receiVed.
`At block 1004, metadata 302 related to the Video content
`102 is receiVed.
`
`EWS—OO594O
`
`EWS-005940
`
`

`

`US 7,526,650 B1
`
`9
`At block 1006, a

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket