» 1::4
`
`Em
`OE m
`c: E
`H‘—‘°
`c; g
`7.1”: U
`0') E
`”a;
`.3 :3
`{Egfii
`“5‘ §.\
`SE'
`2:: E:
`== "’
`Sa§>
`E- 5'
`‘ This is a request for filing a PROVISIONAL APPLICATION FOR PATENT under 37 C.F.R. “3'3 g5
`§ 153(0).
`’
`' —
`
`W- 10 rag
`
`,
`
`.
`
`COVER SHEET
`
`flgyo/
`
`,
`
`.i
`
`. 4
`
`Docket Number
`
`26006.0002U1
`
`Type a Plus Sign (+)
`inside this box -' - - -
`
`+
`
`INVENTOR(s)/APPLICANT(S)
`
`LAST NAME
`
`FIRST NAME
`
`MIDDLE INITIAL
`
`RESIDENCE (City and Either State 01‘ Foreign Country)
`
`-- Atlanta,Georgia
`
`PLATFORM PORTABLE SOFTWARE PLAYBACK ENGINE FOR AUDIO AND VIDEO ASSETS
`
`TITLE OF INVENTION (280 characters max)
`
`Other (specify)
`
`CORRESPONDENCE ADDRESS
`
`D. Andrew Floam
`NEEDLE & ROSENBERG, PC.
`Suite 1200, The Candler Building
`127 Peachtree Street, NE.
`Atlanta
`
`STATE
`
`ZIP CODE
`
`303031311
`
`COUNTRY —
`
`ENCLOSED APPLICATION PARTS (Check All That Apply)
`
`Specification
`
`Number of Pages
`
`Claims
`
`Number of Pages
`
`Drawing(s)
`
`Number of Sheets
`
`[]
`
`[]
`
`Small Entity Statement
`
`Power of Attorney
`
`[]
`
`[]
`
`[]
`
`H:\apps\ss\docs\dat\W046576.WPD
`
`-1-
`
`Page 1 0f 29
`
`LG EXHIBIT 1010
`
`Page 1 of 29
`
`LG EXHIBIT 1010
`
`

