throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`GOOGLE INC.
`
`Petitioner
`
`V.
`
`SIMPLEAIR, INC.
`Patent Owner
`
`Case IPR: Unassigned
`
`DECLARATION OF VIJAY MADISETTI
`
`Mail Stop “PA TENT BOARD”
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`
`P.O. Box 1450
`
`Alexandria, VA 22313-1450
`
` SIMPLEAIR EXHIBIT 2033
`
`Google v. Simp|eAir
`|PR2015—OO18O
`
`i
`
`GOOG 1002
`IPR of U.S. Patent No. 8,601,154
`
`

`
`TABLE OF CONTENTS
`
`Overview ....................................................................................................... .. 1
`
`II.
`
`III.
`
`IV.
`
`Background and Qualifications .................................................................... .. 2
`
`Documents Considered ................................................................................. .. 7
`
`Relevant Legal Standards ............................................................................. .. 9
`
`A.
`
`B.
`
`C.
`
`Ordinary Skill ...................................................................................... ..9
`
`Anticipation ....................................................................................... ..10
`
`Obviousness ....................................................................................... .. 10
`
`State of the Art ............................................................................................ .. 12
`
`VI.
`
`The ‘154 Patent ........................................................................................... .. 20
`
`A.
`
`B.
`
`Claims Considered ............................................................................ ..26
`
`Claim Constmction ........................................................................... ..31
`
`1.
`
`2.
`
`Prior Related Constructions ................................................... .. 31
`
`Additional Constructions ....................................................... .. 35
`
`VII.
`
`Analysis ...................................................................................................... .. 36
`
`A.
`
`Prior Art Grounds .............................................................................. ..36
`
`1.
`
`The Yan-Kane Grounds ......................................................... .. 37
`
`a.
`
`Yan in View of Kane renders claims 1, 2, 3, 6, 7, 8,
`24 and 29 obvious. ....................................................... .. 41
`
`b.
`
`Yan in view of Kane and in further view of
`
`Verkler renders claims 4 obvious ................................ .. 60
`
`c.
`
`Yan in view of Kane and in filrther view of Reilly
`under 35 U.S.C §103 renders claims 9, 10, 14, 15,
`16, 17, 19, 20, 21 and 27 obvious ................................ .. 61
`
`(1.
`
`Yan in View of Kane and in fi.1I'thCI‘ view of
`
`Olazabal renders claim 11 obvious .............................. .. 66
`
`e.
`
`Yan in View of Kane and in lhrther View of Reilly
`and in still further View of PC Magazine under 35
`U.S.C §103 renders claim 13 obvious ......................... .. 67
`
`

`
`f.
`
`Yan in View of Kane,
`in View of Verkler and in
`still further View of Reilly under 35 U.S.C. §103
`renders claims 30, 31, 32, 33 and 34 obvious ............. .. 69
`
`VIII. Conclusion .................................................................................................. .. 73
`
`

`
`perform “functions
`
`well known to users of selective call receivers and portable
`
`personal computing devices.” (GOOG 1009, 728-10.)
`
`88.
`
`In an example, I believe the combination of Yan and Kane can be viewed as
`
`a combination of the Figure 1 of Yan and the Figure 1 of Kane that illustrates the
`
`Central Broadcast Server of Yan that includes the additional data block processing
`
`for transmission to receivers carried out
`
`in the transmission and information
`
`gateways of Kane, e.g., central terminal (102).
`
`-40-
`
`

`
`§l>ai>« Viral»?
`
`Remote
`
`Device
`
` Information
`(Yan)
`
`Source
`
`i\7€’('il@u41s gem/W
`
`-Ivsfe Source,
`
`IICIIUW
`
`
`
`INISIIIII
`HOW]!
`\ "=rs-'=-
`hi}.--4——— —————-_._.l
`
`3395
`CW)
`
`rnnvtotluluunnnéu
`
`—.___—. —_—.———_——--—._—___.___-..-—-;.a.....
`
`4.
`
`
`
`(Yan)
`
`Central Broadcast
`
`Server
`
`Transmission Gateway
`and Information
`
`Gateway (Kane)
`
`a.
`
`Yan in View of Kane renders claims 1, 2, 3, 6, 7, 8, 24
`and 29 obvious.
`
`89.
`
`Claim 1: Preamble, “A method to transmit data from an information
`
`source via a central broadcast server to remote computing devices,
`
`the
`
`-41-
`
`

`
`method comprising” (See, CC-A, 1.P): Yan describes a SIFT server, which can
`
`be “a running server that disseminates tens of thousands of Netnews articles daily.”
`
`(GOOG 1042, p. 178.) “Netnews is an extremely diverse source of information.”
`
`(GOOG 1042, p. 185.) Further, Yan suggests that any of the SIFT servers could
`
`have additional sources of information: “Sifting Netnews is just one application of
`
`SIFT. We have set up another SIFT server, disseminating Computer Science
`
`Technical Reports.” (GOOG 1042, p. 181.) Thus,
`
`I believe Netnews and the
`
`Computer Science Technical reports are information sources, and the SIFT server
`
`is a central broadcasting server.
`
`90.
`
`In the same field, utilizing email, Kane discloses “[a]n electronic mail
`
`message delivery system (100) [that] includes an electronic mail network (113) for
`
`delivering electronic mail messages from originating devices to destination
`
`devices,
`
`the electronic mail messages including network addresses (212)
`
`for
`
`identifying originating and destination devices communicating the electronic mail
`
`messages, and including message data (214).” (GOOG 1009, Abstract.)
`
`91.
`
`“A paging terminal (102) is coupled to the electronic mail network (113) for
`
`receiving the electronic mail messages, storing the received electronic mail
`
`messages including alias. identification (208, 210) of the originating devices of the
`
`electronic mail messages, and encoding messages including the message data and
`
`-42-

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