throbber
MS 1039
`MS 1039
`
`

`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`UNITED STATES DEPARTMENT OF COMMERCE P
`United States Patent and Trademark Office
`""'
`Address: COMMISSIONER FOR PATENTS
`P.O. Box 1450
`Alexandria. Virginia 22313-1450
`www.usplo.gov
`
`‘
`
`APPLICATION NO.
`
`95/001,295
`
`FILING DATE
`
`01/14/2010
`
`FIRST NAMED INVENTOR
`
`ATTORNEY DOCKET NO.
`
`CONFIRMATION N0.
`
`7509178
`
`5567-2
`
`2137
`
`23117
`7590
`NIXON&VANDERHYE, pc
`901 NORTH GLEBE ROAD, 11TH FLOOR
`.ARLINGTON, VA 22203
`
`03/07/2011
`
`.
`
`FERRIS 1". FRED 0
`PAPER NUMBER
`
`ART UNIT
`
`3992 MAIL DATE
`
`DELIVERY MODE
`
`03/07/2011
`
`PAPER
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`time period for reply, if any, is set in the attached communication.
`
`A
`
`A
`
`x___‘.
`
`PTOL-90A (Rcv.04/07)
`
`MS 1039 - Page 1
`
`MS 1039 - Page 1
`
`

`
`
`
`Commissioner for Patents
`United States Patents and Trademark Office
`P.O.Box I450
`Alexandria, VA 22313-1450
`www.uspto. gov
`
`DO NOT USE IN PALM PRINTER
`
`THIRD PARTY REQUESTER'S CORRESPONDENCE ADDRESS
`
`Tracy W. Druce
`NOVAK DRUCE & QUIGG, LLP, WELLS FARGO PLAZA
`1000 Louisiana St., 53rd FLoor
`
`Date:
`
`MAILED
`MAR 0 7 20"
`
`Houston, TX 77002
`
`_
`
`CENTRAL REEXAMINATION UNIT
`
`Transmittal of Communication to Third Party Requester
`Inter Partes Reexamination
`
`REEXAMINATION CONTROL NO. : 95001295
`
`PATENT NO. : 7509178
`
`TECHNOLOGY CENTER : 3999
`
`ART UNIT : 3992
`
`Enclosed is a copy of the latest communication from the United States Patent and Trademark
`Office in the above identified Reexamination proceeding. 37 CFR 1.903.
`
`Prior to the filing of a Notice of Appeal, each time the patent owner responds to this
`communication, the third party requester of the inter partes reexamination may once file
`written comments within a period of 30 days from the date of service of the patent owner's
`response. This 30-day time period is.statutory (35 U.S.C. 314(b)(2)), and, as such, it cannot
`be extended. See also 37 CFR 1.947.
`
`If an ex parte reexamination has been merged with the inter partes reexamination, no
`responsive submission by any ex parte third party requester is permitted.
`
`All correspondence relating to this inter partes reexamination proceeding should be directed
`to the Central Reexamination Unit at the mail, FAX, or hand-carry addresses given at the end
`of the communication enclosed with this transmittal.
`
`PTOL-2070('Rev.07-04)
`
`MS 1039 - Page 2
`
`MS 1039 - Page 2
`
`

`
`
`
`
`
` Responsive to the communication(s) filed by:
`
`
`
`Patent Owner on 16 July 2010
`8.55
`l.
`Third Party(ies) on 16 August 2010
`Patent owner may once file a submission under 37 CFR 1.951(a) withing’month(s) from the mailing date of this
`Office action. Where a submission is filed, third party requester may file responsive comments under 37 CFR
`1.951 (b) within 30-days (not extendable- 35 U.S.C. § 314(b)(2)) from the date of service of the initial
`submission on the requester. Appeal cannot be taken from this action. Appeal can only be taken from a
`Right of Appeal Notice under 37 CFR 1.953.
`
`
`
`
`
`All correspondence relating to this inter partes reexamination proceeding should be directed to the Central
`Reexamination Unit at the mail, FAX, or hand-carry addresses given at the end of this Office action.
`
`PART I. THE FOLLOWING ATTACHMENT(S) ARE PART OF THIS ACTION:
`
`1. E] Notice of References Cited by Examiner, PTO-892
`2. IXI Information Disclosure Citation, PTO/SB/08
`3.1:;
`
`PART II. SUMMARY OF ACTION:
`
`
`
`1a. IX] Claims 1-29 are subject to reexamination.
`
`
`
`
`
`
`
`
`
`1b. [:1 Claims _ are not subject to reexamination.
`
`2.
`
`I1 Claims _ have been canceled.
`
`3. E] Claims _ are confirmed. [Unamended patent claims]
`
`4.
`
`5.
`
`[:1 Claims _ are patentable.
`
`[Amended or new claims]
`
`[Z Claims 1—_2£9_ are rejected.
`
`are objected to.
`6. CI Claims
`E] are not acceptable.
`E] are acceptable
`7.
`[:1 The drawings filed on __
`8 CI The drawing correction request filed on
`r
`is:
`[:1 approved. E] disapproved.
`9 Cl Acknowledgment is made of the claim for priority under 35 U.S.C. 119 (a)-(d). The certified copy has:
`E] been received.
`E] not been received.
`l:] been filed in Application/Control No
`
`10. D Other
`
`
`
`
`
`
`
`
`
`U.S. Patent and Trademark Office
`PTOL-2065 (O8/06)
`
`Q
`
`Paper No. 20110303
`
`MS 1039 - Page 3
`
`
`
`
`
`ACTION CLOSING PROSECUTION
`
`(37 CFR 1.949)
`
`Control No.
`
`95/001,295
`Examiner
`
`Fred Ferris
`
`
`
`
`
`Patent Under Reexamination
`
`7509178
`Art Unit
`
`3992
`
`-- The MAILING DA TE of this communication appears on the cover sheet with the correspondence address. --
`
`
`
`MS 1039 - Page 3
`
`

