(12) United States Patent
`Hammond
`
`111111
`
`1111111111111111111111111111111111111111111111111111111111111
`US006854007B 1
`
`(10) Patent No.:
`(45) Date of Patent:
`
`US 6,854,007 Bl
`Feb.8,2005
`
`(54) METHOD AND SYSTEM FOR ENHANCING
`RELIABILITY OF COMMUNICATION WITH
`ELECTRONIC MESSAGES
`
`(75)
`
`Inventor: Nancey J. Hammond, Eagle, ID (US)
`
`(73) Assignee: Micron Technology, Inc., Boise, ID
`(US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21) Appl. No.: 09/153,994
`Sep. 17, 1998
`
`(22) Filed:
`
`(51)
`
`Int. Cl? ................................................ G06F 15/16
`
`(52) U.S. Cl. ........................ 709/206; 709/207; 719/313
`
`(58) Field of Search .......................... 719/313; 709/206,
`709/207, 200, 313, 310, 204
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`4,962,532 A * 10/1990 Kasiraj et a!.
`.............. 713/166
`5,057,935 A * 10/1991 Williams .................... 358/402
`5,325,310 A * 6/1994 Johnson et a!. ............. 709/206
`5,396,537 A * 3/1995 Schwendeman ........... 340/7.23
`5,487,100 A * 1!1996 Kane ......................... 340/7.23
`(List continued on next page.)
`
`JP
`JP
`JP
`
`........... H04L/12/54
`........... H04L/12/54
`........... H04L/12/54
`
`FOREIGN PATENT DOCUMENTS
`04282934 A * 10/1992
`08130554 A * 5/1996
`11252164 A * 9/1999
`01HER PUBLICATIONS
`Fulton, Jennifer et al. "Netscape Navigator 6 in 1". Que
`Corporation. 1996. p. 177-188. *
`Cox, Nancy. "Messaging's next blockbuster hit". Computer
`Select, Apr. 15, 1997.*
`Microsoft. "Messaging Client API". MAPI Version 1.0. Apr.
`15, 1992. *
`
`Drummond, Rik. "Save and secure electronic commerce."
`Computer Select. Dec. 1, 1996.*
`Moore, K. "An Extensible Message Format for Delivery
`Status Notification." RFC 1894. Jan. 1996. *
`Fleming, S.T. "Electronic mail: case study in task-oriented
`restructuring of application domain." IEEE, Mar. 1994. *
`
`(List continued on next page.)
`
`Primary Examiner-Lewis A Bullock, Jr.
`(74) Attorney, Agent, or Firm-Dorsey & Whitney LLP
`
`(57)
`
`ABSTRACT
`
`A system for enhancing the reliability of communicating
`with electronic messages. The system sends an electronic
`message to designated recipients, and then automatically
`helps ensure that each message has been successfully deliv(cid:173)
`ered within a specified period of time and that each message
`has been reviewed within a specified period of time. In
`addition, the system automatically performs specified activi(cid:173)
`ties after review of a message takes place. The sender of an
`electronic message initiates reliability-enhanced messaging
`by specifying message delivery information and message
`review information. The sender can specify that if delivery
`or review notifications are not received within specified
`periods of time, the message will be resent to the recipient
`or a reminder message will be sent to the recipient or to
`another user. The message information can include various
`frequency and duration options, such as resending a message
`only once or resending it every 2 hours for a week. Message
`information can also specify to resend the message with a
`higher transmission priority or review urgency so that its
`delivery and review is more likely, or could specify to use
`a different recipient system for the recipient (e.g., to a second
`email address if a first address fails, or to a pager if a cellular
`phone is not available). Each recipient of a message can
`have individualized message delivery information. The sys(cid:173)
`tem tracks whether each message has been delivered to each
`recipient, and uses the message delivery information to
`resend the messages whose delivery and review was not
`confirmed.
`
`96 Claims, 7 Drawing Sheets
`
`scrv<>rcomputer,ystem
`
`/100
`
`Apple Inc.
`Exhibit 1006
`Page 001
`
`

`

