Apple Exhibit 1006 Page 00001
`
`

`
`US 6,333,973 B1
`Page 2
`
`US. PATENT DOCUMENTS
`
`,
`,
`5 870 549 *
`5,903,832 *
`5,905,959 *
`5,911,485 *
`
`.
`........................ ..
`0 0,
`395/200 36
`2/1999 B b H
`
`455/414
`5/1999 Seppanen et al.
`.
`................... .. 455/445
`5/1999 Foladare et al.
`6/1999 Rossman ................................ .. 34/22
`
`5,966,663 * 10/1999 Gleason ......... ..
`
`.
`455/414
`4/2000 Tornqvist et al.
`3/2001 V01t
`.................................... .. 370/389
`
`6,055,424 *
`6,205,139 *
`
`455/466
`
`.
`.
`* cued by exammer
`
`Page 00002
`
`
`Page 00002
`
`

`
`U.S. Patent
`
`Dec. 25, 2001
`
`Sheet 1 of 16
`
`US 6,333,973 B1
`
`fi
`
`I
`9
`LL
`
`CD
`E
`
`
`
`
`(D
`E)-I
`3g
`%9
`>
`KO
`(10:
`
`3I
`
`-
`LU
`2
`
`0
`0
`N
`
`Page 00003
`
`
`
` GSMSWITCHING“00FABRIC
`
`
`
`E
`1’ 2‘EIa: E.
`
`
`
`
`Page 00003
`
`

`
`U.S. Patent
`
`Dec. 25, 2001
`
`Sheet 2 of 16
`
`US 6,333,973 B1
`
`1100
`
`2100
`
`@3@
`E] BRAD JOHNSON
`
`@(e1
`
`3) 733-8024
`
`Q |2400
`
`WMMW
`
`2300
`
`Page 00004
`
`
`Page 00004
`
`

`
`U.S. Patent
`
`0~mv_<mn_m
`
`o_%<
`
`m%o:omz<E
`
`
`
`mSoo_>_mzo_._.<o_z:_>_s_oo
`
`83
`
`<zzm_._.z<
`
`M“w
`
`Mm.,
`
`M
`
`1BB
`
`
`
`%zo:<o_z:_>_s_oooz>m<
`
`6%_EInm02,9Mozazm.o9<z<
`
`mommmoomm
`
`2.:
`
`8
`so,
`
`8
`3..
`
`j2%oE:mjzom:2:
`
`S8%m:8os_UEfiwa
`
`
`
`mcam5:mg%>%E<moz_Io:>>m
`
`8%
`
`M.0?‘
`
`Page 00005
`
`
`Page 00005
`
`
`
`
`

`
`U.S. Patent
`
`Dec. 25, 2001
`
`Sheet 4 of 16
`
`US 6,333,973 B1
`
`3440
`
`GUI MANAGER
`
`USER APPLICATIONS
`
`SERVICES CLASS
`
`JAVA ENVIRONMENT
`
`4100
`
`4200
`
`4300
`
`4400
`
`RTOS UTILITIES
`
`4500
`
`DEVICE DRIVERS
`
`4600
`
`FIG. 4
`
`Page 00006
`
`
`Page 00006
`
`

`
`
`
`
`
`tmm_>mm_mm.__<_>_mo_o>E“:2.a,\e_E:<E
`
`U.
`
`w.P
`
`S.88comm8%o3
`
`.5,
`
`mS
`
`0
`
`US 6,333,973 B1
`
`4_<_>_X<n_
`
`
`
` m_>_m1mm>mmm...__Eo»waxnom8?.
`
`w88Dz
`
`997085
`
`0 O
`
`
`
`asm3m_§.m.”_m
`
`8%n_Dv_0<m
`
`m03
`
`8%\o+
`
`Page 00007
`
`
`Page 00007
`
`
`

`
`U.S. Patent
`
`Dec. 25,2001
`
`Sheet 6 of 16
`
`US 6,333,973 B1
`
`2400
`
`-'-'.£-
`
`..
`
`
`
`
`
`
`
`6200
`
`
`
`
`
`
`BCH3BY’BCNflHTD
`
`738-9157
`
`DDAL ININNHNII CDUFT
`:""///../..,//,z/,,/,/
`
`"71" Ill:
`
`;/""M././/.///4/4,,/,///
`F\
`
`
`
`
`
`
`gr’ 521-6704
`
`NOTE OUICK
`
`
`
`
`
`
`FIG. 6
`
`Page 00008
`
`
`Page 00008
`
`