`
`Application/Control Number: 95/001,295
`
`Page 2
`
`Art Unit: 3992
`
`DETAILED ACTION
`
`This Office action is responsive to Patent owners response filed 16 July 2010 and Third Party
`
`requester's comments filed 16 August 2010 in the inter partes reexamination of claims 1-29 of
`
`United States Patent Number 7,509,178 issued to Logan et al.
`
`Claims 1-29 stand rejected.
`
`Declarations
`
`Patent owner has submitted declarations by experts Almeroth and Mishkind and a declaration
`
`under 35 USC 1.131 (Call) attempting to swear behind the Foladare reference.
`
`Requester has submitted declarations by experts Wicker and Novacek that opine on issues
`
`relating to the Prior art and the Almeroth declaration.
`
`Almeroth: The Almeroth declaration opines, for example, that the DAD Manual (ENCO)
`
`describes a system designed specifically for use by radio and television broadcasters, that there is
`
`technical incompatibility between the system described in the DAD Manual and personal audio
`
`players, and that a DAD operator in not “listener”. These allegations are rebutted by Wicker and
`
`Novacek. (See: Wicker at 8,-10 and Novacek at 8-10, for example) Almeroth further opines,
`
`among other things, that in the mid 1990’s downloading was dismissed as a technique for
`
`delivering multimedia content, that DAD does not disclose downloading audio files and
`
`sequencing files for persistent storage, and that DAD’s “Download Playlist” function only works
`
`in serial mode. (e.g. at 12-19). These allegations are further rebutted by Wicker and Novacek.
`
`(See: Wicker at 12-19 and Novacek at 4, 12-19) The examiner notes that the Almeroth
`
`declaration generally does not refer to the actual claim language in making the alleged
`
`MS 1039 - Page 4
`
`MS 1039 - Page 4
`
`

