throbber
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,713,466
`
`____________________
`
`
`
`
`
`PETITION FOR INTER PARTES REVIEW
`OF U.S. PATENT NO. 8,713,466
`
`
`
`
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`
`TABLE OF CONTENTS
`
`INTRODUCTION ........................................................................................... 1 
`
`
`I. 
`
`II.  MANDATORY NOTICES UNDER 37 C.F.R. § 42.8 ................................... 1 
`
`III.  PAYMENT OF FEES ..................................................................................... 1 
`
`IV.  GROUNDS FOR STANDING ........................................................................ 2 
`
`V. 
`
`PRECISE RELIEF REQUESTED AND GROUNDS RAISED ..................... 2 
`
`VI.  LEVEL OF ORDINARY SKILL IN THE ART ............................................. 3 
`
`VII.  CLAIM CONSTRUCTION ............................................................................ 4 
`
`VIII.  DETAILED EXPLANATION OF GROUNDS .............................................. 4 
`A.  Ground 1: Cadiz Renders Obvious Claims 1, 4, 6, 12-14, 17, 22, and
`24 ........................................................................................................... 4 
`
`1. 
`
`2. 
`
`3. 
`
`4. 
`
`5. 
`
`6. 
`
`7. 
`
`8. 
`
`Claim 1 ........................................................................................ 4 
`
`Claim 4 ...................................................................................... 31 
`
`Claim 6 ...................................................................................... 32 
`
`Claim 12 .................................................................................... 33 
`
`Claim 13 .................................................................................... 35 
`
`Claim 14 .................................................................................... 37 
`
`Claim 17 .................................................................................... 40 
`
`Claim 22 .................................................................................... 40 
`
`Claim 24 .................................................................................... 43 
`9. 
`B.  Ground 2: Cadiz and Hawkins Render Obvious Claims 2, 3, 15, and
`23 ......................................................................................................... 43 
`
`1. 
`
`Claim 2 ...................................................................................... 43 
`
`
`
`i
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`Claim 3 ...................................................................................... 47 
`
`Claim 15 .................................................................................... 48 
`
`2. 
`
`3. 
`
`Claim 23 .................................................................................... 49 
`4. 
`C.  Ground 3: Cadiz and Siedlikowski Render Obvious Claims 7-9, 18,
`19, and 25 ............................................................................................ 50 
`
`1. 
`
`2. 
`
`3. 
`
`4. 
`
`5. 
`
`Claim 7 ...................................................................................... 50 
`
`Claim 8 ...................................................................................... 53 
`
`Claim 9 ...................................................................................... 54 
`
`Claim 18 .................................................................................... 56 
`
`Claim 19 .................................................................................... 57 
`
`Claim 25 .................................................................................... 57 
`6. 
`D.  Ground 4: Cadiz and Yamadera Render Obvious Claims 5, 10, 11, 16,
`20, 21, and 26 ...................................................................................... 58 
`
`1. 
`
`2. 
`
`3. 
`
`4. 
`
`5. 
`
`6. 
`
`7. 
`
`Claim 5 ...................................................................................... 58 
`
`Claim 10 .................................................................................... 61 
`
`Claim 11 .................................................................................... 66 
`
`Claim 16 .................................................................................... 67 
`
`Claim 20 .................................................................................... 68 
`
`Claim 21 .................................................................................... 68 
`
`Claim 26 .................................................................................... 69 
`
`IX.  CONCLUSION .............................................................................................. 70 
`
`
`
`
`
`
`
`
`
`ii
`
`

