EWS-005889
`
`Early Warning Services 1019
`IPR of U.S. Pat. No. 8,887,308
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 1 of 10
`
`US 2009/0083541 A1
`
`
`
`‘
`
`Album Name
`
` MP3 Audio Data
` Static Watermark 1-Bit
`
`
`se
`
`
`
`
`Parental Control
`
`
`
`
`
`
`
`
`Transactional
`
`SB3 Header
`
`Data
`
`
`
`NOT
`Encrypted
`“Cleartext
`Header’
`
`Header”
`
`
`
`Encrypted
`“Secure
`
`
`
`
`
`
`.
`
`
`
`Services
`
`FIG. 1A
`(PRIOR ART)
`
`FIG. 1B
`
`EWS-005890
`
`EWS-005890
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 2 of 10
`
`US 2009/0083541 A1
`
`eas,
`
`Japeay
`
`quasalg
`
`JIBLUSIEAA
`
`vOL
`
`
`oIpnyWIAA}XOHBS]DpaydsugjenbiqW
`ayeqJapeoHJapeoyaunjeuBbisydAiouzabesse
`
`
`
`
`
`8Zh9zLSLLPcljeubiqvelZcl
`
`x£¢OL8cl9¢1
`
`
`
`
`alldEGSfeulyauiquiog
`
`eunjeuBis
`
`
`
`uajoun4YySeH185
`
`abesso-w
`
`seidOzt
`
`fay
`
`SbL
`
`SL
`
`Zz
`
`
`
`ZLLZOL80LOLL olpnyindujonEIS{zeaxen/O01
`
`
`
`
`
`ayeqeyepejayy
`
`uonoesuel|
`
`Byepejay
`
`
`
`IBUUaTeAApaquig
`
`vL
`
`LL
`
`XOESID
`
`sapeay
`
`aunoas
`
`Jepeay
`
`Jepeey
`
`paydAisugOlOLL
`
`
`
`AdyJepesy
`
`ch
`
`EWS-005891
`
`EWS-005891
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 3 of 10
`
`US 2009/0083541 A1
`
`
`oaBSEqEIEGsUIlUGUlOlSSIO}SPUEEIE
`
`
`66qejeqSulluO4J8S/Fayelsuasy
`
`
`OeL‘Didulsuogsyyapeayaunoesau,ydAuoug
`FitJJapeaysepeoyaimjeuBlsL‘lqujavosyaunjeuBlsjeubiqysleai5BL
`
`
`
`
`08olpnyWMKOUZIIainaas
`olpny eyepeyayyiB0¢oNeISeed
`
`
`S|lqCASJeuldSYBI]OLSUIGQUIODeeClsFceetereeeeeeerremerrmapmsannnt
`
`
`YIBLUIDIEAA]1ve
`OlpNSHES38D
`JopeeHcds.oopeet
`
`
`
`BVEPEISIWOIPNYDESjeg)1eyedjeuonoesuesys}esaueg:
`':quasn
`
`00¢alpny09
`
`UONOeBSUeLeseqeyed
`
`
`[e0077oeseqejeqd|eo07]u|
`
`
`90S
`
`rayzg
`
`SaA4
`
`
`
`siaysibeyJasn
`
`
`
`synduypuy
`
`
`
`ejeqjeUOSIOg
`
`
`
`siajsiIBaysash
`
`fujBo™uM
`
`PJIOMSSEg
`
`
`
`Jasp]sAeuyey
`
`woJ48jeq
`
`
`
`aseqejeq[2007
`
`
`
`
`
`JOSf)LWOJ4eyepeysyy
`
`99
`
`ChE
`
`|B907JOynduj
`
`aseqejeq
`
`eyeqolpny
`
`
`
`
`
`
`
`OIpryyNAApopes|gpaidAiougyeyBiq
`
`Juasald
`
`pequiz
`
`YIELLUSIEAA
`
`
`
`}XSYeEID,,Puy,JEpeaysunoas
`
`Japes
`
`
`
`eedJEpEsHJapeayPLZ
`
`OL
`
`EWS-005892
`
`EWS-005892
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 4 of 10
`
`US 2009/0083541 A1
`
`abessey|.payipow
`
`
`
`OeJouqAeidsiq“""\-usagseyall4BeeOMSHINYS|llsace
`
`
`
`
`
`
`
`
`
`
`
`Reid9ABHSUBPBAHAll4]
`
`
`
`peaoulayueeg
`
`
`
`©Oldves
`
`
`
`AB]},U0d
`
`Sad
`
`Ele
`
`
`
`ZLesabi)ysabiq
`
`abessayyabesso|Och
`
`
`
`OErece
`
`
`
`
`
`|uoloUn4YseH189)ydhsoeqabescoin
`
`alqoipnyAoebaq
`
`OPpesHegS
`
`aussald
`
`}XOLBE|D
`
`Jepeoy
`
`pajydAusug
`
`JONB9H
`
`1eyiBiq
`
`aunyeubis
`
`EIEUUSIEAA
`
`|zeZZk
`
`BIA
`
`VeSls
`
`O€L
`
`ao¢poe
`
`peed
`
`
`
`$IELUJS]ENAainsiON
`
`Quyainjeubig
`
`Japeay
`
`é]UaSdid
`
`|
`
`©©i
`
`se)
`
`ZOE
`
`
`
`olpnyjndu|
`
`oft
`
`EWS-005893
`
`EWS-005893
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar. 26, 2009 Sheet 5 of 10
`
`US 2009/0083541 A1
`
`
`
`
`
`
`
`uaeg(edly)duesn
`
`cLyOLP
`
`807
`
`OOF
`
`
`
`
`
`aseqeleg|eo07yoeuD
`
`
`
`JOSPFJeJO]JO#9aSOF
`
`9Wodu]sjqeuySanaseqgejeqje007ul]sq]
`
`
`
`yoregheid
`
`
`
`£,310j8gpepodiu;
`
`vyOIA
`
`
`
`E907}YOSYD
`
`ques
`
`aseqejeg
`
`ylyj2007ujS|JesnQHesnPpy
`
`
`BBSO]eseqejeqSct
`IE}O]JOJequini
`
`
`
`FOr feoo*yoy|BlyaseqeieqOL(201)
`
`
`
`}dAl0aqa
`
`
`
`LUI]SULpeyoeeyeney
`
`0
`
`
`
`9bveseqejeq
`
`quesn
`
`oor
`
`ainoas
`
`JapeoH
`
`Japeay
`
`Kay
`
`QLL
`
`DO]‘odasnjey
`
`jualeylgAue;
`
`
`
`BACHS,QUesn
`
`
`
`Aisnoindigueagq
`
`pomelA
`
`
`
`UyS$.GUasnenbiun410
`
`
`
`
`
`
`
`E]USWIUOJIAUZ[2907]
`
`|907
`
`Qnesneasuieay
`
`ejqeug
`
`yoegheidZep9Hodu
`
`(2017)
`
`quesncov
`
`EWS-005894
`
`
`
`all4ogueunyLoduy|
`
`
`
`JUSWIUOWUAUZJe907OU]
`
`Oc
`
`
`
`
`
`}XOHESIOpaydAiouyjeu5ig
`
`
`
`
`
`J9peeHJepeaHainjeubis
`
`9cl
`
`7StLvl
`
`EWS-005894
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 6 of 10
`
`US 2009/0083541 A1
`
`
`
`
`
`
`
`
`
`abesns,qogajepdnweayjspaieysseingWweaysweails
`
`Pics
`diJasn
`
`s,qog
`
`
`
`
`
`WeaAS
`
`Mur
`
`wees
`
`yuayuo4
`
`omePSJEYSUAA
`
`
`
`
`:ayepdnAjpeuoydo
`
`S3]nyweays
`
`
`
`abesnpuy4uUrq
`
`
`
`Sol|¥WOl4Sayny
`
`zd
`
`GSls
`
`
`
`paseysJEpeoHJepeayaumeuBbis
`
`xayealgf/paydhiougjeyBiq
`
`perenalaePoles
`
`!;:weds
`
`
`
`qogO|WeaijspoeysJeAleq
`
`aseqejyeqaulWwol4BuosaulJOAlO}sIHabesy
`BuossitJO(G@alag)Sains}
`
`
`S,qogpuysajnyabesrSJjsaleseuSAejey
`
`paeuspuyadesnJou$.qoguoBulpusdaq
`
`
`
`BusJOLeaspaieysayelidoiddyeaajoy
`
`SomWieel]Sdeysayepdy
`weans
`EpeleusZz
`janesSULwoul:
`
`
`
`
`(S0I/'¥)JUBLULIOJIAUA[2907]Oj]S|l-jOHUAaYINYHoOduiy
`
`
`
`
`qogoO]sainyabesnpuyyur]weesporeusgpues
`
`
`
`JekeidBIDS}UIeE|dWICDsiH
`WOl4QI488$,qogjoBNXy
`
`puy‘seinyeabesn‘yulqweadgspareysypoenxg
`
`
`
`
`
`JepesyHandessulLol4yul]eseyoind
`
`
`
`
`poleusaleUuS
`
`
`dannspodwysah}
`
`jueldwoys.qog
`
`Buosaseyoindaut
`
`
`
`
`
`sseyoind Coc
`
`sainy
`
`aul
`
`
`
`juel|dway‘Buos
`
`
`
`sassacoyJdARiq
`
`EWS-005895
`
`EWS-005895
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar. 26, 2009 Sheet 7 of 10
`
`US 2009/0083541 A1
`
`809
`
`
`
`BYSGanA[E007
`
`uondwepsy
`
`aseqejegq
`
`
`
`SHSQSAAPOUyspeldOL
`
`0S9
`
`
`
`
`
`$a0yJakejgeIpayyJuedW0D
`
`cO9
`
`—_
`
`
`
`JU@LUUOHAUZ{29077O}U]S14ONUeUINYUOdU]
`
`
`
`
`
`‘Gpusjuonsjsenbayaysqan,
`
`
`
`Qjucwoesuei‘ques
`
`olpny
`
`Bjeg
`
`[XxaLea|D
`
`Japeey
`
`pajdAlug
`
`JapeaH
`
`jen6ig
`
`aunyeuBbis
`
`yeu]Jasaywojuy
`
`
`
`ApeailySEHaji4Siu
`
`
`
`powiesapsyuaeq
`
`fe07]euayepdn
`
`9ilqSlULJULsseqejeq
`
`
`
`pawaapeyuaegsey
`
`
`
`S,BHSGEAAYOSUD
`
`4H88SOFaseqeieg
`
`
`
`SEHJasp)SIUL
`
`
`
`pawssapayA|snoiAalg
`
`
`
`Buossius
`
`909
`
`
`
`ysJapeoH
`
`ainoes
`
`q0s9
`
`
`
`2059gos9
`
`ydAbag
`
`Japeey
`
`Key
`
`¥09
`
`egg
`
`
`
`
`
`
`
`SYSGAAU@YO!‘q|uONSesueL]‘q|JUAUOD‘Quasyparauley
`
`arsgOrso|
`
`VvS9
`
`9Sls
`
`0c9
`
`ecg
`
`
`
`UBAIE)BY}SABIISY
`
`
`
`BY|WoldSOVA
`
`aseqeieq
`
`WIMpayeloossy
`
`Buoseu
`
`UudHO|
`
`
`yuryal
`
`uondiuepeayuonoesuely
`
`pappe-anje,
`
`JO1U94Lu0H
`
`BNIES
`
`G9
`
`EWS-005896
`
`EWS-005896
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 8 of 10
`
`US 2009/0083541 A1
`
`cod
`
`cel
`
`bel
`
`bel
`
`9cL
`
`ZHB0/AaQ
`L#01a
`aiqeliod
`alqeod
`JEINIeD
`
`auoudee
`cHOd
`#Od=f#
`qJapiAdid
`¥JaplAoid
`yuayueg
`yuajuey
`002
`
`cOL
`
`902
`
`EBOIAGoeee
`
`ZLaiqeyod
`
`ZHB0INeg
`
`vel
`
`gel
`
`J2iN|}aDhe
`
`|
`
`audud
`
`ccd
`
`eel
`
`paZi[BsJUBD
`
`
`
`JOAINSBurweays
`
`JSAIBS
`
`LANYSALNI
`
`ocl™
`
`JOAIBS
`
`JaAI8SByepeyey
`
`J9AIaSCI
`
`aypeziyeque9 aud
`
`pezyenus5
`gqJa}eyayaug
`
`1981]PeZzijeyusg
`puyaySqay\
`
`uso]PSEZI/eUaD
`puyeusqey,yJa}12j8yaulUD
`
`veeZHB01NEQ]
`
`pepusww0lay
`velsIGeHOd
`;geJEineD‘
`cedc#Odoe
`ColL#Odhe
`uondwepay
` |sow|Z-OlA
`JeYOW9xOUg
`JEVOW949L4g
`
`IBAIBS
`
`Jaaas
`
`IBAIBS
`
`algeod
`
`L#B01Aaq
`
`(jea1sAyd)
`
`2Je218y
`
`(j2o1sAyd)
`
`qsa}1eey
`
`vOL
`
`EWS-005897
`
`EWS-005897
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 9 of 10
`
`US 2009/0083541 A1
`
`©~
`
`8a/
`
`oldas
`
`Joyesauad
`
`Ord
`
`Jas
`
`puewwog
`
`du]
`
`99L
`
`vol
`
`YSeH
`
`JOJBISUGC)
`
`abessayy
`
`\s08iq
`
`soyelsuey
`
`col
`
`
`
`HO,eWay
`
`INObojeuy
`
`092
`
`JBYSAUOD¥/d
`
`8S2
`
`Aoweayy
`
`etQxepeg9)vepeeH
`
`
`anmereceJajo81eq
`
`apea
`
`9G?
`
`cvl
`
`BvL
`
`allqo1pny
`
`yndu}
`
`eas
`
`VLOlas
`
`
`
`YIBLLUBBA)
`
`Joyoa}eq
`
`Aeidsig
`
`pr.
`
`PSL
`
`Japea}
`
`JoydAuoaq
`
`EWS-005898
`
`EWS-005898
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Mar.26, 2009 Sheet 10 of 10
`
`US 2009/0083541 A1
`
`Aoebe7vSIall4dub
`
`AW1)dSilaedW
`
`ON
`
`08
`
`oS
`OQ
`eo
`
`c08
`
`
`
`
`
`
`
`(panouisyseAfiepeesH)SSA
`
`say
`
`JOPEOHCdSoul
`
`IG-Ly¥aeuLSsUyBoulS|:CdS,Wa-b¥SISLS|olpnyyndu}
`
`808
`
`
`
`DISUBIOYJO4puas
`
`uojeBysenu|
`
`8Ola
`
`908
`
`vls
`
`
`
`DUYCesnaleyjavy.
`(palipoySejy4epeaH)EOUBUINY
`
`
`
`
`
`
`
`
`
`SHJEWUS]EAACyalejey
`
`é9ll4Bu}Ul
`
`Adoayaseyoindued
`
`Jespeu“ABidJON|0d“ALVWILISATI
`001yayBuueys)
`
`
`
`equ]ey,UeUL
`
`
`
`Ofuasi]OLBuljdwepyseypIYyDvy)
`
`é6ulus}sry
`
`
`
`S|PHUDONIng‘UO
`
`
`
`
`
`$S37]S.quesnanbiunOJBQUINAsu$s]ZlLes
`
`
`
`
`
`(ISN!PEyONUeEDjejualeg
`
`
`
`SLEall4FSGSjusyIny
`
`Aeid
`
`SSA
`
`EWS-005899
`
`
`Zall4SULuy]yweuUeTeéjUBSeld
`
`
`
`
`uasaidepesyONJapeaycds-_-
`
`ONOJJUOD|P}UaIeYS918
`ONUl]USBHULSsO18
`
`
`
`EWS-005899
`
`
`
`
`
`
`
`

