SimpleAir, Inc. v. Google Inc.
70 F. Supp. 3d 747
E.D. Tex.2014Background
- SimpleAir sued Google for infringing claims 1, 2, 3, 7, and 22 of U.S. Patent No. 7,035,914, alleging Google’s GCM/C2DM (Accused Services) practice the claimed method; a jury found infringement and no invalidity.
- Google moved under Fed. R. Civ. P. 50 for JMOL on (1) insufficient evidence of infringement and (2) obviousness; the Court reviews under a deferential standard drawing all inferences for the nonmoving party.
- Claim 1 recites a multi-step method including: transmitting data from an information source to a central broadcast server; preprocessing (including parsing) at the server; transmitting to an information gateway to build data blocks and assign addresses; transmitting preprocessed data to receivers communicating with devices; and instantaneously notifying devices whether online or offline via a data channel.
- At trial SimpleAir advanced three infringement theories (first-party Google servers, GCM FrontEnd→BackEnd transmissions, and attribution of third-party actions to Google); the Court found substantial evidence supporting the first two theories.
- Google also asserted obviousness based on SkyTel, AT&T ('284), and Bell ('486) references; the jury found the asserted claims not invalid, and the Court found substantial evidence supporting that verdict including secondary considerations (licenses, industry praise, commercial embodiment).
Issues
| Issue | Plaintiff's Argument | Defendant's Argument | Held |
|---|---|---|---|
| Sufficiency of evidence that Google "transmits data from an information source to a central broadcast server" | Google application servers and GCM FrontEnd/BackEnd transmissions carry data originating from information sources; experts testified to this mapping | "From" requires the information source itself to perform the sending; transmission within server components doesn't satisfy the claim | Court: Google waived new claim-construction attack; substantial evidence supports infringement under first-party and FrontEnd→BackEnd theories; verdict stands |
| Preprocessing / parsing limitation | Parsing of the TCP/IP packet by GCM constitutes parsing and thus preprocessing; other preprocessing (e.g., verification) also shown | Claim requires separate preprocessing step plus separate parsing; parsing must target payload only | Court: parsing is a type of preprocessing; parsing of full TCP/IP packet suffices; substantial evidence supports verdict |
| "Assigning addresses to said data blocks" | Ordinary meaning of address suffices; MCS endpoint address is the address needed to route messages to the device | Address must be the device’s destination address (e.g., phone address), not an intermediate endpoint | Court: plain meaning not limited to device address; MCS endpoint qualifies as destination address; evidence adequate |
| "Transmitting preprocessed data to receivers" (and who performs transmitting) | Google’s MCS server initiates/transmits messages to receivers causing delivery to devices (direct infringement under SiRF) | Actual transmission performed by carrier/third parties; if third parties perform steps, Google lacks control for joint infringement | Court: SiRF controls — initiating transmission suffices; substantial evidence supports Google’s performance; in any event Google controls receivers sufficiently for vicarious/joint liability |
| "Instantaneously notifying" devices whether online/offline via a data channel | GCM transmission to receivers automatically notifies device processors; GCM works when devices are online via data channel | Notification occurs within the device (receiver) and not by Google; insufficiency and joint-infringement defenses | Court: Expert and Google witness support that MCS transmission causes notification; jury could credit that testimony; alternatively, Google controls receivers so third-party actions are attributable to Google |
| Sufficiency for dependent claims (2,3,7,22) | Dependent limitations were shown at trial; many depend on claim 1 findings | Many arguments were bare, conclusory | Court: Google largely waived detailed challenge under local rules; even on merits, record evidence supports infringement of dependent claims |
| Invalidity – obviousness based on SkyTel, '284, '486 | Prior art combination renders claims obvious; SkyTel system shows similar features | Prior art does not disclose notification whether devices are online/offline via a data channel; SkyTel is a combination of references and does not map to claims; secondary considerations weigh against obviousness | Court: Google failed to prove obviousness by clear and convincing evidence; jury reasonably credited SimpleAir’s expert and secondary considerations; JMOL on invalidity denied |
Key Cases Cited
- Reeves v. Sanderson Plumbing Prods., 530 U.S. 133 (2000) (JMOL standard: courts must draw all reasonable inferences for nonmovant and not weigh credibility)
- KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398 (2007) (legal standard for obviousness; must identify reason to combine prior art)
- Phillips v. AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (claim construction: give terms their plain and ordinary meaning absent contrary construction)
- SiRF Tech., Inc. v. Int'l Trade Comm'n, 601 F.3d 1319 (Fed. Cir. 2010) (initiating transmission can constitute performance of transmitting step for infringement)
- Aristocrat Techs. Austl. Pty Ltd. v. Int'l Game Tech., 709 F.3d 1348 (Fed. Cir. 2013) (joint-infringement standard requires control or direction to hold party liable for steps performed by others)
- Versata Software, Inc. v. SAP Am., Inc., 717 F.3d 1255 (Fed. Cir. 2013) (JMOL and post-trial claim construction waiver principles)
- Finisar Corp. v. DirecTV Group, Inc., 523 F.3d 1323 (Fed. Cir. 2008) (standard of review for JMOL in patent cases)