throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`____________
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________
`
`
`
`MICROSOFT CORPORATION and HP INC.,
`
`Petitioners,
`
`v.
`
`SYNKLOUD TECHNOLOGIES, LLC,
`
`Patent Owner.
`
`____________
`
`
`
`Cases IPR2020-01269 and IPR2020-01270
`
`U.S. Patent No. 9,219,780
`
`____________
`
`
`
`SECOND DECLARATION OF ZAYDOON (“JAY”) JAWADI
`IN SUPPORT OF PATENT OWNER’S RESPONSE
`
`IPR2020-01269 and IPR2020-01270
`Exhibit 2014
`
`
`
`i
`
`
`
`
`
`
`

`

`
`
`TABLE OF CONTENTS
`
`
`I. BACKGROUND AND QUALIFICATIONS ..................................................... 1
`
`II. MATERIALS REVIEWED ................................................................................ 6
`
`III. LEGAL UNDERSTANDING ............................................................................. 7
`
`IV. CLAIM CONSTRUCTION ................................................................................ 7
`
`A.
`
`Petitioner’s Construction of “Cache Storage” Is Flawed .............................. 7
`
`V. OPINIONS ......................................................................................................... 12
`
`Independent Claims 1, 9, and 16 Are Not Obvious in View of McCown
`A.
`and Dutta ............................................................................................................... 13
`
`Independent Claims 1, 6, and 9: Utilizing Download Information for the
`a.
`File Cached in the Cache Storage of the Wireless Device ............................... 13
`
`i. Responses to the Board’s Decision Regarding Utilizing Download
`Information for the File Cached in Cache Storage in the Wireless Device .. 15
`
`1. McCown’s Web Page Display vs. ’780 Cache Storage ........................ 15
`
`2. Dutta’s Conventional Browser Cache vs. the ’780 Non-Conventional
`Cache Storage Usage ................................................................................... 16
`
`3. Response to PTAB Decision, 27-28 ..................................................... 18
`
`4. Response to PTAB Decision, 28 ........................................................... 22
`
`5. Response to PTAB Decision, 29 ........................................................... 24
`
`6. Response to PTAB Decision, 30 ........................................................... 26
`
`Summary of Why McCown in View of Dutta Does Not Disclose
`ii.
`Utilizing Download Information for the File Cached in the Cache Storage in
`the Wireless Device ....................................................................................... 27
`
`iii. Petitioners’ Interpretation of Utilizing Download Information for the
`File Cached in the Cache Storage of the Wireless Device in the ’780 Patent
`
`32
`
`iv. Steps of Utilizing Download Information for the File Cached in the
`Cache Storage of the Wireless Device in the ’780 Patent ............................. 34
`
`
`
`ii
`
`

`

`v. McCown Does Not Disclose, Suggest, or Imply Storing Download
`Information in Cache or Retrieving Download Information from Cache ..... 35
`
`vi. Dutta Does Not Disclose How Any Data in Its Cache Is Used ............ 35
`
`vii. Dutta Does Not Disclose, Suggest, or Imply Storing Download
`Information in Cache or Retrieving Download Information from Cache ..... 38
`
`viii. The Combination of McCown and Dutta Does Not Disclose, Suggest,
`or Imply Storing Download Information in Cache or Retrieving Download
`Information from Cache ................................................................................ 38
`
`ix. Petitioners Rely Solely on Expert’s Opinion That It Would Have Been
`Obvious to Store the Download Information in Cache and to Retrieve the
`Download Information from Cache ............................................................... 39
`
`Petitioners’ Readily Accessible Theory for the Motivation for Storing
`x.
`the Download Information in Cache ............................................................. 40
`
`xi. McCown Contradicts Petitioners’ Theory for the Motivation for
`Storing the Download Information in Cache ................................................. 41
`
`xii. Petitioners’ Description of McCown’s Steps Contradicts Petitioners’
`Theory for the Motivation for Storing the Download Information in Cache 44
`
`xiii. McCown Stores the Files in the Storage Site, Further Negating the
`Need to Store the Download Information in Cache ...................................... 47
`
`’780 Patent vs. McCown’s Steps of Utilizing Download Information
`xiv.
`for the File Cached in the Cache Storage of the Wireless Device ................ 49
`
`xv. Difference between Retrieving from Cache and Retrieving from
`Displayed Web Page ...................................................................................... 53
`
`xvi. Download Information for the File (Singular) ................................... 54
`
`xvii. Dutta Does Not Cure McCown’s Deficiencies in Storing Download
`Information in Cache and Retrieving Download Information from Cache .. 55
`
`xviii. Petitioners’ Second Purported Reason (Re-Opening the Webpage) to
`Store Download Information in Cache .......................................................... 56
`
`Storing McCown’s URLs in Cache Is Unnecessary, Wasteful,
`xix.
`Counterintuitive, and Not Obvious ................................................................ 60
`
`xx. Coates Does Not Cure McCown’s and Dutta’s Deficiencies in Storing
`Download Information in Cache and Retrieving Download Information from
`Cache ............................................................................................................. 60
`
`
`
`iii
`
`

