1111111111111111 IIIIII IIIII 11111 1111111111 111111111111111 1111111111 111111111111111 11111111
`US 20030228863Al
`
`(19) United States
`(12) Patent Application Publication
`Vander Veen et al.
`
`(10) Pub. No.: US 2003/0228863 Al
`Dec. 11, 2003
`(43) Pub. Date:
`
`(54)
`
`VOICEMAIL USER INTERFACE METHODS
`AND APPARATUS FOR MOBILE
`COMMUNICATION DEVICES
`
`(76)
`
`Inventors: Raymond P. Vander Veen, Waterloo
`(CA); Mihal Lazaridis, Waterloo (CA)
`
`Correspondence Address:
`David B. Cochran, Esq.
`JONES DAY
`North Point, 901 Lakeside Ave
`Cleveland, OH 44114 (US)
`
`(21)
`
`Appl. No.:
`
`10/456,715
`
`(22)
`
`Filed:
`
`Jun. 6,2003
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 60/386,709, filed on Jun.
`10, 2002.
`
`Publication Classification
`
`(51)
`(52)
`
`Int. Cl.7 ....................................................... H04K 3/00
`U.S. Cl.
`................... 455/412.1; 455/413; 455/550.1;
`455/1
`
`(57)
`
`ABSTRACT
`
`Voicemail user interface methods and apparatus for mobile
`communication devices are disclosed. Voicemail notification
`messages corresponding to voicemail messages are received
`through a wireless receiver of the mobile device and voice(cid:173)
`mail message header lines corresponding to them are dis(cid:173)
`played in a message list. In one illustrative example, the
`mobile device provides a graphical user interface (GUI) for
`the end-user with visual objects corresponding to PLAY,
`REWIND, FAST FORWARD, SKIP BACK, SKIP FOR(cid:173)
`WARD, as examples, which provides for transparency of
`voicemail system-specific commands. Preferably,
`the
`mobile device receives the voicemail notification messages
`from several different voicemail systems for consolidating
`such processing using this single common user interface.
`Each voicemail notification message preferably includes
`voicemail message summary information, such as a calling
`party identifier, a message time stamp, and message length,
`for use in providing the voicemail message header informa(cid:173)
`tion in the message list. In addition, each voicemail notifi(cid:173)
`cation message preferably includes voicemail retrieval/pro(cid:173)
`cessing information, such as a voicemail access telephone
`number, a voicemail message identification number, and
`voicemail message processing commands, for use in pro(cid:173)
`viding the system interface transparency.
`
`i--i:------------~,: :.~~-~.;f G
`I B
`
`I
`
`Display
`
`:I~--~
`
`134
`
`_L ~~
`
`112
`I - - -~
`I
`I
`I
`I
`I
`I
`I
`I
`I
`116
`L _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
`
`~ -~ - - ,
`
`\__132
`
`Keyboard
`
`114
`
`Auxiliary UI
`
`104
`
`NETWORK . - , c - - - - - - - - - - ;
`(PSTN)
`124
`
`PUBLIC OR
`PRIVATE
`NETWORK ..--,---;
`(INTERNET)
`130
`
`118
`
`Base
`Station
`Controller
`
`GGSN
`
`120
`128
`126
`L-----------------------
`
`Motorola Solutions, Inc., Ex1006, p. 1
`
`

`

`Patent Application Publication Dec. 11, 2003 Sheet 1 of 11
`
`US 2003/0228863 Al
`
`Fl·G. 1
`-----------------------1
`142 I
`102
`_/ ______ I_
`I
`
`SIM Interface
`
`140
`
`SIM
`
`Display
`
`112
`
`Keyboard
`
`114
`
`144
`
`V
`
`Auxiliary UI
`
`Controller
`
`I :~~-LB
`
`Battery
`Interface
`
`Regulator
`
`136
`
`106
`
`108
`
`RF
`Transceiver
`
`110
`
`~132
`
`100
`
`116
`L _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
`
`-------------------------,
`--z.J . .y
`122
`104
`:
`
`NETWORK ---+-I ________ _
`(PSTN)
`124
`
`132
`
`MSC/
`VLR
`
`HLR
`
`118
`
`PUBLIC OR
`PRIVATE
`NETWORK - - - - - (cid:173)
`(INTERNET)
`130
`
`GGSN
`
`SGSN
`
`Base
`Station
`1---- Controller
`
`120
`128
`126
`L - - - - - - - - - - - - - - - - - - - - - - - ~
`
`Motorola Solutions, Inc., Ex1006, p. 2
`
`

`

