throbber
.
`
`United States Patent [19
`Boaz et al. -.
`v
`
`USOO5333266A
`
`[11] Patent Number:
`[45] Date of Patent:
`
`5,333,266
`Jul. 26, 1994
`
`[54] METHOD AND APPARATUS FOR MESSAGE
`HANDLING IN COMPUTER SYSTEMS
`[75] Inventors: Wade Boaz, Clifton; Daniel D’Elena,
`Milford; Michael Lucivero, Emerson,
`all of NI; Sarka Martinez, Boca
`Ramn, F1a_; Ronald J_ salpietra,
`Novi, Mich; Olga E, Savastano,
`Bloom?eld; Ronald Soltis, Wayne,
`both of NJ.
`.
`'
`.
`_
`.
`[73] Asslgnee' gern?gzzlgrugllgis glhgfhmes
`rpo
`’
`’
`'
`'
`[21] Appl. No.: 858,918
`[22] Filed:
`M an 27, 1992
`
`[5
`
`Int. Cl.5 ............................................ .. G06F
`‘JES- Cl. .................................................. ..
`Fleld Of Search ............. ..
`700, 600,
`370/60’ 94-1
`
`[55]
`
`References Cited
`
`U's' PATENT DOCUMENTS
`4,791,660 12/1988 Oye et a1. .
`4,794,639 12/1988 Urui et al. .
`4,805,207 2/1989 MCNP“ at al- -
`gqshldal ‘J
`t al
`4’837’798 6/1989 Cohen‘:
`e
`'
`4,847,891 7/1989 Kotani .
`4,90l,34l 2/1990 Carter et al. .
`5,121,384 6/1992 Ozeki et al. ......................... .1 370/60
`
`'
`
`5,170,252 12/1992 Gear et al. ........................ .. 358/181
`Primary Examiner—Robert L. Richardson
`Attorney, Agent, or Firm-J. E. Hoel; K. A. Seaman
`57
`ABSTRACT
`[
`1
`_
`An Integrated Messaging System which integrates mail
`from a plurality of mail servers handling messages of
`different media types such as text, voice, facsimile,
`video and image. The IMS maintains the in-basket for
`all mail systems, eliminating the need to collect each
`type of mail separately. Any terminal interface, tele
`phone or computer workstation can be used to collect,
`generate and act upon a message of any media type
`Further, from the preferred system, the user can request
`another ?le server and its associated termmals to per
`form
`Services‘ 'The system includes a variety
`traditional
`and Voice
`functions
`can
`be used for any message‘ The
`also includes syn
`chronization means which checks to see whether the
`mail count in each in-basket is the same to guarantee
`that the same mail items are in each ?le server in-basket.
`An integrated messaging protocol is used to pass infor
`mation between the ?le servers. It is designed in a ge
`neric manner to allow wide variety of foreign message
`formats at each of the respected media ?le server. For
`the majority of transactions, the protocol is independent
`of message body format, referencing only the message
`P0111ter Or header
`
`36 Claims, 19 Drawing Sheets
`
`r'52
`
`‘
`
`OFFICE
`OFFICE
`(cgigg?n iizprgggiiégl
`125
`m E9
`
`OSRH L35
`
`ISRH L'i?
`
`FSRH 138
`
`MEMORYlQQ
`
`OPERATING
`SYSTEM
`129
`
`SOF'WARE
`122
`
`STORE
`125
`
`IMSJQQ
`IMS SYNCH VSRH 1&2
`m
`TEXT-TO-SPEECH
`SPEECH-TO'TEXT
`HQ
`
`OCR-TO-TEXT
`TEXT -TO-OCR
`Mg
`
`(BUS101
`
`CPU
`1-02
`
`DISPLAY
`DASD
`CO-
`FLOPPY
`PROC. m & KEYBD
`DISK
`log
`ADAPTER
`ADAPTER
`108-) ]
`noJ I
`
`CD ROM
`ADAPTER
`£2
`I
`
`NETWORK
`ADAPTER
`1.1.4.
`|
`
`Google Ex. 1211, pg. 1
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 1 0f 19
`
`5,333,266
`
`Google Ex. 1211, pg. 2
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 2 of 19
`
`5,333,266
`
`FIG. 2
`
`('52
`
`MEMORY _1_QQ
`
`OPERATING
`SYSTEM
`m
`
`OFFICE
`SERVER
`SOFTWARE
`122
`—
`
`OFFICE
`POINTER
`STORE
`124
`—
`
`OFF‘CE
`OFF‘CE
`MESSAGE
`MESSAGE
`STORE (CHAR
`STORE
`(CONTENT) AOTERISTIOS) m
`32.5
`1.2%
`
`MEDIA
`EXT.
`
`mm
`IMSSYNCH VSRHQ OSRHBA
`B1
`TEXT-TO-SPEECH
`SPEECH-TO-TEXT
`m
`
`1$RH13§
`
`FSRHQS
`
`OOR-TO-TEXT
`TExT-TO-OOR
`m
`
`(BUSTOI
`
`DISPLAY
`DASD
`60-
`CPU
`FLOPPY
`PROC. m &KEYBD
`102
`DISK
`— 1%
`ADAPTER
`ADAPTER
`108-]
`IIDJ
`
`CD ROM
`ADAPTER
`I_I_g
`
`NETWORK
`ADAPTER
`m
`
`Google Ex. 1211, pg. 3
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 3 of 19
`
`5,333,266
`
`FIG. 3
`
`K50
`
`MEMORY 15D
`
`OPERATING
`SYSTEM
`m
`
`vOIOE
`SERvER
`SOFTWARE
`L72
`
`VOICE
`POINTER
`STORE,
`L7_4
`
`voIoE
`MESSAGE
`STORE
`E6
`
`MEDIA
`EXT.
`
`1_78.
`
`(BUSIST
`
`00-
`CPU
`PROO.
`152
`— 15$
`
`DASD
`156
`-——
`
`DISPLAY
`FLOPPY
`&KEYBD
`DISK
`ADAPTER
`ADAPTER
`J
`J
`158
`160
`
`ODROIvI
`ADAPTER
`I_S_2_
`|
`
`NETWORKP
`ADAPTER
`LEA
`I
`
`PBX
`ADAPTER
`155
`l
`
`Google Ex. 1211, pg. 4
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 4 of 19
`
`5,333,266
`
`FIG. 4
`
`(-54
`
`MEMORY gag
`
`OPERATING
`SYSTEM
`ggg
`
`IMAGE
`SERVER
`SOFTWARE
`.22
`
`IMAGE
`POINTER
`STORE
`2A
`
`IMAGE
`MESSAGE
`STORE
`225
`
`MEDIA
`ExT.
`
`2_23
`
`(BUS 201
`
`00
`CPU
`PROC.
`202
`_ Q05
`
`DASD
`2%
`
`FLOPPY
`DISPLAY
`DISK
`& KEYBD
`ADAPTER
`ADAPTER
`208 J
`210 J
`
`CD ROM
`ADAPTER
`g3
`
`NETWORK
`ADAPTER
`m
`
`Google Ex. 1211, pg. 5
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 5 of 19
`
`5,333,266
`
`FIG. 5
`
`(-56
`
`MEMORY m
`
`OPERATING
`SYSTEM
`g7_0
`
`FAx
`SERVER
`SOFTWARE
`ZZZ.
`
`FAx
`POINTER
`STORE
`2H
`
`FAx
`MESSAGE
`STORE
`ZZQ
`
`MEDIA
`EXT.
`
`2E
`
`( BUS 251
`
`CPU
`252
`—-
`
`FLOPPY
`DISPLAY
`DASD
`00-
`DISK
`& KEYBD
`256
`PROO.
`ADAPTER
`2g — ADAPTER
`258 J
`260 J
`
`CD ROM
`ADAPTER
`?g
`
`NETWORK
`ADAPTER
`25g
`
`Google Ex. 1211, pg. 6
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 6 of 19
`
`5,333,266
`
`FIG. 6
`
`MEMORYBQQ
`
`OPERATING
`SYSTEM
`
`PRESENTATION
`MANAGER
`22
`
`IMS
`INTERFACE
`3_2_§
`
`(BUS 301
`
`00-
`CPU
`PROC.
`302
`— 3%
`
`DASD
`3%
`
`DISPLAY
`&KEYBD
`ADAPTER
`308-]
`
`FLOPPY
`DISK
`ADAPTER
`L310
`
`CD RoM
`ADAPTER
`912
`
`NETWORK
`ADAPTER
`m
`
`SCQBQER
`
`FAX
`DARD
`
`VOICE
`CARD
`
`Google Ex. 1211, pg. 7
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 7 of 19
`
`5,333,266
`
`FIG. 7
`
`f HOST 350
`
`MEMORY 35
`
`OPERATING
`SYSTEM
`2-0:
`
`OFFICE SERVER
`SOFTWARE
`
`VOICE SERVER
`SOFTWARE
`
`TEXT-TO-SPEECH
`SPEECH-TO-TEXT
`m
`
`IMAGE SERVER
`SOFTWARE
`222'
`
`OCR-TO-TEXT
`TEXT -TO-OCR
`E'
`
`FAX SERVER
`SOFTWARE
`l'
`
`FACSIMILE
`WORKSTATION
`
`PBX
`5.2‘
`
`IMAGE
`WORKSTATION
`B3.‘
`
`( BUS 352
`
`OFFICE
`WORKSTATION
`
`d ’ ,
`
`QB! FACSIMILE 5Q‘
`
`TELEPHONE LINES
`
`Google Ex. 1211, pg. 8
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 8 0f 19
`
`5,333,266
`
`FIG.8
`
`OFFICE
`WORKSTATION
`E
`
`4133/“
`
`400
`
`OFFICE SERVER
`SOFTWARE 1_2_2_
`
`I
`
`402
`416
`I30 '\ v . N
`
`VOICE
`TERMINAL
`53
`
`423/M
`
`404
`"\J
`VOICE SERVER
`SOFTWARE E
`
`A
`
`.
`
`406
`420
`V v\’
`
`INTEGRATED MESSAGING SYSTEM SERVER
`
`A
`
`424
`410
`v v\J
`
`IMAGE SERVER
`SOFTWARE 22
`
`426
`
`IMAGE
`WORKSTATION
`l3
`
`[I
`
`428
`414
`v \T\J
`
`FACSIMILE SERVER
`SOFTWARE 2:/'_2_
`
`FACSIMILE
`WORKSTATION
`SQ
`
`Google Ex. 1211, pg. 9
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 9 0f 19
`
`5,333,266
`
`' '-
`
`FIG. 9
`
`(2 BYTES) (2 BYTES) (2 BYTES) (2 BYTES)
`MSG LEN
`VERB ID
`FLD LEN FIELD ID
`
`(N BYTES)
`FIELD VALUE
`
`RECORD (VSUSERID, VSNODE, SESSIONPHONE, RECORDTYPE, VSSEQUENCE)
`MSG LEN
`VERB ID
`FLD LEN
`FLD ID
`FIELD VALUE
`44
`88
`1o
`54
`SOLTIS
`12
`52
`VOICENOD
`8
`88
`2885
`5
`25
`1
`5
`53
`o
`RECORDR (VSUSERID, VSNODE, SESSIONPHONE, ERRCODE)
`MSG LEN
`vEFIB ID
`FLD LEN
`FLD ID
`36
`34
`1o
`54
`12
`52
`8
`88
`2
`15
`
`FIELD VALUE
`SOLTIS
`VOICENOD
`2885
`o
`
`ENDRECORD (VSUSERID, VSNODE, DELETEFLAG, SESSIONPHONE)
`MSG LEN
`VEFIB ID
`FLD LEN
`FLD ID
`FIELD VALUE
`85
`69
`1o
`54
`SOLTIS
`12
`52
`VOICENOD
`1
`64
`1
`8
`88
`(2885
`ENDRECORDR (VSUSERID, VSNODE, SESSIONPHONE, ERRCODE)
`MSG LEN
`VERB ID
`FLD LEN
`FLD ID
`FIELD VALUE
`36
`70
`1o
`54
`SOLTIS
`12
`52
`VOICENOD -
`8
`88
`2885
`2
`15
`o
`PLAY (VSUSERID, VSNODE, SESSIONPHONE, PLAYACTION, VSSEQUENCE)
`MSG LEN
`VERB ID
`FLD LEN
`FLD ID
`FIELD VALUE
`48
`25
`10
`54
`SOLTIS
`12
`52
`VOICENOD
`8
`88
`2885
`1
`23
`2885
`8
`58
`12845578
`PLAYR (vsusEFIID, VSNODE, sEssIoNPHoNE, EFIRDDDE, VSSEQUENCE)
`MSG LEN
`VERB ID
`FLD LEN
`FLD ID
`FIELD vALuE
`44
`26
`1o
`54
`SOLTIS
`12
`52
`voIoENoD
`8
`88
`2885
`2
`15
`o
`8
`58
`12845578
`
`Google Ex. 1211, pg. 10
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 10 of 19
`
`5,333,266
`
`FIG. 10
`
`f500
`VOICE SYNCHRONIZATION FLOW
`uSER CREATES, ADDRESSES AND SENDS VOICE
`MESSAGE FRoM TELEPHONE
`‘
`NEw VOICE MAIL HEADER SENT TO |MS
`‘
`RECEIVE VOICE HEADER
`
`f504
`
`K502
`
`v
`
`v
`
`I
`
`4,1
`
`506
`NO
`
`[508
`ll ASK OFFICE
`SYSTEM FoR COUNT
`OF VOICE ITEMS
`K510
`Q] SEND COUNT
`OF VOICE ITEMS
`TO ‘M8
`
`513%;
`VMS
`COUNT?
`
`NO
`
`'
`
`7
`YES r514
`1
`*1 35%";5
`OFFICE INBASKET
`
`V
`[516
`ll FDR REFRESHED
`VOICE ITEMS, CHECK -
`OFFICE INBASKET
`
`NO [520
`ADD VOICE
`ll
`READER TO OFFICE
`INBASKET
`_._______l
`[522
`l]
`REQUEST
`7 REFRESH OF VOICE
`HEADER FRDM vMS
`f524
`1] FOR EACH
`VOICE HEADER, SEND
`REFRESH VOICE
`HEADER TO ‘M3
`
`END
`
`Google Ex. 1211, pg. 11
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 11 of 19
`
`5,333,266
`
`FIG. 1 1
`
`TEXT SYNCHRONIZATION FLOw
`g) USER CREATES ADDRESSES AND SENOS TEXT
`MESSAGE FROM WORKSTATION
`I
`_O] NEw TEXT MAIL NOTIFICATION SENT TO IMS
`
`I
`l] RECEIvE NEw TEXT MAIL NOTIFICATION
`
`I
`_I] OBTAIN COUNT OF TEXT ITEMS FOR RECIPIENT
`
`I
`_I_! SEND NEW TEXT MAIL NOTIFICATION TO vMS
`
`I
`l] RECEIvE TEXT MAIL NOTIFICATION AND COUNT
`
`I
`1] CHECK TEXT MAIL COUNT FOR INTENDED -
`RECIPIENT
`
`550
`
`552
`
`554
`
`556
`
`55s
`
`560
`
`562
`
`/' 566
`ll ADD TEXT
`HEADER TO INBASKET
`
`_v_]
`
`_I_]
`
`‘_Ij
`
`REQUEST LISTING OF ALL TEXT HEADERS
`FOR INTENOEO RECIPIENT FOR IMS
`
`I
`
`I
`
`GET TEXT INBASKET FROM OFFICE
`
`FOR EACH TEXT ITEM IN INRASKET, SENO
`REFRESH TEXT ITEM NOTICE TO vMS
`
`568
`
`570
`
`572
`
`_vj
`
`ADD TO vMS INBASKET
`
`' 576
`
`END
`
`Google Ex. 1211, pg. 12
`
`

`
`U.S. P
`atent
`
`July 26, 1994
`
`Sheet 12 of 19
`
`5,333,266
`
`FIG. 12
`
`:
`
`In-basket
`
`AV
`
`File View Help
`RON.FRKLAN1 \/~ 711
`Some Text Mail for youw713
`11-3-89
`7:05:03 am~/— 712
`SARKA.VCFRK \/.\ 715
`An-important message/\716
`11-15-89 10:34:45 am 5:54 min. (Comment)w 722
`WADEFWCFRK
`K
`No Description
`11-15-89 12:07:05 pm 2:13 min.
`1%
`SALP.FXOH
`Contract Documents
`11-17-89 10:45:01 am (Passage)w724
`DAND.1MFRK
`No Description
`11-17-89 11:51:51 am
`LUCIVER.FRKLAN1
`Meeting Notice
`11-18-89 9:01 :33 am
`
`706 x
`
`706 x
`
`7101
`
`720 1
`
`Google Ex. 1211, pg. 13
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 13 of 19
`
`5,333,266
`
`FIG. 13
`
`Forward
`
`l;asbefore.......................
`[Text Comm nt
`tt
`
`Addressing
`
`Description
`Comments
`e
`C
`C
`
`Record
`
`Options
`
`Send
`
`754
`
`Cancel
`
`752
`
`Google Ex. 1211, pg. 14
`
`

`
`us. Patent
`
`my 26, 1994
`
`sheet 14 of 19
`
`5,333,266
`
`Google Ex. 1211, pg. 15
`
`

`
`U.S. Patent
`
`July 26, 1994
`
`Sheet 15 of 19
`
`5,333,266
`
`2GE
`
`wmemoac_m_v_oS>m_g2:nm:§m
`
`
`
`m_o_o>.mm>_o:._“E9”.
`
`
`
`amnem:_.$s_<ao_a_ammo
`
`
`
`.:_ERnmo“:o_§:o
`
`so:
`
`.
`
`.____SmV.mm_o
`
`
`
`gs88a$%_mme:§.%_n_
`
`2m9m
`
`_|..Il.l..|..IsJ
`
`Google Ex. 1211, pg. 16
`
`Google Ex. 1211, pg. 16
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 16 of 19
`
`5,333,266
`
`FIG. 16
`RECORDING A MESSAGE:
`I000
`
`USER DOUBLE
`CLICKS ON THE
`RECORDER
`ICON
`
`LOAD THE REOORD
`DIALOG BOx
`
`LOAD MESSAGE
`BOx "WILL CALL BACK"
`
`1002
`
`1 04
`0
`
`IF NO REOORDS
`ARE RUNNING
`
`/
`
`1008
`
`START THE
`RECORD THREAD
`K1010
`1
`GET ITEMS SEQUENCE #
`(NEW ITEMS wILL = 0),
`REOORD TYPE, USER'S
`USER ID AND DOMAIN
`NAME, PHONE NUMBER
`
`A
`
`‘
`
`&
`
`r1012
`
`CALL THE RECORD vERB
`
`rI010
`GET ITEMS USER'S USER
`ID AND DOMAIN NAME,
`PHONE NUMBER
`
`r1018
`CALL THE GET
`vMS SEOUENOE vERB
`&
`F1020
`PHONE CALLS BACK
`
`1022
`
`USER CLICKS
`ON END REOORD
`BUTTON
`
`r1024
`START THE END.
`REOORD THREAD
`l
`
`1026
`r’
`GET ITEMS USER'S
`USER ID AND DOMAIN
`NAME, PHONE NUMBER
`
`&
`
`F“ 1028
`
`START THE GET END
`RECORD THREAD
`I
`
`I
`r1014
`
`OALL THE END
`REOORD vERB
`
`GET vMS SEQUENCE
`vERB RETURNS WHEN
`REOORD HAS TRULY
`ENDED. SAvE THE
`SEOUENOE # AND
`RECORDING DURATION
`
`C)
`
`Google Ex. 1211, pg. 17
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 17 of 19
`
`5,333,266
`
`FIG. 17
`
`PLAYING A MAIL IOON FROM THE lN-BASKET:
`1050
`
`USER
`CLICKS ON
`VOICE MAIL
`ITEM
`
`LOAD THE PLAY
`DIALOG BOx
`
`LOAD MESSAGE
`BOX, "WILL CALL BACK"
`
`1052
`
`I054
`
`1056 I
`
`'
`
`IF NO PLAYS
`ARE RUNN'NG
`
`ELSE
`
`r1058
`
`START THE
`PLAY THREAD
`F1060
`I
`GET ITEMS SEOUENOE #,
`USER'S USER ID AND
`DOMA'N NAME’
`PHONE NUMBER
`
`r1062
`
`f1063
`
`CALL THE PLAY vERB
`
`START THE GET END
`PLAY THREAD
`
`r1064
`GET ITEMS USER'S USER
`ID AND DOMAIN NAME,
`PHONE NUMBER
`
`r—1066
`CALL THE GET
`END PLAY vERB
`f
`F1068
`PHONE CALLS BACK
`
`I070
`
`USER CLICKS
`ON END PLAY
`BUTTON
`
`'
`
`_
`
`(-1072
`START THE END
`PLAY THREAD
`r1074
`I
`GET ITEMS USER'S
`USER ID AND DOMAIN
`NAME, PHONE NUMBER
`
`(-1076
`
`@
`CALL THE END
`PLAY VERB
`
`K-1080
`GET PLAY END RETURNS
`wHEN PLAY BACK HAS =
`TRULY ENDED
`
`C)
`
`Google Ex. 1211, pg. 18
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 18 of 19
`
`5,333,266
`
`FIG. 18
`CREATING AN IN-BASKET VIEW FILLED WITH VOICE AND TEXT MAIL:
`
`I100
`
`USER OPENS
`THE INBASKET
`
`r1102
`CALL OFFICE SERVER
`TO GET ALL INBASKET ITEMS
`
`DISPLAY A TEXT
`ITEM ICON
`
`“I8
`
`-
`
`SEQUENCE # NOT = 0,
`AND NOT=TEXT
`
`ELSE
`
`1122
`
`INDICATE A
`voICE BUCKSLIP
`
`-
`
`SAvE ALL RELATIVE
`INFORMATION IE.
`E
`IPT
`D sgspg ‘EDT-haw“-
`
`‘
`
`SEQUENCE #
`
`NOT=0
`
`‘I108
`
`MAIL TYPE IS A voICE
`MAIL ITEM
`
`ELSE
`
`INDICATE A
`TExT BUCKSLIP
`
`M10
`
`OBTAIN SEQUENCE #,
`LENGTH OF TIME,
`BUCKSLIP SEQUENCE #
`
`T112
`< DISPLAY A voICE %
`ITEM ICoN
`
`1114
`
`1124
`
`1 126
`
`ELSE
`
`ELSE
`
`IF NOT
`THE LAST MAIL
`ITEM
`
`r1128
`DISPLAY ALL MAIL
`ITEMS W/ THEIR
`RELEVANT INFORMATION
`
`Google Ex. 1211, pg. 19
`
`

`
`US. Patent
`
`July 26, 1994
`
`Sheet 19 0f 19
`
`5,333,266
`
`FIG. 19
`DIALING FROM THE PHONE PANEL:
`
`1150
`
`1152
`
`I154 .
`
`1156
`
`USER DOUBLE
`CLICKS ON THE
`PHONE
`ICON
`
`LOAD THE DIAL
`DIALOG BOX
`
`USER ENTERS
`PHONE NUMBER
`
`USER CLICKS ON
`DIAL BUTTON
`
`“66
`LOAD MESSAGE BOX,
`‘WILL CALL BACK‘
`
`H68
`F’
`CALL DIAL ANALOG THREAD
`
`(-1170
`GET USER'S USER ID
`AND DOMAIN NAME,
`PHONE NUMBER, CALL
`TO PHONE NUMBER
`
`& r1172
`CALL THE DIAL vERB
`
`r1158
`READ THE PHONE NUMBER
`
`A r1174
`PHONE CALLS BACK
`
`IF PHONE
`NUMBER IS
`INVALID
`
`I160 ELSE ‘
`
`1162
`
`I164
`
`DISPLAY ERROR
`MESSAGE ,
`
`IF
`USING AN ANALOG
`PHONE
`
`Google Ex. 1211, pg. 20
`
`

`
`1
`
`5,333,266
`
`METHOD AND APPARATUS FOR MESSAGE
`HANDILING IN COMPUTER SYSTEMS
`
`BACKGROUND OF THE INVENTION
`
`This invention relates generally to electronic messag-
`ing systems. More particularly, this invention relates to
`a multimedia messaging system in which message infor-
`mation processed and stored by any of a plurality of
`interconnected electronic mail systems can be accessed
`from any system.
`Voice mail messaging in a telecommunication system
`when the caller is unavailable has become nearly ubiqui-
`tous. The voice message is recorded and a notification
`may be given to the called party indicating the presence
`of a message. Further, it is also common to provide
`electronic mail systems such as IBM’s PROFS TM and
`OfficeVision/VM TM in which text messages are sent
`from a sender’s computer terminal over a data network
`to other computer terminals within the network. While
`these messaging systems have greatly improved the
`efficiency of today’s office environment, access to a
`terminal or voice mail system is not always possible.
`Further, as the office environment evolves toward mul-
`timedia systems, one will work with a large amount of
`information, collected from a variety of media types
`including text, image, video, voice and facsimile. Much
`of this information need not originate from the local
`computer terminal. Thus, it would be advantageous if
`the receiver could receive mail from all of these differ-
`ent media, or at least notification thereof, whether he
`had access to all or to only one of the mail systems
`normally at his disposal. In other words, it would be
`advantageous to integrate the messaging systems effi-
`ciently, particularly voice mail and electronic mail sys-
`tems because of their relative prevalence, such that all
`types of mail items are available from any system.
`The prior art has suggested several possible inte-
`grated messaging systems, all of which have their disad-
`vantages. One system includes a human operator who
`takes the phone message, when the receiving party is
`unavailable and manually types in a notification which
`is sent to the receiving party’s electronic mail. In this
`system, the receiving party has notification of the mes-
`sage, but because of the manual nature of the transac-
`tion, only a limited amount of information is generally
`forwarded. The user does not generally have access to
`an entire voice message at his data terminal as he would
`with a voice mail system.
`At least one other proposed integrated messaging
`system would allow a recipient to access both text and
`voice messages from either the electronic mail system
`or the voice mail system. However, the recipient must
`designate which messaging system is to receive all of
`the messages. This is a burden on the recipient who
`must be able to project to which system he is more
`likely have access and whose plans may be subject to
`change. If the recipient guesses incorrectly, both types
`of mail may be unavailable. The capabilities of the ter-
`minals of the respective systems differ greatly in capa-
`bility, a computer terminal is more versatile in handling
`some of the media types than a telephone. Choosing the
`more readily available system, voice mail, because of
`uncertain travel plans can lead to the loss of consider-
`able message content. Further, prior systems send the
`entire content of a message to the designated recipient
`
`5
`
`l0
`
`15
`
`20
`
`25
`
`30
`
`35
`
`45
`
`50
`
`55
`
`65
`
`2
`service which reduces system performance given the
`large amount of data in a multimedia message.
`Only a limited degree of integration of the various
`messaging services is taught by the prior art. Usually,
`the recipient is only notified that he has messages on one
`or more of his message services. If the messaging sys-
`tems are not well integrated with a consistent message
`protocol, there is always the possibility that a foreign
`message will be rejected.
`
`SUMMARY OF THE INVENTION
`
`It is therefore an object of the invention to integrate
`a plurality of messaging system which handle messages
`of different media types into an integrated messaging
`system.
`It is another object of the invention that mail of any
`media type and originating from any messaging system
`coupled to the integrated messaging system can be ac-
`cessed at a terminal associated with any of the messag-
`ing services.
`It is another object of the invention to a request from
`a local terminal to access message functions from a
`foreign messaging system.
`It is another object of the invention to build an inte-
`grated in-basket containing all the mail to a recipient,
`regardless of media type, at each message service in the
`integrated messaging system.
`It is another object of the invention to guarantee that
`each in-basket has the identical mail items.
`
`It is another object of the invention to request mes-
`sage functions from a foreign messaging system be per-
`formed at a terminal coupled to the foreign messaging
`system at a local terminal.
`These and other objects are accomplished by an Inte-
`grated Messaging System (IMS) which integrates mail
`from a plurality of mail servers handling messages such
`as electronic mail and voice mail as well as media such
`as facsimile, video and image. The IMS maintains syn-
`chronicity between all in-baskets for all mail systems,
`eliminating the need to collect E-mail and voice mail
`separately. In its most preferred embodiment, any ter-
`minal interface,
`telephone or computer workstation,
`can be used to generate, manipulate or receive a mes-
`sage of any media type. Although the capabilities of the
`terminal device may limit the user’s ability to handle
`certain types of media, e.g., video. Thus, from the pre-
`ferred system terminal, the user can access messaging
`services from any mail server in the IMS to collect,
`create, and act upon messages of any media type. The
`IMS includes a variety traditional E-mail and voice mail
`functions which can be used for any message.
`In the preferred embodiment, the IMS comprises a
`plurality of file servers each coupled to a plurality of
`workstations. Before modification for inclusion inthe
`IMS, each file server and its associated terminals and
`workstations were configured to handle message ser-
`vices of a particular media type.. The file servers are
`coupled together by the IMS, which allows worksta-
`tions which are coupled to a file server which normally
`handles messages of a particular media type to request
`messaging services from a file server which handle
`messages of a second media type. Thus, by requesting
`the appropriate file server, any terminal can create and
`access mail regardless of media type. Each file server
`includes a message store for the messages of the media
`type which it handles, as well as a message pointer store
`which serves as an in-basket. The message pointer store
`includes message pointers for all the messages to system
`
`Google Ex. 1211, pg. 21
`
`Google Ex. 1211, pg. 21
`
`

`
`3
`users regardless of media type. The message pointer
`store is partioned into a plurality of mail baskets and
`note baskets for each user of the file server. Each file
`server contaiffs media extension code which allows a
`protocol conversation with the IMS and contains new
`definitions for message pointers of foreign media types.
`The media extensions also automatically shadow mail
`pointers to the IMS which sends copies of the message
`pointers to the recipient’s mail baskets at each of the
`other file servers. The IMS also includes synchroniza-
`tion means which checks to see whether the mail count
`\
`in each in-basket is the same to guarantee that the same
`mail items are in each file server in-basket.
`An Integrated Messaging Protocol (IMP) is used to
`pass information between the file servers. It is designed
`in a generic manner to allow wide variety of foreign
`message formats at each of the respected media file
`server. Each request will generate a corresponding
`response within the protocol. These requests and re-
`sponses in the IMP are mapped onto local requests and
`responses by the media extension at both the requesting
`file server and the responding file server. The IMP is
`independent of message body format, referencing only
`the message pointer in the file servers.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`These and other objects and features will be more
`readily understood from the following description and
`attached drawings which include:
`FIG. 1 is an overall diagram of one preferred embodi-
`ment of the electronic hardware in the integrated mes-
`saging system.
`FIG. 2 is a block diagram of the office server.
`FIG. 3 is a block diagram of the voice server.
`FIG. 4 is a block diagram of the image server.
`FIG. 5 is a block diagram of the facsimile server.
`FIG. 6 is a block diagram of the office workstation.
`FIG. 7 is a block diagram of an alternative embodi-
`ment of the integrated message system.
`FIG. 8 shows the overall message flows in an IMS
`having electronic voice, image and facsimile mail sys-
`tems.
`
`5
`
`10
`
`I5
`
`20
`
`25
`
`30
`
`35
`
`FIG. 9 shows the general message format in the Inte-
`grated Messaging Protocol as well as some specific
`message requests and message responses.
`FIG. 10 is a flow diagram of the text synchronization
`procedure in IMS.
`FIG. 11 is a flow diagram of the voice synchroniza-
`tion procedure in IMS.
`FIG. 12 is the integrated mail basket panel which
`notifies the recipient about the mail items.
`FIG. 13 is the forward panel which is used to forward
`a message at a computer workstation in the IMS.
`FIG. 14 is the recorder panel which is used to gener-
`ate a message at a computer workstation in the IMS.
`FIG. 15 is the play voice mail panel used to play a
`voice message at a computer workstation in the IMS.
`FIG. 16 is a flow diagram of recording a message.
`FIG. 17 is a flow diagram of creating an in basket
`view.
`FIG. 18 is a flow diagram of playing a mail item.
`FIG. 19 is a flow diagram of dialing from the phone
`panel.
`
`45
`
`50
`
`55
`
`DETAILED DESCRIPTION OF THE
`DRAWINGS
`
`65
`
`The invention may be run on a variety of different
`computers operating under a number of different oper-
`
`5,333,266
`
`4
`ating systems. However, for purposes of illustration,
`one preferred embodiment of the Integrated Messaging
`System (IMS) is shown in FIG. 1. A plurality of media
`file servers 50, 52, 54 and 56 are coupled together into a
`local area network (LAN) by a shared bus 60 such as
`the IBM Token Ring network. Each media file server
`handles messages of particular media type and has asso-
`ciated terminals which also handle messages of the same
`media type. As the file servers are coupled to each other
`through the IMS, each terminal can request messaging
`services from the other file servers, enabling the termi-
`nals to handle messages any media type handled by the
`file servers in the IMS. The messaging service may be
`performed by either the requesting terminal, or, if the
`requesting terminal is hardware limited, by a terminal
`associated with the file server from which the messag-
`ing service was requested. The bus structures depicted
`in FIG. 1 coupling the terminals to their respective file
`servers are merely illustrative. The workstations can be
`on the same token ring as the servers, or different rings
`communicating to the servers via bridges between
`rings, etc.
`The voice messaging server (VMS) 50 is responsible
`for voice messaging functions and allows for remote
`telephone access to all messages and interfaces with the
`local telephone switch or PBX 62. The programming
`on the VMS 50 which provides voice mail functions can
`be any of a number of commercially available platforms
`with suitable modifications to accept messages of other
`media types. Typical voice server functions include:
`create, revise, send, forward and append voice mail
`items, save a mail item in the voice mail store, and up-
`date the VMS addresses. The PBX 62 is connected to
`telephone terminals 63, 64, 65 and 66 and outside tele-
`phone lines.
`The electronic mail or office server 52 drives the
`office e-mail and directory functions and allows access
`to the Integrated Messaging System by workstations 70,
`71, 72 and 73. The office server code which drives the
`office functions has the appropriate revisions to handle
`messages of other media types. Typical office server
`functions include create, revise, send, forward and ap-
`pend text mail items, save mail items in the text mail
`store and update text mail addresses. In one preferred
`embodiment, the integrated messaging server software
`(IMSS) which is the piece of code which passes requests
`and responses between the mail systems as well as keep-
`ing the message counts synchronized in each recipient’s
`in-basket on each of the mail systems is also resident on
`the office server 52.
`
`Image server 54 is also coupled to the Token Ring 60.
`It is part of an image system capable of handling of
`‘image data. The image system will typically comprise a
`dedicated host system 76 with its own set of worksta-
`tions (not pictured) together with DASD and optical
`storage 77 for the image data. Typically, image systems
`will archive digitized images of documents entered into
`the system by video camera or scanner which are com-
`pressed and stored in image files referred to as image
`objects. The image system contains image application
`code which scans, stores, retrieves, displays or ex-
`changes the archived images. An image system is de-
`scribed in co-pending, commonly assigned patent appli-
`cation Ser. No. 211,646 by C. A. Parks et al., entitled
`“Dual Density Digital Image Systems filed Jun. 27,
`1988 which is hereby incorporated by reference. An-
`other co-pending patent application is by C. A. Parks et
`al., entitled “Object Management and Delivery System
`
`Google Ex. 1211, pg. 22
`
`Google Ex. 1211, pg. 22
`
`

`
`5,333,266
`
`5
`Having Multiple Object Resolution Capability”, Ser.
`No. 211,722, filed Jun. 27, 1988 which is commonly
`assigned and is also hereby incorporated by reference.
`A facsimile'§er_ver 56, also on the token ring 60, cou-
`ples a plurality of facsimile machines 84 and 86 to the
`IMS. The facsimile routing system also comprises fac-
`simile workstations 80, 82 to which the facsimile images
`may be sent. Alternatively,
`the facsimile machines
`could be replaced by facsimile cards in either the fac-
`simile server 56 or the facsimile workstations 80, 82.
`Facsimile server functions include: create, send, for-
`ward facsimile mail items. The facsimile workstations
`are used for further distribution and/or routing of the
`facsimile messages. Distribution lists and cover sheets
`for each user can be stored at the facsimile workstations
`or facsimile server to facilitate routing. A facsimile
`routing system is described in co-pending, commonly
`assigned patent application Ser. No. 693,739 to Argenta
`et al., entitled “Apparatus and Method of Operation
`For Facsimile Sub-System and An Image Archiving
`System”, filed Apr. 30, 1991 which is hereby incorpo-
`rated by reference.
`The servers 50, 52, 54 and 56 communicate over the
`IBM token ring (TR) network 60, using the Integrated
`Messaging Protocol (IMP), a message protocol de-
`signed in a generic fashion so that any of the systems
`can pass message pointers of mail items of foreign media
`types. Each of the media file servers process and store
`mail of their respective media types. In addition, users
`at terminals associated with a particular server and
`media type are able to contact other media servers in
`the IMS network for mail functions of a different media
`type than that normally associated with the terminal.
`The IMP passes both messages and message pointers
`seamlessly from server to server in the IMS. However,
`most transactions do not require the actual message
`content, message pointers which are much smaller than
`the message content are passed and stored to reduce
`storage requirements and processing time. Further, a
`foreign message pointer is much easier to accommodate
`than a foreign message or unknown format.
`The servers 50, 52, 54 and 56 and the workstations 70,
`71, 72, 73, 80 and 82 preferably belong to the IBM line
`of the IBM PS/2 TM family of personal computers
`running on IBM’s OS/2 TM operating system software.
`As depicted in FIG. 1, servers 50, 52, 94, 56 are IBM
`Model 80 servers and workstations are PS/2 Model 50
`personal computers. They include well known compo-
`nents such as a system processor unit, ROM, RAM,
`hard and floppy disk drive storage, one or more system
`busses, a keyboard, a mouse and a display. The personal
`computers must also contain an I/O adapter card which
`allows communication between the MicroChanne1
`(TM) bus within the personal computer and the external
`bus, e.g., the Token Ring Network 60. Information on
`the PS/2 family can be found in Technical Reference
`Manual Personal System/2 (Model 50, 60 Systems) Part
`No. 68X2224 (S68X-2224) and Technical Reference
`Manual, Personal System/2 (Model 80) Part No.
`68X2256 (S68X-2256). Further information can be
`found on the Token Ring Network in “IBM Token-
`Ring Network Introduction” publication no GA27-
`3677 available from the IBM Corporation.
`Alternatively,
`the servers and workstations could
`belong to the IBM RISC System/6000 family of work-
`stations running on the AIX operating system. Further
`information on the RISC System/6000 can be found in
`IBM RISC System/6000 POWERstation and POWER-
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`50
`
`55
`
`65
`
`6
`server Hardware Technical Reference—General Infor-
`mation Manual (SA23-2643), IBM RISC System/6000
`POWERstation and POWERserver Hardware Techni-
`cal Reference Options and Devices (SA23-2646), IBM
`RISC System/6000 Hardware Technical Referen-
`ce——7012 POWERstation and POWERserver (SA23-
`2660), IBM RISC System/6000 Hardware Technical
`Reference——7013
`and
`7016 POWERstation
`and
`POWERserver
`(SA23—2644) and IBM RISC Sys-
`tem/6000 Hardware Technical Reference--7015
`POWERserver (SA23-2645).
`The terminals coupled to the IMS may be located
`within the same area or at a remote location. For exam-
`
`ple, workstation 70 may be located on the same desktop
`as phone 63, and workstation 72 may be located on the
`same desktop as phone 64. Workstations 71 and 73 may
`be coupled to the IMS by fiber optic cable several miles
`away in an area in which phones are not allowed, e. g.,
`certain government secure buildings, while phone 65 is
`located in a different city and state from the IMS. Phone
`65 could be located in an airport terminal, or a user’s car
`phone.
`Referring to FIG. 2, an architectural block diagram
`of the office server 52 is shown. Those skilled in the art
`use the terms “server” and “file server” to describe both
`
`the data processing system in charge of message process
`and control of a particular media type within the IMS
`and the software in the system which contains the sets
`of instructions which allow the data processing system
`to accomplish these functions. In the following descrip-
`tion, the terms “server” or “file server” will denote a
`piece of hardware, whereas the term “server software”
`is the code that drives the hardware. As shown in FIG.
`2, a memory 100 is coupled by means of a bus 101 to a
`central processing unit 102 an optional co-processor
`104, disk storage 106, display and keyboard adaptors
`108, floppy disk adaptor 110, CD ROM adaptor 112.
`The office server 52 communicate via to the token ring
`via network adaptor

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket