`
`US 20040203956A1
`
`(19} United States
`(12) Patent Application Publication (10) Pub. No.: US 2004/0203956 A1
`
`'l‘sampalis Oct. 14, 2004 (43) Pub. Date:
`
`
`(54} METHOD AND APPARATUS FOR
`PROVIDING WIRELESS MESSAGING
`
`(52} US. Cl.
`
`....................................... 455i466; 455,-“412.1
`
`(76)
`
`Inventor:
`
`loannis Tsampalis, Chicago, II. (US)
`
`(57)
`
`ABSTRACT
`
`Correspondence Address:
`VEDDICR PRICE KAUFMAN & KAMMHOLZ
`222 N. LASALLE STREET
`CHICAGO; IL 50601 (US)
`
`(21} Appl. No.:
`(22
`Filed:
`
`10"!335’140
`Dec. 31’ 2002
`
`Publication Classification
`
`Aiirsl mobile wireless communication deviee(100) includes
`mobile wireleas communication device messaging format
`capabilities determinator circuitry (104) operable to obtain
`second mobile wireless communication device messaging
`format capabilities information (110) ol‘ 3 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 oflhe formats. identified
`in the second mobile wireless communication device mes-
`
`{51}
`
`Int. CL? ....................................................... H04Q 7120
`
`saging format capabilities information (110).
`
`
`
`MOBILE WIRELESS COMMUNICFKTION
`
`DEVICE MESSAGING FORMAT CAPABILITIES
`
`DETERMINATOR CIRCUITRY
`/'402
`
`
`
`
`LOCAL MSG'G
`REMOTE MSGG
`
`
`FORMAT
`q.
`FUHMnT
`
`
`DETERMINATOR
`FORMAT cmalurles n" CAPAB'L'T'ES
`DEIEQEIJL‘QR
`
`
`CIRC UITRY
`INFORMAI IO
`CIRCUITRY
`
`
`
`
`
`
`
`
`
`
`
`r—20
`
`218
`ACTIVE MESSAGI;
`
`ACTIVE MSG RECIPIENT
`LIST
`
`
`
`
`
`
`FORMAT
`
` R EM OTE MSG'G
`
`.
`226,
`r'
`I110
`203 223
`t WW"
`FM“
`\ 112
`
`DETERMINATOR
`CAPABILITIES
`cmcunrw
`
`I,I"
`108
`
`1
`
`APPLE 1007
`
`APPLE 1007
`
`1
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 1 0f 11
`
`US 2004/0203956 A1
`
`FIG. 1
`
`108
`
`1X.“
`
`DEVICE MESSAGING FORMAT
`CAPABILITIES DETERMINATOR
`CIRCUITRY
`
`/ 104
`
`.
`
` MOBILE WIRELESS COMMUNICATION
`
`’3 110
`Y
`
`MEMORY
`
`‘\ 110
`
`Y
`
`SEND MESSAGE CIRCUITRY
`
`2
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 2 0f 11
`
`US 2004/0203956 A1
`
`FIG. 2
`
`r
`
`100
`
`
`FIRST MOBILE WIRELESS COMMUNICE‘OI'EON DEVICE
`
`
`USER INTERFACE
`/
`
`'
`220mm 1
`
`SEND MESSAGE CIRCUITRY
`
`10
`
`Ail
`
`/
`
`110:
`
`,
`
`
`FIRST MOBILE WIRELESS
`
`OMMUNICATION DEVICE MSG'
`-
`FORMAT CAPABILITIES
`“FORMATION
`mm-
`mm—
`EMS
`
`Ir
`
`
`
`
`REMOTE ”599
`LOCAL ”390
`FORMAT
`FORMAT
`
`
`
`
`CAPABILITIES
`CAPABILITIES
`
`
`DETERMINATOR
`DETERMINATOR
`CERCUITRY
`CIRCUITRY
`
`
`
`
` DETERMINATOR CIRCUITRY
`REMOTE MSG‘G
`("228
`
`FORMAT _i
`CAPABILITIES
`"" \
`\
`
`DETERMINATOR
`'
`‘
` CIRCUITRY
`
`
`
`
`
`
`
`
`
`
`
`MOBILE WIRELESS COMMUNICATION
`DEVICE MESSAGING FORMAT CAPABILITIES
`
`DETERMINATOR CIRCUITFIY
`402
`
`
`6
`
`
`
`3
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 3 0f 11
`
`US 2004/0203956 A1
`
`/- 222
`
`
`
`“a
`
`
`
`
`
`
`
`
`
`FLAG MSG’G FRMT CAPS LAST UPDATE TiME
`RECIPIENT NAME RECIPIENT ID
`II
`JANE DOE
`312-111—1111Mum-0111;111:122
`——m—_
`_—m——
`——_ 12:01:00 0000002
`—_m——
`——liI—_
`
`
`
`
`
`304
`
`FIG. 3
`
`308
`
`218
`
`WI!—
`
`—_
`—m_
`
`FIG. 4
`
`4
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 4 0f 11
`
`US 2004/0203956 A1
`
`
`
`
`
`
`
`OBTAIN MOBILE WIRELESS
`
`COMMUNICATION DEVICE
`
`MESSAGING FORMAT
`CAPABILITIES INFORMATION - "
`IDENTIFYING AT LEAST ONE
`
`OF SEVERAL MESSAGING
`FORMATS
`
`
`
`SEND A MESSAGE IN A
`
`MESSAGE FORMAT
`COMPATIBLE WITH AT LEAST
`ONE OF THE MESSAGING
`FORMATS IDENTIFIED IN THE
`SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`504
`
`
`
`
`
`GENERATE A MOBILE
`WIRELESS
`COMMUNICATION
`
`DEVICE MESSAGING
`
`FORMAT CAPABILITIES
`INFORMATION REQUEST
`
`
`
`
`
`
`
`
`704__H
`
`
`
`
`
`
`
`
`
`
`
`
`
`RECEIVE A FIRST MOBILE WIRELESS
`
`
`COMMUNICATION DEVICE MESSAGING
`FORMAT CAPABILITIES INFORMATION
`
`
`REQUEST
`
`
`RETRIEVE FIRST MOBILE WIRELESS
`
`
`COMMUNICATION DEVICE MESSAGING
`FORMAT CAPABILITIES INFORMATION
`FROM THE MOBILE WIRELESS
`COMMUNICATION DEVICE BASED ON
`THE FIRST MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGING
`FORMAT CAPABILITIES INFORMATION
`REQUEST
`
`
`
`-.JD03
`
`GENERATE A FIRST MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGING
`FORMAT CAPABILITIES LIST BASED ON
`THE FIRST MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGE
`FORMAT CAPABILITIES INFORMATION,
`BASED ON THE FIRST MOBILE
`WIRELESS COMMUNICATION DEVICE
`MESSAGING FORMAT CAPABILITIES
`INFORMATION REQUEST
`
`|_-___-___J___,
`
`7E)8—~w
`
`
`
`
`
`
`
`
`SEND A RESPONSE TO THE FIRST
`
`MOBILE WIRELESS COMMUNICATION
`
`DEVICE MESSAGING FORMAT
`CAPABILITIES INFORMATION REQUEST
`CONTAINING THE FIRST MOBILE
`
`WIRELESS COMMUNICATION DEVICE
`MESSAGING FORMAT CAPABILITIES
`
`INFORMATION
`
`
`
`
`
`
`
`
`RECEIVE A RESPONSE TO
`THE REQUEST, THE
`RESPONSE CONTAINING
`THE MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES
`INFORMATION
`
`
`
`
`
`
`
`
`
`
`
`
`FIG. 7
`
`5
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 5 0f 11
`
`US 2004/0203956 A1
`
`FIG. 8
`
`OBTAIN MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION
`_ IDENTIFYING AT LEAST ONE
`OF SEVERAL MESSAGING
`FORMATS
`
`
`
`(
`502
`
`PERFORM A LOCAL QUERY ON
`THE SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES BY THE FIRST
`MOBILE WIRELESS
`
`COMMUNICATION DEVICE
`
`SEND A MESSAGE IN A
`MESSAGE FORMAT
`COMPATIBLE WITH AT LEAST
`ONE OF THE MESSAGING
`504
`FORMATS IDENTIFIED IN THE /
`SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION
`
`
`
`6
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 6 0f 11
`
`US 2004/0203956 A1
`
`FIG. 9
`
`OBTAIN MOBILE WIRELESS
`
`SEVERAL MESSAGING FORMATS
`
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`CAPABILITIES INFORMATION
`IDENTIFYING AT LEAST ONE OF
`
`502
`/
`
`lII '
`
`I ________
`STORE THE MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`
`904
`CAPABILITIES INFORMATION OF I J
`A SECOND MOBILE WIRELESS
`:—
`I COMMUNICATION DEVICE IN THE I
`1
`MOBILE WIRELESS
`l
`.
`COMMUNICATION DEVICE
`I
`I ........ I. - - - - _ _ -.,
`
`III I
`
`906
`I
`STORE THE SECOND MOBILE
`1 /)
`WIRELESS COMMUNICATION
`|
`DEVICE MESSAGING FORMAT
`: CAPABILITIES INFORMATION IN A .
`l
`PHONE BOOK IN THE MOBILE
`I
`. WIRELESS COMMUNICATION
`I
`:
`DEVICE
`:I
`I— ————————————————
`
`504
`
`SEND A MESSAGE IN A MESSAGE
`FORMAT COMPATIBLE WITH AT
`LEAST ONE OF THE MESSAGING
`FORMATS IDENTIFIED IN THE
`SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE
`MESSAGING FORMAT
`
`CAPABILITIES INFORMATION
`
`7
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 7 0f 11
`
`US 2004/0203956 A1
`
`FIG. 10
`
`MESSAGE CIRCUITRY
`
`MEEEEE‘IEEflIEEKED
`BY USER THROUGH
`SEND MESSAGE
`CIRCUITRY
`
`RECIEVE A REQUEST
`TO SEND A MESSAGE
`THROUGH SEND
`
`RECEIVE RECIPIENT
`ID FROM SEND
`MESSAGE
`CIRCUITRY
`
`STORE RECIPIENT
`ID IN ACTIVE
`MESSAGE
`RECIPIENT LIST
`
`{/—
`
`1008
`
`/"
`
`1010 I
`
`TO
`1202
`
`1102
`
`8
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 8 0f 11
`
`US 2004/0203956 A1
`
`"“th
`
`\‘
`
`FIG. 11
`
`FROM
`1010
`
`TO
`1 002
`
`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
`k OT FOUND OR ENTRY EXPIR I
`
`
`
`
`1106“
`
`1103—
`
`1110..
`
`
`GENERATE AND SEND SECOND MOBILE
`WIRELESS COMMUNICATION DEVICE MSG'G
`
`FORMAT CAPABILITIES REQUEST
`
`
`
`
`RECEIVE A SECOND MOBILE WIRELESS
`COMMUNICATION DEVICE MESSAGING FORMAT
`
`
`CAPABILITIES REQUEST
`
`
`
`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
`
` 1112 a
`
`
`1114 ‘
`LOCATE FIRST
`
`
`MOBILE WIRELESS DEVICE
`
`
`
`DEFAULT MSG'G CAPABILITY IN THE
`
`SECOND MOBILE WIRELESS
`
`SG'
`
`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 0f 11
`
`US 2004/0203956 A1
`
`1200
`
`_
`
`“m...“
`
`“x
`1
`
`FIG. 12
`
`FROM
`1006
`
`,1204
`
`NO
`
`x/H 1202
`
`FUNCTIONALITY SET OFF?
`
`
`
`YES
`
`
`CLEAR FLAGS OF
`
`ALL RECIPIENTS
`
`END
`
`FOR EACH UNFLAGGED RECIPIENT
`
`1206
`
`[a
`
`SEND MESSAGE WITH THE FIRST
`
`MOBILE WIRELESS COMMUNICATOIN
`
`DEVICE DEFAULT MESSAGING
`FORMAT
`
`\“H 1208
`r—“- 1210
`
`
`NEXT
`ITEM
`
`
`
`NEXT ITEM
`FOR EACH RECIPIENT IN THE ACTIVE
`END
`MESSAGE RECIPIENT LIST THAT IS
`
`FLAGGED
`
`
`DISPLAY OPTIONS AND
`INPUT USER SELECTION
`
`
`
`GENERATE USER NOTICE THAT RECIPIENT HAS LIMITED
`
`
`MSG‘G CAPABILITIES AND SUGGES TO TRANSFORM THE
`MESSAGE TO A INTO A RECIPIENT COMPATIBLE FORMAT
`
`
`ACCEPT
`TRANSFORMATION
`
`
`
`PREPARE MESSAGE IN
`SELECTED FORMAT
`
`
`
`
`
`
`“"1214
`
`DON'T ACCEPT
`TRANSFORMATION
`
`r’ 1213
`
`1216
`
`
`
`SEND MESSAGE AS
`FORMATTED
`\— 1222
`
`1224
`
`10
`
`10
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 10 of 11
`
`US 2004/0203956 A1
`
`FIG. 13
`
`1304
`
`/100
`
`1302\ {I {290
`
`FIRST MOBILE
`WIRELESS
`COMMUNICATION
`DEVICE
`
`
`
`LOCAL
`RELAYISERVER
`
`REMOTE
`RELAYI'SERVER
`
`SECOND MOBILE
`WIRELESS
`COMMUNICATION
`DEVICE
`
`:
`f
`
`f
`
`1328
`
`1330
`
`1332
`
`396
`JIMMLSUBMITREQI/ "‘ 225
`
`(MMLSUBMIT RES)
`.
`I
`
`/_
`
`1310
`
`
`
`
`
`
`
`a (NEW CAPABILITIES
`SIGNAL ONE)
`
`{1314
`I:MM1_N0fifiICATION_
`REG)
`
`J
`
`h
`
`(NEW CAPABILITIES
`SIGNAL THREE)
`I
`
`\~1703
`
`I
`
`“1320
`
`NETWORK 108
`
`11
`
`11
`
`
`
`Patent Application Publication Oct. 14, 2004 Sheet 11 0f 11
`
`US 2004/0203956 A1
`
`‘ 1322
`
`NEW CAPABILITIES SIGNAL Two
`
`. UNSUPPORTED_MESSAGE -'/
`
`1304
`/- FROM: REMOTE RELAYI‘SERVER "’ ,1302
`1402 — TO:
`LOCAL RELAYISERVER ——-”’
`14 4”
`0
`“Clef-- MM_STATUS_CODE
`
`XnMMS-MM-STATUS-CODE: ‘-
`1410
`. UNRECOGNIZED .--/
`
`,1408
`
`.1412
`
`FIG. 14
`
`(m 1326
`
`NEW CAPABILITIES SIGNAL ONE
`
`1302
`
`/ FROM: LOCAL RELAYISERVER 3’
`1502,- TO:
`FIRST MOBILE WIRELESS COMMUNICATION DEVICE 3” 100
`1504
`)1508
`
`1506
`
`/‘ MM_STATUS
`
`X-MMS—MM-STATUS: ..- ”
`,1510
`
`- REJECTED “M”
`- UNSUPPORTED_MESSAGE a“
`
`1,1412
`
`FIG. 15
`
`PHONEBOOK:
`SECOND MOBILE WIRELESS COMMUNICATION DEVICE'S USER'S HOME
`
`((NON-MESSAGE SUPPORTING}
`
`1602
`
`, 405
`
`1604 —_-IE-
`
`SECOND MOBILE WIRELESS COMMUNICATION DEVICE'S MOBILE
`{MMSI‘SMS SUPPORTED)
`
`k
`
`#406
`
`FIG. 16
`
`12
`
`12
`
`
`
`US 2004/0203956 A1
`
`Oct. 14, 2004
`
`METHOD AND APPARATUS FOR PROVIDING
`WIRELESS MESSAGING
`
`FIELD OF 'I'IIl-j. INVEN'I‘ION
`
`[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
`
`[0002] Mobile messaging systems, characterised by their
`non—real—time store—and—forward messaging to and from
`mobile messaging devices, currently exist. For example,
`Short Messaging Service (SMS), a text based mobile mes-
`sage system,
`is such a messaging service. Further, both
`Enhanced Messaging Service (EMS) and Multi-Media Ser-
`vice (MMS), each text-plus based mobile messaging sys-
`tems, are also mobile messaging systems.
`
`[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
`only a subset of the supported concurrent multiple mobile
`messaging systems. Such networks permit the sending of
`messages from a sending mobile messaging device having a
`Iirst mobile messaging system format {e.g., MMS) to a
`receiving mobile messaging device capable of only receiv-
`ing messages in a second mobile messaging system format
`{e.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 baclt to the sending mobile messaging device.
`
`In this case where the message is bounced back due
`[0004]
`to an incompatible message system format,
`the sending
`messaging device is typically unable to determine this
`incompatibility until after the message is sent. More spe-
`cifically,
`the sending messaging device is typically only
`aware of the incompatibility after a number of events occur,
`namely: the message has becn fully completed and the list 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.
`
`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 elcmcnts 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.
`
`the invention that provides the obtaining ofmobile wireless
`communication device messaging format capabilities before
`sending a message to the mobile wireless communication
`device in accordance with one embodiment to the invention;
`
`[0008] FIG. 3 is a block diagram illustrating the use of a
`phonebook as used in one example of a system in accor-
`dance with one embodiment of the invention;
`
`[0009] FIG. 4 is a block diagram illustrating the use of an
`active message recipient list as used in one example of a
`systcm in accordance with one embodiment of the invention;
`
`[0010] FIG. 5 is a method for obtaining of mobile wireless
`communication device messaging format capabilities before
`sending a message to the mobile wireless communication
`device in accordance with one embodiment of the invention;
`
`[0011] FIG. 6 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;
`
`[0012] FIG. 7 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;
`
`[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.
`
`[0014] FIG. 9 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 [low 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;
`
`[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 wirelcss 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 MMS based
`system, before sending a message to the mobile wireless
`communication device in accordance with one embodiment
`of the invention;
`
`[0007] FIG. 2 is a detailed block diagram illustrating one
`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 A1
`
`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—rcal—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 and other 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-fonavard 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 device stores the obtained messaging format
`capabilities information of the receiving mobile wireless
`communication device in a phoncbook accessible by the
`sending mobile wireless communication device. This pro-
`vides for the advantage of quickly and locally obtaining the
`messaging formal capabilities information of the receiving
`mobile wireless communication device without having to
`retrieve such in formation 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.
`
`[0024] FIG. 1 illustrates a mobile wireless communication
`device such as a cellular telephone, two-way pager, or other
`device employing non-real-time store-and-forward messag-
`ing (e.g., SMS, EMS, MMS messaging). As shown, a first
`mobile wireless communication device 100 contains a 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 determinator circuitry 104 and the
`send messaging circuitry 106. Further,
`the first mobile
`wireless communication device 100 is further connected to
`
`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-
`
`lers or alternatively discrete logic, state machines, or any
`suitable combination of hardware, software stored in
`memory andtor 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 formal capabilities information 110. The
`second mobile wireless communication device messaging
`format capabilities information 1.10 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 front a target
`device, network element, or any other suitable source. The
`second mobile wireless communication device messaging
`format capabilities information 1.10 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 and is 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 formal capabili-
`ties information 110, to the network 108 via the transceiver
`102.
`
`[0026] Further, ifdesired, first mobile wireless communi-
`cation dcvice 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-
`mation 110 does not contain a message format capability
`possessed by the first mobile wireless communication device
`100, then, the user may choose to not send the message to
`a second mobile wireless communication device 200 as the
`
`message would be expected to be bounced back since it is
`now known to be incompatible with message format capa-
`bilities of the first mobile wireless communication device.
`
`including the
`'I‘he circuitry deseribed above,
`[0027]
`mobile wireless communication device messaging format
`capabilities determinator circuitry 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,
`
`14
`
`14
`
`
`
`US 2004/0203956 A1
`
`Oct. 14, 2004
`
`can be executed, causing one or more processors to perform
`the functionality inherent in such code, and as described
`above.
`
`[0028] FIG. 2 illustrates a system containing a first and
`second mobile wireless communication devices. 100 and
`200, connected over a wireless network such as a cellular
`wireless network, intemet 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 formal capabilities determinator
`circuitry 208, local messaging format capabilities detenni-
`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 recipient list 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 determinator circuitry 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 [tag 306, phone-
`book messaging format capabilities 308. phonebook last
`update time 310, and individual phonebook entry 312.
`
`[0032] FIG. 4 shtth, in greater detail, the active message
`recipient list 218 of first 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 4-04 and a recipient list messaging format
`capabilities 406 as well as individual recipient list 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 phoncbook 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
`
`phonebook flag 306 is not set, the remote messaging format
`capabilities determinator circuitry 208 is called to determine
`the second mobile wireless communication device messag—
`ing format capabilities information 110. However, if the
`phonebook flag 306 is set for the individual phonebook entry
`312,
`the phonebook messaging format capabilities 308,
`(cg, 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 message recipient list 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 the 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, il‘the corresponding phonebook [lag 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, (eg, 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 whether there is a corresponding
`phonebook llag 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 in formation 1'10. The
`remote messaging format capabilities determinator circuitry
`
`15
`
`15
`
`
`
`US 2004/0203956 A1
`
`Oct. 14, 2004
`
`208 in the first mobile wireless communication device 100
`receives the second mobile wireless communication device
`
`messaging formal capabilities information 110 and stores
`this information in memory 107 in a manner that 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 phoncbook entry 312 does not have a 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 checked as it is entered in the
`preferred embodiment, other embodiments include waiting
`to check such recipient ID 4-02 until after multiple recipient
`IDs are entered.
`
`[0036] When the user interface 202 detects a request to
`send the active message 216 (unforrnatted), 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 of the first mobile wireless
`communication device 100 to the corresponding mobile
`wireless communication devices associated with the particu—
`lar recipient [Us 402.
`
`[0037] Further, for those recipient IDs 402 that have a
`corresponding recipient list flag 404 set, the send message
`circuitry 1