throbber

`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`________________
`
`FACEBOOK, INC., INSTAGRAM, LLC, and WHATSAPP INC.,
`Petitioners,
`
`v.
`
`BLACKBERRY LIMITED,
`Patent Owner
`________________
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`________________
`
`PATENT OWNER’S RESPONSE
`PURSUANT TO 37 C.F.R. § 42.120
`
`
`
`
`
`05710-00016B/11236096.1
`
`

`

`TABLE OF CONTENTS
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`Page
`
`I.
`
`OVERVIEW OF THE ’120 PATENT ............................................................ 3
`
`A.
`
`B.
`
`C.
`
`The ’120 Patent Specification ............................................................... 3
`
`The ’120 Patent Claims ......................................................................... 4
`
`Prosecution History of the ’120 Patent ................................................. 4
`
`II.
`
`OVERVIEW OF THE CITED ART ............................................................... 5
`
`A. Dallas (Ex. 1003) ................................................................................... 5
`
`B.
`
`C.
`
`D.
`
`E.
`
`Brown (Ex. 1004) .................................................................................. 7
`
`LeBlanc (Ex. 1005) ............................................................................... 7
`
`Bott (Ex. 1007) ...................................................................................... 8
`
`Kent (Ex. 1010) ..................................................................................... 9
`
`F. Mann (Ex. 1011) .................................................................................... 9
`
`III. LEVEL OF ORDINARY SKILL IN THE ART ........................................... 10
`
`IV. THE BOARD’S CONSTRUCTION OF “NOTIFICATION(S)” ................. 10
`
`V.
`
`STANDARD OF REVIEW ........................................................................... 18
`
`VI. DALLAS FAILS TO DISCLOSE THE CLAIMED
`“NOTIFICATIONS” ..................................................................................... 19
`
`A. Dallas’s “Red Flags,” “Sparkle” Icon and Font Variations Are
`Not “Notifications”.............................................................................. 19
`
`B.
`
`C.
`
`Dallas Teaches Away From Using the Claimed “Notifications” ........ 21
`
`Dallas’s Red Flags and Sparkle Icon Are a Message’s “Manner
`of Display,” Not “Notifications” ......................................................... 22
`
`VII. DALLAS AND LEBLANC DO NOT TEACH “SILENCING”
`NOTIFICATIONS ......................................................................................... 25
`
`VIII. THE PROPOSED COMBINATIONS FAIL TO DISCLOSE
`“DISPLAYING” IGNORED MESSAGES ................................................... 26
`
`A. Dallas Teaches Automatically “Hiding” Ignored Threads ................. 26
`
`B.
`
`Dallas Teaches Away From Automatically “Expanding”
`Ignored Threads ................................................................................... 30
`
`
`
`i
`
`