`

`METHOD PAYMENT OF FILING FEES FOR THIS PROVISIONAL APPLICATION FOR PATENT (Check One)
`
`AMOUNT
`
`[] A check or money order is enclosed to cover the filing fees.
`
`FILING FEE
`
`The invention was made by an agency of the United States Government or under a contract with an agency of
`the United States Government.
`
`[X]
`
`No.
`
`[]
`
`Yes. The name of the US. Government agency and the Government contract number are:
`
`
`
`Date
`
`1/19/00
`
`D. Andrew Floam
`
`REGISTRATION N0.
`(IfAppropriate)
`
`34,597
`
`
`
`
`YPED or PRINTED NAME:
`
`EDLE & ROSENBERG, P.C.
`
`finite 1200, The Candler Building
`“127 Peachtree Street, N.E.
`
`
`
`tlanta, Georgia 30303—1 811
`
`CERTIFICATE OF EXPRESS MAILING
`
`EXPRESS MAIL NO. EL219086865US
`
`[hereby certify that this correspondence is being deposited with the United States Postal Service as Express Mail Invoice No. EL219086865US in an
`envelope ddressed to: BOX PROVISIONAL APPLICATION, Assistant Commissioner for Patents, Washington, DC. 20231, on the day and year indicated
`
`can
`
`Sylvester
`
`9
`
`\ [lemon
`
`H:\apps\ss\docs\dat\W046S76.WPD
`
`-2-
`
`Page 2 of 29
`
`Page 2 of 29
`
`

`

`
`
`'fabie of Contents
`
`Version 1.0.0
`
`‘1.
`
`2.
`
`
`introduction ......................................................................................................................... ’IO
`
`1. 1 Beam”: PLIRPOSE‘.
`,
`............................................................................................................................ 19
`, 1.2
`DESCRIPTION OF Mfimwemcy USED TO CREATE m DOCUMENT"
`10
`1.3
`Emmom, Acmmms AND ABBREVLmQNS .............................................................................................. 11
`
`REHRENCES“
`1.4
`...................................................................................................................... 12
`
`OVERVEW ..............
`1.5
`13
`Executive Summary ......................................................................................................................... 'i 5
`
`
`
`
`
`3.
`
`PROD’UCT CONCEPT ............................................................................................................................................. 15
`2.1
`Producf Ofiérz‘ng
`15
`2.1.1
`2.2
`TARGET MARKETS AM} CHANNELS
`15
`
`PROJECT OBJECTIVES ..................................................................................................... 16
`2.3
`
`....I6
`2.3.1
`Primw‘yNeezis..............
`
`Prqfecf Goa! .........................
`2. 3.2
`I6
`
`............................................................................. 1 6
`"2.4
`KEY PRODUCT REQUIREMENTS
`
`Product Concept Svewiew ...........
`..................................................................... 17
`
`
`3.1
`ZAPIUKEBOX ................................................................................................... 19
`
`3.2
`ZAPSTAHON ..............................
`19
`3.3
`....... 20
`ZAPCEH‘RAL...
`3.4
`ZAPACCESS ..............................................................................................
`20
`3.5
`IVAULT .....................................................................................................
`20
`3.6
`ZICHARGED .......
`20
`3.?
`PRODUCT MAP ..................................................................................................................................................... 18
`
`4 User Characteristics.......................................................................... L....."............................................ 1 9
`
`4.1
`19
`PRELMJNARY USE CASE ANALYSIS .................................................
`
`4.1.1
`Actors ............................................
`...1
`
`4.1.2
`............................................................................................................ 19
`Use €332.51...
`
`4.2
`H051: PC ................................................................................................................................ 23
`User Backgroumi............ 20
`4.2. 1’
`
`PiayM’zwéc & Waieo .................................................................................................................. 23
`4.2.2
`
`Dmmz'ozszusic a": f/‘itfeo .............................................................................................................. 23
`4.2.3
`4.2.1.
`Synchronize :Music & Video
`
`4.3
`ZAPSTATION
`
`. .
`. .
`.2}
`
`UserBackgrozmci ......
`
`4.3.1
`
`5. ZapJukebox System Architecture .............................................................................;........................ 22
`
`5.1
`5.2.1
`5.1.2
`5.2.3
`
`22
`TOPOLOGY..
`LoomPlayback ................................................................................ 26
`
`
`NewarkPlaybacfi; ...................... 26
`Imemet Streaming..................................................................................................................................... 27
`
`6.
`
`Product Features ............................................................................................................................... 25
`
`6.1
`SUMMARY .......................................................................................................................................................... 25
`6.2
`DESCRIPTIONS ....................
`
`6.2.1
`Sfieamng Camneis' ...................................................................................................
`..
`
`6.2.2 fsczvz'gaie Sireams. ....................................................................................................................................... 30
`
` 1
`WW
`§
`333%..ézémw; éz'szfiwwm
`
`.3
`
`Page 3 0f 29
`
`Page 3 of 29
`
`

`

`Version 1.0.0
`
`6.2. 3
`Audio Pfayback........................................................................................................................................... 30
`6.2. 4'
`Video Pfayéack.................................................................... 30
`
`6.2.5
`Integrafed iysfemef Browser ...................................................................... 31
`
`62.6
`CD Piayéacfc zirRecord ................................
`....31
`
`6.2.7
`...32
`CBDB...................................
`
`5. 2.8
`M'efa Dam Dasqéme......................................................................................... 32
`
`6.2.9
`. 33
`Piaygis? Comimcziafl'.................................
`
`6.2. f 0 Virmaffisxef flimy ........................................................... 33
`
`Sync Wizfiz Extermfl fievices........................................................................ 33
`(5.2. I Z
`
`Timménws‘ Pyévz'ew ................................
`.. .28
`6.2.12
`
`
`DVD Playback............................................ 34
`6.2.13
`
`In:ema¢ionaiizafion.........,....................................,
`..................................29
`6.2.14
`Single Window Inteigface .......................................
`....35
`6.2.15
`
`35
`6.2.16
`Skin Banister
`
`Oracle 8i Lite Database................................................................................... 36
`6.2.1 7
`
`....36
`6.2.18
`26132406635 .......................................................................................
`
`....37
`6.2.19
`iVmIi.................,
`
`Java CodeBase...............................................................
`....37
`6.2.20
`6.2.2] Automatic Livgmée ........................................................................................
`7
`
`....37
`6.2.22
`Ecommerce Enabied
`
`Unique Seria[i\7umber.....................'_..:.Z,
`‘
`....................................................
`.
`. ........................... 38
`6223
`
`7. OEM Extensions and Customization .................................................................................................. 32
`
`Constraints, Assumptions and Dependencies .....................................a.......................................... 33
`8.
`8. RISKS”............................................ 41
`
`
`
`
`WW
`. W
`WW
`WW;
`g
`imagéefiaa; 3’22? rzmswfi-
`g
`
`Page 4 of 29
`
`Page 4 of 29
`
`

`

`
`
`Zapgakebox ERD
`
`“
`
`< :.
`
`1. introduction
`
`1.1
`
`Eocameht Purpose
`
`This Product Requirements document {9RD} is intended to specify the product attributes of the
`Z2i product. The expected audience for the document is anyone involved with the product, both
`at Z2i and our partnets', as well as potential OEMs and customers
`
`This Product Requirements Document was created by Z2i marketing, engineering, manufacturing
`and customer service organizations based on competitive comparisons and technology vision.
`it
`serves as the singular product specification for the ZapJukebox product. it is intended to capture
`a common View of the overall attributes that meet the needs of the customer.
`
`Any issues that surface during the Discovery or Foundation Phases are being captured within an
`lssues database.
`lnvestigation and resolution of these issues will be performed during
`Foundation or during review and signofi of this document.
`
`White in many cases further detail mayor may not be known at this time concerning specific
`features, this detaii will be captured with rigor during the Foundation phase. The desire at this
`stage is to capture the product user ferret requirements at a consistent level of granularity.
`
`1.2
`
`fiescription of Methodoiogy Used to Create the Document
`
`The format of this document is based upon framework captured in historical developments of
`ZZi’s engineers Revisions to the format, such as addition, deletion, or relocation of certain
`sections, have been made where appropriate and value was added to the document.
`
`This document also uses the IEEE Recommended Practices for Software Requirements
`Specifications.
`. m
`
`Throughout this document the verbs shalt, shaft not, shoutfishouid not, and may are used
`consistentiy‘ with lEEE and other international Standards, astoiiows:
`
`a Any statement in this document using the verb shali or the phrase shall not represents a
`"requirement" (is, mandate). This defines that the software/hardware will not be acceptable
`unless these requirements are provided in an upon agreed manner Each shali requirement
`will aiso be tagged with a [PRDXXX] to indicate a requirement number. The numbers will not
`be reused if a requirement is deieted or change to should or may. For reference the last
`used requirement number wiil be indicated here as {PRDXXX}.
`
`El
`
`Any statement in this document using the verb should or the phrase shoutd not represents
`a "recommendation“ (is, encouraged, but NOT a requirement). These arierequirements that
`would enhance the sofhwarefhardware product, but would not make it unacceptable if they
`are absent.
`‘
`’
`
`:1
`
`any statement in this document using the verb may represents a “option“ (is, permitted, but
`NOT a requirement). These are requirements that may or may not be worthwhile. {Note that
`may not is not useful in this context. The verb may suffices as an eitherfor option, and may
`not wouid be confused with shail not.)
`
`
`
`Page 5 0f 29
`
`Page 5 of 29
`
`

`

`Zapéakebog'PRD
`
`1.3
`
`Definétions, Acmnyms and Abbreviations
`
`
`
`Term
`Definition
`
`
`
`flPEG
`~ “
`Motion Pictures Experts Group
`MP3
`,.
`‘
`.F
`MPEG ‘i Layer 3 audio format
`
`1
`EEAC
`)
`Enhanced Perceptuai Audio Code:
`
`
`Quickfime
`Appie’s AudioNideo
`;—
`1
`
`
`
`
`
`“T
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Page 6 0f 29
`
`Page 6 of 29
`
`

`

`Zapiekebox PRD
`
`
`T
`Yer-m
`i
`Definition
`
`;
`‘1
`
`
`
`i
`r
`i
`I
`I
`
`
`ii
`
`i i
`
`
`
`
`
`
`
`
`i
`
`i
`i
`
`i
`
`I
`
`
`
`
`
`2
`T
`x ‘
`
`Tame *1;Qefintrons
`
`J
`
`
`
`
`
`
`
`
`“3.4
`
`References
`
`‘
`
`
`The foiiowing documents of the issue in effect on the date of this specification form 21 art of this
`sgecification to the extent snecified herein.
`in the event of a conflict between the documents
`referenced herein and the contents of this specification, the contents of this specification shail be
`considered a superseding requirement
`'
`
`
`Source Document
`
`Author
`
`,
`
`T
`
`Reference
`
`
`
`Tabi‘e 2. Reference Documents
`
`——=———————___—__._______—________
`
`memwfwmmw
`i;
`{canfleestie? miefrmeee
`g
`
`5
`
`Page 7 0f 29
`
`Page 7 of 29
`
`

`

`ZapfokcboxPRD
`/ _> in
`; "
`
`The documents listed beiow are either appiicable to this specification or provide supplemental
`information for this specification.
`in the event of a conflict between the documents referenced
`herein and the contents of this specification, the contents of this specification snail supersede
`those of the referenced document.
`
`1
`‘
`
`
`
`L
`
`SourceBecurnent
`
`lEEE Guide for Beueioping
`System Requirements ~
`% Specifications
`‘
`.
`
`
`
`
`Reference
`
`iEEE Std 1233-1996
`
`;
`
`*
`
`1
`i
`
`Author
`
`iEEE
`
`lEEE
`
`g lEEE Recommended Practices
`{ for Software Requirements
`, Specifications
`r
`7
`
`ESE Std 830-1993
`‘
`
`‘1
`
`
`
`Tobie 3. Suppi‘emem‘al Reference Documents
`
`'i .5 Guewiew
`
`in addition to this introduction, this document contains the following sections:
`
`Section 2:
`
`Section 3:
`
`Section 4:
`
`Executive Summary introduces the product concept and provides a high-level
`description of the product offering. Target markets, project objectives and key
`product requirements are presented.
`
`Product Concept Overview includes high—IEWI‘pl’OdUCt architecture along with
`product feature and functionality summaries. , tn addition, a product map and
`possible future product features and accessories are provided.
`
`User Characteristics detaiis the typical users of the system, their background,
`roles and responsibiiities, and interactions with the system. Use cases are also
`covered to detail the user scenarios that the software is intended to address.
`
`Section 5:
`
`ZapJukebox Software Architecture outlines the high level components that are
`essential
`to the operation of the sofmare. The areascouered include the
`
`software modules, and briefly describe how the major product features fit within
`the architecture.
`’
`
`Section 6:
`
`Product Features sets forth and defines the system ievel
`
`features and
`
`associated system requirements. Each feature is discussed with respect to the
`other maior components within the sofhivare.
`
`Section 3’:
`
`infotainment appliance Requirements describes the requirements necessary
`for an GEM engine to become ZapEnabled. This includes the OS, processor,
`memory, e.c.
`
`
`
`
`Page 8 0f 29
`
`Page 8 of 29
`
`

`

`Zagekeboxieno
`
`Section 8:
`
`OEM Extensions and Customization outlines the extent to which Zapdukebox
`will accommodate GEM-specific and market differentiating features.
`
`Section 9:
`
`Constraints, fissumptions and Dependencies details the baseline knowledge
`fromwhich all of the above were derived.
`
`Section 13:
`
`ErroriReference source not found. discusses the next steps Within the overall
`Project‘Plan. This section contains an estimate of efforts required to move
`through the RapidDevelopment Phase
`
`Section 12:
`
`Error! Reference source not found. identifies an ongoing list of areas where Z2i
`
`resources, experience, technology, source code, and so on can be leveraged to
`aid the project.
`
`Section 13:
`
`Risks discusses any (items which are not well-known and may therefore
`adversely impact cost and schedule.
`
`Section 14:
`
`identifies any open and unresolved issues
`Error? Reference souroeinet found.
`that exist at the time of printing this document.
`
`Appendix A:
`
`Features Matrix represents a roadmap for features and functionality in terms of
`Zapdukebox release versions.
`
`Appendix 8: Workshop Matrix outlines the features and functionality that were discussed in
`the Z2i ZapJukebox workshop held from WSW-toMIDIY
`
`Appendix C: NV Codes Selection Guide presents a conglomeration of information about
`potential AV coder: vendors for the ZapJukebox product.
`
`
`
`
`
`
`WWWJWHW
`
`i
`g
`
`”WW:”WWW“?
`,.
`.
`m
`sensaeoea? refs. merger;
`g
`
`7
`
`Page 9 0f 29
`
`Page 9 of 29
`
`

`

`ZapEéflre’oox PRD
`
`2. Executive Summary
`
`this section introduces the product concept and provides a high—level description of the product
`offering. Target markets, project objectives and key product requirements are presented.
`
`2.1
`
`Product Contact a
`
`The ZapJukebox product concept evolved from a desrie to create highly portable cross-platform
`playback engine for audio and video assets.
`it was further desired that this engine might be the
`functional basis for consumer intortainment appliances.
`
`The ZZi soitware solution wiil allow PC, Mac and Linux usesr to play back music, video and
`interactive assets on their respective platforms.
`
`There are several fundamental objectives behind the Z2i Zapdukebox product.
`
`DDDEJUEJU
`
`Provide a cross-platform music and Video Jukebox.
`
`Provide a Java based multimedia player.
`Provide a highly portable and flexibienplattorm for GEMS
`
`Provide for a means of security for content owners
`
`Provide for “virtual access” to a users stored assets.
`
`Provide integration with the 22$ ZapCentral portal site.
`
`Provide a basis for a continuing revenue stream for ZZi.
`
`2.1.1 Product Offering
`
`The host—based software should operate on any Microsoft 95.198 or NT4.0i’5.0 Windows—based
`computer. Additonally,
`it should operate on any PowerPC based Macintosh with appropriate
`subsystems.
`Lastly,
`it should operate on a Linux x86 system with appropriate hardware
`components. This software may be purchased separately, or may be included as part of an OEM
`ZapStation player package.
`
`A path to provide advanced features Via the installation of additonal software will be provided for
`customers who require more sophisticated AV capabilities. These advanced capabilities should
`integrate seamlessiy with the remaining Z2i system. The advance software may be a product
`offering separate from the basic ZapJukebox software.
`
`2.2
`
`Target Markets and Channels
`
`The ZZi Zapdukebox product is currently targeted to be marketed to customers through the
`following channels
`
`:1 OEMs — Manufacturers of PCs and consumer electronics devices —— namely ZapStatIons. As
`previously stated above,
`the ZapStatlon embedded component may be included in the
`consumer appliance at manufacture time. However, the ZapJukeboX system should remain
`disabled until the host software has been installed and activated.
`
`
`
`
`g
`
`Condemned; reformation
`
`g
`
`
`
`Page 10 of 29
`
`Page 10 of 29
`
`

`

`ZapfukebogPRD
`
`D End User Consumers - Anyone wanting to listen to Music and video on their PC, Mac or
`Linux box.
`
`2.3
`
`Proiect Chic-actives
`
`2.3.1 Primary Needsn
`Low cost} high periormance, high sound and video quality.
`
`2.3.2 Project 8an
`
`Produce a cutting edge product that wili aliow for Z2i market penetration in the digitai media
`distribution and webcasting business.
`
`2.4
`
`Key Product Requirements
`Low UMC
`
`
`
`The ability to deliver a free as wed ass ‘very low cost software package to the masses that will
`enable virtual asset ownership and manégement essential. Most of our would be competitors
`provide versions of music and video players for free and charge for a higher performance
`upgrade. Our target price is $0 for a limited feature set and $30 for the enhanced feature set.
`The component cost for the free version shouid be “free” and no more than $5 for the enhanced
`version.
`
`High Performance
`
`The Zapdukebox sewers shail take advantage of the computers processor speed and memory
`to give a very responsive “feel" to the user.
`lt should quickly execute mouse commands and
`various functions in tine with competiton.
`
`High Audio and Video Queffh/
`
`Using the iatest in audio and video codes technology, ZapJukebox shall deliver excellent output
`quaiity.
`
`
`
`
`WW .. WW
`2
`Sorrows? goéerezeeee
`
`g
`
`9
`
`Page 11 of 29
`
`Page 11 of 29
`
`

`

`Zapgfakebog, PRD
`
`3. Product Concept Duet-view
`
`This section includes high-level product architecture along with product feature and functionality
`summaries.
`in addition, sales configuration, a product map and possible future product features
`and accessories are provided.
`
`3.1
`
`Zapdukebox .
`
`U
`
`Zaodukebox consits of a combination of Java and C++ code for playing back audio and video
`assets on PC’s, Mac’s, Linux systems and future infotainment appliances. The bulk of its code
`shall be based on Java to allow for maximum portabilty across many platforms.
`it is meant to
`piay popular audio formats such as MP3, EPAC, WAV, REAL and video formats such as MPEG,
`REAL and other Quicktime Codecs. The Zapdukebox shaii have OracleLite relational database
`at its core to ailow it to be more adept at performing is multimedia data management and
`synchronization functions.
`
`This document wili encompass the feature list and provide a rudimentary layout of the
`Zapdukebox architecture only. Throughoutthis document, certain assumptions have been made
`with regards to the audio and video codecs. The application will also provide ability to send and
`receive multimedia fiies using TCPi’iP. Thekuser wilt be able to select ZapCentrai using their web
`browser or the built —in HTML Window.
`V
`
`3.2
`
`ZapStation
`
`ZapStation is a free standing consumer appliance which is built by third party manufactures to the
`reference specification provided by Z2i.
`it wiii run the ZapJukebox Software Engine for GEMS.
`This device wiil exceute most of the functionality of the computer based Zapdukebox.
`it will use
`a Television screen for the presentation of its GU: and it wiiiaiso have a small DIN‘l sized Vacum
`Fiourescent Dispiay (VFD). Upon first glance the ZapStation shall resemble a consumer
`electronics DVD piayer. This unit shall connect to the internet via broadband as well 56KB
`modem. Through a broadband connection the ZapStation snail have the abiiity to download
`audio and video a rate which wiii be very pleasing. Connection at 56KB will be more patience
`challenging.
`
`Some of the features are enumerated below.
`
`:1 DVD Player
`
`El MP3 I Digitai Music Jukebox
`
`:i Digitai Video MPEG3 Piayer— Downloaded Video
`:1 Web Browser
`
`2 Emaii.
`
`a Chat >
`
`El Graphicai user interface for event control and system administration
`El Personalized lnformation Presenter
`
`3.3
`
`ZapCentrai
`
`——-——-_____—_____—___—_____
`
`
`
`é
`
`(Comatose? Faxcroaica
`
`g
`
`
`
`Page 12 of 29
`
`Page 12 of 29
`
`

`

`ZapiukeboXEPD
`
`ZapCenttal shall be the portal that wiil feed the Zapdukebox as well as ZapStation clients around
`the world.
`it shall provide a personalized View of itself to each user if requested. A user of
`ZapCentrai must register to have access to its data fiies. Once registered: the member’s profile
`wili be used to deliver is presentational experience. ZapCentral shall house thousands or millions
`of assets that can be requested by ZZi Members.
`
`3.4
`
`ZapAccess
`
`ZapAcoess shai'i’be a service program that is facilitated by ZapCentral and sold by music and
`video retailers. Once’a customer becomes a ZapAccess member, they will have the right
`purchase, download and use any associated multimedia assets that they have rights to. Asset
`rights can be ourchased or given away freely, depending on. the posting artist ZapAccess shall
`also allow for the concept of Virtual Asset Ownership and Distribution. Throught the ZapAccess
`membership. Z2i Wilt allow members to synchronize their multimedia databases across their
`Z2iCharged sotbrvare platforms and appliances.
`
`3.5
`
`iVAULT
`
`iVauit is the marketing name for core tachnoiog}! which shall serve as the basis for our Virtual
`Asset Ownership and Distribution progtamjiVAULT is synonomous for Virtual Asset User Library
`Technology.
`it is premised on four undefigling functions: rights management, watermarking,
`encrypting and containment.
`
`3.6
`
`ZZiCHPxRGED
`
`Z2iCHARGEB shall be the monika that wiii be appiied to consumer appiiances which are
`powered by the Zapdukebox OEM Software Engine.
`it will be exploited like "lntellnside”,
`"OnOracle’fi “Bothy" and others. All ZZICHARGED applianaes‘sryitt have internet connectivity as a
`core functionality.
`~‘
`
`3.7
`
`Product Map
`
`ZapCentral
`Web Broadband interface
`
`
`
`
`
`
`
`
`
`
`
`5
`
`: Easter istediétihraf‘r‘t:
`Easter Oracié‘SQWE?‘
`
`
`
`E»
`
`.
`
`uaauotalaeote.
`
`.l
`
`
`
`Operating System
`
` m W
`
`otimmwwmmmmwmwsamm
`gasses:as; fr:rormaace
`
`mm
`
`/I
`
`Page 13 of 29
`
`Page 13 of 29
`
`

`

`’ Zaprskebox PRD
`
`
`4. fiser Characteristics
`
`4.1
`
`Preiiminary Use Case Ahalysis
`
`This section is see-e present a preiiminary use case anaiysis for the Quasar system.
`
`
`
`Piay Music 8‘ Video
`
`
`
`
`fl Downioad Music a Video
`
`ZapJukebM Synchronize Music &
`
`User
`Video
`
`
`ZapAccess
`User
`
`ZapCentrai
`
`4.1.1 Actors
`
`Figure f.” Prelimlh‘ary Use Case Diagram
`
`Zapdekeoox User — represents the directly connected user ot the ZapJukebox. The user
`represents the primary end customer for the ZapJukebox product.
`
`ZapAccess User - represents the remotely connected‘o'ser' oi the Zapdukebox to his assets
`from a Zapswtion or via browser. This user accesses his owned assets via the iVAULT
`modei.
`'
`
`4.1.2 Use Cases
`
`Pia}! Mesic a Video — Music and video assets can be piayed iocaily on any Zapdukebox
`player. The assets can reside or: the hard driver or be streamed from the remote ZapCentrai.
`Doweioad Music 8: Video — Music and video assets can be downloadedfrom ZapCentral or
`other internet sites. Only ZapAccess purchased assets can be distributed as a part of the
`iVAULT service.
`\
`
`Synchronize Music & Video— Any music of video that exist on one‘s PC can be synchronized
`or replicated to other authorized Z2iCHARGED devices. A ZapAccess user can View or listen
`to their assets from many different places; on their PC, ZapStation or via remote browser.
`
`4.2
`
`HGST PC
`
`This section specifies the generic user characteristics associated with a ZapJukebox that is
`running on a PC. The audio and video quality associated with playback is being defined internally
`at 22i. A test suite of tits shali be used in the deveiopmeht and QA process to insure quaiity
`standards.
`
`W.
`
`W ,
`.mmc
`it
`sooeeeea‘aé missed-ass
`
`g
`
`1.2.
`
`Page 14 of 29
`
`Page 14 of 29
`
`

`

`ZagfiakebogPRD
`
`4.2.1 User Background
`
`The target user should be anyone who owns a Windows PC, Mac or Linux PC who wishes to
`download and playback music and video files on their system. The user should be familiar
`with standard PC types of applications and using the internet.
`
`a1.2.2 Play Music & \fiqee
`Typical media played on the Zapdukebox wilt be songs, movies, small video clips, narrations,
`etc The sound quaiity associated with playback will be CID-Transparent using “Hi-Quality”
`settings and Good with “Standaxl” settings.
`
`The Video image quality associated with ZapJukebox playback will be dependent on the input
`datatile.
`
`4.2.? Download Music a Video
`
`Typical media played on the Zapduhebox will be songs, movies, small video clips, narrations:
`etc. The sound quality associated with playback will be CID-Transparent using “Hi-Qualit3f’
`settings and Good with “Standard? settings.
`The Video image quality associated saith Zapdukebox playback will be dependent on the input
`datafile.
`_
`
`4.2.4 Synchronize Music 8: Video
`
`Music and Video shall be capable of synchronization with the ZapJukebox user’s ZapCentral
`ZapAocess account. Once synchronized, a user can (assess their media files from other
`Z2ECHARGED oilents.
`~
`
`
`
`
`
`@MWWWWWWW‘4meWW
`
`5
`§
`
`.
`.
`.~
`.
`,
`.
`fieeeeaeea referaseeee
`
`E
`
`3
`
`/
`
`Page 15 of 29
`
`Page 15 of 29
`
`

`

`ZapJukebox PRD
`
`4.3
`
`ZagStation
`
`This section specifies fire generic user characteristics associated with a Zapd’ukebox GEM
`Software Engine that is running on a ZapStaticn infotainment appiiance.
`
`4.3.1 User Backgréiifid
`The target deer ehculd be a common electronics appiiance consumer who wants to piay
`music and video in his home. Even though the ZapStation could be used for business
`purposed, its primary market target is the home.
`
`
`
`———-——————-—-———.——_—__._—_—__—__
`
`
`WWW
`N
`y
`t
`a,
`,
`5 ’ V . 'V
`mwwmmm
`igléfiéfigfiffifiz {fiffi‘fii'flé‘fifié
`
`:4:mm
`
`Wn/
`
`/4
`
`Page 16 of 29
`
`Page 16 of 29
`
`

`

`Zapg‘skeboxv PRD
`
`5. Zapétfitebox System Architecture
`
`5.1
`
`Topology
`
`The current Zapddk‘eboé; product concept envisions that the product may be operated in three
`distinct topologies,:Tbgese topologies are summarized as Local Playback, Network Playback and
`lnternet Streaming,
`’
`
`5.1.”! Local Playback
`
`in this topology, the ZapJukebox software is playing assets that reside on internal hard drives,
`CD, DVD, Floppyr or other removable media.
`it is assumed that the media has a transport
`rate essential for maintaining quality playback from and “data rate” standpoint. This is the
`model that most users will use on a daily basis.
`
`
`
`@953
`
`Figure 2: Local Pfayback Topology
`
`The points of most relevance in the Local Playback topology are listed below.
`
`a Host is capable of playing music in this configurationas a background task. Other
`applications can function in the foreground.
`~
`'
`
`D Host processor is responsible for decompressing the media files with its internal
`processor,
`
`is responsible for providing multimedia data at a rate necessary to allow the
`El Host
`ZapJukebox to render “Excellent” quality sound and video.
`
`is resopnsible for providing necessary sound hardware for music and voice
`Ci Host
`rendition.
`
`5.1.2 Newark Playback
`
`ln this topology, the Host machine of the Zapdukebox is connected to an networked server or
`a mounted hard drive on a computer which is on its local network. The network should allow
`for '10 Mbs data transfer rate. Based on network trafic, sound and video quality can be
`degraded during playback. This topology is used in many offices where assstes are shared
`and security is at a minimum Secured file types are not permitted in this senario.
`
`
`
`A‘
`
`g
`g
`
` W“mm
`«-
`.
`-
`< v
`to
`‘
`t
`2e-
`$5.???"fififiaé {3?}???£31639???
`
`mat
`
`\vii
`
`Page 17 of 29
`
`Page 17 of 29
`
`

`

`ZagjekeboxltDRD
`
`
`gt......Ewe
`
`ZeoJukebox Host
`
`Network Server
`
`Figure 3: Network Playback Topology
`
`The points of most relevance in the Client Cnly topology are the following:
`Cl Zapdukebox host is capable of playing multimedia in this topology from any connected
`server.
`
`Other Zapduke box clients can'ac‘cess server data.
`
`Server data cannot be ZapAooess'secured.
`
`a Server data is only “referenced” BQE'Zapdukebox and not ”managed”.
`removed by any network member with appropriate priviledges.
`
`le data can be
`
`5.1.3 lnternet Streaming
`
`in this topology, the Host Zapdukebox client interacts with an internet based source for music
`or video. This can be with ZapCentral or other sites capable of streaming audio or video
`data;
`it
`is important to note that internet connection exceeds should be at the level of
`broadband to insure “good” quality. Streaming quality, is typically less than that of an asset
`playing directiy from a users local hard drive.
`~
`~
`
`
`
`
`E2
`
`"”
`
`ZapJukebox Host
`
`lnternet
`
`ZapCentral or cher
`
`Figure 4: internet Streaming Topology
`
`The points of most relevance in the internet Streaming topoiogy are the following:
`1:1 ZapJukebox host is capable of adding URL reference to its playlist,
`
`El Media file is not Secure unless it is on ZapCentral.
`
`a Piayback quatity wiil be dependent on lnternet connection speed.
`
`
` mummmvx‘am
`
`new
`WflWr-‘g
`3
`g
`
`a: mwgnriwnyv
`, 3- mg ,
`in“ «,5; ‘
`arm! Sizgsfisfm‘f {flit}; rrzq’fufiiré
`
`/6
`
`Page 18 of 29
`
`Page 18 of 29
`
`

`

`Zag§akebox PRD
`
`:1 Video pie’ybeck quaiity is affected more than audio playback quaiity.
`
`D Streaming data formats include MP3, EPAC, Quicktime and REAL audio and Video.
`
`
`
`mam
`
`wwg
`
`36¢f§€:”532 £ef§§'€;e£m
`
`mm?
`g
`
`I 7
`
`Page 19 of 29
`
`Page 19 of 29
`
`

`

`Zagjfikehoz’PRD
`
`6. ?rociuet Features
`
`5.1
`
`Summary
`
`This section deiaiis'the' high-level system requirements for the specific Zapdukebox features
`listed. The information captured here is the results many weeks of planning and prototyping,
`requirements gathering meetings, and technology investigations. The gathering of these features
`and requirementsis an~on~going process.
`
`l l
`
`Feature List
`
`—
`l
`Streaming Channels
`Single Window interface
`Navigate Streams
`Skin Builder
`
`Audio Playback
`‘ Oracle Database
`
`
`
`Video Piayback
`ZapAccess
`L“intergrated lntemet Browser
`.
`l
`iVAULT Security
`
`
`i- CD Playback
`: 3
`Keyword Search
`CS Encoding
`“1 Multi—Key Sort
`
`
`CD Library Catalog
`1 Nested Playlist
`CDDB
`i Drag & Drop Playiist
`
`Meta Data
`Java Code Base
`
`
`
`
`
`
`Piaylist Email
`
`Ecommerce Stragegy
`
`Sync