||||||||||||||l||||||||||||||||||||||||||||||||||||||||||||||||||||||||l||||||||||||||||||
`
`US 2(H)4(X)68545A1
`
`(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2004/0068545 A1
`
` Danicll ct al. (43) Pub. Date: Apr. 8, 2004
`
`
`(54) DISPLAYING AND WORKING WITH EMAIL
`ATTACHMENTS
`
`Related U.S. Application Data
`
`(75)
`
`Inventors: W. Todd Daniell, Marietta, GA (US);
`Mar}.r S. Amoff, Lawrcnccvillc, GA
`(US); Dale W. Malik. Dunwoudy. GA
`(US)
`
`Corrcslmndcncc Address:
`THOMAS, KAYIWIN, HORSTEMEYI‘ZR 8:
`RISLEY, LLP
`100 GALLERLA PARKWAY, NW
`STE 1750
`ATLANTA, GA 303396948 (Us)
`'
`(73) Aggjgnw: Bensnmh Intellectual pmpefly Col-p0-
`mtmn,wj]mingmn‘ DE
`
`(21) Appl, Nu;
`
`10,326,250
`
`(22)
`
`Filed:
`
`Dec. 19, 2002
`
`(60)
`
`Provisional application No. 6(J_.-"4]6,916, filed on Oct.
`8, 2002. Provisional application No. 60X426,422, Iliad
`on Nov. 14. 3002.
`
`Publication Classification
`
`“’61? [5116
`II“. CL? ................................................... ..
`(5])
`(52) U.S. C].
`............................................................ .. 709,806
`
`ABSTRACT
`
`(57)
`_
`A
`_
`I
`‘
`IDVUUIIUI‘I provulu
`Prcicrrcd cmbodimcnls of the present
`syslcms and mclhods for organizing and managing allach-
`merits from electronic messages. Om: cmhodirncnl of [he
`system, among others,
`includes an clcclronic messaging
`ciicnl For receiving electronic messages and art allachmcnt
`management system configured to prcorganizc default direc—
`tory locations for saving altachmcnls inlo [hose diructory
`locations and aiso to display descriptive information regard—
`ing attachments such as namc, type, and size. Other syslcms
`and mclhuds are also provided.
`
`
`
`MEMORY
`
`m
`ATTACHMENT
`MANAGEMENT
`SYSTEM
`
`
`
`
`
`
`
`IUO\
`
`PROCESSOR
`
`
`
`
`
`
`fl
`ELECTRONIC
`
`fl
`
`MSG. SYSTEM
`[15
`
`OPERATING
`SYSTEM
`
`{DIS}
`fl
`
`
`
` LOCAL INTERFACE g
`
`DATA
`CONNECTION
`
`E
`
`
`@
`
`REMOTE
`COMPUTER
`
`INPU‘l‘iOUTPUT
`
`DEVICE(S)
`
`(no;
`I_(J6
`
`
`
`1
`1
`
`Facebook Ex. 1010
`Facebook EX. 1010
`U.S. Pat. 7,535,890
`U.S. Pat. 7,535,890
`
`

`

`
`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 1 0f 14
`
`US 2004/0068545 A1
`
`502mm
`
`«$228
`
`a”.
`
`ydOEm—E
`
`SJ
`
`.er—EIU<HH<
`
`.u,ZmEmO<Z<E
`
`Emdiwhm
`
`::
`
`2:35me
`
`
`
` Ozfiémmoa355$.82
`
`Emhm‘rm
`
`a$8
`
`
`
`amguamte#03
`
`$3
`
`azo_.u.umzzoo
`
`SPSQSQE
`
`8505.5
`
`a53
`
`fi.05
`
`fan:
`
`mommmuoE
`
`m3
`
`2
`
`
`
`
`
`
`
`
`
`

`

`D.AtnBta)1
`
`n.mta.E.ID.HPn0.ha.EID.
`
`Apr. 8, 2004 Sheet 2 0f 14
`
`US 2004/0068545 A1
`
`
`
`
`
` %>MOHUm—M55:32me20M.”—
`
`
`
`
`
`oomli‘
`
`
`
`OHMum:r520)?—
`
`
`
`HAD<meHMDOEZOUm—Mm.
`
`
`
`OZEarmmFxOFOmEE
`
`3m
`
`EoBmmEBECEWfigEmamazommmmmmm:
`
`$0.6qu525mm3.N:
`
`
`
`aI
`
`
`
`quHUm‘m—mOHammbHmEOMm
`
`
`
`Z<m<mgr“Sprawl—MmQflfi
`
` %HZmEIU/mtxw
`
`
`
`m<M/MOHUm—daDmZEmDmmmHum
`
`
`
`>MOFU§EbuDaimD
`
`cl:
`
`
`
`Z<90¢OHQZ<EEOUmam—0mm
`
`thEIU<bH¢
`
`mmlm
`
`3
`
`N.U—m
`
`
`
`
`
`
`
`
`

`

`
`
`Patent Application Publication
`
`r.pA
`
`US 2004/0068545 A1
`
`
`
` a$89:tam:on
`
`
`
` %wagon“.$329“
`
`
`
`
`
`m—MDOEZOUOPm.me.EEOxm
`
`
`
`
`
`mOZELEm>mOPUmEGbagging
`
`
`
`
`
`mE>H>¢OOmP<UIU<mMO“—
`
`elm
`
`m.Uuh
`
`
`
`20%3:83mm
`
`
`
`20563$50qu
`
`mm
`
`:9:E;Sada
`
`w9:3me
`
`a
`
`
`
`mdn—hum—4mm.OHMum:rpm—20m;
`
`._.~5<mem0mZO30M”—
`
`
`
`wZOC.<UOJarmor—.Umda
`
`com
`
`ZO_H<EMO...~Z_
`
`
`
`Oman?OZ.Q¢<Om—M
`
`><-Em.fla
`
`
`
`ZO~H<UOAWMOHUMEDfl
`
`
`
`M._.zm2mo<t<
`
`_
`
`
`
` .mz<an?903.228mamumxMClem-.mezmzmu<t<Qm5294.S8m429:03
`Hszmu<fi<$053.593.2053Em$055.5mmBeams320:334cm,
`
`
`
`
`
`4
`
`wag—baaDMZ—«Emma;[rm—m
`
`
`
`
`b43<mmnm<20:dequwaZOmmmEMmmD
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 4 0f 14
`
`US 2004/0068545 A]
`
`><1Em5
`
`
`
`
`
`zQZEmEEEVde5.4.2:
`
`
`
` §53455?ozagoma
`
`m.05
`
`w.0?—
`
`.aezmzzu<fi<z<m>oEmm
`
`ohoz<EEoo<mamomm
`
`
`
`mfiaufimfi53mm
`
`aP2m25<t<
`
`
`
`Dmkomdmm920me
`
`EZMEIU<HH<
`
`0mm
`
`
`
`
`
`QZ<.m;>.~.£352mzh
`
`aHZmEIU<t<m:.:.LOmNE
`
`
`
`mIHLOme‘EFOEmils>¢Amm~fl
`
`mHZmExU<E<
`
`mm.
`
`5
`
`

`

`
`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 5 0f 14
`
`002SU
`
`1A5458(00m,
`
`oamll.‘
`
`
`
`
`
`025quMmhmfim0<mmm2
`
`ZOFQUEmm‘q‘
`
`96
`
`
`
`
`
`ZO_P<EMO.H~Z_><1EmamELdtnEp
`
`mmlo
`
`w.0?—
`
`
`
`rerEEU<FH<OZEvaOm—m
`
`220OFozfiazou¢mzmumm
`
`HZmzzu<t.<z<
`
`ma
`
`$52053USN;
`
`Emzmu<t<
`
`mm
`
`
`
`m<qDogm<mZMEO
`
`<5FZmEEUxxtd
`
`
`
` aZOE<UELm<mFZmEEU<HH<
`
`OEmOmEOUOhZmDHmE
`
`6
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 6 0f 14
`
`US 2004/0068545 A1
`
`
`
`
`
`ES»0255:5&3::éflo
`
`
`
` amESEE95:55:
`
`b.0:—
`
`aonll‘
`
`
`
`UHZOmHUmAm02—5007:Z<mamomm
`
`
`
`Z<OZEEHZOUm0<mmm=2
`
`thEIU<ti
`
`oIn
`
`Mime/52MIRMasha—Q
`
`ZHmh.ZmEIU{t<m0
`
`
`
` a30025.»Ragga
`
`
`
` aEco:amSmE
`
`7
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 7 0f 14
`
`US 2004/0068545 A1
`
`FZmEIQfiE2mg
`
`Wow
`
`
`
`m0;mozrfimmfichméfiH5,“me
`
`
`
`
`
`
`
`mmzoazoumfi09$3220%
`
`
`
`OZDm<OmEZO_._.<EMOH_Z_><1EW_D
`
`
`
`
`
`mEHOZaZmLOH3025?PZMEEU<E<
`
`m0<mmm2
`
`cow
`
`w.0:
`
`
`
`
`
`
`
`m0<mmm2EZOEPUm—qm$5ng
`
`mm
`
`
`
`HZMEIU<E<mZOHm<m3Hf.OZEEPZOU
`
`
`
` amoémmfiEEO
`
`
`
`>MOHUMEDhqadflmflmdZOF<UOA
`
`.new.
`
`203k.on—
`
`
`
`
`
`FmOHUmEDQmE-UmmmmmmDHmm
`
`
`
` %Emzznzgam><m
`
`
`
`ydOhUm—d—DDmZEQO—dn—Hum
`
`
`
`ZOEI<UOAVEOHUmF—Eomm
`
`
`
`Pg3<mmflm<205k.qu«mmZOmmmm
`
`aI
`
`8
`
`
`
`
`
`zo_._.<u_..=mm5u.z_<Emu<noEmixu<5<z<_925%
`
`a;_
`
`
`
`
`
`
`
`
`
`
`

`

`
`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 8 0f 14
`
`US 2004/0068545 A]
`
`
`
`
`
`DZ<mat.F3234at.Emu—QED
`
`
`
`‘232357:IU<mLOmum—m
`
`m0¢mmm27:PZMEEU<E<
`
`cm:
`
`yam—$52mrhwcfimmflfl
`
`2—mEZmEIU<t<n5
`
`
`
`3825?amt/mam
`
`mg
`
`3.0;
`
`a.05.“
`
`
`
`
`
`
`
`m—EH20m...—QZ<EEOUmZmUmE
`
`
`
`
`
`M<ADDHHM<L<D<mflOHMmmb
`
`
`
`m0<mmm2UHZomHUm—qm
`
`
`
`
`
`m0<wmm2U_ZOMPUmAmZmEO
`
`
`
`
`
`$283:mofimmz<31:55
`
`
`
`«2552.EmEmu<t<2:;
`
`a.
`
`
`
`mmofi:mogmmz.<55%
`
`a.
`
`DZ
`
`
`
`58.:5:65
`
`9
`
`
`
`
`
`

`

`
`
`
`
` 2__.Em25<,£<misufifi<m><mE.oz<228mamumm
`
`
`
`
`VMOHUWEQ
`
`
`
`H15<mmfl<.Cq.31:“.m><mOh.Emmb.EEOML
`
`
`
`
`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 9 0f 14
`
`US 2004/0068545 A1
`
`
`
`
`
`ZmEOOh.QZ<EEOUmam—0mm
`
`HZmEEU<E<Z<
`
`SN—
`
`om:
`
`
`
`
`
`
`
`072m:PZMEEU¢E¢ZmEO
`
`ommw
`
`
`
`ZOEEUEAEJQQmF<UOmw¢
`
`
`
`02¢FZm—EEOfir—LHawmquO
`
`OH723,5202¢ZOP<UEAE<
`
`
`
`OZ~O<mmm§BZOflhUm—Am
`
`aHZWEU
`
`NH.Umh
`
`
`
`
`
`202E004>MOHUm$=Qmam—0mm
`
`
`
`m‘:2HHZmEEU<hH<mEOHm
`
`
`
`m5.P<F<SEOLm>:.<Z
`
`ZOF<UOA
`
`ow:
`
`noEnigmaOhZMDHmE
`
`EZOMHUMJQLOthm—HZOU
`
`Oma_m0<mmm2
`
`:..0:—
`
`_
`
`
`
` c2_MMwDEOME
`
`10
`10
`
`
`
`
`
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 10 of 14
`
`US 2004/0068545 A]
`
`MESSAGE CENTER
`
`
`CURLY'S INBOX
`
`
`SUBJECT
`- FROM
`LUNCH
`- HANCOCK JOHN
`
`
`A R085. BETSY
`
`OK?
`
`
`
`an; mm
`
`REMINDER
`
`I
`
`DATE
`WED 2:13:1976
`
`E
`
`3A1'FACHMENTS
`
`E] Ii
`
`FROM: JOHN ADAMS TO: CURLY@STOOGES‘TRI
`SUBJECT: BIG IDEAS
`
`PLEASE REVIEW MY THREE PROPOSALS AND THEN WE‘LL TALK.
`
`PREVIEW
`WINDOW
`
`FIG. 13
`
`11
`11
`
`

`

`Patent Application Publication
`
`MAIL OPTIONS ‘
`
`Apr. 8, 2004 Sheet 11 0f 14
`
`US 2004/0068545 A1
`
`
`
`THE MESSAGE CENTER W’ILL AUTOMATICALLY CHECK FOR NEW MAIL THROUGHOUT THE
`DAY AS LONG AS YOUR COMPUTER IS TURNED ON AND CONNECTED TO A PHONE LINE
`
`ALWAYS CHECK FOR NEW EMAIL WHENEVER | START UP THE MESSAGE CENTER
`
`[3 YES. AUTO CHECK FOR NEW MAIL
`NO. DO NOT AUTO CHECK.
`I WILL USE THE “GET MAIL" BUTTON TO CHECK FOR NEW
`MAIL
`'
`
`INDICATE YOUR CONNECTION TYPE:
`
`DIAL Access
`
`SPECIFY DEFAULT LOCATIONS TO SAVE ATTACHMENTS
`
`CilF’ROGRAM FILESIMESSAGE CENTERIS
`
`
`
`FILES
`
`C:I‘PROGRAM FILESI'MESSAGE CENTERIIF
`
`I
`
`BROWSE
`
`PICTURES
`
`CiiPROGRAM FILESI'MESSAGE CENTERI'P
`
`SOUNDS
`
`PRECONFIGURE
`DEFAULT
`LOCATIONS
`
`FIG. 14
`
`12
`12
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 12 0f 14
`
`US 2004/0068545 A]
`
`l7
`
`FROM: CURLY@STOOGES.TRI
`
`TO:1—.—_I I'
`
`USE A COMMA TO SEPARATE MULTIPLE ADDRESSES
`
`60: IS
`
`SUBJECT:
`
`
`
`TYPE YOUR MESSAGE HERE.
`
`ATTACHMENTS
`
`I
`
`WE “El @
`
`
`ATTACHMENTS
`
`FIG. 15
`
`13
`13
`
`— A
`
`DD OR REMOVE
`
`'
`
`

`

`
`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 13 of 14
`
`US 2004/0068545 A1
`
`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 ATTACHIREMOVE A FILE BY DRAGGING IT FROM YOUR DESKTOP AND
`DROPPING IT INTO THE ATTACHMENT BOX BELOW.
`
`|
`
`ADD FILES
`
`C:\MY DOCUMENTSH
`
`| PICTURS _
`
`C:\MY PICTUREST
`
`'
`
`| ADD SOUDS _
`
`C:\MY SOUNDS\
`
`|g
`
`I
`
`ATTACHMENT BOX
`
`SIRENWAV
`
`(33 kB)
`
`TO REMOVE AN A'I'I'ACHMENT, SELECT THE ATTACHMENT ABOVE AND CLICK REMOVE
`
`FIG. 16
`
`14
`14
`
`
`
`

`

`Patent Application Publication
`
`Apr. 8, 2004 Sheet 14 of 14
`
`US 2004/0068545 A]
`
`PLEASE REWEW MY THREE PROPOSALS AND THEN WE'LL TALK.
`
`OK?
`
`- - JOHN
`
`DATE: FEBRUARY 8, 1976
`FROM: ADAMS, JOHN
`T0: HOWARD, CURLY
`CC:
`SUBJECT: BIG IDEAS
`
`
`ADOBE ACROBAT DOCUMENT
`
`SAVE FILE
`|
`YOU HAVE 3 FILE(S) ATTACHED.
`
`
`OPEN FILE
`
`g;
`
`
`
`PROPOSAU .DOC
`
`WORD FILE
`
`PROPOSALZZIP
`
`PROPOSALS‘PDF
`
`WINZIF' F|L_E
`
`FIG. 17
`
`15
`15
`
`

`

`
`
`US 2004/0068545 A1
`
`DISPLAYING AND WORKING WITH EMAIL
`ATTACHMENTS
`
`C ROSS-REFERENC E TO RELATED
`APPLICATIONS
`
`[0001] This application claims priority to copending US.
`provisional applications entitled, "FUNCTIONAL SPECI-
`FICATION FOR E-MAII. CLIENT," having Serial No.
`60,1416316, filed Oct. 8, 2002, which is entirely incorpo-
`rated herein by reference;
`and "DISPLAYING AND
`WORKING WITH EMAIL ATTACHMENTS," having
`serial No. 6(II426,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 does at least
`the following tasks. It shows a list of all the messages in a
`user’s mailbox by displaying information from message
`headers. The message header information often shows a user
`the address of each person who sent each message,
`the
`subject of each message, the time and date of each 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.
`Funher, 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 subject for the message, and then types the
`body of the message. Additionally, most clients permit a user
`to add attachmean to messages that the user sends and to
`also save attachments from the messages the user receives.
`
`[0005] Specifically, an attachment is 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 attachment is 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 binary file 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 SM'I‘I:l (simple mail transfer protocol) standard,
`such as the Internet.
`
`[0006] Two popular encoding mechanisms utilized by
`electronic messaging clients for attachments are MIME
`
`16
`16
`
`Apr. 8, 2004
`
`(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. Atypical header clearly identifies the attach-
`ment file 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 and the subject of the message.
`
`is
`[0007] After an electronic mail with an attachment
`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 type of file. Often, in a Windows environment, the
`application that is needed to execute the binary file is already
`associated with the {ilenamc extension of the binary lile, 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 has to be selected
`from a row of numerous buttonsiicons; 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. Tbus, a heretofore unaddressed
`need exists in the industry to address the aforementioned
`deficiencies and inadequacies.
`
`of the present invention will be or become apparent to one
`
`SUMMARY OF THE INVEN'I‘ION
`
`invention
`Preferred embodiments of the present
`[0009]
`provide systems and methods for organizing and managing
`attachments from electronic messages. Briefly described one
`embodiment ol. the system, among others, includes an elec-
`tronic messaging client [or 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, and size.
`
`[0010] The preferred embodiments of the present inven-
`tion can also be viewed as providing a method for 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.
`
`[0011] Other systems, methods, features, and advantages
`
`

`

`
`
`US 2004/0068545 A1
`
`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 thisdescription, and the scope of the present
`invention.
`
`BRIEF DESCRIPTION OF T1111 DRAWINGS
`
`[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. I is a block diagram of a computer than can
`implement the attachment management system of one pre-
`ferred embodiment of 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 llowchart 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 llowehart 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-
`menl system of FIG. 1 for displaying information regarding
`an attachment from an unopened electronic message.
`
`[0020] FIG. 8 is a flowchart describing the functionality
`ofa 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 de5cribing 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. I.
`
`[0026] FIG. 14 is a pictorial representation of an options
`interface of one preferred embodiment of the attachment
`management system of FIG. I.
`
`[0027] FIG. 15 is a pictorial representation of a write
`interface of one preferred embodiment of the attachment
`management system of FIG. I.
`
`17
`17
`
`Apr. 8, 2004
`
`[0028] FIG. 16 is a pictorial representation of an attach»
`ment interface of one preferred embodiment of the attach-
`ment management system of FIG. I.
`
`read
`[0029] FIG. 17 is a pictorial representation of a
`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
`attachment management system within an electronic mes-
`saging client. Auser can invoke the 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.
`
`auxiliary processor among several processors associated
`
`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, and is 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 ofa general purpose computer 100 that can imple—
`ment the attachment management system 101 of the pre-
`ferred embodiment of the present invention is shown in FIG.
`I.
`
`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 andi’or output (HO)
`devices 106 (or peripherals)
`that are communicativer
`coupled via a local interface 108. The local interface 108 can
`be, for example but not limited to, one or more buses or other
`wired or wireless connections, as is known in the art.
`Further,
`the local interface 108 may have additional elew
`merits, 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, andfor data connections 112 to enable
`appropriate communications among the aforementioned
`components.
`
`[0033] The processor 102 may be a hardware device for
`executing 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
`
`

`

`
`
`US 2004/0068545 A1
`
`LA
`
`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, etc.)) and non—
`volatile memory elements (e.g., ROM, hard drive tape,
`CDROM, etc.). Moreover, the memory 104 may incorporate
`electronic, magnetic, optical, andi’or other types of storage
`media. Note that the memory 104 can have a distributed
`architecture, where various components. are 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 ofwhich 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’8)
`110. The operating system 110 essentially controls the
`execution of other computer programs, and provides sched—
`tiling,
`input-output control,
`file and data management,
`memory management, and communication control and
`related services. The electronic messaging client 115 facili-
`tates the transmission and reception of electronic messages,
`such as email and instant messaging. Preferably, the attach-
`ment management system 101 is 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 DIS 110. Furthermore, the
`attachment management system 101 can be written as (a) an
`object oriented programming language, which has classes of
`data and methods, or (b) a procedure programming lan-
`guage, which has routines, subroutines, andi’or functions, for
`example but not limited to, C. C++, Pascal, Basic, Fortran,
`Cobal,
`l’erl, 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 sugv
`gested by the present disclosure.
`[0037] The HO devices 106 may include input devices, for
`example but not
`limited to, a keyboard, mouse, scanner,
`digital camera, multi-furtction device, microphone, etc. Fur-
`thermore,
`the liO devices 106 may also include output
`devices, for example but not limited to, a printer, display,
`etc. Finally, the “0 devices 106 may further include devices
`that communicate both inputs and outputs, for instance but
`not
`limited to,
`a modulatori’demodulator
`(modem;
`for
`accessing another device, system, or network}, a radio
`frequency (RF) or other transceiver, a telephonic interface,
`a bridge. a router, etc.
`[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 BIOS is a set of essential software routines that initialize
`and test hardware at startup, start the DIS 110, and support
`the transfer of data among the hardware devices. The BIOS
`is stored in ROM so that the BIOS can be executed when the
`
`computer 100 is activated.
`
`18
`18
`
`Apr. 8, 2004
`
`[0039] When the computer 100 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 101,
`the electronic messaging client
`115, and the DIS 110, in whole or in 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 may be a server, a router, a peer device
`or other common network node, and typically includes many
`or all ofthe 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.
`
`the attachment management system 101 can be implemented
`
`[0041] When the attachment management system 101 and
`electronic messaging client 1.15 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 an electronic,
`magnetic, opt ical, or other physical device or means that can
`contain or store a computer program for use by or in
`connection with a computer related system or method. 'lhe
`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 computervbascd 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-
`mu nicate, 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 limited to, an electronic, magnetic, optical,
`electromagnetic, infrared, or semiconductor system, appa-
`ratus, device, or propagation medium. More specilic
`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 compact disc 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 101 is implemented in hardware,
`
`

`

`
`
`US 2004/0068545 A1
`
`with any combination of the following technologies, which
`are each 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 arrayts} (I’GA), a field programmable
`gate array (FPGA), etc.
`
`Preferred Operation
`
`[0044] The overall operation of the attachment manage—
`ment system 101 will be described with reference to FIG. 2
`which depicts the functionality of one preferred embodiment
`ot‘thc attachment management system 101. It should also be
`noted that in some alternative implementations the functions
`noted in the various blocks may occur but of the order
`depicted in the tIowcharts 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 of the attachment managing system
`101 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.
`
`If the user provides a customized attachment direcv
`[0046]
`tory location, as shown in 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 lile directory. "My Files for Attachments,"
`should be SCI as the default attachment directory on the C:
`drive of his or her computer, or some other storage medium.
`If the customized directory location does not exist, it will be
`created for the 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 lecation. 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.
`
`[0047] Next in block 220, a command is received from a
`user, typically via a GUI, to add a file as an attachment to an
`electronic message that
`the user is composing. Once the
`command is received, the user is prompted to select a file
`contained in the default directory location, as depicted in
`block 230. For example, the electronic messaging client may
`open a Windows Explorer file browser at the default direc—
`tory location for the user to select file(s) to attach to an email
`message. In block 240,
`the selected file is added as an
`attachment to the electronic message.
`
`[0048] Referring to FIG. 3, one embodiment of the attach-
`ment management system 101 for adding an attachment is
`
`19
`19
`
`Apr. 8, 2004
`
`described in greater detail. In block 310, a user is prompted
`to specify the default attachment directory location for
`difierent categories of files. For example.
`the user may
`specify different attachment default directories for different
`classifications of files such as "sound" files, “image” files, or
`"general" files. A general file, as the name suggests, is a
`general category of files that do not fit into another type.
`
`[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 user stores his 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.
`
`block 370, the file is added as an attachment to the electronic
`
`[0050] Next in block 350, the user initiates