as) United States
`a2) Patent Application Publication (0) Pub. No.: US 2004/0068545 Al
`(43) Pub. Date: Apr. 8, 2004
`
`Daniell et al.
`
`US 2004006854S5A1
`
`(54) DISPLAYING AND WORKING WITH EMAIL
`ATTACHMENTS
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 60/416,916, filed on Oct.
`8, 2002. Provisional application No. 60/426,422, filed
`on Nov. 14, 2002.
`
`Publication Classification
`
`(ST) TM C1? cecccecccccccccessssssssossssssesesceeeeneeseeseees 206F 15/16
`G2) USEC:
`sccssississssainicccusnsseccsmaisscanscinncccectss 709/206
`
`(57)
`
`ABSTRACT
`
`(75)
`
`Inventors: W. Todd Daniell, Marietta, GA (US);
`Mary 8S. Arnoff, Lawrenceville, GA
`(US); Dale W. Malik, Dunwoody, GA
`(US)
`
`Correspondence Address:
`THOMAS, KAYDEN, HORSTEMEYER &
`RISLEY, LLP
`100 GALLERIA PARKWAY, NW
`STE 1750
`ATLANTA, GA 30339-5948 (US)
`
`(73) Assignee: BellSouthIntellectual Property Corpo-
`ration, Wilmington, DE
`
`(22)
`
`Filed:
`
`Dec. 19, 2002
`
`invention provide
`Preferred embodiments of the present
`systems and methods for organizing and managing attach-
`ments from electronic messages. One embodiment ofthe
`system, among others,
`includes an electronic messaging
`client for receiving electronic messages and an attachment
`management system configured to preorganize detault direc-
`tory locations for saving attachments into those directory
`(21) Appl. No.:—10/326,250
`locations andalso to display descriptive information regard-
`ing attachments such as name, type, and size. Other systems
`and methods are also provided.
`
`NO
`
`
`
`
`MEMORY
`104
`
`
`ATTACHMENT
`MANAGEMENT
`SYSTEM
`
`
`
`101
` PROCESSOR
`ELECTRONIC
`MSG. SYSTEM
`102
`lus
`OPERATING
`SYSTEM
`
`(O/S)
`110
`
` LOCAL INTERFACE 108
`
`
`
`
`
`
`INPUT/OUTPUT
`
`
`DEVICE(S)
`(1/0)
`106
`
`
`DATA
`CONNECTION
`
`12
`120
`
`REMOTE
`COMPUTER
`
`1
`
`Facebook Ex. 1010
`Facebook Ex. 1010
`U.S. Pat. 7,535,890
`US. Pat. 7,535,890
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 1 of 14
`
`US 2004/0068545 Al
`
`FLOWAY
`
`UILNdWOD
`
`0zI
`
`zit
`
`Vivd
`
`NOLLOANNOD
`
`LNAWHOV.LLY
`
`LNAWADVNVIM
`
`WALSAS
`
`OINOWLOAaLO
`
`
`
`WALSAS‘DSW
`
`sit
`
`ONILVUddO
`
`W3LSAS
`
`(S/o)
`
`OLl
`
`801AOVAYALNIIVOOT
`
` LNd.LNO/LNdNI
`
`
`
`TO
`
`(S)401Aaa
`
`(o/D
`
`901
`
`wossaoowd
`
`zor
`
`2
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 2 of 14
`
`US 2004/0068545 Al
`
`ATLOATASOLYASN
`
`
`
`AYOLOAUIGLTAVAAGWOU
`
`0€z
`
`tO
`
`LdWOUd
`
`00?—¥
`
`
`
`OLYASNLdNOUd
`
`
`
`LTAVIIAJUNOIINODANd*
`
`
`
`ONILLASAYOLOTAIG
`
`O1z
`
`
`AYOLOMUIGGALLIOTdS-YASNLASeSINOdeaHaeSI
`
`AYOLOTUILINVIIGSv.
`riz_—Ziz
`
`
`
`
`
`
`
`NVSV911dGa.LOSTASGdv
`
`LNANHOVILVY
`
`Obz
`
`
`
`SVAYOLOSAIGGANINSGsadLAS
`
`
`
`AMOLOAAIGLTINVAG
`
`91z
`
`
`
`NVddvVOLGNVWIWODJAISOgu
`
`LNAWHOVLLY
`
`Oz
`
`3
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 3 of 14
`
`US 2004/0068545 Al
`
`
`
`SSANOUdLIGS/NAdO
`
`06€
`
`
`
`SSHOOUdTVAOWSY
`
`ose
`
`
`
`SUNDINOOOLWISNLdNOUd
`
`
`
`
`
`SONLLIASAYOLOSUICLTAVAAG
`
`
`
`ddALAWMOOALVOHOVYOd
`
`ole
`
`
`
`LINVAES¥NOILYOOTESGNOdSAUWISN
`
`AMOLOSAIGGANGAadLAS
`
`
`NOILV9OOTAYOLOTUIGOcE
`
`¢‘OW
`
`
`
`WOUAdLOATAS
`
`
`
`NOLLVOOYAHLONV
`
`S9€
`
`WOUAdLOATAS
`
`éLInvaaa
`
`z9€
`
`INANHOVLLYSVIdGav
`
`ore-
`
`
`
`NOILVD0OTAYOLOAAIG
`
`ore
`
`
`
`NVddVOLGNVWWOdSAISOaY
`
`INAWHOVLLY
`
`Ose
`
`
`
`adLOATASOLYASNLdNOUd
`
`LITNVAAGJOANOWOU
`
`
`
`SNOILVOOTAYOLOAUIA
`
`O9E
`
`NOILVWYOINI
`
`
`
`daddvONIGHYVOFe
`
`AV1dSI0OfE
`
`
`
`PAEAYOLOAAUIGGAZINOLSNOLAS
`
`aTLTAVAd$VNOILVOOT
`
`4
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 4 of 14
`
`US 2004/0068545 Al
`
`
`
`
`
`NOILVAROANIAV1dSIGFLVadn
`
`
`
`LINANHOVLLVONIGUVOTY
`
`Obs
`
`$‘OA
`
`POW
`
`O1s
`
`LNAWHOVLLYNVSAOWSY
`
`OLAUNVWWOOVSAISON
`HH08
`
`GLEet
`
`
`
`CNV“AdA.LL“AINVNAHLAV1dSI0
`
`INAWHOVLLVAHLAOAZI8
`
`Olb
`
`
`
`UVINOILAVdLOATAS
`
`INAWHOVLLY
`
`ozs
`
`
`
`ddLOATASAAOWAYA
`
`INAWHOVILV
`
`ogs
`
`
`
`HHLdOAZIS‘IWLOLAHLAWTdSIG
`
`SLNHNWHOVILV
`
`Oz
`
`5
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 5 of 14
`
`US 2004/0068545 Al
`
`
`
`
`
`DNISO'TOUALAVJOVSSAW
`
`NOILVOTTddvV
`
`Org
`
`NOILVWHYOANIAVIdSIGALWGdn
`
`
`
`LNSWHOIVLLVYONIGUVOAY
`
`os9
`
`9°D14
`
`06—-
`
`NadOOLGNVWIOOVSAISOae
`
`INSWHOV.LLVNV
`
`019
`
`
`
`YVINOLLAVdLOATAS
`
`INAWHOVLLY
`
`029
`
`
`
`UVTINOLLAVdNadO
`
`VIALNSNHOVLLVY
`
`
`
`NOILVOITddVS.LNANHOVLLY
`
`09
`
`ONISOdWOOOLNYNLAY
`
`6
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 6 of 14
`
`US 2004/0068545 Al
`
`00L—¥
`
`
`
`JINOYLOATAONINOONINVSAISON
`
`
`
`NVONINIVINOO3DVSSaW
`
`INSWHOVLILV
`
`Old
`
`
`
`YHaWANSHLAVTdSId
`
`
`
`MOCNIA,MATAdad
`
`StL
`
`Oz
`
`NISINAWHOVILILVJO
`
`
`éACOWMAIATUd
`
`
`
`HLIMONIGVAHADVSSAWAVTdSIG
`
`
`
`YOLVOIGNILNSNHOVLLV
`
`O€L
`
`7
`
`L°o1
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 7 of 14
`
`US 2004/0068545 Al
`
`8°*Old
`
`
`
`HOVSSAN
`
`098
`
`0s8
`
`ONGYVOdeANOILVAYOANIAVTdS10
`
`
`
`JOVSSAWOINOULOATEJAIOFeY
`
`HHLONINAdOLNOHLIMLNSNHOVLLY
`
`
`
`LNFNHOVLLYANOLSV3TLYONINIVINOD
`
`
`
`ADVSSIWNAdO
`
`0L8
`
`
`
`AYOLOAUIGLTNVAACSVNOILVOOT
`
`NOILVOOT
`
`|
`
`Ors
`
`
`
`
`
`AYOLOAUIGGaldIOddSYASNLAS
`
`INAWNHOVLLYNadO
`
`068
`
`
`
`018
`
`VdOLNANHIVLLVYNVONIAVS
`NOLLVOIISSV19NIVLYIO
`
`AUNDIANOOAAdOLUSNLdWOUd
`
`
`
`
`
`YOASONILLASAYOLOAYIGLINVAIA
`
`
`
`LNAWHOVLLYJAYS
`
`088
`
`
`
`AMOLOTAIGGANIWAGAadLAS
`
`
`
`NOILVOOTAYOLOAYIG0¢8
`
`
`
`LTINVIAIGSVNOILVOOTédSNOdSdu
`
`0€8__
`
`8
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 8 of 14
`
`US 2004/0068545 Al
`
`
`
`
`
`CNV4dAL‘AWVNSHLAV1dSI0
`
`
`
`‘IVNCIAIGNIHOVS403ZIS
`
`
`
`JOVSSAWNILNIWHOVLLV
`
`0£01
`
`adaddAWNNFHLAVTdSId
`
`
`
`NISLNAWHOVLLVJO
`
`
`
`MOQCNIMMAIATYd
`
`S76
`
`01‘SIA
`
`6‘Old
`
`ed
`
`
`
`
`
`HHLWOGNVAWOOSAATSONY
`
`UVINIILUVdVAVIOLWISN
`
`
`
`FOVSSAWOINOULOATA
`
`
`
`HOVSSHAWOINOWLOATANadO
`
`09g——*
`
`
`
`
`
`ONIGVAHADVSSAWVAVTdSIG
`
`
`
`YO.LVOIGNILNAWHOVLLYALIA
`
`016.
`
`
`
`YAAVAHADVSSAW¥LOATAS
`
`$16
`
`
`
`éAQOWMAIATYd
`
`_06
`
`9
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 9 of 14
`
`US 2004/0068545 Al
`
`
`
`CNYLNSWHOVLLYaSO719
`
`
`
`
`
`OLNYNLAYAGNVNOILVSITIddV
`
`
`
`ONIDVSSAWNOINOYLOATA
`
`LNAI.
`
`O€ZI
`
`clOW
`
`
`
`HHLLVLYWYOdSAILVN
`
`NOILVOOT
`
`Ori
`
`JOAW1dSIdOLNYNLAY
`
`JINOYLOATAJOSLNALNOO
`
`HOVSSAN
`
`Ost
`
`Il‘Old
`
`
`
`
`
`SLINILNJWHOVILYGUOLS
`
`068—*
`
`
`
`N3dOO.LGNVAWIWODSATSOFN
`
`INAWHOVILVYNV
`
`OIcl
`
`0sg—*
`
`
`
`INANHOVLLYUVTINOILYVdVFAVSOLGNVWINOOJAISO9N
`
`OIII
`
`
`
`
`AYOLOTAUIG
`
`LTANVAAVLVddAJAVSOLYASNIdWOUd
`
`OclI
`
`
`
`
`
`
`
`ONISNLNAWHOVLLYNAdO
`
`
`
`
`
`NOILVOO'TAYOLOAICFATAOTa
`
`
`
`NOILVOIMIddVGALVIOOSSV
`
`Occ
`
`Ofll
`
`wasnWows
`
`10
`10
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 10 of 14
`
`US 2004/0068545 Al
`
`MESSAGE CENTER
`
`
`
`[coer
`
`CURLY'S INBOX
`
`
`|_| HANCOCK, JOHN|LUNCH 7 WED 2/13/1976
`
`DATE
`SUBJECT
`|__| FROM
`
`
`BIG IDEAS
`
`REMINDER
`A_[
`ROSS, BETSY
`
`OK?
`
`MON 2/11/1976
`
`FROM: JOHN ADAMS TO: CURLY@STOOGES.TRI
`SUBJECT: BIG IDEAS
`
`3 ATTACHMENTS
`
`PLEASE REVIEW MY THREE PROPOSALS AND THEN WE'LL TALK.
`
`PREVIEW
`WINDOW
`
`FIG. 13
`
`11
`
`

`

`Patent Application Publication
`
`Apr. 8,2004 Sheet 11 of 14
`
`US 2004/0068545 Al
`
`MAIL OPTIONS ©
`
`
`
`THE MESSAGE CENTER WILL AUTOMATICALLY CHECK FOR NEW MAIL THROUGHOUT THE
`DAY AS LONG AS YOUR COMPUTERIS TURNED ON AND CONNECTEDTO A PHONELINE
`
`ALWAYS CHECK FOR NEW EMAIL WHENEVER | START UP THE MESSAGE CENTER
`[_] YES, AUTO CHECK FOR NEW MAIL
`NO, DO NOT AUTO CHECK.
`| WILL USE THE "GET MAIL" BUTTON TO CHECK FOR NEW
`MAIL
`
`LWSAVEJ}LCANCELJ
`
`INDICATE YOUR CONNECTION TYPE:
`
`DIAL ACCESS
`
`SPECIFY DEFAULT LOCATIONS TO SAVE ATTACHMENTS
`
`FILES
`
`C:/PROGRAM FILES/MESSAGE CENTER/F
`
`|
`
`BROWSE
`
`PICTURES [C/PROGRAM FILES/MESSAGE CENTER/P|[|BROWSE_|
`
`
`
`SOUNDS [C/PROGRAM FILES/MESSAGE CENTERS||| BROWSE |
`
`PRECONFIGURE
`DEFAULT
`LOCATIONS
`
`FIG. 14
`
`12
`
`

`

`Patent Application Publication
`
`Apr. 8,2004 Sheet 12 of 14
`
`US 2004/0068545 Al
`
`[SAVEASDRAFTJ
`FROM: CURLY@STOOGES.TRI
`
`[cance|
`
`to:|t—i“‘™éOOO!OOOOCOCOCOC#@d”S#SC«SYGEADORESS|
`USE A COMMA TO SEPARATE MULTIPLE ADDRESSES
`ce:[iC™~“‘CSNCCOC#C#C(C(C(C#d;#é«@eraboress_J
`SUBJECT[| —‘id@d;
`
`
`
`ara Od Do
`
`TYPE YOUR MESSAGE HERE.
`
`ATTACHMENTS
`
`aas
`
`ADD OR REMOVE
`
`&£
`
`ATTACHMENTS
`
`FIG. 15
`
`13
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 13 of 14
`
`US 2004/0068545 Al
`
`ADD OR REMOVE ATTACHMENTS
`
`
`
`TO ATTACH FILES TO THIS MESSAGE,CLICK ANY OF THE BUTTONS BELOW AND THEN
`NAVIGATE TO SELECT THE FILE YOU WANT TO ATTACH.
`
`OR, YOU CAN ATTACH/REMOVEA FILE BY DRAGGING IT FROM YOUR DESKTOP AND
`DROPPING IT INTO THE ATTACHMENT BOX BELOW.
`
`|___ADD FILES
`|__ ADD PICTURES ‘|
`|__ADD SOUNDS
`__Jf
`
`CMY DOCUMENTS\
`(CMY PICTURES\
`[C:\MY SOUNDS\
`
`|
`
`|BROwsE|
`[___BROWsE|
`[BROWSE|
`
`TO REMOVE AN ATTACHMENT, SELECT THE ATTACHMENT ABOVE AND CLICK REMOVE LREMOVE|
`
`ATTACHMENT BOX
`
`SIREN.WAV
`(33 kB)
`
`FIG.16
`
`14
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 14 of 14
`
`US 2004/0068545 Al
`
`Ilex!
`
`FORWARD
`
`DATE: FEBRUARY8, 1976
`ao ADAMS, JOHN
`O: HOWARD, CURLY
`CC:
`SUBJECT: BIG IDEAS
`
`PLEASE REVIEW MY THREE PROPOSALS AND THEN WE'LL TALK.
`
`OK?
`
`-- JOHN
`
`ADOBE ACROBAT DOCUMENT
`
`YOU HAVE 3 FILE(S) ATTACHED.
`
`LLswerce—] [_orenrie9
`
`
`
`PROPOSAL1.DOC
`
`WORD FILE
`
`
`
`PROPOSAL2.ZIP
`
`PROPOSAL3.PDF
`
`WINZIP FILE
`
`FIG. 17
`
`15
`
`

`

`US 2004/0068545 Al
`
`Apr. 8, 2004
`
`DISPLAYING AND WORKING WITH EMAIL
`ATTACHMENTS
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application claims priority to copending U.S.
`provisional applications entitled, “FUNCTIONAL SPECI-
`FICATION FOR E-MAIL CLIENT,” having serial No.
`60/416,916, filed Oct. 8, 2002, which is entirely incorpo-
`rated herein by reference;
`and “DISPLAYING AND
`WORKING WITH EMAIL ATTACHMENTS,” having
`serial No. 60/426,422, filed Nov. 14, 2002, which is entirely
`incorporated herein by reference.
`
`TECHNICAL FIELD
`
`{0002] The present invention is generally related to elec-
`tronic messaging, and more particularly, is related to attach-
`ments for electronic messaging.
`
`BACKGROUND OF THE INVENTION
`
`[0003] Electronic messaging involves the transmission of
`electronic messages over computer networks, such as a local
`area network or the Internet. An electronic message may be
`a simple text message containing only ASCII, or it may be
`a complex message containing electronic files such as
`images, sounds, spreadsheets, etc. Electronic messaging is
`generally referred to as email, but it may also comprise other
`messaging technologies like instant messaging.
`
`[0004] To send and receive electronic messages, electronic
`messaging clients are used. No matter which type of client
`is used, an electronic messaging client generally doesat least
`the following tasks. It showsa list ofall the messages in a
`user’s mailbox by displaying information from message
`headers. The message header information often showsa user
`the address of each person who sent each message,
`the
`subject of each message, the time and date of cach message,
`and the size of each message. The electronic messaging
`client also lets a user select a message header and read the
`body of the electronic message for that message header.
`Further, an electronic messaging client enables a user to
`create new messages and send them. In composing a mes-
`sage, a user typically types in the email address of the
`recipient and the subjectfor the message, and then types the
`body of the message. Additionally, most clients permil a user
`to add attachments to messages that the user sends and to
`also save attachments from the messages the user receives.
`[0005] Specifically, an attachmentis an electronic file that
`can accompany an electronic mail message. The attachment
`can be of any file format, such as word processing docu-
`ments, spreadsheets, sound files, images, and other pieces of
`software. The attachmentis often not text, but binary code.
`Otherwise, the attachment text could simply be added in the
`body of the message by the user creating the message.
`Accordingly, the original binaryfile structure of the attach-
`ment is often converted by an electronic messaging client
`into a file version that only contains text characters so that
`the file may be transmitted over messaging systems that
`utilize the SMTP (simple mail transfer protocol) standard,
`such as the Internet.
`
`(Multipurpose Internet Mail Extension) and Uuencode.
`These encoding mechanisms utilize an algorithm to convert
`a binary file into ASCII code (text), In converting a binary
`file into text, the electronic messaging client delineates the
`beginning and end of the converted file structure with
`boundary markers. Between these boundary markers are
`also a series of headers that define the content of the
`attachment. A typical header clearly identifies the attach-
`mentfile type, original filename, and encoding mechanism
`for the converted binary file. In addition, headers separate
`several individual attachments in an electronic message that
`contains multiple attachments. Also, at the beginning of each
`electronic message, a header indicates the email addresses of
`both the sender and recipient andthe subject of the message.
`[0007] After an electronic mail with an attachment
`is
`received by an electronic messaging client, the electronic
`messaging recognizes the type of attachment encoding and
`converts the attached file back to its binary form. To access
`this binary file, the recipient needs an application installed
`on the recipient’s computer that can execute or access that
`particular typeoffile. Often, in a Windows environment, the
`application that is needed to executethe binary file is already
`associated with the filename extension ofthe binary file, so
`that a user’s command to open the binary file will cause the
`application to access the binary file.
`
`[0008] Generally, electronic messaging clients display and
`manage attachments in the same manner. For example, to
`access an attachment in a received email message, a user
`typically has to know a) that a button or icon needs to be
`selected; b) which particular button or icon hasto be selected
`from a row of numerous buttons/icons; and c) numerous
`other steps involved in opening the attachment file. While
`these traditional methods may be adequate for knowledge-
`able or experienced users of electronic mail clients or
`programs, a more straight forward and less arcane manage-
`ment structure is desired. Thus, a heretofore unaddressed
`need exists in the industry to address the aforementioned
`deficiencies and inadequacies.
`
`SUMMARY OF THE INVENTION
`
`invention
`Preferred embodiments of the present
`[0009]
`provide systems and methods for organizing and managing
`attachments from electronic messages. Briefly described one
`embodiment ofthe system, among others, includes an elec-
`tronic messaging client for receiving electronic messages
`and an attachment management system configured to pre-
`organize default directory locations for saving attachments
`to and also to display descriptive information regarding the
`attachment such as the name, type, andsize.
`[0010] The preferred embodiments of the present inven-
`tion can also be viewed as providing a methodfor organizing
`and managing attachments from electronic messages. In this
`regard, one embodiment of such a method, among others,
`can be broadly summarized by the following steps: preor-
`ganizing a default directory location for storing a particular
`classification of attachments; receiving an electronic mes-
`sage having an attachment; storing the attachment
`in a
`default directory location according to the classification of
`the attachment;
`and displaying descriptive information
`regarding the attachment.
`
`(0006] Two popular encoding mechanisms utilized by
`electronic messaging clients for attachments are MIME
`
`[0011] Other systems, methods, features, and advantages
`of the present invention will be or become apparent to one
`
`16
`
`

`

`US 2004/0068545 Al
`
`Apr. 8, 2004
`
`with skill in the art upon examination of the following
`drawings and detailed description. It is intended that all such
`additional systems, methods, features, and advantages be
`included within this description, and the scope of the present
`invention.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0028] FIG. 16 is a pictorial representation of an attach-
`ment interface of one preferred embodiment of the attach-
`ment management system of FIG, 1.
`
`[0029] FIG. 17 is a pictorial representation of a read
`interface of one preferred embodiment of the attachment
`management system of FIG, 1.
`
`[0012] Many aspects of the invention can be better under-
`stood with reference to the following drawings. The com-
`ponents in the drawings are not necessarily to scale, empha-
`sis instead being placed upon clearly illustrating the
`principles of the present invention. Moreover, in the draw-
`ings, like reference numerals designate corresponding parts
`throughout the several views.
`
`[0013] FIG. 1 is a block diagram of a computer than can
`implement the attachment management system ofone pre-
`ferred embodimentof the present invention.
`[0014] FIG. 2 is a flowchart illustrating the functionality
`of a representative embodiment of the attachment manage-
`ment system of FIG, 1.
`
`[0015] FIG. 3 is a flowchart describing the process of
`adding a file as an attachment as referenced in FIG, 2.
`
`[0016] FIG. 4 is a flowchart describing the process of
`displaying information regarding an attachment as refer-
`enced in FIG, 3.
`
`[0017] FIG. 5 is a flowchart describing the process of
`removing an attachment as referenced in FIG,3.
`
`[0018] FIG, 6 is a flowchart describing the process of
`opening an attachment as referenced in FIG, 3.
`[0019] FIG. 7 is a flowchart describing the functionality
`of a representative embodiment of the attachment manage-
`ment system of FIG.1 for displaying information regarding
`an attachment from an unopened electronic message.
`
`(0020] FIG. 8 is a flowchart describing the functionality
`of a representative embodiment of the attachment manage-
`ment system of FIG. 1 for managing and displaying infor-
`mation regarding an attachment from an electronic message.
`[0021] FIG. 9 is a flowchart describing the process of
`displaying information regarding an attachment in preview
`mode as referenced in FIG, 8.
`
`[0022] FIG. 10 is a flowchart describing the process of
`displaying information regarding an attachment
`in an
`opened electronic message as referenced in FIG.8.
`
`[0023] FIG. 11 is a flowchart describing the process of
`saving an attachment as referenced in FIG. 8
`
`[0024] FIG. 12 is a flowchart describing the process of
`opening an attachment as referenced in FIG. 8.
`
`(0025] FIG. 13 is a pictorial representation of an inbox
`interface for one preferred embodiment of the attachment
`management system of FIG, 1.
`
`[0026] FIG. 14is a pictorial representation of an options
`interface of one preferred embodiment of the attachment
`management system of FIG, 1.
`
`[0027] FIG. 15 is a pictorial representation of a write
`interface of one preferred embodiment of the attachment
`management system of FIG, 1.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`
`[0030] The preferred embodiments of the present inven-
`tion are directed to integrating the functionality of an
`attachment management system into an electronic messag-
`ing client such that the functionality is available to a user
`while the user is reading and writing an electronic message
`on the electronic messaging client. In one preferred embodi-
`ment, an improved system and method is provided for
`managing attachments in electronic messages. Generally
`described, this embodiment employs a graphical user inter-
`face (GUI) architecture to provide the functionality of an
`atlachment management system within an electronic mes-
`saging client. Auser can invokethe attachment management
`system and access the attachment management system func-
`tionality within the context of the electronic messaging
`client user interface. Referring now to the drawings in which
`like numerals represent like elements through out the several
`figures, aspects of preferred embodiments of the present
`invention will be described.
`
`Preferred Environment
`
`[0031] One preferred embodiment of an attachment man-
`agement system of the present
`invention can be imple-
`mented in software, firmware, hardware, or a combination
`thereof. Preferably, the attachment management system is
`implemented in software, as an executable program in
`combination with other program modules, andis executed as
`part of an electronic messaging client by a special or general
`purpose digital computer, such as a personal computer,
`workstation, minicomputer, or mainframe computer. An
`example of a general purpose computer 100 that can imple-
`ment the attachment management system 101 of the pre-
`ferred embodimentofthe present invention is shown in FIG.
`1.
`
`in terms of hardware architecture, as
`(0032] Generally,
`shown in FIG. 1, the computer 100 includes a processor
`102, memory 104, and one or more input and/or output (I/O)
`devices 106 (or peripherals)
`that are communicatively
`coupled via a local interface L08. The local interface 108 can
`be, for example but not limited to, one or more buses orother
`wired or wireless connections, as is known in the art.
`Further,
`the local interface 108 may have additional ele-
`ments, which are omitted for simplicity, such as controllers,
`buffers (caches), drivers, repeaters, and receivers, to enable
`communications. Further, the local
`interface may include
`address, control, and/or data connections 112 to enable
`appropriate communications among the aforementioned
`components.
`
`[0033] The processor 102 may be a hardware device for
`execuling software that can be stored memory 104. The
`processor 102 can be any custom made or commercially
`available processor, a central processing unit (CPU) or
`auxiliary processor among several processors associated
`
`17
`
`

`

`US 2004/0068545 Al
`
`Apr. 8, 2004
`
`with a computer 100, and a semiconductor based micropro-
`cessor (in the form of a microchip) or a macroprocessor.
`[0034] The memory 104 can include any one or combi-
`nation of volatile memory elements (e.g., random access
`memory (RAM, such as DRAM, SRAM, ete.)) and non-
`volatile memory elements (e.g., ROM, hard drive tape,
`CDROM, etc.). Moreover, the memory 104 may incorporate
`electronic, magnetic, optical, and/or other types of storage
`media. Note that the memory 104 can have a distributed
`architecture, where various componentsare situated remote
`from one another, but can be accessed by the processor 102.
`[0035] The software in memory 104 may include one or
`more separate programs each of which comprises an ordered
`listing of executable instructions for implementing logical
`functions. In the example of FIG. 1, the software in memory
`104 includes the attachment management system 101, elec-
`tronic messaging client 115, and an operating system (0/S)
`110. The operating system 110 essentially controls the
`execution of other computer programs, and provides sched-
`uling,
`input-output control,
`file and data management,
`memory management, and communication control and
`related services. The electronic messaging client 115 facili-
`tales the transmission andreception of electronic messages,
`such as email and instant messaging. Preferably, the attach-
`ment management system 101is integrated into or operates
`along with the electronic messaging client 115.
`[0036] The attachment management system 101 may be a
`source program, executable program (object code), script, or
`any entity comprising a set of instructions to be performed.
`If the attachment management system 101 is a source
`program,
`then the program needs to be translated via a
`compiler, assembler, interpreter, or the like, which may or
`may not be included within the memory 104, so as to operate
`properly in connection with the O/S 110. Furthermore, the
`attachment management system 101 can be written as (a) an
`object oriented programming language, which hasclasses of
`data and methods, or (b) a procedure programming lan-
`guage, which hasroutines, subroutines, and/or functions, for
`example but not limited to, C, C++, Pascal, Basic, Fortran,
`Cobal, Perl, Java, and Ada.
`In addition,
`the attachment
`management system 101, in some embodiments, is so inte-
`grated into the electronic messaging client 115 that there are
`not clear lines of separation, as might otherwise be sug-
`gested by the present disclosure.
`[0037] The I/O devices 106 may include input devices, for
`example but not
`limited to, a keyboard, mouse, scanner,
`digital camera, multi-function device, microphone, etc. Fur-
`thermore,
`the I/O devices 106 may also include output
`devices, for example but not limited to, a printer, display,
`etc. Finally, the 1/O devices 106 may further include devices
`that communicate both inputs and outputs, for instance but
`not
`limited to,
`a modulator/demodulator (modem;
`for
`accessing another device, system, or network), a radio
`frequency (RF) or other transceiver, a telephonic interface,
`a bridge, a router, ete.
`[0038]
`If the computer 100 is a PC, workstation, or the
`like, the software in the memory 104 may further include a
`basic input output system (BIOS) (omitted for simplicity).
`The BIOSisa set of essential software routines that initialize
`and test hardware at startup, start the O/S 110, and support
`the transfer of data among the hardware devices. The BIOS
`is stored in ROM sothat the BIOS can be executed when the
`
`computer 100 is activated.
`
`[0039] When the computer L100 is in operation, the pro-
`cessor 102 is configured to execute software stored within
`the memory 104,
`to communicate data to and from the
`memory 104, and to generally control operations of the
`computer 100 pursuant
`to the software. The attachment
`management system LOL,
`the electronic messaging client
`115, and the O/S 110, in whole orin part, but typically the
`latter, are read by the processor 102, perhaps buffered within
`the processor 102, and then executed.
`
`[0040] The computer 100 may operate in a networked
`environment using logical connections to one or more
`remote computers, such as a remote computer 120, The
`remote computer 120 maybe a server, a router, a peer device
`or other common network node, andtypically includes many
`or all of the elements described relative to the computer 100.
`The data connection 112 depicted in FIG. 1 may include a
`dial-up modem, network interface card, DSL modem, etc.
`that provides access to a messaging network 140, such as the
`Internet.
`
`(0041] When the attachment management system 101 and
`electronic messaging client
`ILS are implemented in soft-
`ware, as is shown in FIG. 1,
`it should be noted that the
`attachment management system 101 can be stored on any
`computer readable medium for use by or in connection with
`any computer related system or method. In the context of
`this document, a computer readable medium is anelectronic,
`magnetic, optical, or other physical device or meansthat can
`contain or store a computer program for use by or in
`connection with a computer related system or method. The
`attachment management system 101 can be embodied in any
`computer-readable medium for use by or in connection with
`an instruction execution system, apparatus, or device, such
`as a computer-based system, processor-containing system,
`or other system that can fetch the instructions from the
`instruction execution system, apparatus, or device and
`execute the instructions.
`
`In the context of this document, a “computer-
`[0042]
`readable medium” can be any means that can store, com-
`municate, propagate, or transport the program for use by or
`in connection with the instruction execution system, appa-
`ratus, or device. The computer readable medium can be, for
`example but not limitedto, an electronic, magnetic, optical,
`electromagnetic, infrared, or semiconductor system, appa-
`ratus, device, or propagation medium. More specific
`examples (a nonexhaustive list) of the computer-readable
`medium would include the following: an electrical connec-
`tion (electronic) having one or more wires, a portable
`computer diskette (magnetic), a random access memory
`(RAM) (electronic), a
`read-only memory (ROM) (elec-
`tronic), an erasable programmable read-only memory
`(EPROM, EEPROM, or Flash memory) (electronic), an
`optical fiber (optical), and a portable compactdise read-only
`memory (CDROM) (optical). Note that the computer-read-
`able medium could even be paper or another suitable
`medium upon which the program is printed, as the program
`can be electronically captured, via for
`instance optical
`scanning of the paper or other medium,
`then compiled,
`interpreted or otherwise processed in a suitable manner if
`necessary, and then stored in a computer memory.
`
`In an alternative embodiment, where the attach-
`[0043]
`ment management system LOL is implemented in hardware,
`the attachment management system 101 can be implemented
`
`18
`
`

`

`US 2004/0068545 Al
`
`Apr. 8, 2004
`
`with any combination of the following technologies, which
`are cach well known in the art: a discrete logic circuit(s)
`having logic gates for implementing logic functions upon
`data signals,
`an application specific integrated circuit
`(ASIC) having appropriate combinational
`logic gates, a
`programmable gate array(s) (PGA), a field programmable
`gate array (FPGA),etc.
`
`described in greater detail. In block 310, a user is prompted
`to specify the default attachment directory location for
`different categories of files. For example,
`the user may
`specify different attachment default directories for different
`classifications offiles such as “sound” files, “image”files, or
`“general” files. A general file, as the name suggests, is a
`general category offiles that do not fit into another type.
`
`Preferred Operation
`
`[0044] The overall operation of the attachment manage-
`ment system LOL will be described with reference to FIG, 2
`which depicts the functionality of one preferred embodiment
`ofthe attachment management system 101. It should also be
`noted that in somealternative implementations the functions
`noted in the various blocks may occur out of the order
`depicted in the flowcharts of FIG. 2 and subsequent flow-
`charts. For example, two blocks shown in succession in a
`flowchart may,
`in fact, be executed substantially concur-
`rently. Alternatively, the blocks may sometimes be executed
`in the reverse order depending upon the functionality
`involved.
`
`the functionality of one
`[0045] As depicted in FIG. 2,
`preferred embodiment ofthe attachment managing system
`LOL or method 200 for adding an attachment to an electronic
`message may be construed as beginning at block 210. In
`block 210, a user is prompted to preconfigure a default
`attachment directory. The default attachment directory is
`intended to be the directory where files that are to be added
`as attachments are stored. Accordingly, a user is prompted to
`provide a customized directory name and the associated
`directory path for this location.
`[0046]
`Ifthe user provides a customizedattachment direc-
`tory location, as shownin blocks 212-214, then the custom-
`ized attachment directory name is set as the default direc-
`tory. For example, a user may specify that his or her
`customized file directory, “My Files for Attachments,”
`should be set as the default attachment directory on the C:
`drive ofhis or her computer, or some other storage medium.
`If the customized directory location does not exist, it will be
`created forthe user. Alternatively, if the attachment directory
`location is not provided by a user, then a predefined file
`directory location is set as the default directory, as shown in
`block 216. For example, a standard directory named “My
`Attachments” located at C:\Attachments may be assigned as
`the default attachment directory settings for any user that
`does not specify a custom directory location. Generally, a
`user is also afforded the opportunity to reconfigure the
`default directory locations at a later time by utilizing an
`“option” window on a GUI of the attachment management
`system 101.
`
`[0049] As depicted in block 320, the attachment manage-
`ment system 101 contemplates that a user may fail
`to
`provide his or her own default location. Accordingly,
`in
`block 330, if the user does not provide a particular default
`attachment directory location for a file classification, then a
`predefined location is set as the default attachment directory
`location for that file category or classification. Again, how-
`ever, as shown in block 340, if the user does designate a
`customized directory location for an attachment file cat-
`egory, then that customized location Is set as the attachment
`directory default location for that file category. For example,
`a user may choose to retrieve sound files from a directory
`named “My Sounds” where the userstoreshis or her favorite
`sound files. If this specified directory location has not yet
`been created, it will be created after it has been set as the
`default location.
`
`{0050] Next in block 350, the user initiates a command,
`typically via a GUI, to add a file as an attachment to an
`electronic messagethat the user is composing. Typically, the
`user composes the electronic message on an electronic
`messaging client, such as Microsoft Outlook, Eudora, or an
`electronic messaging client provided by the user’s ISP.
`Alternatively, the electronic messaging client may comprise
`an instant messaging client or some other electronic mes-
`saging system. In composing the message, a user typically
`has an electronic document open in a “Write” window upon
`which the user may type or enter a textual message into the
`body of the document. Users typically