`

`xxi. Utilizing Download Information Cached in the Cache Storage of the
`Wireless Device: Independent Claims 1, 9, and 16 Are Not Obvious in View
`of McCown and Dutta ................................................................................... 61
`
`b. Dependent Claims 3, 10, and 17: Cached Downloading Information ..... 61
`
`c. Dependent Claims 2-8, 10-15, and 17-20 Are Not Obvious in View of
`McCown and Dutta and Are Not Obvious in View of McCown, Dutta, and
`Coates ................................................................................................................ 62
`
`VI. CONCLUSION .................................................................................................. 63
`
`
`
`
`
`iv
`
`

`

`I, Zaydoon (“Jay”) Jawadi, declare as follows:
`
`I.
`
`BACKGROUND AND QUALIFICATIONS
`
`1. My name is Zaydoon (“Jay”) Jawadi.
`
`2.
`
`I am an independent expert and consultant. I have been retained as an
`
`expert witness on behalf of SynKloud Technologies, LLC (“SynKloud”) for the
`
`above-captioned Inter Partes Reviews (IPRs) regarding U.S. Patent No. 9,219,780
`
`(“’780 Patent”).
`
`3.
`
`As shown in my curriculum vitae (attached as Exhibit 2002), I have a
`
`Bachelor of Science in Electrical Engineering from Mosul University, a Master of
`
`Science in Computer Science from Columbia University with a Citation for
`
`Outstanding Achievement – Dean’s Honor Student, and over 40 years of
`
`experience in software and product design and development, engineering,
`
`consulting, and management in the fields of data storage, Internet, software, data
`
`networking, computing systems, and telecommunication.
`
`4.
`
`I have worked with and possess expertise in numerous technologies,
`
`including data storage
`
`technologies and
`
`interfaces, Internet and website
`
`technologies, databases, data networking
`
`technologies and protocols, and
`
`telephony.
`
`5.
`
`From 1978 to 1980, I worked as a telecommunication/electrical
`
`engineer for Emirtel (formerly Cable and Wireless, now Etisalat). During my
`
`
`
`1
`
`

`

`employment at Emirtel, among other things, I worked on telephony and
`
`telecommunication products and services, and I developed software in assembly
`
`and high-level languages for archiving, storing, and retrieving data to and from
`
`data storage devices, such as disk drives and tape drives.
`
`6.
`
`From 1981 to 1983, I worked as a software engineer for Amdahl
`
`Corporation (now Fujitsu), a California-based major supplier of computers,
`
`systems, and data storage subsystems.
`
`7.
`
`From 1984 to 1994, I worked as a software, data storage, and systems
`
`consultant to various data storage and computer companies in California, the
`
`United States, Asia, and Europe. I provided technical consulting services in data
`
`storage, data storage systems, data storage devices, software design and
`
`development, system software, device driver software, data storage device
`
`firmware, data storage software, data storage chips, data storage tools, data storage
`
`test systems and test software, data storage and I/O protocol development systems,
`
`data storage and I/O protocol analyzers, data storage and I/O monitoring systems,
`
`and data storage manufacturing systems and software.
`
`8.
`
`From 1992 to 1996, I was President and founder of Zadian
`
`Technologies, Inc., a California-based leading supplier of networked data storage
`
`test systems, with over 50,000 units installed worldwide in mission-critical
`
`customer operations with premier high-technology customers, such as Conner
`
`
`
`2
`
`