`262
`
`SIM
`
`264
`
`SIM
`Interface
`
`V+
`
`254
`
`Battery
`Interface
`
`256
`
`Battery
`
`""C
`
`I")
`
`I")
`
`228
`
`Microprocessor·
`
`~ .... ~ = ....
`~ "Cl -....
`~ ....
`.... 0 =
`~
`O' -....
`~ ....
`.... 0 =
`~ 230
`~
`~ ri
`'"""'
`'"""' ~
`N
`§
`'JJ. =(cid:173)~
`~ ....
`N
`0 ....,
`'"""'
`'"""'
`
`200
`
`~ -:z...~..-v
`
`FIG. 2
`
`-:z...t..-v
`
`~\ ~
`~ \♦ _ - - - - - -
`Signals~ I I I
`I r' -I Receiver ,_
`
`I
`
`16
`
`__ -
`
`-
`
`- -I
`-
`I
`c22D
`
`• DSP
`
`:
`
`Control
`
`LOs I 213
`
`I 218
`I ______ 211
`
`Control
`___ -
`
`-
`
`-
`
`I
`I
`I
`I
`I
`I
`I
`I
`
`1
`
`202
`
`222
`
`Display
`
`224
`
`Memo
`226
`RAM
`
`I
`
`238
`
`-~
`232
`
`.~ Speaker
`
`'--234
`
`I 1111
`
`• I Microphone
`236
`
`Other
`Device
`Subsystems
`242
`
`Short-Range
`Communications
`
`240
`
`d
`'JJ.
`N
`0
`
`@
`
`0
`N
`N
`00
`00
`O'I
`
`~ >
`'"""'
`
`Motorola Solutions, Inc., Ex1006, p. 3
`
`

`

`304,
`
`----1 >1( I
`
`-1
`
`Unified
`Messaging
`Notification
`system
`
`I
`
`I
`
`316
`
`Corporate
`· ·
`Phone
`Services I
`
`(~_
`
`Firewall
`
`IOEJEl1
`312
`I 91 308
`
`Unified
`Messaging
`Notification
`System
`
`346
`
`332
`
`302
`
`□: 300
`32r
`
`Carrier Based
`Mailbox
`
`328
`
`FIG. 3
`
`322
`
`Mobile
`Device
`
`""C
`
`~ .... ~ = ....
`~ "Cl -....
`~ ....
`.... 0 =
`~
`O' -....
`~ ....
`.... 0 =
`
`I")
`
`I")
`
`~
`~
`ri
`'"""'
`'"""' ~
`N
`§
`'JJ. =(cid:173)~
`~ ....
`0 ....,
`'"""'
`'"""'
`
`~
`
`d
`'JJ.
`N
`0
`
`@
`
`0
`N
`N
`00
`00
`O'I
`
`~ >
`'"""'
`
`Motorola Solutions, Inc., Ex1006, p. 4
`
`

`

`r-----------------------------
`
`1
`
`-
`
`-
`
`---;-401- -
`
`-
`
`- 1
`
`I
`I
`I
`I
`
`400
`
`~
`
`404
`
`Type
`
`Length
`
`Data
`
`[Ox08]
`[Ox08]
`[Ox02]
`[Ox02]
`[Ox02]
`[Ox02]
`
`[Ox91]
`[Ox94]
`[Ox98]
`[Ox9C]
`[OxA1]
`[OxA4]
`length
`[OxAB]
`[Ox02]
`[OxAC] [Ox02]
`(OxB1]
`[OxOB]
`[OxB4]
`[OxOB]
`[OxBB]
`[Ox04]
`[OxBC] [Ox02]
`
`Ox8797088d369ca3d3L
`Oxa6ae9d843493fb7al
`OxOA
`Ox01
`Ox28
`Ox28
`
`Ox28
`Ox05
`"17702910430"
`"15198887465"
`Ox102939483949
`Ox19
`
`Description
`
`mailbox ID
`protocol ID
`protocol version
`security level
`min DTMF length
`maxDTMF
`
`DTMF gap length
`skip length
`access number
`caller ID
`timestamp
`message length
`
`IJoicemail Message
`Date: May 30, 2002 3: 19 PM
`Length: 6 seconds
`Caller
`RIM HQ
`8887465
`
`""C
`
`~ .... ~ = ....
`~ "Cl -....
`~ ....
`.... 0 =
`~
`O' -....
`~ ....
`.... 0 =
`
`I")
`
`I")
`
`Database of Saved Voice-Mail
`Systems
`
`Q_rotocol ver
`FFWD=13
`PREV=21
`
`: •
`
`REW=14
`NEXT=22
`
`REW=35
`NEXT=55
`
`STOP=36
`Etc ...
`
`FIG. 4
`
`~
`~
`ri
`'"""'
`'"""' ~
`N
`§
`'JJ. =(cid:173)~
`~ ....
`0 ....,
`'"""'
`'"""'
`
`,i;;..
`
`402
`
`406
`
`408
`
`d
`'JJ.
`N
`0
`
`@
`
`0
`N
`N
`00
`00
`O'I
`
`~ >
`'"""'
`
`Motorola Solutions, Inc., Ex1006, p. 5
`
`

