UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`LINKEDIN CORPORATION,
`Petitioner,
`
`v.
`
`EBUDDY TECHNOLOGIES B.V.,
`Patent Owner.
`
`IPR2022-00164
`U.S. Patent No. 8,230,135
`
`PETITION FOR INTER PARTES REVIEW OF
`U.S. PATENT NO. 8,230,135
`
`Mail Stop “Patent Board”
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`TABLE OF CONTENTS
`
`RENDERS THOSE CLAIMS OBVIOUS IN VIEW OF CHEUNG
`
`
`
`
`
`I. MANDATORY NOTICES ...................................................................1
`A. Real Party-In-Interest (37 C.F.R. §42.8(b)(1)) ................................1
`B.
`Identification of Related Matters (37 C.F.R. §42.8(b)(2)) .................1
`C.
`Counsel and Service Information (37 C.F.R. §§42.8(b)(3) & (b)(4)) ..2
`D.
`Payment of fees (37 C.F.R. §42.103) .............................................2
`II.
`INTRODUCTION ...............................................................................3
`III. STATEMENT OF PRECISE RELIEF REQUESTED FOR EACH
`CHALLENGED CLAIM ......................................................................3
`A. Claims for Which Review Is Requested .........................................3
`B.
`Statutory Grounds of Challenge ....................................................4
`IV. CLAIM CONSTRUCTION ..................................................................5
`V. A PERSON HAVING ORDINARY SKILL IN THE ART ........................6
`VI. OVERVIEW OF THE STATE OF THE ART .........................................6
`A. U.S. Patent App. Pub. No. 2003/0208545 to Eaton (“Eaton”)
`(Ex[1006]) .................................................................................9
`B. U.S. Patent App. Pub. No. 2004/0061716 to Cheung (“Cheung”)
`(Ex[1007]) ............................................................................... 13
`C. Korean Patent Publication No. 2000-0036288 to Kim (“Kim”)
`(Ex[1008]) ............................................................................... 16
`D. U.S. Patent No. 7,590,696 to Odell (“Odell”) (Ex[1016]) ............... 18
`VII. THE ’135 PATENT ........................................................................... 20
`VIII. SUMMARY OF THE PROSECUTION HISTORY ............................... 23
`IX. GROUND 1: EATON ANTICIPATES CLAIMS 1-3, 6, 7 AND 9 AND/OR
`AND/OR ODELL. ............................................................................. 24
`A.
`Independent Claim 1 ................................................................. 24
`B. Dependent Claim 2 ................................................................... 47
`C. Dependent Claim 3 ................................................................... 49
`
`i
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`D. Dependent Claim 6 ................................................................... 50
`E. Dependent Claim 7 ................................................................... 51
`F.
`Dependent Claim 9 ................................................................... 52
`G. Motivation to Combine Eaton with Cheung and/or Odell ...... 53
`X. GROUND 2: CLAIMS 1-3 AND 6-10 ARE OBVIOUS OVER EATON
`ALONE AND/OR IN VIEW OF CHEUNG AND/OR ODELL ............... 56
`A. Dependent Claim 8 ................................................................... 57
`B. Dependent Claim 10.................................................................. 61
`XI. GROUND 3: KIM ANTICIPATES AND/OR RENDERS OBVIOUS
`CLAIMS 1-3 AND 9. ......................................................................... 62
`A.
`Independent Claim 1 ................................................................. 62
`B. Dependent Claim 2 ................................................................... 74
`C. Dependent Claim 3 ................................................................... 75
`D. Dependent Claim 9 ................................................................... 76
`XII. GROUND 4: CLAIMS 1-3 AND 6-10 ARE OBVIOUS OVER KIM
`ALONE AND/OR IN VIEW OF CHEUNG .......................................... 76
`A. Dependent Claim 6 ................................................................... 77
`B. Dependent Claim 7 ................................................................... 79
`C. Dependent Claim 8 ................................................................... 79
`D. Dependent Claim 10.................................................................. 81
`E. Motivation to Combine Kim with Cheung ........................... 82
`XIII. THE BOARD SHOULD NOT DENY INSTITUTION UNDER §314(a)... 84
`XIV. CONCLUSION ................................................................................. 86
`
`
`
`
`
`
`
`ii
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Cases
`Amber.IO, Inc. D/B/A Two Tap v. 72Lux, Inc. D/B/A Shoppable,
`IPR2020-00015, Paper 8 (PTAB April 1, 2020).......................................... 23
`Apple Inc. v. Fintiv, Inc.,
`IPR2020-00019, Paper 11 (PTAB Mar. 20, 2020)............................ 84, 85, 86
`Apple, Inc. v. Omni Medsci, Inc.,
`IPR2020-00029, Paper 7 (PTAB April 22, 2020) ................................... 23, 27
`Dish Network L.L.C. v. Broadband iTV, Inc.,
`IPR2020-01359, Paper 15 (PTAB Feb. 12, 2021) ....................................... 85
`eBuddy Technologies B.V. v. LinkedIn Corporation,
`No. 20-cv-01501 (D. Del.)......................................................... 1, 84, 85, 86
`Google LLC v. Uniloc 2017 LLC,
`IPR2020-00115, Paper 10 (PTAB May 12, 2020) ....................................... 86
`Sotera, Wireless, Inc. v. Masimo Corp.,
`IPR2020-01019, Paper 12 (PTAB Dec. 1, 2020)......................................... 86
`Wilson Wolf Manufacturing Corporation v. Brammer Bio, LLC, C.A.
`No. 19-2315-RGA, D.I. 22, 4................................................................... 84
`Statutes
`35 U.S.C. §102 .....................................................................................passim
`35 U.S.C. § 103 ..................................................................................... 3, 4, 5
`35 U.S.C. §112 ............................................................................................. 5
`35 U.S.C. §§ 315(e) ...................................................................................... 4
`
`iii
`
`
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`
`Other Authorities
`37 C.F.R. §42.8(b) .................................................................................... 1, 2
`37 C.F.R. § 42.10(b)...................................................................................... 2
`37 C.F.R. §42.103 ......................................................................................... 2
`37 C.F.R. § 42.108 ........................................................................................ 5
`37 C.F.R. § 42.300 ........................................................................................ 3
`37 C.F.R. § 42.302 ........................................................................................ 4
`
`
`
`
`iv
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`EXHIBIT LIST
`
`Exhibit No.
`
`Description
`
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`1014
`
`1015
`
`U.S. Patent No. 8,230,135 to Taylor
`
`File History for Application No. 11/637,514
`
`File History for U.S. Patent No. 8,230,135 to Taylor
`
`Declaration of Dean Willis (“Willis Decl.”)
`
`Curriculum Vitae of Dean Willis
`
`U.S. Patent App. Pub. No. 2003/0208545 to Eaton
`
`U.S. Patent App. Pub. No. 2004/0061716 to Cheung
`
`Korean Patent Publication No. 2000-0036288 to Kim
`
`Return of Service in Related Action
`
`Patent Owner’s Preliminary Infringement Contentions in
`Related Action
`
`Scheduling Order in Related Action
`
`First Amended Complaint in Related Action
`
`U.S. Patent No. 8,402,179 to Taylor
`
`Reserved
`SmallTalk-80 The Language and its Implementation,
`Addison Wesley, ISBN 0-201-11371-6 (1983)
`
`
`v
`
`
`
`