`

`Peripherals (now Seagate), DEC (now HP), EMC (now Dell EMC), Exabyte,
`
`Fujitsu, HP, IBM, Intel, Iomega, Quantum (now Seagate), Seagate, Sony,
`
`StorageTek, Tandberg, Tandem (now HP), Toshiba, Unisys, and WD. The
`
`company’s products
`
`included
`
`test systems, manufacturing systems, and
`
`development systems for data storage devices (disk drives, tape drives, removable
`
`drives, flash drives, optical drives, CD-ROM drives, Jukeboxes, and RAID) and
`
`data storage interfaces (SCSI, ATA / IDE / ATAPI, Fibre Channel, SSA, and
`
`PCMCIA / PC Card).
`
`9.
`
`In 1996, Zadian Technologies was acquired by UK-based Xyratex
`
`International LTD (NASDAQ: XRTX, which was later acquired by Seagate,
`
`NASDAQ: STX, in 2014). Following Zadian’s acquisition by Xyratex, I became
`
`an employee of Xyratex until 1998. At Xyratex, I was a general manager of a data
`
`storage interface business unit and, subsequently, a general manager of a data
`
`networking analysis tools business unit, which designed and built Gigabit Ethernet
`
`network protocol analysis and monitoring products, which were sold, under OEM
`
`agreement, by the largest supplier of network protocol analysis and monitoring
`
`products.
`
`10. From 1999 to 2001, I was CEO, Chairman, and cofounder of Can Do,
`
`Inc., a California-based Internet eCommerce and community company. The
`
`CanDo.com website offered over 10,000 products for sale as well as extensive
`
`
`
`3
`
`

`

`consumer features, such as news, chat, messages, and product information for
`
`people with disabilities. The company also provided technologies for display
`
`magnification and sound/audio adaptation through the Internet to make websites
`
`more accessible to persons with vision and hearing impairments. The company
`
`was funded by leading venture capital firms.
`
`11. From 2001 to 2007, I was President and cofounder of CoAssure, Inc.,
`
`a California-based provider of Web-based technology services and solutions for
`
`automated telephony speech recognition and touchtone applications, serving
`
`multiple Fortune-500 companies.
`
`12.
`
`In 2009, I cofounded and have since been President of Rate Speeches,
`
`Inc., a California-based Internet company providing online services, resources, and
`
`technologies for creating, rating, evaluating, and enhancing public speaking,
`
`presentation, and communication skills. Rate Speeches also operates the
`
`ratespeeches.com website and the Speech Evaluator online software.
`
`13. Since moving to Silicon Valley in Northern California in 1981, I have
`
`worked on numerous technology products that have generated billions of dollars in
`
`sales.
`
`14.
`
`I hold a California community college lifelong computer science
`
`instructor credential. I have taught various data storage and computer technologies
`
`
`
`4
`
`

`

`to thousands of professional engineers and academic students in the United States,
`
`Europe, and Asia.
`
`15.
`
`In my work as an expert and consultant, I have examined, analyzed,
`
`and inspected numerous data storage systems, computer systems, software
`
`products, cell phone applications, tens of millions of lines of source code, and the
`
`frontend and backend software of more than 100 websites, including massive,
`
`highly-trafficked consumer and business websites.
`
`16. Through my education, industry and expert experience, and industry
`
`and expert knowledge, I have gained a detailed understanding of the technologies
`
`at issue in this case.
`
`17. My additional industry experience is in my curriculum vitae.
`
`18. My expert litigation support cases, including cases in which I have
`
`testified during the last four years as an expert, can be found in my curriculum
`
`vitae, which is Exhibit 2002.
`
`19. As such, I am qualified to provide opinions regarding the state of the
`
`art at the time the ’780 Patent was filed (which I understand to be no later than
`
`February 16, 2015, but claiming a priority date of December 4, 2003) and how a
`
`person of ordinary skill in the art (“POSITA”) at that time would have interpreted
`
`and understood the ’780 Patent.
`
`
`
`5
`
`