`
`tnCtaP3U
`
`D
`
`Mm
`
`7m
`
`M
`
`m6S
`
`3
`
`.5B:m:30E:
`
`
`
`mmfizmomo<mmm_>_
`
`MdEozwooE._m_EozwooE
`
`oomn
`
`8:
`
`
`
`
`
`zomz:o_,o<mm@zomv_o<_,j_m@82
`
`
`
`UmO4><_.m_zz<ow@
`
`
`
`>jm_v_mm_.En_Hm>jm§EmaEM
`
`7IIwmuGE«KOE
`
`1M...Bm
`
`9MM
`
`
`Page 00009
`
`
`

`
`
`
`_m8-Ew62¢Lmzmmaooz_>__v_
`
`
`
`
`
`3”?$52:comm
`
`U.S.Patent
`
`
`
`.3”?852:comm
`
`Dec.25,2001
`
`
`
`E30Eémav_._<._w&
`
`V
`
`
`
`E30om<om_ov:<$.
`
`
`
`58%?6:;amI._.__>_wZ_._OO
`
`mo<tooOHmzo_5mm_o
`
`Sum._.<m_oz:mm__>_
`
`Sheet8of16
`
`
`
`ZONm<._Z_Dm._.<OO:_m.IO_I>>Gm;000
`
`
`
`moodozoommmm»
`
`
`
`
`
`.r<m_wz_Em_>_m_I._.._I
`
`
`
`Z_w..:.5920»comm
`
`mmmze30>mmm
`
`ms_<z550E02
`
`
`
`B:4mm:oz4D<n_
`
`mmGE
`
`US6,333,973B1
`
`ms_<z550E02
`
`
`
`5:4mm:oz495
`
`<m.03
`
`Page 00010
`
`
`Page 00010
`
`
`
`
`
`

`
`U.S. Patent
`
`Dec. 25,2001
`
`Sheet 9 of 16
`
`US 6,333,973 B1
`
`
`
` 5.8-»?63amm_<mm_>>mB3:33325.8mm
`
`
`
`E30Eémav:<$.
`
`
`
`En_z__>_mm._.IO_._..._
`
`929.9A<>mzm_o
`
`
`
`mO._><._.xm._<
`
`._.I0_.E~59
`
`
`
`._.m<n_mQ.j_>>
`
`30>v_z<E
`
`E”?._.<5m:.<0
`
`mm.0?‘
`
`.3.03
`
`Page 00011
`
`_._._.<_._>>n_O$9©mmtmm<E09>.Emn_Ow_n_m=.:.
`._._m_>
`
`
`
`m5_wz_m_v__._959
`
`OHIw_>>30>on
`
`m9_<omm
`
`mm;
`
`_>_<zHH2:8
`9EmV550Eoz$524
`
`5: 4
`
`
`
`3,22852%comm
`
`
`
`Emma?63;am_¢__>_wZ_._OO
`
`._._DO9_<om_ox:_<._wx
`
`V
`
`
`
`
`
`
`Page 00011
`
`