`

`1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 7
`I
`501
`I
`I
`I
`I
`I
`I
`I
`I
`
`I
`I
`I
`I
`
`500
`
`~ [0xA4] [0x02]
`
`0x8797088d369ca3d3L
`0x0000000000000001L
`[0x01][0x20][0x02][0x21]
`0x28
`0x28
`0x28
`[0xA8] [0x02]
`[0xAC] [0x02] 0x05
`[0xB1] [0x0B]
`"17702910430"
`[0x84] [0x0B]
`"15198887465"
`[0xB8] [0x04]
`0x102939483949
`[OxBC] [0x02]
`0x19
`
`mailbox id
`bit flags
`DTMF cmds ~ ~
`min DTMF len
`-
`max DTMF len
`DTMF gap len
`skip length
`access number
`caller ID
`timestamp
`message length
`
`504 ........,__
`
`Type Len
`.
`[0x91] [0x08]
`[0x94] [0x08]
`[0x98] [0x06]
`[0xA1][0x02]
`
`Data
`
`Description
`
`l)oicemail Message
`Date: May 3[1, 2[1[12 3:19 PM
`Leng th: 6 seconds
`C,;1l~I~ H
`88874is
`
`I
`I
`
`1
`
`502
`
`-~~ 50 7
`
`• • •
`
`~ IO I
`
`509
`
`I
`
`FIG. 5
`L _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
`
`""C
`
`~ .... ~ = ....
`~ "Cl -....
`~ ....
`.... 0 =
`~
`O' -....
`~ ....
`.... 0 =
`
`I")
`
`I")
`
`~
`~
`ri
`'"""'
`'"""' ~
`N
`§
`rF.J. =(cid:173)~
`~ ....
`Ul
`0 ....,
`'"""'
`'"""'
`
`d
`rF.J.
`N
`0
`
`@
`
`0
`N
`N
`00
`00
`O'I
`
`~ >
`'"""'
`
`Motorola Solutions, Inc., Ex1006, p. 6
`
`

`

`1 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ,
`I
`604
`,_ 601
`I
`I
`I
`I
`I
`I I
`~
`
`TYPE
`Vendor ID
`Mailbox ID
`Flags
`Access Number
`
`600
`
`2nd Access Number
`Message Count
`Password Limits
`
`Message ID
`DTMF Commands
`Caller ID
`Message Length
`Time Stamp
`
`0x05
`0x06
`0x07
`
`0x08
`0x09
`0x0A
`0x0B
`0x0C
`
`Vokemail Message
`Date: May 30, 2002 3: 19 PM
`Length: 6 seconds
`Caller
`RIM HQ
`8887465
`
`CODE LENGTH
`0x01
`Var/Max=15
`0x02
`Var/Max=15
`0x03
`Var/Max=4
`0x04
`Var/Max=15
`
`Var/Max=8
`5
`2
`
`DESCRIPTION
`ID of VM vendor
`ID of VM mailbox
`Misc. bit flags
`VM system access
`telephone number
`2nd access number
`# of VM messages
`Min & Max lengths
`of password
`ID of VM message
`Var/Max=8
`DTMF tone encoding
`Var
`Max=15Caller ID
`2
`Duration of message
`4
`Date/Time of message
`
`602
`
`607
`
`-...
`609
`
`• • •
`
`I
`
`··~ 1 Pa s s~
`
`FIG. 6
`L _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
`
`""C
`
`~ .... ~ = ....
`~ "Cl -....
`~ ....
`.... 0 =
`~
`O' -....
`~ ....
`.... 0 =
`
`I")
`
`I")
`
`~
`~
`ri
`'"""'
`'"""' ~
`N
`§
`'JJ. =(cid:173)~
`~ ....
`0 ....,
`'"""'
`'"""'
`
`O'I
`
`d
`'JJ.
`N
`0
`
`@
`
`0
`N
`N
`00
`00
`O'I
`
`~ >
`'"""'
`
`Motorola Solutions, Inc., Ex1006, p. 7
`
`

`

`Patent Application Publication Dec. 11, 2003 Sheet 7 of 11
`
`US 2003/0228863 Al
`
`FIG. 7
`
`0xC1
`
`706
`
`,.- 700
`
`data
`
`702
`
`704
`
`708
`
`710
`
`712
`
`714
`
`FIG. 8
`
`START
`
`START
`
`FIG. 9
`
`902
`
`NO
`
`904
`
`RECEIVE VOICEMAIL NOTIFICATION
`WITH SUMMARY AND RETRIEVAL
`INFORMATION TO MOBILE DEVICE
`
`VOICEMAIL MESSAGE
`RECEIVED AND STORED
`
`ALERT END USER
`
`806
`
`906
`
`908
`
`SEND VOICEMAIL NOTIFICATION
`WITH SUMMARY AND RETRIEVAL
`INFORMATION TO MOBILE DEVICE
`
`DISPLAY VOICEMAIL HEADER
`INFORMATION IN MESSAGE LIST
`
`910
`
`PROVIDE TRANSPARENT
`VOICEMAIL RETRIEVAL/
`PROCESSING FUNCTIONS AT
`USER INTERFACE BASED ON
`RETRIEVAL INFORMATION
`
`Motorola Solutions, Inc., Ex1006, p. 8
`
`

`

`Patent Application Publication Dec. 11, 2003 Sheet 8 of 11
`
`US 2003/0228863 Al
`
`FIG. 10
`
`.,... 1004
`
`Voicemail
`recorded and
`saved
`
`PBX System
`sends call to
`voice mail
`
`1006·
`
`1000
`
`Voicemail system sends
`summary of call details to
`PBX/voicemail interface
`
`1016
`
`1018
`
`Device notifies user
`of incoming
`notification message
`
`User opens
`notification
`message and
`issues command
`
`1014
`
`Message Placed into
`Unified Message System
`storage area
`
`UMS sends
`notification message
`to mobile device
`
`1020
`
`Device calls UMS
`using access numbers
`provided in
`notification message
`
`r 1024
`
`Device
`authenticates
`the request by
`user password if
`required
`
`1022
`
`Device sends
`DTMF tones to
`identify the
`voicemail and any
`commands to be
`performed on the
`voice mail
`
`1028
`
`Invalid
`voicemail
`response
`sent to
`user
`
`YES
`
`Execute
`command on
`voicemail
`
`End
`
`Motorola Solutions, Inc., Ex1006, p. 9
`
`

`

`Patent Application Publication Dec. 11, 2003 Sheet 9 of 11
`
`US 2003/0228863 Al
`
`FIG. 11
`
`2:27 PM
`TUE, MAY 28
`
`1102
`
`T.1111 T
`9prs l!I
`
`0•.&.daf;■~~ai%0itdii1■w
`
`~ 2:25p RIM
`~ 2:25p RIM
`
`Top 20 Tips
`Welcome!
`
`1106
`
`1108
`
`1100
`
`FIG. 12
`
`2:28 PM
`TUE, MAY 28
`
`Hide Menu
`
`5p RIM
`
`1106
`
`1108
`
`elete
`Compose Em.ail
`Compose PIN
`Pl.ace C.all
`Compose SMS
`Se.arch
`Options
`Close
`
`1202
`
`1100
`
`Motorola Solutions, Inc., Ex1006, p. 10
`
`

`

`Patent Application Publication Dec. 11, 2003 Sheet 10 of 11
`
`US 2003/0228863 Al
`
`FIG. 13
`
`Voicem.ail Mess.age
`1304 { D.ate: M.ay 30, 2002 3: 19 PM
`Length: 6 seconds:
`
`1306 L C.aller
`
`RIM HQ
`8887465
`- - - - - - - - - - - - - 1
`l)
`
`1302-
`
`1100
`
`FIG. 14
`Hide Menu
`Voicem.ail Mess.age
`D.ate: May 28, 2002 2:2 =-===
`Call RIM HQ
`Length: 6 seconds:
`SMS RIM HQ
`C.aller
`Close
`RIM HQ
`- - - - - - -
`8887465
`
`1304
`
`1306
`
`1402
`1404
`
`1302
`
`1100
`
`Motorola Solutions, Inc., Ex1006, p. 11
`
`

`

`Patent Application Publication Dec. 11, 2003 Sheet 11 of 11
`
`US 2003/0228863 Al
`
`FIG. 15
`2:30 Pr.I
`TUE, MAY 28
`
`1504
`
`2121
`
`T.,111,1
`9prs l!J
`
`My Number: + 15197210000
`Retrie1.Jing l)oicemail Msg ...
`
`1516
`
`Caller: RIM HQ
`Length: 6 seconds
`
`1510
`
`1512
`
`1506
`
`1100_)
`
`1514
`
`FIG. 16
`1604
`2:30 PM
`TUE, MAY 28
`
`1504
`
`P......:l:::...ay-in_g_Vo_i_ce_m_a_il _M_s_g.-.. - - - - --l
`
`My N~@ber: + 15197210000
`
`} 1510
`
`1518
`
`1516
`
`Caller: RIM HQ
`Length: 6 seconds
`
`1512
`
`®8®®
`Forward 5 seconds
`
`@) ~ _f 1506
`
`1100
`
`1514
`
`1602
`
`Motorola Solutions, Inc., Ex1006, p. 12
`
`

`