`

`
`
`
`Exhibit No.
`
`Description
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`1016
`
`1017
`
`1018
`
`1019
`
`1020
`
`1021
`
`1022
`
`1023
`
`1024
`
`1025
`
`U.S. Patent No. 7,590,696 to Odell
`RFC 3261 “SIP: Session Initiation Protocol”, Rosenberg et.
`al., IETF, June 2002
`RFC 3428 “Session Initiation Protocol (SIP) Extension for
`Instant Messaging”, Campbell, et. al., IETF, December
`2002
`RFC 3920 “Extensible Messaging and Presence Protocol
`(XMPP): Core”, St. Andre, IETF, October 2004
`RFC 3921 “Extensible Messaging and Presence Protocol
`(XMPP): Instant Messaging and Presence”, St. Andre,
`IETF, October 2004
`“Exploring the JDS Linux Desktop”, Adelstein & Heiser,
`O’Reilly Media, September 2004, ISBN-10:
`9780596007522
`“Chat and Instant Messaging Systems (synchronous):
`Report 2/ 3”, Kinsel et. al., International Review of
`Research in Open and Distance Learning Volume 3,
`Number 2, ISSN: 1492-3831, October 2002.
`“GoToMyPC 4.0”, Greg Keiser, ZDNet, August 18, 2003
`https://www.zdnet.com/article/gotomypc-4-0/
`“Apple Introduces Apple Remote Desktop 2”, Apple Press
`Release, June 21, 2004,
`https://www.apple.com/newsroom/2004/06/21Apple-
`Introduces-Apple-Remote-Desktop-2/
`“How to set up Google Talk on Mac OS X with Adium”,
`Matt Maldre, August 25, 2005
`https://www.spudart.org/blog/how-set-google-talk-mac-os-
`x-adium/
`
`vi
`
`
`
`

`