`

`C.
`
`Brown Teaches Away From Automatically “Expanding”
`Ignored Threads ................................................................................... 32
`
`IX. CONCLUSION .............................................................................................. 33
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`
`
`
`
`
`ii
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`TABLE OF AUTHORITIES
`
`Page(s)
`
`CASES
`
`Phillips v. AWH Corp.,
` 415 F.3d 1303 (Fed. Cir. 2005) ....................................................................10
`
`Samsung Elecs. Co., Ltd. v. Infobridge Pte. Ltd.,
`IPR2017-00100 (Paper 30) slip. op., 15 (PTAB Apr. 23, 2018) ...................19
`
`Trivascular, Inc. v. Samuels,
` 812 F.3d 1056 (Fed. Cir. 2016) ............................................................. 18, 19
`
`STATUTORY AUTHORITIES
`
`35 U.S.C. § 282(b) ...................................................................................................10
`
`35 U.S.C. § 314(a) ...................................................................................................18
`
`35 U.S.C. § 316(e) ...............................................................................................2, 18
`
`RULES AND REGULATIONS
`
`37 C.F.R. § 42.100(b) ..............................................................................................11
`
`
`
`
`
`
`
`
`
`iii
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`Exhibit #
`Ex. 2001
`Ex. 2002
`Ex. 2003
`Ex. 2004
`
`Ex. 2005
`
`PATENT OWNER’S LIST OF EXHIBITS
`
`
`Description
`Excerpts from the Prosecution History of the ’120 Patent
`Deposition Transcript of Dr. S. Chatterjee
`Expert Declaration of Dr. Hugh Smith
`BlackBerry v. Facebook, Inc., et al., 2:18-cv-01844-GW-(KSx),
`Dkt. 157, Corrected Final Ruling on Claim
`Construction/Markman Hearing (“Markman Order”)
`BlackBerry v. Facebook, Inc., et al., 2:18-cv-01844-GW-(KSx),
`Dkt. 117, Facebook Defendants’ Opening Claim Construction
`Brief
`
`iv
`
`
`
`
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`Facebook, Inc., Instagram, LLC, and WhatsApp Inc.’s Petition (Paper 2,
`
`“Pet.”) proffer six invalidity grounds for U.S. Patent No. 9,349,120 B2 (“’120
`
`Patent”) (Ex. 1001).1 Claims 1–3, 5, 7–11, 13–15, 17, 19–22, and 24 (“Challenged
`
`Claims”) are allegedly obvious over primary reference Alastair Dallas, Using
`
`Collabra Share 2 (Que Corporation 1995) (“Dallas”) (Ex. 1003) in view of five
`
`secondary references: (i) Mark R. Brown, Using Netscape Communicator 4 (Que
`
`Corporation 1997) (“Brown”) (Ex. 1004), (ii) Jeff Kent, C++ Demystified: A Self-
`
`Teaching Guide (McGraw-Hill/Osborne 2004) (“Kent”) (Ex. 1010); (iii) Ed Bott,
`
`Using Microsoft Windows Millennium Edition (Que Corporation 2001) (“Bott”)
`
`(Ex. 1007); (iv) Bill Mann, How to Do Everything with Microsoft Office Outlook
`
`2007 (The McGraw-Hill Companies 2007) (“Mann”) (Ex. 1011); and (v) Dee-Ann
`
`LeBlanc, Using Eudora (Que Corporation 2d ed. 1997) (“LeBlanc”) (Ex. 1005).
`
`On September 4, 2019, the Board instituted review (Paper 9, “ID”). Patent Owner
`
`BlackBerry Limited (“PO”) timely submits this Response.
`
`The ’120 Patent is directed to a system and method for silencing receipt
`
`notifications for select message threads. Petitioner has not met its “burden of
`
`
`1 Hereinafter, Facebook, Inc., Instagram, LLC, and WhatsApp Inc. are
`
`collectively referred to as “Petitioner.”
`
`
`
`
`
`1
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`proving a proposition of unpatentability by a preponderance of the evidence.” 35
`
`U.S.C. § 316(e). The Petition should be denied for many reasons.
`
`First, as described in more detail below, the Petition fails to show that any
`
`proposed prior art combination teaches the ’120 Patent’s claimed “notification(s).”
`
`Indeed, Petitioner’s primary reference, Dallas, not only fails to disclose the
`
`claimed “notification(s),” it teaches away from the limitation.
`
`Second, the Petition fails to prove the proposed combination of Dallas and
`
`LeBlanc discloses the limitation of “silencing” notifications. Even if LeBlanc
`
`arguably discloses allowing a user to choose which notification to use, the Petition
`
`has failed to prove LeBlanc teaches “silencing” these notifications.
`
`Third, none of the relied-upon references teaches “displaying” new silenced
`
`messages. To the contrary, the prior art teaches away from doing so, describing
`
`the advantages of automatically hiding new “ignored” messages.
`
`As these aforementioned limitations are found in the independent claims,
`
`they are a requirement of each and every Challenged Claim. Accordingly, as the
`
`Petition has failed to demonstrate these independent limitations, the Board should
`
`affirm the validity of the Challenged Claims by denying the Petition.
`
`
`
`
`
`2
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`I.
`
`OVERVIEW OF THE ’120 PATENT
`
`A. The ’120 Patent Specification
`
`At the time of the claimed invention, users could receive notifications in the
`
`form of auditory user alerts such as ringtones, visual alerts such as flashing lights
`
`or pop-ups, and physical alerts such as vibration upon receipt of an electronic
`
`message. Ex. 1001 at 1:28-32. In the past, however, the user would receive a
`
`notification each time a new message was received in any thread, regardless of
`
`whether the user was actually engaging with that thread. See id. at 1:43-46; Ex.
`
`2003 at ¶ 29-30.
`
`The ’120 Patent addresses this and other issues by allowing the user to
`
`“silence” individual message threads, thereby permitting the user to continue to
`
`receive messages in those threads without receiving associated receipt notifications.
`
`Id. at 13:28-33. The patent accomplishes this by grouping messages into “threads”
`
`based on, e.g., conversation topics. Id. at 1:33-43, 11:53-12:7. The claimed
`
`invention then uses a “flag” that, on a thread-by-thread basis, “override[s] a
`
`currently-enabled notification setting,” thereby “prevent[ing] . . . receipt
`
`notification[s]” for new messages “associated with the selected message thread[.]”
`
`Id. at 16:66-17:2. Such new messages are still displayed in the inbox, but in a
`
`different manner than messages in any thread not flagged as silenced. Id. at 17:8-
`
`10; Ex. 2003 at ¶ 31-32.
`
`
`
`
`
`3
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`B.
`
`The ’120 Patent Claims
`
`The ’120 Patent has three independent claims: 1, 13 and 24. All of the
`
`claims relate to silencing notifications for incoming electronic messages. Ex. 2003
`
`at ¶ 33.
`
`C.
`
`Prosecution History of the ’120 Patent
`
`The ’120 Patent was filed as U.S. Application No. 12/713,577 on February
`
`26, 2010. Related application data includes Provisional Application No.
`
`61/167,542, filed on April 8, 2009.
`
`The ’120 Patent was subject to a thorough examination by Examiners
`
`Benjamin A. Ailes and Quang N. Nguyen. During prosecution, the Applicant
`
`repeatedly pointed out a novel aspect of the invention that allows a user to be
`
`“made aware of” silenced messages by displaying them together with unsilenced
`
`messages in an inbox in a different manner, while at the same time avoiding
`
`distracting and bothersome “notifications”:
`
`[Amended] Claim 1 recites “to display the new incoming electronic
`message in an inbox together with any message thread not flagged as
`silenced, while silencing any further notifications pertaining to receipt
`of the new incoming electronic message.”
`
`This allows a user to conveniently see messages at one glance in
`his/her inbox, while not being bothered by notifications related to
`message threads which have been marked as silenced. Accordingly,
`while a user is made aware of such messages and can track them in
`the inbox, the user can avoid being distracted by unnecessary
`notifications.
`
`
`
`
`
`4
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`Ex. 2001 at 28 (12/19/2014 Amendment page 17 of 18) (emphasis added). The
`
`Examiner accepted these arguments and they were incorporated by reference into
`
`the ’120 Patent’s “reasons for allowance.” Id. at 35 (1/21/2016 NOA page 2) (“In
`
`this case, the substance of applicant's remarks filed on 12/19/2014 with respect to
`
`the amended claim limitations point out the reason claims are patentable over the
`
`prior art of record.”).
`
`II. OVERVIEW OF THE CITED ART
`
`A. Dallas (Ex. 1003)
`
`The Petition’s primary reference for Grounds 1-6 is excerpts from Dallas.
`
`Dallas is a user manual describing the functionality and use of “groupware”
`
`software aimed at “empower[ing] workers to organize and categorize documents
`
`and discussion threads.” Ex. 1003 at 28.2 Dallas’s “Collabra Share” software is
`
`based on a hierarchal document management system which is comprised of
`
`“librar[ies]” at the highest level, which contain within them “forums,” “categories,”
`
`“threads” and finally “document[s]” as the lowest tier. Id. at 53; Ex. 2003 at ¶ 34-
`
`35. Dallas’s “libraries,” for example, are shown in the Library viewing pane in
`
`Figure 4.4:
`
`
`2 Unless otherwise noted, citations refer to the parties’ bates stamped pagination.
`
`
`
`
`
`5
`
`

`