`

`US 2009/0083541 Al
`
`Mar. 26, 2009
`
`METHOD AND APPARATUS FOR
`DISTRIBUTING DIGITAL CONTENT
`
`RELATED APPLICATIONS
`
`[0001] This application claimspriority to U.S. Provisional
`application Ser. No. 60/953,484 filed Aug. 2, 2007, and incor-
`porated herein in its entirety.
`
`BACKGROUND OF THE INVENTION
`
`1. Field of Invention
`[0002]
`[0003] This invention pertains to an apparatus and method
`for exchangingordistributing files with digital content. The
`files include a headingthatis partially encrypted and includes
`various information that uniquely identifies the file. Optional
`data may also be included that enhances or augments the
`digital content or that allows the user to obtain additional
`content, goodsorservices.
`[0004]
`2. Description of the Prior Art
`[0005] Digital content, such as music, is presently available
`from many different sources in many different formats. One
`popular format for this purpose is the MP3 format. This
`formatrefers to the Audio Layer of MPEG1 (a commonvideo
`compression standard promulgated by the Motion Pictures
`Experts Group) and uses well known algorithms for com-
`pressing a sound sequenceinto a very small file (about one-
`twelfth the size of the original file) while preserving the
`original level of sound quality whenit is played. Distributing
`music in the MP3 format offers several advantages, such as
`interoperability among many music devices andonlineretail-
`ers. The processesthus deliver a better experience for the user
`and potentially increase the market size for selling digital
`content.
`
`[0006] Howeverselling music in the standard MP3 format
`also has several disadvantages, such as:
`[0007]
`1. Lack of copy protection functionality or any
`other playback control mechanism for the content pro-
`vider.
`2. Lack of a robust method to identify which
`[0008]
`consumer purchased a particular MP3 file. Even if a
`purchaser’s ID, such as his email address is included in
`the file (e.g., the MP3 header), the file can still be easily
`changed since this information is not protected.
`[0009]
`3.A purchaser or consumerhas no way of know-
`ing that an MP3file is authentic and of high quality, as
`opposed to being poorly ripped from an illegitimate
`source.
`
`4. There is no robust method to assert the copy-
`[0010]
`right of the content and to enable contentfiltering.
`
`SUMMARYOF THE INVENTION
`
`[0011] The present invention provides a system for distrib-
`uting audio files. As part of this system, a new typeofdigital
`file is presented, which is hereinafter referred to as an SB3
`file, that is backward compatible with all current MP3 play-
`ers, and uses the same data compression and header format as
`standard MP3files. Alternatively, the SB3file can incorporate
`content in other well knowndigital audio formats, such as the
`MPEG-AACformat. The SB3files in this format may offer
`value-added content and services (“VACS”) to the consumer.
`In additionthe files may optionally offer playback control to
`the content owners through a combination of watermarks,
`digital signatures and encryption. When consumers purchase
`new SB3 audio files, they may receive VACS that can be
`
`played on respective compliant media playersthat follow a set
`of playback control rules. The goal is to offer (by creating,
`partnering, or acquiring) VACS so compelling that consumers
`will choose to switch from non-compliant MP3 players.
`[0012] More particularly, the subject application pertains to
`a method and apparatus for distributing digital files to users
`from a server using a distributed network. The apparatus and
`method provide a digital file including digital content and a
`header. The headeris partitioned into two portions, a cleartext
`portion and an encrypted portion. The header includesinfor-
`mation uniquely identifying the digital file. For example, in
`one embodiment, the header includes information about a
`respective userofthedigital file. The header may also include
`information about the content,
`the content provider,
`the
`reseller, details of the transaction by whichthe digital file has
`been acquired, etc. This digital file is transmitted over the
`distributed network to a user.
`
`[0013] The user preferably has a compliant player that
`checks the received digital file for a header. If a header is
`found,further processing takes place. Ifno headeris found, in
`one embodiment, the player assumesthat a legacy file has
`been received (i.e., a noncompliantfile) and thefile is stored
`or presentedto the user as required. In another embodiment,
`a watermarkis embeddedin thefile, for example in the digital
`content. The watermark is used to confirm that the header of
`the file Gf any) is genuine.
`[0014] Additional materials Gncluding content, goods and
`services) may be provided that are identified by a token, a link
`or other means. The additional materials may augment the
`content or may include promotional goods or services. The
`user can keep the content and the additional information
`and/or may share it with others depending onthe rules set by
`the provider of the additional materials.
`[0015] The goods and services may be provided in a mes-
`sage ora special link may be providedto one or more websites
`that source additional content. Alternatively, the link or token
`maytrigger a message from a compliant player that includes
`a request for additional materials and the server can pointthe
`request to a content provider or other sources. The additional
`contentis sent to the requesting compliant player.
`[0016]
`In one aspect of the invention, a user purchases the
`file and the file provider(e.g., a retailer or content provider)
`then generates the file including therein a header that incor-
`porates therein one or moredata fields such transactional data
`and/or other information associated with the user, such as user
`ID orhis e-mail. At least a portion of the headeris encrypted.
`Some of the data fields may be incorporated in both the
`encrypted andthe plaintext portions of the header.
`[0017] Whenthe userreceivesthedigitalfile, his compliant
`player checks for the header and the watermark and uses the
`same for authentication. If no header or watermark is
`
`detected, the file is presented as a standard or conventional
`contentfile.
`
`In another aspect of the invention, the present appli-
`[0018]
`cation provides a method and apparatus for distributing digi-
`tal contentfiles in which a digitalfile including digital content
`and a headeris provided. The headeris partitioned into two
`portions, a cleartext portion and an encrypted portion, that
`includes information identifying a respective user of said
`digital file and a link identifying a content source. The digital
`file is transmitted oversaid distributed network to one of said
`
`users. Once the digital file is received, it can be stored or
`played at will. In addition, the digital file is shared by other
`similar users. The header includesa link that can be used by
`
`EWS-005900
`
`EWS-005900
`
`

`

`US 2009/0083541 Al
`
`Mar. 26, 2009
`
`any of the users to receive additional content, recommenda-
`tions and so on. The link can be a dynamic anda static link and
`can lead to a content source that generates a new file or
`streamsthe content.
`
`In another aspect ofthe invention,the link leads to a
`[0019]
`recommendation server that provides recommendations for
`new content.
`
`In another aspect of the invention, a method and
`[0020]
`apparatus are presentedfor distributing digital contentfiles to
`users from a server using a distributed network by providing
`a digital file including digital content and a header, said
`header partitioned into two portions, a cleartext portion and
`an encrypted portion, said header including information iden-
`tifying a respective user ofsaid digital file and a link identi-
`fying a content source.
`[0021]
`In another aspect of the invention, tokens are pro-
`videdin the header. The token can be used to obtain additional
`materials such as various promotional goods andservices.
`The token may be used as part of a customer appreciation
`program.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0035] Audio Watermarking Overview
`is embedded
`[0036] An audio watermark is data that
`directly within the audio signalitself. The audio watermark is
`imperceptible by humans, but can be read by computersoft-
`ware. There are many companies that supply audio water-
`marking technology. The present system can use any audio
`watermarking, as long as(1) it is not perceptible by listeners,
`(11) it is difficult to remove, and (iii) there are enough bits
`available in the watermark payload for our particular needs.
`[0037]
`Presently there are various types of audio water-
`marksavailable, which are broadly classified into two groups:
`static and transactional.
`
`[0038] A static watermark is embedded once per master
`copy, usually by the content owner or provider, before it is
`sent to an onlineretailer or CD replicator. A static watermark
`can include several fields, each field being dedicated to cer-
`tain information, such as:
`[0039] Content ID: includes an ISRC, parental control,
`and assert that it is owned by a distributer. Content
`filtering applications can search for this watermark to
`determineif the file is copyrighted.
`[0040]
`Product ID: This watermark field identifies if the
`file was originally soldon a CD, DVD,digital download,
`digital stream, etc. If such a file were foundin anille-
`gitimate channel, the watermark could determine the
`initial sourceofthe leak.
`
`[0041] Retailer ID: This watermark field identifies the
`nameofthe retailer (e.g., Amazon, iTunes, Napster) that
`distributed thefile.
`
`FIG. 1A showsthe componentsofa priorart digital
`[0022]
`audiofile;
`[0023] FIG.1B showsthe components ofadigitalaudiofile
`generated in accordance with this invention;
`[0024]
`FIG. 1C shows a methodusedbya retailer for gen-
`erating the digital file of FIG. 1B;
`[0025]
`FIG. 2 shows a methodfor generating a similar SB3
`file from a compliant or non-compliant CD;
`SB3 Header Present: This one-bit watermark
`[0042]
`asserts that an SB3 header should be attached to the
`[0026]
`FIG. 3 shows a method performed by a compliant
`player to determine that an SB3file fromaretailer is authen-
`audio data. If an audio file was watermarked with this
`tic;
`field, but there was no SB3 header present, the header
`[0027]
`must have beenillegitimately stripped, andthe audiofile
`player;
`should not be played.
`FIG. 4 shows a method performed by a compliant
`[0028]
`[0043] A transactional watermark is dynamically gener-
`player to determine that an SB3 file from another user is
`ated and embeddedbytheretailer within an audiofile at the
`authentic and authorized;
`time of the sale to the end consumer. Potential transactional
`[0029]
`FIG. 5 shows a method of sharing links between
`users that allow a user to get streamed content;
`[0030]
`FIG. 6 shows a method ofredeeming tokensor value
`added content and services in accordance with this invention;
`[0031]
`FIG. 7 shows a block diagram of a system with
`several users receiving and using SB3 digital files in accor-
`dance with this invention;
`[0032]
`FIG. 7A shows a block diagram of a compliant
`player constructed in accordance with this invention; and
`[0033]
`FIG. 8 shows a process for handling a file with a
`complex watermark;
`
`FIG. 3A shows a display screen for a compliant
`
`watermark fields include one or more of the following:
`[0044] UserID: A unique ID correspondingto the indi-
`vidual user purchasing the content. Ideally, each end
`user has a single UserID acrossall retailers, but this may
`not be commercially viable. Alternatively, each end user
`has one UserIDfor a particular onlineretailer. In other
`words, each retailer provides the sameuser IDtoall its
`purchasers. The UserID may include the user’s e-mail
`address.
`
`the user
`
`[0045] Date/Time: The date and time that
`acquired the content.
`[0046] TransactionID: An ID that uniquely identifies this
`transaction. A retailer should generate a unique Trans-
`actionID for every piece of content it sells. Ideally,
`TransactionID’s would be uniqueacross all retailers, but
`this may not be commercially viable. Details of the
`transaction (such asretail price, client software version,
`IP address, ISRC, UserID, Date/Time) are stored in a
`database and referenced by the TransactionID.
`[0047] Ofcourse, other information maybe included in the
`watermark as well.
`
`SB3 File Format:
`[0048]
`that
`[0049] This
`section describes the “SB3” format
`enables interoperability acrossall conventional MP3players.
`The SB3 format offer users the ability to gain value added
`
`EWS-005901
`
`DETAILED DESCRIPTION OF THE INVENTION
`
`[0034] As previously discussed, the present invention pro-
`vides a system for distributing digital files. Each digital file
`includes a header with an encrypted anda cleartext portion,
`and digital content that is compressed using either an MP3
`compression format, or other well-known formats, such as
`MPEG-AACandothers. The file is termed here an SB3file,
`and as shall be described in more detail below, it is back-
`wardly compatible with conventionalor legacy players (such
`as MP3 players). Optionally, the SB3 files may offer value-
`added content and services (““VACS”). Moreover, optionally,
`playback control is offered to the content owners through a
`combination of watermarks, digital signatures and encryp-
`tion.
`
`EWS-005901
`
`

`

`US 2009/0083541 Al
`
`Mar. 26, 2009
`
`content and services, and may offer the content owners a
`certain amount of content protection.
`[0050] The additional information can be included in an
`in-band audio watermark and/or an out-of-band header. The
`main advantageof placing information in a watermark is that
`the audio watermark is robust (i.e.,
`it is very difficult for
`someoneto removethe information). The disadvantageis that
`there are not manybits available to embedrobustly and inau-
`dibly in a watermark.In addition, audio watermarking can be
`expensive from a time, cost and computational perspective,
`especially if a watermark is embedded in a transactional
`manner.
`
`[0051] On the other hand,it is very simple and inexpensive
`to include a large amount of information, even in a transac-
`tionalbasis, within a headerof an audiofile. The disadvantage
`of a header, as discussed above,is that it is relatively simple
`for someone to removethe headerof an audiofile, replace it
`with a different header, and the resulting audiofile will still be
`playable on any MP3player.
`[0052] The SB3file format includes informationrelating to
`the audio file and the transaction (e.g., the end-user, the
`retailer, the time/date, the nameofthe song,etc.) in the header
`file. It also includes a one bit watermark that will signify that
`a header wasoriginally attachedtothe file.
`[0053] One drawbackto this design is that in the eventthat
`the header of an audio file is removed, the system will not
`know anything aboutthetransaction (e.g., who purchased the
`song, when it was purchased, by whichretailer, etc.). The
`system will only know,by evidenceofthe one-bit watermark,
`that there once was a headerattached.
`
`In other configurations, certain fields are replicated
`[0054]
`from the header, which also places them in the embedded
`watermark. For example, the content owner could include a
`RetailerID watermark and headerof each audiofile before it
`is sent to a particular retailer (e.g., Amazon, Apple, etc.).
`Additionally, a retailer could embed the unique UserID of an
`end-customer in an audio file just before it is sent to the
`consumer. Adding this extra information into the watermark
`will
`require
`additional
`computational
`resources
`and
`expenses, but may be worth the ability to learn more about a
`file’s origin if its header had beenillegitimately removed.
`File Format Overview:
`[0055]
`[0056] The SB3 file will store relevant information about
`the audio file in an SB3 header. The header will be “digitally
`signed”(a cryptographic method to be described in the fol-
`lowing section, Header Security), which will reliably tell the
`media playerclientif the SB3 header or audio data has been
`altered. The audio data within the SB3 file will be embedded
`
`with a simple one-bit static watermark, whichasserts that the
`file should have a Compliant SB3 header attachedto it. This
`one-bit static watermark is referred to as the “SB3 Header
`
`Present” watermark. If a Compliant media playerseesa file
`with an embedded “SB3 Header Present” watermark but
`
`without a SB3 header attached to the file, the player that
`knowsthe headerhas beenillegitimately removed, andit will
`not be played. Certain portions of the SB3 header can only be
`viewed by compliant players, while other portions of the
`header can be viewed by all MP3players.
`HeaderInformation:
`[0057]
`[0058] The structure ofa conventional MP3file is shown in
`FIG. 1A, in which a headeris attachedto the beginning ofthe
`MP3 compressed audio data file. The header usually contains
`static metadata describing the MP3 audiofile, suchastitle,
`
`artist, album, year, genre in addition to technical attributes
`such asbit rate, sample rate, codec version, stereo mode,etc.
`[0059] The SB3 file format is compatible with the MP3
`header format, but also includes some additional information
`in its header, ranging from a few bytes to several megabytes,
`depending on the application. Ifa standard MP3 media player
`does recognize certain fields within an SB3file, it will skip it
`and continue to play the audio. However, compliant SB3
`media players will recognize the additional information and
`will operate accordingly.
`[0060] The header for each SB3 file may contain several
`fields, such as certain static metadata fields that are associated
`with a particular song that a retailer sells. These fields may
`include one or moreofthe following:
`[0061]
`‘Title, artist, album, year, genre, track number,
`cover art
`
`[0062] Bitrate, sample rate, codec version, stereo mode
`[0063] Content ID/recording information (as mentioned
`earlier, the recording/product/retailer information can
`also be embedded in a static watermark if there is an
`additional need for forensic tracking(e.g., if the header
`has been stripped), ISRC, Parental Control.
`[0064]
`Product information: identifies the original distri-
`bution medium, such as electronic download, stream,
`CD,radio,etc.
`[0065] Retailer: includes the nameofthe online retailer
`(e.g. Amazon).
`[0066] User information: includes the Userld and or the
`user’s e-mail address.
`
`[0067] A method for preparing an SB3file by a retailer in
`accordance with this invention is shown in FIG. 1C.
`
`[0068] Whenthe onlineretailer prepares a song to be down-
`loaded to a particular consumer, he creates the various header
`information including the conventional static metadata 102,
`as well as additional information, including an SB3 “header
`present” watermark 104, as well as other additional transac-
`tional metadata fields such as:
`
`[0069] User Data 108 pertainingto the particular user and
`purchaser may include information, such as:
`[0070]
`a. Nameofthe user.
`[0071]
`b. Email address of the user.
`[0072]
`cc. Date/time of the purchase.
`[0073] d.A unique UserID that identifies the user. This
`UserID may be unique acrossallretailers, if it is possible
`to coordinate amongvariousonlineretailers. Otherwise,
`the UserID will be unique onlyto a particular consumer
`at a specific onlineretailer.
`[0074] Transactional data 110 may include information,
`such as:
`
`a.A unique Transaction ID that identifies a par-
`[0075]
`ticular copy of a particular song. This Transaction ID is
`combined with the all of the other information in the
`
`header and is stored in a centralized database (not
`shown).
`[0076]
`b. Several web links that can guide a Compliant
`media player to web pagesthat can offer varied applica-
`tions, such as streamed versions of the song, an online
`retailer to purchase additional songs, a website to
`redeem tokens, and manyothers, as will be discussed in
`the Value-Added Content and Services section.
`
`Inaddition to static & transactional metadata, value-
`[0077]
`added content (“VAC”’) 112, such as a ringtoneor additional
`audio/visual data, can be dynamically inserted into the header
`
`EWS-005902
`
`EWS-005902
`
`

`

`US 2009/0083541 Al
`
`Mar. 26, 2009
`
`[0078] The SB3 header is assembled(step 12). Its structure
`is illustrated in FIG. 1B.
`
`[0092]
`FIG. 2 shows such a method 50. In this method a
`ofaparticularfile for a particular user. For further details, see
`the Value-Added Content & Services section.
`compliant CD 200 is ripped by a compliant CD-ripping appli-
`cation (step 52). As part of step 52, a test is performed to
`determine ifthe user is usingthis application forthefirst time.
`If he is, then in step 54 the userregisters the application and
`provides personalinformationto a central server (not shown),
`preferably online. In step 56, user data 202 obtained during
`the registration process is saved in a user data base 58.
`[0093]
`Ifthe user has registered before (step 52), then in
`step 60 he logsin using a user name and password.In step 62
`the user data 202 is retrieved from the database 58.
`
`In FIG. 1B it should be noted that a portion of the
`[0079]
`SB3 header data is encrypted, while another portion is not
`encrypted. The non-encrypted data, referred to herein as the
`“Cleartext Header’, is viewable by any conventional MP3
`player. The encrypted header data, whichis referred to herein
`as the “Secure Header”, can only be viewed by a compliant
`playerthat has the necessary decryption key to view the data.
`The system hasthe flexibility to determine if certain header
`data fields should be in the cleartext Header, the Secure
`Header, or both. It may be advantageous to include certain
`fields, such as a user’s email address, in both the cleartext and
`secure headers. In this particular case, having the user’s email
`address publicly viewable may have a deterrent factor. Addi-
`tionally, by having the email address alsoin the secure header,
`enable another level of protection for this data. Other data
`fields may also be found in both the cleartext and the secure
`headers. These fields may includetheretailer name, the type
`of media on whichthe contentis originally recordedortrans-
`mitted to the user, tokens, etc. In addition, the audio file 100
`is modified by embedding therein a watermark 104 (step 14)
`resulting in a watermarked audiofile 128.
`[0080] All the headers and the watermarked audiofile are
`combined into an intermediate file 114 that includes the
`secure and cleartext headers and the watermarked audiofile.
`
`[0081] Header Security
`[0082] Because the SB3file keeps very important informa-
`tion in its header, it is vital to know whether the header has
`been altered at any point before it reaches the end-user.
`[0083] When a retailer packages a file for delivery, the
`following steps are taken, as can be seen in FIG. 1C.
`[0084] Using public key cryptography, one or more pub-
`lic/private header keys pairs 116 are generated by a
`central trusted authority (e.g. Verisign) for each legiti-
`materetailer, including on-line retailers (e.g., Amazon)
`or physicalretailers.
`[0085] The secure headerfrom file 114 is encrypted(step
`16) to generate an encrypted header 118.
`[0086] The retailer sends its public key(s) to all of its
`customers when they purchase an SB3file.
`[0087] The encrypted header 118 and the remainder of the
`intermediate file 114 are fed to a hash function generator to
`obtain a hash (step 18) that is used in a message digest 120.
`[0088] Next, the message digest 120 is then encrypted (step
`22) using a message key 122 to create a digital signature 124.
`The digital signature 124, the encrypted header 118, the
`cleartext header 126 and the watermarked audio data 128 are
`
`then combinedto generate the SB3 file 130 (step 23).
`[0089] Alternatively, steps 16 and 18 are combined andthe
`hash for the message digest is generated by encrypting the
`whole intermediate file 114 using the header key and then
`applying the hash function to this encryptedfile to generate
`the digital signature.
`[0090] CD-Ripping Extensions:
`[0091] A compliant media player could also have a CD-
`ripping application, which can produce SB3files from a CD
`that have the same functionality as SB3 files purchased elec-
`tronically online. While conventional CDs have no embedded
`watermarks, in the present invention, a CD that is used has an
`embedded watermark therein as described above “SB3
`Header Present” watermark.
`
`[0094] The compliant application generates in step 50 the
`audio data 204 and the value added content 206 as part of the
`ripping process. The application also determines whetherit
`has Internet access in step 64. If there is no Internet access,
`then the application obtains static audio metadata 208 from
`the user and/or a local data base (step 66). If there is Internet
`access (step 64) then thestatic audio metadata 208 is obtained
`from a remote source (step 68) such as Gracenotes. Alterna-
`tively the metadata is provided by the user.
`[0095]
`In step 70, the various data is combinedas transac-
`tional data 210.
`
`Instep 72 an SB3 Headerpresent watermark 212 is
`[0096]
`embeddedinto the audio data 204. In step 74, the various data
`is combinedinto an intermediate file having a secure header,
`a cleartext header and a watermarkeddigital data. In steps 76
`and 78 the secure header is encrypted anda digital signature
`is created, respectively, as in the apparatus and method of
`FIG. 1C. In step 80, the digital signature andthe file 214 are
`combined to obtain a final SB3 file 216 having the same
`componentsasthe file 130 in FIG. 1C.
`[0097] The method creates SB3 files with the following
`characteristics:
`
`[0098] The ripped SB3files