`
`Application/Control Number: 95/001,295
`
`.
`
`Page 3
`
`Art Unit: 3992
`
`distinctions over the prior art, and attempts to focus on an intended use distinction of the device.
`
`(See: Wicker at 9-15) In contrast the Wicker and Novacek declarations are factual and on point
`
`- to the language of the claims. (See: Wicker at 7-9, and Novacek 2, for example) Wicker, for
`
`example, gives specific examples that appear to demonstrate incorrect and inaccurate allegations
`
`made in the Almeroth declaration. (Seer Wicker at 8, 10, 16 for example) Also see Novacek at 5,
`
`6, and 18.
`
`Regarding obviousness rejections based on combinations of the remaining prior art the‘ Almeroth
`
`declaration is again off point. Almeroth proposes that the Sony devices are consumer electronics
`
`devices intended for individual listeners while DAD is specially designed for operators of
`
`television and radio broadcasters. Almeroth concludes that the two classes of users are separate
`
`and distinct and there exists no motivation or to combine the different references. (Almeroth at
`
`25)
`
`Here, Dr. Almeroth analyzes the wrong group of people. The relevant persons of ordinary skill in
`
`the art are engineers developing computerized audio playback systems and software, n_ot
`
`consumers or disk jockeys. Because both DAD and the Sony devices are designed for digital
`
`audio playback, engineers developing software for digital audio playback would certainly be
`
`"motivated to consider both. Thus, for example, a developer of DAD-like systems would be
`
`motivated to look at CD players, which were the dominant digital audio playback device in 1995,
`
`with playback controls that were universally recognized. Such a developer would also have been
`
`familiar with minidisk players, which were less, popular but not uncommon. Both types of
`
`systems were used both by consumers and in radio stations. (See: Wicker at 28, 29)
`
`MS 1039 - Page 5
`
`MS 1039 - Page 5
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 4
`
`The examiner finds that, in weighing the evidence, the Wicker and l\lovacek declarations favor
`
`the requester. The preponderance of evidence suggests that certain allegations made in the
`
`Almeroth declaration appear to be either inaccurate or incorrect with regard to the prior art.
`
`Hence, the Almeroth declaration is unpersuasive in distinguishing the claims over the prior art.
`
`Mishkind: The Mishkind declaration attempts to support Patent owner’s allegation that the main
`
`playback machines provided by DAD are similar analog cart machines. (PO response at 10)
`
`Mishkind opines that no cart machines at the time of the invention included a control button that
`
`would either restart a playingaudio cut to the beginning, or jump back to the beginning
`
`preceding a currently playing audio cut. (Mishkind at 8-10) As explained in more detail below,
`
`the examiner has maintained the features of the ‘178 Patent as presently claimed remain obvious
`
`and/or anticipated by the prior art. Accordingly, the examiner finds the cart machine analogy as
`
`proposed in the Mishkind declaration to be unpersuasive in distinguishing the claims over the
`
`prior art.
`Call 11.131 )1 The declaration submitted by the Patent Owner does not comply with 37 CFR
`
`1.131. The declaration fails to address each claim element and explain why the declaration and
`
`accompanying declaration prove the alleged conception and diligence as required by 37 C.F.R.
`
`1.131 (and MPEP § 715.07). With respect to diligence, the declarant makes a statement that he
`
`and his co-inventors were diligently reviewing and preparing the application for submission to
`
`the Patent Office, but fails to provide any evidence supporting that statement, such as
`
`correspondence between him and the other inventors. Further, the declaration is signed by only
`
`one of the three inventors. (MPEP 715.04(1)) requires the signatures of all inventors)
`
`Hence, the Call declaration is facially unpersuasive. (Also see TPR comments page 8)
`
`MS 1039 - Page 6
`
`MS 1039 - Page 6
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Response to Arguments
`
`Page 5
`
`Patent owner initially argues that the prior art references differ from ‘I78 Patent for the
`following reasons:
`
`The DAD Manual fails to disclose downloading separate audio files and a sequencing file.
`
`Patent owner primarily argues that DAD never locally stores downloaded separate audio files
`
`and therefor does not meet the limitation as claimed.
`
`Here the examiner finds -the Novacek declaration (1 1-19) to be persuasive in rebutting Patent
`owner’s arguments and therefore agrees with requester. (See: examiner’s comments on
`
`declarations)
`
`The Sound Blaster is a local system that relies on local audio files and local playlists.
`
`Patent owner argues that'Sound Blaster fails to disclose downloading separate audio files or
`
`sequencing files from a server and fails to disclose responding to control commands by
`
`referencing data from the sequencing file. Patent owner cites the Almeroth declaration at 21-23.
`
`The examiner finds the Wicker declaration (25-26) to be persuasive in rebutting Patent owner’s
`
`arguments and therefore agrees with requester. (See: examiner’s comments on declarations)
`
`Foladare is a central system that relies on centrally stored audio files and centrally stored
`playlists.
`
`Patent owner argues that Foladare’s playlist is not a separate sequencing file and that Foladare is
`
`invalidated as prior art based Patent owner’s declaration filed under 37 CFR 1.131.
`
`Here, the examiner finds requesters comments persuasive in rebutting Patent owner's arguments.
`
`(TPR at 9) Specifically, that Foladare explicitly discloses retrieving a playlist and separately
`
`retrieving the audio content identified in the playlist:
`
`MS 1039 - Page 7
`
`MS 1039 - Page 7
`
`