`US 2003/0228863 Al
`
`Dec. 11, 2003
`
`1
`
`VOICEMAIL USER INTERFACE METHODS AND
`APPARATUS FOR MOBILE COMMUNICATION
`DEVICES
`
`BACKGROUND
`[0001] 1. Field of the Invention
`[0002] The present invention relates generally to mobile
`communication devices and the associated communication
`networks within which they operate, and more particularly
`to user interfaces of mobile communication devices used for
`retrieving and processing remotely-stored voicemail mes(cid:173)
`sages.
`[0003] 2. Description of the Related Art
`[0004]
`"Voicemail" is a common feature for practically all
`voice-based communication products. As examples, home
`telephone systems now offer voicemail features built right
`into telephones, telephone companies offer voicemail ser(cid:173)
`vices in their phone networks, corporations provide voice(cid:173)
`mail for every desk with integration with e-mail, and wire(cid:173)
`less carriers offer voicemail packages in connection with
`their cellular telephones. The average professional may have
`two or three different voicemail systems that must be
`checked for new voicemail messages from the home, the
`office, or cellular telephone. Each voicemail system typi(cid:173)
`cally has a different password access and different command
`the same voicemail functions (e.g. PLAY,
`codes for
`REWIND, SAVE, and DELETE).
`[0005] The result of the above is that the end user must
`check several different voicemail systems for voicemail
`while away and remember each set of voicemail command
`codes. One way to handle this problem is to manually
`forward all phone calls (i.e. via call forwarding) from all
`devices to a common unified messaging service (UMS).
`Here, the end user can check all messages at once from a
`single voicemail location. However, this solution is prone to
`problems since the end user may forget to forward phone
`calls as necessary, may be too busy traveling to regularly
`check for voicemail messages, and may forget passwords
`needed to access the voicemail systems.
`[0006] Accordingly, there is a strong need to provide
`unified methods and apparatus for handling and processing
`voicemail messages to reduce the problems created by
`today's use of multiple voicemail systems. There is also a
`strong need to simplify the user interface for retrieving and
`processing voicemail messages from several different voice(cid:173)
`mail systems.
`
`SUMMARY
`
`[0007] Voicemail user interface methods and apparatus for
`mobile communication devices are described herein. Voice(cid:173)
`mail notification messages corresponding to voicemail mes(cid:173)
`sages are received through a wireless receiver of the mobile
`device and voicemail message header lines corresponding to
`them are displayed in a message list. In one illustrative
`embodiment, the mobile device provides a graphical user
`interface (GUI) for the end-user with visual objects corre(cid:173)
`sponding to PLAY, REWIND, FAST FORWARD, SKIP
`BACK, SKIP FORWARD, as examples, which provides for
`transparency of voicemail system-specific commands. Pref(cid:173)
`erably, the mobile device receives the voicemail notification
`messages from several different voicemail systems for con-
`
`solidating such processing using this single common user
`interface. Each voicemail notification message preferably
`includes voicemail message summary information, such as
`a calling party identifier, a message time stamp, and message
`length, for use in providing voicemail message header
`information in the message list. In addition, each voicemail
`notification message preferably includes voicemail retrieval/
`processing information, such as a voicemail access tele(cid:173)
`phone number, a voicemail message identification number,
`and voicemail message processing commands, for use m
`providing the system interface transparency.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0008] Embodiments of present invention will now be
`described by way of example with reference to attached
`figures, wherein:
`[0009] FIG. 1 is a block diagram which illustrates perti(cid:173)
`nent components of a mobile communication device which
`communicates within a wireless communication network;
`[0010] FIG. 2 is a more detailed diagram of a preferred
`mobile communication device of FIG. 1;
`[0011] FIG. 3 is a diagram of communication network
`components which may be used in connection with the
`methods described herein;
`[0012] FIG. 4 is an example of voicemail and database
`information which may be used for that described in the
`present application;
`[0013] FIG. 5 is another example of voicemail and data(cid:173)
`base information which may be used for that described in the
`present application;
`[0014] FIG. 6 is yet another example of voicemail and
`database information which may be used for that described
`in the present application;
`[0015] FIG. 7 is a message format which may be used for
`communication of voicemail notification messages having
`voicemail notification payloads (VNPs);
`[0016] FIG. 8 is a flowchart of a general method of
`sending voicemail notification information from a voicemail
`system to a mobile communication device;
`[0017] FIG. 9 is a flowchart of a general method of
`receiving and processing voicemail notification information
`by a mobile communication device;
`[0018] FIG. 10 is a flowchart which describes an illustra(cid:173)
`tive overview of methods of the present application; and
`[0019] FIGS. 11-16 are illustrations of a visual display of
`the mobile communication device, showing voicemail mes(cid:173)
`sage data and a graphical user interface (GUI) for retrieving
`and processing voicemail messages.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENTS
`
`[0020] Voicemail user interface methods and apparatus for
`mobile communication devices are described herein. Voice(cid:173)
`mail notification messages corresponding to the voicemail
`messages are received through a wireless receiver of the
`mobile device, and voicemail message header lines corre(cid:173)
`sponding to them are displayed in a message list. In one
`illustrative example, the mobile device provides a graphical
`
`Motorola Solutions, Inc., Ex1006, p. 13
`
`

`

`US 2003/0228863 Al
`
`Dec. 11, 2003
`
`2
`
`user interface (GUI) for the end-user with visual objects
`corresponding to PLAY, REWIND, FAST FORWARD,
`SKIP BACK, SKIP FORWARD, etc., which provides for
`transparency of voicemail system-specific commands. Pref(cid:173)
`erably, the mobile device receives the voicemail notification
`messages from several different voicemail systems for con(cid:173)
`solidating such processing using this single common user
`interface. Each voicemail notification message preferably
`includes voicemail message summary information, such as
`a calling party identifier, a message time stamp, and message
`length, for use in providing the voicemail message header
`information in the message list. In addition, each voicemail
`notification message preferably includes voicemail retrieval/
`processing information, such as a voicemail access tele(cid:173)
`phone number, a voicemail message identification number,
`and voicemail message processing commands, for use in
`providing the system interface transparency.
`
`[0021] FIG. 1 is a block diagram of a communication
`system 100 which includes a mobile station 102 which
`communicates through a wireless communication network
`104. In the embodiment of FIG. 1, wireless network 104 is
`configured in accordance with General Packet Radio Service
`(GPRS) and a Global Systems for Mobile (GSM) technolo(cid:173)
`gies; however, any suitable type of network communication
`protocols may be utilized. For example, the network may be
`based on code division multiple access (CDMA) or other
`suitable technologies. As another example, the network may
`be based on an Integrated Dispatch Enhanced Network
`(iDEN) which is a high-capacity digital trunked radio sys(cid:173)
`tem providing integrated voice and data services.
`
`[0022] Mobile station 102, which is one type of mobile
`communication device, preferably includes a visual display
`112, a keyboard 114, and perhaps one or more auxiliary user
`interfaces (UI) 116, each of which are coupled to a controller
`106. Controller 106 is also coupled to radio frequency (RF)
`transceiver circuitry 108 and an antenna 110. Typically,
`controller 106 is embodied as a central processing unit
`(CPU) which runs operating system software in a memory
`component (not shown). Controller 106 will normally con(cid:173)
`trol overall operation of mobile station 102, whereas signal
`processing operations associated with communication func(cid:173)
`tions are typically performed in RF transceiver circuitry 108.
`Controller 106 interfaces with device display 112 to display
`received information, stored information, user inputs, and
`the like. Keyboard 114, which may be a telephone type
`keypad or full alphanumeric keyboard, is normally provided
`for entering data for storage in mobile station 102, infor(cid:173)
`mation for transmission to network 104, a telephone number
`to place a telephone call, commands to be executed on
`mobile station 102, and possibly other or different user
`inputs.
`
`[0023] Mobile station 102 sends communication signals to
`and receives communication signals from network 104 over
`a wireless link via antenna 110. RF transceiver circuitry 108
`performs functions similar to those of station 118 and base
`station controller 120, including for example modulation/
`demodulation and possibly encoding/decoding and encryp(cid:173)
`tion/decryption. It is also contemplated that RF transceiver
`circuitry 108 may perform certain functions in addition to
`those performed by base station controller 120. It will be
`apparent to those skilled in art that RF transceiver circuitry
`108 will be adapted to particular wireless network or net(cid:173)
`works in which mobile station 102 is intended to operate.
`
`[0024] Mobile station 102 includes a battery interface 134
`for receiving one or more rechargeable batteries 132. Battery
`132 provides electrical power to electrical circuitry in
`mobile station 102, and battery interface 132 provides for a
`mechanical and electrical connection for battery 132. Bat(cid:173)
`tery interface 132 is coupled to a regulator 136 which
`regulates power to the device. When mobile station 102 is
`fully operational, an RF transmitter of RF transceiver cir(cid:173)
`cuitry 108 is typically keyed or turned on only when it is
`sending to network, and is otherwise turned off to conserve
`resources. Similarly, an RF receiver of RF transceiver cir(cid:173)
`cuitry 108 is typically periodically turned off to conserve
`power until it is needed to receive signals or information (if
`at all) during designated time periods.
`
`[0025] Mobile station 102 operates using a Subscriber
`Identity Module (SIM) 140 which is connected to or inserted
`in mobile station 102 at a SIM interface 142. SIM 140 is one
`type of a conventional "smart card" used to identify an end
`user ( or subscriber) of mobile station 102 and to personalize
`the device, among other things. Without SIM 140, the
`mobile station terminal is not fully operational for commu(cid:173)
`nication through wireless network 104. By inserting SIM
`140 into mobile station 102, an end user can have access to
`any and all of his/her subscribed services. SIM 140 generally
`includes a processor and memory for storing information.
`Since SIM 140 is coupled to SIM interface 142, it is coupled
`to controller 106 through communication lines 144. In order
`to identify the subscriber, SIM 140 contains some user
`parameters such as an International Mobile Subscriber Iden(cid:173)
`tity (IMSI). An advantage of using SIM 140 is that end users
`are not necessarily bound by any single physical mobile
`station. SIM 140 may store additional user information for
`the mobile station as well, including datebook (or calendar)
`information and recent call information.
`
`[0026] Mobile station 102 may consist of a single unit,
`such as a data communication device, a cellular telephone,
`a multiple-function communication device with data and
`voice communication capabilities, a personal digital assis(cid:173)
`tant (PDA) enabled for wireless communication, or a com(cid:173)
`puter
`incorporating an
`internal modem. Alternatively,
`mobile station 102 may be a multiple-module unit compris(cid:173)
`ing a plurality of separate components, including but in no
`way limited to a computer or other device connected to a
`wireless modem. In particular, for example, in the mobile
`station block diagram of FIG. 1, RF transceiver circuitry
`108 and antenna 110 may be implemented as a radio modem
`unit that may be inserted into a port on a laptop computer.
`In this case, the laptop computer would include display 112,
`keyboard 114, one or more auxiliary Uis 116, and controller
`106 embodied as the computer's CPU. It is also contem(cid:173)
`plated that a computer or other equipment not normally
`capable of wireless communication may be adapted to
`connect to and effectively assume control of RF transceiver
`circuitry 108 and antenna 110 of a single-unit device such as
`one of those described above. Such a mobile station 102 may
`have a more particular implementation as described later in
`relation to mobile station 402 of FIG. 2.
`
`[0027] Mobile station 102 communicates in and through
`wireless communication network 104. In the embodiment of
`FIG. 1, wireless network 104 is configured in accordance
`with General Packet Radio Service (GPRS) and a Global
`Systems for Mobile (GSM) technologies. Wireless network
`104 includes a base station controller (BSC) 120 with an
`
`Motorola Solutions, Inc., Ex1006, p. 14
`
`

