throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`APPLE, INC., EVENTBRITE INC., STARWOOD HOTELS & RESORTS
`WORLDWIDE, INC., EXPEDIA, INC., FANDANGO, LLC,
`HOTELS.COM, L.P., HOTEL TONIGHT, INC., HOTWIRE, INC.,
`KAYAK SOFTWARE CORP., OPENTABLE, INC., ORBITZ, LLC, PAPA
`JOHN’S USA, INC., STUBHUB, INC., TICKETMASTER, LLC, LIVE
`NATION ENTERTAINMENT, INC., TRAVELOCITY.COM LP,
`WANDERSPOT LLC, AGILYSYS, INC., DOMINO’S PIZZA, INC.,
`DOMINO’S PIZZA, LLC, HILTON RESORTS CORPORATION,
`HILTON WORLDWIDE, INC., HILTON INTERNATIONAL CO., MOBO
`SYSTEMS, INC., PIZZA HUT OF AMERICA, INC., PIZZA HUT, INC.,
`and USABLENET, INC.,
`Petitioner
`
`v.
`
`AMERANTH, INC.
`Patent Owner
`
`____________
`
`Case CBM2015-000801
`Patent No. 6,384,850
`____________
`
`Submitted Electronically via the Patent Review Processing System
`
`CORRECTED PATENT OWNER’S RESPONSE
`
`1 CBM2015-00096 has been consolidated with this proceeding.
`
`

`
`TABLE OF CONTENTS
`
`CBM2015-00080
`
`Page
`
`I. STATEMENT OF PRECISE RELIEF REQUESTED ...................................... 1
`II. INTRODUCTION.............................................................................................. 1
`III. CLAIM CONSTRUCTION ............................................................................... 3
`1.
`“wireless handheld computing device” ....................................................... 4
`2.
`“central database” ...................................................................................... 4
`3.
`“web page”.................................................................................................. 4
`4.
`“web server”................................................................................................ 5
`5.
`“communications control module”.............................................................. 5
`6.
`“synchronized”............................................................................................ 6
`7.
`“hospitality applications” ........................................................................... 6
`8.
`“application program interface”................................................................. 7
`9.
`“outside applications”................................................................................. 7
`10. “integration” ............................................................................................... 7
`11. “single point of entry for all hospitality applications”................................ 7
`12. “automatic” ................................................................................................. 8
`13. “Wherein the communications control module is an interface between the
`hospitality applications and any other communications protocol”...................... 9
`IV. THERE HAS BEEN NO SHOWING OF OBVIOUSNESS...................... 12
`A. DeLorme Does Not Disclose Claim 12 First Wherein Clause ..................... 13
`B. DeLorme Does Not Disclose Claim 12 Element “b”.................................... 27
`C. DeLorme Does Not Disclose The Claimed “Application Program Interface”
`That “Enables Integration of Outside Applications with the Hospitality
`Applications”...................................................................................................... 40
`D. DeLorme Does Not Disclose The Claimed “Communications Control
`Module” Nor ‘Wherein The Communications Control Module Is An Interface
`Between The Hospitality Applications And Any Other Communications
`Protocol”……..................................................................................................... 42
`E. Claim As A Whole ……............................................................................... 45
`F. Dependent Claims ......................................................................................... 46
`G. Objective Evidence Of Non-Obviousness.…… ........................................... 50
`
`-i-
`
`

`
`CBM2015-00080
`
`1. There is a very strong nexus between the evidence of “secondary
`considerations” and the challenged claims ………………………………53
`2. The Ameranth patents in this family, including the challenged claims, have
`been successfully and extensively licensed…………………………………….63
`3. Ameranth's products enjoyed substantial, widespread commercial success.65
`4. Ameranth's 21st Century Restaurant received numerous technology awards
`and industry acclaim after its introduction. ........................................................ 68
`5. Ameranth received overwhelming industry praise for the 21st Century
`Restaurant technology. ....................................................................................... 70
`6. Starbucks and numerous other companies copied the Ameranth technology
`reflected in the challenged claims. ..................................................................... 72
`7. Other companies in the industry tried and failed to develop the integrated,
`synchronized innovation of the Ameranth technology and patent claims.......... 78
`8. Objective Evidence Conclusion................................................................... 80
`V. CONCLUSION................................................................................................ 80
`
`-ii-
`
`

`
`TABLE OF AUTHORITIES
`
`CBM2015-00080
`
`Page
`
`Cases
`
`Allen Archery, Inc. v. Browning Mfg. Co.,
`819 F.2d 1087 (Fed. Cir. 1987)........................................................................... 70
`
`Ameranth v. Pizza Hut et al.,
`Case No. 3-11-cv-01810 (S.D. Cal. 2013), Dkt. No. 27 at p. 3........................... 55
`
`Berk-Tek LLC. v. Belden Techs., Inc.,
`IPR2013-00059, FWD 34 (PTAB April 28, 2014) ............................................. 22
`
`Gambro Lundia AB v. Baxter Healthcare Corp.,
`110 F.3d 1573 (Fed. Cir. 1997) ........................................................................ 54, 70
`
`CFMT, Inc. v. Yieldup Int’l. Corp.,
`349 F.3d 1333 (Fed. Cir. 2003)....................................................................... 16
`
`Crocs, Inc. v. ITC,
`598 F.3d 1294 (Fed. Cir. 2010)........................................................................... 73
`
`Dynamic Drinkware, LLC v. National Graphics, Inc.,
`800 F.3d 1375 (Fed. Cir. 2015)........................................................................... 22
`
`Eli Lilly & Co. v. Zenith Goldline Pharmaceuticals, Inc.,
`471 F.3d 1369 (Fed. Cir. 2006)........................................................................... 68
`
`Free Motion Fitness, Inc. v. Cybex Int’l, Inc.,
`423 F.3d 1343 (Fed. Cir. 2005)).......................................................................... 47
`
`Grain Processing Corp. v. Am. Maize-Products Co.,
`840 F.2d 902 (Fed. Cir. 1988)............................................................................. 33
`
`-iii-
`
`

`
`CBM2015-00080
`
`Heidelberger v. Hantscho Prods.,
`21 F.3d 1068 (Fed. Cir. 1994)............................................................................. 73
`
`HIMPP v. Hear-Wear Techs., LLC,
`751 F.3d 1362 (Fed. Cir. 2014)........................................................................... 23
`
`In re GPAC Inc.,
`57 F.3d 1573 (Fed. Cir. 1995)....................................................................... 54, 65
`
`In re Roufett,
`149 F.3d 1350 (Fed. Cir. 1998)........................................................................... 64
`
`In re Warner,
`379 F.2d 1011 (CCPA 1967)............................................................................... 16
`
`In re Wesslau, 147 USPQ 391,393 (CCPA 1965)………………………………...26
`
`Kurtz v. Belle Hat Lining Co., Inc.,
`280 F. 277, 281 (2nd Cir. 1922) ........................................................................... 72
`
`Microsoft Corp. v. Proxyconn, Inc.,
`789 F.3d 1292, 1298 (Fed. Cir. 2015) ...................................................................... 3
`
`Power Integrations, Inc. v. Fairchild Semiconductor Int’l, Inc.,
`711 F.3d 1348, 1368 (Fed. Cir. 2013) .................................................................... 56
`
`Power-One v. Artesyn Techs, Inc.,
`599 F.3d 1343, 1352 (Fed. Cir. 2010) .................................................................... 70
`
`Rambus Inc. v. Rea,
`731 F.3d 1248, 1256 (Fed. Cir. 2013) .............................................................. 51, 70
`
`Teva Pharm., Inc. v. Sandoz, Inc.,
`723 F.3d 1363, 1372 (Fed. Cir. 2013) .................................................................... 53
`
`-iv-
`
`

`
`CBM2015-00080
`
`Unique Concepts, Inc. v. Brown,
`939 F.2d 1558, 1563 (Fed. Cir. 1991) .................................................................... 25
`
`Vandenberg v. Dairy Equip. Co., a Div. of DEC Int’l, Inc.,
`740 F.2d 1560, 1567 (Fed. Cir. 1984) .................................................................... 77
`
`Statutes
`§101........................................................................................................................ 22
`35 U.S.C. §316(e)................................................................................................... 34
`35 U.S.C. §103 ............................................................................................. 19,26,80
`
`Rules
`37 C.F.R. §42.207(a) ................................................................................................ 1
`
`-v-
`
`

`
`CBM2015-00080
`
`PATENT OWNER’S LIST OF EXHIBITS
`
`Exhibit No.
`
`Description
`
`2001
`
`2002
`
`2003
`
`2004
`
`2005
`
`2006
`
`2007
`
`Food.com Internal Memorandum, “Ameranth Licensing
`Contract,” Sept. 13, 1999
`
`iOS Simulator User Guide, March 9, 2015
`
`Ameranth/Par Technology Corp. License
`Announcement, Jan. 28, 2013
`
`http://blogs.wsj.com/digits/2014/04/02/apples-jobs-
`declared-holy-war-on-google-over-android/, discussing
`Apple 2010 emails made public in Apple v. Samsung
`Litigation
`
`The House that Tech Builds,
`http://hospitalitytechnology.edgl.com/news/the-house-
`thattech-builds99460?referaltype=newsletter, Hyatt CTO
`Interview, April 8. 2015
`
`Domino’s Press Release,
`http://www.prnewswire.com/news-releases/dominos-
`pizza-first-in-industry-to-offer-mobile-
`ordering58317297.
`html, Sept. 27, 2007
`
`“Domino's app let's you voice-order pizza,”
`http://www.usatoday.com/story/money/business/2014/06
`/16/dominos-voice-ordering-app-nuancefast-
`food-restaurants/10626419/, June 16, 2014
`
`-vi-
`
`

`
`2008
`
`2009
`
`2010
`
`2011
`
`2012
`
`2013
`
`2014
`
`2015
`
`2016
`
`2017
`
`2018
`
`CBM2015-00080
`
`“Starbucks to roll out innovations in mobile platform--
`Company says new mobile features could be ‘holy grail’
`of throughput,” http://nrn.com/quick-service/starbucks-
`roll-out-innovations-mobile-platform, March 13, 2014
`
`“Starbucks’ mobile order and pay sees hot start, aided by
`Integration,” www.mobilecommercedaily.com, April 27,
`2015
`
`“Agilysys Introduces InfoGenesis Roam Mobile
`Software,” June 21, 2011
`
`Ex parte McNally, Appeal No. 2012-001503 (PTAB
`Nov. 4, 2014)
`
`Decision in Appeal No. 2010-000055 (BPAI March 3,
`2011)
`
`Decision in Appeal No. 2009-011707 (BPAI Feb. 14,
`2011)
`
`Decision in Appeal No. 2009-008033 (BPAI Jan. 28,
`2011)
`
`Excerpts from Microsoft Computer Dictionary (4th ed.
`1999)
`
`“The Computerworld Honors Program--Case Study,”
`Award to Marriott International, Inc. (2006)
`
`Decision in BPAI Appeal No. 2011-004999 (PTAB Oct.
`17, 2013 )
`
`Transcript of FS/TEC Awards Presentation (Feb. 2009)
`
`-vii-
`
`