`
`U.S. Patent
`
`Dec. 25, 2001
`
`Sheet 10 of 16
`
`US 6,333,973 B1
`
` RECD 24/O6/9513:14
`
`BRIAN BEATON
`(613) 238-6602
`5]")
`<<GTALK DISCARD QUIT
`
`
`
`NOTE OUICK NAME
`PAD
`NOTES LIST
`
`
`
`FIG. 10
`
`Page 00012
`
`
`
`RWND
`\l\l
`
`PAUSE
`F I"
`
`PLAY
`I\
`
`
`Page 00012
`
`

`
`U.S. Patent
`
`Dec. 25, 2001
`
`Sheet 11 of 16
`
`US 6,333,973 B1
`
`CDG STUDIO
`
`765-6775
`
`VIEW DISCARD QUIT
`
`FOEWARD TO:
`
` RECD 24/O6/9513114
`
`
`
` NUMBER
`
`
`NOTE OUICK NAME
`PAD
`NOTES LIST
`
`FIG. 11
`
`
`
`Page 00013
`
`
`Page 00013
`
`

`
`U.S. Patent
`
`Dec. 25, 2001
`
`Sheet 12 of 16
`
`US 6,333,973 B1
`
`COLIN SMITH
`
`[EU smith@nortel.ca
`
` RECD 24/O6/9513214
`
`
`
`
`
`
`[§‘TALK DISCARD QUIT
`
`TO: ANDREW CONNELLY
`
`FROM: COLIN SMITH @
`
`RE: WEDNESDAY
`MORNINGS SALES
`
`MEETING
`
`
`
`
`
`
`THE WEDNESDAY
`MORNING SALES MEETING
`
`
`
`
`
`WILL BE HELD AT 9:00 (9
`
`NOTE OUICK NAME
`PAD
`NOTES LIST
`
`FIG. 12
`
`Page 00014
`
`
`Page 00014
`
`

`
`U.S. Patent
`
`Dec. 25,2001
`
`Sheet 13 of 16
`
`US 6,333,973 B1
`
`&.~I4
`
`m_>_<zV5503
`
`5:Jwmfioz
`
`m2GE
`
`m_>_<zV550502m.mkmdkfl.
`
`
`
`»m:4mEoz4D<n_
`
`<2.GE
`
`Page 00015
`
`mmzoflméx
`
`.2:0»5w:3
`
`
`
`
`
`.2292.rm.1.1520
`
`ll.)
`
`253P500Z,u_
`
`
`
`
`
`.02,rmwiZovvofi
`
`3”?352%comm
`
`
`
`_,Nmm-§,62;1%E500om<_>_
`
`._._DO9_<om_ovj<._ME
`
`.
`
`
`
`
`
`
`Page 00015
`
`
`
`
`
`
`
`

`
`tnCtaP0U
`
`c
`
`Mm
`
`MMM.MS
`
`/0SU
`
`33,
`
`1B
`
`mSE00<m><m
`
`pzmmmpoz
`
`mfifi
`
`:20
`
`rmmmgmv8EAM
`
`P4:95w:3mMZQUJM3
`
`3umanFGE
`
`02GE
`
`Page 00016
`
`
`Page 00016
`
`
`
`

`
`U.S. Patent
`
`Dec. 25,2001
`
`Sheet 15 of 16
`
`US 6,333,973 B1
`
`as02%
`
`
`
`55000m<_>_E
`
`§.8-BiS$Am
`
`
`
`m_>_<zx050E02
`
`
`
`534050240/E
`
`I
`
`
`
`M3..03
`
`
`
`m_>_<zv_050E020mknsfinu
`
`
`
`53405024D<n_
`
`
`
`<3‘.0E
`
`Page 00017
`
`.2:0»5w:33200503
`
`
`
`
`
`.2.£92.rm.w.§..w
`
`
`
`20:3.53002$
`
`
`
`
`
`62.,rmwi200.003
`
`
`
`3:2852:comm
`
`
`
`_.m._DO00m<_>_
`
`amafiq3E.,__m
`
`._._DOom<0m_av_._<.rV3
`
`V
`
`
`
`
`
`
`Page 00017
`
`
`
`
`
`
`

`
`M.WMS.U.
`
`336SU
`
`.o/,,
`
`m3
`
`
`
`mNoomém2:8:4moawmmm59AmEmztzmmz<_.m__\_W_,_om_fi<m_.5zSOEj<o
`
`MnFGE66FGE
`
`Page00018
`
`
`Page 00018
`
`
`

`
`US 6,333,973 B1
`
`1
`INTEGRATED MESSAGE CENTER
`
`RELATED APPLICATIONS
`
`This application is related to U.S. patent application, Ser.
`No. 08/842,015, entitled MULTITASKING GRAPHICAL
`USER INTERFACE; U.S. patent application, Ser. No.
`08/841,485, entitled ELECTRONIC BUSINESS CARDS;
`U.S. patent application, Ser. No. 08/841,486, entitled
`SCROLLING WITH AUTOMATIC COMPRESSION AND
`
`EXPANSION; U.S. patent application, Ser. No. 08/842,019,
`entitled CLID WITH LOCATION ICON; U.S. patent
`application, Ser. No. 08/842,017, entitled CLID WITH
`DRAG AND DROP CAPABILITY; and U.S. 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 searchable 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 office 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 been designed with the
`capability to directly receive, or download, different types of
`messages, such as faxes, e-mail, and Short Messaging Ser-
`vice (SMS) messages. One conventional mobile telephone
`has a display, a keypad, and numerous hard keys, and uses
`menus to enable a user to view different 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.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`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, suffer 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 different 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
`different 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;
`
`Page 00019
`
`
`Page 00019
`
`

`
`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;
`
`10
`
`15
`
`20
`
`FIGS. 14A and 14B are example displays in which the
`user responds to an ink message by establishing a voice call;
`and
`
`25
`
`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.
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`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 ADSI 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
`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 1200 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
`
`Page 00020
`
`
`Page 00020
`
`

