Filed: February 16, 2017
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________________
`
`GOOGLE INC.
`Petitioner
`
`v.
`
`BLACKBERRY LTD.
`Patent Owner
`
`____________________
`
`Patent No. 8,402,384
`
`____________________
`
`
`
`PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 8,402,384
`
`
`
`
`
`
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`
`TABLE OF CONTENTS
`
`INTRODUCTION ........................................................................................... 1
`
`
`I.
`
`II. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8 ................................... 1
`
`III. PAYMENT OF FEES UNDER 37 C.F.R. § 42.15(a) .................................... 2
`
`IV. GROUNDS FOR STANDING ........................................................................ 2
`
`V.
`
`PRECISE RELIEF REQUESTED AND GROUNDS RAISED ..................... 2
`
`VI. LEVEL OF ORDINARY SKILL IN THE ART ............................................. 3
`
`VII. OVERVIEW OF THE ’384 PATENT AND PRIOR ART ............................. 4
`
`A.
`
`B.
`
`C.
`
`The ’384 Patent ..................................................................................... 4
`
`Cadiz ...................................................................................................... 4
`
`Ng ........................................................................................................ 10
`
`D. Matthews ............................................................................................. 10
`
`E.
`
`Smith .................................................................................................... 10
`
`VIII. CLAIM CONSTRUCTION .......................................................................... 11
`
`IX. DETAILED EXPLANATION OF GROUNDS ............................................ 12
`
`A. Ground 1: Cadiz Renders Obvious Claims 1, 4-7, and 10-13 ............ 12
`
`1.
`
`2.
`
`3.
`
`4.
`
`5.
`
`6.
`
`7.
`
`Claim 1 ...................................................................................... 12
`
`Claim 4 ...................................................................................... 45
`
`Claim 5 ...................................................................................... 46
`
`Claim 6 ...................................................................................... 47
`
`Claim 7 ...................................................................................... 49
`
`Claim 10 .................................................................................... 51
`
`Claim 11 .................................................................................... 54
`
`i
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`Claim 12 .................................................................................... 57
`
`Claim 13 .................................................................................... 60
`
`8.
`
`9.
`
`B. Ground 2: Cadiz and Ng Render Obvious Claims 2 and 3 ................. 62
`
`1.
`
`2.
`
`Claim 2 ...................................................................................... 62
`
`Claim 3 ...................................................................................... 65
`
`C. Ground 3: Cadiz and Matthews Render Obvious Claim 8 .................. 65
`
`1.
`
`Claim 8 ...................................................................................... 65
`
`D. Ground 4: Cadiz and Smith Render Obvious Claim 9 ........................ 68
`
`1.
`
`Claim 9 ...................................................................................... 68
`
`X.
`
`CONCLUSION .............................................................................................. 71
`
`
`
`
`
`
`
`
`
`ii
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`
`TABLE OF AUTHORITIES
`
` Page(s)
`
`Federal Cases
`KSR Int’l Co. v. Teleflex Inc.,
`550 U.S. 398 (2007) .....................................................................................passim
`
`Federal Statutes
`
`35 U.S.C. § 102(b) ..................................................................................................... 3
`
`35 U.S.C. § 102(e) .................................................................................................... 3
`
`35 U.S.C. § 103(a) ..................................................................................................... 2
`
`Regulations
`
`37 C.F.R. § 42.8 ......................................................................................................... 1
`
`37 C.F.R. § 42.15(a) ................................................................................................... 1
`
`37 C.F.R. § 42.100(b) .............................................................................................. 11
`
`
`
`
`
`iii
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`
`LIST OF EXHIBITS
`
`
`U.S. Patent No. 8,402,384
`
`Declaration of Dr. Dan R. Olsen Jr.
`
`Curriculum Vitae of Dr. Dan R. Olsen Jr.
`
`Prosecution History of U.S. Patent No. 8,402,384
`
`U.S. Patent Application Publication No. 2002/0186257 (“Cadiz”)
`
`U.S. Patent Publication No. 2004/0075701 (“Ng”)
`
`RESERVED
`
`U.S. Patent Publication No. 2005/0198584 (“Matthews”)
`
`U.S. Patent No. 6,333,973 (“Smith”)
`
`European Patent Application No. EP1265157 (“Cadiz-EP”)
`
`Prosecution History of European Patent Application No. 06125884.4
`
`Caroline Rose et al., “Inside Macintosh Volume 1” (1985)
`
`“Macintosh Human Interface Guidelines,” Apple Computer, Inc.
`(1995)
`
`
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`
`
`iv
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`
`I.
`
`INTRODUCTION
`
`Google Inc. (“Petitioner”) requests inter partes review (“IPR”) of claims 1-
`
`13 (“the challenged claims”) of U.S. Patent No. 8,402,384 (“the ’384 patent”) (Ex.
`
`1001), which, according to PTO records, is assigned to BlackBerry Limited
`
`(“Patent Owner”). For the reasons set forth below, the challenged claims should be
`
`found unpatentable and canceled.
`
`II. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8
`Real Party-in-Interest: Petitioner identifies Google Inc. as the real party-in-
`
`interest.
`
`Related Matters: The ’384 patent is at issue in Blackberry Ltd. v. BLU
`
`Prods. Inc., Case No. 1:16-cv-23535 (S.D. Fla.). Petitioner is concurrently filing an
`
`IPR petition challenging all claims of continuation U.S. Patent No. 8,713,466.
`
`Counsel and Service Information: Lead counsel for Petitioner is Naveen
`
`Modi (Reg. No. 46,224), and Backup counsel are (1) Joseph E. Palys (Reg. No.
`
`46,508), (2) Phillip Citroën (Reg. No. 66,541), and (3) Arvind Jairam (Reg. No.
`
`62,759). Service information is Paul Hastings LLP, 875 15th St. N.W.,
`
`Washington, D.C., 20005, Tel.: 202.551.1700, Fax: 202.551.1705, email: PH-
`
`Google-Blackberry-IPR@paulhastings.com. Petitioner consents
`
`to electronic
`
`service.
`
`
`
`1
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`III. PAYMENT OF FEES UNDER 37 C.F.R. § 42.15(a)
`The required fees are submitted herewith. The PTO is authorized to charge
`
`any additional fees due at any time during this proceeding to Deposit Account No.
`
`50-2613.
`
`IV. GROUNDS FOR STANDING
`Petitioner certifies that the ’384 patent is available for IPR and Petitioner is
`
`not barred or estopped from requesting IPR on the grounds identified herein.
`
`V.
`
`PRECISE RELIEF REQUESTED AND GROUNDS RAISED
`
`Claims 1-13 of the ’384 patent should be canceled as unpatentable based on
`
`the following proposed grounds and prior art:
`
`Ground 1: Claims 1, 4-7, and 10-13 are obvious under 35 U.S.C. § 103(a)
`
`in view of U.S. Patent Publication No. 2002/0186257 (“Cadiz”) (Ex. 1005);
`
`Ground 2: Claims 2 and 3 are obvious under § 103(a) in view of Cadiz and
`
`U.S. Patent Publication No. 2004/0075701 (“Ng”) (Ex. 1006);
`
`Ground 3: Claim 8 is obvious under § 103(a) in view of Cadiz and U.S.
`
`Patent Publication No. 2005/0198584 (“Matthews”) (Ex. 1008); and
`
`Ground 4: Claim 9 is obvious under § 103(a) in view of Cadiz and U.S.
`
`Patent No. 6,333,973 (“Smith”) (Ex. 1009).
`
`For purposes of this proceeding, Petitioner assumes the earliest effective
`
`filing date of the ’384 patent is no earlier than November 9, 2004. Cadiz published
`
`2
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`on December 12, 2002, and Smith issued on December 25, 2001, and are therefore
`
`prior art at least under pre-AIA 35 U.S.C. § 102(b). Ng was filed on October 16,
`
`2002, and published on April 22, 2004, and therefore is prior art at least under pre-
`
`AIA 35 U.S.C. §§ 102(e) and 102(a). Matthews was filed on January 27, 2004, and
`
`therefore is prior art at least under pre-AIA 35 U.S.C. § 102(e).
`
`Ng, Ebert, Matthews, and Smith were not considered during prosecution of
`
`the ’384 patent. A publication of a European counterpart of Cadiz, EP1265157
`
`(“Cadiz-EP”) (Ex. 1010), is listed on the face of the ’384 patent, but it was not
`
`discussed or relied upon for any claim rejection during prosecution. During
`
`prosecution of European Application No. 06125884.4, which involved claims with
`
`similar limitations as the ’384 patent, the applicant was unable to overcome
`
`rejections based on Cadiz-EP. (Ex. 1011, 22-25, 160, 161, 165-66.)
`
`VI. LEVEL OF ORDINARY SKILL IN THE ART
`A person of ordinary skill in the art at the time of the alleged invention of
`
`the ’384 patent (POSA) would have had an undergraduate degree in computer
`
`science, electrical engineering, or equivalent thereof, and at least two years of
`
`3
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`experience in the relevant field, e.g., graphical user interfaces. (Ex. 1002, ¶¶13-14.)
`
`More education can supplement practical experience and vice versa.1
`
`VII. OVERVIEW OF THE ’384 PATENT AND PRIOR ART
`A. The ’384 Patent
`The ’384 patent issued on March 19, 2013, from U.S. Patent Application No.
`
`10/983,606, which was filed on November 9, 2004. It is generally directed to
`
`controlling an apparatus in which at least one dynamic bar is displayed on a main
`
`screen of a graphical user interface (“GUI”). (Ex. 1004, 377.) The dynamic bar
`
`provides interfaces for applications and functions on the apparatus, as well as an
`
`expandable pop-up interface for displaying preview information. (Id.; Ex. 1002,
`
`¶¶22-23.)
`
`Cadiz
`
`B.
`Cadiz is generally directed to “provid[ing] peripheral awareness of
`
`information to a user.” (Ex. 1005, Abstract; Ex. 1002, ¶¶25-33.) Cadiz discloses
`
`that information of interest to a user is “automatically tracked or watched via at
`
`
`
` 1
`
` Petitioner submits the declaration of Dr. Dan R. Olsen Jr. (Ex. 1002), an expert in
`
`the field of the ’384 patent. (Ex. 1002, ¶¶1-12; Ex. 1003.) For purposes of this
`
`proceeding, the time of the alleged invention includes the mid-to-late 2004 time
`
`frame up to the November 9, 2004 filing date of the ’384 patent.
`
`4
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`least one conventional communications interface for accessing one or more
`
`conventional communications sources,” and “[c]urrent information is then
`
`automatically dynamically provided in an interactive peripheral display which
`
`minimizes any potential distraction to the user.” (Ex. 1005, Abstract.) Graphical
`
`user interfaces (GUIs) were well known at the time of Cadiz, including in the
`
`context of rectangular windows, and Cadiz describes using a GUI to provide a user
`
`with notifications. (Id.; Ex. 1002, ¶¶15-21; see also Ex. 1012; Ex. 1013.)2
`
`For example, Cadiz discloses displaying on a display of a computing device
`
`a “sidebar,” which “can be generally described as a container hosting one or more
`
`columns of items in a persistent interactive display strip along one edge of a
`
`conventional display device.” (Ex. 1005, ¶[0070].) FIG. 5 of Cadiz (annotated
`
`below) “illustrates an exemplary user interface for interacting with a system and
`
`method according to the present invention,” and shows a “user interface [that]
`
`includes at least one sidebar 505 . . . for displaying iconized tickets” (annotated in
`
`red). (Id., ¶[0191].)
`
`
`
` 2
`
` Petitioner references Exs.1012 and 1013 only to demonstrate the state of the art at
`
`the time of the alleged invention and is not relying on these exhibits as a basis for
`
`any ground.
`
`5
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`
`
`
`According to Cadiz, “[d]etermining or specifying, tracking or watching, and
`
`providing the information is accomplished using at least one customizable dynamic
`
`encapsulated object, a ‘ticket,’ that when paired with a ‘viewer,’ provides
`
`peripheral awareness of information to the user.” (Id., Abstract.) Various such
`
`items are shown in the sidebar 505 of FIG. 5 (e.g., item 515).
`
`Cadiz discloses examples of information that can be shown to a user in a
`
`sidebar. For instance, an item may “represent a person or other entity,” which “is
`
`preferably represented by a graphical image representing the current availability of
`
`the entity.” (Id., ¶[0194].) To illustrate, FIG. 8A (below) shows a “peripheral
`
`6
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`awareness interface 800 showing pawns 805 associated with person items 810, 815
`
`and 820 in accordance with the present invention.” (Id., ¶[0201].) The sidebar of
`
`FIG. 8A includes various types of tracked information, including information
`
`pertaining to a calendar appointment, email messages in email folders, availability
`
`of online contacts, and a stock price. (Id., FIG. 8A.)
`
`
`
`When a person item is selected, a “person window 565” is shown, which
`
`provides “further information about the person or entity.” (Id., ¶[0194]; see also
`
`id., ¶¶[0183], [0201], FIG. 5.) The person window 565 may include “action buttons
`
`for initiating communication via any of a number of conventional communications
`
`7
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`channels or access points 570,” “communications availability function 575,” and
`
`communication history function 580. (Id., ¶[0194], FIG. 5.) FIG. 8B (below) of
`
`Cadiz is “an exemplary screen image illustrating a dynamic person window or
`
`‘enhanced tooltip’ person window 825 accessed by selection of one of the person
`
`items 815 of FIG. 8A.” (Id., ¶[0201].)
`
`
`
`The person window of FIG. 8B “provides a short summary of new messages
`
`825 and 830 sent from the person represented by the person item 820” 3 as well as
`
`“the availability via any of five individual communications channels 840, including
`
`a short message, email, voice mail, telephone call, or in person availability.” (Id.,
`
`¶[0201].)
`
`
`
` 3
`
` The reference to person item 820 is a typographical error, as the person window
`
`in FIG. 8B shows “Gavin,” who is displayed as person item 815 in FIG. 8A (not
`
`820). (Ex. 1005, FIGS. 8A-8B; Ex. 1002, ¶29.)
`
`8
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`As another example of information displayed in a sidebar, Cadiz discloses
`
`that FIG. 10 (below) “represents an email type ticket/item 1010 within another
`
`container/sidebar 1000.” (Id., ¶[0203].) Cadiz explains that the viewer 220 for
`
`displaying such a ticket “is capable of displaying specific email information, such
`
`as, for example, number of messages received, or number of messages from a
`
`particular source.” (Id., ¶[0025]; see also id., ¶[0072].) Cadiz discloses that “[u]ser
`
`selection of the email ticket/item 1000 serves to expand/open an enhanced tooltip
`
`email window 1020 which allows user interaction with received email as from
`
`within a typical email application.” (Id., ¶[0203]; Ex. 1002, ¶31.)
`
`
`
`
`
`9
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`As shown in each of FIGS. 8A and 10, a single sidebar may display one or
`
`more person items together with one or more email items, among other
`
`information. (Ex. 1002, ¶33.)
`
`C. Ng
`Ng is generally directed to “graphically providing alerts and notices on the
`
`display of [an] electronic device.” (Ex. 1006, ¶[0013].) The device display may
`
`include status indicators such as “a battery status indicator 106 [and] a received
`
`signal strength indicator (‘RSSI’) 108.” (Id., ¶[0014]; Ex. 1002, ¶34.)
`
`D. Matthews
`Matthews is generally directed to “control[ling] tiles within a sidebar” in a
`
`GUI. (Ex. 1008, Title.) Matthews, which incorporates Cadiz by reference,
`
`describes the same sidebar described in Cadiz. (Id., ¶[0049].) As one example of
`
`information presented in a tile, Matthews discloses that an email notification tile
`
`312 in the sidebar contains a listing of emails 314. (Id., FIG. 3, ¶[0058]; Ex. 1002,
`
`¶¶35-36.)
`
`E.
`Smith
`Smith is generally directed to an “integrated message center operat[ing] on
`
`telecommunications equipment, having a display and a processor, to consolidate
`
`messages of different types for viewing and manipulation by a user.” (Ex. 1009,
`
`Abstract.) Smith discloses several ways in which received messages of different
`
`10
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`types are displayed to the user. (Id., FIGS. 6-15B.) As one example, FIG. 7A of
`
`Smith shows that a list of notifications is displayed for received messages, such as
`
`calls and emails, with each entry in the list “identif[ying] a received message and
`
`includes the sender’s name 7400 and an identification icon 7500, identifying the
`
`type of message.” (Id., 8:36-43, FIG. 7A; Ex. 1002, ¶37.)
`
`VIII. CLAIM CONSTRUCTION
`Because the ’384 patent will not expire before issuance of a final written
`
`decision, for purposes of this proceeding, the claims of the ’384 patent should be
`
`given their broadest reasonable construction. See 37 C.F.R. § 42.100(b). All the
`
`terms in the challenged claims should be interpreted in accordance with their plain
`
`and ordinary meaning under the broadest reasonable interpretation standard.4
`
`Petitioner applies this understanding in the analysis of the ’384 patent in this
`
`petition.
`
`
`
` 4
`
` Any claim interpretations submitted or implied herein for the purpose of this
`
`proceeding are not binding upon Petitioner in any litigation involving the ’384
`
`patent. Moreover, Petitioner does not concede that the challenged claims are not
`
`invalid for reasons not raised herein.
`
`11
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`
`IX. DETAILED EXPLANATION OF GROUNDS
`A. Ground 1: Cadiz Renders Obvious Claims 1, 4-7, and 10-13
`1.
`Claim 1
`a)
`“A method for controlling an apparatus comprising a
`display, the method comprising:”
`
`To the extent the preamble of claim 1 is construed to be limiting, Cadiz
`
`discloses the limitations therein. (Ex. 1002, ¶¶38-42.) For example, Cadiz discloses
`
`that “an exemplary system for implementing the invention includes a computing
`
`device, such as computing device 100” (“apparatus”). (Ex. 1005, ¶[0050], FIG. 1.)
`
`As shown in FIG. 1, Cadiz’s device includes an output device 116, “such as a
`
`display.” (Id., ¶[0054], FIG. 1; Ex. 1002, ¶39.) FIG. 2 also shows that Cadiz’s
`
`device includes “any conventional display device 260.” (Ex. 1005, ¶[0074], FIG. 2;
`
`see also id., ¶[0057]; Ex. 1002, ¶40.)
`
`Cadiz discloses a method for controlling computing device 100 related to
`
`displaying a user interface, as exemplified in connection with, e.g., FIGS. 4, 5, 6B,
`
`8A, 8B, and 10. For example, Cadiz explains that information “is provided either
`
`graphically, textually, or via some combination thereof, by hosting one or items
`
`200 within one or more containers 250 for providing peripheral awareness
`
`interfaces on one or more display devices 260.” (Ex. 1005, ¶[0076]; see also id.,
`
`¶¶[0090], [0094], FIGS. 4, 5, 6A-6B, 8A-8B, 10; Ex. 1002, ¶41.)
`
`12
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`Accordingly, Cadiz discloses a method for controlling an apparatus
`
`comprising a display. (Ex. 1002, ¶42; see also citations and analysis below for the
`
`remaining elements of claim 1.)
`
`b)
`
`“displaying a dynamic bar on the display;”
`
`Cadiz discloses these features. (Ex. 1002, ¶¶43-50.) For example, Cadiz
`
`describes presenting on the display “containers,” such as a “sidebar” (“dynamic
`
`bar”), which “host[s] one or more columns of items in a persistent interactive
`
`display strip along one edge of a conventional display device.” (Ex. 1005, ¶[0070];
`
`see also id., ¶¶[0071]-[0073], [0077]-[0081], [0089], [0095]-[0099], [0167],
`
`[0176]-[0178], [0190]-[0195], [0197], [0201], [0203], FIGS. 2, 3, 4A, 5, 6A-6B,
`
`8A, 10; Ex. 1002, ¶43.) For example, FIG. 5, which “illustrates an exemplary user
`
`interface for interacting with a system and method according to the present
`
`invention,” shows a “user interface [that] includes at least one sidebar 505 . . . for
`
`displaying iconized tickets.” (Ex. 1005, ¶[0191], FIG. 5.) As shown in FIG. 5, the
`
`sidebar 505 is bar-shaped, consistent with the “dynamic bar” described in the ’868
`
`patent. (See, e.g., Ex. 1001, 7:12-20 (“dynamic bar 304 may lie . . . vertically”),
`
`FIGS. 3, 5.)
`
`The sidebar is dynamic because it “automatically provid[es] dynamic
`
`communication access and information awareness” on the display. (Ex. 1005,
`
`¶[0016]; see also id., ¶¶[0017], [0059], [0063], [0076], [0084], [0103], [0115],
`
`13
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`[0167], [0170]-[0172], [0182]-[0185], [0197]-[0198], [0201], [0203]; Ex. 1002,
`
`¶44.) For example, according to Cadiz, “specified communications contacts and
`
`informational elements are dynamically tracked or received and provided to a user
`
`on an ongoing basis.” (Ex. 1005, ¶[0063].)
`
`Cadiz provides examples of how the interface of FIG. 5 can be implemented.
`
`(Ex. 1002, ¶45.) One example is a person-centric interface, as described in
`
`connection with, e.g., FIGS. 6B and 8A-C. Another example is an email-centric
`
`interface, as described in connection with, e.g., FIG. 10. Both of these example
`
`interfaces can be shown in the same sidebar, as illustrated in these Figures. (Ex.
`
`1005, FIGS. 6B, 8A-C, 10; Ex. 1002, ¶45.) Each of these example interfaces
`
`independently discloses the features of limitation 1.b, as discussed in turn below.
`
`PERSON-CENTRIC INTERFACE
`
`FIGS. 6B and 8A-C illustrate a person-centric interface for interacting with
`
`communications contacts. For example, FIGS. 6B and 8A each illustrate a
`
`“sidebar” (or “container”) that provides a “peripheral awareness interface”
`
`containing multiple person items (i.e., person items 610, 615, and 620 of FIG. 6B
`
`and person items 810, 815, and 820 of FIG. 8A).5 (Ex. 1005, ¶¶[0197], [0201],
`
`
`
` 5
`
` An “item,” which is also referred to as “dynamic thumbnail[],” is “a combination
`
`of a ‘ticket’ describing the information or contact of interest and a specialized
`
`14
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`FIGS. 6B, 8A.) The primary difference between the interfaces shown in FIGS. 6B
`
`and 8A is that FIG. 8A also displays “pawns” 805 associated with the person
`
`items. (Id., ¶[0201].) As shown in FIGS. 6B and 8A, the sidebars are bar-shaped.
`
`(Ex. 1002, ¶46.)
`
`The sidebars are also dynamic. (Id., ¶47.) For example, Cadiz explains that
`
`the sidebar “automatically provides peripheral awareness of information of interest
`
`to a user,” and that, “[i]n order to facilitate peripheral awareness of the
`
`communications availability or status, the ticket thumbnails for communicating
`
`with people use images or pictures of faces to represent the people embodied by
`
`the ticket.” (Ex. 1005, ¶¶[0196]-[0197], FIGS. 6B, 8A; see also id., ¶¶[0019],
`
`[0061], [0182].) Cadiz explains that “the image or picture of a face for a particular
`
`person automatically changes as the communications availability or status
`
`changes,” e.g., the sidebar dynamically displays “a frontal close-up when the
`
`
`
`‘viewer’ for displaying whatever information or communications contact is
`
`represented by the ticket.” (Ex. 1005, ¶[0017]; see also id., ¶¶[0065], [0077],
`
`[0089].) FIG. 8A illustrates person tickets/items and FIG. 10 illustrates an email
`
`ticket/item. (Ex. 1005, ¶¶[0201], [0203], FIGS. 8A, 10; see also id., ¶¶[0025],
`
`[0069], [0072], [0079], [0090], [0170]-[0172], [0174], [0182], [0197], FIGS. 4B,
`
`6A-6B; Ex. 1002, ¶46.)
`
`15
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`person is available, and a profile when the person is busy.” (Id., ¶¶[0197]-[0198],
`
`FIGS. 6B, 8A; see also id., ¶¶[0062], [0182].) Because the person items, like those
`
`shown in FIGS. 6B and 8A, automatically change in accordance with availability
`
`or status changes, the sidebars in FIGS. 6B and 8A are dynamic. (Ex. 1002, ¶47.)
`
`The sidebar shown in FIG. 8A is also dynamic because it includes pawns
`
`805, which “serve[] as an additional indicator of communications status or
`
`availability where a non-standard or ambiguous image is used for representing a
`
`particular contact.” (Ex. 1005, ¶[0201]; Ex. 1002, ¶48.)
`
`EMAIL-CENTRIC INTERFACE
`
`FIG. 10 illustrates an email-centric interface and “represents an email type
`
`ticket/item 1010 within another container/sidebar 1000.” (Ex. 1005, ¶[0203].) As
`
`shown in FIG. 10, the sidebar 1000 is bar-shaped. (Ex. 1002, ¶49.)
`
`
`
`The sidebar 1000 is also dynamic. (Ex. 1002, ¶50.) For example, Cadiz
`
`describes an interface that includes “an email ticket for watching an email inbox
`
`folder” and that “a summary of the number of messages received in the folder is
`
`preferably displayed in the thumbnail.” (Ex. 1005, ¶[0072]; see also id., ¶[0059]
`
`(explaining that the “peripheral awareness interface provides a user with
`
`dynamically updated status,” such as “email status”), [0064] (“email status”),
`
`[0067] (“monitoring an email folder”), [0025] (explaining that a viewer/ticket “is
`
`capable of displaying specific email information, such as, for example, number of
`
`16
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`messages”), [0069] (same), [0090] (same), [0178] (explaining that “displayed
`
`tickets” can include “items for monitoring an email inbox”).) Displaying the
`
`number of messages received in a monitored email inbox folder—e.g., 5 new
`
`messages, as shown in FIG. 10—is an example of displaying dynamically
`
`changing information.6 (Ex. 1002, ¶50.)
`
`c)
`
`“displaying dynamic preview information in the dynamic
`bar, the dynamic preview information being determined
`from information managed by a software application, the
`dynamic preview information being updated to reflect a
`change to the information managed by the software
`application;”
`
`Cadiz discloses these features, for example, with respect to both the person-
`
`centric interface and the email-centric interface, which are addressed in turn below.
`
`(Ex. 1002, ¶¶51-63.)
`
`PERSON-CENTRIC INTERFACE
`
`“displaying dynamic preview information in the dynamic bar”
`
`Regarding the person-centric interface, Cadiz discloses displaying dynamic
`
`preview information in the dynamic bar for the same reasons Cadiz discloses
`
`
` In FIG. 10, based on the display of “5 new messages, 389 Tota[l]” in email
`
` 6
`
`window 1020, a POSA would have understood that “5/3” in item 1010, although
`
`partially cut off on the right side, signifies 5 new messages and 389 total messages
`
`in the “UserFeedback” folder. (Ex. 1002, ¶50.)
`
`17
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`“displaying a dynamic bar on the display,” as discussed above with respect to
`
`claim element 1.b. (See supra Part IX.A.1.b; Ex. 1002, ¶52.) For example, as
`
`discussed above, the sidebar of FIG. 8A (“dynamic bar”) displays dynamic
`
`preview information because “the image or picture of a face for a particular person
`
`automatically changes as the communications availability or status changes.” (See,
`
`e.g., Ex. 1005, ¶¶[0197]-[0198], FIGS. 6B, 8A; Ex. 1002, ¶52.) Similarly, the
`
`displayed pawns 805 also automatically change to reflect communications
`
`availability or status changes. (Ex. 1005, ¶[0201]; Ex. 1002, ¶52.) Such
`
`information is a preview because it displays a visual representation of a person’s
`
`communications availability or status instead of the more detailed communications
`
`information displayed when the user accesses an enhanced tooltip person window
`
`or activates a communications software application, as discussed directly below
`
`and with respect to claim elements 1.d-g. (See infra Parts IX.A.1.d-g; Ex. 1002,
`
`¶52.)
`
`“the dynamic preview information being determined from information
`managed by a software application, the dynamic preview information
`being updated to reflect a change to the information managed by the
`software application”
`Cadiz discloses that the information displayed in the sidebar of FIGS. 8A
`
`(“dynamic preview information”) is determined from information managed by a
`
`software application. (Ex. 1002, ¶53.) For example, Cadiz describes the
`
`management of such dynamic preview information in the context of FIG. 2
`
`18
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`(annotated below), which illustrates an architectural diagram including services
`
`230 (annotated in red) as an interface between items 200 (e.g., person items 810,
`
`815, and 820 displayed in the sidebar of FIG. 8A) and information sources 240.
`
`(Ex. 1005, ¶¶[0074]-[0076], FIG. 2; see also id., ¶¶[0021], [0066], [0084]-[0088],
`
`[0115], [0167], [0171].)
`
`
`
`That is, each item includes “pointers to particular ‘services’ that represent
`
`any of a number of conventional means for interacting with the information or
`
`communications contacts,” wherein the “services represent shared code or
`
`functions that provide functionality for accessing, receiving, retrieving, and/or
`
`otherwise interacting with any conventional information, source of information, or
`
`19
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`communications contact.” (Ex. 1005, ¶[0021]; see also id., ¶¶[0066], [0085], FIGS.
`
`2-4.) Cadiz further explains that “[c]urrent information or status is automatically
`
`either retrieved or received, i.e., either by ‘pulling’ or ‘pushing’ such information,
`
`from any one or more of a number of conventional [information] sources 240 by
`
`using the functionality associated with one or more services 230.” (Id., ¶[0084].)
`
`Accordingly, the availability or status information in the sidebar of FIG. 8A
`
`(“dynamic preview information”) is managed by services 230. (Ex. 1002, ¶54.)
`
`Cadiz explains that services 230 include software applications. (Id., ¶55.)
`
`For instance, Cadiz explains that an example of a “service” is “functionality for
`
`communicating with contacts or transferring information via any number of
`
`conventional methods, such as, for example instant messaging or peer-to-peer
`
`communications schemes” (Ex. 1005, ¶¶[0022], [0067], [0086]), and identifies
`
`software applications as examples of such conventional methods and schemes. (See
`
`also id., ¶¶[0084], [0183], [0194], [0201], 8A, 8B.) For example, Cadiz explains
`
`that “applications [are] provided by these schemes.” (Id., ¶[0006] (emphasis
`
`added); see also id., ¶¶[0009]-[0010], [0058]-[0059].) Cadiz also explains that
`
`“[i]nformation about a person’s availability or state can be obtained from any
`
`conventional system such as, for example, MSN® Messenger®,” which was a
`
`well-known instant messaging software application developed by Microsoft. (Id.,
`
`¶[0185] (emphasis added); see also id., ¶[0087]; Ex. 1002, ¶55.)
`
`20
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,402,384
`Moreover, referring to FIG. 3, Cadiz explains that items (e.g., person items
`
`810, 815, and 820) are created and updated in connection with a software
`
`application. (Ex. 1002, ¶56.) For example, Cadiz explains that “information or
`
`contacts of interest to a particular user are identified either automatically by one or
`
`more computer program applications in response to user interaction with such
`
`application programs, or by the user via a user interface module 310,” and then
`
`“tickets representing the information or contacts of interest are created or modified
`
`via a ticket manager module 320.” (Ex. 1005, ¶¶[0101]-[0102] (emphasis added);
`
`see also id., ¶¶[0182], [0197], [0201].) Once the tickets are created, “the sys