`Google, et al. v. Parus Holdings, Inc.
`IPR2020-00846
`Page 1 of 4
`
`
`
`Case No. IPR2020-00846 & -00847
`
`US. Patent Nos. 7,076,431 & 9,451,084
`
`1. Paul Mulka, hereby declare the following:
`
`1.
`
`My name is Paul Mulka. 1 am a citizen of the United States
`
`over 21 years of age. I make this Declaration based on facts and matters within my
`
`own knowledge and on information provided to me by others, and if called as a
`
`witness, I could and would competently testify to the matters set forth herein.
`
`2.] am a professional software engineer with over 20 years of work
`
`experience in the sofiware industry.
`
`I graduated from college with a Bachelor of
`
`Science in Computer Science and Mathematics in the December 1998. After
`
`graduating college, [joined Webley Systems as a software engineer. Starting in
`
`July 1999, 1 was part of the team that developed the Webley Assistant. Through
`
`the remainder of 1999 and into 2000,
`
`I worked on debugging and developing
`
`software related to the Webley Assistant.
`
`3. While working at Webley,
`
`I became personally acquainted with
`
`Alexander Kurganov and Valery Zhukoff.
`
`4. Based on information provided to me from the management at Parus, Inc.
`
`(formerly Webley Systems) and a review of the source code management system,
`
`it is my understanding that Alex and Valery were employed by Webley Systems in
`
`1999 and 2000. From at least November 1999 through January 2000, Alex and
`
`Valery were employed full time in developing the Webley Assistant’s website
`
`access functionality, including weather, stock price, and other functionality.
`
`l
`
`Parus Exhibit 2060, Page 2 of 4
`
`Parus Exhibit 2060, Page 2 of 4
`
`
`
`Case No. IPR2020-00846 & -00847
`
`US. Patent Nos. 7,076,431 & 9,451,084
`
`5. From the time I started working at Webley Systems, the company used a
`
`source code management tool called CVS. CVS tracks when source code is
`
`checked into the system after creation or after edits have been made by users. The
`
`time of the check-in and the identity of the person who checked the source code in
`
`to the system is tracked by the system. Typically, a source code file is created by a
`
`software engineer and later checked into the CVS system.
`
`6. Based on my review of the CVS records between December 1, 1999 and
`
`January 10, 2000 (attached as Exhibit A), Alex checked in 11 source code files
`
`related to speech recognition and functionality additions to the Webley Assistant
`
`and Valery checked in 47 source code files between December 1, 1999 and
`
`January 7, 2000 related to web server and agent code. Most, if not all, of the
`
`source code files checked in to the CVS system by Alex and Valery related to the
`
`website access component of the Webley Assistant.
`
`That
`
`supports my
`
`understanding that Alex and Valery were working full time on the website access
`
`aspects of the Webley Assistant.
`
`I»)
`
`Parus Exhibit 2060, Page 3 of 4 7%
`
`Parus Exhibit 2060, Page 3 of 4
`
`
`
`Case No. 1PR2020-00846 & -00847
`
`US. Patent Nos. 7,076,431 & 9,451,084
`
`I declare that all statements made herein of my knowledge are true, and that
`
`all statements made on information and belief are believed to be true, and that
`
`these statements were made with the knowledge that willful false statements and
`
`the like so made are punishable by fine or imprisonment, or both, under Section
`
`1001 ofTitle 18 ofthe United States Code.
`
`Date:
`
`" / 0 Q: L) Q /
`
`By:
`
`, /‘ ,-,
`,7
`.I
`a ‘1
`.,, CW9 K WAX/fig,
`
`Paul Mulka
`
`Lu
`
`Parus Exhibit 2060, Page 4 of 4
`
`Parus Exhibit 2060, Page 4 of 4
`
`
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