`
`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. BOCK 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 Java” 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 efficient 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
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`Page 00021
`
`
`Page 00021
`
`

`
`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 mail notification message might include
`the caller’s name and telephone number, a time and date
`stamp, and the name and address of voice mail server 5600.
`Fax mail server 5700 processes and stores fax mail
`messages for the user. When a caller sends a fax, or fax mail
`message, to network services provider 1200 for the user, fax
`mail server 5700 stores the fax at a location corresponding
`to the user and again informs SMS server 5300 of the
`pending message and the identity and telephone number of
`the caller. SMS server 5300 formulates an SMS fax notifi-
`
`cation message to notify the user of the fax. The fax
`notification message might include the sender’s name and
`telephone and/or fax number, a time and date stamp, and the
`name and address of fax mail server 5700.
`
`10
`
`15
`
`20
`
`25
`
`30
`
`35
`
`40
`
`45
`
`50
`
`55
`
`60
`
`65
`
`8
`Similarly, e-mail server 5800 processes and stores e-mail
`messages, and informs SMS server 5300 of the pending
`message and the identity of the caller. SMS server 5300, in
`turn, notifies the user of the pending message via an SMS
`e-mail notification message. The SMS notification message
`might include the sender’s name, telephone number, and
`e-mail address, a time and date stamp, and the name and
`address of e-mail server 5800. Backup 5900 serves as a
`backup memory device that stores pending messages in the
`event of a failure in one of the servers.
`
`II. System Processing
`Mobile telephone 1100 provides a graphical user interface
`on display 2400 (FIG. 2) to facilitate management of the
`messages by the user. FIG. 6 is an example of an idle screen
`of display 2400 including various graphical
`icons and
`information, such as integrated message center 6100 and
`business card 6200.
`
`Business card 6200 contains information regarding indi-
`viduals or businesses the user may desire to call. In the case
`of an individual, business card 6200 includes the individu-
`al’s name and address,
`the individual’s home, business,
`and/or cellular telephone numbers, and location icons. The
`location icons indicate graphically the characteristics repre-
`senting the location or type of telephone number. In other
`words, a home icon indicates that the corresponding tele-
`phone number is the individual’s home telephone number.
`Message center 6100 represents a unified mailbox through
`which the user is presented with SMS notification messages
`for all types of received messages, including voice, text, ink,
`fax, e-mail, etc. To access message center 6100, the user
`selects the message center icon, for example, simply by
`pressing it. Once the user selects the message center icon,
`message center 6100 displays a list of received messages.
`FIGS. 7A and 7B are examples of typical message center
`displays.
`FIG. 7A is an example display in which message center
`6100 presents the user with an indication of the total number
`of messages received 7100 and sent 7200, and a scrollable,
`selectable list 7300 of notification headers for all
`the
`
`received messages. Each entry in the scrollable list of
`notification headers identifies a received message and
`includes the sender’s name 7400 and an identification icon
`
`7500, identifying the type of message. The identification
`icons include, for example, icons used to identify voice mail,
`SMS messages, e-mail, and faxes.
`Message center 6100 organizes the messages according to
`user preference. For example,
`the messages might be
`arranged alphabetically, chronologically, by message type,
`or by sender. In addition, the user might specify that each
`message include a date/time stamp to indicate when the
`message was received.
`If the user desires, message center 6100 will provide more
`detailed information about any of the received messages
`before retrieving the actual message. To view the detailed
`information, the user selects a message from the scrollable
`list and message center 6100 displays the detailed informa-
`tion corresponding to the selected message. The detailed
`information might include the sender’s home, office, and/or
`cellular telephone number, a location icon indicating from
`where the sender sent
`the message,
`the sender’s e-mail
`address, the date and time the message was received, etc.
`Message center 6100 obtains the detailed information from
`the notification message received from network services
`provider 1200 or from the directories st