`US 6,854,007 Bl
`Page 2
`
`U.S. PATENT DOCUMENTS
`5,740,231 A * 4/1998 Cohn et a!. ................. 370/401
`5,742,668 A * 4/1998 Pepe eta!. .................. 455/415
`5,764,899 A * 6/1998 Eggleston et a!.
`.......... 709/203
`5,790,639 A * 8/1998 Ranalli et a!.
`.............. 358/407
`5,793,973 A * 8/1998 Birdwell et a!.
`............ 709/223
`5,819,110 A * 10/1998 Motoyama ................... 710/15
`5,842,195 A * 11/1998 Peters et a!. ................... 707/1
`5,893,099 A * 4/1999 Schreiber eta!. ............. 707/10
`5,923,848 A * 7/1999 Goodhand et a!. .......... 709/219
`5,930,471 A * 7/1999 Milewski et a!.
`........... 709/204
`5,940,823 A * 8/1999 Schreiber eta!. ........... 707/200
`5,978,836 A * 11/1999 Ouchi ........................ 709/203
`6,002,852 A * 12/1999 Birdwell et a!.
`............ 709/203
`6,038,601 A * 3/2000 Lambert et a!.
`............ 709/226
`6,108,688 A * 8/2000 Nielsen ...................... 709/206
`6,108,709 A * 8/2000 Shinomura et a!. ......... 709/228
`6,157,945 A * 12/2000 Balma et a!.
`............... 709/206
`6,175,859 B1 * 1!2001 Mohler ....................... 709/206
`6,185,603 B1 * 2/2001 Henderson et a!.
`......... 709/206
`6,208,996 B1 * 3/2001 Ben-Shachar et a!.
`...... 345/963
`6,272,532 B1 * 8/2001 Feinleib ...................... 709/206
`6,314,454 B1 * 11/2001 Wang eta!. ................ 709/206
`6,327,046 B1 * 12/2001 Miyamoto et a!. ......... 358/1.15
`6,370,567 B1 * 4/2002 Ouchi ........................ 709/206
`6,427,164 B1 * 7/2002 Reilly
`........................ 709/206
`6,453,341 B1 * 9/2002 Miloslavsky ................ 709/206
`6,603,389 B1 * 8/2003 Murray . ... .. ... ... ... ... ... .. 340/7.2
`6,618,747 B1 * 9/2003 Flynn et a!.
`................ 709/206
`2002/0055898 A1 * 5!2002 Burakoff et a!. .............. 705!35
`2002/0144154 A1 * 10/2002 Tomkow ..................... 713/201
`
`01HER PUBLICATIONS
`
`"Conferencing Tools," http://www.cio.com/WebMaster/
`wm_conferencing.html, p. 1 [Accessed Jan. 22, 1998].
`
`"What is HyperNews? ,"http://www.cer.ch/WebOfficialDoc/
`HyperNews/WhatlsHN.html, pp. 1-4 [Accessed Jan. 22,
`1998].
`"The Right Work Environment for Network-Centric Com(cid:173)
`puting,"
`http://esuite.lotus.com/eSuite/eSuite_Site.nsf/
`b9160abf61cf14e38525653b006a4e99/
`2d227cfblf91d8dc85256541002254,p.1 [Accessed Jan. 22,
`1998].
`"Project Cyrus: Overview of Technologies Chosen," http://
`andrew2.andrew.cmu.edu/cyrus/cyrustechoverview.fm.
`html, pp. 1-2 [Accessed Jan. 22, 1998].
`"Multiple-reply
`'SPAR' Service," DataBack Systems,
`http://www2.databack.com/mailback/multispar.htm, pp. 1-2
`[Accessed Jan. 28, 1998].
`"Conferencing Systems," Collaborative Conferencing,
`http://www.hypernews.org/HyperNews/get/www.collab/
`conferencing.html, pp. 1-4 [Accessed Jan. 22, 1998].
`"AutoResponder/ Auto Mailer/ Auto bot Comparisons," http://
`www.makura.com/auto/autocomp.html, pp. 1-18 [Accessed
`Jan. 28, 1998].
`"Lotus cc:Mail Release 8.1," http://www.ccmail.com/over(cid:173)
`view/r81specsheet.htm, pp. 1-3 [Accessed Jan. 22, 1998].
`"Lotus cc:Mail Technical Overview," http://www.ccmail.
`com/overview/overview.htm, pp. 1-43 [Accessed Jan. 22,
`1998].
`"Group Wise 5: Detailed Information," Novell Group Wise 5
`Product Details, http://www.sisnema.com.br/novell/ngw5/
`ngw5.1/informativo/infoing.htm, pp. 1-9 [Accessed Jan. 28,
`1998].
`
`* cited by examiner
`
`Apple Inc.
`Exhibit 1006
`Page 002
`
`