`

`20.
`
`I am being compensated for my work and any travel expenses in
`
`connection with
`
`this proceeding at my standard consulting rates.
`
` My
`
`compensation is in no way dependent on or contingent on the outcome of my
`
`analysis or opinions rendered in this proceeding and is in no way dependent on or
`
`contingent on the results of these or any other proceedings relating to the above-
`
`captioned patent.
`
`21. Although I am not rendering an opinion about the level of skill of a
`
`POSITA proffered by Petitioners, based on my professional experience, I have an
`
`understanding of the capabilities of a POSITA (as such a POSITA is defined by
`
`Petitioners). Over the course of my career, I have supervised and directed many
`
`such persons. Additionally, I myself, at the time the ’780 Patent was filed and at
`
`its priority date, qualified as at least a POSITA.
`
`II. MATERIALS REVIEWED
`
`22.
`
`In preparing this declaration, I reviewed the ’780 Patent, including its
`
`claims in view of its specification, the prosecution history of the ’780 Patent,
`
`various prior art and technical references from the time of the invention, the
`
`IPR2020-01269 Petition (“’1269 Petition”) and its exhibits (Ex. 1001 – Ex. 1036),
`
`and the IPR2020-01270 Petition (“’1270 Petition”) and its exhibits (Ex. 1001 – Ex.
`
`1036).
`
`
`
`6
`
`

`

`23.
`
`I also reviewed excerpts from Newton’s Telecom Dictionary, 15th ed.,
`
`(1999) attached as Exhibit 2015.
`
`III. LEGAL UNDERSTANDING
`
`24.
`
`I have worked with counsel in the preparation of this Declaration.
`
`Nevertheless, the opinions, statements, and conclusions offered in this Declaration
`
`are purely my own and were neither suggested nor indicated in any way by counsel
`
`or anyone other than myself. I confirmed with counsel my understanding that an
`
`obviousness determination requires an analysis of the scope and content of the
`
`prior art, the differences between the prior art and the claims, the level of ordinary
`
`skill in the pertinent art at the time of the invention of the challenged patent, and an
`
`evaluation of any relevant secondary considerations.
`
`IV. CLAIM CONSTRUCTION
`
`25.
`
`I reviewed the comments in the Petition and Petitioners’ expert’s
`
`declaration (Ex. 1003) pertaining to claim “construction of the claims” of the ’780
`
`Patent for both the 1269 and 1270 IPRs. My understanding is simply that the
`
`claims should be construed in accordance with their plain and ordinary meaning in
`
`the context of the specification of the patent and its file history.
`
`A.
`
`Petitioner’s Construction of “Cache Storage” Is Flawed
`
`26. Petitioner argues that “the the ordinary meaning in the context of the
`
`780 Patent of “cache storage” is storage that is more readily accessible by the user
`
`
`
`7
`
`

`

`or user application than the original storage location.” 1269 Petition, 7; 1270
`
`Petition, 7.
`
`27.
`
`In my opinion, Petitioner’s construction of “cache storage” is flawed
`
`and improper.
`
`28. A POSITA would have known that cache storage is not merely any
`
`storage location “that is more readily accessible by the user or user application than
`
`the original storage location.” Such construction omits three basic cache
`
`principles.
`
`29. First, cache storage is used to save information that may be needed
`
`multiple times (subsequent to initial access) in a more readily accessible location,
`
`eliminating the need to retrieve the data again from the original source of the
`
`information. In other words, storing information in cache, when the information is
`
`initially fetched, is intended not for the initial access to the information, but for
`
`subsequent access or accesses to that information. Petitioner’s construction omits
`
`this basic principle of cache.
`
`30. Second, cache storage includes a cache search mechanism invoked
`
`when information is needed. The cache search mechanism is used to determine if
`
`the requested information is in cache (cache hit) or not in cache (cache miss). If
`
`the information is not in cache, the information is fetched and stored in cache in
`
`
`
`8
`
`

`

`anticipation of subsequent accesses to that information. Petitioner’s construction
`
`also omits this basic principle of cache.
`
`31. Third, cache storage includes a replacement algorithm, mechanism, or
`
`policy for replacing information in cache, such as least recently used (LRU)
`
`algorithm. Petitioner’s construction also omits this basic principle of cache.
`
`32. Petitioner’s own references for cache storage describe these three
`
`basic cache principles, namely that cache storage is used to save information that
`
`may be needed multiple times (subsequent to initial access), that cache storage
`
`includes a mechanism to determine cache hit/miss, and that cache storage includes
`
`a replacement algorithm.
`
`33. Petitioner’s EX-1008 (Newton’s Telecom Dictionary), 1999 version,
`
`confirms that cache storage is used to save information that may be needed
`
`multiple times (subsequent to initial access), that cache storage includes a
`
`mechanism to determine cache hit/miss, and that cache storage includes a
`
`replacement algorithm.
`
`“A cache works like this. When the CPU needs data from memory,
`the system checks to see if the information is already in the cache. If it
`is, it grabs that information; this is called a cache hit. If it isn’t, it’s
`called a cache miss and the computer has to fetch the information by
`access the main memory or hard disk, which is slower. Data retrieved
`during a cache miss is often written into the cache in anticipation of
`further need for it.
`...
`
`
`
`9
`
`

`

