`
`
`
`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 CBM CBM2015-000801
`Patent 6,384,850
`
`
`
`PETITIONER’S REPLY BRIEF
`
`
`
`
`1 CBM2015-00096 has been consolidated with this proceeding.
`
`WEST\268720567.1
`
`
`1
`
`
`
`I.
`
`
`INTRODUCTION
`
`Patent Owner Ameranth’s (“PO”) arguments in its Corrected Patent Owner
`
`Response (“POR”) all fail. DeLorme’s system synchronizes applications and data
`
`by sharing data between applications; its WCU is a handheld device that inherently
`
`stores hospitality applications and data; its Interface & Interaction Bus includes
`
`software and is a communications control module that routes communications to a
`
`WCU and an internet-only desktop PC embodiment in the same system; and its
`
`hospitality applications are integrated via an API with outside applications. PO’s
`
`evidence of secondary considerations is defective for lack of nexus and other
`
`reasons, and fails to overcome the showing of obviousness over DeLorme.
`
`II. ARGUMENT
`A.
`PO Has Waived Any Standing Argument
`Contrary to the assertion in the POR at 1 n.2, the Petition does not “merely”
`
`reference CBM2014-00016, but rather includes a detailed showing of standing
`
`spanning more than three pages. Pet. at 5-8. In contrast, PO’s attempt to
`
`incorporate its argument from its Preliminary Response violates Board rules (37
`
`C.F.R. § 42.6(a)(3)) and thus constitutes a waiver (Paper No. 14 at 3).
`
`B. DeLorme Discloses “wherein the applications and data are
`synchronized between” the four claimed entities
`
`PO’s primary argument is that the Petition fails to show that DeLorme
`
`discloses “wherein the applications and data are synchronized between the central
`
`WEST\268081547.1
`
`1
`
`
`
`database, at least one wireless handheld computing device, at least one web server
`
`and at least one web page”2 (the “Synchronization Clause”) as recited in claim 12.
`
`POR at 13. The Petition established that Synchronization Clause should be
`
`construed to mean that “the same data is present on each of the central database, at
`
`least one wireless handheld computing device, at least one web server and at least
`
`one web page at the same time.” Pet. at 23. This construction was supported by the
`
`declaration of Dr. Turnbull, who explained that a POSITA would understand
`
`synchronization of data and applications among the four claimed entities as
`
`requiring the sharing of data between those four entities. Ex. 1002 ¶¶ 81-83.
`
`Consistent with this construction, the Petition establishes that DeLorme discloses
`
`such sharing of data between the four claimed entities. Pet. at 56-57.
`
`In its POR, PO does not dispute Petitioner’s showing that DeLorme
`
`discloses synchronizing data among the four entities recited in the Synchronization
`
`Clause. PO has thus waived any such argument.3 Rather, PO appears to argue that
`
`applications cannot be synchronized by synchronizing the data used by those
`
`applications. See, e.g., POR at 14 n.9 (“one of the fundamental aspects of the
`
`claims, i.e., that both the ‘applications’ and the ‘data’ are synchronized, not merely
`
`2 Unless otherwise indicated, all emphases herein were added by Petitioner.
`
`3 Paper No. 14 (Scheduling Order) at 3 (“The patent owner is cautioned that any
`
`arguments for patentability not raised in the response will be deemed waived.”).
`
`WEST\268081547.1
`
`2
`
`
`
`the ‘data’”; emphasis in original). PO is clearly wrong. Claim 16 establishes that
`
`one way in which applications can be synchronized is by sharing data among
`
`them. Claim 16, which depends from claim 12, recites:
`
`16. The information management and synchronous communications
`system of claim 12 wherein the applications and data are
`synchronized by digital data transmission between the central
`database, at least one wireless handheld computing device, at least one
`Web Server and at least one Web page.
`
`Ex. 1001 at 16:42-47. Because claim 16 is a species of the Synchronization Clause
`
`genus of claim 12, nothing more than digital data transmission is required to
`
`synchronize applications.
`
`Synchronizing applications and data through the transmission of only data as
`
`recited in claim 16 is consistent with the teachings of the ’850 patent. The ’850
`
`patent lacks any disclosure of synchronizing applications in any other manner.
`
`Instead, the ’850 patent teaches that sharing data among applications stored on the
`
`four claimed entities is the way in which the applications are synchronized:
`
`The synchronous communications control module ... provides a
`single point of entry for all hospitality applications to communicate
`with one another wirelessly or over the Web ... The single point of
`entry works to keep all wireless handheld devices and linked Web
`sites in synch with the backoffice server (central database) so that
`the different components are in equilibrium at any given time and an
`overall consistency is achieved. For example, a reservation made
`
`WEST\268081547.1
`
`3
`
`
`
`online is automatically communicated to the backoffice server which
`then synchronizes with all the wireless handheld devices wirelessly.
`Similarly, changes made on any of the wireless handheld devices will
`be reflected instantaneously on the backoffice server and the other
`handheld devices. Ex. 1001 at 11:24-42.
`
`Nothing in this passage discusses the transmission of anything other than data to
`
`keep the applications in the central database in sync with those on the wireless
`
`handheld devices and web pages. Ex. 1070 ¶¶ 5-11; see also ¶¶ 12-17.
`
`
`
`While PO repeatedly criticizes the Petition and Dr. Turnbull for allegedly
`
`“reading out” the requirement to synchronize applications, it is telling that the POR
`
`does not articulate exactly what is required to synchronize an application. The
`
`closest the POR comes is providing an “example” of application synchronization:
`
`Data is communicated from both sides (client and server), but
`software/ applications are not synchronized between the server and
`WCU client. Thus, for example, the updating of a restaurant menu to
`achieve “consistency” between the wireless handheld device of claim
`element “b” and the central database so that the updated menu is
`synchronized with the central database and then “stored” as part of
`the hospitality application on the handheld to facilitate future
`ordering, was not taught by DeLorme, nor possible with the DeLorme
`WCU. There is no mention in DeLorme of synchronizing application
`software between server side and client side.
`
`POR at 18. PO appears to contend that sending menu data from the central
`
`database and storing it on the wireless device as part of the hospitality application
`
`WEST\268081547.1
`
`4
`
`
`
`is how an application can be synchronized. But PO admits that this method is just
`
`an example, and this example does not preclude other ways of synchronizing
`
`applications. In this regard, the Board previously held the claims are not limited to
`
`a wireless device with a locally stored database, but also encompass wireless
`
`devices without a locally stored database. Ex. 1068 at 18-19. Moreover, the patent
`
`does not disclose storing menu data or a menu database as part of an application
`
`program (POR at 18), or any way of synchronizing applications other than through
`
`transmission of data. Thus, nothing in the specification precludes synchronizing
`
`both data and applications by transmitting only data as recited in claim 16.
`
`Furthermore, Ameranth’s expert Dr. Weaver admitted that applications can
`
`be synchronized by sending updated data to a wireless device. Ex. 1076 at 149:12-
`
`16. Dr. Weaver further conceded that DeLorme discloses exactly that. Id. at
`
`150:10-21. While Dr. Weaver later testified that applications could only be
`
`synchronized by checking whether the software on each of the claimed entities was
`
`the same version, and if not, transmitting updated software code (id. at 153:3-19),
`
`Dr. Weaver conceded that the patent does not describe checking software versions
`
`or the transmission of updated software code. Id. at 154:9-155:4.
`
`PO’s argument regarding the Synchronization Clause fails for a second
`
`reason. This limitation simply requires that “applications and data are
`
`synchronized.” It does not require any application on any of the four claimed
`
`WEST\268081547.1
`
`5
`
`
`
`entities to be “updated,” or to be configured to perform updates or any other type
`
`of synchronization. Under the BRI, all that is required by the claim is that the
`
`applications on the four entities be synchronized. Thus, DeLorme’s disclosure of
`
`the TRIPS system wherein updated data is available to each of the four recited
`
`entities is a disclosure of a system in which the applications on those entities are
`
`synchronized to the full extent required by claim 12.
`
`C. DeLorme’s WCU Is a Handheld Device
`PO argues that DeLorme’s WCU is not a “wireless handheld device”
`
`because DeLorme’s WCU needs to be held with both hands. POR at 27-28 and n.9.
`
`This argument relies on PO’s unsupported construction of handheld that is limited
`
`to holding with a single hand. However, the plain meaning of handheld is not so
`
`limited. Ex. 1069 (“handheld: compact enough to be used or operated while being
`
`held in the hand or hands”). Even under PO’s construction, DeLorme’s WCU
`
`qualifies as handheld. DeLorme explicitly discloses that WCU devices 907 “are
`
`typically handheld.” Ex. 1024 at 71:67-72:2 (cited in Pet. at 53). DeLorme further
`
`discloses that the WCU functions can be performed, among other things, by a PDA
`
`or a “smart” phone (Id. at 75:38-45), both of which are devices that can be held
`
`with a single hand. Ex. 1070, ¶¶ 20-21; Ex. 1076 at 53:12-25. Finally, Fig. 9
`
`depicts a user holding WCU 907 with only one hand and using his other hand only
`
`to operate the device. Ex. 1024 at Fig. 9.
`
`WEST\268081547.1
`
`6
`
`
`
`D. DeLorme’s WCU Has Stored Hospitality Applications and Data
`PO argues that “DeLorme clearly provides no disclosure of a locally-stored
`
`software application and associated data for the claimed wireless device.” POR at
`
`29. In making this argument, the POR contradicts its own earlier assertion:
`
`DeLorme discloses that the WCU is “programmed” to transmit data to
`the server side and to receive data back from the server side. (Exh.
`1024 75:59 et seq.). “Programmed” means that software is stored on
`the WCU.
`
`POR at 18. Petitioner agrees that the WCU is programmed to transmit data to, and
`
`receive data from, the server side. See also Ex. 1076 at 162:4-12. This establishes
`
`that data is stored on the WCU. If data is sent from the WCU, that data is
`
`inherently stored on the WCU prior to its transmission, and if data is received by
`
`the WCU, that data is inherently stored on the WCU for some period of time
`
`afterward. Ex. 1070, ¶ 25. Similarly, DeLorme discloses electronic transfer of a
`
`“digital display” to a PDA (Ex. 1024 at 18:25-32) and storage of a reservation or
`
`discount coupon confirmation code on the WCU (Id. at 77:63-78:1). This is all that
`
`is required by the claims. To the extent that PO contends that some database must
`
`be permanently stored on the handheld device in order to satisfy this limitation,
`
`claim 12 is not so narrow. The Board has previously held that a wire-less device
`
`with a locally stored database is but one species of a genus that also includes
`
`wireless devices without a locally stored database. Ex. 1068 at 18-19.
`
`WEST\268081547.1
`
`7
`
`
`
`Petitioner also agrees with PO that DeLorme’s disclosure that the WCU is
`
`“programmed” to exchange data with the server means that software is stored on
`
`the WCU. POR at 18 (citing Ex. 1024 at 75:59 et seq.); Ex. 1076 at 160:12-25. In
`
`addition to exchanging data with the server, this software performs other tasks,
`
`including voice recognition of user inputs (Ex. 1024 at 76:46-59), conversion of
`
`output to audio form (id.) and processing data from a GPS receiver (id. at 75:46-
`
`59). This WCU software is an application. Ex. 1070 ¶¶ 26-27. The WCU appli-
`
`cation is a hospitality application because the data exchanged with the server and
`
`presented to the user is hospitality data, and because this hospitality data is ex-
`
`changed using a format specific to DeLorme’s TRIPS hospitality system (Ex. 1024
`
`at 73:30-41). The exchanged data relates to travel, e.g., selections of “hotel, rest-
`
`aurant or menu,” travel position information, reservations, etc. Ex. 1024 at 76:29-
`
`67; 74:2-29; Ex. 1076 at 161:24-162:3 (admitting that the WCU includes software
`
`enabling users to make reservations). This data is thus hospitality data under the
`
`proper BRI construction. See, e.g., Ex. 1071 at 1; Ex. 1072 at 1; Ex. 1073 at 1; Ex.
`
`1070 ¶¶ 28-32. Thus, both hospitality applications and data are stored on the WCU.
`
`Although DeLorme’s WCU in its non-Web form satisfies the “wireless
`
`handheld device” limitations of claim 12, PO also asserts that the Board sua sponte
`
`combined the “internet only” embodiment of DeLorme with the WCU to arrive at
`
`an internet version of the WCU onto which java applets were installed in order to
`
`WEST\268081547.1
`
`8
`
`
`
`satisfy the requirement for a wireless handheld device on which an application is
`
`stored. POR at 33-34 (citing ID, Paper No. 13, at 22). As shown in the Petition,
`
`such a combination would have been obvious to a POSITA, who would have been
`
`motivated to make the combination and substitute an off-the-shelf wireless hand-
`
`held device for the WCU in order to save money by using existing hardware and
`
`internet communications protocols, which were supported by TRIPS. Pet. at 24-26;
`
`Ex. 1002 ¶¶ 93-99. PO fails to establish any error for the following reasons.
`
`First, PO overreaches by characterizing DeLorme’s disclosure of the use of
`
`TRIPS data packets for WCU communications as “express restrictions and
`
`requirements” (POR at 36), asserting that “DeLorme’s WCU is antithetical to the
`
`use of web pages/web browser thereon” (Id. at 36-37), and arguing that DeLorme
`
`“teaches away” from an internet-enabled WCU (POR at 30-31). DeLorme’s
`
`descriptions of the WCU and the use of TRIPS data packets are not accompanied
`
`by any indication that his system was restricted to WCUs that used TRIPS data
`
`packets, or that other implementations (e.g. internet implementations) were
`
`undesirable, impossible, inoperative, or otherwise discouraged. Thus, PO’s argu-
`
`ment that DeLorme’s disclosure precludes other implementations of the WCU is
`
`legally incorrect and must be rejected. MPEP § 2141.02(VI); In re Fulton, 391
`
`F.3d 1195, 1201 (Fed. Cir. 2004) (“the prior art’s mere disclosure of more than one
`
`alternative does not constitute a teaching away from any of these alternatives
`
`WEST\268081547.1
`
`9
`
`
`
`because such disclosure does not criticize, discredit, or otherwise discourage the
`
`solution claimed”); IPR2012-00001, Paper No. 59, at 35; see generally Ex. 1075.
`
`PO’s argument that the use of Java applets on a WCU is “directly contrary”
`
`to claim 12’s requirements for an application to be stored on the wireless device
`
`and for that application to be synchronized (POR at 37-38) is also flawed. Once a
`
`Java applet is downloaded to the WCU, “smart cell phone” or other wireless
`
`device, it is stored on the device. There is no requirement that the application must
`
`be stored on non-volatile or permanent storage. Notably, downloading a Java
`
`applet to the wireless device constitutes synchronizing of the application on the
`
`wireless device even under PO’s improperly narrow “synchronized” construction.
`
`In any event, the ability of the Java applet to synchronize data with the rest of the
`
`TRIPS system is sufficient under the correct construction. Ex. 1070 ¶¶ 34-36.
`
`Second, PO fails to establish any procedural error in the Board’s Decision.
`
`In In re Cuozzo Speed Techs., LLC, 293 F.3d 1268 (Fed. Cir. 2015)(cert. granted
`
`Jan. 15, 2016)), the Federal Circuit addressed a patent owner’s argument that the
`
`PTAB’s final written decision relied on grounds not identified in the petition and
`
`found that the “fact that the petition was defective is irrelevant because a proper
`
`petition could have been drafted.” Cuozzo at 1274. All of PO’s cited cases (POR at
`
`22-23) are inapposite because they involve Board decisions relying on common
`
`sense or its own knowledge rather than prior art disclosures, whereas here De-
`
`WEST\268081547.1
`
`10
`
`
`
`Lorme discloses internet embodiments and Java applets. No error has been shown.
`
`E.
`
`Transmission of an Application to the Wireless Handheld Device
`Is Not Required by Claim 12
`
`PO also argues that DeLorme fails to disclose element b) of claim 12
`
`because DeLorme does not disclose transmitting any applet or software code to the
`
`WCU. POR at 34. This argument rests on an erroneous claim construction and
`
`therefore must be rejected. Element b) simply requires “at least one wireless
`
`handheld computing device on which hospitality applications and data are stored.”
`
`“Store” means “to retain information in a device from which the information can
`
`later be withdrawn.” Ex. 1074 at 739. Thus, the mere presence of a hospitality
`
`application accessible on the wireless handheld device is all that is required under a
`
`correct construction. In contrast, PO’s implied construction requiring writing the
`
`application program to the wireless handheld device is wrong because claim 12 is a
`
`device claim, not a method claim or a product-by-process claim, and the language
`
`of element b, including the use of the passive voice and the absence of any
`
`“configured to” or similar language, indicates that “stored” means “retained.”
`
`Moreover, even if PO’s construction were correct (it is not), claim 12 includes no
`
`requirement that such a storage operation must occur more than once. Thus,
`
`DeLorme’s disclosure of an application on the WCU, which also inherently
`
`discloses at least one storage operation performed on the WCU (Ex. 1070 ¶¶ 39-
`
`40), is sufficient to disclose element b) under PO’s incorrect construction.
`
`WEST\268081547.1
`
`11
`
`
`
`F. DeLorme Discloses Use of the WCU with Desktop Internet
`Embodiments
`
`PO also argues that DeLorme precludes the combination of its desktop
`
`online via a World Wide Web site embodiment with the non-Web WCU. POR at
`
`39-40. PO is, yet again, wrong. The “entirely online” embodiment of DeLorme is
`
`described as an alternative to the version of TRIPS that comes partially on a CD-
`
`ROM. Both embodiments run on a desktop PC. Ex. 1024 at 14:1-52. Both
`
`embodiments involve Web-based communications, including map data updates,
`
`special discount offers, and other travel information. Id. at 14:19-42.
`
`DeLorme further makes clear that the non-web WCU can be used in such
`
`desktop systems that include web communications. The WCU is discussed in
`
`connection with Fig. 9. DeLorme discloses that “Fig. 9 illustrates an important
`
`alternative or additional embodiment of TRIPS – that permits mobile users 901, at
`
`remote locations ... two-way access by wireless communications 903 to engage the
`
`novel travel reservation information planning system of one or more TRIPS 904
`
`communications facilities or service bureaus.” Ex. 1024 at 71:61-66. This
`
`description indicates that the WCU can be used as an addition to the desktop
`
`systems discussed above. This indication is confirmed by DeLorme’s disclosure
`
`that the WCU embodiments “can function either with or without (elation [sic,
`
`relation] to desktop TRIPS user setups as described heretofore with reference to
`
`Fig. 1A” Id. at 72:20-23. DeLorme thus discloses that non-Web WCUs can be used
`
`WEST\268081547.1
`
`12
`
`
`
`in the same system as desktop PCs, and both PC embodiments (“internet only” and
`
`CD-ROM) involve web-based communications.
`
`DeLorme’s discussion of Fig. 4 also establishes that the WCU can be used
`
`with web-based desktop embodiments. DeLorme states that the flow chart of Fig. 4
`
`includes features that are preferable for the internet-only desktop embodiment. Ex.
`
`1024 at 36:31-36. Later in the discussion of Fig. 4, DeLorme discloses:
`
`Moreover, the Main Menu 413 and Interaction Bus 414 in FIG. 4
`correspond to, and coordinate the response to, alternative input means
`embedded in specialized TRIPS field or in-vehicle embodiments that
`typically include the wireless communication of GPS position sensor
`data along with simplified, "push-button" travel information inquiries
`sent by users actually en route or at remote locations. Such automated,
`standardized operational TRIPS sequences are further described
`hereinafter--particularly referring to FIG. 9.
`
`Id. at 37:58-67. The “specialized TRIPS field or in-vehicle embodiments”
`
`referenced in this passage are clearly the WCUs of Fig. 9. See id. at 71:67-72:2
`
`(describing WCU mounted in a vehicle), 73:13 (WCU used in the field), 73:26-30
`
`(WCU configured for push button inquiries). Thus, the discussion of the WCU and
`
`the internet-only desktop embodiment in connection with Fig. 4 further indicates
`
`that both can be used in the same system. Indeed, Ameranth’s expert Dr. Weaver
`
`admitted that the “same” TRIPS server can be accessed by users using web
`
`browsers or WCUs. Ex. 1076 at 169:3-15.
`
`WEST\268081547.1
`
`13
`
`
`
`G. DeLorme Discloses an “Application Program Interface”
` that “Enables Integration of Outside Applications”
`
`PO makes two arguments as to why DeLorme does not disclose an
`
`application program interface. Neither argument has merit. PO first makes the
`
`incomprehensible argument that the claimed API must integrate outside
`
`applications with hospitality applications “from within the applications
`
`themselves.” POR at 40 (emphasis in original). PO provides no support for this
`
`“within” requirement, and provides no explanation as to what it means to integrate
`
`an outside application with a hospitality application from within the applications.
`
`While PO cites ¶85 of its expert’s declaration, that paragraph simply parrots the
`
`statements in the POR. Id. The ’850 patent specification is also of no help – the
`
`only mention of the claimed API are three identical references to “a well-defined
`
`application program interface ("API") that enables third parties... to fully integrate
`
`with computerized hospitality applications.” Ex. 1001 at 2:11-15; 3:64-67;11:16-
`
`18. PO’s failure to support or explain this argument renders Petitioner unable to
`
`respond meaningfully and is sufficient reason to disregard it.
`
`PO’s second argument is that TRIPS applications are not hospitality
`
`applications. This argument is also wrong because TRIPS applications are
`
`hospitality applications. See infra at §2.D; Exs. 1071, 1072. That the TRIPS
`
`hospitality applications are integrated with third-party outside applications that
`
`themselves are hospitality applications is of no moment as the Board has held that
`
`WEST\268081547.1
`
`14
`
`
`
`“outside applications” does not preclude hospitality applications. Paper 13 at 10.
`
`Additionally, the TRIPS system necessarily has an API because DeLorme
`
`discloses that TRIPS is able to communicate and exchange data with outside
`
`applications. Ex. 1024 at 16:5-9; 77:60-78:21; Ex. 1070 ¶¶ 52-54. As Ameranth’s
`
`expert Dr. Weaver admitted, “all software operates through an API when it is
`
`going to communicate over a network ...” Ex. 1076 at 80:13-20; see also 223:11-13
`
`(accord); 170:2-172:16 (admitting that TRIPS communicates with outside
`
`applications over a network using predefined communication protocols,
`
`communication formats and inputs and outputs); 225:11-24 (accord).
`
`H. DeLorme Discloses a Communications Control Module (“CCM”)
`PO makes four arguments as to why DeLorme does not disclose a CCM,
`
`each of which fails. First, PO argues that DeLorme’s Interface & Interaction Bus
`
`209 “is not a server-side software layer.” POR at 43. However, as the Board
`
`recognized, DeLorme discloses that the Interface & Interaction Bus 209 “generally
`
`represents TRIPS processes for user-controlled sequencing, variable integration
`
`and selective accumulation of geographic, temporal, topical and accounting travel
`
`information in response to TRIPS user input travel inquiries.” Paper No. 13 at 25
`
`(quoting Ex. 1024 at 31:15-19); see also Ex. 1024 at 31:24-25 (“the Interface &
`
`Interaction Bus 209 also manages integrated and/or automated operations.”). Thus,
`
`the Interface & Interaction Bus 209 is not merely hardware but rather includes
`
`WEST\268081547.1
`
`15
`
`
`
`software. Paper 13 at 25. While there is no “server side” claim requirement, the
`
`Interface & Interaction Bus 209 is clearly “server side.” Ex. 1024 at Fig. 2; 34:26-
`
`56 (describing user logging on to TRIPS Internet site and having interactions
`
`processed by Fig. 2 subsystems); Ex. 1076 at 174:13-15; Ex. 1070 ¶¶ 56-59.
`
`Second, PO argues that DeLorme’s Interface & Interaction Bus 209 “does
`
`not provide an interface between hospitality applications and communication
`
`protocols.” POR at 43. However, as established in the Petition at 56, DeLorme
`
`discloses that Bus 209 (which is also represented by the Main Menu 413 and the
`
`Interaction Bus 414) serves as an interface between retail consumers (e.g. 205 in
`
`Fig. 2) and the various server-side subsystems (i.e. applications) that comprise
`
`TRIPS (213, 217, 221 and 223 in Fig. 2). See also Ex. 1002 at ¶¶ 206-209. The
`
`Petition and Dr. Turnbull further explain that a POSITA would understand or find
`
`obvious that Bus 209 must use different protocols to correspond with desktop users
`
`in the Web-only embodiments and WCU users communicating with the proprietary
`
`TRIPS data packets in the non-Web WCU embodiments. Pet. at 56; Ex. 1024 at
`
`14:66-15:13, 73:26-45, and 73:67-74:29; Ex. 1002 ¶ 209. Ameranth’s expert
`
`concurs. Ex. 1076 at 176:17-177:12. PO’s second argument thus also fails.
`
`Third, PO argues that DeLorme’s Interface & Interaction Bus 209 “does not
`
`monitor and route communications to different devices while concurrently using
`
`different protocols.” POR at 42. However, as discussed above, DeLorme discloses
`
`WEST\268081547.1
`
`16
`
`
`
`systems including desktop users employing web-based communications (using one
`
`protocol) together with WCU users employing non-Web communications (using a
`
`different protocol). See infra at § 2. F. Interface & Interaction Bus 209 routes these
`
`communications using different protocols to the various TRIPS subsytems (i.e.
`
`applications 213, 217, 221 and 223). Ex. 1024 at Fig. 2; Ex. 1076 at 177:9-12; Ex.
`
`1070 ¶¶ 64. In any event, there is no requirement for the various devices in the
`
`system of claim 12 to communicate using different protocols or to do so con-
`
`currently. Indeed, nothing in the ’850 patent precludes the use of Web-based
`
`communications protocols for all devices.4 See CBM2015-00091, Paper No. 9 at
`
`32-33 (“[t]he only specific protocol discussed in the specification is HTTP, a web
`
`based communications protocol.”). PO’s third argument thus fails.
`
`4 PO’s contrary assertion is not supported by the patent. POR at 9-10 (citing ’850
`
`patent at 11:49-57). The cited passage describes a “simple point to point wireless
`
`capability ... 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.” Id.
`
`In wireless communications, point-to-point communications are direct from one
`
`device to another, without passing through any intermediate device. Ex. 1074 at
`
`574. Thus, this passage describes direct communications that do not pass through
`
`the CCM. The CCM is not involved in any protocol translation for these messages,
`
`and PO’s argument fails because it is not supported by the specification.
`
`WEST\268081547.1
`
`17
`
`
`
`Fourth, PO argues that DeLorme’s Interface & Interaction Bus 209 “is not ‘a
`
`software layer that sits on top of a communications protocol and acts as an
`
`interface between hospitality applications and the communications protocol’ as
`
`stated by the specification.” POR at 43. This supposed requirement “stated by the
`
`specification” is not recited in the claim, and PO’s improper attempt to import it
`
`into the claims should be rejected. In any event, Interface & Interaction Bus 209
`
`includes software, does sit on top of Web-based and WCU non-Web protocols and
`
`does act as an interface between these devices and the different TRIPS subsystems/
`
`applications 213-223 for the reasons discussed above. See also Ex. 1024 at 37:54-
`
`65 (discussing the Main Menu 413 and Interaction Bus 414 processing both
`
`Internet and non-Web WCU transactions); Ex. 1076 at 176:17-177:12; Ex. 1070 ¶
`
`66. Accordingly, PO’s fourth and final argument also fails.
`
`PO also argues that claims 14 and 15 are not disclosed in DeLorme. The
`
`Petition explained that because the TRIPS database maintains all travel and
`
`itinerary information, it would have been obvious to a POSITA that information
`
`entered on a Web page in a desktop Web embodiment would automatically be
`
`reflected in the form of an updated itinerary in future downloads of the itinerary to
`
`a WCU (claim 14) and vice versa (claim 15). Pet. at 60-61 (citing Ex. 1002 ¶¶ 227,
`
`232). PO does not contest this showing and thus has waived any contrary
`
`argument. Instead, PO contends that the web page and wireless handheld device
`
`WEST\268081547.1
`
`18
`
`
`
`cannot be satisfied by the same structure. POR at 44. But Petitioner’s showing
`
`concerns two different structures – a desktop Web-based embodiment and a WCU
`
`embodiment. PO’s argument is thus based on PO’s assertion that the DeLorme
`
`does not disclose the use of a Web-based embodiment and a non-Web WCU
`
`device in the same system, which is wrong for the reasons discussed above.
`
`Dependent Claims
`
`I.
`PO’s arguments that DeLorme does not disclose the “single point of entry”
`
`limitation of claim 13 are confusing and/or incorrect. PO argues that Petitioner
`
`ignored either or both of the “single point of entry” limitation or its “center of
`
`communications for hospitality applications” construction. POR at 47. But the
`
`Interface & Interaction Bus 209 (which is not just hardware as discussed above) is
`
`a single point of entry and a center of communications for the web-based and
`
`WCU users and the different TRIPS subsystems/applications 213, 217, 221 and
`
`223 as shown in Fig. 2. PO then argues that Petitioner “pointed to the same
`
`disclosure in DeLorme which it asserts satisfied the ‘synchronized’ and handheld
`
`limitations.” POR at 47. This is clearly incorrect as the Petition identifies the WCU
`
`907 as the wireless handheld device (Pet. at 53) and cited passages of DeLorme
`
`that disclose synchronizing data between the central database (relational database),
`
`the wireless handheld device (WCU), and the at least one web page (in the desktop
`
`Web-based embodiment). Pet. at 60 (citing Ex. 1024 at 14:24-47; 72:37-43; 72:67-
`
`WEST\268081547.1
`
`19
`
`
`
`73:6; Ex. 1002 ¶ 222). PO also mischaracterizes the Petition as relying on
`
`DeLorme’s disclosure of communications with third-party hospitality applications
`
`when the Petition clearly discusses communications between applications within
`
`the TRIPS system. Compare POR at 48 and n. 23 with Pet. at 59-60. Finally, PO
`
`repeats its incorrect argument that TRIPS does not comprise hospitality
`
`applications, which is wrong for the reasons discussed above.
`
`With respect to claims 14 and 15, PO argues that DeLorme does not disclose
`
`“automatic” downloads, because downloads occur in response to user action. POR
`
`at 50. This argument is premised on PO’s construction of “automatic,” purportedly
`
`drawn from the specification. But PO’s construction ignores other statements
`
`which do not include a strict “no user action” requirement. For example, the ’850
`
`patent states tha