`

`server computer ~ystem
`
`/
`
`100
`
`j_ r ;nputlcmtput dev;,,,, , 120 v t
`
`, _ _ _ _ c_P_l_f _
`
`I.
`
`_ _
`
`130
`_n_1c_n_1o_ry ___ )L____-.
`.'Vlessage Review
`132
`Server
`
`.'Vlessage Sender
`
`134
`II '--------'
`II Message Receiptj 136
`-
`-
`__j
`Tracker
`Message Track me, ( 137 I
`1 ahk hoco,oc J_j
`
`storage device 126
`
`, M~ssage
`.
`frackmg Table
`r---~12 7
`
`1 1
`
`CPU L 151
`I
`~-
`L__
`.
`!52
`
`rnemm
`
`t
`
`. r
`
`~~~~~: j
`
`network
`connection
`
`r
`
`I 22
`
`message
`reviewer L 154
`
`I
`
`l _
`
`____j
`
`computer(cid:173)
`readable
`media driveL 123
`
`I
`display L 124
`
`I
`
`i
`
`I
`
`I
`
`Fig. I
`
`network
`
`JSO \ I 40
`
`158
`
`180
`
`I
`
`d •
`\Jl
`•
`~
`~ ......
`~ = ......
`
`"'!"j
`~
`?'
`~CIO
`
`N c c
`
`Ul
`
`'JJ. =(cid:173)~
`~ .....
`'"""' 0 ......,
`
`-..J
`
`e
`rJ'l
`-..a-..
`00
`(It
`
`~ b
`Q
`""-l
`~
`1--"
`
`Apple Inc.
`Exhibit 1006
`Page 003
`
`

`

`U.S. Patent
`
`Feb.8,2005
`
`Sheet 2 of 7
`
`US 6,854,007 Bl
`
`Message Tracking Table
`
`J 127
`
`Row/
`Col urn
`n
`
`I
`
`2
`
`3
`
`4
`r-----
`
`1
`
`2
`
`3
`
`4
`
`5
`
`6
`
`7
`
`~
`
`Message
`ID
`
`Rccipien
`tlD
`
`Send
`T1me
`
`Delivery
`Time
`
`Review
`Timc
`
`I
`
`I
`
`2
`
`3
`
`ABC
`
`BCD
`
`CDE
`
`ABC
`
`07/26/XX 07/26/XX 07/28/XX
`18:26:33
`10:12:33
`ll'\:.28~15
`07/26/XX 07/27/XX 07/27/XX
`;R:26:33
`00:15 12
`11:33:37
`07128/XX
`07/30/XX
`09:08:13
`10:05:~0
`08110/XX
`09:10:13
`
`081110/XX
`09:10:17
`
`Resend
`Time
`Period
`
`1 hour
`
`Review
`Post-
`Remindc Review
`rTime
`Time
`Period
`.Period
`1 day
`1 hour
`
`2 hours
`
`18 hours
`
`2 days
`
`I day
`
`1
`minute
`
`Message Tracking Table (continued)
`
`Row/
`Column
`
`9
`
`10
`
`11
`
`Post-
`Review
`Review
`Reminder
`Record
`Record
`07/27/XX 07/28/XX
`18:30:10
`11:13:00
`
`Resend
`Record
`
`07/26/X.Y..
`20:26:45
`07/26/XX
`22:28:13
`
`1
`
`2
`
`3
`
`4
`
`i
`
`I
`
`127
`
`(
`
`/
`
`P.
`
`I
`
`\3
`
`14
`
`Reseml
`Options
`
`High
`Pnorily
`::Vfax
`3 times
`
`Review
`Reminder
`OptlDns
`High
`Urgem;y
`Template
`X
`
`Post-
`Review
`Options
`Message
`y
`
`07/31/XX
`09:10:00
`08/0JIXX
`09:10:10
`
`Supervisor Template
`R
`Template
`s
`
`Fig. 2
`
`Apple Inc.
`Exhibit 1006
`Page 004
`
`

`