`

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

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`LIST OF EXHIBITS
`
`U.S. Patent No. 8,713,466
`
`Declaration of Dr. Dan R. Olsen Jr.
`
`Curriculum Vitae of Dr. Dan R. Olsen Jr.
`
`Prosecution History of U.S. Patent No. 8,713,466
`
`Prosecution History of U.S. Patent No. 8,402,384
`
`U.S. Patent Application Publication No. 2002/0186257
`(“Cadiz”)
`U.S. Patent No. 7,007,239 (“Hawkins”)
`U.S. Patent No. 6,741,232 (“Siedlikowski”)
`U.S. Patent Publication No. 2002/0123368 (“Yamadera”)
`U.S. Patent No. 7,454,714 (“Totman”)
`European Patent Application No. EP1265157 (“Cadiz-EP”)
`Caroline Rose et al., “Inside Macintosh Volume 1” (1985)
`“Macintosh Human Interface Guidelines,” Apple Computer,
`Inc. (1995)
`
`Prosecution History of European Patent Application No.
`06125884.4
`
`
`
`iv
`
`1001
`
`1002
`
`1003
`
`1004
`
`1005
`
`1006
`
`1007
`
`1008
`
`1009
`
`1010
`
`1011
`
`1012
`
`1013
`
`1014
`
`
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`
`I.
`
`INTRODUCTION
`Google Inc. (“Petitioner”) requests inter partes review (“IPR”) and
`
`cancellation of claims 1-26 (“the challenged claims”) of U.S. Patent No. 8,713,466
`
`(“the ’466 patent”) (Ex.1001), which is purportedly assigned to BlackBerry
`
`Limited (“Patent Owner” or “PO”).
`
`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 ’466 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 parent U.S. Patent No. 8,402,384.
`
`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.
`
`III. PAYMENT OF FEES
`
`The required fees are submitted herewith. The PTO is authorized to charge
`
`
`
`1
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`any additional fees due during this proceeding to Deposit Account No. 50-2613.
`
`IV. GROUNDS FOR STANDING
`
`Petitioner certifies that the ’466 patent is available for IPR and Petitioner is
`
`not barred or estopped from requesting this IPR.
`
`V.
`
`PRECISE RELIEF REQUESTED AND GROUNDS RAISED
`
`Claims 1-26 of the ’466 patent should be canceled as obvious on the
`
`following grounds and prior art:
`
`Ground 1: Claims 1, 4, 6, 12-14, 17, 22, and 24 are obvious under 35
`
`U.S.C. § 103(a) in view of U.S. Patent Publication No. 2002/0186257 (“Cadiz”)
`
`(Ex.1006);
`
`Ground 2: Claims 2, 3, 15, and 23 are obvious under § 103(a) in view of
`
`Cadiz and U.S. Patent No. 7,007,239 (“Hawkins”) (Ex.1007);
`
`Ground 3: Claims 7-9, 18, 19, and 25 are obvious under § 103(a) in view of
`
`Cadiz and U.S. Patent No. 6,741,232 (“Siedlikowski”) (Ex.1008); and
`
`Ground 4: Claims 5, 10, 11, 16, 20, 21, and 26 are obvious under § 103(a)
`
`in view of Cadiz and U.S. Patent Publication No. 2002/0123368 (“Yamadera”)
`
`(Ex.1009).
`
`The ’466 patent is a continuation of U.S. Patent No. 8,402,384 (“the ’384
`
`patent”), which was filed on November 9, 2004. For purposes of this proceeding,
`
`Petitioner assumes the earliest effective filing date of the ’466 patent is no earlier
`
`
`
`2
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`than the November 9, 2004 filing date of the ’384 patent. Cadiz was published on
`
`December 12, 2002. Yamadera was published on September 5, 2002. Therefore,
`
`Cadiz and Yamadera are prior art at least under pre-AIA 35 U.S.C. § 102(b).
`
`Hawkins was filed on October 14, 2001. Siedlikowski was filed on January
`
`23, 2002. Therefore, Hawkins and Siedlikowski are prior art at least under pre-AIA
`
`35 U.S.C. § 102(e).
`
`Hawkins, Siedlikowski, and Yamadera were not considered during
`
`prosecution. A counterpart of Cadiz, EP1265157 (“Cadiz-EP”) (Ex.1011), is listed
`
`on the face of the ’384 patent, but 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 ’466 patent, the
`
`applicant was unable to overcome rejections based on Cadiz-EP. (Ex.1014, 22-25,
`
`160, 161, 165-66.)
`
`VI. LEVEL OF ORDINARY SKILL IN THE ART
`
`A person of ordinary skill in the art (POSA) at the time of the alleged
`
`invention of the ’466 patent would have had an undergraduate degree in computer
`
`science, electrical engineering, or equivalent thereof, and at least two years of
`
`experience in the relevant field, e.g., graphical user interfaces. (Ex.1002, ¶¶13-14.)
`
`More education can supplement practical experience and vice versa.1
`
`1 Petitioner submits the supporting declaration of Dr. Dan R. Olsen Jr. (Ex.1002,
`
`
`
`3
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`
`VII. CLAIM CONSTRUCTION
`
`Because the ’466 patent will not expire before issuance of a final written
`
`decision, for purposes of this proceeding, the claims of the ’466 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.2
`
`VIII. DETAILED EXPLANATION OF GROUNDS3
`A. Ground 1: Cadiz Renders Obvious Claims 1, 4, 6, 12-14, 17, 22,
`and 24
`1.
`Claim 1
`a)
`“A method for displaying preview information, the
`method comprising:”
`To the extent the preamble is limiting, Cadiz discloses the limitations
`
`¶¶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.
`
`2 Any claim interpretations submitted or implied herein for the purpose of this
`
`proceeding are not binding upon Petitioner in any litigation involving the ’466
`
`patent. Moreover, Petitioner does not concede that the challenged claims are not
`
`invalid for reasons not raised herein.
`
`3 An overview of the technical background, the ’466 patent, and the prior art is
`
`provided by Dr. Olsen. (Ex.1002, ¶¶15-23, 25-36.)
`
`
`
`4
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`therein. (Ex.1002, ¶¶25-31, 38-41.) For example, Cadiz discloses that “the
`
`invention includes a computing device” 100 (Ex.1006, ¶[0050]), which includes an
`
`output device 116, “such as a display” (id., ¶[0054], FIG. 1). (Ex.1002, ¶¶38-39.)
`
`Additionally, Cadiz describes “implementing
`
`the peripheral awareness
`
`interface…on any conventional display device 260.” (Ex.1006, ¶[0074], FIG. 2;
`
`Ex.1002, ¶39.)
`
`
`
`Cadiz discloses displaying a GUI on the display, e.g., as shown in FIGS. 8A-
`
`8C and 10. (Ex.1002, ¶40.) The GUIs include “preview information,” such as
`
`information about the availability of a person in FIG. 8A and about received emails
`
`in FIG. 10. (See Parts VIII.A.1.b, VIII.A.1.d; Ex.1002, ¶41.) Accordingly, Cadiz
`
`discloses a method for displaying preview information. (Ex.1002, ¶41; see also
`
`analysis below for the remaining elements of claim 1.)
`
`b)
`
`“displaying on a display dynamic preview information in
`a 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; and”
`Cadiz discloses these features. (Ex.1002, ¶¶42-62.) As discussed above in
`
`Part VIII.A.1.a, Cadiz discloses a display. (Ex.1006, ¶¶[0050], [0054], [0074],
`
`FIGS. 1-2.) Cadiz describes displaying a “sidebar” (“dynamic bar”) on the display,
`
`which “host[s] one or more columns of items in a persistent interactive display
`
`strip along one edge of a conventional display device.” (Ex.1006, ¶[0070]; see also
`5
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`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 shows an “exemplary user interface” with “at least one
`
`sidebar 505…for displaying iconized tickets.” (Ex.1006, ¶[0191], FIG. 5.) The
`
`sidebar is bar-shaped, consistent with the “dynamic bar” described in the ’466
`
`patent. (See, e.g., Ex.1001, 7:17-19 (“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.1006,
`
`¶[0016]; see also id., ¶¶[0017], [0059], [0063], [0076], [0084], [0103], [0115],
`
`[0167], [0170]-[0172], [0182]-[0185], [0197]-[0198], [0201], [0203]; Ex.1002,
`
`¶44.) For example, “specified communications contacts and informational
`
`elements are dynamically tracked or received and provided to a user on an ongoing
`
`basis.” (Ex.1006, ¶[0063].)
`
`Cadiz provides examples of how the interface of FIG. 5 can be implemented
`
`to display preview information in the sidebar (“dynamic bar”). (Ex.1002, ¶45.) One
`
`example is a person-centric interface, as described with, e.g., FIGS. 6B and 8A-C.
`
`Another example is an email-centric interface, as described with, e.g., FIG. 10.
`
`Both exemplary interfaces can be shown in the same sidebar. (Ex.1006, FIGS. 6B,
`
`8A-C, 10; Ex.1002, ¶45.) Each of these example interfaces independently discloses
`
`
`
`6
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`
`the features of limitation 1.b.
`
`PERSON-CENTRIC INTERFACE
`
`“displaying on a display dynamic preview information in a dynamic
`bar”
`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” that provides a “peripheral awareness interface” containing multiple
`
`person items (i.e., items 610, 615, and 620 of FIG. 6B; items 810, 815, and 820 of
`
`FIG. 8A).4 (Ex.1006, ¶¶[0197], [0201], 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 and display dynamic preview information.
`
`(Id., ¶47.) For example, the sidebar “automatically provides peripheral awareness
`
`
`4 An “item” (or “dynamic thumbnail[]”) is “a combination of a ‘ticket’ describing
`
`the information or contact of interest and a specialized ‘viewer’ for displaying...the
`
`ticket.” (Ex.1006, ¶[0017]; see also id., ¶¶[0065], [0077], [0089].) FIG. 8A
`
`illustrates person tickets/items and FIG. 10 illustrates an email ticket/item.
`
`(Ex.1006, ¶¶[0201], [0203], FIGS. 8A, 10; see also id., ¶¶[0025], [0069], [0072],
`
`[0079], [0090], [0170]-[0172], [0174], [0182], [0197], FIGS. 4B, 6A-6B.)
`
`
`
`7
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`of information of interest to a user” using “images or pictures of faces to represent
`
`the people embodied by the ticket.” (Ex.1006, ¶¶[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 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
`
`and display dynamic preview information. (Ex.1002, ¶47.)
`
`The sidebar shown in FIG. 8A is also dynamic and displays dynamic
`
`preview information because it further includes pawns 805, which “serve[] as an
`
`additional indicator of communications status or availability.” (Ex.1006, ¶[0201];
`
`Ex.1002, ¶48.)
`
`Such information is dynamic preview information because it includes a
`
`dynamically updated visual representation of a person’s communications
`
`availability or status instead of the more detailed communications information
`
`displayed when the user accesses a person window or activates a communications
`
`software application, as discussed directly below and with respect to claim
`
`elements 1.c-e. (See Parts VIII.A.1.c-e; Ex.1002, ¶49.)
`
`
`
`8
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`“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 FIG. 8A
`
`(“dynamic preview information”) is determined from information managed by a
`
`software application. (Ex.1002, ¶50.) For example, Cadiz describes
`
`the
`
`management of such dynamic preview information in the context of FIG. 2
`
`(annotated below), which shows services 230 (annotated in red) as an interface
`
`between items 200 (e.g., item 815 of FIG. 8A) and information sources 240.
`
`(Ex.1006, ¶¶[0074]-[0076], FIG. 2; see also id., ¶¶[0021], [0066], [0084]-[0088],
`
`[0115], [0167], [0171].)
`
`
`
`
`
`9
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`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
`
`communications contact.” (Ex.1006, ¶[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 is
`
`managed by services 230. (Ex.1002, ¶51.)
`
`Cadiz explains that services 230 include software applications. (Id., ¶52.)
`
`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.1006, ¶¶[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
`
`
`
`10
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`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, ¶52.)
`
`Moreover, referring to FIG. 3, Cadiz explains that items (e.g., person item
`
`815) are created and updated in connection with a software application. (Ex.1002,
`
`¶53.) For example, Cadiz explains that “information or contacts of interest…are
`
`identified either automatically by one or more computer program applications in
`
`response to user interaction with such application programs,” and then “tickets
`
`representing the information or contacts of interest are created or modified via a
`
`ticket manager module 320.” (Ex.1006, ¶¶[0101]-[0102] (emphasis added); see
`
`also id., ¶¶[0182], [0197], [0201].) Once the tickets are created, “the present
`
`invention then automatically tracks or receives the current state of the items 200
`
`via an information and communication module 330 which, in essence, uses one or
`
`more of the previously described services for accessing and/or interacting with
`
`one or more information sources.” (Id., ¶[0103] (emphasis added).) As discussed
`
`above, such services include software applications (e.g., MSN® Messenger®).
`
`(Ex.1002, ¶53.)
`
`Accordingly, Cadiz discloses that the communications availability or status
`
`
`
`11
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`information displayed in FIG. 8A (“dynamic preview information”) is managed by
`
`a software application (e.g., MSN® Messenger®). (Id., ¶54.)
`
`Furthermore, as discussed above, Cadiz discloses, for example, “provid[ing]
`
`the user with dynamically updated status,” that preview information automatically
`
`changes as status changes, and that this automatically changed information is
`
`managed by the software application, as discussed above. (Ex.1006, ¶¶ [0059],
`
`[0201]). Therefore, Cadiz discloses that the dynamic preview information is
`
`updated to reflect a change to the information managed by the software
`
`application. (Ex.1002, ¶55.) Indeed, a POSA would have recognized that, if the
`
`dynamic preview information was not updated in such a way, the user would not
`
`have been informed of status changes. (Id.)
`
`EMAIL-CENTRIC INTERFACE
`
`“displaying on a display dynamic preview information in a dynamic
`bar”
`FIG. 10 illustrates an email-centric interface and “represents an email type
`
`ticket/item 1010 within another container/sidebar 1000.” (Ex.1006, ¶[0203].) As
`
`shown in FIG. 10, the sidebar 1000 is bar-shaped. (Ex.1002, ¶56.)
`
`The sidebar 1000
`
`is also dynamic and displays dynamic preview
`
`information, as discussed above. (Ex.1002, ¶57.) 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
`12
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`thumbnail.” (Ex.1006, ¶[0072]; see also
`id., ¶[0059]
`
`displayed
`
`in
`
`the
`
`(“dynamically updated status,” such as “email status”), [0064] (“email status”),
`
`[0067] (“monitoring an email folder”), [0025] (“number of messages”), [0069]
`
`(same), [0090] (same), [0178] (“monitoring an email inbox”).) Displaying the
`
`number of messages received in a monitored email folder—e.g., 5 new messages—
`
`is an example of displaying dynamically changing information.5 (Ex.1002, ¶57.)
`
`Such information is dynamic preview information because it dynamically
`
`displays the number of received messages instead of the more detailed message
`
`information displayed when the user accesses an email window or activates an
`
`email software application, as discussed directly below and with respect to claim
`
`elements 1.c-e. (See Parts VIII.A.1.c-e; Ex.1002, ¶58.) Indeed, displaying the
`
`number of messages received, as shown in email item 1010 of FIG. 10, is similar
`
`to how the ’466 patent describes displaying “dynamic preview information” with
`
`respect to FIG. 5 (“counts of new events 502”). (See Ex.1001, 7:51-67, FIG. 5;
`
`Ex.1002, ¶¶58-59.)
`
`
`
`5 In FIG. 10, based on the display of “5 new messages, 389 Tota[l]” in email
`
`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, ¶57.)
`
`
`
`13
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`“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 explains that the information displayed in the sidebar of FIG. 10
`
`(“dynamic preview information”) is determined from information managed by a
`
`software application, for reasons similar to those discussed above for the person-
`
`centric interface. (Ex.1002, ¶60.) For example, as discussed above, Cadiz explains
`
`that each item (e.g., email ticket/item 1010) includes “pointers to particular
`
`‘services’ that represent any of a number of conventional means for interacting
`
`with the information or communications contacts,” and that example “services” are
`
`“functionality necessary for monitoring an email folder” and “sending or receiving
`
`email messages.” (Ex.1006, ¶¶[0021], [0022], [0067], [0086]; see also id.,
`
`¶¶[0019], [0059], [0064], [0069], [0071]-[0072], [0084], [0088], [0090], [0178],
`
`[0183]-[0184], [0187], [0194], [0203].) Such functions were known to be provided
`
`by email applications, such as Microsoft Outlook, a known software application
`
`used with Microsoft Windows, to which Cadiz is related. (Ex.1002, ¶60.)
`
`In fact, with respect to FIG. 10, Cadiz identifies an email application as a
`
`service that provides such functionalities. (Id., ¶61.) For example, by selecting an
`
`email item, “the user may interact with any message in this window in the same
`
`manner as if the messages with being accessed or viewed within the users’ email
`
`application.” (Ex.1006, ¶[0072] (emphasis added); see also id., ¶[0203].)
`14
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`Alternatively, selecting an email item “provid[es] a viewer that instantiates an
`
`instance of the user[’]s email program for purposes of displaying the
`
`tracked/watched inbox folder.” (Id., ¶[0072] (emphasis added).)
`
`Additionally, for reasons similar to those discussed above for the person-
`
`centric interface, Cadiz explains that email tickets/items are automatically created
`
`and updated in connection with a user’s interaction with a software application.
`
`(Ex.1006, ¶¶[0101]-[0103]; Ex.1002, ¶62.)
`
`c)
`
`“expanding the dynamic bar to display an expanded
`dynamic bar in response to a first input, displaying the
`expanded dynamic bar comprising:”
`Cadiz discloses these features, for example, with respect to both the person-
`
`centric interface and the email-centric interface. (Ex.1002, ¶¶63-69.) For instance,
`
`interaction with items in a sidebar “call[s] up actionable expanded information or
`
`contact windows, namely ‘enhanced tooltip windows,’ that provide further
`
`levels of detail beyond that provided by the iconized ticket thumbnail.”
`
`(Ex.1006, ¶¶[0105]-[0106] (emphasis added); see also id., ¶¶[0072], [0099],
`
`[0170], [0183]-[0184], [0186], [0193]-[0194], [0201]-[0203], FIGS. 2, 5, 8B, 10.)
`
`FIG. 5 of Cadiz illustrates examples of such windows displayed in response to an
`
`interaction with an item, including “person window” 565 and “enhanced tooltips”
`
`555. (Id., ¶¶[0193]-[0194], FIG. 5; Ex.1002, ¶63.) The person-centric interface of
`
`FIG. 8B provides an example of a person window (Ex.1006, ¶[0201]), and the
`
`
`
`15
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`email-centric interface of FIG. 10 provides an example of an enhanced tooltip (id.,
`
`¶[0203]), each of which discloses an expanded dynamic bar, as discussed in more
`
`detail below.6 (Ex.1002, ¶63.)
`
`PERSON-CENTRIC INTERFACE
`
`Cadiz explains that FIG. 8B illustrates “a dynamic person window or
`
`‘enhanced tooltip’ person window 825 accessed by selection of one of the person
`
`items 815 of FIG. 8A.” (Ex.1006, ¶[0201] (emphasis added); see also id.,
`
`¶¶[0170], [0183]-[0186], [0194].) Cadiz discloses that the selection of the person
`
`ticket/item 820 of FIG. 8A is from an input device, such as a “mouse.” (Ex.1006,
`
`¶[0050]; see also id., ¶¶[0054], [0071], [0170], [0183], [0201]; Ex.1002, ¶64.)
`
`The person window 825 is bar-shaped, as shown in FIG. 8B, consistent with
`
`the discussion of an expanded dynamic bar in the ’466 patent. (Ex.1001, 7:40-42
`
`(“Dynamic bar 304 is expanded via a…pop-up interface 407”), 8:1-7, FIGS. 4, 6;
`
`Ex.1002, ¶65.) The person window 825 also provides additional dynamic preview
`
`information beyond that displayed in the person ticket/item 825, as discussed in
`
`more detail below with respect to claim element 1.d. (See Part VIII.A.1.d; Ex.1002,
`
`6 These examples are similar to the examples of an “expanded dynamic bar”
`
`disclosed in the ’466 patent, which identifies a “pop-up interface” as an example of
`
`displaying an “expanded dynamic bar.” (Ex.1001, 7:32-34, FIGS. 4, 6; Ex.1002,
`
`¶63.)
`
`
`
`16
`
`

`

`¶65.)
`
`Petition for Inter Partes Review
`Patent No. 8,713,466
`
`
`Accordingly, Cadiz discloses expanding the person item 820 (“dynamic
`
`bar”) to display the person window 825 (“expanded dynamic bar”) in response to a
`
`selection of the person item 820 (“first input”). (Ex.1002, ¶66.)
`
`EMAIL-CENTRIC INTERFACE
`
`Referring to FIG. 10, Cadiz explains 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.” (Ex.1006, ¶[0203] (emphasis added); see also id., ¶¶[0071]-[0072].)
`
`As discussed above for the person-centric interface, Cadiz discloses an input
`
`device for selecting items, such as email item 1010 of FIG. 10. (See Ex.1006,
`
`¶¶[0050], [0054], [0071], [0170], [0183], [0201]; Ex.1002, ¶67)
`
`The email window 1020 is bar-shaped, as shown in FIG. 10, consistent with
`
`the discussion of an expanded dynamic bar in the ’466 patent. (Ex.1001, 7:40-42,
`
`8:1-7, FIGS. 4, 6; Ex.1002, ¶68.) The email window 1020 also provides additional
`17
`
`
`
`

`

`Petition for Inter Partes Review
`Patent No. 8,713,466
`dynamic preview information beyond that displayed in the email item 1010, as
`
`discussed in more detail below with respect to claim element 1.d. (See Part
`
`VIII.A.1.d; Ex.1002, ¶68.)
`
`Accordingly, Cadiz discloses expanding the email item 1010 (“dynamic
`
`bar”) to display the email window 1020 (“expanded dynamic bar”) in response to a
`
`selection of the email item 1010 (“first input”). (Ex.1002, ¶69.)
`
`d)
`
`“displaying additional dynamic preview information
`determined from
`the
`information managed by
`the
`software application, the additional dynamic preview
`information being different from the dynamic preview
`information displayed in the dynamic bar;”
`Cadiz discloses these features for reasons similar to those discussed above
`
`for claim element 1.b and for the additional reasons discussed below, for example,
`
`with respect to both the person-centric interface and the email-centric interface.
`
`(Ex.1002, ¶¶70-78.)
`
`PERSON-CENTRIC INTERFACE
`
`Cadiz’s person window 825 of FIG. 8B (“expanded dynamic bar”) displays
`
`additional dynamic preview information that is different from the dynamic preview
`
`information displayed in the sidebar of FIG. 8A (“dynamic b

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