I|||||||||||||ll|||||||||||||||||||||||||||||||||||||||||||||||||||||||l||||||||||||||||||
`
`US 2{l{)40tl685-'-1-5A1
`
`(19) United States
`(12) Patent Application PllbliCflti0Il
`Danicll ct al.
`
`(10) Pub. No.: US 2004/0068545 A1
`(43) Pub. Date:
`Apr. 8, 2004
`
`(54)
`
`l)ISPI.AYlN(} AND VVORKING W['1'H EM/“I.
`ATTACHMENTS
`
`Related U.S.Applic:1tinn Data
`
`(75)
`
`Inventors: W. Todd Daniell, Marietta, GA (US);
`Mary S. Arnoff, Iawrenceville, GA
`(US); Dale W. Malik. Dunwoody. (3/\
`(US)
`
`Correspondence Address:
`TH()M/\S, KAYDHN, H()RS'[‘EMl'CYl€R S:
`RISLEY, LLP
`100 GALLERLA PARKWAY, NW
`STE 1750
`ATLAN1-A’ GA 303396948 (US)
`
`(73) Amjgnw: 1ge[]S"mh [me||,_.ctu,_.] pmpe,-;_v Cm-P0-
`fa-[["n,yVj]ming[0n‘ DE
`
`(21) Appl, N(_}_;
`
`10,326,250
`
`(22)
`
`l"iIe(l:
`
`Dec. 19, 2002
`
`(60)
`
`Provisional application No. 6(J_.-"4]6,9l6, filed on Oct.
`8, 2002. l’rovi.~:.ional application No. 6UX426,422, llletl
`on Nov. 14. 2002.
`
`I'ul)Iication Classification
`
`IIII. (31.7 ................................................... .. G951? 15.116
`(51)
`(52) U.S. C].
`............................................................ .. 709.906
`
`ABSTRACT
`
`(57)
`_
`‘
`_
`1
`‘
`ll'l\-"l.!l‘lIlUI‘l provtde
`Preierred embodiments of the present
`systems and methods for organizing and managing attach-
`ments from electronic messages. One embodiment of the
`system, among others,
`includes an electronic niessaging
`client For receiving electronic messages and an attachment
`management system configured to preorganize default direc-
`tory lot:ati0ns for saving attaehntents into those directory
`locations and also to display descriptive intormation regarr|—
`irtg attachments such as name, type, and size. Other systems
`and methods are also provided.
`
`
` MEMORY
`
`E
`ATTACHMENT
`
`MANAGEMENT
`S YSTEM
`
`
`lU0\
`
`PROCESSOR
`
`E
`
`MSG. SYSTEM
`ll5
`
`OPERATING
`SYSTEM
`
`{ms}
`E
`
`
`
` LOCAL INTERFACE Q
`
`DATA
`CONNECTION
`
`E
`
`
`E
`
`REMOTE
`COMPUTER
`
`INPUTIOUTPUT
`
`DEVlCE(S)
`
`(no)
`E
`
`
`
`1
`‘
`
`Apple 1010
`Apple 1010
`U.S. Pat. 7,535,890
`U.S. Pat. 7,535,890
`
`
`
`E
`ELECTRONIC
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 1 of 14
`
`US 2004/0068545 A1
`
`Eozmm
`
`mm.5._:ou
`
`mm
`
`
`
`amufamezwd..Go._
`
`<55
`
`3zofiumzzou
`
`S._.5o¢:,_z_
`
`@mu_>.u5
`
`§5.:
`
`_.03
`
`.:,m_E:u<E<a5_o2.n=>_.
`
`._.z...__2mo<z<2
`
`:m.$>m
`
`as.
`
`2zoEbm._m
`
`ozE§EoHzmpmrmcm:
`
`Em_m>m
`
`3Q8
`
`/8_
`
`mommmoofi
`
`mm
`
`2
`
`
`
`
`
`
`
`
`

`
`D.AtnBtaP
`
`n.mta.EMuPn0....ua.mM.
`
`Apr. 8,2004 Sheet 2 of 14
`
`US 2004/0068545 A1
`
`
`
`
`
`ms:CmqmmOHmum:E205
`
`
`
`
`
` %ioeumfio[S2559EOME
`
`N.U_.m
`
`Salk
`
`
`
`OHmum:.5205.
`
`
`
`._.AD<m.mQmazoazoumya.
`
`
`
` 3ozfiemmwxoeomfio
`
`wmoeomfiaomr__ouna.~Em:Emomozonammmum:
`
`>mo._bmmE5253m4.EN
`
`
`
`3l
`
`
`
`7?».3Baomeumqmm02¢.
`
`HZmEIU€.b._.<
`
`ova
`
`
`
`m<%MOr~.Um.~:DamzamamyzEm
`
`
`
`>mE.um_...:m_n5Ema
`
`Em
`
`
`
`z<9:.ohozflzzoomamumm
`
`pzm2:u<.E¢
`
`mm
`
`3
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 3 of 14
`
`US 2004/0068545 A1
`
`
`
` ammmuofitnmxzmao
`
`
`
` %mmmuofi._<>o:mm
`
`
`
`>mO._bm.~=Qomz_..m5m:EEm
`
`
`
`._.u_afimam<ZOEEUOA
`
`
`
`ZOC.<UO.._wmoeommfi
`
`
`
`wmozommmxmmm:
`
`fl
`
`mm
`
`
`
`
`
`mac?5_oom_~<u:u<mmom
`
`
`
`NMDOEZOUOHmum:E295
`
`
`
`
`
`muz_.E.m__m>mo&H.:__o._.._rJ<umQ
`
`m.UHm
`
`
`
`29:mg:Bmqmm
`
`
`
`zoE...oow_~m=¢oz<
`
`mm
`
`20%,.3;53mm
`
`WE.5Emm
`
`,:,m_2mu<E<m<mi994.
`
`elem-.
`
`
`
`ZOC.<UO..h>mo5mEo
`
`SA
`
`
`
`z<an?opoz<_2Eoum>Eu.n:_
`
`Q_.zmsEo<C<
`
`
`
`5:..um._mmOHmum:._a=./_OmE
`
`-_.._D<.._mQmomzoEOME
`
`
`
`wZO:.<UO4>.mO._.Um~:Q
`
`Sm
`
`zo:.<2m8z_
`
`
`
`am.Qn<oz_Qm<omE
`
`><._._mEfl
`
`
`
`HZmEEU<.E.<S_o5$__oommzzoemaoEm
`
`mm.|m.SD<..._mDm<ZO_._.<UO..
`
`4
`
`
`
`
`
`
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 4 of 14
`
`US 2004/0068545 A]
`
`
`
`
`
`ZO_._.<_2MO..._Z_><.amEm§<o.S
`
`
`
` §HZm=>:._U<.E.<OZ_Dm<OmE
`
`m.05
`
`w.02
`
`.ad
`
`OHn_z<EEoo<mamomm
`
`.~zm2:u<.rEz<m>o2mm
`
`
`
`mfiauzai55%
`
`%pzm2:u<.rE
`
`
`
`omfiomfimmm>o2mm
`
`+zm_2:u<,:.<
`
`fl
`
`
`
`
`
`n_z<.m.::...n:2<ZE:><1Em_Q
`
`
`
` 3._.Zm:2IU<:_L.<m:.E...._Omma
`
`
`
`5......momm;._<._.Ohm:.~Emdma
`
`EmezmExuEL<
`
`5
`
`

`
`Patent Application Publication
`
`Apr. 8,2004 Sheet 5 of 14
`
`1A54586Wm.002SU
`
`o3I1..1
`
`
`
`
`
`025040amt?mofimmz
`
`ZOE.¢.U3.E<
`
`ea
`
`
`
`zo_.::>Eomz_><,Em_Dm§d.5
`
`
`
` EfflZmEEU{HF(<OZ_QM<OmE
`
`e.05
`
`zmaoopozfiazou<mzmumz
`
`._.ZmE:U<:.<z<
`
`ma
`
`
`
`m3:o_EE(Sufi;
`
`ezm2:u<Ea
`
`am i
`
`
`
`m<.5o_,E§ZMEO
`
`<5._.Zm_E$U<.H..Cq.
`
`
`
` azofi<o:.E<m.ezm::o<E<
`
`OZ._mOn=2OUOhzmamm
`
`6
`
`
`
`
`
`
`

`
`87:1
`
`
`
`BzomfimsmOZ=zOUZ_Z<mamomm
`
`
`
`Z<OZ=,:<HZOUmo<mmmE
`
`mmmfizz$5><fim_o
`
`7:w._.Z.n=>_IU(.C.<no
`
`
`
` Q>6o2_33.n:>mE.._
`
`._.ZmE_._U<H._.€
`
`oIn
`
`
`
` EAmmo:><n=>mE
`
` PatentApplicationPublication
`
`Apr. 8, 2004 Sheet 6 of 14
`
`US 2004/0068545 A1
`
`
`
`
`
`:350255:mo<mmuESxama
`
`
`
` Qmo§0Ez_ezmEmu<E.<
`
`b.9:
`
`7
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 7 of 14
`
`US 2004/0068545 A1
`
`a.05
`
`mofiwmmz
`
`can
`
`mm
`
`
`
`ozoyiomaZO_._.<EmO.._Z_><1Em_D
`
`
`
`
`
`MEH02.220.HDO:C>2HZmEEU<.C.<
`
`
`
`
`
`mo<mmm_2szofumfimmimumm
`
`
`
`
`
`HZm_EIU<H.r<MZO$5:.5...OZ_Z_¢.._.ZOU
`
`
`
`HZm=2IU¢.:.<zmao
`
`mm
`
`
`
`mmzoazoumfioemum:._..:>_O~E
`
`
`
`
`
`mommozrram§cBm_Eo5:552
`
`
`
`zo_._.<u_.=mm<d.z_<bm_u<no._zm::_uE..Ez<.oz_><m
`
`ea.
`
`
`
` %pzm2:u<E<m><m
`
`
`
`5_o,_bmm_oomzammmazEm
`
`
`
`20.5894>mo5mEn_cam
`
`
`
`Safimnm<20:50..Emzommmm
`
`Q|
`
`
`
` am_o<mmm_2zmmo
`
`
`
`>moBm~__n_am:_um._mmum:Em
`
`
`
`._5.._O.HUmE_DhqDd£mDm<Z_O_._.<UO1_
`
`.
`
`.2;.
`
`ZOCQUOJ
`
`8
`
`
`
`
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 8 of 14
`
`US 2004/0068545 A1
`
`3.0;
`
`a.O—,m
`
`EmIii
`
`
`
`@285:moémmz¢><.amE
`
`
`
`
`
`mi20?...QZEAEOUmimomx
`
`.x<u_DOE.M<n_<nfimmOHmmm:
`
`
`
`mw<mmm2Ezomeumnm
`
`
`
`
`
`mcémmzU_ZOM.HUmAmzmmo
`
`
`
`DZ<MEL..m=2<Zmze><:mE
`
`
`
`._<:Q_>_Q7:mu<mLOmma
`
`mmémmmfi7:._.ZmEEU<._LL<
`
`on:
`
`
`
`
`
`xo5.uEz_..zms_:u<.:.<:._.__s
`
`
`
`mmofizmommmmz.<Bmfimm
`
`Q.
`
`3.
`
`
`
`xmmzazmze>§.§n_
`
`7:m._.Zm_S:._U<._L.<no
`
`
`
`.$OQZ_>2>m:>m§
`
`ma
`
`.am
`
`
`
`ammo:.sm=>mE
`
`9
`
`
`
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 9 of 14
`
`US 2004/0068545 A1
`
`
`
`
`
`QZ<._.Zm_EEU4.._L.<mmod
`
`
`
`OHzmafiaQZ<ZOE.<U:n.E<
`
`
`
`oz5<mmm2U_ZO.m._.Um_._m
`
`.—.Zm:Hu
`
`23
`
`2.U~h
`
`ZO—H.<UOq
`
`8:
`
`no><._._m_oOhZKDHMM
`
`o_zom5m:_mLOmh.ZmC.ZOU
`
`o2_moémmz
`
`3GE
`
`
`
`mmp._.¢._.<—>EOn_m>:.<z
`
`
`
`
`
`ealki
`
`Salk...
`
`
`2__._zm2:uE.E
`
`m<._:B,E<m<m><mE.oz<22oom>Eumm
`
`
`
`zmmo090252300mzmumm
`
`hZm$EU<._.._.<Z<
`
`Sm.
`
`
`VMOHUWEO
`
`
`
`._.15<n_m_Q<._.<..n._..:...m><mO._.mam:.529:
`
`am:
`
`
`
`
`
`0253._.Zm:2EU.«nE.¢.zmmo
`
`82
`
`
`
`ZO_.._..¢UH1_En—(R.E<_oomm<
`
`
`
`
`
`ZO_._.<UOu_§o5$=am>_m_umE
`
`
`
`m.EZH._.Zm=2EU<.F_.<mmoem
`
`_
`
`
`
` 9:_mum::9:
`
`10
`10
`
`
`
`
`
`
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 10 of 14
`
`US 2004/0068545 A]
`
`MESSAGE CENTER
`
`CURLY'S INBOX
`
`I FROM
`I HANCOCK JOHN
`
`SUBJECT
`LUNCH
`
`*
`
`DATE
`WED 2r13.'1976
`
`A Ross. BETSY
`
`BIGIDEAS
`
`REMINDER
`
`E] |i
`
`E
`
`FROM: JOHN ADAMS T0: CURLY@S'|'OOGES.TR|
`SUBJECT: BIG IDEAS
`
`SATFACHMENTS
`
`PLEASE REVIEW MY THREE PROPOSALS AND THEN WE'LL TALK.
`
`OK?
`
`PREVIEW
`WINDOW
`
`FIG. 13
`
`11
`11
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 11 of 14
`
`US 2004/0068545 A1
`
`MAIL OPTIONS ‘
`
`THE MESSAGE CENTER WILL 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 I START UP THE MESSAGE CENTER
`
`El YES. AUTO CHEC_K FOR NEW MAIL
`NO. DO NOT AUTO CHECK.
`I INILL USE THE “GET MA|L" BUTTON TO CHECK FOR NEW
`MAIL
`'
`
`INDICATE YOUR CONNECTION TYPE:
`
`DIAL Access
`
`SPECIFY DEFAULT LOCATIONS TO SAVE ATTACHMENTS
`
`FILES
`
`C:IPROGRAM FILES.-‘MESSAGE CENTERIF
`
`I
`
`BROWSE
`
`PICTURES
`
`CJPROGRAM FILESIMESSAGE CENTERJP
`
`SOUNDS
`
`CJPROGRAM FILESIMESSAGE CENTERIS
`
`PRECONFIGURE
`DEFAULT
`LOCATIONS
`
`FIG. 14
`
`12
`12
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 12 of 14
`
`US 2004/0068545 A1
`
`|7
`
`FROM: CURLY@$TOOGE5.TRI
`
`-ro:r“SS 1
`
`USE A COMMA TO SEPARATE MULTIPLE ADDRESSES
`
`cC= I GETADDRESS
`
`j
`
`TYPE YOUR MESSAGE HERE.
`
`ATTACHMENTS
`
`'
`
` _
`
`ADD OR REMOVE
`ATTACHMENTS
`
`'
`
`FIG. 15
`
`13
`13
`
`

`
`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;ww DOCUMENTSI
`
`| PICTURS _
`
`C:\MY PICTURESI
`
`'
`
`| ADD souos _
`
`C‘.:\MY sounnsx
`
`|g
`
`ATTACHMENT BOX
`
`SIREN.WAV
`
`(33 kB)
`
`TO REMOVE AN ATTACHMENT, SELECT THE ATTACHMENT ABOVE AND CLICK REMOVE
`
`I
`
`FIG. 16
`
`14
`14
`
`

`
`Patent Application Publication
`
`Apr. 8, 2004 Sheet 14 of 14
`
`US 2004/0068545 A]
`
`DATE: FEBRUARY 8, 1976
`FROM: ADAMS, JOHN
`T0: HOWARD, CURLY
`CC:
`SUBJECT: BIG IDEAS
`
`PLEASE REWEW MY THREE PROPOSALS AND THEN WE'LL TALK.
`
`OK?
`
`YOU HAVE 3 FlLE(S) ATTACHED.
`
`I
`
`SAVE FILE
`
`OPEN FILE
`
`PROPOSAL1 .DOC
`
`WORD FILE
`
`PROPOSAL2.Z|P
`
`W'|NZ|F' F|L_E
`
`PROPOSALSPDF
`
`ADOBE ACROBAT DOCUMENT
`
`FIG. 17
`
`15
`15
`
`

`
`US 2004/0068545 A1
`
`Apr. 8, 2004
`
`DISPLAYING AND WORKING WITH EMAIL
`ATTACHMENTS
`
`C ROSS-REFERENC E TO RELATED
`API’LICAl‘IONS
`
`[0001] This application claims priority to copending U.S.
`provisional applications entitled, "1"-UNCTIONAI. SPECI-
`FICATION FOR E-MAIL CLIENT," having serial No.
`60;’4l6,9l6, tiled Oct. 8, 2002, which is entirely incorpo-
`rated herein by reference;
`and "DISPLAYING AND
`WORKING VVITI-I EMAIL ATTACHMENTS," having
`serial No. 6(tf426.422, filed Nov. 14, 2002, which is entirely
`incorporated herein by reference.
`
`TECIINICAI. FIE.I.I)
`
`[0002] The present invention is generally related to elec-
`tronic messaging, and more particularly, is related to attach-
`ments for electronic messaging.
`
`BACKGROUND OF TI-IE INVENIION
`
`[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 ASCI I, 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 pennit 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 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 liles, 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 SMTI’ (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 deline the content of the
`attachment. Atypical header clearly identifies the attach-
`ment file type, original lilename, 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 tile. Often, in a Windows environment, the
`application that is needed to execute the binary file is already
`associated with the filename 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. Thits, a heretofore unaddressed
`need exists in the industry to address the aforementioned
`deficiencies and inadequacies.
`
`SUMMARY OF TI-IE INVENTION
`
`invention
`Preferred embodiments of the present
`[0009]
`provide systems and methods for organizing and managing
`attachments from electronic messages. Briefly described one
`embodiment of 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: prcor-
`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
`16
`
`

`
`US 2OI34/0068545 A1
`
`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 thisdescription, and the scope of the present
`invention.
`
`BRIEF Dl3SCRlP'f'I(JN OF TIIIE 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.
`
`react
`[0029] FIG. 17 is a pictorial representation of a
`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. 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 llowchart 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
`ofa representative embodiment of the attachment manage-
`ment system of FIG. I 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. 14 is 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 clicnt 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.
`
`Preferred Environment
`
`[0031] One preferred embodiment of an attachment man-
`agement systcm of the present
`invention can bc imple-
`mented in software, firmware, hardware, or a combination
`thereof. Preferably, the attachment management system is
`implemented in software, as an executable program in
`corrtbirtation 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 andfor output (U0)
`devices 106 (or peripherals)
`that are communicatively
`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 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, 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
`auxiliary processor among several processors associated
`
`17
`17
`
`

`
`US 2tlI34/0068545 A1
`
`Apr. 8, 2004
`
`DJ
`
`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, andfor 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 (0tS)
`110. The operating system 110 essentially controls the
`execution of other computer programs, and provides sched-
`uling,
`input-output control,
`tile 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 maybe 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 OIS 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, andfor 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 U0 devices 106 may include input devices, for
`example but not
`limited to, a keyboard, mouse, scanner,
`digital camera, multi-function device, microphone, etc. Fur-
`tltermore,
`the IEO devices 106 may also include output
`devices, for example but not limited to, a printer, display,
`etc. Finally, the U0 devices 106 may further include devices
`that communicate both inputs and outputs, for instance but
`not
`limited to,
`a modulatorfdemodulator
`(modem;
`for
`accessing another device, system, or network}, a radio
`frequency (R17) 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.
`
`[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
`I15, and the OIS 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, DSI. 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 L15 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 icat, 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. ‘the
`attachment management system 101 can be embodied in any
`computer—readahle medium for use by or in connect ion with
`an instruction execution system, apparatus, or device, such
`as a computervbased 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 specific
`examples (a nonexhaustive list) of the computer-readable
`medium would include the following: an electrical connec-
`tion (clectronic) 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 iiber (optical), and a portable compact disc read-only
`memory (CDROM) (optical). Note that the cornputer-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,
`intcrpretcd 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 l01 is implemented in hardware,
`the attachment management system 101 can be implemented
`
`18
`18
`
`

`
`US 2004/0068545 A1
`
`Apr. 8, 2004
`
`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 array[s} (l’GA), 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
`diflerent 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 tiles that do not fit into another type.
`
`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
`ofthc attachment management system 101. It should also be
`noted that in some alternative implementations the functions
`noted in the various blocks may occur out of the order
`depicted in the llowcharts 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 prcconfigurc 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 direcw
`[0046]
`tory location, as shown in blocks 2'12-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 set 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 he
`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
`Attachmertts” 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.
`
`[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 lile
`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 I'lle(s) to attach to an email
`message. In block 240,
`the selected tile is added as an
`attachment to the electronic message.
`
`[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 [lie 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.
`
`[0050] Next in block 350,