`
`
`
`Exhibit No.
`
`Description
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`1026
`
`1027
`
`1028
`
`1029
`
`1030
`
`1031
`
`1032
`
`1033
`
`1034
`
`1035
`
`1036
`
`“Design Patterns for High Availability”, Embedded, July
`31, 2002 https://www.embedded.com/design-patterns-for-
`high-availability/
`“Web Database Applications with PHP & MySQL, 2nd
`Edition 2nd Edition”, Williams and Lane, O’Reilly Press,
`May 16, 2004, ISBN-10 : 9780596005436
`“Fedora Linux A Complete Guide to Red Hat's Community
`Distribution”, Chris Tyler, O’Reilly Media, October 17,
`2006, ISBN-10 0596529740
`“Open Source Messaging Application Development
`Building and Extending Gaim”, Sean Egan, Apress, July
`26, 2005 ISBN-10 1430200472
`“Instant Messaging and Presence Service (OMA-IMPS)
`v1.2”, Open Mobile Alliance, May of 2004
`
`U.S. Patent No. 7,469,301 to Daniell
`
`“A History of the GUI”, Jeremy Reimer, Ars Technica,
`May 5, 2005
`http://www.freeemailtutorials.com/microsoftOutlook2003/i
`ncomingMailOutlook2003/newMailDesktopAlert.php
`“TaskbarNotifier, a skinnable MSN Messenger-like Popup
`in C# and now in VB.NET too”, Codeproject.com, Mar.
`30, 2003
`
`U.S. Patent No. 8,099,464 to Cooperman
`
`“Getting started with HTML”, Dave Raggett, May 24,
`2005, https://www.w3.org/MarkUp/Guide/
`
`vii
`
`
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`I. MANDATORY NOTICES
`A. Real Party-In-Interest (37 C.F.R. §42.8(b)(1))
`Petitioner LinkedIn Corporation (“LinkedIn”) is a real party-in-interest.
`
`Petitioner also identifies Microsoft Corporation (“Microsoft”) as a real party-in-
`
`interest, but solely because LinkedIn is a wholly-owned subsidiary of Microsoft.
`
`Identification of Related Matters (37 C.F.R. §42.8(b)(2))
`B.
`Patent Owner has asserted U.S. Patent No. 8,230,135 (the “’135 Patent”)—
`
`along with related U.S. Patent Nos. 8,402,179 (the “’179 Patent”), 8,510,395 (the
`
`“’395 Patent”), and 9,584,453 (the “’453 Patent”)—against LinkedIn in co-pending
`
`litigation, eBuddy Technologies B.V. v. LinkedIn Corporation, No. 20-cv-01501
`
`(D. Del.) (“Delaware Action”). LinkedIn was served with the original complaint in
`
`the Delaware Action on November 16, 2020. Ex[1009], 2. Patent Owner has
`
`asserted Claims 1-3 and 6-10 of the ’135 Patent against LinkedIn. Ex[1010]. Trial
`
`is currently set to begin on June 12, 2023. Ex[1011], 16.
`
`Concurrently with this Petition, Petitioner has filed or will file petitions for
`
`IPR of each of the related patents that Patent Owner asserts against Petitioner in
`
`the Delaware Action. Because the patents are related, Petitioner respectfully
`
`requests that the same panel review all four petitions.
`
`1
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`C. Counsel and Service Information (37 C.F.R. §§42.8(b)(3) & (b)(4))
`Petitioner designates the following Lead and Backup Counsel. Concurrently
`
`filed with this Petition is a Power of Attorney for appointing the following Lead
`
`and Backup Counsel, per 37 C.F.R. § 42.10(b). Service via hand-delivery may be
`
`made at the postal mailing addresses below. Petitioner consents to electronic
`
`service by e-mail at the following address: linkedin-135ipr@pillsburylaw.com.
`
`Lead Counsel
`
`Back-Up Counsel
`
`Matthew W. Hindman Christopher Kao
`
`(Reg. No. 57,396)
`(Pro hac vice motion to be filed once
`authorized)
`PILLSBURY WINTHROP SHAW
`Brock S. Weber
`PITTMAN LLP
`(Pro hac vice motion to be filed once
`2550 Hanover Street
`authorized)
`Palo Alto, CA 94304
`PILLSBURY WINTHROP SHAW
`Telephone: 650.233.4087
`PITTMAN LLP
`Facsimile: 650.233.4545
`Email:
`Four Embarcadero Center, 22nd Floor
`matthew.hindman@pillsburylaw.com
`San Francisco, CA 94111
`Telephone: 415.983.1000
`Facsimile: 415.983.1200
`Email:
`christopher.kao@pillsburylaw.com
`Email:
`brock.weber@pillsburylaw.com
`
`Payment of fees (37 C.F.R. §42.103)
`D.
`Petitioner authorizes the Patent and Trademark Office to charge Deposit
`
`Account No. 033975 for the petition fee and for any other required fees.
`
`2
`
`
`
`

`