`
`2019
`
`2020
`
`2021
`
`2022
`
`2023
`
`2024
`
`2025
`
`2026
`
`2027
`
`2028
`
`2029
`
`2030
`
`2031
`
`2032
`
`2033
`
`2034
`
`CBM2015-00080
`
`Declaration of Dr. Alfred Weaver
`
`Microsoft Computer Dictionary (4th ed.) excerpts
`
`May 1999 announcement from National Restaurant
`Association (NRA) show in Chicago, IL.
`Excerpts from transcript of Deposition of John Harker,
`May 3, 2010
`May 14, 2012 press release re Skywire
`
`Ameranth 21st Century System Product Brochure (two-
`sided), distributed May 1999 (original and annotated)
`
`Press releases and announcements of various Ameranth
`patent licenses and alliances
`
`Hospitality Technology, "POS Scoreboard", 2004 and
`2006
`
`Microsoft RAD Award, 2003.
`
`Excerpts from book, "Market Busters"
`
`"Best New Products", QSR magazine, September 1999
`
`Email messages between Microsoft and Starbucks
`personnel, 2006-2007
`Scott Maw remarks, Nov. 18, 2015 Starbucks investor
`conference
`
`May 2006 Ameranth presentation to Pizza Hut
`
`Transcript of Micros remarks, 2008 FSTEC meeting
`
`Micros announcement of Simphony product
`
`-viii-
`
`

`
`2035
`
`2036
`
`2037
`
`2038
`
`2039
`
`2040
`
`2041
`
`2042
`
`2043
`
`2044
`
`2045
`
`2046
`
`2047
`
`2048
`
`2049
`
`2050
`
`2051
`
`CBM2015-00080
`
`Transcript of Paul Armstrong remarks, 2008 FSTEC
`meeting
`Micros HSI press releases
`
`Micros JTECH press release
`
`Micros mycentral/Simphony press release
`
`Mark Nance PowerPoint presentation, 2009 FS/TEC
`meeting
`
`NCR/Radiant press release, July 2011
`
`PAR Technology acquires PixelPoint, article, August
`2005
`
`Dominos AnyWare announcement, August 2015
`
`Agilysys/InfoGenesis Mobile brochure
`
`"Wireless finds a welcome in hospitality," Bloomberg,
`Feb. 2004
`Mobile Commerce Daily article re Agilysys InfoGenesis,
`May 2015
`Agilysys/InfoGenesis press release, June 2012
`
`Agilysys Announces Availability of InfoGenesis™
`Mobile v2.0, Sept. 2013
`Xpient acquires Progressive, press release, August 2004
`
`Radiant Systems acquires Aloha Technologies, press
`release, Dec. 2003
`Case Study, Ameranth/Improv Comedy Clubs, Spring
`2000 (annotated)
`Computerworld Award summary, 2001 (annotated)
`
`-ix-
`
`

`
`CBM2015-00080
`
`2052
`
`2053
`
`2054
`
`2055
`
`2056
`
`Photograph from 1999 NRA meeting in Chicago, IL,
`including Keith McNally and Graham Granger
`Dunkin’ Donuts Selects CARDFREE as its Mobile
`Platform, Business Wire, Dec. 2015.
`
`Transcript of remarks from 2009 FSTEC meeting,
`Technology Executives Panel
`
`PowerPoint slides and screen shots from Ameranth
`presentation to Starbucks, December 1, 2006
`
`"Starbucks Claims 90 Percent Mobile Payments Market
`Share", PYMTS, Oct. 31, 2014.
`
`-x-
`
`

`
`CBM2015-00080
`
`I.
`
`STATEMENT OF PRECISE RELIEF REQUESTED
`
`In accordance with 37 C.F.R. §42.207(a), Patent Owner, Ameranth,
`
`Inc., (“PO”) submits this Response to the CBM review Petition (“Pet.”)
`
`against U.S. Patent No. 6,384,850 ("the '850 patent"). For the reasons below,
`
`the Petition should be denied.2
`
`II.
`
`INTRODUCTION
`
`The only issue remaining for the Board to resolve is whether Petitioner met
`
`its burden to prove that a POSA at the time of the invention would have found the
`
`challenged ‘850 claims to be obvious based only on the DeLorme reference.
`
`However, two facts are indisputable. First, the DeLorme inventors did not conceive
`
`or possess Ameranth’s inventions. Petitioner does not dispute this reality,
`
`otherwise it would have argued anticipation based on DeLorme and, as confirmed
`
`by the Board, Petitioner admitted that DeLorme did not disclose the claimed
`
`2 Petitioner’s standing argument merely references CBM2014-00016, and is thus
`
`insufficient. PO submits that Petitioner was required to provide, in the Petition, the
`
`basis for standing. Further, if the Federal Circuit rules that the `850 patent in CBM
`
`2014-00015 is not a CBM patent and that institution was improper, having relied
`
`on that institution for this CBM dooms the current petition as well. Patent Owner
`
`incorporates herein its Preliminary Response arguments regarding standing and
`
`preserves its right to appeal the Board’s determination thereof.
`
`-1-
`
`

`
`CBM2015-00080
`
`communications control module (“CCM”).3 Further, due to the challenge being
`
`based on this single reference, it is indisputable that the DeLorme inventors, who
`
`were clearly POSA and who clearly had access to their own patent, did not find
`
`Ameranth’s inventions to be obvious, otherwise they would have themselves
`
`“conceived” it and included it in their specification to solve their stated problem.
`
`But they did not.
`
`The “system of systems” concept of the ‘850 patent, as reflected in the
`
`“synchronous communication system” claims, was designed for smooth
`
`growth/changes for multiple and ever-varying communications. Delorme’s limited
`
`concept was not. Delorme admitted that his “preferred embodiment” relied on
`
`“tangible media,” e.g. CDs, which were clearly distributed by hand, not computer
`
`system or network:
`
`Thus, the preferred TRIPS embodiment, shown in use in FIG.
`lA, comes partly on tangible media, for example, as a North
`American Atlas on CD-ROM with a TRIPS "starter" kit.
`Exh. 1024 14:19-21 (emphasis added). DeLorme also only described various
`
`3 “Petitioner argues that DeLorme discloses the claimed system except that
`
`DeLorme does not disclose explicitly that the communication control module is
`
`configured as an interface between the hospitality applications and any other
`
`communications protocol.” Inst. Dec. 20 (emphasis added).
`
`-2-
`
`

`
`CBM2015-00080
`
`independent “alternative” embodiments:
`
`Alternatively, all TRIPS function, data and service can be provided
`entirely online (i.e. without significant standalone software
`components)—for example, from a central TRIPS service bureau, or
`by means of a TRIPS Internet World Wide Web Site.
`FIG. 9 also depicts alternative TRIPS embodiments and remote
`usage scenarios which facilitate "on the spot" simplified travel
`planning and transactions, via WCU 907 from remote locations
`Exh. 1024 43-47, 72:37-43 (emphasis added); see also Exh. 1002 ¶¶ 210-12.
`
`Further, in addition to the technical infirmities of the DeLorme disclosure
`
`vis-à-vis the claimed subject matter, a large quantity of objective evidence
`
`demonstrates nonobviousness.
`
`III. CLAIM CONSTRUCTION
`
`A BRI construction cannot read elements out of the claims and cannot be
`
`inconsistent with the intrinsic evidence. Microsoft Corp.v. Proxyconn, Inc., 789
`
`F.3d 1292, 1298 (Fed. Cir. 2015).
`
`Patent Owner presents the following proposals, all of which are supported
`
`by the intrinsic evidence. The Declaration of Dr. Alfred Weaver (Exh. 2019) in
`
`support of Ameranth’s positions on nonobviousness is critical in the claim
`
`construction analysis because it provides the perspective of a POSA in viewing the
`
`claims in light of his own knowledge and the specification disclosure. Per Dr.
`
`Weaver, a POSA would have had a Bachelor’s degree in either electrical
`
`-3-
`
`

`
`CBM2015-00080
`
`engineering or computer science and at least three years of experience in the
`
`hospitality market in the fields of developing software for wireless networks and
`
`devices, developing Internet-based systems or applications, with knowledge of or
`
`equivalent experience in software development in the hospitality market for at least
`
`three years. (Exh. 2019 ¶21).
`
`“wireless handheld computing device”
`1.
`Patent Owner proposes “a wireless computing device that is sized to be held
`
`in one’s hand.” See Everingham Order (Exh. 1032 at 24); Exh. 2019 ¶27.
`
`“central database”
`2.
`Patent Owner proposes “a database file structure connected to the system in
`
`association with a central server, comprised of records, each containing fields,
`
`together with a set of operations for searching, sorting, recombining and other
`
`functions.” Microsoft Comp. Dict. (4th ed.1999) (Exh. 1034 at 8); Exh. 1001 at
`
`2:24, 11-34-35 (“backoffice server (central database)”); id. at 2:8-10, 11:13-15
`
`(“synchronization between a central database and multiple handheld devices”).
`
`(Exh. 2019 ¶28).
`
`“web page”
`3.
`The PTAB construed consistent with its prior rulings to mean “a document,
`
`with associated files for graphics, scripts, and other resources, accessible over the
`
`internet and viewable in a web browser.” Inst. Dec. 7; see also CBM2014-00015
`
`(Exh. 1017 thereto at 8). (Exh. 2019 ¶29).
`
`-4-
`
`

`
`CBM2015-00080
`
`The PTAB separately construed the non-recited term “document” in accord-
`
`ance with Petitioner’s request. Patent Owner objects to that construction because it
`
`is not a term in the claims. Further, not only is Petitioner’s proposal not a BRI for
`
`this term, the proposed construction is inconsistent with the web context and the
`
`specification (Exh. 1001 12:20-24) and is thus inconsistent with how a POSA
`
`would view “web based” documents served via the claimed “web server.” (Exh.
`
`2019 ¶29).
`
`“web server”
`4.
`The Microsoft Computer Dictionary states: “Web Server:” “See HTTP
`
`Server.” (Exh. 2020 (Page 479)). The Dictionary then states in regard to “HTTP
`
`Server:” “Server software that uses HTTP to serve up HTML documents and any
`
`associated files and scripts when requested by a client such as a web browser.”
`
`(Exh. 2020 (Page 224)). Patent Owner proposes that this definition be adopted.
`
`Web Server is a recited element, its critical functionality in the claims has not been
`
`appreciated by the Petitioner or the Board, and DeLorme suffers critical infirmities
`
`in meeting this limitation as properly construed and relative to the CCM and the
`
`third wherein clause of claim 12, as discussed below. (Exh. 2019 ¶30).
`
`5.
`
`“communications control module”
`
`This is a software layer, as Judge Payne concluded in prior district court
`
`litigation stating that “the specification itself provides the best construction for the
`
`term at issue.” (Exh. 1033 at 13). Based on the District Court constructions and
`
`-5-
`
`

`
`CBM2015-00080
`
`intrinsic evidence, Patent Owner proposes the following construction for the CCM:
`
`a layer that sits on top of any communication protocol and acts as an
`interface between hospitality applications and the communication
`protocol.
`
`See Exh. 1001 4:9-13. Further, it is clear that the software-based CCM provides the
`
`“automatic” communications “routing” functionality as shown by the specification,
`
`e.g., “[a]communication control program monitors and routes all communications
`
`to the appropriate devices,” which “must be running for proper communications
`
`to exist between all devices on the network.” (Exh. 1001 9: 21-22, 38-39
`
`(emphasis added)). It is also the CCM that deals concurrently with both HTTP and
`
`non-HTTP communications messaging protocols of the system, and also supports
`
`the integration of the separately recited API (which then also deals with software
`
`application-to-application direct integration and with third party systems/devices
`
`such as POS systems, as discussed further below). (Exh. 2019 ¶31).
`
`6.
`
`“synchronized”
`
`The Board correctly construed this term to mean “made, or configured to
`
`make, consistent.” Inst. Dec. 9; Exh. 2019 ¶32.
`
`7.
`
`“hospitality applications”
`
`The Board correctly construed this term to mean “applications used to
`
`perform services or tasks in the hospitality industry.” This is consistent with the
`
`specification which states “hospitality applications, e.g., reservations, frequent
`
`-6-
`
`

`
`CBM2015-00080
`
`customer ticketing, wait lists, etc.” Exh. 1001 4:6–7; Inst. Dec. 9; Exh. 2019 ¶33.
`
`8.
`
`“application program interface”
`
`The recited API is not a generic API divorced from the definition of its
`
`function within ‘850 claim 12. (Exh. 2019 ¶34). See also the discussion of the
`
`proposed construction of “integration” below.
`
`9.
`
`“outside applications”
`
`The Board construed “outside applications” to mean “third party
`
`applications, such as point of sale companies, affinity program companies, and
`
`internet content providers.” Inst. Dec. 10; Exh. 2019 ¶35.
`
`10.
`
`“integration”
`
`The Board construed “integration” to mean “combining of different
`
`activities, programs, or hardware components into a functional unit.” Inst. Dec. 11.
`
`This term and construction also must be considered in relation to the “CCM” and
`
`“outside applications” terms as well. (Exh. 2019 ¶36).
`
`11.
`
`“single point of entry for all hospitality applications”
`
`The proper construction for this limitation leverages Judge Payne’s focused
`
`construction as to “single point of entry” itself, but the complete element needs to
`
`be considered as a whole to be consistent with the entirety of claim 13 (as well as
`
`the specification description directly related to this element). Judge Payne
`
`construed “a single point of entry” as “a center of communication.” (Exh. 1033 at
`
`-7-
`
`

`
`CBM2015-00080
`
`18).7 Patent Owner submits that this is the proper BRI construction but that the full
`
`term in which it appears, as the core aspect of claim 13, should be construed as “a
`
`center of communication for all hospitality applications.” (Exh. 2019 ¶37).
`
`12.
`
`“automatic”
`
`As detailed in Dr. Weavers report, automatic functionality is a key inventive
`
`concept of the patents and, as explained above relative to the CCM and the
`
`specification at col 9, it is the CCM which must be running that provides the
`
`“automatic,” i.e., routing functionality. Further, the specification clearly defines
`
`that “[n]o user action is needed during operation of the software once the
`
`application is launched.” (Exh. 10019:27-29 (emphasis added)). “Automatic” is
`
`“without user action” and thus means “done or produced as if by machine.” (Exh.
`
`2019 ¶38). “No user action” is terminology used in the specification and is
`
`consistent with the ordinary and customary definition of “automatic” established
`
`by the BPAI/PTAB. See BPAI Appeal No. 2010-000055 at 5 (Exh. 2012) (relying
`
`on Merriam Webster Collegiate Dictionary (http://www.merriam-
`
`webster.com/dictionary/automatic).
`
`7 “The communication module also provides a single point of entry for all
`
`hospitality applications, e.g., reservations, frequent customer[,] ticketing, wait
`
`lists, etc. to communicate with one another wirelessly and over the Web. (Exh.
`
`1001 4:5-8) (emphasis added).
`
`-8-
`
`

`
`CBM2015-00080
`
`13.
`
`“Wherein the communications control module is an interface
`between the hospitality applications and any other
`communications protocol”
`
`In addition to correctly construing CCM standing alone as discussed above,
`
`this wherein clause must be separately considered and construed as part of this
`
`broader claim element itself as well as in the context of “integration” and “outside
`
`applications,” and the claim as a whole. (Exh. 2019 ¶39).
`
`The Board’s initial determination in CBM2015-00099 that neither the claims
`
`nor the specification “require more than [] web based communications protocols”
`
`(CBM2015-00099, Inst. Dec. 35) and that “the only specific protocol discussed in
`
`the specification is HTTP” (Id. at 32) was erroneous and ignores that the system as
`
`claimed “integrates” with, e.g., POS system devices and accommodates and adapts
`
`to new protocols without the necessity to change the underlying/core hospitality
`
`applications, a concept not taught by Delorme as discussed below. For example,
`
`the claims and specification refer to “integration” with “outside applications,” i.e.,
`
`third party systems such as POS system devices (clearly which operate with
`
`different protocols). (Exh. 2019 ¶40). The specification states:
`
`A simple point to point wireless capability is contemplated which
`permits simple digital messages to be sent from the wireless
`handheld devices ... to a receiver in a beeper and/or valet parking
`base-station. … A simple protocol is used to acknowledge receipt of
`the message and thus simultaneous communication is not necessary,
`
`-9-
`
`

`
`CBM2015-00080
`
`which reduces the cost of the wireless link
`Exh. 1001 11:49-57 (emphasis added). It is readily apparent that this passage
`
`refers to an exemplary simple digital messaging “wireless” (i.e., non-HTTP)
`
`protocol for, e.g., interfacing with pagers and beepers, just as a communication
`
`with a third party POS system might involve a different protocol. The claimed
`
`CCM as described by the specification accommodates and routes messages to such
`
`systems/devices when appropriate, which a system relying only on web/browser-
`
`based protocols could not do. (Exh. 2019 ¶40). This is consistent with the
`
`specification requirement that the CCM must be capable of concurrent
`
`communications via both HTTP and non-HTTP protocols while monitoring and
`
`routing messages operating under different protocols to the appropriate
`
`devices/components as recited in the claims.8 (Exh. 2019 ¶41).
`
`The Board declined to construe CCM or this wherein clause and failed to
`
`appreciate the claimed functionality as required by the specification disclosure and
`
`the explicit claim structure, as exemplified by the Board’s incorrect conclusion in
`
`CBM2015-00099 that only “HTTP” protocols are disclosed by the specification .
`
`Patent Owner proposes that this wherein clause be construed as “a server-
`
`8 Similarly, dependent claim 15 of the `325 patent recites a “wireless paging
`
`device,” which operates under a non-HTTP protocol, further reinforcing that the
`
`CCM must have functionality to interface to multiple protocols.
`
`-10-
`
`

`
`CBM2015-00080
`
`side software layer that provides an interface between the hospitality applications
`
`and communication protocols and which monitors and routes communications
`
`between different devices while concurrently using different protocols.” (Exh.
`
`2019 ¶42). This construction is compelled by the specification, which clearly
`
`discloses at least two different protocols:
`
`The communication module also provides a single point of entry for
`all hospitality applications, e.g., reservations, frequent customer
`ticketing, wait lists, etc. to communicate with one another wirelessly
`and over the Web.
`Exh. 1001 4:5-11.
`
`A communications control program monitors and routes all
`communications to the appropriate devices. It continuously monitors
`the wireless network access point and all other devices connected to
`the network such as pagers, remote devices, internet Web links and
`POS software. Any message received is decoded by the software, and
`then routed to the appropriate device.
`Exh. 1001 9:21-27. The CCM as part of the claimed system as a whole thus
`
`provides a functionally independent layer interface for and between the hospitality
`
`applications on different devices/clients while concurrently using different
`
`protocols including both HTTP and non-HTTP protocols. (Exh. 2019 ¶42).
`
`Moreover, Petitioner should not be heard to object to Patent Owner’s
`
`proposed construction for this wherein clause because its expert (Exh. 1002 ¶51)
`
`has already substantively agreed that the specification compels PO’s proposal.
`
`-11-
`
`

`
`CBM2015-00080
`
`IV.
`
`THERE HAS BEEN NO SHOWING OF OBVIOUSNESS
`
`In addition to admitting that DeLorme did not disclose the claimed
`
`CCM, Petitioner entirely missed both the overall “synchronization” of the
`
`claims as a whole, i.e., they include “applications and data” being
`
`synchronized, and the full “integration” of “third party applications” with
`
`“hospitality applications,” which are separately recited in the claims.
`
`Exemplary of Petitioner’s mistakes, Petitioner’s expert Turnbull
`
`mischaracterized the “synchronization” element as:
`
`[D]ata are synchronized between the central database, the at least one
`wireless handheld computing device, at least one Web server and at
`least one Web page … I have considered interpretation of this phrase
`as used in the ’850 and ’325 patents. From my review, I believe that
`the phrase is incongruent with how a POSITA would describe any
`similar application functionality.
`Exh. 1002 ¶81 (emphasis added). However, that statement completely read
`
`“applications and” out of the element (immediately preceding “data”), and in so
`
`doing parsed out the inventive idea which the Board itself recognized was critical
`
`to the patentability of these claims, as detailed above and below. These and other
`
`errors in the Petition and the Board’s conclusions based thereon, and the infirmities
`
`of DeLorme vis-à-vis the actual claimed subject matter, compel a conclusion of
`
`nonobviousness of all challenged claims on multiple independent bases. (See Exh.
`
`2019 ¶¶53-55).
`
`-12-
`
`

`
`CBM2015-00080
`
`A.
`
`DeLorme Does Not Disclose Claim 12 First Wherein Clause
`
`The correct reading of this wherein clause pursuant to the Board’s
`
`construction of “synchronized” is: “Both applications and data are made or
`
`configured to make consistent between the central database, a wireless handheld
`
`computing device, a web server and a web page.” DeLorme does not disclose
`
`this element. There is no teaching or suggestion in DeLorme of making
`
`applications consistent between a wireless handheld computing device and
`
`any of the other components of this limitation. This is not surprising
`
`considering that DeLorme does not even disclose the storage of any hospi-
`
`tality application on the WCU, as discussed further below. (Exh. 2019 ¶57).
`
`In a prior case, the Board fully appreciated that both data and
`
`applications are synchronized per these claims, and that the recited
`
`combination of elements interact in a specific way to synchronize both
`
`applications and data:
`
`The combination of these components interact in a specific way
`to synchronize applications and data between the components
`and outside application that is integral to the claimed invention
`and meaningfully limit these claims.
`CBM2014-00015, Inst. Dec. 24 (emphasis added); See Exh. 2019 ¶58.
`
`Strikingly, and notwithstanding the clear claim language and the
`
`Board’s prior characterization of the claimed subject matter, Petitioner’s
`
`-13-
`
`

`
`CBM2015-00080
`
`expert Turn

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