`
`Application/Control Number: 95/001,295
`Art Unit: 3992
`
`‘
`
`Page 7
`
`Requester’s analysis correctly notes that independent claim 14 does not recite "compressed"
`
`audio program files mentioned in (1), and no that claim recites "intuitive" controls or "locally-
`
`stored" audio files mentioned in (3).
`
`The examiner agrees with requester's reasoning as further explained below in the response to
`
`specific art rejections.
`
`The 'l78 prosecution history emphasizes the three claims features in combination.
`
`Patent owner asserts that the file history makes clear that the sequencing file is used to respond
`
`to commands like, jump, skip, and skip backwards. The examiner does not agree. In the NOA
`
`the examiner simply repeated the language of a single claim limitation and did not specifically
`
`comment on the express meaning or interpretation of claim language during the original
`
`prosecution. Hence it is unclear from the prosecution history how much, if any, weight was given
`
`by the examiner to these arguments at the time of allowance. The prosecution history did not,
`
`for example, clarify the meaning of the term "sequencing file" over and above the cited prior art
`
`in reexamination. Patent owner cites the following passage:
`
`All of the claims set forth an audio program player that downloads and stores a plurality of audio
`program files and a seguencing file that specifies an ordered seguence of a collection of the
`stored audio program files. (Response at 7)
`
`From this passage the meaning of the term “sequencing file” appears to simply be that it
`
`specifies an ordered sequence of a collection of the stored audio program files. In other words, a
`
`"sequencing file" is simply a play list:
`
`The proper interpretation of "sequencing file" in light of specification and prosecution
`history is not simply a play list.
`
`MS 1039 - Page 8
`
`MS 1039 - Page 8
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`9
`
`Page 6
`
`retrieving means, connected to said first selection means, and operable for remotely retrieving
`said selected particular playlist from said first memory means and for retrieving from said second
`memory means the audio data content identified in said playlist and..
`
`(Foladare 8:52-60)
`
`None of the references disclose the claimed listener interface features.
`
`Patent owner argues that none of the references disclose the features of claims 6-8 and 12
`
`relating to using the same control input button. Patent owner cites the Almeroth declaration at
`
`21-72.
`
`Requester has commented that multiple references (DAD, Sound Blaster, Sony Discman, Sony
`
`Minidisc) all teach the claimed user interface elements. (TPR response at 9-13) The examiner
`
`agrees with requester's reasoning as explained below in the response to specific art rejections.
`
`The 'l78 specification emphasizes the combination of three claimed features (1-3).
`
`1. The audio program. player is configured to download from a server computer both separate
`digital compressed audio program files and a separate sequencing file specifying an ordered
`sequence of a collection of the separate audio files;
`
`2. The audio program player stores, on a digital memory unit, both the downloaded separate
`audio files and the downloaded separate sequencing file;
`
`3. The audio program player provides intuitive listener controls permitting listener-inputted
`program selection commands to select locally-stored audio files specified by the sequencing file
`for playback.
`
`Patent owner believes that both independent claims 1 and 14 require these features. Requester
`
`has maintained that they do not. (TPR at 3)
`
`MS 1039 - Page 9
`
`MS 1039 - Page 9
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 8
`
`Patent owner argues that, in light of the specification and file history, the claim term "sequencing
`
`file" is readily understandable to one of skill in the art as a file that is received by the player,
`
`stored, and used by the processor to both control playback of each song in the ordered sequence
`
`and respond to control commands.
`
`Requester has asserted that this definition contradicts Patent owner’s position in litigation.
`
`_ Irrespective of requester’s position, the examiner maintains that the recited “sequencing file" can
`
`be understood to simply imply a play list comparable to that disclosed in the cited prior art for at
`
`least two reasons. First, Patent owner has not argued that the recited “sequencing file” is
`
`anything other than simply a play list. In fact Patent owner appears to be limiting the meaning of
`
`the recited “sequencing file” by arguing that a “sequencing file” is simply the sequence in which
`
`audio programs would play. In their response Patent owner presents the following argument:
`
`“The named inventors, James Logan, Charles Call, and Daniel Goessling, solved this set of
`problems by inventing a personal audio player that could, inter alia, receive and store (i) a
`selection of audio programs and (ii) a se arate file of data "a se uencin file" that determines
`the sequence in which those programs would play. [2:48-51].” (PO Response at page 5, parazl,
`emphasis added)
`
`In other words, Patent owner appears to argue that a “sequencing file” functionally IS just a
`
`playlist. Accordingly, the examiner maintains that Patent owner appears to be engaging in
`
`circular reasoning by arguing, on the one hand, that a "sequencing file" in NOT a playlist, but
`
`then on the other hand arguing that a sequencing file is simply a “separate file of data ("a
`
`sequencing file") that determines the sequence in which those programs would play”. (e. g. a play
`
`list) Still further, the fact that a sequence file could be used for “controlling playback”, as argued
`
`by Patent owner, can be understood to simply mean controlling the order in which songs are
`
`played.'(Again, as in a play list)
`
`MS 1039 - Page 10
`
`MS 1039 - Page 10
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 9
`
`Second, the examiner notes that the actual '178 specification, while more specific than argued by
`
`Patent owner, does not appear to expressly define or limit the meaning of the claimed
`
`“sequencing file”. For example at 6:22 the ’178 specification recites:
`
`
`As hereinafter described in connection with FIG. 5 each voice or text
`
`program segment preferably includes a sequencing file which contains the
`identification of highlighted passages and hypertext anchors within the program
`content. This sequencing file may further contain references to image files
`and the start and ending offset locations in the audio presentation when each
`image display should begin and end. In this way, the image presentation may be
`synchronized with the audio programming to provide coherent multimedia
`programming. (‘I78 6:22 emphasis added)
`
`Here the specification mentions that the sequencing file includes identification of “highlighted
`
`passages” and “hypertext anchors” and r_n_ay contain references to “image files”. These features
`
`are not claimed. The examiner also notes that the passages above appear to describe features in
`
`the context of synchronizing images with audio content. None of which are claimed.
`
`Further, from the passages beginning at 12:9, it is unclear what elements would be expressly
`
`required by a sequencing file. These passages recite:
`
`As described in more detail later in connection with FIGS. 4 and 5, the
`
`sequence of program segments to be presented to the user is formed into a
`schedule file (seen at 307 in FIG. 4) consisting of a seguence of program
`segment identification numbers which are used to compile a seguencing file,
`
`called the selections file illustrated at 351 in FIG. 5 which contains more
`
`detailed information about the seguence of events which occur during playback.
`The player obtains information from the selections file which identifies the
`individual program segments to be fetched from mass storage and played for the
`user, as well as the segment identification information which is recorded in a
`usage logging file in the manner illustrated in FIG. 3. (‘I78 at 12:9 emphasis added)
`
`Thus, from the specification it is unclear what is specifically “compiled” into the “sequencing
`
`file” from the “selections file”, in determining the sequence of events occurring during playback.
`
`MS 1039 - Page 11
`
`MS 1039 - Page 11
`
`

`
`Application/Control Number: 95/001,295
`
`-
`
`Page 10
`
`Art Unit: 3992
`
`In any event, these features are not specifically claimed and can not be read directly into the
`
`claims. Accordingly, it is the examiners position that, taken in light of both the specification and
`
`Patent owner’s own arguments, the broadest reasonable interpretation of the claimed
`
`"sequencing file" reads on the play lists as disclosed in the prior art.
`
`(R1) Rejections based on the DAD Manual (claims 1-11. 1_3-15 and 28-29)
`
`' Regarding printed publication and enabling disclosure
`
`@: Patent Owner initially argues that the DAD Manual is not a printed publication and is not an
`
`enabling disclosure.
`
`jlfl: Requester argues the declaration of Eugene Novacek refutes Patent owner’s position and
`
`that the DAD system described in the DAD Manual was available for purchase at the time - a
`
`person of ordinary skill in the art could have reduced the DAD Manual disclosure to practice by
`
`simply purchasing a DAD system from ENCO. (TPR at 14-15)
`
`Examiner: The examiner agrees with Requester’s reasoning.
`
`Regarding the “listeners" and "audio output unit"
`
`E: Patent Owner argues that users of the DAD system described in the DAD Manual are not
`
`"listeners" and cites the Almeroth and Mishkind declarations. [Patent Owner's Response, at 8-9]
`
`Patent owner also argues that DAD did not include an audio output unit that "reproduced audio
`
`program files in audible form perceptible to a listener” because it was drawn to radio
`
`broadcasting. [Patent Owner's Response, at 15] [Almeroth at 8] [Mishkind at 10]
`
`MS 1039 - Page 12
`
`MS 1039 - Page 12
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 11
`
`I13: Requester argues that the DAD Manual clearly indicates that operators of DAD
`
`workstations were expected to listen to the audio it was reproducing. It included a headphone
`
`jack, and the DAD Manual refers to speakers. [DAD Manual, at 16-4; Wicker Decl., 14] It was
`
`typical for DAD operator to listen to the audio he/she being played by the device. [Novacek
`
`Decl., 8, 10; Wicker Decl., 6, 8, 14] Requester asserts that Patent Owner's argument that DAD
`
`was used only for broadcasting is wrong. The DAD Manual clearly indicates that it was not used
`
`exclusively for broadcasting [Novacek Decl., 8, 10] It was also used, among other things, for
`
`studio production. [Novacek Decl., 10] During studio production, the output would not be
`
`broadcast, and the user would often be the only listener. [Novacek Decl., 10] In any event, "a
`
`reference may be relied upon for all that it would have reasonably suggested to one having
`
`ordinary skill in the art, including non-preferred embodiments." (MPEP 2123)
`
`Further, Requester notes that DAD was not at all limited to broadcasts, and users, purchasers,
`
`and operators of DAD often would use DAD to themselves play and listen to audio files.
`
`[Novacek Decl., 8, 10]
`
`Examiner: The examiner agrees with requester. A “listener”, in the context of both the DAD
`
`Manual, and the 'l78 Patent, can be interpreted to simply be the operator of the device. The
`
`"audio output unit" cited by the Examiner and the Requester is the stereo headphone output. This
`
`output was used by the DAD operator to listen to the audio program files and meets the language
`
`of the claim requiring "reproduced audio program files in audible form perceptible to a listener”.
`
`The fact that the output of DAD could a@ be broadcast over the air, in addition to being listened
`
`to by the operator, is simply irrelevant relative to the language of the claim.
`
`MS 1039 - Page 13
`
`MS 1039 - Page 13
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 12
`
`Regarding claim 1 recited Audio Program Player
`
`EQ: Patent Owner argues that DAD workstations in a networked system do not have a
`
`local hard drive for persistently storing audio files. Patent Owner also argues that it would not
`
`have been obvious to modify one of the DAD playback interfaces from one form of standalone
`
`player (a cart machine) to another (a CD player). [Mishkind at 1]
`
`E: Requester asserts that Patent Owner's Response makes a number of inaccurate allegations
`
`to support the argument that the DAD Manual did not disclose an "audio program player" as
`
`recited in claim 1 of the ' 178 Patent. [Patent Owner's Response, at 10-14] Requester maintains
`
`that the DAD manual specifically discloses downloading files from a file server over a network
`
`to a local hard drive, where those files would be stored for minutes or hours until they are played.
`
`[Wicker Decl., 19-23; Novacek Decl., 1 1, 12] The DAD Manual calls this the "Playback
`
`Lookahead" option:
`
`This feature copies audio files from the network to the local hard drive in the
`background, then plays the cut from the local hard drive at the appropriate
`time. (DAD Manual, pg. 12-9) (emphasis added)
`
`Requester further asserts that Patent Owner's argument that the DAD Manual does not disclose a
`
`networked system that could locally store files downloaded from over a network is simply
`
`wrong. Patent Owner cites to a portion of the DAD Manual that discloses a configuration in
`
`which workstations in a network do not use Playback Lookahead and do not store audio files
`
`locally. [Patent Owner's Response, at 10] However, the DAD Manual discloses multiple network
`
`configurations, including embodiments where audio files on networked workstations are stored
`
`locally. For example, the DAD Manual compares multiple network configurations including a
`
`"File Server Network" embodiment and an "Audio Server Network" embodiment. [DAD
`
`MS 1039 - Page 14
`
`MS 1039 - Page 14
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 13
`
`Manual, at 12-4 to 12-5] The File Server Network embodiment expressly states that individual
`
`work stations store local files so that they may "operate independentlyiof any other workstations
`
`and the File Server hard drive", while the Audio Server Network embodiment forces all audio
`
`cuts to be played from the audio server and does not explicitly disclose local storage in the
`
`workstations. [DAD Manual, at 12-4 to 12-5; see also DAD Manual 13-8 ("For systems
`
`configured as a File Server Network (see Section 12.3-A), it is possible to power down the File
`
`Server while network workstations continue to operate independently. All individual
`
`workstations must be equipped with local (internal) hard drives.")].
`
`Asdescribed in the Reexamination Request, both DAD and the Sound Blaster references
`
`explicitly borrowed user interfaces from standalone audio players, demonstrating that this was a
`
`common practice in the computerized audio player art.
`
`Regarding modification of the DAD playback interfaces from one form of standalone player (a
`
`cart machine) to another (a CD player), Requester asserts that both DAD and the Sound Blaster
`
`references explicitly borrowed user interfaces from standalone audio players, demonstrating that
`
`this was a common practice in the computerized audio player art.
`
`Examiner: The examiner concurs with Requester that DAD Discloses the Recited Audio
`
`Program Player for at least the reasons set forth above. Specifically, Patent owner’s arguments
`
`that the DAD also included a cart machine simulator are off-point. DAD discloses the recited
`
`"audio program player" because it meets the requirement for each of the claimed elements
`
`including a communications port, a digital memory, and audio output unit, one or more manual
`
`controls, and a processor delivering a succession of audio program files in an ordered sequence
`
`as specified by a sequencing file... Each of these elements is set forth in the rejections.
`
`MS 1039 - Page 15
`
`MS 1039 - Page 15
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 14
`
`Regarding claim 1: (i) a communication port.., for downloading a plurality of separate
`digital compressed audio program files and a separate sequencing file" and (ii) a digital
`memory... for persistently storing said separate digital compressed audio program files and
`said separate sequencing file.
`
`EQ: Patent Owner argues that because the externally prepared playlist is translated into the DAD
`
`format, the "source data files" are not themselves the playlist, and thus, the "import" feature does
`
`not result in the downloading of a playlist. [Patent Owner's Response, at 1 1] Patent Owner also
`
`argues that the imported playlists must be manually modified to become a DAD playlist.
`
`[Almeroth at 11, 15, 16-19]
`
`1:13: Requester asserts that DAD explicitly discloses preparing a playlist on a separate computer
`
`and then transferring it over a network and importing it into a DAD playlist. [Reexamination
`
`Request, at 32-33] Further, as described in the DAD Manual the "Import" function would
`
`automatically create a DAD playlist from a playlist created on a separate computer system, like
`
`Selector. [Novacek Decl., 13-17] While a user could modify that playlist, it was not required -
`
`the automatically created playlist resulting from the "Import" feature could be immediately used
`
`for playback by the DAD workstation. [Novacek Decl., 13-17)]
`
`Patent Owner also argues that "[t]he ‘import’ capability thus imports locally stored files."
`
`[Patent Owner's Response, at 1 1] This argument is contradicted by the express disclosure of the
`
`DAD Manual. The DAD Manual explicitly discloses that "[t]he source data file from the external
`
`system must be transferred into the DAD486x via floppy disk or network connection." [DAD
`
`Manual, at 7-19 (emphasis added); Office Action, at 5]
`
`Patent Owner's Response goes on to reiterate its inaccurate argument that individual DAD
`
`workstations on a network do not store files locally. [Patent Owner's Response, at 12] This
`
`argument is simply wrong, for the reasons discussed above. [Wicker Decl., 18-20, 22; Novacek
`
`MS 1039 - Page 16
`
`MS 1039 - Page 16
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 15
`
`Decl., 1 1, 12, 21] Namely, the File Server Network configuration does have local storage of
`
`files. [DAD Manual, at 12-4 to 12-5]
`
`Patent Owner also argues that a serial connection from a DAD workstation may only be attached
`to external automation equipment and that this prohibited a DAD workstation from being
`
`connected over a network to a server. [Patent Owner's Response, at 12] This is not true.
`
`[Novacek Decl., 4, 17, 18] Further, the serial port was only one way in which the DAD system
`
`could import a playlist; the more common mechanism for the DAD workstation to download a
`
`playlist was through use of the "import" tool over a local area network. [Novacek Decl., 18]
`
`Finally, Patent Owner again argues that the DAD Manual only discloses streaming over a
`
`network rather than downloading files for "persistent storage" over a network. [Patent Owner's
`
`Response, at 13-14] As discussed above, the streaming configuration relied on by Patent Owner
`
`is only one way that the DAD system could be used. The Patent Owner's argument ignores the
`
`explicit disclosure in the DAD Manual that files are downloaded from a file server and stored
`
`locally in Playback Lookahead mode and the File Server Network configuration. [DAD Manual,
`
`at 12-4; Wicker Decl., 18-20, 22; Novacek Decl., 11, 12,21].
`
`In the File Server Network configuration, individual workstations could continue playing audio
`
`files even if the File Server was turned off, which would be impossible if the only way to play
`
`files on individual workstations was by streaming as Patent Owner contends. [DAD Manual, at
`
`13-8 ("For systems configured as a File Server Network (see Section 12.3-A), it is possible to
`
`power down the File Server while network workstations continue to operate independently. All
`
`individual workstations must be equipped with local (internal) hard drives."]
`
`MS 1039 - Page 17
`
`MS 1039 - Page 17
`
`

`
`Application/Control Number: 95/001,295
`
`Art Unit: 3992
`
`Page 16
`
`Examiner: The examiner concurs with Requester that DAD discloses (i) a communication port..,
`
`for downloading a plurality of separate digital compressed audio program files and a separate
`
`sequencing file" and (ii) a digital memory... for persistently storing said separate digital
`
`compressed audio program files and said separate sequencing file, as required by the claims for
`
`at least the reasons explained above.
`
`Regarding claim 1 “one or more manual controls”
`
`@: Patent owner argues that the DAD Manual does not disclose "one or more manual controls“.
`
`[Pate

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