`
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`Ex 1003 at 109, Fig. 4.4 (annotated). Dallas shows using “red flags” and a
`
`document counter to indicate that new documents have been added to a library. Id.
`
`Dallas also describes “threads” and “categories” as using the “red flag” and
`
`“sparkle” icons. See, e.g., id. at 55, Fig. 1.9; Ex. 2003 at ¶ 36.
`
`Dallas explains that, unlike an alert such as a telephone ringing, these flags
`
`and sparkle icons do not interrupt a user’s concentration. Ex. 1003 at 140
`
`(chapter page 115) (“Unlike a ringing telephone, when you see the red flag on the
`
`button, indicating that there are new documents, you can choose whether to
`
`interrupt your concentration.”). A user can also choose to turn off the red flags and
`
`sparkle icons for “threads” and “categories,” by using the “ignore” feature. Id. at
`
`
`
`
`
`6
`
`

`

`
`111-12. Dallas does not disclose an “ignore” feature for turning off red flags and
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`sparkle icons for libraries. Ex. 2003 at ¶ 37-38.
`
`B.
`
`Brown (Ex. 1004)
`
`The Petition cites excerpts from Brown as a secondary reference for
`
`Grounds 1-6. Brown is a user manual for the Netscape Communicator software
`
`which allows users to browse the web, read email and the like. Ex. 1004 at 34; Ex.
`
`2003 at ¶ 39. Brown includes an “ignore” feature that hides the selected thread
`
`entirely from view:
`
`To ignore a thread, select the first message in the thread (or the
`collapsed thread's only message) and choose Message, Ignore from
`the Messenger menu; then choose Thread. The newly ignored thread
`disappears from view in the Message List. The best part is that
`messages in this thread continue to be downloaded and sorted by
`Messenger. They're just not shown. Of course, there's a way to show
`the ignored threads again, if you want or need to.
`
`Ex. 1004 at 50 (chapter page 209).
`
`C. LeBlanc (Ex. 1005)
`
`The Petition adds LeBlanc as “further support for ‘notification’ limitations
`
`of the challenged claims” for Grounds 4-6. See, e.g., Pet. at 65-66. LeBlanc is a
`
`user manual describing the Eudora program aimed at assisting individuals using
`
`email. Ex. 1005 at 20. The Petition has only submitted select excerpts from
`
`LeBlanc amounting to 26 pages (only four of which are substantive), although the
`
`manual is over 290 pages long. The provided four substantive pages address the
`
`
`
`
`
`7
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`“Checking Mail Manually” feature and include a partial disclosure of the “reading
`
`mail” function. Id. at 23-26; Ex. 2003 at ¶ 40-41. The “Checking Mail Manually”
`
`feature discloses popups which are displayed both when there is new mail and
`
`when no new mail has arrived:
`
`Ex. 1005 at 23 (annotated). The limited excerpts of LeBlanc also indicate that a
`
`user may choose what type of user alerts to receive (pop-up windows, flashing etc.).
`
`Ex. 1005 at 24-25 (“You can choose what Eudora does to point out to you that you
`
`
`
`have new mail.”); Ex. 2003 at ¶ 42.
`
`D. Bott (Ex. 1007)
`
`The Petition cites Bott as a secondary reference for Grounds 2 and 5 for the
`
`“system comprises a wireless device” limitation of dependent claim 9. Pet. at 4,
`
`19-20, 58. Bott describes the features of Microsoft’s Windows Millennium Edition
`
`
`
`
`
`8
`
`

`

`
`operating system. Ex. 1007 at 1. Bott discusses wireless networks for connecting
`
`to the Internet, including the use of wireless adapters that can be attached to a
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`user’s computer. Id. at 421-22; Ex. 2003 at ¶ 43.
`
`E. Kent (Ex. 1010)
`
`The Petition cites Kent as a secondary reference for Ground 1-6 to allegedly
`
`show the “activate a flag stored in the non-transitory media” and “using the flag
`
`stored in the non-transitory media” limitations of the Challenged Claims. See, e.g.,
`
`Pet. at 4, 31, 38; Ex. 2003 at ¶ 44.
`
`Kent is a basic reference on coding without any disclosure of managing
`
`incoming messages. Thus, Kent explains the C++ programming language,
`
`including the use of C++ to implement Boolean variables called “flags.” Ex 1010
`
`at 148-51. Kent defines a “flag” as a “variable whose value indicates whether a
`
`condition exists.” Id. at 150. Kent describes a flag titled “quit,” which is given the
`
`value “true” if the user enters “Y” and “false” if the user enters “N.” Id. at 150-51;
`
`Ex. 2003 at ¶ 45.
`
`F. Mann (Ex. 1011)
`
`The Petition cites Mann as a secondary reference for Grounds 3 and 6 for the
`
`“new incoming message is displayed in a default view of the inbox” limitation of
`
`dependent claims 11 and 22 of the ’120 Patent. See Pet. at 4, 20, 61; Ex. 2003 at ¶
`
`
`
`
`
`9
`
`

`

`
`46. Mann is not used in the Petition’s grounds addressing the independent claims.
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`Paper 2 at 4.
`
`Mann describes Microsoft Office Outlook 2007 (“Outlook”). Mann
`
`discusses allowing the user to group messages by conversation, which “creates
`
`groups in the Inbox pane that consist of all the messages in a particular thread.” Ex.
`
`1011 at 89. In this configuration, Mann’s Inbox pane shows only the most recent
`
`message in each conversation; the user must click a “down arrow” appearing
`
`adjacent to the subject line to display older messages. Id.; Ex. 2003 at ¶ 46.
`
`III. LEVEL OF ORDINARY SKILL IN THE ART
`
`Petitioner alleges that a person of ordinary skill in the art (“POSITA”) would
`
`have possessed at least a bachelor’s degree in software engineering, computer
`
`science, or computer engineering, or electrical engineering with at least two years
`
`of experience in software application development, including development of
`
`applications for messaging (or equivalent degree/experience). For purposes of this
`
`Response, BlackBerry does not dispute the level of ordinary skill proposed by
`
`Petitioner. Ex. 2003 at ¶ 19-21.
`
`IV. THE BOARD’S CONSTRUCTION OF “NOTIFICATION(S)”
`
`For inter partes reviews filed on or after November 13, 2018, such as this
`
`one, claim terms are construed using the same claim construction standard that is
`
`used in a civil action under 35 U.S.C. Section 282(b), as articulated in Phillips v.
`
`
`
`
`
`10
`
`

`

`
`AWH Corp., 415 F.3d 1303 (Fed. Cir. 2005) (en banc), and its progeny. See 37
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`C.F.R. § 42.100(b).
`
`While the Petition proffered two claim terms for construction, “flag” and
`
`“notification(s),” as recognized by the Board in its Institution Decision, the parties
`
`have resolved their dispute regarding the claim term “flag.” See ID at 8 (“Given
`
`the parties’ positions, we will not construe “flag” in this decision.”). Accordingly,
`
`the sole claim term for construction is “notification(s).” Ex. 2003 at ¶ 47-50.
`
`In the ID, the Board adopted the district court’s construction of “notification”
`
`to require “some form of visual, auditory, or physical cue to draw attention to an
`
`incoming message that would not otherwise have been noticed, at the time of the
`
`incoming message.” ID (Paper 9) at 9 (emphasis added). The Board also invited
`
`the parties to address “how one might evaluate the ‘that would not otherwise have
`
`been noticed’ portion of the construction with regard to what a user might or might
`
`not be doing for the user to not otherwise have noticed the message.” Id.
`
`In the related district court proceeding, the parties engaged in a similar
`
`dispute regarding the meaning of “notification” during claim construction. As here,
`
`Petitioner argued in the district court that display characteristics of a new message
`
`(e.g., font color and icon changes) are the claimed “notification.” Ex. 2005 at 8
`
`(Dkt. 117, Facebook’s Opening Markman Brief) (“Each of the Accused Products,
`
`
`
`
`
`11
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`even when a message thread is allegedly ‘silenced,’ continues to provide visual
`
`notifications and/or alerts pertaining to receipt of new messages in the message
`
`thread, such as badge notifications or other graphical indications and text, such as
`
`bold-face font.”); id at 7-8 (arguing that “visual notifications” such as “check
`
`boxes, an icon, a distinctive color, or a distinctive font” are the claimed
`
`“notifications”). The District Court flatly rejected Petitioner’s broad reading of
`
`“notifications”:
`
`At the hearing, Facebook Defendants agreed that their proposed
`construction of this term would cover a change to a numeric
`character on a phone application icon, without any other cue to draw
`attention to it. They also agreed that a change in the listed number of
`unread messages in an email inbox, without any other cue to draw
`attention to it, would be considered a notification under their
`interpretation. There is inadequate support for such a broad
`interpretation of
`the
`term “notification,” particularly when
`considering the patent intrinsic record.
`
`Ex. 2004 (Markman Order) at 31 (emphasis added). Instead, the Court agreed with
`
`PO’s interpretation of “notification,” which PO again asserts here. In particular,
`
`the district court directly copied from PO’s Markman briefing to construe the claim
`
`term “notification”:
`
`In one portion of its opening claim construction brief, BlackBerry
`states that “notification” in the context of the ’120 Patent “refers to
`some form of visual, auditory, or physical cue to draw a user’s
`attention to an occurrence that the user would not otherwise notice
`and at the time of the occurrence.” Docket No. 116 at 27. The Court
`agrees with BlackBerry and its expert that this explanation is
`
`
`
`
`
`12
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`consistent with the plain meaning of the term “notification” as used in
`the ’120 Patent.
`
`Ex. 2004 (Markman Order) at 30 (emphasis added), citing Ex. 1001 at 1:30-33,
`
`9:26-31, 13:19-22 and BlackBerry’s expert declaration. Thus, the district court’s
`
`construction—which the Board has correctly adopted here—is an explicit rejection
`
`of Petitioner’s position that display characteristics, such as changing icons and font
`
`color, are “notifications,” in favor of BlackBerry’s proper reading that
`
`“notifications” must draw a user’s attention to a new message that would not
`
`otherwise be noticed.
`
`Contrary to the district court’s construction, adopted by the Board, Petitioner
`
`and its expert reiterate their arguments rejected by the district court that nearly any
`
`display characteristic of a new message is a “notification.” For example, Dr.
`
`Chatterjee testified consistently with Petitioner’s position that a new message’s
`
`font color is a “notification” (Ex. 2002 (Chatterjee Tr.) at 53:16-25), and likewise
`
`that bolded text (id. at 54:24-55:4) or italicized text (id. at 55:22-56:4) alone are
`
`also “notifications.” Thus, Petitioner and its expert incorrectly argue that nearly
`
`any difference in a message’s visual appearance is a “notification”—an argument
`
`already rejected by the district court. Ex. 2004 (Markman Order) at 29 (criticizing
`
`Facebook’s position: “Facebook Defendants originally suggested by their proposal,
`
`however, that almost any difference in visual appearance could satisfy this claim
`
`
`
`
`
`13
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`language, stating that even certain un-bolded messages in an email inbox could still
`
`be considered ‘notifications’…Facebook Defendants appear to still suggest by their
`
`proposal that the term “notification” should be construed to encompass almost any
`
`other difference in the visual appearance of a message.”); Ex. 2003 at ¶ 51-55.
`
`Indeed, the district court’s adoption of PO’s description of “notifications”
`
`emphasizes that a “notification” is something that must draw a user’s attention
`
`away from something else, i.e., it must distract or otherwise interrupt a user from
`
`another activity. Ex. 2003 at ¶ 56. “Notifications” do not include display
`
`characteristics only noticed by a user that is already attentive to a thread with a
`
`new message. As recognized by the District Court, this is confirmed by the ’120
`
`Patent’s specification, which consistently refers to “notifications” as alerts such as
`
`“ring tones, visual alerts such as flashing lights or popups and physical alerts such
`
`as vibrations.” See Ex. 1001 at 1:30-32, 9:4-8, 9:17-20, 9:26-31, 13:19-21.
`
`Petitioner’s expert acknowledged that these types of notifications would alert a
`
`user to the arrival of a new message, even if a user’s attention was directed
`
`elsewhere:
`
`Q: Okay, so if your attention was on something else besides the phone,
`when the ring tone happened, you would hear the ring tone, right?
`
`A: You would hear the sound irrespective of what you're looking at,
`whether in your hypothetical you're reading a book, or whether you're
`looking at the phone, whether you're holding the phone, whether
`
`
`
`
`
`14
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`you're looking out the window, irrespective of what you're doing, with
`the caveat that the person in this hypothetical does not have any
`hearing issues, they would be able to hear the sound.
`
`Ex. 2002 (Chatterjee Tr.) at 31:23-32:8; see also 33:18-34:14 (confirming
`
`the same with respect to vibration notifications).
`
`Moreover, the ’120 Patent itself distinguishes its “notifications” from the
`
`display characteristics of a new message by including a separate limitation
`
`covering a “manner of display” of a message. See Ex. 1001 at claim 1[h]. The
`
`specification describes an adjustment of the display characteristics of an incoming
`
`message, such as font color, weight etc. as a change to a message’s “manner of
`
`display.” See, e.g., id. at 14:49-52 (“If the message thread has been silenced by the
`
`user then no notification may be activated and at 614 the message may appear
`
`‘greyed out’ or other diminished fashion when displayed with the inbox contents.”);
`
`Ex. 2003 at ¶ 57-58. Thus, the ’120 Patent itself distinguishes between
`
`“notifications” and display characteristics of a message.
`
`Likewise, the prosecution history confirms that “notifications” are
`
`“distractions” that “bother” a user:
`
`[Displaying silenced messages together with unsilenced messages]
`allows a user to conveniently see messages at one glance in his/her
`inbox, while not being bothered by notifications related to message
`threads which have been marked as silenced. Accordingly, while a
`user is made aware of such messages and can track them in the inbox,
`the user can avoid being distracted by unnecessary notifications.
`
`
`
`
`
`15
`
`

`