`
`
`II.
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`INTRODUCTION
`Petitioner LinkedIn hereby petitions to institute inter partes review (“IPR”)
`
`of Claims 1-3 and 6-10 of U.S. Patent No. 8,230,135 (“’135 Patent”) (Ex[1001]),
`
`and cancel those claims as unpatentable under 35 U.S.C. §§ 102 and 103.
`
`The prior art references presented in this Petition—Eaton (Ex[1006]),
`
`Cheung (Ex[1007]), Kim (Ex[1008]), and Odell (Ex[1016])—disclose systems and
`
`methods for providing event notifications as titles for a process or application. The
`
`invalidity grounds herein therefore establish that Claims 1-3 and 6-10 of the ’135
`
`Patent (the “Challenged Claims”) were anticipated and/or obvious before the date
`
`of the alleged invention in December 2005. None of the prior art presented in this
`
`Petition was cited or discussed during original prosecution of the applications that
`
`led to the ’135 Patent.
`
`Accordingly, Claims 1-3 and 6-10 of the ’135 Patent are invalid under 35
`
`U.S.C. §§ 102 and 103.
`
`III. STATEMENT OF PRECISE RELIEF REQUESTED FOR EACH
`CHALLENGED CLAIM
`A. Claims for Which Review Is Requested
`Petitioner respectfully requests review of Claims 1-3 and 6-10 of the ’135
`
`Patent pursuant to 37 C.F.R. § 42.300 and cancellation of those claims as
`
`unpatentable. Petitioner certifies that it is not barred or estopped from requesting
`
`3
`
`
`
`

`

`
`
`IPR on the identified grounds, including under any of 35 U.S.C. §§ 315(e) or
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`325(e) or 37 C.F.R. § 42.302(b) or (c).
`
`Statutory Grounds of Challenge
`B.
`The Challenged Claims are unpatentable under 35 U.S.C. §§ 102 and 103, as
`
`shown in the grounds below.
`
`Ground
`
`Invalidity
`
`Exhibit(s)
`
`1
`
`Claims 1-3, 6, 7, and 9 are anticipated by and/or
`
`1006, 1007, 1016
`
`obvious over Eaton (Ex[1006]) in view of
`
`Cheung (Ex[1007]) and/or Odell (Ex[1016])
`
`under 35 U.S.C. §§ 102(b) and 103.
`
`2
`
`Claims 1-3 and 6-10 would have been obvious
`
`1006, 1007, 1016
`
`over Eaton (Ex[1006]) alone and/or in view of
`
`Cheung (Ex[1007]) and/or Odell (Ex[1016])
`
`under 35 U.S.C. § 103.
`
`3
`
`
`
`Claims 1-3 and 9 are anticipated by and/or
`
`1008
`
`obvious over Kim (Ex[1008]) in view of the
`
`knowledge of a person of ordinary skill under 35
`
`4
`
`
`
`

`

`
`
`
`4
`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`U.S.C. §§ 102(b) and 103.
`
`Claims 1-3 and 6-10 would have been obvious
`
`1008, 1007
`
`over Kim (Ex[1008]) alone and/or in view
`
`Cheung (Ex[1007]) under 35 U.S.C. § 103.
`
`IV. CLAIM CONSTRUCTION
`Petitioner contends that, unless otherwise specifically noted herein, the claim
`
`terms in the ’135 Patent are accorded their ordinary and customary meaning that
`
`they would have to a person having ordinary skill in the art at the time of the
`
`alleged invention (“PHOSITA”). Petitioner’s interpretation of the claim terms is
`
`further explained for each claim limitation in relation to the prior art discussed in
`
`invalidity Grounds 1-4, below.1
`
`
`1 Petitioner reserves the right to address any claim construction positions taken by
`
`the Patent Owner in its Preliminary Response, including under 37 C.F.R. §
`
`42.108(c). Petitioner further reserves its right to show that claims of the ’135
`
`Patent are invalid under 35 U.S.C. §112 in the co-pending litigation.
`
`5
`
`
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`
`V. A PERSON HAVING ORDINARY SKILL IN THE ART
`A PHOSITA with respect to the ’135 Patent would have a Bachelor’s degree
`
`in Computer Science, Computer Engineering, Electrical Engineering, or a related
`
`field, plus at least two years of professional experience in telecommunications or
`
`computer networking, and would have been familiar with popular Internet
`
`applications like web browsers, Google’s Gmail, AOL Instant Messenger, ICQ,
`
`Jabber, Trillian, and Yahoo Instant Messenger; development using Microsoft
`
`Windows, Java, Linux and the X-Window System (X11); and Internet Engineering
`
`Task Force (IETF) standards including “Extensible Messaging and Presence
`
`Protocol (XMPP): Core.” Ex[1004], Declaration of Dean Willis, ¶¶32-35.
`
`Alternatively, a PHOSITA would possess equivalent additional formal education
`
`such as graduate studies, or work experience to replace formal education. Id., ¶34.
`
`VI. OVERVIEW OF THE STATE OF THE ART
`The ’135 Patent concerns “modifying a title associated with a process to
`
`include information about an event that calls for user notification,” including in
`
`“[p]opular instant messaging services on the public Internet,” such as “.NET
`
`Messenger Service, AOL Instant Messenger, Excite/Pal, Gadu-Gadu, Google Talk,
`
`iChat, ICO, Jabber, Qnext, QQ, Meetro, Skype, Trillian and Yahoo! Messenger.”
`
`Ex[1001], Title, Abstract, 1:25-44, 1:62-1:67. “These services owe many ideas to
`
`6
`
`
`
`

`

`
`
`an older (and still popular) online chat medium known as Internet Relay Chat
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`(IRC).” Id., 1:44-46. Thus, as the ’135 Patent concedes, the instant messaging
`
`(“IM”) space and providing an event notification in the title of a process or
`
`application was a well-developed and crowded field. See also Ex[1004], ¶¶39-68.
`
`For example, by December 2005, most computer systems, including those
`
`running Microsoft Windows or Apple’s OS, included a graphical user interface
`
`(GUI) that had windows associated with applications running on the system.
`
`Ex[1004], ¶¶52-64. “The concept of computer windows is most commonly traced
`
`to the Smalltalk system developed at Xerox’s Palo Alto Research Center (PARC),
`
`starting around 1973.” Id., ¶54. “Displaying a message to a user by creating a new
`
`window and setting the window’s properties [such as the title] to display the
`
`message was (and still would be) a fundamental, very basic use of the windowed
`
`GUI model.” Id., ¶59.
`
`For example, by 2003, Microsoft’s MSN Messenger (Microsoft’s Instant
`
`Messaging client) and Outlook (E-mail program) were both using a “new message
`
`notification” commonly called “toast,” in which new event notification messages
`
`“popped up” (like a pop-up toaster) in the taskbar. Id., ¶60. An example is
`
`reproduced below (with the event notification boxed in red):
`
`7
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`Id. (quoting Ex[1033]). By 2003, Microsoft’s Outlook program also included a
`
`new window that appeared in the bottom right corner of a user’s screen to notify a
`
`user of a new mail event:
`
`
`Id. (quoting Ex[1033]). MSN messenger had a similar feature by 2003. Id., ¶61.
`
`Id., ¶¶61-64 (quoting Ex[1035]).
`
`
`
`8
`
`
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`Likewise, “using a title to convey pertinent information is a basic,
`
`
`
`
`fundamental aspect of writing web pages.” Id., ¶66. The “<title>” element is so
`
`fundamental, in fact, that is commonly included as the first step of explaining how
`
`to write an HTML (HyperText Markup Language) document. Id., ¶¶65-66 (citing
`
`Ex[1036]).
`
`A. U.S. Patent App. Pub. No. 2003/0208545 to Eaton (“Eaton”)
`(Ex[1006])
`Eaton is a U.S. Patent Application that was filed on May 1, 2002. It was
`
`published on November 6, 2003. Ex[1006]. Eaton is therefore prior art to the ’135
`
`Patent under at least pre-AIA 35 U.S.C. §102(b).
`
`Eaton discloses a communications system that includes IM messaging and
`
`an IM user interface for displaying event notifications in the title or titlebar of the
`
`IM interface. Eaton discloses a server receiver 140 that is “coupled to and receives
`
`information about a plurality of events 180” that “can include, for example,
`
`physical events 210 such as sporting events, television or radio broadcast events
`
`200, wireless content events 220, internet events 230, chat session events 240, or
`
`an equivalent.” Ex[1006] at [0028]. This is shown below in Figure 1, in which
`
`server 110 (shaded in blue) receives a plurality of events (shaded in green) and has
`
`a “server processor 150” (shaded in red) for processing such events. See id.,
`
`[0026]-[0030].
`
`9
`
`
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`
`
`
`
`
`
`
`
`
`
`Eaton also discloses processing and displaying event notifications at the
`
`client side. For example, “the event presence notification messages can be
`
`received by the device receiver 330 from the server 110.” Id., [0038]. This is
`
`depicted below in Figure 3 from Eaton in which an instant messaging device 320 is
`
`depicted (as an example of the instant messaging devices shown above in Figure
`
`1), and the device receiver is shaded in blue, the device processor is shaded in red,
`
`and the user interface is shaded in purple:
`
`10
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`
`
`
`
`
`
`
`Id., [0036]-[0038].
`
`Eaton discloses storing the event notifications in a title array. For instance,
`
`“server memory 160” depicted above in Figure 1 “stores a plurality of screen
`
`names 280” and “[e]ach screen name 290 of the plurality of screen names 280
`
`represents one or more events such as event 300 of the plurality of events 180.”
`
`Id., [0031] (emphasis added). This is depicted in Figure 2 of Eaton (below) in
`
`which each screen name 280 stored in the server memory 160 is associated with an
`
`event 300 (shaded in green) from the plurality of events 180 depicted in Figure 1.
`
`Id.
`
`11
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`
`
`
`
`
`
`
`Eaton also discloses that the server memory 160 stores an array of event
`
`notifications in Figure 6, as shown with the same annotations below. Id., [0056]-
`
`[0058], Fig. 6.
`
`
`
`
`
`
`
`
`
`
`Eaton further discloses displaying the event notifications on a user interface
`
`as title-area-display-items. For example, Eaton discloses that each of the plurality
`12
`
`
`
`