`U.S. Patent
`
`Feb.8,2005
`
`Sheet 3 of 7
`
`US 6,854,007 Bl
`
`~:ssage Sender
`~- Routine
`
`eivc Electronic
`Message
`
`[ :
`
`'
`~~'ce:ve designation of
`L recipient
`
`I Add entry to Mcssge
`
`L lracking Table
`
`~ive designation of
`
`message tracking
`ions for recipient
`
`300
`
`305
`
`310
`
`313
`
`315
`
`320
`Yes
`
`resending,
`""-~cquested?
`
`1\;o
`
`Fig. 3A
`
`Cpdatc Messal~e
`Tracking Table with
`Message Rcsend Time
`and Rcsend Options
`
`325
`
`327
`
`B
`
`Apple Inc.
`Exhibit 1006
`Page 005
`
`

`

`U.S. Patent
`
`Feb.8,2005
`
`Sheet 4 of 7
`
`US 6,854,007 Bl
`
`330
`
`Yes
`
`B
`
`Update Message
`Tracking Table with
`Message Review
`Reminder Time and
`Review Reminder
`Options
`
`337
`
`340
`
`L___[Sot Rwiow
`
`Reminder timer
`
`<
`
`Reminding
`Requested?
`
`No
`
`)ost~Rcview
`r-.io
`~ Messages
`Requested')
`
`Yes
`
`1
`
`-
`
`Update Yiessage
`. Tracking Table with
`?ost~Review Time and
`Post-Review Options
`
`345
`
`350
`
`<
`
`More
`
`Send Message to
`recipients aud update
`1lessage Tracking Table
`with Send Time
`
`[
`
`355
`
`360
`
`Yes
`
`More Messages
`to Send?
`
`End
`
`395
`
`Fig. 3B
`
`Apple Inc.
`Exhibit 1006
`Page 006
`
`

`

`U.S. Patent
`
`Feb.8,2005
`
`Sheet 5 of 7
`
`US 6,854,007 Bl
`
`400
`
`.\1essage Receipt
`Tr~cker Routine
`
`-=r=:
`Receive receipt for ser~
`electronic message J 405
`
`430
`
`,~ "\dd review time to
`r
`_:1essag8 Tracking Table
`
`Yes
`
`435
`
`[~
`
`Re,el any extsting
`Review Reminder timers
`
`440
`
`Set Post-Review tm1er if
`indicated by Post(cid:173)
`Review Options
`
`415
`
`Add delivery time to
`Message Tracking Table
`
`Reset any existing
`Resend timers
`
`445
`
`495
`
`Fig. 4
`
`Apple Inc.
`Exhibit 1006
`Page 007
`
`

`

`U.S. Patent
`
`Feb.8,2005
`
`Sheet 6 of 7
`
`US 6,854,007 Bl
`
`Message Tracking
`Table
`Processor Routine
`
`/
`
`1
`
`r
`
`500
`
`Fig. 5A
`
`Select First Entry in
`Message Tracking
`Table
`
`/505
`
`510
`
`Yes
`
`timer expired?
`
`No
`
`Rcscnd message to
`recepient as indicated by
`Resend options, and
`update Resend Records
`m :Message Tracking
`Table
`
`/
`
`525
`
`520
`
`Send reminder message
`as indicated by Review
`Reminder Options, and
`Yes
`> ~--• update Review
`Reminder Records in
`Message Tracking Table
`
`eview Rcm;nder
`timer expired'J
`
`No
`
`c~ B
`
`Apple Inc.
`Exhibit 1006
`Page 008
`
`

`

`U.S. Patent
`
`Feb.8,2005
`
`Sheet 7 of 7
`
`US 6,854,007 Bl
`
`Post-Review
`timer expired?
`
`l\o
`
`530
`
`Yes
`
`l
`
`Send l'ost-Review
`message as imliLOated
`by Pnst-Reviev,
`Options, and Epdate
`Post-Review records
`in ',1essage Tracking
`~_ _ _ Tabk
`
`L----------------~
`
`/
`
`- 537
`
`[!~
`_C_
`I Remove entry fmr}1
`L:-,ge Tracking
`Table
`
`535
`
`539
`
`538
`
`Set new timers
`if needed
`
`545
`
`Yes
`
`More
`entnes''
`
`Yes
`
`~c--~-----+j
`
`550
`
`Sc !eel next entry in
`Message Tracking
`Table
`
`Fig. 5B
`
`END
`
`Apple Inc.
`Exhibit 1006
`Page 009
`
`

`

`US 6,854,007 Bl
`
`1
`METHOD AND SYSTEM FOR ENHANCING
`RELIABILITY OF COMMUNICATION WITH
`ELECTRONIC MESSAGES
`
`TECHNICAL FIELD
`
`The present invention relates generally to communicating
`via electronic messages, and more particularly to enhancing
`the reliability of the communication.
`
`BACKGROUND OF THE INVENTION
`
`Electronically-communicated messages ("electronic
`messages") such as email, paging messages, and voice mail
`have become increasingly popular and pervasive in recent
`years. For the creator of an electronic-message, the ability to
`send the message to one or more recipients provides for
`quick and efficient communication. Such communication via
`electronic messages has become common in both business
`and personal settings.
`While the initial distribution of electronic messages by a
`sender is quick and convenient, ensuring that an electronic
`message is delivered (i.e., received by the recipient) and
`reviewed (e.g., reading an email or paging text, viewing an
`email image, listening to a voice mail message, etc.) within
`a certain time frame is not convenient. Due to the asynchro(cid:173)
`nous nature of most electronic message transmission
`systems, immediate feedback is not provided as to whether
`the electronic message has been reliably received by each of
`the recipients. Some transmission systems provide a facility
`such that if an error is detected by a sending system (e.g., a
`recipient system is currently unavailable at the time of
`sending, the sending system may attempt to resend the
`electronic message. In such systems, if the error reoccurs,
`the transmission system typically notifies the sender that
`delivery failed. Thus, the sender receives no indication that
`message delivery problems exist until after an amount of
`time, which can be lengthy, has elapsed. In other transmis(cid:173)
`sion systems, the sender will receive no notification even if
`the delivery of the electronic message fails.
`Moreover, even if the delivery of an electronic message to
`a recipient is successful, it if often important that the
`recipient review the electronic message within a certain
`amount of time. Transmission systems typically do not
`provide a mechanism to reliably ensure that a recipient has
`reviewed a successfully delivered message. A few transmis(cid:173)
`sion systems allow the sender to request notification when
`an electronic message is received by a recipient and when it
`is accessed (e.g., opened by an application program with
`which the recipient can review the message) by the recipient.
`In some such systems, the recipient's system will provide to
`the sender's system a delivery receipt or a review receipt to
`provide notification when delivery or review of an electronic
`message has occurred. Thus, if a review receipt has not yet
`been received, then the recipient may not have reviewed the
`electronic message. However, the sender has no automatic
`means of prompting or convincing the recipient to review
`the electronic message. Finally, if it desirable that some
`action be automatically performed after a recipient has
`reviewed an electronic message (e.g., sending a follow-up
`message), there is no automatic means of providing this
`functionality.
`
`SUMMARY OF THE INVENTION
`
`Some embodiments of the present invention provide a
`method and system for enhancing the reliability of commu-
`
`5
`
`10
`
`2
`nicating with electronic messages. In particular, the system
`sends an electronic message to designated recipients, and
`then automatically helps ensure that each message has been
`successfully delivered and that each message has been
`reviewed. If the delivery or review of the electronic message
`has not been confirmed after a certain time period, the
`system can automatically resend the electronic message or
`take some other appropriate action. In addition, even if
`delivery or review has been confirmed, the system can
`automatically perform additional specified activities.
`The system allows a sender of an electronic message to
`specify message tracking information, such as message
`delivery information and message review information, that
`specifies actions to take when a message is not delivered or
`not reviewed within a specified period of time. For example,
`15 the sender can specify that if a delivery notification is not
`received within a specified period of time, the message will
`be resent to the recipient. Alternately, if a review notification
`is not received within a specified period of time, the sender
`can specify that a reminder message be sent to the recipient
`20 or to another user (e.g., the recipient's supervisor or
`assistant). The message tracking information can include
`various frequency and duration options, such as resending a
`message only once or instead resending it every 2 hours for
`a week. In addition, message tracking information can
`25 specify to resend the message with a higher transmission
`priority or review urgency so that its delivery and review is
`more likely, or could specify to resend the message or send
`a reminder message to a different recipient system for the
`recipient (e.g., to a second email address if a first address
`30 fails, or to a pager if a cellular phone is not available).
`The system also allows a sender of an electronic message
`to specify message tracking information that specifies
`actions to take after a message is successfully delivered or
`reviewed. For example, the sender can specify that a super(cid:173)
`visor receive a confirmation when a recipient receives an
`35 electronic message and when the recipient reviews the
`message. Alternately, a recipient can be sent a follow-up
`message after review of a first electronic message. The
`message tracking information can include various frequency
`and duration options, such as sending confirmation mes-
`40 sages immediately and sending follow-up messages after a
`specified period of time has elapsed since review of the
`original message.
`In one embodiment, the sender can individualize the
`message delivery information for each recipient of a
`45 message, while in another embodiment the sender can use
`the same message delivery information for all recipients.
`The system tracks whether each message has been delivered
`and reviewed by to each recipient, and uses the message
`information to resend the messages whose delivery or
`50 review is not confirmed.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`FIG. 1 is a block diagram illustrating an embodiment of
`the Message Review Server system of the present invention.
`FIG. 2 is an example of a Message Tracking Table.
`FIGS. 3A and 3B are an exemplary flow diagram of an
`embodiment of the Message Sender routine.
`FIG. 4 is an exemplary flow diagram of an embodiment
`of the Message Receipt Tracker routine.
`FIGS. SA and 5B are an exemplary flow diagram of an
`embodiment of the Message Tracking Table Processor rou(cid:173)
`tine.
`
`DETAILED DESCRIPTION OF THE
`INVENTION
`An embodiment of the present invention provides a
`method and system for enhancing the reliability of commu-
`
`55
`
`60
`
`65
`
`Apple Inc.
`Exhibit 1006
`Page 010
`
`

`

`US 6,854,007 Bl
`
`3
`nicating with electronic messages. In particular, the Message
`Review Server (MRS) system sends an electronic message
`to designated recipients, and then automatically helps ensure
`that each message has been successfully delivered and that
`each message has been reviewed. If the delivery or review
`of the electronic message has not been confirmed after a
`certain time period, the system can automatically resend the
`electronic message or take some other appropriate action. In
`addition, even if delivery or review has been confirmed, the
`MRS system can automatically perform additional specified
`activities.
`The MRS system allows the sender of an electronic
`message to specify message delivery information that speci(cid:173)
`fies actions to take when a message is not delivered within
`a specified period of time. For example, the sender can
`specify that if a delivery notification is not received within
`a specified period of time, the message will be resent to the
`recipient. The message delivery information can also
`include various frequency and duration options, such as
`resending the message only once or instead resending it 20
`every 2 hours for a week in addition, message delivery
`information could indicate to resend the message with a
`higher transmission priority so that successful delivery is
`more likely, or could indicate to resend the message to a
`different recipient system for the recipient (e.g., to a second 25
`email address if a first address fails, or to a pager if a cellular
`phone is not available). The MRS system tracks whether
`each message has been delivered to each recipient, and uses
`the message delivery information to resend the messages
`whose delivery was not verified to be successful.
`The message delivery information can be specified at the
`time of sending the original message, or in some
`embodiments, even after the message has been sent. In one
`embodiment, each recipient of a message can have individu(cid:173)
`alized message delivery information, while in another 35
`embodiment all recipients of a message will share the same
`message delivery information. In addition, the MRS system
`can store such message delivery information in a variety of
`ways. For example, such information could be stored with
`the message (e.g., as a header or as attributes of a message 40
`object). Alternately, message delivery information can be
`stored in a Message Tracking Table accessible by the MRS
`system.
`The MRS system also allows a sender of a message to
`specify message review information that specifies actions to 45
`take when a message is not reviewed within a specified
`period of time. As with the message delivery information,
`this information can be specified in some embodiments at
`the time of sending the message and in other embodiments
`at later times, and in some embodiments message review 50
`information is specified individually for each recipient while
`in other embodiments the information is specified uniformly
`for all recipients of a message. To enhance the likelihood
`that the message is timely reviewed by a recipient, the
`sender can specify a time period after which a reminder 55
`message will be sent if the sender has not been notified
`within that time period that the recipient has reviewed the
`message. This reminder message can have a variety of
`formats. For example, in one embodiment, the same mes(cid:173)
`sage is resent to the recipient, but it is marked as being 60
`urgent and for immediate attention. In an alternate
`embodiment, a different message is sent to the recipient
`(e.g., a reminder to read the original message). In another
`embodiment, a message can be sent to an alternate recipient
`who can assist in ensuring that the original recipient review 65
`the original message (e.g., a supervisor of or an assistant to
`the original recipient). As with the original message, this
`
`4
`reminder message can be reliably sent with the MRS system
`so as to enhance the reliability of its delivery and review.
`After an electronic message has been delivered to or
`reviewed by a recipient, it may be desirable to have the MRS
`5 system automatically take various actions. For example, it
`may be desirable to automatically send one or more addi(cid:173)
`tional messages at specified periods after the message was
`delivered or reviewed. If the original message was to pro(cid:173)
`vide product information to a customer, an automatic
`10 follow-up message to the customer offering additional help
`or soliciting comments may be beneficial. Alternately, the
`original message may have been the first part in a multi-part
`series of messages (e.g., a serial novel), with later messages
`sent only after earlier messages have been reviewed. Thus,
`15 the sender can also specify message post-delivery and
`post-review information, including a time period after the
`delivery or review of the original message at the end of
`which a specified action is to be taken. For the specified
`action to be taken immediately, the time period can be set to
`zero.
`Thus, the MRS system can automatically locate and
`resend an original message when delivery has not been
`confirmed, can automatically send one or more reminder
`messages to the recipient or to others to prompt the recipient
`to review the original message when review of the electronic
`message has not been confirmed; and can automatically
`perform additional activity when delivery or review of the
`original message has been confirmed.
`FIG. 1 illustrates a server computer system 100 suitable
`30 for executing an embodiment of the Message Review Server
`(MRS) system, as well as recipient computer systems 150,
`160, 170, and 180 suitable for receiving electronic messages
`transmitted by the MRS system. In the illustrated
`embodiment, the server computer system and recipient com(cid:173)
`puter systems are connected via network 140, although any
`transmission medium (e.g., circuit-based telephone lines,
`packet-based computer lines, wireless RF, etc.) can be used
`for the transmission of the electronic messages. The server
`computer system includes a CPU 110, input/output devices
`120, and a memory 130. The input/output devices include a
`storage device 126, a network connection 122, a computer-
`readable media drive 123, and a display 124, with a Message
`Tracking Table 127 stored on the storage device. The
`Message Review Server system 132 is executing in memory,
`and is composed of the Message Sender 134, Message
`Receipt Tracker 136, and Message Tracking Table Processor
`137 components.
`Use of the MRS system begins when a sender of an
`electronic message, such as a user of the server computer
`system or another computer attached to the network 140,
`supplies a message to the Message Sender component. In
`addition to supplying the message, the sender identifies one
`or more recipients for the electronic message, and can
`specify various optional message tracking information (i.e.,
`message delivery information, message review information,
`and message post-review information). If the reliability of
`the delivery of the message to a recipient is to be enhanced,
`a sender will supply delivery information including a resend
`period of time and can optionally supply other resend
`options. If the reliability of the review of the message by a
`recipient is to be enhanced, the sender will supply review
`reminder information including a review reminder period of
`time and can optionally supply other review reminder
`options. Finally, if actions are to be taken after a recipient
`has reviewed the message, post-review information includ(cid:173)
`ing a post-review period of time and post-review options can
`be supplied.
`
`Apple Inc.
`Exhibit 1006
`Page 011
`
`

`

`US 6,854,007 Bl
`
`5
`The Message Sender component collects the supplied
`message tracking information, sends the message to the
`specified recipients, and stores the message tracking infor(cid:173)
`mation and the message send time in the Message Tracking
`Table. The Message Sender component also sets appropriate 5
`Resend timers (based on the delivery resend time period)
`and Review Reminder Timers (based on the Review
`Reminder Time period) for the recipients as indicated in the
`message tracking information supplied by the sender. Use of
`various timers will be explained in greater detail below. If 10
`different recipients of a message are to have different mes(cid:173)
`sage tracking options, a separate entry in the Message
`Tracking Table will be created for each recipient of each
`message. Alternately, if all recipients of a message have the
`same message tracking options, a single entry in the Mes- 15
`sage Tracking Table can be created for the message.
`The Message Receipt Tracker component attempts to
`identify when sent messages have been delivered to recipi(cid:173)
`ents and when sent messages have been reviewed by recipi(cid:173)
`ents. In one embodiment, the recipient computer systems 20
`provide receipts when messages are received and when
`messages are reviewed, and in this embodiment the Message
`Receipt Tracker is notified of these receipts. Alternately, the
`Message Receipt Tracker can periodically query a recipient
`to determine if the recipient has received and reviewed a 25
`message, or can monitor a recipient's activities to determine
`when the recipient accesses and reviews a message. After a
`message has been accessed, activities such as scrolling a text
`window or selecting text may indicate that the message is
`being reviewed, or movement of the recipient's eyes could 30
`indicate where attention is focused. After receiving notifi(cid:173)
`cation of message delivery or review, the Message Receipt
`Tracker stores appropriate information from the notification
`in the Message Tracking Table (e.g., the time of delivery for
`a notification indicating that a message was delivered to a 35
`recipient and the time of review for a message that was
`reviewed by a recipient). After receiving a notification, the
`Message Receipt Tracker also resets any existing timers
`related to the notification (e.g., a Resend timer for a delivery
`notification or a Review Reminder Timer for a review 40
`notification). If a review notification is received, the Mes(cid:173)
`sage Receipt Tracker also determines if the corresponding
`message and recipient have post-review activities specified,
`and if so sets an appropriate Post-Review timer.
`The Message Tracking Table Processor component peri- 45
`odically reviews the information in the Message Tracking
`Table as well as the current timers to determine whether a
`specified tracking time period has expired, thus indicating a
`corresponding action needs to be taken. When a Resend
`timer has expired, the Message Tracking Table Processor
`uses the resend options specified for the one or more
`recipients (or uses default options if none have been
`specified) and resends the message to the one or more
`recipients. If a Review Reminder Timer has expired, the
`Message Tracking Table Processor uses the review reminder
`options to create a reminder electronic message to be sent,
`and then sends the message to one or more recipients as
`indicated by the options. Similarly, if a Post-Review timer
`has expired, the Message Tracking Table Processor performs
`the activities specified in the Post-Review options, such as
`sending a follow-up message to one or more recipients.
`After sending a message in response to expiration of a
`time period, the Message Tracking Table Processor records
`the time of sending the message in an appropriate portion of
`the Message Tracking Table for the message and the one or
`more recipients. In addition, if it is appropriate to set another
`timer (e.g., if a message will continue to be resent until the
`
`6
`MRS system is notified that it has been delivered to the
`recipients), a new timer with the appropriate time period is
`set. Alternately, if all required actions have been taken for a
`message and one or more recipients (e.g., notification has
`been received that the message has been reviewed and no
`Post-Review actions have been specified), the entry in the
`Message Tracking Table corresponding to the message and
`the one or more recipients is modified so that it is no longer
`checked by the Message Tracking Table Processor. In one
`embodiment, a flag is set in the entry, while in another
`embodiment the entry is removed from the Message Track-
`ing Table. Those skilled in the art will appreciate that rather
`than using timers, an alternate embodiment can have the
`Message Tracking Table Processor calculate directly from
`information in the Message Tracking Table whether any
`action currently needs to be taken, such as by reviewing the
`specified time periods and the specified records (i.e., the
`send times for messages as well as the delivery and read
`times for the original message).
`The recipient computer system 150 includes a CPU 151,
`a memory 152, and input/output devices 156, including a
`storage device 158. One or more stored messages 159 can be
`stored on the storage device, with the stored messages
`accessible corresponding to one or more users of the recipi(cid:173)
`ent computer system. A message reviewer 154 is executing
`in memory 152 to allow a user of the recipient computer
`system to review messages that have been received by the
`recipient computer system and stored in the stored mes(cid:173)
`sages. In an alternate embodiment, messages can be stored
`on the server computer system, and the message re