throbber

`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`UNITED STATES DEPARTMENT OF COMMERCE
`United States Patent and Trademark Office
`Address: COMMISSIONER FOR PATENTS
`P.O. Box 1450
`Alexandria, Virginia 22313-1450
`www.uspto.gov
`
`‘
`
`APPLICATIONNO.
`
`FILING DATE
`
`FIRST NAMED INVENTOR
`
`ATTORNEY DOCKET NO.
`
`CONFIRMATION NO.
`
`95/000,479
`
`05/28/2009
`
`7161506
`
`080272-0012
`
`2572
`
`08/27/2010
`7590
`26111
`STERNE, KESSLER, GOLDSTEIN & FOX P.L.L.C.
`1100 NEW YORK AVENUE, N.W.
`WASHINGTON, DC 20005
`
`‘
`
`LEUNG,CHRISTINA ¥
`
`3992
`
`MAIL DATE
`
`08/27/2010
`
`DELIVERY MODE
`
`PAPER
`
`Please find below and/or attached an Office communication concerning this application or proceeding.
`
`The time period forreply, if any, is set in the attached communication.
`
`1
`
`PTOL-90A (Rev. 04/07)
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 001
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 001
`
`

`

`\ UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`Commissioner for Patents
`United States Patent and Trademark Office
`P.O. Box 1450
`Alexandria, ¥A 22313-1490
`anuuspto.gov
`
`DO NOT USEIN PALM PRINTER
`
`(THIRD PARTY REQUESTER'S CORRESPONDENCE ADDRESS)
`
`MCDERMOTT WILL & EMERY LLP
`600 13° STREET NW
`WASHINGTON, DC 20005-3096
`
`Transmittal of Communication to Third Party Requester
`Inter Partes Reexamination
`;
`
`REEXAMINATION CONTROL NUMBER95/000,479.
`
`PATENT NUMBER7,161,506.
`
`TECHNOLOGYCENTER 3900.
`
`ART UNIT 3992.
`
`Enclosedis a copy of the latest communication from the United States Patent and
`Trademark Office in the above-identified reexamination proceeding. 37 CFR 1.903.
`
`Priorto thefiling of a Notice of Appeal, each time the patent owner respondstothis
`communication, the third party requester ofthe inter partes reexamination may oncefile
`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 requesteris permitted.
`
`All correspondencerelating to this inter partes reexamination proceeding should be
`directed to the Central Reexamination Unit at the mail, FAX, or.hand-carry addresses
`givenat the end of the communication enclosed with this transmittal.
`
`PTOL-2070 (Rev.07-04)
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 002
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 002
`
`

`

`
`
`ACTION CLOSING PROSECUTION|951000,479 7161506
`
`Control No.
`
`
`
`Patent Under Reexamination
`
`-- The MAILING DATEof this communication appears on the cover sheet with the correspondenceaddress.--
`
`Christina Y. Leung
`
`3992
`
`Responsive to the communication(s)filed by:
`Patent Owner on 15 March 2010
`
`Third Party(ies) on
`
`Patent owner may oncefile a submission under 37 CFR 1.951(a) within 1 month(s) from the mailing date of this
`Office action. Where a submission is filed, third party requester mayfile 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 correspondencerelating to this inter partes reexamination proceeding should be directed to the Central
`Reexamination Unit at the mail, FAX, or hand-carry addressesgiven at the end of this Office action.
`
`PART |. THE FOLLOWING ATTACHMENT(S) ARE PART OF THIS ACTION:
`
`1. LJ Notice of References Cited by Examiner, PTO-892
`2. & Information Disclosure Citation, PTO/SB/08
`3.0
`
`PART Il. SUMMARY OF ACTION:
`
`1a. KX] Claims See Continuation Sheet are subject to reexamination.
`1b.&]Claims See Continuation Sheet are not subject to reexamination.
`2. [)Claims___ have been canceled.
`
`X] Claims 6,7,16,41 and 42 are confirmed. [Unamended patent claims]
`[]Claims ___ are patentable.
`[Amended or newclaims]
`
`&] Claims 1-5,8,9,11,17,20-23,27,39,43,69-73,79,81,82,84-90,96 and 98 are rejected.
`
`are objectedto.
`
`[-] are not acceptable.
`[_] are acceptable
`[_] The drawingsfiled on
`(_] The drawing correction requestfiled on
`is:
`[] approved.
`(_] disapproved.
`[] Acknowledgment is madeof the claim for priority under 35 U.S.C. 119 (a)-(d). The certified copy has:
`[] been received.
`_[_] not been received.
`] beenfiled in Application/Control No
`10. [[] Other
`
`CONAAAw C] Claims
`
`U.S. Patent and Trademark Office
`PTOL-2065 (08/06)
`
`Paper No. 20100823
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 003
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 003
`
`

`