`

`
`
`of IM devices 120 includes “an instant message user interface 360,” as depicted in
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`Figure 4, below (the user interface is shaded in purple and exemplary event
`
`notifications are shaded in green). Eaton also discloses displaying event
`
`notifications in Figure 7, reproduced below with similar shading used for Figure 4.
`
`Eaton Figure 4
`
`
`
`
`
`
`Eaton Figure 7
`
`
`
`
`
`
`
`
`
`
`
`
`See e.g., id., [0037], [0045], [0059]-[0063].
`
`B. U.S. Patent App. Pub. No. 2004/0061716 to Cheung (“Cheung”)
`(Ex[1007])
`Cheung is a U.S. Patent Application that was filed on September 30, 2002.
`
`It was published on April 1, 2004. Ex[1007]. Cheung is therefore prior art to
`
`the ’135 Patent under at least pre-AIA 35 U.S.C. §102(b).
`
`Cheung discloses an event notification system that can be used in Microsoft
`
`OFFICE applications and Microsoft’s MSN instant messaging service, for
`
`instance, in which “notifications 112 such as reminders of tasks or events
`
`13
`
`
`
`

`

`
`
`created . . . are input to a database daemon 110, which provides a record in the
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`database for each such notification and makes the database available to central
`
`notification manager 104 to produce a reminder to the user in the display of a
`
`user’s PC.” Ex[1007] at [0027]-[0029]. The central notification manager 104 has
`
`a “central notification manager user interface 120.” Id., [0030].
`
`Cheung further discloses that:
`
`User interface 120 is designed to be non-intrusive and to
`
`pop-up on the display screen without stealing the focus
`
`from another application in which the user is currently
`
`working. A title bar 122 indicates that the current
`
`notification is generated by one of the OFFICE™ software
`
`programs. In this example, a line 124 provides a reminder
`
`that the user has scheduled a meeting in regard to “client
`
`support.” A line 126 indicates that the meeting is to take
`
`place “Today” at 6:00 PM, while a line 128 indicates that
`
`the meeting will be held in a second floor audio-visual
`
`conference room.
`
`14
`
`
`
`