`Generally, when the cache is exhausted, it is flushed and the data is
`written back to main memory, to be replaced with the next cache
`according to a replacement algorithm.
`...
`The cache also will hold information that you recently accessed, in
`anticipation of your wanting to back up, or access it again.
`...
`Caching A process by which information is stored in memory or
`server in anticipation of next request for information.” Exhibit
`2015, Newton’s Telecom Dictionary, emphasis added
`
`34. Petitioner’s EX-1030 (Microsoft Press Computer Dictionary) also
`
`confirms that cache storage is used to save information that may be needed
`
`multiple times (subsequent to initial access) and that cache storage includes a
`
`mechanism to determine cache hit/miss.
`
`“A special memory subsystem in which frequently used data values
`are duplicated for quick access. A memory cache stores the contents
`of frequently accessed RAM locations and the addresses where
`these data items are stored. When the processor references an address
`in memory, the cache checks to see whether it holds that address.
`If it does hold the address, the data is returned to the processor; if it
`does not, a regular memory access occurs.” EX-1030, Microsoft
`Press Computer Dictionary, emphasis added
`
`35. Petitioner’s omitting (from the cache storage construction) these three
`
`basic principles (that cache stores information that may be needed multiple times /
`
`subsequent to initial access, that cache storage includes a mechanism to determine
`
`cache hit/miss, and that cache storage includes a replacement algorithm) results in
`
`considering or deeming as cache any location that is “that is more readily
`
`accessible by the user or user application than the original storage location.” In
`
`
`
`10
`
`

`

`other words, under such overly broad and flawed construction, any storage location
`
`(e.g., disk drive, random access memory, etc.) that stores the information and that
`
`is faster than the original source would constitute cache, even if the information is
`
`only transitorily and temporarily stored in that location and not saved for future
`
`hits, even if the location is never intended or designed to operate as cache, even if
`
`the location does not operate as cache (missing the three basic cache principles
`
`mentioned above), and even if the location entirely contradicts the three basic
`
`cache principles described earlier.
`
`36. Under Petitioner’s construction, other than the original location where
`
`a web page is stored at the web server, any storage location where the web page is
`
`stored would constitute cache, because any such alleged storage location other than
`
`the original location “is more readily accessible by the user or user application than
`
`the original storage location.”
`
`37. For at least these reasons, in my opinion, Petitioner’s construction of
`
`“cache storage” as “stored in storage that is more readily accessible by the user or
`
`user application than the original storage location” is flawed and improper.
`
`38.
`
`I respectfully disagree with the PTAB’s Decision to adopt Petitioner’s
`
`construction of the term “cache storage” as “stored in storage that is more readily
`
`accessible by the user or user application than the original storage location.” 1269
`
`Decision, 13; 1270 Decision, 13
`
`
`
`11
`
`

`

`39.
`
`In my opinion, the term “cache storage” should be construed in
`
`accordance with its plain and ordinary meaning in the context of the specification
`
`of the ’780 Patent and its file history.
`
`V. OPINIONS
`
`40.
`
`In the 1269 IPR, Petitioners present two grounds under which claims
`
`1-8 and 16-20 of the ’780 Patent are purportedly invalid; in particular, Petitioners
`
`contend that Claims 1-3, 7, 8, and 16-20 are obvious under §103 based on
`
`McCown (Ex. 1005) in view of Dutta (Ex. 1006); and contend that Claims 4-6 and
`
`16-20 are obvious under §103 based on McCown in view of Dutta and Coates (Ex.
`
`1007). ’1269 Petition, 4. In the 1270 IPR, Petitioners present two grounds under
`
`which claims 9-15 of the ’780 Patent are purportedly invalid; in particular,
`
`Petitioners contend that Claims 9, 10, 12, 13, and 15 are obvious under §103 based
`
`on McCown in view of Dutta; and contend that Claims 9-15 are obvious under
`
`§103 based on McCown in view of Dutta, and in further view of Coates. ’1270
`
`Petition, 4.
`
`41.
`
`In my opinion, as described below, Petitioners have not established a
`
`reasonable basis to conclude that the claims of the ’780 Patent are obvious.
`
`
`
`12
`
`

`

