throbber
Atty Docket No. FABO-045/00US
`(309101-2137)
`
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`FACEBOOK, INC. and WHATSAPP INC.,
`Petitioners,
`
`v.
`
`UNILOC USA, INC., UNILOC LUXEMBOURG, S.A.,
`Patent Owner(s).
`
`
`
`
`Case IPR2016-01756
`Patent No. 8,571,194
`
`
`PETITIONERS’ REPLY
`
`
`
`
`
`
`
`
`

`

`Table of Contents
`
`
`Page
`
`2.
`
`
`Introduction ..................................................................................................... 2 
`I.
`II. Wu and Howard Disclose “Without Requiring Registration” ....................... 3 
`A. Wu ........................................................................................................ 4 
`1. Wu’s Login Process Does Not Involve Registration
`“With A Conference Call Server”.............................................. 4 
`The Authentication Processes in Figure 6 Do Not
`Require “Registration… By the Potential Members
`Including the First Party and the At Least One Other
`Party”.......................................................................................... 8 
`The Patent Owner’s Claim Construction Arguments Are
`Irrelevant .................................................................................. 14 
`B. Howard ............................................................................................... 18 
`III. Wu Discloses “Without Requiring Individual Selection” ............................ 22 
`IV. Conclusion .................................................................................................... 26 
`
`3.
`
`
`
`
`
`-i-
`
`
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`
`
`
`
`List of Exhibits
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`
`
`
`
`Exhibit No.
`1022
`1023
`1024
`
`Title of Document
`Deposition Transcript of Dr. DiEuliis (“DiEuliis Depo.”)
`
`Excerpts from Stevens, TCP/IP Illustrated, Volume 1 (1994)
`
`U.S. Patent Pub. No. 2004/0013254 to Max Hamberg et al.
`(“Hamberg”)
`
`1025
`
`Reply Declaration of David Klausner (“Klausner Reply”)
`
`
`
`1
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`I.
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`INTRODUCTION
`The Patent Owner’s lengthy response spends very little time actually
`
`addressing the Wu and Howard references. The Patent Owner spends dozens of
`
`pages on irrelevant digressions about claim construction (while offering no actual
`
`constructions), but does not connect those arguments to the prior art. It is not until
`
`page 44 that the Patent Owner makes its first attempt to directly address the “without
`
`requiring registration” limitation as disclosed in Wu. The Patent Owner argues that
`
`Wu discloses multiple instances of “registration” (a term that the Patent Owner does
`
`not construe and its expert refused to define), but those instances do not involve
`
`registration “with a conference call server,” “by the potential members,” as the plain
`
`language of the claims require.
`
`With respect to instituted Ground 2, which adds the Howard reference, the
`
`Patent Owner essentially has no answer. It is undisputed that under the combination
`
`of Wu and Howard, users register only with authentication server 110 of Howard,
`
`which sits entirely outside of the cluster of (AOL) servers in Wu. There is also no
`
`serious dispute that the authentication server in Howard is not a “conference call
`
`server,” under any conceivable construction of the term, because it has no
`
`involvement in requesting or providing the voice communication features of Wu.
`
`The Patent Owner is thus left arguing that the two references cannot be combined,
`
`but ignores the extensive analysis and multiple motivations to combine set forth in
`
`
`
`2
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`the Petition and acknowledged in the Institution Decision. For the reasons set forth
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`below and in the Petition, the Petitioners respectfully request that the Board find the
`
`challenged claims unpatentable.
`II. WU AND HOWARD DISCLOSE “WITHOUT REQUIRING REGISTRATION”
`
`The Patent Owner’s arguments gloss over the claim language, which recites
`
`an “option” to automatically initiate voice communication “without requiring
`
`registration with a conference call server for establishing the voice communication
`
`by the potential members including the first party and the at least one other party.”
`
`(’194, Claim 1.) This negative claim limitation imposes at least three separate
`
`components: initiation of voice communication using the “option” must not require
`
`(1) “registration,” (2) “with a conference call server,” (3) “by the potential members
`
`including the first party and the at least one other party.” A prior art reference can
`
`therefore disclose this negative limitation if it lacks even one of these three
`
`components. For example, a prior art reference will satisfy this limitation even if it
`
`requires registration, if that registration is not “with a conference call server.” A
`
`prior art reference can also satisfy the limitation if it requires “registration with a
`
`conference call sever,” but the registration is not performed “by the potential
`
`members.” As shown below, all of the Patent Owner’s arguments about Wu ignore
`
`one or more of the three components of the “without requiring registration”
`
`limitation listed above.
`
`
`
`3
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`This section will first address the Patent Owner’s arguments with respect to
`
`Wu. This section will then address the disclosures of Howard, cited in combination
`
`with Wu in instituted Ground 2.
`
`A. Wu
`1. Wu’s Login Process Does Not Involve Registration “With A
`Conference Call Server”
`The Patent Owner contends that the login process in Wu, in which the user
`
`enters her screen name and password to gain access to the system, involves
`
`“registration with a conference call server.” But the Petition explained in great detail
`
`why that login process requires the user to interact only with a “login server,” which
`
`is not a “conference call server” because it has no involvement in establishing voice
`
`communication. (Petition, at 40-48; Ex. 1002, ¶¶103-116.)
`
`The Patent Owner relies on Paragraph 63 of Wu, which describes a logon
`
`process that users follow to gain access to a service provider such as AOL.
`
`(Response, at 44-45; DiEuliis Decl., Ex. 2003, ¶¶97-98 (citing Wu, ¶0063); see also
`
`Wu, ¶¶0003-4.) That paragraph describes a process in which a user inputs a screen
`
`name and password, which “host 604” uses to determine if the user is authorized to
`
`access the system. (Wu, ¶0063.) The Patent Owner appears to argue that because
`
`“host 604” performs the login process, and “host 604” also performs steps required
`
`to initiate voice communication, Wu discloses registration “with a conference call
`
`server” and thus does not satisfy the negative limitation. (Response, at 43-48.)
`
`
`
`4
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`But the “host” device in Wu relied upon by Petitioners is not a monolithic
`
`server, but a collection of discrete components and systems – including a separate
`
`login server. The Petition explained in great detail, including with annotations to
`
`Figures 3 and 5 of Wu, why the login server (350, 570) of the host device (335, 535)
`
`is both physically and functionally separate from the “conference call server” that is
`
`responsible for voice communication services. (Petition, at 41-46; see also Wu,
`
`¶0032 (“The host device 335 [of Figure 3] includes a login server 370…”), ¶¶0049-
`
`0050 (same; Figure 5 including login server 570).)
`
`Wu makes clear that the “host 604” relied upon by the Patent Owner shares
`
`those same characteristics. For example, three paragraphs up from the passage cited
`
`by the Patent Owner, Wu states that “[t]he host 604 [of Figure 6] typically has
`
`attributes comparable to those described with respect to host device 135, 235, 335,
`
`435, and 535” (Wu, ¶0060), explicitly referring back to the more detailed depictions
`
`of the host device 335 and 535 that were discussed in the Petition.1 One of ordinary
`
`skill would thus have understood that the login process in Paragraph 63 would be
`
`performed by the login server component of “host 604,” consistent with every other
`
`
`1 All underlining has been added for emphasis.
`
`
`
`5
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`embodiment in Wu. (Klausner Reply, Ex. 1025, ¶¶26-29.)2
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`The Patent Owner also has no answer to the disclosure in Paragraph 51 of Wu
`
`(described in detail in the Petition), which explains that the login server 570 of Wu
`
`“breaks the connection” with the client after login authentication is completed,
`
`allowing the client to connect directly to the IM server using the IP address provided
`
`by the login server. (Petition, at 43-46; Ex. 1002, ¶¶110, 111; Wu, ¶0051.)3 The
`
`
`2 The Patent Owner’s mischaracterization of the “host” as a monolithic entity also
`
`ignores Wu’s teaching that “[f]or brevity, several elements in the figures described
`
`[] are represented as monolithic entities. However, as would be understood by one
`
`skilled in the art, these elements each may include numerous interconnected
`
`computers and components designed to perform a set of specified operations.” (Wu,
`
`¶0014.) Indeed, the Patent Owner appears to concede that there is “express
`
`disclosure in Wu that the host may be implemented as multiple computing devices.”
`
`(Response, at 53 (citing Wu, ¶20).)
`
`3 Instead, the Patent Owner can only quibble that Wu does not expressly list
`
`“establishing a talk session” as one of the functions performed by the IM host
`
`complex 590. (Response, at 55-56.) But one of ordinary skill would have certainly
`
`understood that it is performed by one of the servers within the IM host complex 590
`
`based on Wu’s teachings, although Wu may not refer to any particular server using
`
`
`
`6
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`Patent Owner suggests that the login server is somehow still involved with the voice
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`communication (Response, at 56), but the Patent Owner’s own expert agreed at his
`
`deposition that by the time users in Wu have entered into an IM session, any
`
`connection between the users and the login server has been broken. (Ex. 1022,
`
`84:25-85:2, 86:2-8.) Wu does not suggest that the login server 570 has any role in
`
`providing any services to the client (including IM and voice communication
`
`services) after that connection is broken. Moreover, any contention that the login
`
`server in Wu must be mapped as part of the claimed “conference call server” – no
`
`matter how tangential its “role in establishing a talk session” (Response at 59, 60) –
`
`is without merit. (See also id., at 51-54.) The ’194 specification contemplates that
`
`even components that play a role in establishing a talk session can nevertheless be
`
`“discrete from” the conference call server. (’194, 6:14-29.)
`
`Finally, the Patent Owner’s own arguments confirm that the login process in
`
`
`the nomenclature “conference call server.” (Klausner Reply, ¶29 (citing Wu,
`
`¶¶0052, 0059, 0065, Fig. 6).) Moreover, while the Patent Owner contends that Wu’s
`
`process is “analogous to the registration required in Hamberg and successfully
`
`distinguished from the claims during prosecution” (Response, at 48), Hamberg,
`
`unlike Wu, does not use a separate login server that “breaks the connection” with
`
`the client after login authentication. (See Hamberg, Ex. 1024.)
`
`
`
`7
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`Wu is irrelevant to the “without requiring registration” limitation. The Patent
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`Owner’s own expert concedes that the “without requiring registration” limitation
`
`only becomes operative when the claimed “option” to initiate voice communication
`
`is displayed to the user. (Klausner Reply, ¶30 (quoting DiEuliis Decl., Ex. 2003,
`
`¶40).) This is further confirmed by a passage in the ’194 specification that the Patent
`
`Owner cites as a “teaching[] concerning automatic
`
`initiation of voice
`
`communication” without requiring registration. (Response, at 21-22 (citing ’194
`
`patent, 4:25-38).) That passage expressly contemplates that potential participants
`
`may have registered with “the instant messaging service” prior to the initiation of
`
`the voice communication. (’194, 4:33-38.) Because the login process in Wu
`
`similarly occurs before the “option” (the “START TALK” button in Figure 7) even
`
`appears, that process is irrelevant to the “without requiring registration” limitation.
`
`(Klausner Reply, ¶30.)
`
`2.
`
`The Authentication Processes in Figure 6 Do Not Require
`“Registration… By the Potential Members Including the
`First Party and the At Least One Other Party”
`The Patent Owner also argues that, beyond the initial login process addressed
`
`above, the process in Figure 6 of Wu “requires two registrations: one to authenticate
`
`a text message and another just prior to initiating voice communication.” (DiEuliis
`
`Decl., Ex. 2003, ¶99; see also id., ¶¶80-81; Response, at 45-48.) The first purported
`
`“registration” identified by the Patent Owner appears in Paragraph 67 of Wu in
`
`
`
`8
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`which the host authenticates a text message by a sender (Step 610), and the second
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`appears in Paragraph 72 in which the host authenticates a “talk request” from the
`
`sender (Step 650). (See Wu, ¶¶0067, 0072; Response, at 45-49; DiEuliis Decl.,
`
`¶¶79-80.) But neither of these purported “registrations” takes Wu out of disclosing
`
`the “without requiring registration” requirement.
`
`The Patent Owner does not provide any reasoned explanation as to why either
`
`of these two authentication steps involve “registration… by the potential members,”
`
`as claimed. This is not surprising considering that the Patent Owner provides no
`
`construction for the “registration” term. The Patent Owner’s expert, in fact, refused
`
`at his deposition to explain how he was interpreting “registration” and testified that
`
`he had formed no opinion on the subject. (DiEuliis Depo., Ex. 1022, 41:14-42:13.)
`
`The Patent Owner’s arguments thus reduce to nothing more than attaching the label
`
`“registration” to authentication processes in Wu, without any accompanying
`
`explanation as to how those processes apply to the claim language.
`
`Nevertheless, as explained above and in the Petition, the only time a user
`
`registers in Wu is during the initial login with the separate login server, which is not
`
`a conference call server. The authentications in Steps 610 and 650 of Figure 6 reflect
`
`steps that occur after login with the login server has completed. (Wu, ¶¶0063, 0067,
`
`0071.) Those do not show additional “registration[s]… by the potential members,”
`
`as the Patent Owner asserts, but describe how the system responds to requests from
`
`
`
`9
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`a user to initiate communications among already-registered members. Neither of
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`those authentication steps requires the user to reenter username and password
`
`information, or supply any other personal information to gain access to the system,
`
`because that process already took place when the user logged in using the login
`
`server. (Petition, at 45-48; Ex. 1002, ¶¶111-116; Klausner Reply, ¶36.)
`
`The Patent Owner’s arguments conflate “registration… by the potential
`
`members” with “authentication,” but the two are not the same thing. Networked
`
`computer systems will often – without requiring further input from the user –
`
`perform authentication processes when requests are received to ensure that the user
`
`continues to have proper access to the system. (Klausner Reply, ¶36.) But the act
`
`of authentication by the server in Wu is not the same thing as registration by the
`
`potential members, which is what the claim recites.4 As noted, these authentications
`
`do not involve the user reentering the registration information it used to login to the
`
`service. (Id., ¶¶36, 37.)
`
`To the extent any construction can be discerned from the Patent Owner’s
`
`response, it appears to be so broad as to exclude every embodiment in the
`
`
`4 Note the claimed requirement of registration “by the potential members” does not
`
`depend on any construction of “registration” itself, as discussed further below in the
`
`text.
`
`
`
`10
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`specification of the ’194 patent. As explained in the Petition, the applicant stated
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`during prosecution that:
`
`The embodiments described above with respect to paragraphs 22, 23
`and 50-53 [of U.S. Pub. No. 2011/0033035, Ex. 1009] clearly do not
`require prior registration with a conference call server by potential
`members of a voice communication. Indeed, the conference server may
`simply strip telephone numbers from the conference request message
`sent from the instant messaging service and establish the voice
`communication directly therefrom.
`
`(Petition, at 27-28 (quoting Ex. 1010, p.10).) The applicant did not identify any
`
`other embodiment as support for this claim limitation.
`
`Those embodiments describe a process in which a conference call requester
`
`sends a “conference request message” to the conference call server – a message that
`
`mirrors the talk request in Wu. As explained in Paragraph 52 of the applicant’s
`
`published application (which appears verbatim in the issued patent):
`
`When a conference call requester desires to initiate a conference call,
`the conference call requester may generate 106 a message (hereafter
`referred to as the ‘conference request message’) to the conference
`server identifying the parties who are potential recipients (‘potential
`targets’) to a conference call.
`
`(Ex. 1009, ¶52; see also ’194, 6:44-51 (same disclosure as ¶52).) Paragraph 53 goes
`
`on to explain that “[t]he conference request message may then be received 110 by
`
`
`
`11
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`the conference server. The conference server may parse 112 the received message to
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`determine the address of the selected conference call targets.” (Ex. 1009, ¶53; see
`
`also ’194, 6:59-62 (same disclosure as ¶53).)
`
`Thus, just like the talk request in Wu, the “conference request message” in the
`
`’194 patent – an integral part of the very embodiment that the applicants identified
`
`as support for the “without requiring registration” requirement – identifies the
`
`potential participants to the communication. There is no material difference between
`
`the “conference request message” in the specification and the “talk request” in Wu.
`
`(Compare Wu, ¶0071 (“The talk request may contain information including, but not
`
`limited to, the message type, the screen name and/or IP address of the sender and
`
`recipient, and a randomly generated security number”), with ’194, 6:44-51 (“[T]he
`
`conference call requester may generate 106 a message (hereafter referred to as the
`
`‘conference request message’) to the conference server identifying parties who are
`
`potential participants (‘potential targets’) to a conference call. The potential call
`
`targets may be identified by an alias, such as a user name associated with the
`
`conference call targets in the conference call requester’s NAD.”); see also Klausner
`
`Reply, ¶¶39-41.)
`
`Thus, to the extent sending the “talk request” of Wu involves registration by
`
`the potential members (which it does not as discussed above), then so too would
`
`transmission of the “conference request message” to the conference call server as
`
`
`
`12
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`described in the specification of the ’194 patent.
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`Federal Circuit law is clear that a “claim construction that excludes a preferred
`
`embodiment… is rarely, if ever correct and would require highly persuasive
`
`evidentiary support.” Epos Techs. Ltd. v. Pegasus Techs Ltd., 766 F.3d 1338, 1347
`
`(Fed. Cir. 2014) (citation omitted). The Patent Owner has not even addressed the
`
`preferred embodiment discussed above, let alone offered any “highly persuasive
`
`evidentiary support.”5 The Patent Owner’s apparent interpretation of “registration”
`
`would exclude not only a preferred embodiment, but the sole embodiments the
`
`applicant identified during prosecution as providing support for the “without
`
`requiring registration” limitation. (Ex. 1010, p.10.) Accordingly, the Board should
`
`reject the Patent Owner’s suggestion that “registration…by the potential members”
`
`
`5 The Patent Owner and its expert instead point to other embodiments in the
`
`specification, including the very embodiments the Examiner found (and the
`
`applicant did not dispute) disclosed prior registration. (Response, at 21-23; DiEuliis
`
`Decl., ¶¶57-59.) Those embodiments either affirmatively require registration with a
`
`conference call server, or are irrelevant to the “without requiring registration”
`
`limitation. (Klausner Decl., ¶¶10-13.)
`
`
`
`13
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`takes place when a talk request is sent identifying the participants to a conference.6
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`3.
`
`The Patent Owner’s Claim Construction Arguments Are
`Irrelevant
`The Patent Owner spends an inordinate number of pages arguing about the
`
`meaning of the terms “registration” and “conference call server,” but offers no
`
`interpretation of its own and urges the Board not to adopt any construction. The
`
`Patent Owner’s meritless arguments have nevertheless simplified the claim
`
`construction process, as explained below.
`
`a.
`“conference call server”
`With respect to the term “conference call server,” the Patent Owner goes on
`
`at length about how the claimed conference call server need not directly and
`
`
`6 The Patent Owner’s expert attempted to dismiss the relevance of the applicant’s
`
`discussion of “registration” in the prosecution history by noting that the claim was
`
`later amended to remove the word “prior” from the phrase “prior registration.”
`
`(DiEuliis Decl., Ex. 2003, ¶51.) This argument is meritless, as reflected in the fact
`
`that it is not mentioned or cited anywhere in the Patent Owner’s response. Indeed,
`
`the prosecution history reveals that the word “prior” was later removed from the
`
`claims for reasons unrelated to the applicant’s arguments discussed in the text.
`
`(Klausner Reply, ¶¶6-8.) The applicant never attempted to disavow or augment the
`
`remarks in its July 9, 2012 response (Ex. 1010) discussed in the text. (See Ex. 2005.)
`
`
`
`14
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`independently establish the voice communication itself and may use a physically-
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`separate component or system to do so. (Response, at 29-35; DiEuliis Decl., ¶¶68-
`
`70.) The Petition did not take a position as to whether a “conference call server” can
`
`indirectly establish a conference call. The Patent Owner’s own arguments have
`
`confirmed that this issue is wholly irrelevant to the resolution of this IPR.
`
`The Petition’s analysis made clear that the prior art cited in Ground 1 and
`
`Ground 2 discloses the “without requiring registration” limitation regardless of
`
`whether a “conference call server” can indirectly establish a conference call. With
`
`respect to Ground 1, the only server in Wu with which users might have to register
`
`is the login server, and that server has no role in initiating or establishing voice
`
`communication – either directly or indirectly. (Petition, at 40-45; Ex. 1002, ¶¶107-
`
`111.) The same is true with respect to the Howard reference cited in Ground 2. The
`
`only “registration” that takes place under the combination of Wu and Howard is with
`
`the “authentication server” in Howard, which sits entirely outside the (AOL)
`
`network and servers of Wu that provide IM and voice communication services.
`
`(Petition, at 63, 67; Ex. 1002, ¶124.) Under either combination, there is no
`
`registration with any server that establishes – either directly or indirectly, by itself
`
`or in combination with other components – the voice communication in the claims.
`
`As noted, any suggestion that the login or authentication server must somehow be
`
`mapped as part of the claimed “conference call server” is meritless because the ’194
`
`
`
`15
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`patent expressly contemplates that even components having a role in the
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`establishment of voice communication can nevertheless be “discrete from” the
`
`conference call server. (’194, 6:14-29.)7
`
`b.
`“registration”
`In light of the Patent Owner’s response, the dispute about the “without
`
`requiring registration” limitation with respect to Wu has narrowed to whether the IM
`
`and talk requests in Wu (¶¶0067, 0072) involve “registration… by the potential
`
`members.” None of arguments presented above rely on any particular construction
`
`for “registration.” For example, even assuming that the term “registration” is itself
`
`not limited to personal information supplied by users (Response, at 16), the
`
`limitation “registration… by the potential members” would nevertheless impose
`
`such a requirement. Thus, if the Board were to simply find that the IM and talk
`
`requests in Wu do not involve “registration… by the potential members,” that
`
`
`7 The Patent Owner is presumably pressing the construction of “conference call
`
`server” in order to impact later-filed IPR petitions filed by other petitioners on
`
`different prior art (such as IPR2017-00597), where the claim construction issue is
`
`potentially more relevant. The Petitioners respectfully submit that the “conference
`
`call server” issues should be resolved in the context of the later-filed IPR
`
`proceedings where the differences in construction would make a difference.
`
`
`
`16
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`finding would obviate the need for an explicit construction of “registration.”
`
`
`
`
`Case IPR2016-01756
`Patent 8,571,194
`
`With respect to Ground 2, discussed below, no definition of “registration” is
`
`required because the Patent Owner does not appear to dispute that Howard discloses
`
`the “without requiring registration” limitation and instead relies on arguments about
`
`combinability. (Response, at 65-67; DiEuliis Decl., Ex. 2003, ¶¶115-121.)
`
`Nevertheless, to the extent an explicit construction is needed, the Board
`
`should adopt the one offered by the Petitioners. As explained above and in the
`
`Petition, the registration process in the specification (to which the Examiner pointed
`
`during prosecution) is consistent with the definition of “registration” provided in
`
`Newton’s Telecom Dictionary. Both descriptions even use common terminology of
`
`“subscriber” and recite the same process of gaining access to a service by providing
`
`personal information. (Compare Newton’s Telecom Dictionary, Ex. 1008, p.763
`
`(“The process of supplying personal information needed to establish a subscriber
`
`account and get access into a network or a server.”), with ’194, 7:57-64 (“If User A
`
`is not a subscriber to the service, User A may be informed 316 that he is not allowed
`
`to use the service… User A may be provided with the opportunity to subscribe to
`
`the service at this point… [and] may be queried to provide information identifying
`
`a method for paying for the proposed conference call, such as through use of a credit
`
`card.”).) The Patent Owner does not identify anything else in the ’194 specification
`
`that discloses a registration process. (Klausner Reply, ¶¶10-12.) The dictionary
`
`
`
`17
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`definition offered by the Petitioners thus represents the plain and ordinary meaning
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`of “registration” at the time of the alleged invention, and is consistent with the
`
`intrinsic evidence. See Interval Licensing LLC v. AOL, Inc., 766 F.3d 1364, 1377
`
`(Fed. Cir. 2014) (“We have recognized that technical dictionaries can assist the court
`
`in determining the meaning of particular terminology to those of skill in the art of
`
`the invention.”) (citation omitted). And to the extent this definition can be
`
`characterized as limiting (Response, at 16-18), it would, in fact, provide for broader
`
`claim scope as the term “registration” is part of the negative limitation “without
`
`requiring registration.” Petitioners’ proposed construction is thus further consistent
`
`with the BRI standard.
`
`B. Howard
`The Patent Owner devotes only a small portion of its response to addressing
`
`the Howard reference cited in Ground 2. (Response, at 66-67.) This is because the
`
`Patent Owner has no meaningful response to Howard.
`
`As explained in the Petition, the process in Howard begins with the user
`
`registering with the authentication server 110. (See Petition at 65-66 (quoting
`
`Howard, Ex. 1007, 5:44-47).) “This registration is a one-time process which
`
`provides necessary information to the authentication server.” (Id. (quoting Howard,
`
`5:47-49).) “After registering and logging into the authentication server,” Howard
`
`explains, “the user can visit any affiliate server (i.e., affiliate servers that are also
`
`
`
`18
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`registered with the same authentication server) without requiring any additional
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`authentication and without re-entering user information that is already contained in
`
`the user profile.” (Id. (quoting Howard, 5:57-63).)
`
`The Patent Owner’s arguments about Wu addressed above rely on the
`
`assertion that three authentication processes in Wu constitute “registration” with a
`
`conference call server by the potential members. But under the combination of Wu
`
`and Howard, “registration” occurs only with the authentication server 110 of
`
`Howard, and that server sits entirely outside the system of Wu. (Petition, at 67.)
`
`The affiliate server 110 of Howard is not a “conference call server” because it has
`
`no involvement in establishing voice communications. The Patent Owner concedes
`
`in its response that “Howard makes no mention of either instant messaging or voice
`
`communication” (Response at 67), so the authentication server 110 in Howard
`
`obviously does not “request[] a remote affiliate server… to initiate a bridge for the
`
`voice communication” (Response, at 66), much less establish (directly or indirectly)
`
`voice communication in the manner described in Wu.
`
`This combination is thus fatal to the Patent Owner’s claims, and for that
`
`reason, the Patent Owner has no meaningful response to it. Under the proposed
`
`combination of Wu and Howard, after a user has registered and logged-into the
`
`authentication server 110 of Howard, the user can then access the affiliate servers –
`
`which include all of the servers in Wu – “without requiring any additional
`
`
`
`19
`
`

`

`Atty Docket No. FABO-045/00US
`(309101-2137)
`
`authentication” (Howard, 5:60-61), thus eliminating all of the authentications and
`
`Case IPR2016-01756
`Patent 8,571,194
`
`
`
`
`so-called “registrations” in Wu that the Patent Owner relies upon. Accordingly, even
`
`if the Patent Owner’s arguments about Wu and the “without requiring registration”
`
`limitation had any merit, Howard remedies them.
`
`The Patent Owner did not address any of the multiple motivations to combine
`
`described in the Petition. (Petition, at 67-69; Ex. 1002, ¶¶119-126.) The Patent
`
`Owner instead makes misguided challenges to the combination.
`
`First, the Patent Owner confusingly argues that “[a]pplying Petitioner’s
`
`flawed reasoning to the teachings of the ’194 Patent, one would erroneous [sic]
`
`conclude the disputed claim language could be satisfie

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