`U.S. Patent No. 8,199,747
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`
`FACEBOOK, INC., WHATSAPP INC.,
`Petitioners
`
`v.
`
`UNILOC USA, INC., UNILOC LUXEMBOURG, S.A.,
`Patent Owners
`
`U.S. Patent No. 8,199,747
`
`TITLE: SYSTEM AND METHOD FOR INSTANT VOIP MESSAGING
`
`
`
`
`
`PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 8,199,747
`
`
`
`Table of Contents
`
`
`Page
`
`
`
`
`I. Mandatory Notices Under 37 C.F.R. § 42.8(A)(1) ........................................ 1
`A.
`Real Party-In-Interest under 37 C.F.R. § 42.8(b)(1) ............................ 1
`B.
`Related Matters under 37 C.F.R. § 42.8(b)(2) ..................................... 1
`C.
`Lead and Back-Up Counsel under 37 C.F.R. § 42.8(b)(3) .................. 2
`D.
`Service Information .............................................................................. 3
`E.
`Power of Attorney ................................................................................ 3
`Fee Payment - 37 C.F.R. § 42.103 ................................................................. 3
`II.
`III. Requirements for Inter Partes Review under 37 C.F.R. §§ 42.104 and
`42.108 ............................................................................................................. 4
`A. Grounds for Standing under 37 C.F.R. § 42.104(a) ............................. 4
`B.
`Identification of Challenge under 37 C.F.R. § 42.104(b) and
`Statement of Precise Relief Requested ................................................ 4
`IV. Technology Background Relevant to a Person of Ordinary Skill in the
`Art ................................................................................................................... 4
`The ’747 Patent ............................................................................................... 6
`V.
`VI. Claim Construction Under 37 C.F.R. § 42.104(B)(3) .................................... 8
`A.
`“node” ................................................................................................... 8
`VII. Claims 1-3, 12, and 13 Are Unpatentable ...................................................... 9
`A.
`Brief Summary and Date Qualification of the Prior Art .................... 10
`
`Overview of Zydney (Ex. 1003) .............................................. 10
`
`Overview Appelman (Ex. 1004) .............................................. 15
`B. Ground 1: Claims 1, 3, and 13 Are Obvious Over Zydney .............. 19
`
`Claim 1 (Independent) ............................................................. 19
`(a)
`“A method for instant voice messaging over a
`packet-switched network, the method comprising:”
`(Preamble, Claim 1) ....................................................... 19
`(i)
`“A method for instant voice messaging” ............ 19
`(ii)
`“over a packet-switched network” ...................... 20
`-i-
`
`
`
`
`
`
`
`Table of Contents
`(continued)
`
`Page
`
`(b)
`(c)
`
`(d)
`
`(e)
`
`(f)
`
`(ii)
`
`(ii)
`
`“generating an instant voice message” (Claim 1[a]) ..... 22
`“wherein generating includes recording the instant
`voice message in an audio file and attaching one or
`more files to the audio file;” (Claim 1[b]) ..................... 26
`(i)
`“wherein generating includes recording the
`instant voice message in an audio file” ............... 26
`“… and attaching one or more files to the
`audio file” ............................................................ 27
`“transmitting the instant voice message having one
`or more recipients;” (Claim 1[c]) .................................. 30
`“receiving an instant voice message when a
`recipient is available; and” (Claim 1[d]) ....................... 34
`“receiving a temporarily stored instant voice
`message when a recipient becomes available,
`wherein the instant voice message is temporarily
`stored when at least one recipient is unavailable.”
`(Claim 1[e]) ................................................................... 35
`(i)
`“wherein the instant voice message is
`temporarily stored when at least one
`recipient is unavailable” ...................................... 35
`“receiving a temporarily stored instant voice
`message when a recipient becomes
`available” ............................................................. 38
`Claim 3 (Independent) ............................................................. 41
`(a)
`“A method for instant voice messaging over a
`packet-switched network, the method comprising:”
`(Preamble, Claim 3) ....................................................... 41
`“generating an instant voice message” (Claim 3[a]) ..... 41
`“controlling a method of generating the instant
`voice message based upon a connectivity status
`[sic; of] each recipient” (Claim 3[b]) ............................ 41
`
`(b)
`(c)
`
`-ii-
`
`
`
`
`
`
`
`
`
`
`
`
`
`Table of Contents
`(continued)
`
`Page
`
`(d)
`
`(e)
`
`(a)
`
`“transmitting the instant voice message having one
`or more recipients;” (Claim 3[c]) .................................. 44
`“receiving an instant voice message when a
`recipient is available; and” (Claim 3[d]) ....................... 44
`“receiving a temporarily stored instant voice
`message when a recipient becomes available,
`wherein the instant voice message is temporarily
`stored when at least one recipient is unavailable.”
`(Claim 3[e]) ................................................................... 45
`Claim 13 (Dependent) .............................................................. 45
`(a)
`“displaying an indication that an instant voice
`message has been received;” ......................................... 45
`“separating the instant voice message into an audio
`file and one or more files; and” (Claim 13[c]) .............. 47
`“playing the audio file.” (Claim 13[d]) ......................... 53
`(c)
`C. Ground 2: Claims 2 and 12 Are Obvious Over Zydney and
`Appelman ........................................................................................... 54
`
`Claim 2 (Independent) ............................................................. 54
`(a)
`“A method for instant voice messaging over a
`packet-switched network, the method comprising:”
`(Preamble, Claim 2) ....................................................... 54
`“receiving a list of nodes within the packet-
`switched network, the list of nodes including a
`connectivity status of each node, said connectivity
`status being available and unavailable, wherein a
`node within the list is adapted to be selected as a
`recipient of an instant voice message” (Claim 2[a]) ..... 54
`(i)
`“receiving a list of nodes within the packet-
`switched network” ............................................... 54
`“…the list of nodes including a connectivity
`status of each node, said connectivity status
`being available and unavailable” ........................ 56
`-iii-
`
`
`
`
`(b)
`
`(b)
`
`(ii)
`
`
`
`
`
`
`
`
`
`Table of Contents
`(continued)
`
`Page
`
`
`
`(c)
`(d)
`
`(iii) “wherein a node within the list is adapted to
`be selected as a recipient of an instant voice
`message;” ............................................................. 69
`“displaying said list of nodes;” (Claim 2[b]) ................. 73
`“transmitting the instant voice message having one
`or more recipients;” (Claim 2[c]) .................................. 73
`“receiving an instant voice message when a
`recipient is available; and” (Claim 2[d]) ....................... 73
`“receiving a temporarily stored instant voice
`message when a recipient becomes available,
`wherein the instant voice message is temporarily
`stored when at least one recipient is unavailable.”
`(Claim 2[e]) ................................................................... 74
`Claim 12 (Dependent) .............................................................. 74
`(a)
`“displaying an indication that an instant voice
`message has been received; and”................................... 74
`“playing the instant voice message.” ............................. 74
`(b)
`VIII. Conclusion .................................................................................................... 75
`
`
`(e)
`
`(f)
`
`
`
`
`
`
`
`-iv-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`List of Exhibits
`
`
`
`
`
`
`
`Description of Document
`Ex. No
`1001 U.S. Patent No. 8,199,747 to Michael J. Rojas
`1002 Declaration of Tal Lavian, Ph.D.
`1003
`PCT Patent Application No. PCT/US00/21555 to Herbert Zydney et
`al. (filed August 7, 2000, published February 15, 2001 as WO
`01/11824 A2) (with line numbers added)
`1004 U.S. Patent No. 6,750,881 to Barry Appelman
`1005
`Excerpts from Margaret Levine Young, Internet: The Complete
`Reference (2d ed. 2002)
`
`1006
`
`Prosecution File History for U.S. Patent No. 8,199,747, Amendment
`Under 37 C.F.R. § 1.111 (February 2, 2012)
`1007 U.S. Patent No. 6,757,365 B1 to Travis A. Bogard
`1008 N. Borenstein et al., Request for Comments (RFC) 1521: MIME
`(Multipurpose Internet Mail Extensions) Part One: Mechanisms for
`Specifying and Describing the Format of Internet Message Bodies,
`September 1993
`
`1009
`
`1010
`
`PCT Patent Application No. PCT/US00/21555 to Herbert Zydney et
`al. (filed August 7, 2000, published February 15, 2001 as WO
`01/11824 A2) (original)
`
`Excerpts of Joint Claim Construction and Prehearing Statement filed
`on March 10, 2017 in Case No. 16-cv-00642 (E.D. Tex.), including
`Exhibit A.
`
`-v-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`Facebook, Inc. and WhatsApp Inc. (“Petitioners”) respectfully submit this
`
`Petition for Inter Partes Review of claims 1-3, 12, and 13 of U.S. Patent No.
`
`8,199,747 (Ex. 1001) (“’747 patent”).
`
`I. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8(A)(1)
`A. Real Party-In-Interest under 37 C.F.R. § 42.8(b)(1)
`Facebook, Inc. and WhatsApp Inc. are the real parties-in-interest.
`
`B. Related Matters under 37 C.F.R. § 42.8(b)(2)
`The ’747 patent is the subject of two pending litigations involving the
`
`Petitioners: Uniloc USA, Inc., Uniloc Luxembourg, S.A. v. Facebook, Inc., Case No.
`
`6:16-cv-00728-JRG (E.D. Tex. filed July 5, 2016), and Uniloc USA, Inc., Uniloc
`
`Luxembourg, S.A. v. WhatsApp, Inc., Case No. 6:16-cv-00645-JRG (E.D. Tex. filed
`
`June 14, 2016), which have been consolidated for pretrial purposes with Uniloc USA,
`
`Inc. et al v. Samsung Electronics America, Inc., Case No. 16-cv-00642 (E.D. Tex.).
`
`The Petitioners are also aware of the following additional pending litigations
`
`involving the ’747 patent:; Uniloc USA, Inc. et al v. BlackBerry Corp. et al, Case
`
`No. 16-cv-00639 (E.D. Tex.); Uniloc USA Inc et al v. Line Euro-Americas Corp. et
`
`al, Case No. 16-cv-00641 (E.D. Tex.); Uniloc USA, Inc. et al. v. Tencent Am., LLC
`
`et al., Case No. 16-cv-00694 (E.D. Tex.); Uniloc USA, Inc. v. Snap Inc., Case No.
`
`16-cv-00696 (E.D. Tex.); Uniloc USA, Inc. et al v. AOL Inc., Case No. 16-cv-00722-
`
`JRG (E.D. Tex.); Uniloc USA, Inc. et al v. BeeTalk Private Ltd., Case No. 16-cv-
`
`
`
`
`
`-1-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`00725-JRG (E.D. Tex.); Uniloc USA, Inc. et al v. Green Tomato Ltd., Case No. 16-
`
`cv-00731-JRG (E.D. Tex.); Uniloc USA, Inc. et al v. Avaya Inc., Case No. 16-cv-
`
`00777 (E.D. Tex.); Uniloc USA, Inc. et al v. Vonage Holdings Corp. et al, Case No.
`
`16-cv-00893 (E.D. Tex.); Uniloc USA, Inc. et al v. Telegram Messenger, LLP, Case
`
`No. 16-cv-00892 (E.D. Tex.); Uniloc USA, Inc. et al v. Motorola Mobility LLC, Case
`
`No. 16-cv-00992 (E.D. Tex.); Uniloc USA, Inc. et al v. HTC America, Inc., Case No.
`
`16-cv-00989 (E.D. Tex.); Uniloc USA, Inc. et al v. HeyWire, Inc., Case No. 16-cv-
`
`01313 (E.D. Tex.); Uniloc USA, Inc. et al v. Google, Inc., Case No. 17-cv-00214
`
`(E.D. Tex.). Although the Petitioners are not parties to these other litigations,
`
`because they involve allegations of infringement of the ’747 patent, they may be
`
`impacted by a decision by the Board in this IPR proceeding.
`
`C. Lead and Back-Up Counsel under 37 C.F.R. § 42.8(b)(3)
`Petitioners provide the following designation of counsel.
`
`BACK-UP COUNSEL
`Phillip E. Morton (Reg. No. 57,835)
`pmorton@cooley.com
`zpatdcdocketing@cooley.com
`COOLEY LLP
`ATTN: Patent Group
`1299 Pennsylvania Avenue NW
`Suite 700
`Washington D.C. 20004
`Tel: (703) 456-8668
`Fax: (703) 456-8100
`
`
`
`-2-
`
`
`
`LEAD COUNSEL
`Heidi L. Keefe (Reg. No. 40,673)
`hkeefe@cooley.com
`zpatdcdocketing@cooley.com
`COOLEY LLP
`ATTN: Patent Group
`1299 Pennsylvania Avenue NW
`Suite 700
`Washington, DC 20004
`Tel: (650) 843-5001
`Fax: (650) 849-7400
`
`
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`LEAD COUNSEL
`
`
`
`
`
`BACK-UP COUNSEL
`Andrew C. Mace (Reg. No. 63,342)
`amace@cooley.com
`zpatdcdocketing@cooley.com
`COOLEY LLP
`ATTN: Patent Group
`1299 Pennsylvania Avenue NW
`Suite 700
`Washington, DC 20004
`Tel: (650) 843-5808
`Fax: (650) 849-7400
`
`D.
`Service Information
`This Petition is being served to the current correspondence address for the
`
`’747 patent, UNILOC USA INC., Legacy Town Center, 7160 Dallas Parkway, Suite
`
`380, Plano TX 75024. The Petitioners consent to electronic service at the addresses
`
`provided above for lead and back-up counsel.
`
`E.
`Power of Attorney
`Filed concurrently in accordance with 37 C.F.R. § 42.10(b).
`
`II.
`
`FEE PAYMENT - 37 C.F.R. § 42.103
`This Petition requests review of five (5) claims. A payment of $23,000 is
`
`submitted herewith, based on a $9,000 request fee (for up to 20 claims), and a post-
`
`institution fee of $14,000 (for up to 15 claims). This Petition meets the fee
`
`requirements of 35 U.S.C. § 312(a)(1).
`
`
`
`
`
`-3-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`III. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R. §§ 42.104
`AND 42.108
`A. Grounds for Standing under 37 C.F.R. § 42.104(a)
`The Petitioners certify that the ’747 patent is available for inter partes review
`
`and that the Petitioners are not barred or otherwise estopped from requesting inter
`
`partes review on the grounds identified herein.
`
`B.
`
`Identification of Challenge under 37 C.F.R. § 42.104(b) and
`Statement of Precise Relief Requested
`The Petitioners respectfully request that the Board initiate inter partes review
`
`of claims 1-3, 12, and 13 on the following grounds:
`
`Ground
`1
`2
`
`Claims
`1, 3, 13
`2, 12
`
`Basis for Challenge
`Unpatentable over Zydney (Ex. 1003), under § 103(a)
`Unpatentable over Zydney (Ex. 1003) in view of
`Appelman (Ex. 1004), under § 103(a)
`
`
`
`Part VII below explains why the challenged claims are unpatentable based
`
`on these grounds. Submitted with the Petition is the Declaration of Tal Lavian, Ph.D.
`
`(Exhibit 1002) (“Lavian”), a technical expert with decades of relevant technical
`
`experience. (Lavian, ¶¶ 1-10, Ex. A.)
`
`IV. TECHNOLOGY BACKGROUND RELEVANT TO A PERSON OF ORDINARY SKILL
`IN THE ART
`As explained by Dr. Lavian, a person of ordinary skill in the art for purposes
`
`of the ’747 patent would have possessed at least a bachelor’s degree in computer
`
`
`
`
`-4-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`science, computer engineering, or electrical engineering with at least two years of
`
`experience in development and programming relating to network communication
`
`systems (or equivalent degree or experience). (Lavian, ¶¶ 13-16.)
`
`As discussed in more detail below, the ’747 patent relates generally to instant
`
`messaging systems. The term “instant messaging” or “IM” generally refers to a
`
`technology that allows two or more people to exchange information with other users,
`
`including text, voice data, and/or files. (Id., ¶ 31.)
`
`Instant messaging technologies date back to at least the 1960s with the MIT
`
`“Interconsole Messages” system, which allowed users to exchange textual messages
`
`over a network. (Id., ¶ 33.) Through the 1980s and 1990s, companies such as
`
`CompuServe, Commodore, and America Online (AOL), among others, released
`
`instant messaging solutions to the public, some of which became immensely
`
`popular. (Id., ¶¶ 34-38.) For example, by 2002, AOL Instant Messenger (AIM), the
`
`instant messaging service offered by AOL, had more than 100 million registered
`
`users. (Id., ¶ 38.)
`
`The ’747 patent also acknowledges that instant messaging solutions were
`
`known in the art. The Background section of the patent explains that known instant
`
`messaging (“IM”) systems generally included client devices, IM software installed
`
`on those client devices, and IM servers. (’747, 2:30-34.) IM systems communicated
`
`over a packet-switched network, such as the Internet. (Id., 1:33-34, 2:30-34.) The
`
`
`
`
`
`-5-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`IM server maintained a list of users that were currently “online” and able to receive
`
`messages and presented this list to the users via the instant messaging software. (Id.,
`
`2:34-37; Lavian, ¶¶ 42, 43.) A user could select one or more recipients and send
`
`them a message. (’747, 2:38-40; Lavian, ¶¶ 31, 42, 43.) The IM server would
`
`transmit the message to the recipients and the message would be displayed to the
`
`recipients by the IM software. (’747, 2:40-42.)
`
`Instant messaging services typically required that the user have software (an
`
`IM client) that provides a user interface allowing a user to send messages to one or
`
`more recipients. The messages would typically be communicated to a server which
`
`would either deliver the message to the recipients, or store them at the server if the
`
`recipient was not currently available. (Lavian, ¶¶ 31, 42, 43.) IM clients typically
`
`varied in terms of what types of information they could transmit, how they indicate
`
`availability of other users, whether and how they secure the communications, and
`
`other details. (Id., ¶ 32.)
`
`V. THE ’747 PATENT
`The ’747 patent purports to describe a system and method for delivering
`
`instant voice messages over a packet-switched network. (’747, Abstract.) The
`
`disclosed system includes a client such as a VoIP telephone or PC computer
`
`“enabled for IP telephony” that is connected to a server and instant voice message
`
`(“IVM”) recipients through a network(s). (Id., 1:39-46, 2:56-67, 6:61-65.)
`
`
`
`
`
`-6-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`In one embodiment, when a user chooses to send an IVM, the IVM client
`
`displays a “list of one or more IVM recipients.” (Id., 7:61-64.) This recipient list is
`
`provided and stored by an IVM server. (Id.) Once recipients are selected, the user
`
`records a message, such as by using a microphone to record a digitized audio file.
`
`(Id., 8:3-7.) The patent states that one or more files may be attached to the instant
`
`voice message, such as by using a conventional “drag-and-drop” technique. (Id.,
`
`12:20-33, 13:28-33.)
`
`Once the voice message is generated, the client transmits the voice message
`
`to the server for delivery to one or more recipients. (Id., 8:17-25.) After receiving
`
`the instant voice message, the server transmits the voice message to the one or more
`
`recipients. (Id., 8:22-25.) If the recipient is “available” (currently connected to the
`
`IVM server), it will receive the instant voice message. (Id., 8:28-30.) If a recipient
`
`is unavailable (offline), the server temporarily saves the voice message and transmits
`
`it once the recipient becomes available. (Id., 8:30-35.) The recipient is notified of
`
`the new voice message and can play the audio file aloud. (Id., 8:25-28.) If the voice
`
`message had attachments, the recipient can also access the attached files. (Id., 12:64-
`
`13:4.)
`
`This Declaration addresses claims 1-3, 12, and 13. Claims 1-3 are
`
`independent claims; claim 12 depends from claim 2; and claim 13 depends from
`
`claim 1.
`
`
`
`
`
`-7-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`VI. CLAIM CONSTRUCTION UNDER 37 C.F.R. § 42.104(B)(3)
`The constructions below provide the broadest reasonable interpretation in
`
`light of the specification to a person of ordinary skill in the art.
`
`A.
`“node”
`Independent claim 2 recites the step of “receiving a list of nodes within the
`
`packet-switched network, the list of nodes including a connectivity status of each
`
`node, said connectivity status being available and unavailable, wherein a node
`
`within the list is adapted to be selected as a recipient of an instant voice message.”
`
`(’747, claim 2 (emphasis added).) The word “node” (or “nodes”) appears only in
`
`claim 2 and does not appear anywhere in the written description of the ’747 patent.
`
`The patent owner in the concurrent litigation involving the ’747 patent has
`
`proposed to define “node” as “potential recipient.” (Ex. 1010, Ex. A, at p.4, ¶ 5.)
`
`The Petitioners respectfully request that the Board adopt this definition as the
`
`broadest reasonable construction of “node” for purposes of this proceeding.
`
`The written description is generally consistent with this broadest reasonable
`
`construction. The portion of the specification that appears to correspond to the “list
`
`of nodes” recited in claim 2 describes providing a list of instant voice messaging
`
`(IVM) recipients, such as in the form of a contact list. (’747, 7:61-65 (“The IVM
`
`client 208 displays a list of one or more IVM recipients on its display 216, provided
`
`and stored by the local IVM server 202.”), 8:48-52, 9:32-35, 10:17-19, 13:58-62
`
`
`
`
`
`-8-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`(“The users are represented in the database as records, each record comprising a user
`
`name, a password, and a contact list (a list of other users with whom the user wishes
`
`to exchange instant voice messages), and other data relating to the user.”).) The ’747
`
`patent further states:
`
`[T]he IVM client 208 requests from the global IVM server 502 a global
`contact list (not shown) of global one or more IVM recipients with
`which the IVM client 208 may exchange instant voice messages. . . .
`The global IVM server system 502 stores and maintains this contact
`list. Thus, the global IVM server system 502 responds by transmitting
`the contact list to the IVM client 208. The IVM client 208 displays the
`contact list on its display 216. Alternatively, the is global contact list
`may 65 be replicated to the local IVM server 202 within the local IVM
`system 510, in which case the local IVM client 208 obtains the global
`contact list from the local IVM server 202.
`
`(’747, 15:56-16:1 (underlining added).) In light of the description in the written
`
`description, the Petitioners respectfully request that the Board interpret “node”
`
`under its broadest reasonable construction as “potential recipient.”1
`
`VII. CLAIMS 1-3, 12, AND 13 ARE UNPATENTABLE
`Claims 1-3, 12, and 13 are unpatentable based on the following grounds:
`
`
`1 The Petitioners reserve their right to argue that “node” is indefinite under the
`
`narrower claim construction standards applicable in the concurrent litigation.
`
`
`
`
`
`-9-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`
`Basis for Challenge
`Ground Claims
`1
`1, 3, 13 Unpatentable over Zydney (Ex. 1003), under § 103(a)
`2
`2, 12
`Unpatentable over Zydney (Ex. 1003) in view of Appelman
`(Ex. 1004), under § 103(a)
`
`This Petition will first provide an overview of each reference.
`
`A. Brief Summary and Date Qualification of the Prior Art
` Overview of Zydney (Ex. 1003)
`Zydney is a published PCT application that describes a system for voice
`
`communication that enables a user to send instant voice messages, which Zydney
`
`calls “voice containers.” (Zydney, Ex, 1003, 2:2-3.) The system transmits the voice
`
`containers “instantaneously or stored for later delivery,” depending on whether or
`
`not the recipient is currently online. (Id., 1:19-22, 15:8-21.) Zydney qualifies as
`
`prior art vis-à-vis the ’747 patent under 35 U.S.C. § 102(b) (pre-AIA) because
`
`Zydney was published on February 15, 2001, more than one year before the earliest
`
`patent application filing date for the ’747 patent.
`
`The Petitioners also note that the Zydney reference contains page numbers but
`
`does not contain line numbers. Accordingly, for convenience of the Board and ease
`
`of reference, Exhibit 1003 to this Petition contains a copy of Zydney in which line
`
`numbers have been added to the left of each page (beginning on page 1), to facilitate
`
`precise citation to the passages of the reference cited in this Petition. Any citations
`
`to line numbers of Zydney in this Petition and in the Lavian Declaration, therefore,
`
`
`
`
`-10-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`refer to these added line numbers as shown in Exhibit 1003. A copy of the original
`
`Zydney reference without line numbers is submitted as Exhibit 1009.
`
`The system of Zydney is generally shown in Figure 1A, reproduced below.
`
`
`
`
`
`
`
`-11-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`(Id., Fig. 1A.)2
`
`Three key components of the system include the “SENDER PC SOFTWARE
`
`AGENT” shown on the left (22), the “RECIPIENT PC SOFTWARE AGENT”
`
`shown on the right (28), and the “CENTRAL SERVER” shown in the middle (24)
`
`of Figure 1A. (Id., 10:19-11:1.) Zydney explains that the sender and recipient
`
`software agents may work on any suitable client device such as “a personal
`
`computer, wireless handheld computer such a personal data assistant (PDA), digital
`
`telephone, or beeper.” (Id., 11:14-20.) Central server (24) facilitates instant voice
`
`messaging between the sender and the recipient. (Id., 10:20-11:1.) The sender,
`
`recipient, and central server communicate with each other using a communications
`
`network, as shown with the bottom cloud labeled “INTERNET” in Figure 1A. (Id.,
`
`Fig. 1A; see also id., 5:4-5, 5:15-18, 10:11-14, 14:2-5.)3
`
`
`2 All highlighting in reproduced figures, and all underlining in any quotations, have
`
`been added unless otherwise noted.
`
`3 Figure 1A also depicts an alternative embodiment in which a sender and recipient
`
`can communicate using phones (32, 34) connected over the Public Switched
`
`Telephone Network (PSTN). This Petition will focus on the Internet-connected
`
`embodiment described in the text.
`
`
`
`
`
`-12-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`Sending a voice instant message from a sender to a recipient in Zydney is
`
`straightforward. A message sender (originator) “selects one or more intended
`
`recipients from a list of names that have been previously entered into the software
`
`agent.” (Id., 14:17-19.) The sender also “digitally records messages for one or more
`
`recipients using a microphone-equipped device and the software agent. The
`
`software agent compresses the voice and stores the file temporarily on the PC if the
`
`voice will be delivered as an entire message.” (Id., 16:1-4; see also id., 20:11-14,
`
`21:11-16 (describing “the recording of one or more voice packet messages on a
`
`personal computer” as “voice files [that] can be played and recorded using voice
`
`container enabled devices.”).) The voice message is placed into a “voice
`
`container,” which can be transmitted to the destination. (Id., 10:20-11:3.)
`
`Zydney describes at least two modes in which voice messages can be
`
`transmitted: a “pack and send” mode and an “intercom” mode. This Petition will
`
`focus primarily on the “pack and send” mode as it is more pertinent to the challenged
`
`claims of the ’747 patent.
`
`Zydney explains that “[a] pack and send mode of operation is one in which
`
`the message is first acquired, compressed and then stored in a voice container 26
`
`which is then sent to its destination(s).” (Id., 11:1-3; see also id., Fig. 4.) The
`
`software agent compresses and stores the voice message file, which Zydney refers
`
`to as a “voice container,” on the client device. (Id., 16:3-4, 12:1-8, 10:20-11:3.) The
`
`
`
`
`
`-13-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`sender also can include “multimedia attachments” with the voice message, such as
`
`graphics. (Id., 19:2-8, 22:17-20, Fig. 6.) The software agent then transmits the voice
`
`container (and any attachments) to either the central server for delivery or,
`
`alternatively, directly to the recipient. (Id., 12:1, 12:20-23, 16:7-10.)
`
`If the recipient is online, it receives the voice container immediately. (Id.,
`
`1:21-22 (“routed to the appropriate recipients instantaneously.”).) If the recipient is
`
`offline, the server stores the voice container until the recipient is available, as shown
`
`in Figure 4. (Id., 13:12-15, 14:9-11, Fig. 4 (“if recipient is not online, client sends
`
`voice container to server file”).) The central server can later forward the stored voice
`
`container to the recipient once it logs in. (Id., claim 1, 14:14-16, Fig. 4 (“recipient
`
`logs on to internet or intranet,” “server recognizes recipient, downloads voice
`
`container”), 16:10-12 (“If the intended recipient has a compatible active software
`
`agent on line after log on, the central server downloads the voice recording almost
`
`immediately to the recipient.”).)
`
`Once the recipient’s software agent receives the voice container, it unpacks
`
`the voice container and any attachments, and presents them to the recipient. (Id.,
`
`Fig. 18, 35:20-22.) The software agent can then audibly play the voice message to
`
`the recipient through the speakers or headset attached to the device. (Id., 13:19-22,
`
`14:14-16, 16:10-14.)
`
`
`
`
`
`-14-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
` Overview Appelman (Ex. 1004)
`Appelman, entitled “User Definable On-Line Co-User Lists,” is an issued
`
`United States patent, originally assigned to America Online, describing an instant
`
`messaging system that keeps track of the logon status of users.4 (Appelman, Ex.
`
`1004, Abstract.) This Petition cites Appelman for its teachings regarding a “list of
`
`nodes” as recited in claim 2 for Ground 2. Appelman qualifies as prior art to the
`
`’747 patent under 35 U.S.C. § 102(e) (pre-AIA) because it issued from an application
`
`filed in the United States on February 24, 1997, which is before the earliest patent
`
`application filing date for the ’747 patent.
`
`Appelman describes a technique for allowing a user to create a list of users
`
`called a “Buddy List,” which records the names of selected other co-users with
`
`whom the user may wish to communicate. (Id., 1:53-59, Fig. 3.) The buddy list also
`
`keeps track of whether the other co-users are currently logged onto the system.
`
`“When a user logs on to a system, the user’s set of buddy lists is presented to the
`
`buddy list system. The buddy list system attempts to match co-users currently
`
`logged into the system with the entries on the user’s buddy list. Any matches are
`
`displayed to the user. As co-users logon and logoff, a user’s buddy list is updated to
`
`reflect these changes.” (Id., 1:64-2:2; see also id., 2:51-3:6.)
`
`
`4 Appelman is current assigned to Petitioner Facebook, Inc.
`
`-15-
`
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`Figure 2a of Appelman, reproduced below, shows an example Buddy List
`
`table 32 that records the screen name of each “buddy” user as well as the connectivity
`
`status of each user (whether the user is logged “in” or logged “out”).
`
`
`
`(Appelman, Fig. 2a.) Appelman explains that each user can create different buddy
`
`lists. (Id., 3:61-64.) In the example above, the user has created two buddy lists
`
`(“Home List” and “Work List”). The buddy list called “Home List” contains the
`
`name/address and logon status for three users: “John Smith,” “Jane Doe” and
`
`“Simon Roe.” (Id., Fig. 2a, 3:41-47.) For each user, the table indicates either “IN”
`
`
`
`
`
`-16-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`to indicate that the user is currently logged into the system, or “OUT” to indicate
`
`that the user is not logged in. (Id., 3:43-47, 4:4-7.)
`
`When a user logs in, the system presents a user interface that displays the
`
`buddy list, including the name and connectivity status of each co-user on the list.
`
`(Id., 2:66-3:8, 4:28-36.) Figure 3 below shows an exemplary user interface for the
`
`“Home List” buddy list shown in Figure 2a above:
`
`
`
`
`
`-17-
`
`
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,199,747
`
`
`
`
`