throbber
Trials@uspto.gov
`571.272.7822
`
`Paper No. 40
`
` Filed: January 31, 2019
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`SAMSUNG ELECTRONICS AMERICA, INC.,
`Petitioner,
`
`v.
`
`UNILOC 2017 LLC,
`Patent Owner.
`
`____________
`
`Case IPR2017-01799
`Patent 8,199,747 B2
`____________
`
`
`Before JENNIFER S. BISK, MIRIAM L. QUINN, and
`CHARLES J. BOUDREAU, Administrative Patent Judges.
`
`BISK, Administrative Patent Judge.
`
`
`
`
`FINAL WRITTEN DECISION
`35 U.S.C § 318(a) and 37 C.F.R. § 42.73
`
`
`
`I.
`
`INTRODUCTION
`
`Samsung Electronics America, Inc. (“Petitioner”) filed a Petition
`
`requesting inter partes review of claims 1–3, 12, and 13 (“challenged
`
`claims”) of U.S. Patent No. 8,199,747 B2 (Ex. 1001, “the ’747 patent”).
`
`
`
`
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`Paper 1 (“Pet.”). Uniloc 2017, LLC (“Patent Owner”) filed a Preliminary
`
`Response. Paper 7 (“Prelim. Resp.”). We instituted this review as to all
`
`challenged claims. Paper 9 (“Inst. Dec.”) (instituting claims 2 and 12);
`
`Paper 16 (“Post-SAS Order”) (modifying the institution decision to include
`
`all challenged claims).
`
`Subsequent to institution, Patent Owner filed a Patent Owner
`
`Response. Paper 21 (“PO Resp.”). Petitioner filed a Reply. Paper 24
`
`(“Reply”). Patent Owner also filed a Motion to Exclude (Paper 28),
`
`Petitioner opposed (Paper 31), and Patent Owner filed a Reply (Paper 32).
`
`A transcript of the oral hearing held on October 30, 2018, has been entered
`
`into the record as Paper 39 (“Tr.”).
`
`This Final Written Decision is entered pursuant to 35 U.S.C. § 318(a).
`
`For the reasons that follow, Petitioner has demonstrated by a preponderance
`
`of the evidence that claims 1–3, 12, and 13 of the ’747 patent are
`
`unpatentable.
`
`A. Related Matters
`
`
`
`Petitioner represents that the ’747 patent is the subject of numerous
`
`ongoing actions before the U.S. District Court for the Eastern District of
`
`Texas, including an action filed against Petitioner (Case No. 2-16-cv-
`
`00638). Pet. 1–5; see Paper 3, 2–3; Paper 14, 1; Paper 15, 1; Paper 26, 1–2.
`
`Before the Office, the ’747 patent also was the subject of Cases
`
`IPR2017-01257 and IPR2017-02085, in which we denied institution, and
`
`Case IPR2018-00748, in which we terminated the Petition prior to a decision
`
`on institution. IPR2017-01257, Paper 8 (Dec. 4, 2017); IPR2017-02085,
`
`Paper 11 (April 16, 2018); IPR2018-00748, Paper 13 (Sept. 7, 2018).
`
`
`
`2
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`B. The ’747 Patent
`
`The ’747 patent, titled “System and Method for Instant VoIP
`
`Messaging,” relates to Internet telephony, and more particularly, to instant
`
`voice over IP (“VoIP”) messaging over an IP network, such as the Internet.
`
`Ex. 1001, [54], 1:14–18. The ’747 patent acknowledges that “[v]oice
`
`messaging” and “instant text messaging” in both the VoIP and public
`
`switched telephone network environments were previously known. Id. at
`
`2:18–42. In prior art instant text messaging systems, according to the ’747
`
`patent, a server would present a user of a client terminal with a “list of
`
`persons who are currently ‘online’ and ready to receive text messages,” the
`
`user would “select one or more” recipients and type the message, and the
`
`server would immediately send the message to the respective client
`
`terminals. Id. at 2:30–42. According to the ’747 patent, however, “there is
`
`still a need in the art for . . . a system and method for providing instant VoIP
`
`messaging over an IP network,” such as the Internet. Id. at 2:43–47. The
`
`invention of the ’747 patent is thus directed to such a system and method.
`
`Id. at 1:15–18, 6:43–45.
`
`In one embodiment, the ’747 patent discloses local instant voice
`
`messaging (“IVM”) system 200, depicted in Figure 2 below. Id. at 6:18–20.
`
`
`
`3
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`
`
`
`
`As illustrated in Figure 2, local packet-switched IP network 204,
`
`which may be a local area network (“LAN”), “interconnects” IVM
`
`clients 206, 208 and legacy telephone 110 to local IVM server 202. Id.
`
`at 6:46–65; see id. at 7:19–20, 7:57–61. Local IVM server 202 enables IVM
`
`functionality over network 204. Id. at 7:57–61.
`
`In “record mode,” IVM client 208 “displays a list of one or more IVM
`
`recipients,” provided and stored by local IVM server 202, and the user
`
`selects recipients from the list. Id. at 7:53–55, 7:61–67. IVM client 208
`
`then transmits the selections to IVM server 202 and “records the user’s
`
`speech into . . . digitized audio file 210 (i.e., an instant voice message).” Id.
`
`at 8:1–7.
`
`When the recording is complete, IVM client 208 transmits audio
`
`file 210 to local IVM server 202, which delivers the message to the selected
`
`recipients via local IP network 204. Id. at 8:1125. “[O]nly the available
`
`
`
`4
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`IVM recipients, currently connected to . . . IVM server 202, will receive the
`
`instant voice message.” Id. at 8:2930. IVM server 202 “temporarily saves
`
`the instant voice message” for any IVM client that is “not currently
`
`connected to . . . local IVM server 202 (i.e., is unavailable)” and “delivers
`
`it . . . when the IVM client connects to . . . local IVM server 202 (i.e., is
`
`available).” Id. at 8:30–35; see id. at 9:13–17. Upon receiving the instant
`
`voice message, the recipients can audibly play the message. Id. at 8:25–28.
`
`C. Illustrative Claims
`
`Of the challenged claims, claims 1–3 are independent. Those claims
`
`are reproduced below:
`
`1. A method for instant voice messaging over a
`packet-switched network, the method comprising:
`generating an instant voice message, wherein generating
`includes recording the instant voice message in an audio file
`and attaching one or more files to the audio file;
`transmitting the instant voice message having one or more
`recipients;
`receiving an instant voice message when a recipient is
`available; and
`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.
`
`2. A method for instant voice messaging over a
`packet-switched network, the method comprising:
`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;
`displaying said list of nodes;
`transmitting the instant voice message having one or more
`recipients;
`
`
`
`5
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`receiving an instant voice message when a recipient is
`available; and
`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.
`
`3. A method for instant voice messaging over a packet-switched
`network, the method comprising:
`generating an instant voice message; and
`controlling a method of generating the instant voice message
`based upon a connectivity status each recipient;
`transmitting the instant voice message having one or more
`recipients;
`receiving an instant voice message when a recipient is
`available; and
`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.
`
`Ex. 1001, 23:55–24:29.
`
`D. Evidence of Record
`
`The Petition relies upon the following asserted prior art references:
`
`U.S. Patent No. 8,150,922 B2 (issued April 3, 2012) (Ex. 1005,
`“Griffin”);
`
`International Application Publication No. WO 01/11824 A2 (published
`Feb. 15, 2001) (Ex. 1006, “Zydney”);
`
`In addition, Petitioner supports its contentions with the Declaration of
`
`Dr. Zygmunt J. Haas. Ex. 1002. In response, Patent Owner proffers the
`
`Declaration of Mr. William C. Easttom II. Ex. 2001.
`
`
`
`6
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`E. Asserted Grounds of Unpatentability
`
`Petitioner challenges the patentability of claims 1–3, 12, and 13 under
`
`35 U.S.C. § 103 over the combination of Griffin and Zydney. Pet. 6.
`
`II. ANALYSIS
`
`A. Level of Ordinary Skill
`
`Citing Dr. Haas’s testimony, Petitioner proposes that a “person of
`
`ordinary skill in the art at the time of the alleged invention . . . would have
`
`had at least a bachelor’s degree in computer science, computer engineering,
`
`electrical engineering, or the equivalent and at least two years of experience
`
`in the relevant field, e.g., network communication systems.” Pet. 7–8 (citing
`
`Ex. 1002 ¶¶ 15–16). Petitioner further states that “[m]ore education can
`
`substitute for practical experience and vice versa.” Id. Patent Owner’s
`
`declarant, Mr. Easttom, similarly testifies that a person of ordinary skill in
`
`the art is “someone with a baccalaureate degree related to computer
`
`technology and 2 years of experience with network communication
`
`technology, or 4 years of experience without a baccalaureate degree.” PO
`
`Resp. 4 (citing Ex. 2001 ¶ 16).
`
`The principal difference between the parties’ proposed qualifications
`
`is that, as an alternative to an undergraduate degree and two years of
`
`relevant work experience, Patent Owner’s proposal allows for a specific
`
`number of years of experience as a substitute for an undergraduate degree,
`
`while Petitioner’s proposal is vague in this regard. Based on our review of
`
`the ’747 patent and the prior art of record, we find that Patent Owner’s
`
`proposal is more precise as it takes into account a level of experience of four
`
`years with network communication technology without the undergraduate
`
`
`
`7
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`degree. We, therefore, adopt Patent Owner’s expression of the level of skill
`
`in the art, which encompasses both alternative sets of qualifications.
`
`B. Claim Construction
`
`The Board interprets claim terms of an unexpired patent using the
`
`broadest reasonable construction in light of the specification of the patent.
`
`37 C.F.R. § 42.100(b) (2017).1
`
`In the Institution Decision, we adopted a construction of the term
`
`“node” as encompassing a “potential recipient.” Inst. Dec. 7–9. We also
`
`noted that we did not “understand Petitioner’s contentions of unpatentability
`
`in this case to be based on a reading of a ‘potential recipient’—and hence a
`
`‘node’—to be ‘a person.’” Id. at 9 (citing Pet. 45–57). During trial, Patent
`
`Owner renews its arguments relating to the construction of the term “node.”
`
`PO Resp. 5–8. Patent Owner also raises a dispute concerning the scope of
`
`the term “instant voice message.” Id. at 8, 30–33. We address each of these
`
`issues in turn.
`
`1. Node
`
`Claim 2 recites “nodes” that are “within the packet-switched
`
`network,” and that have a connectivity status of available and unavailable.
`
`Ex. 1001, 24:3–6. Patent Owner proposes that a “node” is a device within
`
`the packet-switched network, given the clear claim language that the nodes
`
`are “within the packet-switched network.” PO Resp. 6–7. Patent Owner
`
`also proffers a dictionary definition of “node,” in the computer network
`
`
`1 A recent amendment to this rule does not apply here, because the Petition
`was filed before November 13, 2018. See “Changes to the Claim
`Construction Standard for Interpreting Claims in Trial Proceedings Before
`the Patent Trial and Appeal Board,” 83 Fed. Reg. 51,340 (Oct. 11, 2018) (to
`be codified at 37 C.F.R. pt. 42).
`
`
`
`8
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`context, as a “terminal in a computer network.” Id. at 8 (citing Ex. 2003, 3).
`
`Patent Owner contends that we must determine whether the “node” is a
`
`device, because, according to Patent Owner, Petitioner has mapped claim 1’s
`
`“nodes” to “persons,” instead of devices. Id. Petitioner asserts that no
`
`construction is necessary to explicitly require a device. Reply 1.
`
`Given Patent Owner’s insistence that Petitioner identified “persons”
`
`as “nodes,” we construe the term “node” to be a device, not a person. The
`
`plain and ordinary meaning of the claim is paramount to our conclusion that
`
`the “node” is a device. The language refers to “nodes within the packet-
`
`switched network.” Ex. 1001, 24:34. This unambiguously puts the “node”
`
`in the environment of a network, where devices communicate with each
`
`other. See Ex. 2003, 3 (defining node, in the computer science sense, as “A
`
`terminal in a computer network.”). Accordingly, Patent Owner is correct
`
`that a “node” is a “device.”
`
`2. Instant Voice Message
`
`“instant”
`
`Patent Owner argues that the “instant voice message” is “instant”
`
`because there is an “expectation” that “a person on the receiving end of an
`
`‘instant voice message’” will receive it in real time. PO Resp. 32. Patent
`
`Owner challenges Petitioner’s assertion that a voice message is “instant”
`
`because it is a voice message transmitted in real time to an available
`
`recipient. Id. at 30–33 (citing Pet. 19). Petitioner argues that the
`
`Specification does not support Patent Owner’s contention because of an
`
`embodiment in which the instant voice message is stored at the central
`
`server for delivery, when the recipient becomes available. Reply 5–6.
`
`
`
`9
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`We agree with Patent Owner that merely transmitting the “instant
`
`voice message” in real time is insufficient to define the “instant” feature of
`
`an “instant voice message.” As noted by Patent Owner, the Background of
`
`the Invention purposely distinguishes a voice mail message from an
`
`“instant” text message. Ex. 1001, 2:1842. In the voice mail message
`
`example, the Specification describes the drawbacks of dialing a telephone
`
`number, and after a few more steps, finally “recording the message for later
`
`pickup by the recipient.” Id. at 2:2228 (emphasis added). In contrast, for
`
`an “instant” text message, a server presents the user with “a list of persons
`
`who are currently ‘online’ and ready to receive text messages on their own
`
`client terminals.” Id. at 2:3437 (emphasis added). “The text message is
`
`sent immediately via the text messaging server to the selected one or more
`
`persons and is displayed on their respective client terminals.” Id. at
`
`2:4042. That is, with a voice mail message, a person on the receiving end,
`
`who admittedly was not ready to engage in a direct voice conversation, must
`
`take an active step to retrieve the recorded message, regardless of when the
`
`message was recorded. In contrast, the “instant” text message is
`
`immediately transmitted to the recipient, which is ready to receive it, thus
`
`ensuring a speedy arrival. Thus, the Specification distinguishes a voice mail
`
`message from the “instant” text message in that, although both message are
`
`recorded and transmitted, only the “instant” text message, as the word
`
`“instant” implies, confers immediacy to its receipt by a ready recipient. The
`
`“instant” in the “instant voice message” imparts the same speedy receipt.
`
`Our conclusion that an “instant” voice message must involve this
`
`immediate transmission and, likewise, speedy reception of the message is
`
`not diminished by embodiments that store the message at the server for later
`
`
`
`10
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`delivery. See Ex. 1001, 8:3035 (“[I]f a recipient IVM client is not
`
`currently connected to the local IVM server 202 (i.e., is unavailable), the
`
`IVM server temporarily saves the instant voice message and delivers it to the
`
`IVM client when the IVM client connects to the local IVM server 202 (i.e.,
`
`is available).”). Neither the sender nor the recipients can have any
`
`expectation with regard to the timing of the message’s receipt when the
`
`recipients are not online, and thus, not available to receive the message.
`
`Indeed, this same embodiment carries out the “instant” capability by
`
`delivering the message stored at the server to the client, when the client
`
`connects to the server, thus becoming available to receive it. Consequently,
`
`we agree with Patent Owner that an “instant voice message” is one that is
`
`transmitted in real time and received accordingly, when the recipient is
`
`available.
`
`“attaching”
`
`Patent Owner makes another argument concerning the scope of
`
`“instant voice message,” the issue revolves around what it means to attach a
`
`file to an audio file. PO Resp. 2226. Patent Owner’s argument relies on
`
`the portion of the Board’s Institution Decision where we determined, for
`
`claim 1, that Petitioner had not shown a reasonable likelihood of prevailing
`
`in its challenge of unpatentability because the claim requires an attachment
`
`to the audio file, rather than attachment to the instant voice message. Id.
`
`Our Institution Decision did not provide a construction for either “instant
`
`voice message” or the “attaching” claim limitation. Inst. Dec. 6–9. We note
`
`here that our discussion of claim 1 in our Institution Decision is not binding,
`
`and we may change our view after review of the full record. “[T]he Board is
`
`not bound by any findings made in its Institution Decision. At that point, the
`
`
`
`11
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`Board is considering the matter preliminarily without the benefit of a full
`
`record. The Board is free to change its view of the merits after further
`
`development of the record, and should do so if convinced its initial
`
`inclinations were wrong.” TriVascular, Inc. v. Samuels, 812 F.3d 1056,
`
`1068 (Fed. Cir. 2016).
`
`Since our institution determination, we have had occasion to revisit
`
`the claim language regarding the “attaching” issue, and have found that the
`
`scope of the word is broader than our initial assessment. In a set of related
`
`inter partes reviews, we expressly construed the terms “instant voice
`
`message” and “attaching” to resolve the dispute of whether attaching one or
`
`more files to an instant voice message was different from attaching one or
`
`more files to an audio file. See Final Written Decision, Facebook, Inc., v.
`
`Uniloc 2017 LLC, Case IPR2017-01428, Paper 40, *1221 (PTAB
`
`November 30, 2018). Part of that analysis is relevant here also, and where
`
`appropriate is included below.2
`
`Claim 1 of the ’747 patent recites that generating an instant voice
`
`message includes “attaching one or more files to the audio file.” Ex. 1001,
`
`23:59. Although this claim requires attaching one or more files to “an audio
`
`file,” we note that related patents recite attaching one or more files to an
`
`“instant voice message” instead. For instance, claim 9 of U.S. Patent No.
`
`
`2 We also previously construed “instant voice message” as data content
`including a representation of an audio message. Facebook, Inc., v. Uniloc
`2017 LLC, Case IPR2017-01428, slip op. at 1218, (PTAB November 30,
`2018) (Paper 40). There is no dispute in this proceeding concerning the
`content or structure of the “instant voice message,” save for the issue of how
`an attachment of one or more files is accomplished. Accordingly, we need
`not incorporate here our previous construction of “instant voice message” as
`“data content.”
`
`
`
`12
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`8,995,433, which shares the same disclosure with the ’747 patent, recites
`
`that “instant voice message application attaches one or more files to the
`
`instant voice message.” We include this claim language in our discussion to
`
`highlight that the words “attaching” or “attached” are recited with respect to
`
`both an “instant voice message” and an “audio file.”
`
`We start with the claim language. As noted above, the claims of the
`
`’747 patent require attachment of one or more files to an audio file. No
`
`other claim of the ’747 patent recites “attaching” or informs us as to the
`
`scope of that word. As to the Specification, “attachment” is described as
`
`follows:
`
`is enabled
`The attachment of one or more files
`conventionally via a methodology such as “drag-and-drop”
`and the like, which invokes the document handler 306 to
`make the appropriate linkages to the one or more files and
`flags the messaging system 320 that the instant voice
`message also has the attached one or more files.
`
`Ex. 1001, 13:2833. This passage also describes that, in addition to making
`
`linkages, flags alert the messaging system in the client device that the instant
`
`voice message has an attachment. Thus, “attaching” creates an association
`
`between the one or more files and the instant voice message so that the
`
`system, once alerted, may transmit the instant voice message with the
`
`associated one or more files. This passage describes the attachment of files
`
`to an instant voice message in the “record mode,” i.e., when the “instant
`
`voice message” is recorded in an audio file. Id. at 13:528 (describing how
`
`the audio file is recorded and processed before transmission, including
`
`giving the user options to attach documents). The Specification provides no
`
`other detailed description of how to attach a file to either an “instant voice
`
`
`
`13
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`message” or an “audio file.” It seems reasonable, therefore, that, in reciting
`
`attachment to an “instant voice message,” when dealing with the audio file
`
`form of that message, the Specification supports that attachment to an “audio
`
`file” is synonymous with attachment to an “instant voice message,” because
`
`those claims would be referring to the “record mode.” Claim 1, in contrast,
`
`recites attaching to an “audio file.” Thus, this claim is directed to an “instant
`
`voice message” that is in the form of an “audio file.”
`
`The Specification passage identified above describes “attachment” of
`
`one or more files to an instant voice message that, in “record mode,” is an
`
`audio file, and also describes that the “attachment” is made by providing
`
`some indication (e.g., linkages) that another file (or files) is associated with
`
`the instant voice message or the audio file. This conclusion –that
`
`“attaching” is associating—is also confirmed by credible expert testimony
`
`on a person of ordinary skill in the art’s understanding of the conventional
`
`methods of effecting “attachments” at the time of the invention. See Ex.
`
`1040, 135:9137:13, 139:519. For instance, Mr. Easttom testified that,
`
`under conventional methods, two files would be considered “attached” if the
`
`recipient device knows that those two documents are associated or where
`
`“additional information” that indicates the association (that “they go
`
`together”) is added to the attachment and the message. Id.
`
`The discussion above brings us to the issue Patent Owner raises of
`
`whether attachment must be to the audio file itself. PO Resp. 30. Patent
`
`Owner urges us to construe the “attached to” phrase (and its variants) very
`
`narrowly. For example, Patent Owner argues that attaching to the audio file
`
`is different than attaching to a structure that is used to transport that audio
`
`file. Id. at 23 (arguing that attaching a file to a data container is
`
`
`
`14
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`distinguishable from attaching one or more files to an audio file). The
`
`argument implies that an “attachment” requires some direct physical
`
`appendage or some particular joining of the one or more files and the audio
`
`file. The Specification describes “attaching” broadly, however, as making
`
`appropriate linkages to the one or more files (the attachments), not the audio
`
`file. There is no disclosure of any appendage to the audio file, no alteration
`
`of the audio file to include additional data, and no particular information
`
`provided to the messaging system to carry out the attachment to the audio
`
`file itself. Rather, the Specification describes generally the use of linking
`
`and the flags as the means by which the system handles the one or more files
`
`as attachments of the “instant voice message,” which is in the form of an
`
`audio file, in the embodiment encompassed by claim 1. The tangible
`
`difference between an audio file with an attachment and one without seems
`
`to be in whether the document handler has sufficiently linked the attachment
`
`and whether the flags inform the client system to associate the attachment
`
`for effective transmission to the server. Thus, as long as the client has
`
`sufficient information that the audio file has an attachment, the recited
`
`“attachment” is performed. The particular manner of associating the one or
`
`more files with the audio file—such as whether links, flags, or other like
`
`information is used—is irrelevant, as such details are not recited expressly.
`
`Based on our review of the claim language, the Specification, and the
`
`parties’ arguments on claim construction, we determine that under the plain
`
`and ordinary meaning in the context of the Specification, as explained
`
`above, “one or more files attached to an audio file” means indicating that
`
`another file (or files) is associated with the audio file.
`
`
`
`15
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`C. Alleged Obviousness over Griffin and Zydney
`
`Petitioner argues Griffin and Zydney render obvious claims 1–3, 12,
`
`and 13. Pet. 17–70.
`
`1. Overview of Griffin
`
`
`
`Griffin, titled “Voice and Text Group Chat Display Management
`
`Techniques for Wireless Mobile Terminals,” relates to a technique of
`
`managing the display of “real-time speech and text conversations (e.g., chat
`
`threads) on limited display areas.” Ex. 1005, [54], 1:9−11. Griffin discloses
`
`a wireless mobile terminal as shown in Figure 1, reproduced below.
`
`
`
`Figure 1, above, depicts mobile terminal 100 comprising speaker 103,
`
`which renders signals such as received speech audible; display 102 for
`
`rendering text and graphical elements visible; navigation rocker 105, which
`
`allows a user to navigate a list or menu displayed on the screen; microphone
`
`107, for capturing the user’s speech; and push-to-talk button 101, which
`
`allows the user to initiate recording and transmission of audio. Id. at
`
`
`
`16
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`3:14−30. Griffin also describes, in connection with Figure 2, reproduced
`
`below, the overall system architecture of a wireless communication system
`
`where the mobile terminals communicate with a chat server complex. Id. at
`
`3:49−51.
`
`
`
`Figure 2, above, illustrates wireless carrier infrastructures 202, which
`
`support wireless communications with mobile terminals 100, such that the
`
`mobile terminals wirelessly transmit data to a corresponding infrastructure
`
`202 for sending the data packets to communication network 203, which
`
`forwards the packets to chat server complex 204. Id. at 3:49−61.
`
`Communication network 203 is described as a “packet-based network,
`
`[which] may comprise a public network such as the Internet or World Wide
`
`Web, a private network such as a corporate intranet, or some combination of
`
`public and private network elements.” Id. at 3:61−65.
`
`Griffin’s chat server complex 204 receives encoded data comprising
`
`text, speech, and/or graphical messages (or some combination thereof),
`
`when a plurality of users chat together (i.e., send chat messages from one
`
`
`
`17
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`terminal 100 to another). Id. at 4:11−15, 4:62−65. An outbound chat
`
`message, for example, is decomposed to locate the list of recipients, and the
`
`recipient’s current status is determined. Id. at 5:9−15. Griffin describes
`
`presence status 702 as “an indicator of whether the recipient is ready to
`
`receive the particular type of message, speech and/or text messages only,
`
`etc.).” Id. “When presence status 702 changes, the presence manager 302
`
`[of server complex 204] sends a buddy list update message 600 to all the
`
`subscribers listed in the subscriber identifier field 706 of the corresponding
`
`presence record 700.” Id. at 5:27−30.
`
`Griffin provides a buddy list display illustrated in Figure 9,
`
`reproduced below. Id. at 8:15−16.
`
`
`
`Figure 9, above, depicts title bar 901, where inbound chat message
`
`indicator 905 is an icon accompanied by an audible sound when the icon is
`
`first displayed, indicating to the user that there is at least one unheard or
`
`unread inbound chat message that has arrived at terminal 100. Id. at
`
`8:17−19, 8:28−32. Left softkey 910 labeled “Select” permits selection of a
`
`particular buddy for chatting, selection of which is indicated with selection
`
`
`
`18
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`indicator 906. Id. at 8:45−52, 8:60−67, 9:1−5. “If the user pushes-to-talk,
`
`the display switches to the chat history, and the user is able to record and
`
`transmit a speech message and consequently start a new thread with the
`
`selected buddies.” Id. at 9:27−31.
`
`2. Overview of Zydney
`
`Zydney, titled “Method and System for Voice Exchange and Voice
`
`Distribution,” relates to packet communication systems that provide for
`
`voice exchange and voice distribution between users of computer networks.
`
`Ex. 1006, [54], [57], 1:4–5. While acknowledging that e-mail and instant
`
`messaging systems were well-known text-based communication systems
`
`utilized by users of online services and that it was possible to attach files for
`
`the transfer of non-text formats via those systems, Zydney states that the
`
`latter technique “lack[ed] a method for convenient recording, storing,
`
`exchanging, responding and listening to voices between one or more parties,
`
`independent of whether or not they are logged in to their network.” Id. at
`
`1:7–17. Zydney thus describes a method in which “voice containers”—i.e.,
`
`“container object[s] that . . . contain[ ] voice data or voice data and voice
`
`data properties”—can be “stored, transcoded and routed to the appropriate
`
`recipients instantaneously or stored for later delivery.” Id. at 1:19–22, 12:6–
`
`8. Figure 1 of Zydney is reproduced below.
`
`
`
`19
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`
`
`
`Figure 1, above, illustrates a high-level functional block diagram of
`
`Zydney’s system for voice exchange and voice distribution. Id. at 10:19–20.
`
`Referring to Figure 1, system 20 allows software agent 22, with a user
`
`interface, in conjunction with central server 24 to send messages using voice
`
`containers, illustrated by transmission line 26, to another software agent 28,
`
`as well as to receive and store such messages, in a “pack and send” mode of
`
`operation. Id. at 10:20–11:1. 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. at 11:1–3. The system has the ability to store messages both locally and
`
`centrally at server 24 whenever the recipient is not available for a prescribed
`
`period of time. Id. at 11:3–6.
`
`In the use of Zydney’s system and method, the message originator
`
`selects one or more intended recipients from a list of names that have been
`
`previously entered into the software agent. Ex. 1006, 14:16–18. The agent
`
`permits distinct modes of communication based on the status of the
`
`
`
`20
`
`

`

`IPR2017-01799
`Patent 8,199,747 B2
`
`recipient, including the “core states” of whether the recipient is online or
`
`offline and “related status information” such as whether the recipient does
`
`not want to be disturbed. Id. at 14:19–15:1. Considering the core states, the
`
`software agent offers the originator alternative ways to communicate with
`
`the recipient, the choice of which can be either dictated by the originator or
`
`automatically selected by the software agent, according to stored rules. Id.
`
`at 15:3–7. If the recipient is online, the originator can either begin a real-
`
`time “intercom” call, which simulates a telephone call, or a voice instant
`
`messaging session, which allows for an interruptible conversation. Id. at
`
`15:8–10. If the recipient is offline, “the originator can either begin a voice
`
`mail conversation that will be delivered the next time the recipient logs in or
`
`can be delivered to the recipient’s e-[m]ail as a digitally encoded
`
`[Multipurpose Internet Mail Extension (“MIME”)] attachment.” Id. at
`
`15:15–17. Zydney explains that the choice of the online modes “depe

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