throbber
Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`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-00925
`U.S. Patent No. 8,209,634
`
`REPLY DECLARATION OF SANDEEP CHATTERJEE, PH.D.
`
`
`
`
`
`
`
`
`
`
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 001
`
`

`

`Table of Contents
`
`
`Page
`
`
`
`
`
`I.
`
`Response to Dr. Surati’s Opinions on Field of Art and Person of
`Ordinary Skill in the Art ................................................................................. 1
`Response to Dr. Surati’s Opinions on the Alleged Lack of Motivation
`to Combine Ording’s Userbar with Abiko’s Email System ........................... 2
`III. Response to Dr. Surati’s Opinions on the Alleged Lack of Motivation
`to Adapt the Icon in Ording to Show the Number of Distinct Senders .......... 7
`IV. Response to Dr. Surati’s Opinions on Whether Disclosures in
`Crumlish Undermine the Stated Motvations to Combine ............................ 10
`Response to Dr. Surati’s Opinions on Whether Disclosures in Abiko
`Undermine My Stated Motivations to Combine .......................................... 15
`VI. Response to Dr. Surati’s Opinions on McPherson and Dependent
`Claims 6, 12 and 18 ...................................................................................... 17
`VII. Conclusion .................................................................................................... 20
`
`
`
`II.
`
`V.
`
`
`
`
`
`-i-
`
`
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 002
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`I, Sandeep Chatterjee, Ph.D., declare as follows:
`
`1.
`
`I have been asked to review and respond to certain points raised in the
`
`“Second Declaration of Rajeev Surati, Ph.D.” dated February 10, 2020 (Ex. 2013)
`
`(“Surati Declaration”) filed with respect to the IPR petition for U.S. Patent No.
`
`8,209,634 in IPR2019-00925 in support of the Patent Owner’s Response.
`
`2.
`
`This Declaration responds to the portions of the Surati Declaration that
`
`affirmatively present new facts or new rationale to which a response is warranted. I
`
`note that in many instances, Dr. Surati merely states general disagreements with the
`
`conclusions that I reached (on which the Petition relied), without actually providing
`
`contrary evidence or analysis. As to those statements, I adhere to the analysis in my
`
`opening declaration (Ex. 1102).
`
`I.
`
`RESPONSE TO DR. SURATI’S OPINIONS ON FIELD OF ART AND
`PERSON OF ORDINARY SKILL IN THE ART
`3.
`Dr. Surati provides a formulation of a person of ordinary skill in the art
`
`similar to the one in my opening declaration. (Ex. 2013, ¶¶7-9.) His formulation
`
`shares approximately the same amount of education and experience as mine, but
`
`mine also adds experience in development of applications for messaging on wireless
`
`devices. (Ex. 1102, ¶13.) In any event, I do not perceive material differences
`
`between the two that would impact the application of the prior art to the claims. My
`
`opinions would therefore not change if I applied Dr. Surati’s formulation.
`
`
`
`1
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 003
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`II. RESPONSE TO DR. SURATI’S OPINIONS ON THE ALLEGED
`LACK OF MOTIVATION TO COMBINE ORDING’S USERBAR
`WITH ABIKO’S EMAIL SYSTEM
`4.
`Dr. Surati argues that the Petitioner did not sufficiently show that a
`
`person of ordinary skill in the art would have been motivated to combine Ording
`
`with Abiko. (Ex. 2013, ¶¶41, 44-48.) The crux of Dr. Surati’s argument is that the
`
`Petitioner did not show that a skilled artisan would have been motivated to adapt
`
`Ording to incorporate the email program described in Abiko. (Id.)
`
`5.
`
`Dr. Surati points to Paragraph 80 of my opening declaration to argue
`
`that I did not identify a reason for a person of ordinary skill in the art to modify
`
`Ording to incorporate Abiko’s email program. (Ex. 2013, ¶48.) But Paragraph 80
`
`was not intended to describe motivations to combine Ording and Abiko, but rather,
`
`to lay out the combination itself, i.e. that userbar 600 of Ording would be adapted to
`
`include an icon for the Abiko email program. (Ex. 1102, ¶80.) Other portions of
`
`my declaration, as discussed below, provided motivations to combine Ording and
`
`Abiko. I will briefly summarize them and also respond to Dr. Surati’s positions.
`
`6.
`
`First, my opening declaration explained that a person of ordinary skill
`
`in the art would have been motivated to combine Ording with Abiko because Abiko
`
`provided wireless communications capabilities not disclosed in Ording. (Ex. 1102,
`
`¶¶67, 71-73.) The wireless capabilities of Abiko, as previously explained, “provide
`
`a key convenience in that the user need not be tethered to wires to connect to a
`
`
`
`2
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 004
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`computing network,” a benefit that was “particularly advantageous in the context of
`
`electronic messaging, as it allows users to send and receive messages on the go, as
`
`Abiko expressly confirms.” (Ex. 1102, ¶73 (citing Abiko, Ex. 1109, ¶0004).) Dr.
`
`Surati also did not address, let alone dispute, my opinion that “market and
`
`competitive forces would have further encouraged a person of ordinary skill in the
`
`art to support the ability to use wireless computing devices, as disclosed in Abiko,
`
`with the user interface techniques in Ording.” (Ex. 1102, ¶73.)
`
`7.
`
`Second, with respect to Abiko’s email program itself, I explained that
`
`the “sender-centric” nature of Abiko’s program makes it easier to organize messages
`
`based on their senders. (Ex. 1102, ¶¶48, 105.) For example, “Abiko recognized that
`
`for many users, it is more important to organize and present messages based on their
`
`senders.” (Ex. 1102, ¶105.) Abiko itself explains that “a user who wishes, for
`
`example, to create a list of all received mail messages from a particular sender must
`
`search through numerous messages one by one by means of a manual input
`
`operation.” (Abiko, Ex. 1109, ¶0005 (quoted in Ex. 1102, ¶105).) “Some received
`
`messages required are therefore likely to be overlooked and many operations are
`
`needed to find the messages.” (Id.) Abiko addresses this problem by providing a
`
`technique for automatically organizing and displaying received messages based on
`
`their respective senders, a unique feature of Abiko that Dr. Surati does not claim was
`
`provided by other conventional email clients (including “Apple Mail”).
`
`
`
`3
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 005
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`
`8.
`
`Dr. Surati relies primarily on the fact that Ording describes a feature
`
`that was implemented in connection with the Apple Macintosh user interface. (Ex.
`
`2013, ¶¶29, 46-47.) The commercial embodiment of userbar 600 in Ording appears
`
`to have been the Macintosh OS user interface feature known as the “Dock,” which
`
`was part of the Macintosh user interface as of at least December 2003. (Ex. 2014,
`
`p.5.) Dr. Surati also states that Apple provided an email client known as “Apple
`
`Mail” for use with its Macintosh computers in the 2003 timeframe. (Ex. 2013, ¶¶46-
`
`47.) Dr. Surati appears to argue that a person of ordinary skill in the art would not
`
`have been motivated to combine Ording with the email teachings of Abiko because
`
`the commercial embodiment of Ording – the Apple Macintosh – already offered a
`
`suitable email client. (Id, ¶47.) I find several problems with his analysis.
`
`9.
`
`First of all, Dr. Surati’s argument appears to conflate the disclosures of
`
`the Ording patent with its commercial embodiment in the Apple Macintosh system,
`
`but the two are different and would have been recognized as such by a person of
`
`ordinary skill in the art. Ording itself makes crystal clear that its user interface
`
`techniques are not limited to the Apple Macintosh but “can be used in combination
`
`with any system having a processor and a display.” (Ording, Ex. 1103, 6:19-23.)
`
`And nothing in Ording makes any mention of “Apple Mail” or limits itself to any
`
`particular email software – it more broadly teaches that any “e-mail applications”
`
`can reside on the userbar. (Ex. 1102, ¶¶44-45; Ording, Ex. 1103, 8:64-67
`
`
`
`4
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 006
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`(“Candidate items for such permanent residency on the userbar 600 include, for
`
`example … e-mail applications”), 9:19-23, 13:12-21.)
`
`10. Dr. Surati himself acknowledged at his deposition that nothing in
`
`Ording suggests that its techniques were limited to the Apple Mail email client.
`
`(Surati Depo., Ex. 1130, 90:24-91:7.) He further acknowledged, and I agree, that
`
`the user interface teachings in Ording could have been applied to any email
`
`application. (Id., 91:2-10.) The Ording patent, as he explained, was “trying to patent
`
`concepts in a more general way.” (Id., 92:8-10.) A person of ordinary skill in the
`
`art would have understood Ording in precisely this way, and as such, would have
`
`appreciated that any suitable email system could have been represented in the
`
`userbar 600 of Ording, including the one in Abiko. A skilled artisan would have
`
`regarded the availability of “Apple Mail” on Apple Macintosh systems as irrelevant
`
`to the motivation to combine the userbar 600 of Ording with the Abiko email system.
`
`11. To the extent a skilled artisan’s knowledge of the Apple Macintosh
`
`commercial embodiment had any relevance to the obviousness analysis, that
`
`knowledge would actually undermine Dr. Surati’s opinions. Because the “Dock” of
`
`the Apple Macintosh appears to already embody the userbar 600 feature of Ording,
`
`a skilled artisan as of December 2003 would have found Ording more applicable to
`
`non-Macintosh systems. Stated another way, a person of ordinary skill in the art
`
`seeking to apply Ording would not have used the Apple Macintosh as the platform
`
`
`
`5
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 007
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`on which to implement the disclosed userbar 600, as such an implementation would
`
`have been redundant of capabilities the Macintosh user interface already had.
`
`12. Finally, the apparent premise of Dr. Surati’s argument – that the
`
`availability of “Apple Mail” for the Apple Macintosh would have eclipsed Abiko’s
`
`email client and made it unnecessary – is also undermined by the multitude of email
`
`programs in existence as of December 2003. Dr. Surati himself acknowledged that
`
`the list of “common e-mail programs as of 2003” included at least America Online,
`
`Lotus cc:mail, CompuServe, Qualcomm Eudora, Microsoft Exchange, NetCruiser,
`
`Pegasus Mail and Pine. (Surati Depo., Ex. 1130, at 93:19-95:3; see also id., 83:18-
`
`84:8 (acknowledging that Eudora and Mozilla Thunderbird were both available for
`
`the Macintosh).) The availability of so many email products reflected differences in
`
`the available features in each product, the consumer base each product targeted,
`
`general user preferences, and many other factors. In fact, as Dr. Surati
`
`acknowledged at his deposition, it would have been common for a computer user as
`
`of December 2003 to have multiple different messaging applications on his or her
`
`computer. (Id., 86:14-23.) For example, it was common for computer users to have
`
`at least a first email application from an online service such as America Online, and
`
`a second email application to send or receive business- or work-related messages.
`
`13. Accordingly, even if the existence of “Apple Mail” had some relevance
`
`to the specific teachings of Ording and the motivations to combine (which it does
`
`
`
`6
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 008
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`not), it would not have deterred a skilled artisan from using different email
`
`applications with Ording, including the one in Abiko. As I explained above, Abiko
`
`would have provided specific advantages, including wireless communication and the
`
`ability to easily organize display of messages by sender. Dr. Surati does not claim
`
`that Apple Mail provided those same benefits.
`
`III. RESPONSE TO DR. SURATI’S OPINIONS ON THE ALLEGED
`LACK OF MOTIVATION TO ADAPT THE ICON IN ORDING TO
`SHOW THE NUMBER OF DISTINCT SENDERS
`14. Dr. Surati’s arguments about the claimed “numeric character” follow
`
`much the same approach as his arguments addressed above regarding the
`
`combination of Ording and Abiko – asserting that the petition did not provide any
`
`motivation to combine, while ignoring the specific motivations that were actually
`
`provided. (Ex. 2013, ¶¶49-58.) I respectfully disagree with Dr. Surati’s arguments.
`
`15. First, Dr. Surati nitpicks language in the Petition (and similar
`
`statements in my opening declaration) arguing that a numeric value representing the
`
`number of distinct senders “might be” preferable to some users. (Ex. 2013, ¶¶50-
`
`51.) The point behind Dr. Surati’s argument is unclear, but I used this type of
`
`language to acknowledge what was well-known to persons of ordinary skill in the
`
`art – there was no “one-size-fits-all” approach to organizing and presenting email
`
`messages that would have been ideal for every user. As explained in my opening
`
`declaration, “a person of ordinary skill in the art would have understood that there is
`
`
`
`7
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 009
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`no single solution, applicable to all users, for organizing electronic messages and
`
`notifying users of new (unread) messages.” (Ex. 1102, ¶110.) This is reflected in
`
`part by the existence of so many different email applications in December 2003, as
`
`explained above. I further explained that “[f]or certain categories of users, such as
`
`users of the message sorting and organizing system in Abiko, a more ‘sender-centric’
`
`approach to received messages might be preferable.” (Id.) I am informed that under
`
`applicable patent law, a motivation to combine may exist even if the course of action
`
`proposed by the combination does not present advantages in every conceivable
`
`situation, or has both advantages and disadvantages.
`
`16. Second, Dr. Surati attacks Abiko on the ground that the sender table in
`
`Figure 8 of Abiko shows four (4) listed items and then two “dots” indicating the
`
`presence of additional (and unshown) items. (Ex. 2013, ¶55.) However, a person of
`
`ordinary skill in the art would have understood the dots in Figure 8 to simply indicate
`
`the presence of additional numbered items in the list. Abiko explains that each entry
`
`in the sender table is sorted and ranked through a sequential numbering scheme
`
`(starting at “1”) based on the mail volume associated with each sender. (Abiko, Ex.
`
`1109, ¶¶0116 (“[T]he mail volume numbers are stored starting with the sender from
`
`whom the most messages were received in the order of smaller to larger number
`
`(No) 1, 2, 3 ... in the sender table sorted by mail volume.”), 0121 (“This screen [Fig.
`
`10(b)] displays, for example, multiple sets of ‘Sender name’ information stored in
`
`
`
`8
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0010
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`the ‘Sender name’ column (“KAWADA, Hanako’ ‘satoh@def.or.jp’ etc.) and ‘Mail
`
`volume’ information (‘10, 13’ etc.) in association with the numbers thereof (1, 2, 3
`
`...) of the sender table sorted by date shown in FIG. 8….”) (underlining added).)
`
`Accordingly, as Dr. Surati acknowledged at his deposition, if the list in Figure 8
`
`contained items beyond the four specifically listed, those additional items would
`
`have been sequentially numbered “5,” “6,” etc., until the total number of items to be
`
`displayed was reached. (Surati Depo., Ex. 1130, 98:6-11, 99:1-19.) The presence
`
`of the “dots” in Figure 8 is thus immaterial; the number (i.e., “No”) associated with
`
`the last sender appearing in the list will always correspond to the total number of
`
`distinct senders of messages.
`
`17. Third, Dr. Surati misunderstands my reliance on Dvorak (Ex. 1111).
`
`My opening declaration made clear that Dvorak was not cited with respect to any
`
`specific claim limitation, but to bolster a motivation to combine. (Ex. 1102, ¶56.)
`
`Dr. Surati does not address the fact that Dvorak identifies as his “biggest headache”
`
`the fear of non-receipt of email, which causes senders to “send multiple copies” of
`
`the same message to the same user. (Ex. 1111, at 018; Ex. 1102, ¶107.) Nor does
`
`Dr. Surati dispute that this “biggest headache” would have resulted in an increase in
`
`the number of unnecessary messages from the same sender, such that “a numeric
`
`value representing the total number of new e-mail messages may not have been
`
`particularly informative to some users.” (Ex. 1102, ¶108.)
`
`
`
`9
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0011
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`
`18. Dr. Surati points instead to a separate “mail storm” problem identified
`
`in Dvorak, a problem that Dr. Surati contends would have resulted in “new messages
`
`[being] generated from different senders.” (Ex. 2013, ¶57 (bold in original).) To
`
`the extent Dr. Surati contends that the “mail storms” problems undermines the
`
`motivation to combine, I respectfully disagree. Dvorak itself clearly identifies the
`
`fear of non-receipt (and resulting multiple copies) as the more significant problem,
`
`as it is listed above mail storms in the article and identified as the “biggest headache”
`
`of general Internet email. (Ex. 1111, at 018.) More fundamentally, the variety of
`
`different problems facing e-mail merely confirms the existence of tradeoffs that a
`
`skilled artisan would have to weigh in considering potential approaches, not factors
`
`that render the combination non-obvious. (Ex. 1102, ¶110.)
`
`IV. RESPONSE TO DR. SURATI’S OPINIONS ON WHETHER
`DISCLOSURES IN CRUMLISH UNDERMINE THE STATED
`MOTVATIONS TO COMBINE
`19. Dr. Surati cites portions of Crumlish in which the author states that “I
`
`keep my mail around until I’ve replied to it,” and advising users not to “create a new
`
`mailbox when an existing mailbox will suffice….” (Ex. 2013, ¶¶61-62 (quoting
`
`Crumlish, Ex. 1110 at 049 & Ex. 2015 at 18).) Dr. Surati appears to argue that these
`
`statements from Crumlish would have discouraged a skilled artisan from adopting
`
`the approach of Pegasus Mail in which new messages are stored in a “New mail
`
`folder” separate from the folder holding old messages. (Ex. 2013, ¶62.)
`
`
`
`10
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0012
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`
`20.
`
`I respectfully disagree. The statements in Crumlish cited by Dr. Surati
`
`have nothing to do with an email program automatically placing new messages in a
`
`separate folder to separate them from old messages. They instead advise users not
`
`to create an excessive number of user-created mailboxes for manual filing of email
`
`messages. (Ex. 2015, at 18.) For example, Crumlish explains that different email
`
`programs “offer different commands for creating mailboxes and transferring
`
`messages into them, but the principles are more or less the same as those used for
`
`real-life filing.” (Ex. 2015, at 18 (underlining added).) The separate new mail folder
`
`in Pegasus Mail does not serve this same purpose of facilitating manual filing or
`
`archiving old messages – it instead provides a technique to automatically and
`
`temporarily separate and identify new incoming messages.
`
`21.
`
`In fact, the new mail technique in Pegasus Mail would actually be
`
`complementary to Crumlish’s advice. Crumlish explains that after the new message
`
`has been read, it is automatically moved from the New Mail folder to the Main mail
`
`folder. (Crumlish, Ex. 1110, 063 (“Once you’ve read a message, it will
`
`automatically be moved to the Main mail folder after you close the New Mail folder
`
`or exit Pegasus.”).) Accordingly, after an email message has been read and
`
`automatically moved to the Main mail folder, the user could file that message away
`
`in an appropriate mailbox in accordance with Crumlish’s advice on managing
`
`mailboxes, or any other organizational scheme the user deems most appropriate.
`
`
`
`11
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0013
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`Even if a user chose to follow Crumlish’s advice, therefore, that advice has nothing
`
`to do with the Pegasus Mail technique of automatically and temporarily storing new
`
`mail in a separate folder before it could be subject to manual filing by the user.
`
`22. Another problem with Dr. Surati’s reliance on Crumlish’s statements is
`
`that those statements merely reflect the author’s subjective opinions, and which a
`
`person of ordinary skill in the art would have felt free to disregard. Dr. Surati himself
`
`acknowledged that he does not follow Crumlish’s advice to “keep my mail around
`
`until I’ve replied to it.” (Ex. 1110, at 049; Surati Depo., Ex. 1130, at 95:10-20.) Dr.
`
`Surati also acknowledged (and I agree) that during the 2003 timeframe, email users
`
`employed various different approaches for reviewing and organizing their own email
`
`messages. (Id. at 95:21-96:15.) As he acknowledged, “everyone has their own
`
`preferences in how they respond to mail.” (Id. at 96:13-15.) For example, Dr. Surati
`
`acknowledged that it was “not unusual” for users to keep all of their email in one
`
`place, and for other users to crate folders based on subject matter categories, or for
`
`users to employ different strategies with respect to retaining and deleting messages.
`
`(Id., 96:16-97:18.) It would have been apparent to a person of ordinary skill in the
`
`art (and even end users of email products) that the organization schemes that work
`
`for one user might not work for another, consistent with the diversity of techniques
`
`human beings employ to organize physical letters in the “real” world.
`
`23. Accordingly, a person of ordinary skill in the art would have treated
`
`
`
`12
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0014
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`Crumlish’s comments as mere suggestions that reflect the author’s personal
`
`preferences, not a mandate that email must be organized in a particular way. And a
`
`skilled artisan would have understood that those preferences have no bearing on the
`
`motivation to employ the particular technological approach for storing new mail in
`
`a separate folder implemented by Pegasus Mail.
`
`24. Dr. Surati next cites a statement from Crumlish that new email
`
`“typically appears with some indicator that it’s new, such as the Subject line
`
`appearing in bold, or a bullet or checkmark appearing next to the new
`
`messages.” (Ex. 1013, ¶63 (quoting Ex. 1110 at 048) (boldface added by Dr.
`
`Surati).) Dr. Surati appears to suggest that these user interface indicators would have
`
`taught away from the new folder technique of Pegasus Mail. (Id.) This argument is
`
`unpersuasive for at least two reasons.
`
`25. First, I am informed by counsel that under applicable patent law, the
`
`mere disclosure of alternative designs in a prior art reference does not amount to a
`
`“teaching away,” where those alternative designs do not discredit or otherwise
`
`discourage use of other disclosed techniques. This principle certainly applies here,
`
`as the statements cited by Dr. Surati merely recite capabilities of “typical” email
`
`programs, and as such, would not have discouraged a skilled artisan from following
`
`the path set out by Crumlish’s description of Pegasus Mail.
`
`26. The lack of any discouragement is further demonstrated by the fact that
`
`
`
`13
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0015
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`the cited statements from Crumlish identify the Subject line appearing in bold and
`
`the bullets or checkmarks as mere examples of how to visually differentiate new
`
`from old messages. (Ex. 1110 at 048 (“Unread (usually new) mail typically appears
`
`with some indicator that it’s new, such as the Subject line appearing in bold, or a
`
`bullet or checkmark appearing next to new messages.”) (underlining added).)
`
`Pegasus Mail itself also provides “some indicator that [the email] is new,” i.e. by
`
`placing it in a separate new mail folder. (Id. at 064-065, Fig. 2.15).) Nothing in
`
`Crumlish suggests that this approach is unacceptable or even inferior in any way.
`
`27. Second, the statements that Dr. Surati identifies relate to user-facing
`
`user interface features for identifying new messages, whereas I cited Crumlish in
`
`combination with Abiko for its disclosure of an underlying storage technique in
`
`which new messages were initially stored in a separate new mail folder. (Ex. 1102,
`
`¶¶101-102.) As explained in my opening declaration, a skilled artisan would have
`
`been motivated to adapt Crumlish’s approach to Abiko to obtain the benefit of
`
`allowing Abiko’s mail program to separate new messages (which are of more
`
`immediate concern to the user) from older ones. (Id., ¶103.) These benefits are not
`
`impacted by Crumlish’s identification of exemplary visual indicators for separating
`
`new from older email messages.
`
`
`
`14
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0016
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`V. RESPONSE TO DR. SURATI’S OPINIONS ON WHETHER
`DISCLOSURES
`IN ABIKO UNDERMINE MY
`STATED
`MOTIVATIONS TO COMBINE
`28. Dr. Surati next suggests that it would be improper to modify Abiko to
`
`only process and display new messages. (Ex. 2013, ¶¶68-74.) Dr. Surati contends
`
`that Abiko only discloses processing all mail messages and cannot properly be
`
`adapted to only process only new messages. (Id.)
`
`29. Dr. Surati’s argument cannot be squared with the plain language of
`
`Abiko that I cited in my opening declaration. (Ex. 1102, ¶53.) Abiko plainly states:
`
`“The received messages used to create the menu information including identifying
`
`senders may include all received messages or only received messages that satisfy
`
`prescribed conditions.” (Abiko, ¶0011 (underlining added).) The “menu
`
`information” in this statement plainly includes “‘Sender selection by mail volume
`
`menu’ information” (id., ¶0121 (underlining added)), i.e., the information used to
`
`create the sender screen shown in Figure 10(b). (Id., ¶¶0121, 0122.)
`
`30. Abiko’s statement that sender information can be based on all received
`
`messages or some subset “that satisfy prescribed conditions” (id., ¶0011) directly
`
`refutes Dr. Surati’s suggestion that the sender information displayed in Figure 10(b)
`
`must account for all received messages. As I fully explained in my opening
`
`declaration, it would have been obvious based on disclosures in Abiko alone “to
`
`create the sender table and menu (e.g., Figs. 8, 10) – and thus count the number of
`
`
`
`15
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0017
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`distinct senders – based on received messages that were new (unread).” (Ex. 1102,
`
`¶95.) I further explained why this feature would been obvious in further view of
`
`Crumlish, which discloses a particular technique for temporarily storing new
`
`messages in a separate folder. (Id., ¶¶96-103.) Under either approach, the
`
`motivation to combine is straightforward and compelling – “new messages generally
`
`hold more immediate importance to the user because their contents are yet
`
`unknown,” and “may require immediate attention and further action.” (Id., ¶96.)
`
`31. Dr. Surati also contends that the Petitioner did not explain how the
`
`proposed combination would operate with respect to read and unread messages.
`
`(Ex. 2013, ¶73.) Dr. Surati appears to suggest that the Petitioner was required to
`
`describe further user interface mechanisms in Abiko for allowing the user to access
`
`both read and unread messages. (Id.) But again this argument is refuted by ¶0011
`
`of Abiko, which makes clear that the sender table and menu may either include “all
`
`received messages” or “only received messages that satisfy prescribed conditions.”
`
`(Abiko, ¶0011.) Abiko thus discloses both possibilities, and expressly discloses an
`
`embodiment in which the sender table and menu includes “all received messages,”
`
`which would have included both read and unread messages.
`
`32. Dr. Surati also attempts to discount the importance of the numerical
`
`value shown in the last row of the Abiko sender table and menu (Figs. 8, 10) by
`
`arguing that the number is used in the context of selecting a row on the interface.
`
`
`
`16
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0018
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`(Ex. 2013, ¶77.) Dr. Surati thus contends that this number would not have had “the
`
`elevated level of importance” to warrant highlighting it on a displayed icon. (Id.)
`
`33.
`
`I respectfully disagree. As I explained extensively in my opening
`
`declaration, the key feature of Abiko is the ability to organize and group email
`
`messages based on their respective senders. (Ex. 1102, ¶105 (citing Abiko, Ex.
`
`1109, ¶¶0004-0005).) Figures 8 and 10(b) of Abiko, for example, show a sender
`
`table and menu organized around the four distinct senders, who collectively sent 37
`
`mail messages. (Ex. 1102, ¶¶50-51 (citing Abiko, Figs. 8 & 10(b)).) Because of the
`
`sender-centric nature of the sender table and menu in Abiko, it would not have made
`
`sense to a person of ordinary skill in the art to place the total message count (e.g.
`
`“37”) in the email application’s icon in userbar 600 of Ording, as that number has
`
`far less significance in the context of the Abiko sender table and menu. A skilled
`
`artisan would have found it obvious instead for the numeric character to correspond
`
`to the number of distinct items in the Abiko sender list, i.e. the number of distinct
`
`senders of received email messages.
`
`VI. RESPONSE TO DR. SURATI’S OPINIONS ON MCPHERSON AND
`DEPENDENT CLAIMS 6, 12 AND 18
`34. My opening declaration explained that the “notification bubble”
`
`described in McPherson disclosed the display of “at least one preview of content,”
`
`and thus rendered claims 6, 12, and 18 obvious in combination with the other
`
`references. (Ex. 1102, ¶¶135-137, 140-143.)
`
`
`
`17
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0019
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`
`35. Dr. Surati contends that a person of ordinary skill in the art would not
`
`have been motivated to combine McPherson in this manner because, according to
`
`him, McPherson’s description of the “notification bubble” relates to the PocketPC
`
`instant messaging functionality, not its email features. (Ex. 2013, ¶80.) Dr. Surati
`
`therefore asserts that a skilled artisan would not have adapted McPherson’s instant
`
`messaging “notification bubble” to the email systems in Ording, Abiko, and
`
`Crumlish. Dr. Surati’s argument is unpersuasive for a number of reasons.
`
`36. First, a person of ordinary skill in the art would have found
`
`McPherson’s “notification bubble” feature adaptable to both instant messaging and
`
`email systems. Chapter 20 of McPherson that Dr. Surati submits with his
`
`declaration, in fact, specifically explains in connection with the email interface: “If
`
`a new message arrives while the device is connected, Inbox will notify you. You will
`
`see a notification bubble or hear a sound, unless notification sounds are turned off.”
`
`(Ex. 2016, at 30 (emphasis added).) Dr. Surati did not address this disclosure in his
`
`declaration. I note that McPherson uses the same term “notification bubble” to
`
`describe the same instant messaging notification and preview feature that I cited in
`
`my opening declaration for claims 6, 12, and 18. (Ex. 1102, ¶135.)
`
`37.
`
`I acknowledge that McPherson’s chapter on email (Chapter 20) does
`
`not provide a specific screenshot or description of the “notification bubble” for
`
`email, but it also does not suggest that the email notification bubbles show different
`
`
`
`18
`
`Facebook's Exhibit No. 1129
`IPR2019-00925 - Page 0020
`
`

`

`Reply Declaration of Sandeep Chatterjee, Ph.D.
`
`information or lacks a preview of

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