`:
`
`1 \
`Control No. 95/000,479
`Continuation Sheet (PTOL-2065)
`Continuation of SUMMARY OF ACTION: 1a. Claims subject to reexamination are 1-9,11,16,17,20-23,27,39,41-43,69-73,79,81,82,84-90,96
`and 98.
`Continuation of SUMMARY OF ACTION: 1b. Claims not subject to reexamination are 10,12-15,18,19,24-26,28-38 ,40,44-68,74-
`78,80,83,91-95,97 and 99.
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 004
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 004
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 2
`
`DETAILED ACTION
`
`Reexamination
`
`1.
`
`Claims1-9, 11, 16, 17, 20-23, 27, 39, 41-43, 69-73, 79, 81, 82, 84-90, 96, and 98 of
`
`Fallon (US 7,161,506 B2) are being reexamined. Claims 10, 12-15, 18, 19, 24-26, 28-38, 40,
`
`44-68, 74-78, 80, 83, 91-95, 97, and 99 are not subject to reexamination.
`
`References and Documents Cited in this Action
`
`Fallon (US 7,161,506 B2)
`
`French (US 5,794,220 A)
`
`Sebastian (US 6,253,264 B1)
`
`Franaszek (US 5,870,036 A)
`
`O’Brien (US 4,988,998 A)
`
`Craft (US 5,627,534 A)
`
`Reynar (US 5,951,623 A)
`
`CCITTV.42 bis (“Data Compression Procedures for Data Circuit Terminating
`
`Equipment [DCE] Using Error Correction Procedures,” CCITT Recommendation V.42 bis,
`
`1990)
`
`A)
`
`MacLean (US 5,167,034 A)
`
`Kawashima (W095/29437 A1; English-language equivalent document, US 5,805,932
`
`Aakre (US 4,956,808 A)
`
`LBX (Converseet al., “Low Bandwidth X Extension, Protocol Version 1.0, X
`
`Consortium Standard,” 21 December 1996)
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 005
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 005
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`,
`
`Page 3
`
`LBX X (“LBX X Consortium Algorithms”)
`
`Images(“Basics of Images,”
`
`http://www.geom.uiuc.edu/events/courses/1996/emwh/Stills/basics.html, 1996)
`
`Held (“Data Compression Techniques and Applications,” 1991)
`
`ITU H.263 (“Video Coding for Low Bit Rate Communication,” ITU Recommendation
`
`H.263, March 1996)
`
`ITU T.81 (“Digital Compression and Coding of Continuous ToneStill Images,” ITU
`
`Recommendation T.81, September 1992
`
`Howard (Howard, Paul and Jeffrey Vitter, “Parallel Lossless Image Compression Using
`
`Huffman and Arithmetic Coding,” Data Compression Conference, 27 March 1992)
`
`Simpson (Simpsonetal., “A Multiple Processor Approach to Data Compression,”
`
`ACM,1998)
`
`Dye (US 7,190,284 B1)
`
`Lafe (US 6,449,658 B1)
`
`Admissions (admittedprior art of the Fallon patent)
`
`3PR Request (Third-Party Requester’s request for reexamination filed on 28 May 2009)
`
`Storer Declaration (declaration of James Storer filed 28 May 2009 by 3PR)
`
`PO Response(Patent Owner’s response filed 15 March 2010)
`
`Modestino Declaration (declaration of James Modestinofiled 15 March 2010 by PO)
`
`Information Disclosure Statement
`
`2.
`
`The Information Disclosure Statementfiled 15 March 2010 by PO has been considered.
`
`Items such as declarations and court documents do not constitute patents or printed publications
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 006
`
`
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 006
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 4
`
`and are not prior art. These documentsare therefore not appropriate for an Information
`
`Disclosure Statement, and the citations of these documents therein have beenlined through.
`
`They will not be cited on the face of the patent.
`
`Priority
`
`3.
`
`Fallon, US 7,161,506 B2, is a continuation of application number 10/016,355 (US
`
`6,624,761 B2 filed on 29 October 2001, whichis a continuation-in-part of application number
`
`09/705,446 (US 6,309,424 B1) filed on 03 November 2000, whichis a continuation of
`
`application 09/210,491 (US 6,195,024 B1) filed on 11 December 1998.
`
`4,
`
`Claims 1-9, 11, 16, 17, 20-23, 27, 39, 41-43, 69-73, 79, 81, 82, 84-90, 96, and 98 are
`
`supported for purposes of 35 U.S.C. 112 by Figures 13-18 and the additional disclosure thatfirst
`
`appeared in application number 10/016,355. Therefore, claims 1-9, 11, 16, 17, 20-23, 27, 39, 41-
`
`43, 69-73, 79, 81, 82, 84-90, 96, and 98are entitled to a priority date of 29 October 2001.
`
`Claim Rejections - 35 USC § 102
`
`5.
`
`The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the
`
`basis for the rejections under this section madein this Office action:
`
`A person shall be entitled to a patent unless —
`
`(b) the invention was patentedor described in a printed publication in this or a foreign countryor in public use or on
`sale in this country, more than oneyear prior to the date of application for patent in the United States.
`
`(e) the invention was described in (1) an application for patent, published under section 122(b), by anotherfiled
`in the United States before the invention by the applicant for patent or (2) a patent granted on an application for
`patent by anotherfiled in the United States before the invention by the applicant for patent, except that an
`international application filed under the treaty defined in section 351(a) shall have the effects for purposes ofthis
`subsection ofan application filed in the United States only if the international application designated the United
`States and was published under Article 21(2) of such treaty in the English language.
`
`6.
`
`Claims 1-5, 8, 9, 11, 17, 21-23, 43, 69, 72, 73, 79, and 81 are rejected under 35
`
`U.S.C. 102(e) as being anticipated by Sebastian.
`
`Theserejections are adopted essentially as proposed by 3PR in 3PR Request.
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 007
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 007
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 5
`
`Regarding claim 1, Sebastian discloses a method for compressing data, comprising the
`
`stepsof:
`
`analyzing a data block of an input data stream to identify one or more data types of the
`
`data block, the input data stream comprisingaplurality of disparate data types(i.e., using
`
`elementsincludingfilters 10a-z andfilter selection system 22 in encoder 3; column 1, lines 50-
`
`52; column 2, lines 1-42; column3, lines 66-67; column4,lines 1-25);
`
`performing content dependent data compression,if a data type of the data blockis
`
`identified (column2, lines 33-42; column5, lines 14-18; column 6,lines 22-40);
`
`performing data compression with a single data compression encoder, ifa data type ofthe
`
`data block is not identified (i.e., Sebastian discloses a generic compression system; column 1,
`
`lines 55-60; column 4, lines 9-20).
`
`Regarding claims 2-4, Sebastian discloses appendinga data compression type descriptor
`
`to a compressed data block and outputting the compressed data block with the appended data
`
`compression type descriptor (column 3, lines 31-36; column 5, lines 14-18).
`
`Regarding claim 5, Sebastian discloses that the performing content dependent data
`
`compression further comprises enabling at least one encoder associatedto the data type to
`
`compress the data block (column 1, lines 55-57; column2, lines 33-42).
`
`Regarding claim 8, Sebastian discloses that the performing content dependent data
`
`compression further comprises compressing the data block with cascaded encoders that are
`
`associated to the data type (column 17, lines 15-28; column 19,lines 31-48).
`
`Regarding claim 9, Sebastian discloses that the content dependent compressionislossless
`
`(column2, lines 43-47; column 3, lines 37-41).
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 008
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 008
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 6
`
`Regarding claim 11, Sebastian discloses that the data compressionis lossless (column 2,
`
`lines 43-47; column 3, lines 37-41; column4, lines 9-20).
`
`Regarding claim 17, Sebastian discloses that the input stream is an uncompressed input
`
`stream (column1, lines 19-23).
`
`Regarding claim 21, Sebastian discloses buffering the input data stream (i.e., using
`
`FILE_BUFFER;column7, lines 25-27).
`
`Regarding claim 22, Sebastian discloses buffering a compressed data block(i-e., using
`
`ARRAY;column 7, lines 25-27).
`
`Regarding claim 23, Sebastian discloses outputting a compressed data block; and
`
`providing a compressiontype descriptor with the compressed data block representative of
`
`the type of compression usedto provide the compresseddata block (column3, lines 31-36;
`
`column5, lines 14-18).
`
`Regarding claim 43, Sebastian discloses that the performing content dependentdata
`
`compression further comprises compressingthe data block using at least two encoders (Figures 4
`
`and 5; column 18, lines 41-67; column 19, lines 1-12).
`Regarding claim 69, Sebastian discloses a method comprising:
`receiving a data block in an uncompressed form, the data block being included in a data
`
`stream (column 1, lines 19-23);
`
`analyzing the data block to determine a type ofthe data block (i.¢., using elements
`includingfilters 10a-z andfilter selection system 22 in encoder 3; column J, lines 50-52; column
`
`2, lines 1-42; column3, lines 66-67; column 4,lines 1-25); and
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 009
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 009
`
`

`

`Application/Control Number: 95/000,479 -
`Art Unit: 3992
`
`Page 7
`
`compressing the data block to provide a compressed data block, wherein if one or more
`encoders are associated to the type, compressing the data block with at least one ofthe one or
`
`|
`
`more encoders (column 2,lines 33-42; column 5, lines 14-18; column 6, lines 22-40) else
`
`compressing the data block with a data compression encoder(i.e., Sebastian discloses a generic
`
`compression system; column1, lines 55-60; column4, lines 9-20).
`
`Regarding claims 72 and 73, Sebastian discloses outputting the compressed data block
`
`with a descriptor representative of the compression technique used to compressthe data block
`
`(column3, lines 31-36; column5, lines 14-18).
`
`Regarding claims 79 and 81, Sebastian discloses that the data compression encoderis
`
`lossless and the at least one of the one or more encodersis lossless (column 2, lines 43-47;
`
`column 3, lines 37-41; column 4, lines 9-20).
`
`7.
`
`Claims 69, 70, 72, 73, 79, 81, 82, 84, and 85are rejected under 35 U.S.C. 102(b)as
`
`being anticipated by Franaszek.
`
`Theserejections are adopted essentially as proposed by 3PR in 3PR Request.
`
`Regarding claim 69, Franaszek discloses a method comprising:
`
`receiving a data block in an uncompressed form,the data block being-includedin a data
`
`stream (Figure 2; column4, lines 25-35);
`
`analyzing the data block to determinea type of the data block (column5, lines 49-54);
`
`and
`
`compressing the data block to provide a compressed data block, wherein if one or more
`
`encoders are associated to the type, compressing the data block with at least one of the one or
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 010
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 010
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 8
`
`more encoders, else compressing the data block with a data compression encoder (column 5,
`
`lines 49-54).
`
`Regarding claim 70, Franaszek discloses outputting the data block in the uncompressed
`
`form if the compressed data blockis indicative of data expansion (column4,lines 55-59; column
`5, lines 19-38: column6, lines 41-50).
`
`Regarding elaims 72 and 73, Franaszek discloses outputting the compressed data block
`
`with a descriptor representative of the compression technique used to compressthe data block
`
`(column4, lines 55-59).
`
`Regarding claims 79 and81, Franaszek discloses that the data compression encoderis
`
`lossless and the at least one of the one or more encodersis lossless (i.e., Franaszek discloses
`
`lossless LZ1 compression; column 7, lines 56-65).
`
`Regarding claim 82, Franaszek discloses that the at least one of the one or more encoders
`
`comprises a plurality of encoders provided in parallel (column 6, lines 29-32).
`
`Regarding claims 84 and 85, Franaszek discloses performing an analysis using the size
`
`of the compressed data block and a compression threshold to determine whether to outputthe
`
`data block in the uncompressed form orto output the compressed data block (column 5,lines 26-
`
`29).
`
`Claim Rejections - 35 USC § 103
`
`8.
`
`The followingis a quotation of 35 U.S.C. 103(a) which formsthe basisforall
`
`obviousnessrejections set forth in this Office action:
`
`(a) A patent maynotbe obtained thoughthe inventionis not identically disclosed or described as set forth in
`section 102 ofthistitle, if the differences between the subject matter sought to be patented andthepriorart are
`such that the subject matter as a whole would have been obviousat the time the invention was made to a person
`having ordinary skill in the art to which said subject matter pertains. Patentability shall not be negatived by the
`mannerin which the invention was made.
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 011
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 011
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 9
`
`9.
`
`Claim 20is rejected under 35 U.S.C. 103(a) as being unpatentable over Sebastian in
`
`view of Franazek or Reynar.
`
`This rejection is adopted essentially as proposed by 3PR in 3PR Request.
`
`Regarding claim 20, Sebastian discloses a method as discussed above with regard to
`
`claim 1 but does not specifically disclose counting the size of the data block.
`
`However, Franazek teaches a system that is related to the one described by Sebastian,
`
`including data compression, and teaches countingthe size ofthe data block (column 5, lines 19-
`
`38). Reynar also teaches a system thatis related to the one described by Sebastian, including data
`
`compression, and teaches counting the size of the data block(i.e., the length of the document or
`
`documentportion; column 14, lines 66-67; column 15, lines 1-13).
`
`Regarding claim 20, it would have been obviousto a person of ordinary skill in the art to
`
`count the size of the data block as taught by Franazek and Reynarin the method disclosed by
`
`Sebastian in order to advantageously comparethe sizes of the block before and after compression
`
`and determinethe efficiency of the compression.
`10.
`Claims 27 and 39 are rejected under35 U.S.C. 103(a) as being unpatentable over
`
`Sebastian in view of CCITT V.42 bis or Reynar.
`
`Theserejections are adopted essentially as proposed by 3PR in 3PR Request.
`
`Regarding claim 27, Sebastian discloses a method as discussed above with regard to
`
`claim 1 but doesnot specifically disclose that the data compression further comprises providing a
`
`compressed data block from the single compression encoder so long as the compression ratio of
`
`the compressed data block exceeds a compression threshold. Similarly, regarding claim 39,
`
`Sebastian discloses a method as discussed above with regard to claim 1 but does notspecifically
`
`,
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 012
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 012
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 10
`
`disclose providing a compression threshold and outputting a compressed data block that exceeds
`
`the compression threshold.
`
`However, CCITT V.42 bis teaches a system that is related to the one described by
`
`Sebastian, including data compression. CCITT V.42 bis teaches providing a compression
`
`threshold and outputting a compressed data block that exceeds the compression threshold at least
`
`in the sense that CCITT V.42 bis teaches determiningthe effectiveness of the compression and
`
`only outputting compressed data if compression would beeffective (page 11, sections 7.8-7.8.2).
`
`Reynar also teaches a system thatis related to the one described by Sebastian, including data
`
`compression, and teaches providing a compressed data block from a compression encoder so
`
`long as the compression ratio of the compressed data block exceeds a compression threshold
`
`(column 18, lines 9-21; column 23, lines 10-20).
`
`Regarding claims 27 and 39, it would have been obviousto a person ofordinary skill in
`the art to provide a compression threshold and output a compressed data block that exceeds the
`
`threshold as taught by CCITT V.42 bis or Reynar in the method disclosed by Sebastian in order
`
`to ensure that resources are used for compression only when compression would be effective.
`‘11.
`Claim 82 is rejected under 35 U.S.C. 103(a) as being unpatentable over Sebastian in
`
`view of MacLean.
`
`This rejection is adopted essentially as proposed by 3PR in 3PR Request.
`
`Regarding claim 82, Sebastian discloses a method as discussed above with regard to
`
`claim 1, including one or more encoders, but does not specifically disclose that the at least one of
`
`the one or more encoders comprisesa plurality of encoders provided in parallel. However,
`
`MacLeanteaches a system that is related to the one described by Sebastian, including data
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 013
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 013
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 11
`
`compression, and further teaches a plurality of encoders provided in parallel (column5, lines 24-
`
`27). Regarding claim 82, it would have been obviousto a person of ordinary skill in the art to
`
`include a plurality of encoders provided in parallel as taught by MacLean in the method
`
`disclosed by Sebastian in order to maximize the processing efficiency of the compression
`
`system.
`
`12.
`
`Claims 70, 71, 84-90, 96 and 98 are rejected under 35 U.S.C. 103(a) as being
`
`unpatentable over Sebastian in view of Kawashima.
`
`Since Kawashima WO95/29437 Al is in Japanese, all references below to its disclosure
`
`are made to its English-language equivalent document, US 5,805,932 A.
`These rejections are adopted essentially as proposed by 3PR in 3PR Request.
`
`Regarding claims 70 and 71, Sebastian discloses a method as discussed above with
`
`regard to claim 69 but does not specifically disclose outputting the data block in the
`
`uncompressed form with a descriptor representative of no compression if the compressed data
`
`block is indicative of data expansion.
`
`However, Kawashimateaches a system thatis related to the one described by Sebastian,
`
`including data compression, and further teaches outputting the data block in the uncompressed
`form (i.e., as “pre-compression data”) with a descriptor representative of no compression if the
`
`compressed data block is indicative of data expansion (column5, lines 61-67; column 6,lines 1-
`
`2; column 30, lines 14-18)
`
`Regarding claims 70 and 71, it would have been obviousto a person ofordinary skill in
`
`the art to outputting the data block in the uncompressed form with a descriptor representative of
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 014
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 014
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 12
`
`no compression as taught by Kawashimain the method disclosed by Sebastian in order to ensure
`
`that resources are used for compression only when compression would beeffective.
`
`Regarding claims 84 and 85, Sebastian discloses a method as discussed above with
`
`regard to claim 69 but doesnot specifically disclose performing an analysis using the size of the
`
`compressed data block and a compression threshold to determine whether to output the data
`
`block in the uncompressed form or to output the compressed data block.
`
`However, Kawashimateaches performingan analysis using the size of the compressed
`
`data block and a compression threshold to determine whether to output the data block in the
`
`uncompressed form or to output the compressed data block (column29,lines 43-67; column 30,
`
`lines 1-23)
`
`Regarding claims 84 and 85, it would have been obviousto a person of ordinary skill in
`
`the art to determine whether to output the data block in an uncompressed form or to output the
`
`compressed data block as taught by as taught by Kawashimain the method disclosed by
`
`Sebastian in order to ensure that resources are used for compression only when compression
`
`would be effective.
`
`Regarding claim 86, Sebastian discloses a method comprising:
`
`receiving a data block, wherein the data block is included in a data stream (column1,
`
`lines 19-23);
`
`outputting the data block in a compressed form (column 3, lines 31-36; column 5, lines
`
`14-18);
`
`wherein outputting the data block in the compressed form comprises determining whether
`
`to compress the data block with content dependent data compression based onthe type of the
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 015
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 015
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 13
`
`data block (column 2, lines 1-42; column 5, lines 14-18; column6, lines 22-40) or to compress
`
`the data block with a single data compression encoder(i.e., Sebastian discloses a generic
`
`compression system; column 1, lines 55-60; column 4,lines 9-20).
`
`Further regarding claim 86, Sebastian doesnot disclose determining whetherto output
`
`the data block in received form or in a compressed form; and outputting the data block in
`
`received form or the compressed form based on the determination.
`
`However, Kawashimateaches a system thatis related to the one described by Sebastian,
`
`including data compression, and further teaches determining whetherto output the data blockin
`
`received form (i.e., as “pre-compression data”) or in a compressed form; and outputting the data
`
`block in received form or the compressed form based on the determination (column29,lines 43-
`
`67; column 30, lines 1-23).
`
`Regarding claim 86,it would have been obviousto a person ofordinary skill in the art to
`
`output the data block in received form or in compressed form based on a determination as taught
`
`by Kawashimain the methoddisclosed by Sebastian in order to ensure that resources are used
`
`for compression only when compression would beeffective.
`
`Regarding claims 87 and 88,Sebastian discloses compressing the data block to provide
`the data block in the compressed form in accordance with the determination whether to compress
`the data block with content dependent data compressionor the single data compression encoder
`
`(column 2, lines 1-42; column 4, lines 9-20) but doesnot specifically disclose outputting the data
`
`block in received form with a descriptor representative of no compression if the compressing
`
`causes the size the data block in the compressed form to expand with respectto the data block in
`
`received form.
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 016
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 016
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 14
`
`However, Kawashimaalso teaches a system thatis related to the one described by
`Sebastian, including data compression, andfurther teaches outputting the data blockin the
`
`uncompressed form (i.e., as “‘pre-compression data”) with a descriptor representative of no
`
`compressionif the compressed data block is indicative of data expansion (column5, lines 61-67;
`
`column6, lines 1-2; column 30, lines 14-18)
`
`Regarding claims 87 and 88, it would have been obviousto a person of ordinary skill in
`
`the art to outputting the data block in the uncompressed form with a descriptor representative of
`
`no compression as taught by Kawashimain the method disclosed by Sebastian in order to ensure
`
`that resources are used for compression only when compression would be effective.
`Regarding claims 89 and 90, Sebastian discloses compressing the data block to provide
`
`the data block in the compressed form in accordance with the determination whether to compress
`
`the data block with content dependent data compressionor the single data compression encoder;
`
`and
`
`outputting the data block in the compressed form with a descriptor representative of the
`technique usedto compressthe data block to provide the data block in the compressed form
`
`(column3, lines 31-36; column5, lines 14-18).
`
`Regarding claims 96 and 98,Sebastian discloses that the single data compression
`
`encoderis lossless and at least one encoder.associated with the content dependent data
`
`compression is lossless (column2, lines 43-47; column3, lines 37-41; column4, lines 9-20).
`
`Patentable Claims
`
`13.
`
`Claims6, 7, 16, 41, and 42 are confirmed. Thepriorart of record does not specifically
`
`disclose or fairly teach a method includingall of the elements, steps, and limitations recited in
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 017
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 017
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 15
`
`claims 6, 7, 16, 41, and 42 (includingall of the limitations of claim 1 on which they depend),
`
`particularly including associating a plurality of encoders to the data type or compressing the data
`
`block with a plurality of encoders that are associatedto the data type.
`
`Non-Adopted Proposed Rejections
`
`14.
`
`Non-adopted proposedrejections based on LBX
`
`Noneofthe proposedrej ections based on LBX as the primary reference are adopted.
`
`The proposedrejections of independentclaims 1, 69, and 86 based on LBX (on pages 55-
`
`58, 68-70, and 78-82 of 3PR Request) are not adopted. Regarding claims 1, 69, and 86, LBX
`
`generally discloses compressing the data block with at least one or more encodersassociated to
`the type (i.e., a selected algorithm for stream, bitmap, and pixmap compression as discussed on
`
`page 13 of LBX). However, LBX does not teach combining the above step with compressing the
`
`data block with a single data compression encoderif the type is not specifically identified and
`
`associated with a content-dependent encoder.
`
`In addition to 35 U.S.C 102 rejections of claims 1, 69, and 86 as being anticipated by
`LBX, 3PR also proposed 35 U.S.C. 103 rejections ofclaims 1, 69, and 86 as being unpatentable
`
`over LBX in view of Admissions. These proposedrejections are also not adopted. 3PR alleged
`that Admissions generally teachdifferent compression techniquesbut did not show how LBX in
`
`view of Admissionsteachesall of the limitations of claims 1, 69, and 86 including the
`
`combination ofcontent-dependent compression with content-independent compression.
`Noneofthe proposed 35 U.S.C. 102 and 35 U.S.C. 103 rejections of dependent claims 2-
`
`5,9, 11, 16, 17, 20, 21, 23, 27, 39, 70-73, 79, 81, 84, 85, 87-90, 96, and 98 based on LBX are
`
`adopted becausethe proposedrejections of independent claims 1, 69, and 86 based on LBX are
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 018
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 018
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 16
`
`not adopted. Someofthe proposedrejections of dependent claims based on LBXarealso not
`
`adopted forat least the following additional reasons.
`
`In the table of contents and on page 54 of 3PR Request, 3PR proposedthat claims9, 20,
`
`73, 81, and 98 are “anticipated by LBX.” These proposed 35 U.S.C. 102 rejections are not
`
`adopted. The proposed 35 U.S.C. 102 rejections of claims 9, 81, and 98 on pages 60-61, 75-76,
`
`and 91-93 of 3PR Request do not describe how LBX discloses the claim limitations and only
`
`asserts that the limitations are taught by other references, LBX X and Images. The 35 U.S.C. 103
`
`rejections based on LBX X as a secondary referenceare also not adopted because the LBX X
`document does not appearto havea date of publication. The proposed 35 U.S.C. 102 rejection of
`claim 20 on pages63-64 of 3PR Request does not describe how LBX discloses the claim
`
`limitations andonly asserts that the limitations are taught by other references, Held or CCITT
`
`V.42 bis. The proposed 35 U.S.C. 102 rejection of claim 73 on pages 73-74 of 3PR Request does
`
`not describe how LBX discloses the claim limitations and only asserts that the limitations are
`
`taught by other references, Kawashimaor French.
`
`15.|Non-adopted proposedrejections based on French
`
`3PR proposed 35 U.S.C. 103 rejectionsof claims 69 and 86 as being obvious over French
`in view of Admissions (see pages 93-103 and 110-121 of 3PR Request). These proposed 35
`
`U.S.C.103 rejections are not adopted. 3PR asserted that Admissionsteach variouslimitations of
`
`claims 69 and 86 but further noted that French discloses these same limitations and did not
`
`indicate (according to 3PR) how French doesnotalready completely meetthe limitations of
`
`claims 69 and 86.
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 019
`
`Veritas Techs. LLC
`Exhibit 1012
`Page 019
`
`

`

`Application/Control Number: 95/000,479
`Art Unit: 3992
`
`Page 17
`
`3PR hasnotset forth the differences between theprior art and the claimsat issue, as
`
`required by Graham v. John Deere, to establish a prima facie case of obviousness. In 3PR
`
`Request, 3PR alleged that the claims would have been obviousto one of ordinary skill in the art
`w

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