`A.
`
`Independent Claims 1, 9, and 16 Are Not Obvious in View of
`McCown and Dutta
`
`42. Petitioners contend that independent Claims 1, 9, and 16 are obvious
`
`over McCown (Ex. 1005) in view of Dutta (Ex. 1006). ‘1269 Petition, 4; ‘1270
`
`Petition, 4. I disagree for the reasons outlined below.
`
`a. Independent Claims 1, 6, and 9: Utilizing Download
`Information for the File Cached in the Cache Storage of the
`Wireless Device
`
`43.
`
`Independent Claim 1 of the ’780 Patent recites utilizing download
`
`information for the file cached in the cache storage of the wireless device.
`
`“1. A wireless device access to a remote storage space, the wireless
`device comprising:
`at least one cache storage, and one non-transitory computer-readable
`medium comprising program instructions which, being executed by
`the wireless device, cause the wireless device remotely access to the
`storage space, the program instructions include:
`…
`program instructions for coupling with the storage server across the
`wireless link to carry out a requested operation for remotely access to
`the storage space in response to the user from the wireless device
`performed the operation,
`wherein the program instructions for carrying out operation for the
`access to the storage space comprises program instructions for storing
`data therein or retrieving data therefrom,
`the program instructions for storing data including program
`instructions for downloading a file from a remote server across the
`Internet into the storage space through utilizing download information
`for the file, including name of the file and internet protocol (“IP”)
`address of the remote server, cached in the cache storage in response
`to the user from the wireless device performed the operation for the
`downloading.” ’780 patent, Claim 1.
`
`
`
`
`13
`
`

`

`44.
`
`Independent Claim 9 of the ’780 Patent also recites utilizing download
`
`information for the file cached in the cache storage of the wireless device.
`
`“9. A server comprising:
`a pool of a plurality of storage spaces, and non-transitory computer-
`readable storage medium comprising program instructions which,
`being executed by the server, causes the server delivering storage
`service, the program instructions include:
`program instructions for allocating exclusively, via the storage pool, a
`first one of the storage spaces to a user of a first wireless device;
`program instructions for establishing a communication link for the
`first wireless device remotely access to the first one of the storage
`spaces;
`…
`program instructions for updating the first one of the storage spaces in
`response to the user from the first wireless device performed an
`operation for said remotely access to the first one of the storage
`spaces,
`wherein said access to the first one of the storage spaces comprises
`storing data therein or retrieving data therefrom,
`the storing of a data object including to download a file from a remote
`server into the first one of the storage spaces through utilizing
`download information for the file, including name of the file and
`internet protocol (“IP”) address of the remote server, cached in a
`cache storage of the first wireless device in response to the user from
`the first wireless device performed the operation for the
`downloading.” ‘780 patent, claim 9.
`
`
`
`45.
`
`Independent Claim 16 of the ’780 Patent also recites utilizing
`
`download information for the file cached in the cache storage of the wireless
`
`device.
`
`“16. A system comprising:
`at least one storage server and one wireless device;
`wherein the storage server comprises a plurality of storage spaces, a
`first one of which being allocated to a user of the wireless device for
`
`
`
`14
`
`

`

`exclusive access, and causes presenting the first one of the storage
`spaces to the user on the wireless device, and
`updates the first one of the storage spaces in response to the user from
`the wireless device performed an operation for remotely access to the
`first one of the storage spaces; and
`wherein the wireless device couples with the storage server across a
`wireless link to carry out a requested operation for remotely access to
`the first one of the storage spaces in response to the user from the
`wireless device performed the operation for the access,
`wherein the operation for remotely access to the first one of the
`storage spaces comprises storing data therein or retrieving data
`therefrom,
`the storing of said data including to download a file from a remote
`server into the first one of the storage spaces through utilizing
`download information for the file cached in a cache storage in the
`wireless device in response to the user from the wireless device
`performed the operation for the downloading.” ’780 patent, Claim 16.
`
`
`
`
`
`i. Responses to the Board’s Decision Regarding Utilizing
`Download Information for the File Cached in Cache
`Storage in the Wireless Device
`
`46.
`
`I respectfully disagree with the conclusions in the PTAB’s Decision
`
`regarding the limitation of utilizing download information for the file cached in
`
`cache storage of the wireless device.
`
`1. McCown’s Web Page Display vs. ’780 Cache
`Storage
`
`47.
`
`I respectfully point out that the Decision generally appears to overlook
`
`the fact that McCown teaches obtaining the URL(s) (download information) from
`
`the wireless device web page display, which is significantly different from and
`
`
`
`15
`
`