`
`Ex. 2001 at 28 (12/19/2014 Amendment page 17 of 18) (emphasis added). A
`
`change in font color or an icon change would not “bother” or “distract” a user. Ex.
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`2003 at ¶ 59-60.
`
`For example, as Dr. Chatterjee acknowledged during his deposition, a user
`
`would not see Dallas’s icon or font change if the user was working in a different
`
`document (Ex. 2002 (Chatterjee Tr.) at 50:13-51:17), if the message thread were
`
`scrolled out of view (id. at 47:20-49:25), or if the viewing window were minimized
`
`(id. at 50:2-8). Likewise, if a thread is collapsed, a user would be unaware of
`
`Dallas’s icons or font color. Ex. 2003 at ¶ 61.
`
`Dallas itself provides a prime example of this deficiency in one of its
`
`disclosures relied-upon by Petitioner and its expert, Figure 7.5 (Ex. 1003 at 179)
`
`(annotated):
`
`
`
`
`
`16
`
`

`

`
`
`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`As seen in Dallas’s Figure 7.5, even if a user is already attentive to the
`
`Collabra Share screen, and further still, even if that user is already attentive to a
`
`particular category with a new message in it, the new message’s “red flag” and
`
`“sparkle” icons will only be noticed if they are scrolled into view. For example,
`
`the image above shows that the selected category “Business Planning” has a “red
`
`flag” on its icon, indicating that this selected category contains a new message.
`
`But no “red flags” or “sparkle” icons are visible in the thread/message viewing
`
`pane shown in Figure 7.5—they are scrolled out of view. Ex. 2003 at ¶ 62-63.
`
`
`
`
`
`17
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`
`As demonstrated by this example, a user will be unaware of Dallas’s “red
`
`flags” and “sparkle” icon unless a user already has the new message thread scrolled
`
`into view. Thus, Petitioner’s assertion that Dallas’s colored icons will “notify” a
`
`user of a new message would, as a practical matter, require a user to anticipate
`
`where the new message will arrive, to select the particular category containing that
`
`new message, and to scroll the new message thread into view. See Ex. 2002
`
`(Chatterjee Tr.) at 48-49 (confirming that Dallas’s “red flags” and “sparkle” icons
`
`are only apparent to a user when they are scrolled into view). Otherwise, Dallas’s
`
`“red flags” and “sparkle” icon will not be noticed. Ex. 2003 at ¶ 64.
`
`Thus, Dallas does not disclose a “notification” in any sense. And, in any
`
`case, its disclosures certainly do not comport with the Board’s adopted claim
`
`construction that requires notifications to alert a user to a new message “that would
`
`not have otherwise been noticed.” Accordingly, Petitioner’s assertion should be
`
`rejected.
`
`V.
`
`STANDARD OF REVIEW
`
`“[T]here is a significant difference between a petitioner’s burden to establish
`
`a ‘reasonable likelihood of success’ at institution, and actually proving invalidity
`
`by a preponderance of the evidence at trial.” Trivascular, Inc. v. Samuels, 812
`
`F.3d 1056, 1068 (Fed. Cir. 2016); see also 35 U.S.C. §§ 314(a), 316(e). Because,
`
`
`
`
`
`18
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`at the institution phase, the “Board is considering the matter preliminarily [and]
`
`without the benefit of a full record,” “the Board is not bound by any findings made
`
`in its Institution Decision.” Trivascular, 812 F.3d at 1068. Findings made during
`
`Trial are rendered “under a qualitatively different standard” than is used when
`
`considering institution. Id.; see also Samsung Elecs. Co., Ltd. v. Infobridge Pte.
`
`Ltd., IPR2017-00100 (Paper 30) slip. op., 15 (PTAB Apr. 23, 2018) (“[W]e
`
`consider anew [the] arguments presented in [the] Response. . . . We are not
`
`persuaded by [the] argument that [PO] has not presented anything new to rebut our
`
`previous analysis and conclusion because we now must evaluate the evidence of
`
`record against a different, and higher, standard.” (internal quotation marks
`
`omitted)).
`
`VI. DALLAS FAILS TO DISCLOSE THE CLAIMED “NOTIFICATIONS”
`
`A. Dallas’s “Red Flags,” “Sparkle” Icon and Font Variations Are
`Not “Notifications”
`
`Dallas’s “red flags” and “sparkle” icon are not “notifications” under the
`
`district court’s well-reasoned construction, correctly adopted by the Board in this
`
`proceeding. Ex. 2003 at ¶ 65. Petitioner’s assertion that different icon graphics are
`
`“notifications” would stretch the term to encompass almost any difference in the
`
`visual appearance of a message—a position that the district court has already
`
`rejected. Ex. 2004 (Markman Order) at 29 (criticizing Facebook’s position:
`
`
`
`
`
`19
`
`

`

`IPR2019-00706
`U.S. Patent No. 9,349,120
`
`
`“Facebook Defendants originally suggested by their proposal, however, that almost
`
`any difference in visual appearance could satisfy this claim language, stating that
`
`even certain un-bolded messages in an email inbox could still be considered
`
`‘notifications’…Facebook Defendants appear to still suggest by their proposal that
`
`the term “notification” should be construed to encompass almost any other
`
`difference in the visual appearance of a message.”); see Ex. 2003 at ¶ 65. Indeed,
`
`Petitioner’s assertion directly conflicts with the specification, which repeatedly
`
`describes “notifications” as the attention-grabbing cues designed to draw a user’s
`
`attention to a message “that the user would not otherwise notice.” Ex. 2004
`
`(Markman Order) at 30 (citing Ex. 1001 at 1:30-33, 9:26-31, 13:19-22 and
`
`BlackBerry’s expert); Ex. 2003 ¶ 65. Moreover, the district court has already
`
`agreed with BlackBerry that display characteristics of a message—including
`
`changing an icon graphic—are insufficient to meet the “notification” limitation
`
`because they would not be noticed unless the user was already attentive to the new
`
`message:
`
`At the hearing, Fac

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