throbber
(12) United States Patent
`US 6,333,973 B1
`(10) Patent N0.:
`
`Smith et al.
`(45) Date of Patent:
`*Dec. 25, 2001
`
`U8006333973B1
`
`(54)
`
`INTEGRATED MESSAGE CENTER
`
`(75)
`
`Inventors: Colin Donald Smith, Ottawa; Brian
`Finlay Beaten, Orleans, both Of (CA)
`
`(73) Assignee: Nortel Networks Limited (CA)
`
`........................... 455/461
`4/1998 Pepe et a1.
`5,742,905 *
`...................... 455/419
`8/1998 Vantilla et a].
`5,794,142 *
`
`
`9/1998 GOkh'dlB ~~~~~~~~~~~~~~
`370524
`578157506 *
`5,842,141 * 11/1998 Vaihoja et a1.
`......
`455/574
`(List continued on next page.)
`FOREIGN PATENT DOCUMENTS
`
`(*) Notice:
`
`This patent issued on a continued pros-
`ecution application filed under 37 CER
`1.53(d), and is subject to the twenty year
`patent
`term provisions of 35 U.S.C.
`154(a)(2).
`
`Subject to any disclaimer, the term of this
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`(21) Appl. N0.: 08/842,020
`
`(22) Filed:
`
`Apr. 23, 1997
`
`(51)
`
`(52) U.S. Cl.
`
`Int. Cl? ........................... H04M 1/64; 1104M 11/00,
`H04M 3/42; H04Q 7/20
`.................. 379/8812; 379/671; 379/8811;
`379/88.22; 379/9308; 455/412; 455/413;
`455/466
`379/8801, 88.11,
`(58) Field of Search
`379/93.01, 93.08, 93.17, 100.01, 100.08,
`88.22, 111, 112, 113, 211, 230, 246, 88.12,
`114.06, 114.07, 88.23, 88.24; 455/445,
`517, 417, 459, 419, 433, 466, 422, 38.1,
`412, 413, 414; 370/347, 337, 349, 498,
`524; 341/20—23
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`7/1993 Kotzin ................................. 370/951
`5,228,029 *
`
`2/1994 Engberg etal.
`..... 348/14
`5,283,638 *
`7/1994 Wolfl etal.
`.. 379/96
`5,327,486 “
`7/1996 Robinson et al.
`379/88.25
`.
`5,533,102
`
`9/1996 Hyde-Thomson .
`.. 379/88
`5,557,659 *
`
`5,568,540 * 10/1996 Green et al.
`.. 379/88
`5,583,920 * 12/1996 Wheeler, Jr.
`.. 379/88
`5,608,786 *
`3/1997 Gordon ..........
`379/100
`
`
`2/1998 Serbetcionglu et a].
`5,719,918 *
`379/58
`
`0 630 141
`o 691 777
`wo 96 15490
`8268227
`
`12/1994 (EP) .
`1/1996 (EP) .
`5/1996 (EP) .
`10/1996 (JP) .
`OTHER PUBI .ICATI ONS
`
`Hattori et al., “A Multimedia Intelligent Message Commu-
`nication System for Distributed Coordination Environ-
`ments,” Electronics & Communications in Japan, Part
`1—Communications, vol. 76, No. 1, Jan. 1, 1993, pp. 11—23.
`“Nokia 9000 Communicator User’s Manual,” Nokia Cor—
`poration, 1996, pp. 1—1 through 16—1 (48 pages total).
`
`Primary Examiner—Allan Hoosain
`(74) Attorney, Agent, or Firm—Finnegan, Henderson,
`Farabow, Garrett & Dunner, L.L.P.
`
`(57)
`
`ABSTRACT
`
`An integrated message center operates on telecommunica-
`tions equipment, having a display and a processor, to con—
`solidate [messages of different types for viewing and manipu-
`lation by a user. The telecommunications equipment
`receives notification messages corresponding to pending
`[messages of different types and determines the message type
`of the pending messages. The integrated message center
`associates a message type indicator with each of the received
`notification messages based on the determined message type
`and displays on the display a portion of the received noti-
`fication messages and the associated message type indicators
`as entries in a single selectable list. The user can select one
`of the pending messages for retrieval based on the entries in
`the single selectable list. In response to user selection, the
`integrated message center retrieves the selected pending
`message for viewing and manipulation by the user.
`
`33 Claims, 16 Drawing Sheets
`
`1200
`
`5200
`
`5500
`
`64 kbls 1
`
`5600
`
`VOICE MAIL
`
`T1
`
`
`
`FAX MAIL
`SERVER
`
`E-MAIL
`SERVER
`
`5700
`
`5800
`
`BACKUP
`
`5900
`
`Google Ex. 1001, pg. 1
`
`5300
`
`TCP/IP
`
`
`
`
`
`
`
`TOP/1P
`
`Google Ex. 1001, pg. 1
`
`

`

`US 6,333,973 B1
`
`Page 2
`
`US. PATENT DOCUMENTS
`/.,.
`00
`’
`2,1999 B b H
`5/1999 Seppanen et al.
`5/1999 Foladare et al.
`6/1999 Rossman
`
`,/
`,
`'
`’
`58—0 549 *
`5,903,832 *
`5,905,959 *
`5,911,485 *
`
`
`
`.
`
`,/
`,
`305,200 36
`.455/414
`455/445
`34/22
`
`5,966,663 * 10/1999 Gleason ............................... 455/466
`
`
`9,
`,,
`,,
`,
`.
`,
`,
`.....................
`5
`*
`/
`.1
`6,055,424 *
`4/2000 Tornqvist et a].
`455/414
`0’20””9
`3/2001 V0“
`370389
`
`* Cited by examiner
`
`Google Ex. 1001, pg. 2
`
`Google Ex. 1001, pg. 2
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 1 0f 16
`
`US 6,333,973 B1
`
`F
`
`n
`Q
`LL
`
`O
`E
`
`(I)
`B
`5%
`LIJ
`m9
`>
`XQD
`[I
`OE
`...
`LIJ
`2
`
`EI
`
`0
`<3
`N
`x—
`
`
`
`
`
`
` GSMSWITCHING
`
`
`
`
`FABRIC
`
`1100
`
`Google Ex. 1001, pg. 3
`
`Google Ex. 1001, pg. 3
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 2 0f 16
`
`US 6,333,973 B1
`
`1100
`
`2100
`
`E] BRAD JOHNSON
`
`3).733302-4
`
`2300
`
`2400
`
`FIG. 2
`
`Google Ex. 1001, pg. 4
`
`Google Ex. 1001, pg. 4
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 3 0f 16
`
`US 6,333,973 B1
`
`omwm
`
`8mm886%;
`292923228oz>m<8mm83
`
`
`
`052MI
`
`Exfimm-I
`wmmosomzékmam<833%can85
`
`-.e<I58IE—.99E
`8%5805.mzoEgzzzzoo<>zzEz<
`<5E28
`
`
`
`oowm
`
`853382
`
`Emma
`
`ozajw.
`2%Iam
`
`mm:._.<m"_
`
`09$:12%20m:2:
`
`momwmoomm
`
`8%—2%225
`
`8%EEE$388%
`xo<n_ban—3wmn6‘l
`
`02.18.26
`
`Google Ex. 1001, pg. 5
`
`Google Ex. 1001, pg. 5
`
`
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 4 0f 16
`
`US 6,333,973 B1
`
`3440
`
`I
`
`GUI MANAGER
`
`USER APPLICATIONS
`
`SERVICES CLASS
`
`4100
`
`4200
`
`4300
`
`4400
`
`4600
`
`JAVA ENVIRONMENT
`
`RTOS UTILITIES
`
`4500
`
`DEVICE DRIVERS
`
`FIG. 4
`
`Google Ex. 1001, pg. 6
`
`Google Ex. 1001, pg. 6
`
`

`

`
`
`
`
`tmm>mmmm4_<_>_mo_o>Em2:2%.E9»:
`
`U.
`
`m
`
`PlS.8%8mm8%25
`
`D
`
`u,
`
`%
`
`5
`
`US 6,333,973 B1
`
`m8%4_<_>_-m
`
`mgm,Mmm>mmm
`
`8%6+
`
`wcomm
`
`x<“_
`
`25m8?,mm>mmmgigI$200m4_<_>_
`
`@(
`
`99¢,85
`
`0 o
`
`
`
`commn_DV,_O<m
`
`n._\n_0._.
`
`Google Ex. 1001, pg. 7
`
`Google Ex. 1001, pg. 7
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 6 0f 16
`
`US 6,333,973 B1
`
`738-91 57
`
`2400
`
`6200
`
`
`
`DIAL - QUIT
`{I’I’l/////// //
`.Adfizékdhv
`
`I
`
`3“." I'll
`
`.
`
`WWII/WW
`
`El") 521-6704
`
`NOTE QUICK
`PAD
`NOTESRfl
`
`FIG. 6
`
`Google Ex. 1001, pg. 8
`
`Google Ex. 1001, pg. 8
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 7 0f 16
`
`US 6,333,973 B1
`
`
`
`«.5.szw0<mmm2
`
`
`
`awhzmom®<mmm2
`
`>0;
`
`Hm:
`
`>D_._.
`
`Fm:
`
`
`
` 15$23@ZOwDDIQ_><n_Q“
`
`
`
` zomzzoq2mm@$50208E
`
`«6:5mzz<oq@SixESEWm
`
`comm
`
`Gown
`
`
`2033:
`
` mjmm:@mozozomm>mfimA:
`
`
`
` 20853,j_m@EEOZ08E
`
`>jmxWEE;@
`
`00:.
`
`OOMN
`
`oovx
`
`
`
`mO._><._.mzz<0w
`
`Mn.OE
`
`<5.QE
`
`Google Ex. 1001, pg. 9
`
`Google Ex. 1001, pg. 9
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 8 0f 16
`
`US 6,333,973 B1
`
`
`
`3an$895ammm
`
`
`
`ZMMDOQE_>:v_
`
` :30magmaxéfiwvvm
`5358:3a.
`
`
`
`
`
`3anmmBoEmcomm
`
`
`
`:30$2099vdevv
`
`a)
`
`EBA?SEam1.5552:00
`
`Um_o.,\._:_.OoOHszFOmmE
`
`oouw._.<m_OZ_._.m_m=>_
`
`
`
`.2m_GZPmmEwI._.._I
`
`
`
`2_m_.:FIQZOFComm.
`
`
`
`
`
`20N903Z_owqoogm.IO_I>>Hmm>>000
`
`mszz550502
`
`
`
`534mm5249E
`
`Mm.OE
`
`b i_v_o<._m_My
`
`M.
`
`
`
`$004“.QZOOmwmIH
`
`.mmmflr30>mwm
`
`
`
`m§<zx050Eoz
`
`
`
`53485249E
`
`<m.GE
`
`Google Ex. 1001, pg. 10
`
`Google Ex. 1001, pg. 10
`
`
`
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 9 0f 16
`
`US 6,333,973 B1
`
`
`
`m_<wm_>>mE3.Qmm$o¥m00mm
`
`
`
`58-5123n._m_
`
`3anmmBoEm
`
`
`
`E89?8:;1mI._.:>_w2300
`
`
`
`:30Qm<om5XJEME
`
`v
`
`
`
`.53092090v*._<._w
`
`v
`
`comm
`
`
`
`mmozzzmm._.Io_.E
`
`OHzOmOkA<>mzm©
`
`
`
`.52de._.__>>
`
`
`
`mo._><._.Xm._<
`
`._.IO_.Em30>
`
`30>xz<IH
`
`a?._.<5nmbqo
`
`mmo_wz_m2:@504:H<I>>”5{$9©mmtmm<Go9PEMQOwEmE.
`._._m_>
`
`OHIm_>>30>00
`
`mom<0mm
`
`2:00
`
`
`
`m:>_<Zx050m:.OZ
`
`
`
`
`
`Fm::mmFOZOdd
`
`Mm.OE
`
`«6.0E
`
`Google Ex. 1001, pg. 11
`
`Google Ex. 1001, pg. 11
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 10 0f 16
`
`US 6,333,973 B1
`
`BRIAN BEATON
`(613) 238-6602
`
`[3]")
`
`
`
`
` RECD 24/06/9513214
`<(@TALK DISCARD QUIT
`
`
`E2
`
`RWND
`\I\I
`
`PAUSE
`F I"
`
`PLAY
`I\
`
`
`
`NOTE OUICK NAME
`PAD
`NOTES LIST
`
`
`
`FIG. 10
`
`Google Ex. 1001, pg. 12
`
`Google Ex. 1001, pg. 12
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 11 0f 16
`
`US 6,333,973 B1
`
`CDG STUDIO
`
`FOEWARD TO:
`
`F
`
`HOME
`
`AX OTHER
`
`F
`
`NAME
`
` RECD 24/06/9513:14
`
`
`
`
`I.7656775
`V-EW D_SCARD QU-T
`
`
`
`IE?!
`
`
`
`
`
`
`
`
`
`FAX NUMBER
`
`NOTE OUICK NAME
`PAD
`NOTES LIST
`
`FIG. 11
`
`Google Ex. 1001, pg. 13
`
`Google Ex. 1001, pg. 13
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 12 0f 16
`
`US 6,333,973 B1
`
`COLIN SMITH
`
`El] smith@nortel.ca
`
`C@
`
`TALK DISCARD QUIT
`
`TO: ANDREW CONNELLY
`
` RECD 24/06/95 13: 14
`
`
`
`
`
`
`FROM: COLIN SMITH @
`
`
`RE: WEDNESDAY
`MORNINGS SALES
`
`MEETING
`
`
`
`
`
`
`
`THE WEDNESDAY
`
`MORNING SALES MEETING
`
`WILL BE HELD AT 9:00
`
`
`
`NOTE OUICK NAME
`PAD
`NOTES LIST
`
`FIG. 12
`
`Google Ex. 1001, pg. 14
`
`Google Ex. 1001, pg. 14
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 13 0f 16
`
`US 6,333,973 B1
`
`‘Il
`
`.530
`
`5.500$2
`
`mem-Ev62$
`
`:Hm
`
`
`
`
`
`90mmHmfiDOO0m<_>_vmmBoEm
`
`
`
`.EDOQm<om_n_x._<._ww
`
`v
`
`58ngGEcw
`
`.2:0»FE:5mwioufiv)
`
`m_>_<zV550
`
`5:43524,”
`
`
`
`mm...“.OE
`
`
`
`
`
`.zfe7:rm.4.5.40
`
`|\|\l
`
`[I'll
`
`3:3$00.5
`
`02?me785m
`
`
`
`m__>_<Zx050mFOZamkm«Row
`
`
`
`
`
`Hm::mmFOZD<n_
`
`Sm.F.GE
`
`Google Ex. 1001, pg. 15
`
`Google Ex. 1001, pg. 15
`
`
`
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 14 of 16
`
`US 6,333,973 B1
`
`._.Zm_wmFOZ
`
`QEOO<m_><m
`
`H50
`
`.lfifia
`
`
`
`rmmm-nmv8:;
`
`
`
`.75th7:Tm..kaw
`
`.E«6%5w:3
`
`35853
`
`
`
`
`
`QM“.OEUm.“.OE
`
`Google Ex. 1001, pg. 16
`
`Google Ex. 1001, pg. 16
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 15 0f 16
`
`US 6,333,973 B1
`
`n5OZ<I
`
`
`
`5.500om<2E
`
`amméimimm.
`
`m_>_<z550E02
`
`
`
`5365029E
`
`a
`
`
`
`m“;.OE
`
`
`
`3anmaEEvmcomm
`
`
`Imam-Ev33gmHMISOO
`
`I50im<omalIi4<wmwy
`0m<_>_
`
`.2:9.5w:3..
`amzougmv)
`
`
`
`
`
`.7597:rm.”.520
`
`Ill-
`
`Ill
`
`
`
`zwflgp15002E
`
`
`
`92,Vmwi28.903
`
`Nfllfimdnrnu
`
`
`
`m=>_<Zx050mFOZ
`
`
`
`
`
`._.w_._:meOZD<n_
`
`
`
`31‘.GE
`
`Google Ex. 1001, pg. 17
`
`Google Ex. 1001, pg. 17
`
`
`
`
`

`

`US. Patent
`
`Dec. 25, 2001
`
`Sheet 16 0f 16
`
`US 6,333,973 B1
`
`
`
`who'22i<mm
`
`I._.__>_mmz<w
`
`N08-mmman:A,
`
`20mmm:.OZ
`
`
`
`m2..GE
`
`
`
`EbHmEIamoo<
`
`1:55mz<_,
`
`N08-wmm$51..
`
`
`
`.EOWE._|_<O
`
`
`
`«‘2‘.GE
`
`Google Ex. 1001, pg. 18
`
`Google Ex. 1001, pg. 18
`
`
`
`

`

`US 6,333,973 B1
`
`1
`INTEGRATED MESSAGE CENTER
`
`RELATED APPLICATIONS
`
`This application is related to US. patent application, Ser.
`No. 08/842,015, entitled MULTITASKING GRAPIIICAL
`USER INTERFACE; US patent application, Ser. No.
`08/841,485, entitled ELECTRONIC BUSINESS CARDS;
`U.S. patent application, Ser. No. 08/841,486, entitled
`SCROLLING WITH AUTOMATIC COMPRESSIONAND
`EXPANSION; US patent application, Ser. No. 08/842,019,
`entitled CLID W'ITII LOCATION ICON; U.S. patent
`application, Ser. No. 08/842,017, entitled CLID WITH
`DRAG AND DROP CAPABILITY; and Us. patent
`application, Ser. No. 08/842,036, entitled ICONIZED
`NAME LIST, all of which were filed concurrently herewith,
`and all of which are hereby incorporated by reference.
`BACKGROUND OF THE INVENTION
`
`This invention relates to the field of message handling,
`and more specifically to the field of message presentation to
`a user by which messages of all types are consolidated and
`graphically displayed in a searcliable list to allow for easy
`graphical scanning, prioritizing, editing, selection, viewing,
`forwarding, playback, and response by the user.
`Traditionally, a user could retrieve only voice messages
`by calling and interacting with a voice mail service using
`dual
`tone multi-frequency (DTMF) commands. Such
`retrieval of messages, however, required the user to dial the
`voice mail service and listen to each message, or minimally
`the header of each message, that is, the name of the person
`and the time received. This type of voice mail retrieval
`tended to be a slow and tedious process.
`Additionally,
`the user needed to memorize the DTMF
`number commands to control the voice mail service. Some-
`times these commands were different for the user’s home
`voice mail service and the user’s o dice voice mail service.
`For example, the user needed to remember that pressing “1”
`with the office voice mail service, while pressing “6” with
`the home voice mail service, meant “play the message.”
`More recently, telephones have 36611 designed with the
`capability to directly receive, or download, dilferent types of
`messages, such as faxes, e-mail, and Short Messaging Ser-
`vice (SMS) messages. One conven ional mobile telephone
`
`has a display, a keypad, and numerous hard keys, and uses
`
`menus to enable a riser to View di ‘erent types of received
`messages.
`When a message arrives, an internal processor detects the
`message type and stores the message in a folder dedicated to
`the message type.
`If the telephone receives a fax,
`for
`example, the internal processor stores the fax in a fax folder.
`When the user opens the cover to the display, the internal
`processor displays a note indicating the quantity and type of
`messages received. For example, if two faxes and two SMS
`messages have been received, the note will show “You have:
`2 unread faxes and 2 unread short messages.”
`If the user wants to view a received message, the user first
`goes to the main menu and selects the type of message to
`View. This causes the internal processor to launch a
`message—type specific application to retrieve the message
`from the message folder and display it for the user. For
`example, if the user wants to read a received fax, the user
`selects “Received faxes” from the main menu. In response,
`the internal processor launches the fax application to display
`a list of received faxes. From the list, the user selects a
`particular fax to read. The fax application then displays the
`selected fax.
`
`
`
`5
`
`10
`
`tom
`
`30
`
`L» .n
`.
`
`40
`
`50
`
`60
`
`2
`If the user then wanted to View a received SMS message,
`however, the user must return to the main menu to select
`“Received short messages.” In response, the internal pro-
`cessor launches the SMS application to display a list of
`received SMS messages from which the user selects the
`desired one.
`
`Telephones of this type, however, sulfer from a number of
`drawbacks. First,
`they store in their internal memory all
`received messages, except voice and e—mail messages which
`are stored at an external server. This wastes precious
`memory space, and as a result, fewer messages can be
`locally stored.
`Additionally, message handling is cumbersome because
`the telephones are menu driven and contain separate appli—
`cations for the dilferent message types. To View different
`types of messages, the user must follow a series of menus
`that cause specific applications to be executed.
`Therefore, a need exists to integrate different types of
`messages from different types of equipment into one graphi—
`cal location to notify the user of pending messages and their
`type, and to allow the user to view and respond to the
`messages by simple operation.
`SUMMARY OF THE INVENTION
`
`Systems and methods consistent with the present inven—
`tion address this need by providing an integrated message
`center that graphically displays different types of received
`messages together to facilitate user viewing and manipula—
`tion of the messages without having to follow a series of
`menus or launch separate applications.
`In accordance with the purpose of the invention as
`embodied and broadly described herein, an integrated mes-
`sage center consistent with the principles of the present
`invention operates on telecommunications equipment, hav-
`
`ing a display and a processor, to consolidate messages of
`
`
`
`di erent types for viewing and manipulation by a user. The
`telecommunications equipment receives notification mes-
`sages corresponding to pending messages of different types
`and determines the message type of the pending messages.
`The integrated message center associates a message type
`indicator with each of the received notification messages
`based on the determined message type and displays on the
`display a portion of the received notification messages and
`the associated message type indicators as entries in a single
`selectable list. The user can select one of the pending
`messages for retrieval based on the entries in the single
`selectable list. In response to user selection, the integrated
`message center retrieves the selected pending message for
`viewing and manipulation by the user.
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`The accompanying drawings, which are incorporated in
`and constitute a part of this specification, illustrate systems
`and methods consistent with this invention and, together
`with the description, explain the objects, advantages and
`principles of the invention. In the drawings,
`FIG. 1 is a diagram of a communications network con-
`taining the integrated message center consistent with the
`principles of the present invention;
`FIG. 2 is a diagram of the user mobile telephone operating
`in the network of FIG. 1;
`FIG. 3 is a block diagram of the elements included in the
`user mobile telephone of FIG. 2;
`FIG. 4 is a block diagram of the software components
`stored in the flash ROM of FIG. 3,
`
`Google Ex. 1001, pg. 19
`
`Google Ex. 1001, pg. 19
`
`

`

`US 6,333,973 B1
`
`3
`FIG. 5 is a block diagram of the elements included in the
`network services provider of FIG. 1;
`FIG. 6 is an example of an idle screen of the user mobile
`telephone shown in FIG. 2;
`FIGS. 7A and 7B are example displays of received
`messages;
`FIG. 8A is an example display of a received SMS text
`message;
`FIG. 8B is an example display of a received electronic ink
`message;
`FIGS. 9A and 9B are example displays of SMS text
`messages with hypertext markup language code;
`FIG. 10 is an example display in which the user selects to
`listen to a voice mail message;
`FIG. 11 is an example display in which the user selects to
`forward a fax;
`FIG. 12 is an example display of a received e-mail
`message;
`FIGS. 13A through 13D are example displays in which
`the user responds to an ink message by sending an SMS
`message;
`FIGS. 14A and 14B are example displays in which the
`user responds to an ink message by establishing a voice call;
`and
`
`FIGS. 15A and 15B are example displays in which the
`user receives a voice call and an SMS message, respectively.
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`
`The following detailed description of the invention refers
`to the accompanying drawings that
`illustrate preferred
`embodiments consistent with the principles of this inven-
`tion. Other embodiments are possible and changes may be
`made to the embodiments without departing from the spirit
`and scope of the invention. The following detailed descrip-
`tion does not limit the invention. Instead, the scope of the
`invention is defined only by the appended claims.
`The integrated message center consistent with the prin-
`ciples of the present invention displays different types of
`received messages in a single display and permits manipu—
`lation of the messages by a user, such that the user can view,
`discard, forward, and respond to any type of message
`without the need to launch different applications.
`I. System Architecture
`FIG. 1 is a diagram of a communications network con-
`taining the integrated message center consistent with the
`principles of the present invention. The integrated message
`center is a logical entity that resides in mobile telephone
`1100 and operates in conjunction with network services
`provider 1200 to inform a user of incoming and pending
`messages, such as fax mail, e-mail, voice mail, etc. The
`integrated message center also serves as a mechanism by
`which the user can retrieve, manipulate, and reply to all
`types of messages. User manipulation of the pending mes-
`sages might
`include the ability to view, prioritize, edit,
`playback, discard, and/or forward messages.
`The user uses mobile telephone 1100 to view messages
`from callers having different types of caller equipment, such
`as ordinary telephone 1300, caller mobile telephone 1400
`which is similar to user mobile telephone 1100, facsimile
`equipment 1500, computer 1600, and Analog Display Ser-
`vices Interface (ADSI) telephone 1700. The callers leave
`different types of messages for the user, depending upon the
`type of caller equipment.
`
`10
`
`tom
`
`30
`
`4
`Network services provider 1200 stores many of the mes—
`sages awaiting retrieval by the user and notifies the user of
`the pending messages. Subscriber mobile telephone 1100
`and caller equipment 1300 through 1700 communicate with
`network services provider 1200 over a communications
`network, such as Global System for Mobile Communica-
`tions (GSM) switching fabric 1800.
`While FIG. 1 shows caller equipment 1300 through 1700
`directly connected to GSM switching fabric 1800, this is not
`typically the case. Telephone 1300, facsimile equipment
`1500, computer 1600, and ABS] telephone 1700 normally
`connect to GSM switching fabric 1800 via another type of
`network, such as a Public Switched Telephone Network
`(PSTN).
`When a caller uses telephone 1300 to communicate with
`the user, the caller dials the telephone number corresponding
`to mobile telephone 1100. If the user does not answer the call
`for a predetermined number of rings, or upon direction of the
`user (to be described), the call routes to network services
`provider 1200 over GSM switching fabric 1800 by conven-
`tional mechanisms. Network services provider 1200 stores
`the message left by the caller as voice mail and sends a short
`message to mobile telephone 1100, notifying the user of the
`pending voice mail message.
`When the caller uses caller mobile telephone 1400 to
`communicate with the user, the caller may either call the
`user, as described above with regard to telephone 1300, or
`may send the user a Short Messaging Service (SMS) mes-
`sage. GSM networks typically include an SMS server that
`provides the SMS service. The SMS service is an error-free,
`guaranteed delivery transport mechanism by which callers
`can send short point—to—point messages, i.e., SMS messages,
`through the GSM network, such as GSM switching fabric
`L» .n
`1800, in a GSM signaling channel, simultaneously with, or
`‘ without, a voice or data call.
`GSM protocol limits the length of the standard SMS text
`message to a maximum of 140 bytes. However, GSM
`protocol permits longer messages to be formed by concat-
`enating several messages together, transparent to the caller.
`Because GSM protocol transparently performs this concat—
`enating of messages, the caller sees no restriction on mes-
`sage length.
`If the caller chooses to send the user an SMS message, the
`caller inputs the message data, and selects a destination
`corresponding to the user. GSM switching fabric 1800
`routes the message to an SMS server that services the area
`containing mobile telephone 1100, and the SMS server, in
`turn, relays the message to the user.
`When the caller uses facsimile equipment 1500 to send a
`fax to the user, the caller dials the fax telephone number
`corresponding to network services provider 1200. The caller
`sends the fax to network services provider 1200. Network
`services provider [200 stores the fax and then sends a short
`message to mobile telephone 1100, notifying the user of the
`pending fax.
`When the caller uses computer 1600 to send an e-mail
`message to the user, the caller enters the message into the
`computer and affixes the user’s e—mail address. The user’s
`e-mail address directs the e-mail message to network ser-
`vices provider 1200. Network services provider 1200 stores
`the e—mail message, and then sends a short message to
`mobile telephone 1100, notifying the user of the pending
`e-mail message.
`When the caller uses ADSI telephone 1700 to communi-
`cate with the user,
`the caller dials the telephone number
`corresponding to mobile telephone 1100, as described above
`
`40
`
`50
`
`60
`
`Google Ex. 1001, pg. 20
`
`Google Ex. 1001, pg. 20
`
`

`

`US 6,333,973 B1
`
`5
`with regard to telephone 1300. If the user does not answer
`the call for a predetermined number of rings, or upon
`direction of the user, the call routes to network services
`provider 1200 over GSM switching fabric 1800 by conven—
`tional mechanisms. Network services provider 1200 stores
`the message left by the caller as voice mail and sends a short
`message to mobile telephone 1100, notifying the user of the
`pending voice mail message.
`Mobile telephone 1100 provides a user friendly interface
`to facilitate message retrieval, manipulation, and response
`by the user. FIG. 2 is a diagram of mobile telephone 1100,
`including main housing 2100, antenna 2200, keypad 2300,
`and display 2400.
`FIG. 3 is a block diagram of the hardware elements of
`mobile telephone 1100, including antenna 3100, communi-
`cations module 3200, feature processor 3300, memory 3400,
`sliding keypad 3500, analog controller 3600, display module
`3700, battery pack 3800, and switching power supply 3900.
`Antenna 3100 transmits and receives radio frequency
`information for mobile telephone 1100. Antenna 3100 pref—
`erably comprises a planar inverted F antenna (PIFA)-type or
`a short stub (2 to 4 cm) custom helix antenna. Antenna 3100
`communicates over GSM switching fabric 1800 using a
`conventional voice B-channel, data B-channel, or GSM
`signaling channel connection.
`Communications module 3200 connects to antenna 3100
`and provides the GSM radio, baseband, and audio function—
`ality for mobile telephone 1100. Communications module
`3200 includes GSM radio 3210, VEGA 3230, BOCK 3250,
`and audio transducers 3270.
`
`GSM radio 3210 converts the radio frequency information
`to/from the antenna into analog baseband information for
`presentation to VEGA 3230. VEGA 3230 is preferably a
`Texas Instruments VEGA device, containing analog—to—
`digital (A/D)/digital-to-analog (D/A) conversion units 3235.
`VEGA 3230 converts the analog baseband information from
`GSM radio 3210 to digital information for presentation to
`BOCK 3250.
`
`BOCK 3250 is preferably a Texas Instruments BOCK
`device containing a conventional ARM microprocessor and
`a conventional LEAD DSP device. BOCK 3250 performs
`GSM baseband processing for generating digital audio sig-
`nals and supporting GSM protocols. ROCK 3250 supplies
`the digital audio signals to VEGA 3230 for digital—to—analog
`conversion. VEGA 3230 applies the resulting analog audio
`signals to audio transducers 3270. Audio transducers 3270
`include speaker 3272 and microphone 3274 to facilitate
`audio communication by the user.
`Feature processor 3300 provides graphical user interface
`features and a Java Virtual Machine (JVM). Feature proces-
`sor 3300 communicates with BOCK 3250 using high level
`messaging over an asynchronous (UART) data link. Feature
`processor 3300 contains additional system circuitry, such as
`a liquid crystal display (LCD) controller, timers, UART and
`bus interfaces, and real time clock and system clock gen-
`erators (not shown).
`Memory 3400 stores data and program code used by
`feature processor 3300. Memory 3400 includes static RAM
`3420 and flash ROM 3440. Static RAM 3420 is a volatile
`memory that stores data and other information used by
`feature processor 3300.
`Flash ROM 3440 is a non—volatile memory that stores the
`program code and directories utilized by feature processor
`3300. FIG. 4 is a block diagram of the software components
`of flash ROM 3440. ROM 3440 includes graphical user
`interface (GUI) manager 4100, user applications 4200, ser-
`
`6
`vice classes 4300, Java environment 4400, real time oper—
`ating system (RTOS) utilities 4500, and device drivers 4600.
`GUI manager 4100 acts as an application and window
`manager. GUI manager 4100 oversees the user interface by
`allowing the user to select, run, and otherwise manage
`applications.
`User applications 4200 contain all the user-visible appli-
`cations and network service applications. User applications
`4200 preferably include a call processing application for
`processing incoming and outgoing voice calls, a message
`processing application for sending and receiving short
`messages, a directory management application for managing
`database entries in the form of directories, a web browser
`application, and other various applications.
`Service classes 4300 provide a generic set of application
`programming facilities shared by user applications 4200.
`Service classes 4300 preferably include various utilities and
`components, such as a Java telephony application interface,
`a voice and data manager, directory services, voice mail
`components, text/ink note components, e-mail components,
`fax components, network services management, and other
`miscellaneous components and utilities.
`Java environment 4400 preferably includes a JVM and the
`necessary run—time libraries for executing applications writ—
`ten in the JavaTM programming language.
`RTOS utilities 4500 provide real time tasks, low level
`interfaces, and native implementations to support Java envi-
`ronment 4400. RTOS utilities 4500 preferably include Java
`peers, such as networking peers and Java telephony peers,
`optimized engines requiring detailed real time control and
`high performance, such as recognition engines and speech
`processing, and standard utilities, such as protocol stacks,
`memory managers, and database packages.
`Device drivers 4600 provide access to the hardware
`elements of mobile telephone 1100. Device drivers 4600
`include, for example, drivers for sliding keypad 3500 and
`display module 3700.
`Returning to FIG. 3, sliding keypad 3500 enables the user
`to dial a telephone number, access remote databases and
`servers, and manipulate the graphical user interface features.
`Sliding keypad 3500 preferably includes a mylar resistive
`key matrix that generates analog resistive voltage in
`response to actions by the user. Sliding keypad 3500 pref-
`erably connects to main housing 2100 (FIG. 2) of mobile
`telephone 1100 through two mechanical “push pin”-type
`contacts.
`
`Analog controller 3600 is preferably a Phillips UCB1100
`device that acts as an interface between feature processor
`3300 and sliding keypad 3500, Analog controller 3600
`converts the analog resistive voltage from sliding keypad
`3500 to digital signals for presentation to feature processor
`3300.
`
`Display module 3700 is preferably a 160 by 320 pixel
`LCD with an analog touch screen overlay and an electrolu-
`minescent backlight. Display module 3700 operates in con—
`junction with feature processor 3300 to display the graphical
`user interface features.
`
`Battery pack 3800 is preferably a single lithium-ion
`battery with active protection circuitry. Switching power
`supply 3900 ensures highly elficient use of the lithium-ion
`battery power by converting the voltage of the lithium-ion
`battery into stable voltages used by the other hardware
`elements of mobile telephone 1100.
`These hardware elements of mobile telephone 1100 per—
`mit the user to communicate with network services provider
`
`10
`
`tom
`
`30
`
`L»LA
`
`40
`
`50
`
`60
`
`Google Ex. 1001, pg. 21
`
`Google Ex. 1001, pg. 21
`
`

`

`US 6,333,973 B1
`
`7
`1200 (FIG. 1) to retrieve pending messages. FIG. 5 is a block
`diagram of the elements of network services provider 1200,
`including interface 5100, transcoder and rate adapter unit
`(TRAU) 5200, SMS server 5300,
`interworking function
`(IWF) servers 5400 and 5500, voice mail server 5600, fax
`mail server 5700, e-mail server 5800, and backup 5900.
`Interface 5100 interfaces the elements of network services
`provider 1200 to GSM switching fabric 1800. TRAU 5200
`performs GSM-specific speech encoding and decoding and
`rate adaption of voice signals received from mobile tele-
`phone 1100 for transmission to a destination network, such
`as a PSTN, and vice versa. TRAU 5200 is a conventional
`hardware device that converts, for example, voice signals to
`or from 64 kb/s pulse code modulated (PCM) and 13 kb/s
`RPE—LTP signals.
`SMS server 5300 provides the SMS service for GSM
`switching fabric 1800. SMS server 5300 is a conventional
`hardware device that processes SMS messages. SMS server
`5300 preferably relays SMS messages to or from mobile
`telephone 1100, and notifies the user of pending messages
`via SMS notification messages. SMS server 5300 transmits
`SMS messages, including notification messages, on mobile
`telephone 1100’s GSM signaling channel, which is indepen-
`dent of mobile telephone 1100’s voice and data B-channels.
`IWF servers 5400 and 5500 convert data received from
`mobile telephone 1100 to a format suitable for transmission
`to a destination network. IWF servers 5400 and 5500 are
`conventional hardware devices that provide an interface
`between dissimilar networks.
`IWF server 5400 connects to interface 5100. When the
`user exchanges data with a terminal in a PSTN, for example,
`IWF server 5400 provides a digital interface for transmis-
`sion toward mobile telephone 1100 and a modem interface
`for transmission toward the PSTN. IWF server 5400 pref-
`erably handles conversions to or from transmission control
`protocol (TCP) and Internet protocol (IP). IWF server 5500
`operates similar to IWF server 5400. IWF server 5500,
`however, connects to interface 5100 through TRAU 5200
`and processes mainly voice data.
`Voice mail server 5600 processes and stores voice mes—
`sages for the user. When a caller leaves a voice message,
`voice mail server 5600 stores the message at a location
`corresponding to the user and informs SMS server 5300 of
`the pending message. Voice mail server 5600 also notifies
`SMS server 5300 of the identity and telephone number of the
`caller which voice mail server 5600 obtains from the caller’s
`telephone signal or from a local database. Voice mail server
`5600 might make this notification via a direct connection to
`SMS server 5300 (not shown), or might alternatively, make
`the notification via a modem connection.
`In response to the notification from voice mail server
`5600, SMS server 5300 formulates an SMS voice mail
`notification message to notify the user of the voice mail
`message. The voice

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