throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`
`
`STARBUCKS CORP.
`Petitioner
`
`v.
`
`AMERANTH, INC.
`Patent Owner
`
`____________
`
`Case CBM2015-00091
`U.S. Patent No. 6,384,850
`____________
`
`
`MAIL STOP PATENT BOARD
`Patent Trial and Appeal Board
`United States Patent and Trademark Office
`Post Office Box 1450
`Alexandria, Virginia 22313-1450
`
`
`
`
`
`PATENT OWNER AMERANTH’S SUR-REPLY BRIEF
`
`
`
`
`

`
`CBM2015-00091
`
`
`
`Petitioner Starbucks entirely ignored most of Ameranth’s strong secondary
`
`considerations evidence. The arguments Petitioner did make should be given no
`
`weight by the Board, because they are factually and/or legally incorrect, and/or
`
`ignore the record evidence, and/or are based upon nothing but attorney argument.
`
`
`
`As shown in PO's Response – and not disputed in Petitioner's Reply Brief –
`
`a strong nexus exists between the Challenged Claims and Ameranth's 21st Century
`
`Restaurant (21CR) system, and thus also between the evidence of commercial
`
`success, praise and awards for 21CR and the Challenged Claims. See, e.g., Exh.
`
`2047 (brochures) and other 21CR evidence; POR (Paper 17) at 59-64. Further, the
`
`systemic nexus of "synchronization, integration, and consistency" is neither
`
`“inaccurate” nor "improper", as Petitioner erroneously argues. In fact, these
`
`inventive merits were identified by the Board itself in CBM 2014-00015, Paper 20,
`
`(Inst. Dec.) and with the Board’s construction of "synchronization" yielding
`
`"consistency", confirms the nexus to be both accurate and correct. (See POR at 56.)
`
`Dallas Improv owner Tom Castillo confirmed he was "won over" by Ameranth's
`
`May 1999 demonstration of 21CR and that the "total solution" i.e. the ‘nexus’
`
`was one that no other company could match thus confirming the inventive nexus
`
`was unavailable from any other company. (Exh. 2062, pp. 117-119.)
`
`
`
`The strong evidence of praise and awards for 21CR set forth in the POR
`
`accordingly has the requisite nexus to the Challenged Claims. That evidence
`
`- 1 -
`
`
`

`
`CBM2015-00091
`
`includes the testimony of eyewitness John Harker as to the overwhelming
`
`hospitality industry reception at the May 1999 introduction of Ameranth's 21CR
`
`technology: "… the Ameranth booth was packed … for four straight days, not
`
`only with restaurateurs, but with also the vendor community, the POS vendors,
`
`other hospitality technology providers. And, you know, I knew they would be
`
`busy. I was shocked at how busy they truly were." (Exh. 2045 at p. 107, ln. 16-
`
`25, emphasis added.) It also includes the four technology awards earned by 21CR.
`
`(Exh. 2062, pp. 94-96, 140-141, 156-160, and Exh. 2050.) This undisputed market
`
`reaction upon the introduction of a new product would not have occurred for an
`
`"obvious" product, or for "existing technology".
`
`Petitioner's arguments re PO's license evidence are also erroneous; Petitioner
`
`essentially argues that a license can only be used as evidence of nexus if each
`
`claim is licensed separately. But, in addition to the indisputable fact that licensees
`
`nearly always license entire patents or patent families and not just one or two
`
`claims, there is no requirement that a license, to be evidence of a nexus, must be a
`
`license for only one patent claim or the small set of claims chosen for a CBM by a
`
`petitioner. Ameranth's 46 patent licenses are for the closely-related patents in the
`
`same family of which the '850 patent is the parent. The press releases of the patent
`
`licenses (which were jointly issued with the licensees), see Exh. 2048, specifically
`
`reference the '850 and '325 patents and mobile/web food ordering/reservations for
`
`- 2 -
`
`
`

`
`CBM2015-00091
`
`restaurants, referring to these patents as "essential to achieving a totally
`
`synchronized system." Further, the included Agilysys license specifically
`
`includes a license to all claims of the '850 and '325 patents, including all of the
`
`Challenged Claims. (Exh. 2048, pp. 11-12.)
`
`
`
`Also, Petitioner falsely claimed in its Reply (at p. 21), citing footnote 15 in
`
`the POR in CBM2014-00015, that Patent Owner previously argued that these
`
`licenses were for only '850 claims 1-11 – but Ameranth did not say the licenses
`
`were for those specific claims. Claims 12-16 weren’t discussed in that full POR
`
`because they weren’t instituted in that CBM. Thus that argument is as baseless as
`
`Petitioner's theories arguing that the application of licenses to one patent in a
`
`family makes them inapplicable to the others in the same family. It doesn’t.
`
`
`
`Petitioner's Reply erroneously claims that the 2003 RAD Award is
`
`inapplicable because Ameranth's Hostalert did not include "web components".
`
`Petitioner's claim is untrue. Hostalert did include "web components" and
`
`"seamless integration": "The system efficiently accepts and seamlessly integrates
`
`reservations from all internet, call center, and in-house sources including your own
`
`website." (Exh. 2022, pp. 65-66, emphasis added.)
`
`Also, contrary to Petitioner's erroneous Reply, there is ample evidence of
`
`successful commercialization, and Ameranth’s products were not deployed "only"
`
`at the Dallas Improv. Ameranth’s evidence of 70% market share of the top ten
`
`- 3 -
`
`
`

`
`CBM2015-00091
`
`POS companies is unrebutted. Further, the Improv ticketing system rolled out
`
`nationwide, including, e.g., the Washington D.C. Improv, (see Exh. 2022 at p. 86,
`
`a "web page" screenshot showing the '850 and `325 patents marked with the
`
`system, confirming nexus of this commercial success with the claims/patents). The
`
`evidence submitted by PO further confirms more than 100 deployed locations with
`
`Aloha POS (Exh. 2021, p. 14), plus mobile food ordering in many NBA arenas
`
`including Dallas, Chicago, Toronto, Los Angeles, and Miami, and all Medieval
`
`Times restaurants (Exh. 2021, pp. 23-25, 36). There are now more than 50,000
`
`total locations that have licensed the '850 and '325 patents. (Exh. 1041.)
`
`
`
`Petitioner's reply argument regarding its own copying is disingenuous. The
`
`Microsoft emails confirm that Starbucks VP Rob Reed asked for, received, liked,
`
`and distributed Ameranth's technical documents within Starbucks in 2006. (Exh.
`
`2053.) If this wasn’t true, Starbucks would have submitted a declaration from Rob
`
`Reed, denying it. That they didn’t confirms that it is true. Starbucks brazenly
`
`claims it "doesn’t have" order-ahead functions despite Starbucks' own management
`
`calling order-ahead mobile ordering its "holy grail" (Exh. 2008). Dr. Weaver
`
`(Exh. 2041, ¶ 147) testified that he reviewed the evidence submitted with the POR,
`
`including the Power Point slides and screenshots from Ameranth's 2006
`
`presentation to Starbucks, and Starbucks' own materials on its "Mobile Order &
`
`Pay" system, and concluded that Starbucks had indeed copied the relevant features
`
`- 4 -
`
`
`

`
`CBM2015-00091
`
`of the Challenged Claims. This testimony is unrebutted.
`
`
`
`Regarding copying by others as set forth in the POR, Petitioner doesn't
`
`dispute any of the evidence presented with respect to said copying. Further,
`
`Petitioner is erroneous in arguing that an infringement analysis of specific claims
`
`("meets the limitations", Reply at 24) must be shown to demonstrate copying as
`
`secondary evidence of nonobviousness. Copying and infringement are different.
`
`As for failure of others, the POR shows that Food.com took a license from
`
`Ameranth because its CEO admitted on July 15, 1999 to the "failures" in their
`
`system (i.e., slowness, inefficiencies, and error prone), which existed because they
`
`failed in solving these problems and needed Ameranth’s technology to solve them.
`
`“Ameranth’s technology will help us to increase both the speed and the efficiency
`
`in transmitting orders to our partner restaurants and will significantly decrease our
`
`margin of error’. (Exh. 2062, p. 69.) Further, Pizza Hut received Ameranth's
`
`technical information in 2006, and then after receiving a technology award based
`
`from it in 2009 for their own new online/mobile ordering system, Pizza Hut’s CIO
`
`admitted they had failed to achieve such a system a decade earlier: "We took a run
`
`at that in the late 1990’s but failed." (Exh. 2018, p. 5.)
`
`
`
`For these reasons and those set forth in the POR, its expert report and
`
`exhibits, there is substantial, convincing objective evidence of nonobviousness, in
`
`addition to the strong "primary" reasons for nonobviousness set forth in the POR.
`
`- 5 -
`
`
`

`
`Dated: April 4, 2016
`
`Respectfully Submitted,
`
`CBM2015-00091
`
`
` /s/ John W. Osborne
`__________________________
`
`John W. Osborne
`Lead Counsel for Patent Owner
`USPTO Reg. No. 36,231
`OSBORNE LAW LLC
`33 Habitat Lane
`Cortlandt Manor, NY 10567
`josborne@osborneipl.com
`Tel.: 914-714-5936
`Fax: 914-734-7333
`
`Michael D. Fabiano
`Back-up Counsel for Patent Owner
`USPTO Reg. No. 44,675
`FABIANO LAW FIRM, P.C.
`12526 High Bluff Drive, Suite 300
`San Diego, CA 92130
`mdfabiano@fabianolawfirm.com
`Tel.: 619-742-9631
`
`
`
`- 6 -
`
`
`

`
`CBM2015-00091
`
`
`CERTIFICATE OF SERVICE
`
`I certify that, in accordance with 37 C.F.R. §42.6, a true and correct copy
`
`of the foregoing was served on April 4, 2016 by causing said documents to be
`
`delivered via electronic mail, per agreement of the parties, to counsel for
`
`
`Patrick N. McKeever
`Perkins Coie LLP
`11988 El Camino Real, Suite 350
`San Diego, CA 92130
`PMcKeever@perkinscoie.com
`
`
`Yun L. Lu
`Perkins Coie LLP
`11988 El Camino Real, Suite 350
`San Diego, California 92130
`LLu@perkinscoie.com
`
` /s/ Michael D. Fabiano
`__________________________
`
`Petitioner at the following addresses:
`
`
`Bing Ai
`Perkins Coie LLP
`11988 El Camino Real, Suite 350
`San Diego, California 92130
`Ai-ptab@perkinscoie.com
`
`
`Matthew C. Bernstein
`Perkins Coie LLP
`11988 El Camino Real, Suite 350
`San Diego, California 92130
`MBernstein@perkinscoie.com
`
`
`
`
`Dated: April 4, 2016
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`- 7 -

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