`

`opposite to obtaining the download information from the wireless device cache
`
`storage, as recited in the limitations of the independent claims of the ’780 Patent.
`
`48.
`
`I elaborate further on this point in later sections (§§ V.A.a.x-
`
`V.A.a.xix) of this declaration.
`
`2. Dutta’s Conventional Browser Cache vs. the
`’780 Non-Conventional Cache Storage Usage
`
`49.
`
`I respectfully point out that the Decision generally appears to overlook
`
`the difference between the conventional browser cache in the combination of
`
`McCown and Dutta versus the non-conventional use of wireless device cache
`
`storage in the ’780 Patent.
`
`50. Dutta discloses a generic browser cache. Dutta does not disclose or
`
`imply download information, does not disclose or imply any purpose for the Dutta
`
`browser cache, and does not disclose or imply storing download information in the
`
`Dutta browser cache.
`
`51. McCown does not disclose or imply cache and does not disclose or
`
`imply storing download information in cache.
`
`52. A POSITA would not have been motivated to combine McCown with
`
`Dutta and would not have been motivated to store McCown’s download
`
`information in cache (whether Dutta’s cache or other cache) at the wireless device,
`
`because McCown retrieves all the download information at once and sends it to the
`
`storage server.
`
`
`
`16
`
`

`

`53.
`
`In other words, Dutta discloses a generic, conventional browser cache,
`
`and the combination of McCown and Dutta would also produce a generic,
`
`conventional browser cache. In contrast, the ’780 Patent recites non-conventional
`
`usage of cache storage at the wireless device, namely storing and subsequent
`
`retrieving of download information for out-of-band operation. The combination of
`
`McCown and Dutta does not disclose this non-conventional cache application. In
`
`addition, in my opinion, a POSITA would not have found obvious the ’780 non-
`
`conventional use of the wireless device cache for storing and subsequent retrieving
`
`of download information for out-of-band operation.
`
`54. Even assuming, arguendo, that a POSITA would have been motivated
`
`to combine Dutta’s cache with McCown, the purpose of such purported cache
`
`combination would still be to obtain / retrieve the download information again. In
`
`such combination, during a purported subsequent retrieval of the web page
`
`containing the URLs (download information), according to McCown’s teachings,
`
`McCown would again obtain the download information during the subsequent
`
`retrieval from the web page display, not from cache. Thus, the combination of
`
`established functions from McCown and Dutta would not generate the same result
`
`as the ’780 Patent recites.
`
`55.
`
`I elaborate further on this point in later sections (§§ V.A.a.x-
`
`V.A.a.xix) of this declaration.
`
`
`
`17
`
`

`

`56. Even assuming, arguendo, that a POSITA would have been motivated
`
`to combine Dutta’s cache with McCown, in my opinion, in 2003, a POSITA would
`
`have understood that combining McCown and Dutta would have required major
`
`architectural changes to McCown and Dutta.
`
`57. For example, McCown requires software on the client wireless device
`
`to emulate a hard disk drive that is actually located on a storage server (e.g.,
`
`McCown at 9:14-18, 15:27-16:4) and requires the software to communicate with
`
`the web browser to support the operations of drag-and-drop and copy-and-paste.
`
`However, in the purported combined system of McCown and Dutta, all these
`
`functions would need to be modified and adapted. Such undertaking would have
`
`discouraged a POSITA from combining McCown and Dutta.
`
`58.
`
`I elaborate further on the above points in later sections (§§ V.A.a.vi-
`
`V.A.a.ix) of this declaration.
`
`3. Response to PTAB Decision, 27-28
`
`59. The PTAB Decision states that “Patent Owner, however, does not
`
`address Petitioner’s contention that “[a] Skilled Artisan would understand that the
`
`use of a browser cache in wireless devices was well-k

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