`

`US 2003/0228863 Al
`
`Dec. 11, 2003
`
`3
`
`associated tower station 118, a Mobile Switching Center
`(MSC) 122, a Home Location Register (HLR) 132, a Serv(cid:173)
`ing General Packet Radio Service (GPRS) Support Node
`(SGSN) 126, and a Gateway GPRS Support Node (GGSN)
`128. MSC 122 is coupled to BSC 120 and to a landline
`network, such as a Public Switched Telephone Network
`(PSTN) 124. SGSN 126 is coupled to BSC 120 and to
`GGSN 128, which is in turn coupled to a public or private
`data network 130 (such as the Internet). HLR 132 is coupled
`to MSC 122, SGSN 126, and GGSN 128.
`
`[0028] Station 118 is a fixed transceiver station, and sta(cid:173)
`tion 118 and BSC 120 are together referred to herein as the
`fixed transceiver equipment. The fixed transceiver equip(cid:173)
`ment provides wireless network coverage for a particular
`coverage area commonly referred to as a "cell". The fixed
`transceiver equipment transmits communication signals to
`and receives communication signals from mobile stations
`within its cell via station 118. The fixed transceiver equip(cid:173)
`ment normally performs such functions as modulation and
`possibly encoding and/or encryption of signals to be trans(cid:173)
`mitted to the mobile station in accordance with particular,
`usually predetermined, communication protocols and
`parameters, under control of its controller. The fixed trans(cid:173)
`ceiver equipment similarly demodulates and possibly
`decodes and decrypts, if necessary, any communication
`signals received from mobile station 102 within its cell.
`Communication protocols and parameters may vary
`between different networks. For example, one network may
`employ a different modulation scheme and operate at dif(cid:173)
`ferent frequencies than other networks.
`
`[0029] The wireless link shown in communication system
`100 of FIG. 1 represents one or more different channels,
`typically different radio frequency (RF) channels, and asso(cid:173)
`ciated protocols used between wireless network 104 and
`mobile station 102. Those skilled in art will appreciate that
`a wireless network in actual practice may include hundreds
`of cells, each served by a station 118 (i.e. or station sector),
`depending upon desired overall expanse of network cover(cid:173)
`age. All pertinent components may be connected by multiple
`switches and routers (not shown), controlled by multiple
`network controllers.
`
`[0030] For all mobile station's 102 registered with a
`network operator, permanent data (such as mobile station
`102 user's profile) as well as temporary data (such as mobile
`station's 102 current location) are stored in HLR 132. In
`case of a voice call to mobile station 102, HLR 132 is
`queried to determine the current location of mobile station
`102. A Visitor Location Register (VLR) of MSC 122 is
`responsible for a group of location areas and stores the data
`of those mobile stations that are currently in its area of
`responsibility. This includes parts of the permanent mobile
`station data that have been transmitted from HLR 132 to the
`VLR for faster access. However, the VLR of MSC 122 may
`also assign and store local data, such as temporary identi(cid:173)
`fications. Optionally, the VLR of MSC 122 can be enhanced
`for more efficient co-ordination of GPRS and non-GPRS
`services and functionality ( e.g. paging for circuit-switched
`calls which can be performed more efficiently via SGSN
`126, and combined GPRS and non-GPRS location updates).
`
`[0031] Serving GPRS Support Node (SGSN) 126 is at the
`same hierarchical level as MSC 122 and keeps track of the
`individual locations of mobile stations. SGSN 126 also
`
`performs security functions and access control. Gateway
`GPRS Support Node (GGSN) 128 provides interworking
`with external packet-switched networks and is connected
`with SGSNs (such as SGSN 126) via an IP-based GPRS
`backbone network. SGSN 126 performs authentication and
`cipher setting procedures based on the same algorithms,
`keys, and criteria as in existing GSM. In conventional
`operation, cell selection may be performed autonomously by
`mobile station 102 or by the fixed transceiver equipment
`instructing mobile station 102 to select a particular cell.
`Mobile station 102 informs wireless network 104 when it
`reselects another cell or group of cells, known as a routing
`area.
`
`[0032]
`In order to access GPRS services, mobile station
`102 first makes its presence known to wireless network 104
`by performing what is known as a GPRS "attach". This
`operation establishes a logical link between mobile station
`102 and SGSN 126 and makes mobile station 102 available
`to receive, for example, pages via SGSN, notifications of
`incoming data, or SMS messages over GPRS. In order to
`send and receive GPRS data, mobile station 102 assists in
`activating the packet data address that it wants to use. This
`operation makes mobile station 102 known to GGSN 128;
`interworking with external data networks can thereafter
`commence. User data may be transferred transparently
`between mobile station 102 and the external data networks
`using, for example, encapsulation and tunneling. Data pack(cid:173)
`ets are equipped with GPRS-specific protocol information
`and transferred between mobile station 102 and GGSN 128.
`
`[0033] FIG. 2 is a detailed block diagram of a preferred
`mobile station 202. Mobile station 202 is preferably a
`two-way communication device having at least voice and
`advanced data communication capabilities, including the
`capability to communicate with other computer systems.
`Depending on the functionality provided by mobile station
`202, it may be referred to as a data messaging device, a
`two-way pager, a cellular telephone with data messaging
`capabilities, a wireless Internet appliance, or a data com(cid:173)
`munication device (with or without telephony capabilities).
`Mobile station 202 may communicate with any one of a
`plurality of fixed transceiver stations 200 within its geo(cid:173)
`graphic coverage area.
`
`[0034] Mobile station 202 will normally incorporate a
`communication subsystem 211, which includes a receiver
`212, a transmitter 214, and associated components, such as
`one or more (preferably embedded or internal) antenna
`elements 216 and 218, local oscillators (LOs) 213, and a
`processing module such as a digital signal processor (DSP)
`220. Communication subsystem 211 is analogous to RF
`transceiver circuitry 108 and antenna 110 shown in FIG. 1.
`As will be apparent to those skilled in field of communica(cid:173)
`tions, particular design of communication subsystem 211
`depends on the communication network in which mobile
`station 202 is intended to operate.
`
`[0035] Mobile station 202 may send and receive commu(cid:173)
`nication signals over the network after required network
`registration or activation procedures have been completed.
`Signals received by antenna 216 through the network are
`input to receiver 212, which may perform such common
`receiver functions as signal amplification, frequency down
`conversion, filtering, channel selection, and like, and in
`example shown in FIG. 2, analog-to-digital (ND) conver-
`
`Motorola Solutions, Inc., Ex1006, p. 15
`
`

`

`US 2003/0228863 Al
`
`Dec. 11, 2003
`
`4
`
`sion. AID conversion of a rece