|80
`
`as) United States
`a2) Patent Application Publication co) Pub. No.: US 2004/0203956 Al
`(43) Pub. Date:
`Oct. 14, 2004
`Tsampalis
`
`(54) METHOD AND APPARATUS FOR
`PROVIDING WIRELESS MESSAGING
`
`(62) TESTS sensscaucuanmannsenis 455/466; 455/412.1
`
`(76)
`
`Inventor:
`
`Ioannis Tsampalis, Chicago, IL (US)
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`VEDDER PRICE KAUFMAN & KAMMHOLZ
`222 N. LASALLE STREET
`CHICAGO,IL 60601 (US)
`
`(21)
`
`Appl. No.:
`
`10/335,140
`
`(22)
`
`Filed:
`
`Dee. 31, 2002
`
`Publication Classification
`
`(SV) Ute C7 caicccscsscssssssesenssusescnnetvessaneeneees H04Q 7/20
`
`Afirst mobile wireless communication device (L00) includes
`mobile wireless communication device messaging format
`capabilities determinator circuitry (104) operable to obtain
`second mobile wireless communication device messaging
`format capabilities information (110) of a second mobile
`wireless communication device (100) and send message
`circuitry, operable to send a message (112) in a message
`format compatible with at least one ofthe formats identified
`in the second mobile wireless communication device mes-
`saging format capabilities information (110).
`
`100
`~
`FIRST MOBILE WIRELESS COMMUNICATION DEVICE
`ee
`USER INTERFACE
`
`220/402 YJ
`
`106
`
`
`
`
`
`
`MOBILE WIRELESS COMMUNICATION
`
`
`
`DEVICE MESSAGING FORMAT CAPABILITIES]
`DETERMINATOR CIRCUITRY
`yo402
`
`
`
` ACTIVE MESSAGE 2418
`
`
`V
`
`LOCAL MSG'G
`REMOTE MSG'G
`
`FORMAT
`FORMAT
`
`
`
`CAPABILITIES
`CAPABILITIES
`
`
`
`DETERMINATOR
`DETERMINATOR
`
`
`CIRCUITRY
`CIRCUITRY
`
`
`ACTIVE MSG RECIPIENT
`LIST
`
`220
`
`REMOTE MSG'G
`FORMAT
`
`CAPABILITIES
`
`DETERMINATOR
`CIRCUITRY
`
`
`EMS.
`
`
`COMMUNICATION DEVICE MSG'G
`FORMAT CAPAB
`NFORMATIO
`
`
`
`APPLE 1007
`
`APPLE 1007
`
`1
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 1 of 11
`
`US 2004/0203956 Al
`
`FIG. 1
`
`108
`
`DEVICE MESSAGING FORMAT
`CAPABILITIES DETERMINATOR
`CIRCUITRY
`
`yy 104
`
`;
`
`oo MOBILE WIRELESS COMMUNICATION
`
`A! 40
`V
`
`MEMORY
`
`\
`
`1410
`
`V
`
`SEND MESSAGE CIRCUITRY
`
`2
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 2 of 11
`
`US 2004/0203956 Al
`
`FIG, 2
`
`FIRST MOBILE WIRELESSee DEVICE
`
`f
`- 100
`
`USER INTERFACE
`
`—
`220/402 YJ
`
`
`
`MOBILE WIRELESS COMMUNICATION
`
`
`DEVICE MESSAGING FORMAT CAPABILITIES
`106
`-
`apeNTR CIRCUITRY
`
`
`
`
`
`
`
`V
`
`
`
`
`REMOTE MSG'G
`LOCAL MSG'G
`
`
`FIRST MOBILE WIRELESS
`
`FORMAT
`FORMAT
`
`OMMUNICATION DEVICE MSG'G
`
`
`
`FORMAT CAPABILITIES
`CAPABILITIES
`CAPABILITIES
`
`
`DETERMINATOR||DETERMINATOR
`CIRCUITRY
`CIRCUITRY
`
`
`
`
`
`
`REMOTE MSG'G
`FORMAT
`
`CAPABILITIES
`
`DETERMINATOR
`
`CIRCUITRY
`
`
`
`
`FORMATonEMS
`
` COMMUNICATION DEVICE MSG'G
`
`3
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 3 of 11
`
`US 2004/0203956 Al
`
`
`
`p22
`
`
`
`
`
`
`
`
` 302
`
`FLAG MSG'G FRMT CAPS LAST UPDATE TIME
`RECIPIENT NAME RECIPIENTID
`=[25000111702[_SwSEMS
`
`ea
`_[312-335:3353 ———e|e
`JOHN DOE
`|__|
`SSmaeaes
`312-444-4444||
`|1] SMS;EMS|12:11:08 11/06/02
`[312.555.5555
`[JANETDOE_[312-666-6606 =ease:
`ma
`eerofCSdCSC~CSCS—S
`
`|Of
`
`
`
`304
`
`308
`
`308
`ct
`402
`
`310
`
`26
`
`FIG. 3
`
`308
`
`RECIPIENT ID FLAG MSG'G FT CAP'S
`
`Bait[1] SMSiEMS
`fpizezeeeee fof SSSCS—S
`
`
`INNNCNNN-NNNN|of———S—Sd
`
`
`
`408
`Mees
`
`218
`
`ACTIVE MESSAGE RECIPIENT LIST
`
`
`
`
`
`FIG. 4
`
`4
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 4 of 11
`
`US 2004/0203956 Al
`
`
`
`
`
`
`
`
`702__
`
`
`
`
`
`700
`on
`
`
`
`
`
`
`OBTAIN MOBILE WIRELESS
`RECEIVE A FIRST MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGING
`COMMUNICATION DEVICE
`
`
`ae
`MESSAGING FORMAT
`FORMAT CAPABILITIES INFORMATION
`
`
`REQUEST
`CAPABILITIES INFORMATION |
`
`IDENTIFYING AT LEAST ONE
`
`
`OF SEVERAL MESSAGING
`
`
`RETRIEVE FIRST MOBILE WIRELESS
`FORMATS
`
`704_.__|COMMUNICATION DEVICE MESSAGING
`
`FORMAT CAPABILITIES INFORMATION
`
`SEND A MESSAGE IN A
`FROM THE MOBILE WIRELESS
`MESSAGE FORMAT
`COMMUNICATION DEVICE BASED ON
`
`
`
`
`
`COMPATIBLE WITH ATLEAST|504 THE FIRST MOBILE WIRELESS
`
`
`
`ONE OF THE MESSAGING
`sf
`COMMUNICATION DEVICE MESSAGING
`
`
`FORMATSIDENTIFIED IN THE
`FORMAT CAPABILITIES INFORMATION
`
`SECOND MOBILE WIRELESS
`REQUEST
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION ee|
`| GENERATE A FIRST MOBILE WIRELESS
`| COMMUNICATION DEVICE MESSAGING ,
`706-—~, FORMAT CAPABILITIES LIST BASED ON 1
`\
`THE FIRST MOBILE WIRELESS
`'
`1
`COMMUNICATION DEVICE MESSAGE
`,
`FORMAT CAPABILITIES INFORMATION,
`1
`BASED ON THE FIRST MOBILE
`| WIRELESS COMMUNICATION DEVICE |
`| MESSAGING FORMAT CAPABILITIES
`INFORMATION REQUEST
`
`
`
`
`
`
`
`
`FIG. 5
`:
`
`
`
`'
`
`¥ 600
`
`708—|
`
`“I
`
`OM
`
`L
`
`ATI
`
`
`
`
`opieWIRELESSCOMMUNICATION
`
`DEVICE MESSAGING FORMAT
`CAPABILITIES INFORMATION REQUEST
`CONTAINING THE FIRST MOBILE
`
`WIRELESS COMMUNICATION DEVICE
`MESSAGING FORMATCAPABILITIES
`
`INFORMATION
`
`
`
`
`
`
`Cee
`
`
`COMMUNICATION
`
`
`DEVICE MESSAGING
`
`
`FORMAT CAPABILITIES
`INFORMATION REQUEST |
`
`
`602
`
`
`
`
`RECEIVE A RESPONSE TO
`THE REQUEST, THE
`RESPONSE CONTAINING
`
`
`[--~
`THE MOBILE WIRELESS
`COMMUNICATION DEVICE|604
`MESSAGING FORMAT
`CAPABILITIES
`INFORMATION
`
`
`
`
`
`FIG. 6
`
`FIG. 7
`
`5
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 5 of 11
`
`US 2004/0203956 Al
`
`FIG. 8
`
`OBTAIN MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION
`IDENTIFYING AT LEAST ONE
`OF SEVERAL MESSAGING
`FORMATS
`
`PERFORM A LOCAL QUERY ON
`THE SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES BY THE FIRST
`MOBILE WIRELESS
`COMMUNICATION DEVICE
`
`CAPABILITIES INFORMATION
`
`SEND A MESSAGE IN A
`MESSAGE FORMAT
`COMPATIBLE WITH AT LEAST
`ONE OF THE MESSAGING
`FORMATSIDENTIFIED IN THE
`SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`
`6
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 6 of 11
`
`US 2004/0203956 Al
`
`FIG. 9
`
`OBTAIN MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION
`IDENTIFYING AT LEAST ONE OF
`
`9
`
`SEVERAL MESSAGING FORMATS l
`
`i|1 '
`
`1 I
`
`I |
`
`|
`
`STORE THE MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`904
`CAPABILITIES INFORMATION OF ! °)
`A SECOND MOBILE WIRELESS -
`| COMMUNICATION DEVICE IN THE ,
`MOBILE WIRELESS
`1
`COMMUNICATION DEVICE
`
`paces teem
`
`STORE THE SECOND MOBILE
`WIRELESS COMMUNICATION
`DEVICE MESSAGING FORMAT
`CAPABILITIES INFORMATION IN A |
`PHONE BOOK IN THE MOBILE
`|!
`WIRELESS COMMUNICATION
`DEVICE
`
`! gg
`SD
`
`1I'' 1!\l |
`
`I
`
`CAPABILITIES INFORMATION
`
`|'
`
`SEND A MESSAGE IN A MESSAGE
`FORMAT COMPATIBLE WITH AT
`LEAST ONE OF THE MESSAGING|504
`FORMATSIDENTIFIED IN THE
`SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`
`7
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 7 of 11
`
`US 2004/0203956 Al
`
`FIG. 10
`
`
`
`FROM
`FIG.
`114
`
`RECEIVE RECIPIENT
`ID FROM SEND
`MESSAGE
`CIRCUITRY
`
`a
`
`1008
`
`RECEIVE NEW
`MESSAGE ENTERED
`BY USER THROUGH
`SEND MESSAGE
`CIRCUITRY
`
`_-|STORE RECIPIENT
`4010°
`ID IN ACTIVE
`RECIEVE A REQUEST
`MESSAGE
`TO SEND A MESSAGE
`RECIPIENT LIST
`THROUGH SEND
`MESSAGE CIRCUITRY
`
`TO
`1202
`
`1102
`
`8
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 8 of 11
`
`US 2004/0203956 Al
`
`rt
`
`~
`
`FIG. 11
`
`FROM
`1010
`
`TO
`1002
`
`1102)
`
`<==
`
`
`PERFORM QUERY ON A DATABASE IN THE FIRST
`MOBILE WIRELESS COMMUNICATION DEVICE TO
`DETERMINE THE SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGING FORMAT
`CAPABILITIES
`
`
`
`
`
`
`
`
`
`
`SECOND MOBILE
`YES NO
`WIRELESS COMMUNICATION DEVICE
`NOT FOUND OR ENTRY EXPIRED
`
`
`
`1106 —
`
`1108 -
`
`
`GENERATE AND SEND SECOND MOBILE
`
`WIRELESS COMMUNICATION DEVICE MSG'G
`
`FORMAT CAPABILITIES REQUEST
`
`
`
`
`RECEIVE A SECOND MOBILE WIRELESS
`
`COMMUNICATION DEVICE MESSAGING FORMAT
`CAPABILITIES REQUEST
`
`1110—
`
`GENERATE AND SEND A SECOND MOBILE
`
`WIRELESS COMMUNICATION DEVICE MSG'G
`FORMAT CAPABILITIES LIST
`
`
`
`RECEIVE RESPONSE WITH SECOND MOBILE
`
`WIRELESS COMMUNICATION DEVICE MSG'G
`FORMAT CAPABILITIES LIST
`
`4112 ~
`
`
`
`
`1114 ~
`
`
`LOCATE FIRST
`
`MOBILE WIRELESS DEVICE
`
`DEFAULT MSG'G CAPABILITY IN THE
`SECOND MOBILE WIRELESS
`
`1116—~
`
`
`
`STORE THE SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGING FORMAT
`
`
`CAPABILITIES IN THE FIRST MOBILE WIRELESS
`COMMUNICATION DEVICE
`
`
`
`9
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 9 of 11
`
`US 2004/0203956 Al
`
`TEOO ms
`
`Y
`
`FIG. 12
`
`FROM
`1006
`
`1204
`
`NO
`
`
`
`~ 1202
`i
`
`FUNCTIONALITY SET OFF?
`
`
`
`
`
`|
`,
`
`CLEAR FLAGS OF
`
`ALL RECIPIENTS
`
`am
`FOR EACH UNFLAGGED RECIPIENT
`
`Ene.
`
`1206
`
`
`SEND MESSAGE WITH THE FIRST
`
`MOBILE WIRELESS COMMUNICATOIN
`DEVICE DEFAULT MESSAGING
`
`FORMAT
`— 4208
`-~1210
`
`NEXT
`ITEM
`
`
`FOR EACH RECIPIENT IN THE ACTIVE
`END]
`MESSAGE RECIPIENT LIST THAT IS
`NEXT ITEM
`
`FLAGGED
`
`
`
`
`
`
`
`DISPLAY OPTIONS AND
`INPUT USER SELECTION
`
`
`GENERATE USER NOTICE THAT RECIPIENT HAS LIMITED
`MSG'G CAPABILITIES AND SUGGES TO TRANSFORM THE
`
`
`MESSAGE TO AINTO A RECIPIENT COMPATIBLE FORMAT
`
`
`ACCEPT
`TRANSFORMATION
`
`= 1214
`
`DON'T ACCEPT
`TRANSFORMATION
`~ 1218
`
`1216
`
`PREPARE MESSAGE IN
`SELECTED FORMAT
`
`
`SEND MESSAGE AS
`FORMATTED
`
`\4202
`
`1224
`
`10
`
`10
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 10 of 11
`
`US 2004/0203956 Al
`
`FIG. 13
`
`1304
`
`pres
`
`:
`
`Mg
`
`f
`
`100
`
`1302 -°7° ss,
`\
`
`FIRST MOBILE
`WIRELESS
`COMMUNICATION
`
`LOCAL
`RELAY/SERVER
`
`DEVICE
`
`REMOTE
`
`RELAY/SERVER
`
`SECOND MOBILE
`WIRELESS
`COMMUNICATION
`DEVICE
`
`(—<—<—$K’—— MMie=———
`1330
`1332
`
`i1
`
`328
`
`as
`/(MM1_SUBMIT.REQ).~226
`
`(MM1_SUBMIT.RES)
`.
`
`4310
`
`f
`
`|
`\
`
`
`
` : (NEW CAPABILITIES
`
`226
`So
`
`(13140
`[(MM4_NOTIEICATION__
`REQ)
`
`_(MM1_NOTIFICATION
`
`(NEW CAPABILITIES
`SIGNAL THREE)
`\
`“e402
`
`“SIGNAL ONE)
`
`NETWORK 108
`
`11
`
`11
`
`

`

`Patent Application Publication Oct. 14,2004 Sheet 11 of11
`
`US 2004/0203956 Al
`
`- 1322
`
`NEW CAPABILITIES SIGNAL TWO
`
`, 1304
`_~ FROM: REMOTE RELAY/SERVER ~ 1302
`LOCAL RELAY/SERVER ——~—
`
`-MM_STATUS_CODE =
`
`X-MMS-MM-STATUS-CODE: —
`1410
`
`- UNRECOGNIZED ~~~
`
`1408
`
`1412
`
`FIG. 14
`
`NEW CAPABILITIES SIGNAL ONE
`
`1302
`
`7 1326
`
`1502
`15047
`
`-- MM_STATUS
`
`=
`
`- UNSUPPORTEDMESSAGE ~~
`1506
`toa [ves [NO[Yes|
`
`_~ FROM: LOCAL RELAY/SERVER —~
`_TO:
`FIRST MOBILE WIRELESS COMMUNICATION DEVICE ——~ 19°
`11508
`
`X-MMS-MM-STATUS: -—
`_1510
`
`- REJECTED -——~
`- UNSUPPORTED_MESSAGE —~
`
`, 1412
`
`FIG. 15
`
`PHONEBOOK:
`SECOND MOBILE WIRELESS COMMUNICATION DEVICE'S USER'S HOME
`(NON-MESSAGE SUPPORTING)
`
`1602
`
`MMS
`
`EMS
`
`SMS
`
`~ 406
`
`SECOND MOBILE WIRELESS COMMUNICATION DEVICE'S MOBILE
`({MMS/SMS SUPPORTED)
`
`L
`
`408
`
`FIG. 16
`
`12
`
`12
`
`

`

`US 2004/0203956 Al
`
`Oct. 14, 2004
`
`METHOD AND APPARATUS FOR PROVIDING
`WIRELESS MESSAGING
`
`FIELD OF THE INVENTION
`
`[0001] The invention relates generally to wireless com-
`munication systems and methods, and more particularly to
`methods and apparatus for providing wireless messaging.
`
`BACKGROUND OF THE INVENTION
`
`the invention that provides the obtaining of mobile wireless
`communication device messaging format capabilities before
`sending a message to the mobile wireless communication
`device in accordance with one embodimenttothe invention;
`
`FIG.3 is a block diagram illustrating the use of a
`[0008]
`phonebook as used in one example of a system in accor-
`dance with one embodiment of the invention;
`
`FIG.4 is a block diagram illustrating the use ofan
`(0009]
`active Message recipient list as used in one example of a
`system in accordance with one embodimentofthe invention;
`
`[0002] Mobile messaging systems, characterized by their
`non-real-time store-and-forward messaging to and from
`mobile messaging devices, currently exist. For example,
`(0010] FIG.5isa methodfor obtaining of mobile wireless
`Short Messaging Service (SMS), a text based mobile mes-
`communication device messaging format capabilities before
`sage system,
`is such a messaging service. Further, both
`sending a message to the mobile wireless communication
`Enhanced Messaging Service (EMS) and Multi-Media Ser-
`device in accordance with one embodiment of the invention;
`vice (MMS), cach text-plus based mobile messaging sys-
`tems, are also mobile messaging systems.
`
`FIG. 6 is a method, containing further detail asso-
`[0011]
`ciated with, obtaining of mobile wireless communication
`device messaging format capabilities before sending a mes-
`sage to the mobile wireless communication device in accor-
`dance with one embodiment of the invention;
`
`[0003] Current networks are known to exist which support
`the concurrent operation of multiple mobile messaging
`systems.
`In addition, such networks are also known to
`include mobile messaging devices that are compatible with
`[0012] FIG.7is a method, containing further detail asso-
`only a subset of the supported concurrent multiple mobile
`messaging systems. Such networks permit the sending of
`ciated with, obtaining of mobile wireless communication
`messages from a sending mobile messaging device having a
`device messaging format capabilities before sending a mes-
`first mobile messaging system format (e.g., MMS) to a
`sage to the mobile wireless communication device in accor-
`dance with one embodiment of the invention;
`receiving mobile messaging device capable of only receiv-
`ing messages in a second mobile messaging system format
`(c.g., SMS). Being unable to process the message due to the
`incompatibility of its messaging service capabilities with
`that of the format of the received message, the receiving
`mobile messaging device then typically bounces the mes-
`sage back to the sending mobile messaging device.
`[0014] FIG.9is a method, containing further detail asso-
`[0004]
`In this case where the message is bounced back due
`ciated with, obtaining of mobile wireless communication
`to an incompatible message system format,
`the sending
`device messaging format capabilities before sending a mes-
`messaging device is typically unable to determine this
`sage to the mobile wireless communication device in accor-
`incompatibility until after the message is sent. More spe-
`dance with one embodiment of the invention;
`cifically,
`the sending messaging device is typically only
`aware of the incompatibility after a number of events occur,
`namely: the message has been fully completed and thelist of
`delivery recipients has been set for delivery, the sending of
`the message has completed, the message has reached the
`receiving device, and the message has been bounced back to
`the sending device. As such, because the sending device is
`unaware of the incompatibility until after the message is
`bounced back, there is no opportunity for the sending device
`to change the content of the message, change the recipient
`list associated with the message, or choose not to send the
`message, before sending a message that will
`later be
`bounced back.
`
`[0013] FIG. 8 is a method, containing further detail asso-
`ciated with, obtaining of mobile wireless communication
`device messaging format capabilities before sending a mes-
`sage to the mobile wireless communication device in accor-
`dance with one embodiment of the invention.
`
`[0015] FIG. 10 is a flow chart illustrating one example of
`a method for obtaining of mobile wireless communication
`device messaging format capabilities before sending a mes-
`sage to the mobile wireless communication device in accor-
`dance with one embodiment of the invention;
`
`(0016] FIG. 11 is a flow chart illustrating one example of
`a method for obtaining of mobile wireless communication
`device messaging format capabilities before sending a mes-
`sage to the mobile wireless communication device in accor-
`dance with one embodiment of the invention;
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0005] The invention will be more readily understood with
`reference to the following drawings wherein like reference
`numerals represent like elements and wherein:
`
`[0006] FIG, 1 is a block diagram illustrating one example
`of a system in accordance with one embodiment of the
`invention that provides the obtaining of mobile wireless
`communication device messaging format capabilities before
`sending a message to the mobile wireless communication
`device.
`
`[0017] FIG. 12 is a flow chart illustrating one example of
`a method for obtaining of mobile wireless communication
`device messaging format capabilities before sending a mes-
`sage to the mobile wireless communication device in accor-
`dance with one embodiment of the invention;
`
`[0018] FIG. 13 is a flow chart illustrating one example of
`a method for obtaining of mobile wireless communication
`device messaging format capabilities within an MMSbased
`system, before sending a message to the mobile wireless
`communication device in accordance with one embodiment
`of the invention;
`
`FIG.2 is a detailed block diagram illustrating one
`[0007]
`example of a system in accordance with one embodiment of
`
`[0019] FIG. 14 is a more detailed representation of some
`of the aspects associated with the method of FIG, 13;
`
`13
`
`13
`
`

`

`US 2004/0203956 Al
`
`Oct. 14, 2004
`
`[0020] FIG. 15 is a more detailed representation of some
`of the aspects associated with the method of FIG. 13; and
`
`[0021] FIG. 16 is a more detailed representation of some
`of the aspects associated with the method of FIG. 13.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT
`
`(0022] Briefly, a method and apparatus, obtains mobile
`wireless communication device messaging format capabili-
`ties information, such as non-real-time store-and-forward
`messaging format capabilities, of a receiving mobile wire-
`less communication device. The method and apparatus,
`sends a message to the receiving mobile wireless commu-
`nication device in a message format compatible with one of
`the formats identified with the messaging format capabilities
`of the second mobile wireless communication device.
`Hence, different mobile wireless communication devices
`(e.g., cell phones, two-way pagers andother devices suitable
`for using non-real-time store-and-forward messaging) send
`and receive messages formatted under different
`types of
`non-real-time store-and-forward messaging that are under-
`stood by a
`receiving device.
`In one embodiment, such
`devices are also capable of obtaining messaging format
`capabilities information from a target or recipient mobile
`wireless communication device, that reflect which types of
`non-real-time
`store-and-forward messaging formats
`a
`mobile wireless communication device is capable of pro-
`cessing. Such devices, using the messaging format capabili-
`ties information,
`then send a message to a target mobile
`wireless communication device in a
`format
`that can be
`
`processed by the target mobile wireless communication
`device,
`
`In one embodiment, a sending mobile wireless
`[0023]
`communication devicestores the obtained messaging format
`capabilities information of the receiving mobile wireless
`communication device in a phonebook accessible by the
`sending mobile wireless communication device. This pro-
`vides for the advantage of quickly and locally obtaining the
`messaging format capabilities information of the receiving
`mobile wireless communication device without having to
`retrieve such information externally over a network. Further,
`of those embodiments utilizing a phonebook, such phone-
`book may be located separate from the sending mobile
`wireless communication device including at a location on
`the network.
`
`lers or alternatively discrete logic, state machines, or any
`suitable combination of hardware, software stored in
`memory and/or firmware. Further, in a preferred embodi-
`ment, the mobile wireless communication device messaging
`format capabilities determinator circuitry 104 and the send
`messaging circuitry 106 are software modules executing on
`DSPs contained within a mobile wireless communication
`device. Further, memory, as used herein, may be RAM,
`ROM,distributed memory in one or more circuits or loca-
`tions, optical or magnetic memory, or any suitable memory
`that is capable of storing digital information.
`
`In operation, the mobile wireless communication
`(0025]
`device messaging format capabilities determinator circuitry
`104 communicates through the transceiver 102 to the net-
`work 108 to obtain second mobile wireless communication
`device messaging format capabilities information 110. The
`second mobile wireless communication device messaging
`format capabilities information 110 may be data represent-
`ing that the device can process messages that are in an SMS
`format, EMS format, or another suitable format. The second
`mobile wireless communication device messaging format
`capabilities information 110 may be received froma target
`device, network element, or any other suitable source. The
`second mobile wireless communication device messaging
`format capabilities information 110 is received back from
`the network 108 through the transceiver 102 to the mobile
`wireless communication device messaging format capabili-
`ties determinator circuitry 104. The second mobile wireless
`communication device messaging format capabilities infor-
`mation 110 is stored in memory 107 andis associated with
`the corresponding second mobile wireless communication
`device (see FIG, 2). The send message circuitry 106 oper-
`ates to send a message in a message format compatible with
`at least one of the formats identified in the second mobile
`
`wireless communication device messaging format capabili-
`ties information 110. The send message circuitry 106 sends
`message 112,
`in a format identified in the second mobile
`wireless communication device messaging format capabili-
`ties information 110, to the network 108 via the transceiver
`102.
`
`(0026] Further, if desired, first mobile wireless communi-
`cation device 100 may operate such that the send message
`circuitry 106 allows a user to choose whether or not to send
`the message 112 depending on the second mobile wireless
`communication device messaging format capabilities infor-
`mation 110. For example, if the second mobile wireless
`communication device messaging format capabilities infor-
`FIG. 1 illustrates a mobile wireless communication
`[0024]
`mation 110 does not contain a message format capability
`device such as a cellular telephone, two-way pager, or other
`possessed by the first mobile wireless communication device
`device employing non-real-time store-and-forward messag-
`100, then, the user may choose to not send the message to
`ing (e.g., SMS, EMS, MMS messaging). As shown,afirst
`a second mobile wireless communication device 200 as the
`mobile wireless communication device 100 containsa trans-
`ceiver 102, mobile wireless communication device messag-
`ing format capabilities determinator circuitry 104, send
`messaging circuitry 106 and memory 107. Although shown
`separated here, other embodiments may combine the cir-
`cuitry of the mobile wireless communication device mes-
`saging format capabilities determinatorcircuitry 104 and the
`send messaging circuitry 106. Further,
`the first mobile
`wireless communication device 100 is further connected to
`
`message would be expected to be bounced backsince it is
`now known to be incompatible with message format capa-
`bilities of the first mobile wireless communication device.
`
`including the
`[0027] The circuitry described above,
`mobile wireless communication device messaging format
`capabilities determinatorcircuitry 104 and the send message
`circuitry 106, is preferably software modules. Such software
`modules can be stored as computer code on a variety of
`computer readable mediums, such as floppy disks, hard
`disks, compact disks, optical storage media, or any other
`suitable storage means for digital information. And such
`computer readable program code stored on such mediums,
`
`network 108. As used in this document, the term circuitry
`includes at least
`the following: one or more processing
`devices executing software stored in memory, such as micro-
`processors, digital signal processors (DSPs), microcontrol-
`
`14
`
`14
`
`

`

`US 2004/0203956 Al
`
`Oct. 14, 2004
`
`can be executed, causing one or more processors to perform
`the functionality inherent in such code, and as described
`above.
`
`FIG, 2 illustrates a system containing a first and
`[0028]
`second mobile wireless communication devices, 100 and
`200, connected over a wireless network such as a cellular
`wireless network, internet or other suitable network. Com-
`ponents similar to those shown in FIG, 1 are also included
`in the second mobile wireless communication device 200,
`and include the transceiver 102 and the mobile wireless
`communication device messaging format capabilities deter-
`minator circuitry 104.
`
`In addition, other components for the first mobile
`[0029]
`wireless communication device 100 not previously intro-
`duced in FIG.1 are also shown in FIG, 2. Such components
`include user interface 202, the first mobile wireless com-
`munication device messaging format capabilities informa-
`tion 203, remote messaging format capabilities determinator
`circuitry 208, local messaging format capabilities determi-
`nator circuitry 210, active message 216, active message
`recipient list 218, message text, files, etc. 220, and phone-
`book 222. Further, in one embodiment both phonebook 222
`and active message recipientlist 218 are both databases and
`both are stored in memory 107.
`
`[0030] Further, FIG. 2 shows the second mobile wireless
`communication device 200 to include the following; trans-
`ceiver 102, mobile wireless communication device messag-
`ing format capabilities determinator circuitry 104; second
`mobile wireless communication device messaging format
`capabilities information 110 and remote messaging format
`capabilities determinatorcircuitry 208.
`
`[0031] FIG.3 shows,in greater detail, the phonebook 222.
`Specifically, the phonebook 222 is shown to include recipi-
`ent name 302, recipient ID 304, phonebook flag 306, phone-
`book messaging format capabilities 308, phonebook last
`update time 310, and individual phonebook entry 312.
`
`[0032] FIG. 4 shows, in greater detail, the active message
`recipient list 218 offirst mobile wireless communication
`device 100. Specifically, active message recipient list 218 is
`further shown to include a recipient ID 402, recipient list
`recipient list flag 404 and a recipient list messaging format
`capabilities 406 as well as individual recipientlist entry 408.
`
`In operation, and referencing FIGS. 2-4, a user
`[0033]
`(not shown) interacts with the first mobile wireless commu-
`nication device 100 via the user interface 202 by entering
`message text, files, etc. 220 and an active message recipient
`list 218. As the active message recipient list 218 is populated
`with each recipient ID 402, then, in one embodiment having
`local messaging format capabilities determinator circuitry
`210 and a phonebook 222, immediately after each such
`recipient ID 402 is entered, the send message circuitry 106
`interacts the mobile wireless communication device mes-
`saging format capabilities determinator circuitry 104, spe-
`cifically the local messaging format capabilities determina-
`tor circuitry 210, to retrieve the second mobile wireless
`communication device messaging format capabilities infor-
`mation 110 associated with the second mobile wireless
`
`phonebookflag 306 is not set, the remote messaging format
`capabilities determinatorcircuitry 208 is called to determine
`the second mobile wireless communication device messag-
`ing format capabilities information 110. However, if the
`phonebook flag 306is set for the individual phonebook entry
`312,
`the phonebook messaging format capabilities 308,
`(e.g.,
`the second mobile wireless communication device
`messaging format capabilities information 110 previously
`stored in the phonebook), are returned to the local messaging
`format capabilities determinatory circuitry 210. The phone-
`book messaging format capabilities 308 are subsequently
`associated with the corresponding individual recipient list
`entry 408 in the active messagerecipientlist 218 as the new
`recipient list messaging format capabilities 406. Note, that
`the storing of the second mobile wireless communication
`device messaging format capabilities information 110 in an
`associated phonebook with the first mobile wireless com-
`munication device 100 provides quicker access to ihe capa-
`bilities information of the second mobile wireless commu-
`nication device 200 than if such information is only
`available over the network. Further, other embodiments do
`not utilize a phonebook 222 to store second mobile wireless
`communication device messaging format capabilities infor-
`mation 110, and as such retrieve the information remotely
`when needed.
`
`(0034] Further, if the corresponding phonebookflag 306 is
`set, (e.g., limited messaging capabilities have already been
`identified as being associated with such second mobile
`wireless communication device 200), and the phonebook’s
`last update time 310 has expired, (the time to refresh such
`messaging capabilities information has arrived), or if the
`phonebook flag 306 is not set, (e.g., no limited messaging
`capabilities have yet been identified as being associated with
`such second mobile wireless communication device 200),
`then the remote message format capabilities determinator
`circuitry 208 is then invoked and generates a second mobile
`wireless communication device messaging format capabili-
`ties information request 226 which is sent to the second
`mobile wireless communication device 200. Further, in the
`case where a local phonebook 222 and local messaging
`format capabilities determinator circuitry 210 is not used,
`(e.g., where the second mobile wireless communication
`device messaging format capabilities information 110 must
`be retrieved remotely), then for each recipient 402 entered in
`the active message recipient
`list 218,
`the same remote
`message format capabilities determinator circuitry 208 is
`then invoked to generate a second mobile wireless commu-
`nication device messaging format capabilities information
`request 226.
`[0035] After the first mobile wireless communication
`device 100 sends the second mobile wireless communication
`device messaging format capabilities information request
`226,
`the second mobile wireless communication device
`200’s remote messaging format capabilities determinator
`circuitry 208 receives the second mobile wireless commu-
`nication device messaging format capabilities information
`request 226. The second mobile wireless communication
`device 200 retrieves and sends the second mobile wireless
`communication device messaging format capabilities infor-
`mation 110 to the first mobile wireless communication
`
`communication device 200. If such recipient 402 is found in
`the phonebook 222, then, for that
`individual phonebook
`entry 312,it is determined whetherthere is a corresponding
`phonebook flag 306 set for that recipient ID 402. If the
`
`device 100 in response to the information request 226
`containing the second mobile wireless communication
`device messaging format capabilities information 110. The
`remote messaging format capabilities determinator circuitry
`
`15
`
`15
`
`

`

`US 2004/0203956 Al
`
`Oct. 14, 2004
`
`208 in the first mobile wireless communication device 100
`receives the second mobile wireless communication device
`
`messaging format capabilities information 110 and stores
`this information in memory 107 in a mannerthat associates
`the second mobile wireless communication device messag-
`ing format capabilities information 110 with the correspond-
`ing second mobile wireless communication device 200
`stored as a recipient in active message recipient list 218. If
`an attached phonebook 222 exists (e.g.,
`the associated
`embodiment
`includes the use of such a phonebook for
`storing such information) and either the corresponding indi-
`vidual phonebook entry 312 does not havea flag set, or the
`flag is set and the phonebook last update time 310 has
`expired,
`then,
`in either case,
`the second mobile wireless
`communication device messaging format capabilities infor-
`mation 110 will then be stored in the phonebook’s 222
`phonebook messaging format capabilities 308 for the cor-
`responding individual phonebook entry 312. This process of
`utilizing the mobile wireless communication device mes-
`saging format capabilities determinator circuitry 104 to
`determine the message format capabilities of the corre-
`sponding recipient ID 402, is repeated for each recipient ID
`402 entered in active message recipient list 218. Although
`each such recipient ID 402 is checkedasit is entered in the
`preferred embodiment, other embodiments include waiting
`to check such recipient ID 402 until after multiple recipient
`IDs are entered.
`
`[0036] When the user interface 202 detects a request to
`send the active message 216 (unformatted), the user inter-
`face 202 communicates this information to the send message
`circuitry 106. Upon detection of a request
`to send the
`message 112, a process begins which includes the looping
`through of the recipient IDs 402 in the active message
`recipient
`list 218 to send messages to each designated
`recipient. The send message circuitry 106, for each recipient
`ID 402 with a recipient
`list
`flag 404 not set, sends the
`message 112 in the default format ofthe first mobile wireless
`communication device 100 to the corresponding mobile
`wireless communication devices associated with the particu-
`lar recipient IDs 402.
`[0037] Further, for those recipient IDs 402 that have a
`corresponding recipient list flag 404 set, the send message
`circuitry 106 sends, to the user interface 202, a prompt to th