`

`
`
`Id., [0030] (emphasis added). This is depicted in Figure 3A below (annotated to
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`show event notifications in the title shaded in green, including in the “title bar
`
`122”).
`
`
`
`
`
`See also id., Fig. 5A, [0035]-[0037].
`
`Cheung also discloses providing an associated event notification in the
`
`“taskbar” associated with an application. This is shown below in Figure 5B
`
`(annotated to show the event notification shaded in green) in which an icon 192 is
`
`provided in a “dock (or taskbar) 190,” and “[a]ssociated with icon 192 is a count
`
`194 of the number of active notifications and alerts.” Id., [0038].
`
`15
`
`
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`C. Korean Patent Publication No. 2000-0036288 to Kim (“Kim”)
`(Ex[1008])
`Kim is a Korean Patent Application that was filed on September 2, 1999. It
`
`was published on July 5, 2000. Ex[1008].2 Kim is therefore prior art to the ’135
`
`Patent under at least pre-AIA 35 U.S.C. §102(b).
`
`Kim discloses “receiv[ing] real-time information to be displayed on the title
`
`bar on the Windows display screen of the personal computer from the information
`
`server and stor[ing] it in temporary memory, and display[ing] the information on
`
`the title bar whenever new information is provided to allow the users to easily
`
`obtain information at any time.” Ex[1008], 9-2 (emphasis added). Kim discloses
`
`
`2 Ex[1008] includes Kim, a certified English translation of Kim, and the
`
`translator’s affidavit.
`
`16
`
`
`
`

`

`
`
`that this real-time information can include events such as “stock prices,
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`advertisements, and breaking news” (Ex[1008], Abstract) received at the user’s
`
`computer from, for example, “a stock information server, an advertisement server,
`
`a breaking news server, [] a text broadcasting server, or a combination thereof” (id,
`
`9-2).
`
`After receiving real-time information at the user’s computer from the real-
`
`time information server (id.), Figure 3 of Kim below shows an example in which a
`
`breaking news event notification—“2:10pm Shin Chang-Won arrested (Yonhap
`
`News)”—is provided on the title bar of a Microsoft WordPad application window
`
`(the event notification message is shaded in green).
`
`17
`
`
`
`

`

`
`
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`
`
`D. U.S. Patent No. 7,590,696 to Odell (“Odell”) (Ex[1016])
`Odell is a patent filed on July 21, 2004. It issued on September 15, 2009.
`
`Ex[1016]. Odell is therefore prior art to the ’135 Patent under at least pre-AIA 35
`
`U.S.C. §102(e)(2).
`
`Odell discloses “communicating using an instant messaging system” (id.,
`
`1:31-33) in which “[e]ach user account may have one or more buddy lists” (i.e.,
`
`“contact lists”). Id., 2:47-47. As part of the IM communications system, Odell
`
`18
`
`
`
`
`
`

`

`
`
`discloses providing event notifications in the header, or title, of an application
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`window. For example, as shown below in Figure 16A, Odell discloses that “a
`
`notification 1600 is presented after one of a specified series of events relating to
`
`the accounts listed on the buddy lists of a set of linked accounts.” Id., 19:44-46.
`
`“The header 1602 of the notification 1600 contains [the] screen name of the linked
`
`account whose buddy list contains the account that triggered the notification,” and
`
`the “body 1604 of the notification contains the screen name of the account that
`
`triggered the notification as well as a description of the event that triggered the
`
`notification.” Id., 19:46-52. In annotated Figure 16A, the event notifications,
`
`including in the header 1602 or title, are shaded in green.
`
`
`
`
`
`19
`
`
`
`
`
`

`

`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`Odell discloses that numerous events “may cause a notification 1600 to
`
`
`
`
`appear.” Id., 19:53-54. The events “include signing on to the communications
`
`system, signing off of the communications system, going away from the
`
`communications system by putting up an away message, returning from away,
`
`going idle by not using the communications system for a specified amount of time,
`
`and returning from idle.” Id., 19:55-60.
`
`VII. THE ’135 PATENT
`The ’135 Patent claims nothing more than “modifying a title associated with
`
`a process to include information about an event that calls for user notification.”
`
`Ex[1001], Abstract, 1:62-64. The patent explains what it means by a “process”
`
`and an “event” in broad terms: “a process . . . by way of example but not
`
`limitation, [includes] an IM client process, a browser, or some other process that
`
`has a title associated therewith;” and “an event . . . by way of example but not
`
`limitation, [includes] a new mail event, a new instant message event, a reminder
`
`event, a calendar event, or some other event[.]” Id., 1:64-2:4 (“Summary” of the
`
`claimed invention).
`
`The patent states in its “Background” section that messaging services that
`
`existed when the ’135 Patent was filed, such as AOL Instant Messenger, ICQ,
`
`Jabber, Trillian, Google Talk, and Yahoo! Messenger, included features to alert
`
`20
`
`
`
`

`

`
`
`other users of an instant message event, such as a “presence information feature,
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`indicating whether people on one’s list of contacts are currently online and
`
`available to chat.” Id., 1:25-45.
`
`The patent discloses its
`
`purported invention as a simple
`
`series of steps. For instance,
`
`Figure 7 (shown here) discloses
`
`that the claimed method
`
`involves: (1) processing an
`
`event that calls for user
`
`notification; (2) generating a
`
`notification for the event; (3)
`
`storing the event notification in
`
`an array, or list, of notifications;
`
`(4) providing the notification to
`
`a process; (5) and using one or more of the event notifications as a title in
`
`association with the process. See id., 9:16-10:3.
`
`The patent depicts an example of this technique in the web browser context
`
`in Figures 3A-D, in which the titlebar or taskbar of a Firefox® browser switches
`
`21
`
`
`
`

`

`
`
`between the titles of “www.ebuddy.com” and “New Message.” Id., 5:39-6:12.
`
`Petition for Inter Partes Review of
`U.S. Patent No. 8,230,135
`
`The example of Figures 3C and 3D are excerpted below in which the text has been
`
`clarified from its original, illegible form to match the corresponding written
`
`description (id.):
`
`Figure 3C
`
`Figure 3D
`
`
`The ’135 Patent states that its technique for providing an event notification
`
`
`
`as an alternative title can be implemented with generic computer components—
`
`e.g., any “known or convenient network,” “any known or convenient server,” any
`
`“known or convenient IM network,” and “clients” that “may include any known or