(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2003/0104827 A1
`(43) Pub. Date: Jun. 5, 2003
`
`Moran et al.
`
`US 20030104827A1
`
`(54) REROUTING/REFORMATING WIRELESS
`MESSAGES FOR CROSS CONNECTIVITY
`BETWEEN SERVICE PROVIDERS
`
`(76)
`
`Inventors: Brian Moran, Preston, WA (US),
`David Feinleib, Kirkland, WA (US);
`Chuck Mount, Kirkland, WA (US)
`
`Correspondence Address:
`R. Alan Burnett
`BLAKELY, SOKOLOFF, TAYLOR & ZAFMAN
`LLP
`Seventh Floor
`12400 VVilshire Boulevard
`
`Los Angeles, CA 90025-1026 (US)
`
`(21) Appl. No.:
`
`10/000,223
`
`(22)
`
`Filed:
`
`Nov. 30, 2001
`
`Publication Classification
`
`(51)
`
`Int. Cl.7 ....................................................... H04Q 7/20
`
`(52) US. Cl.
`
`............................................ 455/466; 455/458
`
`(57)
`
`ABSTRACT
`
`A method and system that enables Wireless device users to
`send messages from their devices to other Wireless devices
`that use a different service provider than the sending device.
`Generally, the method and system are enabled through use
`of a third party rerouting/reformatting service that appears
`transparent to the Wireless device users and service provid-
`ers. In one embodiment, the method includes converting an
`original SMS message into an e-mail message and routing
`the e-mail message to the rerouting/reformatting service,
`whereupon the e—mail message is reformatted into a desti—
`nation message that is dispatched for delivery to a destina-
`tion device selected by a user who generated the original
`SMS message. In another embodiment, rerouting indieia is
`.
`.
`appended to an SMS [message such that it IS routed to the
`rerouting/reformatting service, which again performs refor-
`matting and message dispatch functions to deliver the mes-
`sage to a selected destination device.
`
`AT&T
`WIRE _ESS
`AT&T
`USER 2
`WIRELESS
`
`
`'
`USER1
`.120 AT&T WIRELESS
`SMPT GATEWAY
`VERIZON
`
`2
`
`60
`
`64 /
`
`14
`l
`
`
`
`§§
`
`
`
`26
`VESEZRON
`1
`
`
`
`'
`
`36
`
`
`
`7 /
`I?
`|
`.;
`:1»
`i/
`30 g
`’4‘“
`
`1.
`
`
`
`SMPT GATEWAY
`
`66
`
`VOICESTREAM
`SMPT GATEWAY
`
`68
`
`SPRINT PCS
`SMPT GATEWAY
`
`ll @72
`70
`REROUTING/
`97
`REFORMMATING
`SERVICE
`
`w
`
`WAP
`
`40x VOICESTREAM
`SMSC
`
`INST. MESSAGING
`SERVICE CTR.
`
`67
`
`50“
`
`SPRINT PCS
`SMSC
`
`L» LAND—LINE SMPT
`
`POP3
`
`69
`
`71
`
`VOICESTREAM
`USE
`R1
`
`
`
`SPRINT p03
`USER 1
`
`
`
`
`
`
`
`
`
`
` 16’\
`
`a @n62, e4, 66, 68
`
`+ PROVIDER SMPT
`
`AT&T
`WIRELESS
`SMSC
`
`
`
`
`
`28“
`VERIZON
`SMSC
`
`
`
`
`
`
`—> PROVIDER SMSCIII16, 28, 40, 50
`
`II
`-LI
`
`
`
`
`
`a
`93
`
`
`
`
`
`APPLE 1006
`
`APPLE 1006
`
`1
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 1 0f 10
`
`US 2003/0104827 A1
`
`AT&T
`WIRELESS
`USER 1
`
`AT&T
`WIRELESS
`USER 2
`.l
`
`
`
`16
`
`AT&T
`WIRELESS
`
`14
`
`/
`
`In
`
` Ema"?
`SMSC
`
`'‘
`
`
`
`VERIZON
`USER 1
`
`”x VOICESTREAM
`/
`/
`/
`/
`USER 2
`/ /\\\
`
`/ /
`
`4)
`A}?‘1‘:
`
`
`
`SPRINT PCS
`USER 2
`
`
`
`VOICESTREAM
`USER 1
`
`
`
`SPRINT PCS
`SMSC
`
`SPRINT PCS
`USER 1
`
`50
`
`FIG. 1 (PRIOR ART)
`
`2
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 2 0f 10
`
`US 2003/0104827 A1
`
`AT&T
`WIRELESS
`USER 2
`
`AT&T
`WIRELESS
`USER 1
`
`FIG. 2A
`
`62
`
`64
`
`/60
`
`66
`
`89
`
`68
`
`,1
`
`20
`
`AT&T WIRELESS
`SMPT GATEWAY
`
`VERIZON
`SMPT GATEWAY
`
`VOICESTREAM
`SMPT GATEWAY
`
`SPRINT PCS
`SMPT GATEWAY
`
`
`1'....=:_441“\\‘\‘“\‘7'
`
`1’
`
` 26
`
`VERIZON
`USER 1
`
`
`
`VOICESTREAM
`USER 1
`
`46
`
`
`
`
`
`USER 1
`
`REROUTING/
`
`REFORMMATING
`
`SERVICE
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`AT&T
`WIRELESS
`SMSC
`
`62, 64, 66, 68
`
`PROVIDER SMPT
`
`’V VERIZON
`SMSC
`
`PROVIDER SMSC
`
`16, 28, 40, 5O
`
`
`
`“VOICESTREAM
`SMSC
`
`INST. MESSAGING
`SERVICE CTR.
`
`SPRINT PCS
`SMSC
`
`
`
`LAND—LINE SMPT
`
`
`
` 9
`
`71
`
`6
`
`3
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 3 0f 10
`
`US 2003/0104827 A1
`
`AT&T
`WIRELESS
`USER 2
`
`FIG- 23
`
`16
`
`AT&T
`WIRELESS
`USER ‘I
`
`
`
`
`
`26
`VERIZON
`USER 1
`
`
`
`I
`ll
`g;
`a“
`g;
`Q!
`::><><
`30 4.'
`
`SMSC
`
`/61
`
`89
`
`
`
`
`VOICESTREAM
`USER 1
`
`46
`
`
`
`fl-mp.
`
`J: 00
`
`SPRINT PCS
`USER ‘I
`
`(”(-1
`
`16
`
`I
`
`ll'lln..._._=I: SSaw”4:.
`
`
`
`73
`
`72
`
`
`
`
`
`
`
`REROUTING/
`
`
`REFORMMATING
`
`SERVICE
`
`AT&T
`WIRELESS
`SMSC
`
`
`
`16, 28,40, 50
`
`INST. MESSAGING
`SERVICE CTR.
`
`SPRINT PCS
`SMSC
`
`
`
`LAND-LINE SMPT
`
`69
`
`71
`
`4
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 4 0f 10
`
`US 2003/0104827 A1
`
`83
`
`7
`
`AT&T WIRELESS
`SMPT GATEWAY
`
`/70
`
`,___._____________.__A7_‘7_______________
`REROUTING/REFORMATTING SERVICE
`
` TRANSACTION
`‘_
`
`
`
`
`
`|I|I|II II
`
`IIIIII
`
`I
`
`I I
`
`I
`
`82
`
`
`
`l-—
`
`
`b76IIIIII _
`
`
`
`APPLICATION SERVER
`
`
`AII]HLJ|1|J_ —
`
`.
`
`POPS SERVER
`
`
`
`
`
`EXTRACTOR &
`
`MESSAGE
`
`REF ORMATTER
`
`
`SEND MESSAGE TO SMSC <1
`OR SMTP GATEWAY
`
`
`
`DESTINATION
`MESSAGE
`
`
`
`
`
` LAND-LINE SMPT
`
`
`AT&T
`WIRELESS
`
`SMSC
`
`VERIZON
`SMSC
`
`VOICESTREAM
`SMSC
`
`SPRINT PCS
`SMSC
`
`
`
`
`
`INST. MESSAGING
`
`
`SERVICE CTR.
`
`
`
` 50
`
`FIG. 3A
`
`5
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 5 0f 10
`
`US 2003/0104827 A1
`
`
`
`"i_ TRANSACTION
`WIRELESS
`
`hs
`
`SMSC
`DATABASE fish PHONE MAP
`
`V
`~§§E DEVICE CAPS
`
`- L
`NEEE DEVICES
`
`
`
`
`“5E;
`USER
`
`
`
`EXTRACTOR &
`
`
`lflflllfl‘
`MESSAGE
`HJIIIHM
`
`
`REF ORMATTER
`
`
`
`
`
`
`
`
`
`
`
`
`
`AT&T
`WIRELESS
`SMSC
`
`
`
`
`
`
`
`
`
`6
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 6 0f 10
`
`US 2003/0104827 A1
`
`
`
`USER ENTERS TEXT MESSAGE AND SELECTS
`UNIQUE IDENTIFIER FOR DESTINATION DEVICE
`
`
`
`
`REROUTING/REFORMA'ITING SERVICE DOMAIN
`IS APPENDED TO PHONE NUMBER TO CREATE
`
`A URL ADDRESS
`
` TEXT MESSAGE IS SENT AS AN E—MAIL
`
` 104
`MESSAGE TO AN SMTP GATEWAY
`
`100
`
`102
`
`
`CORRESPONDING TO SERVICE PROVIDER
`
`
`
`E—MAIL MESSAGE IS ROUTED FROM SMTP
`GATEWAY TO REROUTING/REFORMATTING
`SERVICE URL ADDRESS
`
`106
`
`EXTRACT TEXT CONTENT, SENDING DEVICE ID
`AND DESTINATION DEVICE ID
`
`108
`
`
`
`RETRIEVE USER ID, DESTINATION DEVICE
`CAPABILITIES AND WIRELESS ACCESS POINT
`
`FROM DATABASE BASED ON SENDING DEVICE
`
`
`ID AND DESTINATION DEVICE ID
`
`
`
`
`
`
`
`IDENTIFY DESTINATION ROUTE SERVICE
`
`PROVIDER(S) BASED ON WIRELESS ACCESS
`
`POINT AND/OR DESTINATION DEVICE CAPS
`
`
`
`
`
`
`
`
`REFORMAT MESSAGE AS NECESSARY TO
`CORRESPOND TO RULES FOR DESTINATION
`
`SERVICE PROVIDER(S) AND DEVICE CAPS
`
`
`
`
`
`DELIVER MESSAGE TO DESTINATION DEVICE
`VIA APPROPRIATE SERVICE PROVIDER
`
`FACILITIES (E.G., SMSC, SMPT GATEWAY, ETC.)
`
`
`
`
`
`TRANSACTION INFORMATION IS RECORDED IN
`
`SERVICE DATABASE FOR BILLING RECORDS
`
`110
`
`112
`
`114
`
`116
`
`118
`
`FIG. 4A
`
`7
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 7 0f 10
`
`US 2003/0104827 A1
`
`USER ENTERS TEXT MESSAGE AND SELECTS
`UNIQUE IDENTIFIER FOR DESTINATION DEVICE
`
`200
`
`REROUTING INDICIA IS APPENDED TO UNIQUE
`IDENTIFIER TO REROUTE MESSAGE TO
`REROUTING SERVICE
`
`
`
`
`
`
`
`SMSC IDENTIFIES REROUTING INDICIA AND
`REDIRECTS MESSAGE TO REROUTING
`
`SERVICE
`
`
`SMS MESSAGE IS SENT TO SMSC FOR
`SENDING DEVICE SERVICE PROVIDER
`
`202
`
`204
`
`206
`
`EXTRACT TEXT CONTENT, SENDING DEVICE ID
`AND DESTINATION DEVICE ID
`
`108
`
`
`RETRIEVE USER ID, DESTINATION DEVICE
`CAPABILITIES AND WIRELESS ACCESS POINT
`
`FROM DATABASE BASED ON SENDING DEVICE
`
`
`ID AND DESTINATION DEVICE ID
`
`
`
`
`
`
`
`IDENTIFY DESTINATION ROUTE SERVICE
`PROVIDER(S) BASED ON WIRELESS ACCESS
`
`
`POINT AND/OR DESTINATION DEVICE CAPS
`
`
`
`
`
`REFORMAT MESSAGE AS NECESSARY TO
`CORRESPOND TO RULES FOR DESTINATION
`
`
`SERVICE PROVIDER(S) AND DEVICE CAPS
`
`
`
`
`
`DELIVER MESSAGE TO DESTINATION DEVICE
`VIA APPROPRIATE SERVICE PROVIDER
`
`FACILITIES (E.G., SMSC, SMPT GATEWAY, ETC.)
`
`
`
`
`
`TRANSACTION INFORMATION IS RECORDED IN
`
`SERVICE DATABASE FOR BILLING RECORDS
`
`110
`
`1’12
`
`114
`
`116
`
`118
`
`FIG. 4B
`
`8
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 8 0f 10
`
`US 2003/0104827 A1
`
`
`
`USER SIGNUP
`
`USER ID INFORMATION:
`
`USER ID:
`
`<USER |D>
`
`CONTACT INFORMATION:
`
`STREET ADDRESS 1:
`
`ADDRESS LINE 1>
`
`142 STREET ADDRESS 2:
`
`<ADDRESS LINE 2>
`
`CITY: <ADDRESS LINE 2>
`ZIP COD ' <ZIP CODE>
`
`STATE: STATE>
`E-MAIL: <E-MAIL ADDRESS>
`
`a
`
`146
`
`PHONE :<PHONE NUMBER>
`
`150
`
`148
`
`<DEV|CE NAME>
`DEVICE # 1 DEVICE NAME:
`<DEVICENAME>
`INFO:
`DEVICEID;
`@162
`@1160
`©v156 9/153
`PHONE
`PAGER FDA/HANDHELD E-MAILADDRESS
`
`152
`154
`
`DEVICE PHONE NUMBER:
`
`<PHONE NUMBER>
`
`164
`
`SERVICE PROVIDER:
`
`<VOICESTREAM>
`
`n
`
`5ng mmggg: Waggggmggggggw
`© IMMEDIATE DELIVERY'xJ170
`174
`O BATCH DELIVERYw 172
`CONFIRM DELIVERY
`
`BILLING INFORMATION:
`
`CREDIT CARD:
`<MASTERCARD>
`
`178
`
`n
`
`CREDIT CARD #:
`#### ## ##5## ##1##
`
`180
`
`
`
`PASSWORD: E
`
`CONFIRM PASSWORD: :v
`
`
`
`
`
`9
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 9 0f 10
`
`US 2003/0104827 A1
`
`
`In——
`
`- RULE DEFINITION VARCHAR(1023)
`
`
`
`
`
`RULE DEFINITIONS
`
` 85
` 84
`AL
`
`
`
`USERID
`
`
`
`
`VARCHAR(30)
`USER RULES
`PASSWORD
`VARCHAR(15)
`
`
`
`
`ADD LINE 1
`VARCHAR(30)
`ADD LINE 2
`
`VARCHAR(SO)
`VARCHAR(20)
`
`CITY
`
`
`SHORT
`
`VARCHAR(30)
`
`
`STATE
`
`
`
`CHAR(2)
`EMAIL
`
`
`VARCHAR(30)
`
`PHONE
`
`VARCHAR(15)
`
`CREDIT CARD VARCHAR(I5)
`
`
`CREDIT CARD# SHORT
`
`DEVICE TYPE
`
`
`VARCHAR(20)
`RULE ID
`SHORT
`
`LONG
`FK1,FK3 USERINDEX
`
`
`PHONE MAP
`
`
`
`DEVICE MODEL
`VARCHAR(20)
`
`
`DEVICE ID
`
`EM
`VARCHAR(20)
`
`PHONE #
`
`VARC HAR(1 5)
`
`
`DEVICE NAME
`SERVICE PROVIDER VARCHAR(25)
`VARCHAR(20)
`
`
`
`
`EMAILADDRESS
`VARCHAR(40)
`
`
`
`VARCHARmzm
`
`DEVICEINDEX
`SERVICE PROVIDER
`LOG TIME
`MESSAGE SIZE
`WEB LINK
`
`LONG
`
`VARCHARas)
`DATEnME
`SHORT
`
`VARCHAR(20)
`DEVICE TYPE
`BINARY(1)
`TEXT
`
`
`
`
`BINARY(1)
`GRAPHICS
`
`
`
`BINARY(1)
`WAP
`
`
`BINARY(1)
`IMODE
`
`MAXLENGTH
`SHORT
`
`
`
`
`
`TWO-WAY
`BINARY(1)
` 90
`
`10
`
`10
`
`

`

`Patent Application Publication
`
`Jun. 5, 2003 Sheet 10 0f 10
`
`US 2003/0104827 A1
`
` TO & FROM
`
`LOCALNVIDE AREA
`
`NETWORK (OPTIONAL)
`
`\
`
`210
`
`11
`
`11
`
`

`

`US 2003/0104827 A1
`
`Jun. 5, 2003
`
`REROUTING/REFORMATING WIRELESS
`MESSAGES FOR CROSS CONNECTIVITY
`BETWEEN SERVICE PROVIDERS
`
`BACKGROUND OF THE INVENTION
`
`[0001]
`
`1. Field of the Invention
`
`[0002] The present invention generally concerns wireless
`messaging services, and in more particular concerns a
`method and system for rerouting and reformatting messages
`so that users can send messages to other users that use
`different wireless service providers.
`
`[0003]
`
`2. Background Information
`
`[0004] Under the present wireless bandwidth allocation
`scheme in the United States,
`there are several wireless
`service providers for each metropolitan market, and gener-
`ally at least two service providers for rural markets. Unlike
`other areas of the world, such as Europe, the various service
`providers for a given US. market generally do not provide
`text messaging cross-compatibility with other service pro-
`viders in that market. This problem is illustrated in FIG. 1,
`wherein a plurality of users having different service provid-
`ers are depicted. These users include AT&T Wireless users
`1 and 2, Verizon Wireless users 1 & 2, Voicestream users 1
`& 2, and Sprint PCS users 1 and 2.
`
`[0005] Text messages are commonly sent using the short
`messaging service (SMS) protocol. In many instances, the
`user of a particular wireless service provider will only be
`able to send text messages to other users who use the same
`provider. For example, AT&T user 1 can send a text message
`as an SMS message to AT&T user 2 via wireless commu—
`nication paths 10 and 12. Path 10 comprises the route from
`a cellular phone 14 that uses AT&T wireless for its service
`provider to an AT&T wireless short messaging service
`center (SMSC) 16 via a cellular antenna 18. Path 12 com-
`prises the route from AT&T wireless SMSC 16 via cellular
`antenna 18 to a cellular phone 20 that also uses AT&T
`wireless as its service provider. As will be recognized by
`those skilled in the art, the actual connection path from a
`cellular phone to another cellular phone and/or an SMCS
`may comprise several cellular antennas; however, for sim-
`plicity, each of the connection paths described herein com-
`prise only a few cellular antennas at most.
`
`In addition to paths l0 and 12, there are other paths
`[0006]
`illustrated in FIG. 1 that successfully link users operating
`phones having a common service provider, including paths
`22 and 24, which enables Verizon user 1 to send an SMS
`message from a cellular phone 26 via cellular antenna 18, a
`Verizon SMSC 28, and a cellular antenna 30 to a cellular
`phone 32 operated by Verizon user 2. Similarly, paths 32 and
`34 enable SMS messaging between cellular phones 36 and
`38 respectively operated by Voicestream users 1 and 2 via
`cellular antennas 18 and 30 and a Voicestream SMSC 40,
`while paths 42 and 44 enable SMS messaging between PCS
`phones 46 and 48 via cellular antennas 18 and 30 and a
`Sprint PCS SMSC 50.
`
`[0007] Although there are instances in which service pro-
`viders provide some cross-compatibility for SMS messag-
`ing, there are many markets in which the user audience for
`SMS messaging is greatly restricted to only those users who
`have the same service provider. For example, AT&T wire-
`less user 1 may not be able to send SMS messages to any
`
`Verizon user, any Voicestream user, or an Sprint PCS user,
`as provided by failure paths 52, each of which is depicted as
`a dashed line with an “X” in FIG. 1. Similar failure paths 52
`are shown in the Figure to illustrate the lack of cross-
`compatibility for SMS messaging when the sending phone
`and the receiving phone use diiferent service providers.
`
`It is clear that the present scheme is inadequate for
`[0008]
`many users. It would therefore be desirable to provide a
`scheme that would provide a much higher degree of cross-
`compatibility for SMS messaging between users having
`different service providers. Furthermore, it would be pref-
`erable that the scheme may be implemented without requir-
`ing changes to the existing wireless services infrastructure.
`
`SUMMARY OF THE INVENTION
`
`invention addresses the foregoing
`[0009] The present
`cross—connectivity problem by providing a method and
`system that enables wireless device users to send messages
`from their devices to other destination wireless devices that
`use a different service provider than the sending device.
`Typical sending and destination devices include cellular
`phones, pagers, wireless PDA’s, Pocket PCs, and wireless
`laptops. In addition, the invention enables messages to be
`sent from wireless devices to e-mail addresses. Generally,
`the method and system are enabled through use of a third
`party rerouting/reformatting service that appears transparent
`to the wireless device users and service providers, although
`such functionality may also be provided directly by one or
`more wireless service providers.
`
`In one embodiment, the method includes convert-
`[0010]
`ing an original SMS message into an e—mail message and
`routing the e-mail message to the message rerouting service,
`whereupon the e-mail message is reformatted into a desti-
`nation message (as necessary) that is dispatched for delivery
`to a destination device selected by a user who generated the
`original SMS message. The method begins by enabling the
`user to generate an original short messaging service (SMS)
`message on a sending wireless device and request
`the
`message be sent to a selected destination wireless device. In
`response to an activation cue, such as the user depressing a
`“SEND” key, an e-mail message comprising content corre-
`sponding to the original SMS wireless message and includ-
`ing indicia identifying the destination wireless device is
`automatically generated and sent to the message rerouting
`service. Upon reaching the message rerouting service, the
`e-mail message is parsed to determine a wireless access
`point for the destination wireless device, which will typi—
`cally comprise a phone number if the destination device is
`a cellular phone or pager, or may comprise an IP address.
`The wireless access point may be embedded in the body or
`address of the e-mail message, or such information may be
`retrieved from a database operated by the message rerouting
`service using search criteria based in part on indicia con-
`tained in the e-niail message or address. Based on the
`wireless access point, one or more service providers that
`provide infrastructure for routing messages to the wireless
`access point are determined, and a destination message is
`generated from the content of the e-mail message. The
`destination message is then dispatched from the message
`rerouting service to be delivered to the destination wireless
`device via message routing infrastructure provided by the
`previously-identified service providers. In general, the des-
`tination message will be formatted based on the particular
`
`12
`
`12
`
`

`

`US 2003/0104827 A1
`
`Jun. 5, 2003
`
`requirements for those service providers that enable the
`delivery of the destination message to the destination device
`For example, if the destination device is a cellular phone or
`pager,
`the e-mail message is reformatted into an SMS
`message. Other types of destination messages include e-mail
`messages and instant messages.
`
`an SMS message is
`In another embodiment,
`[0011]
`rerouted to the message rerouting service, which again
`performs reformatting (as necessary) and message dispatch
`functions to deliver the message to a selected destination
`device. In this embodiment, rerouting indicia is appended to
`an original SMS message generated by a user with the
`sending device, causing the original SMS message to be sent
`to the rerouting service via an SMSC operated by a service
`provider for the sending wireless device rather than attempt-
`ing to directly send the message to the destination device.
`Upon reaching the rerouting service, various routing indicia
`are extracted from the SMS message, and a destination
`message is generated and dispatched for delivery to the
`dcstination device in a manncr similar to that dcscribcd
`above.
`
`In accord with other aspects of the invention,
`[0012]
`methods are provided to enable wireless device users to send
`text messages to e—mail address using the message rerouting
`service.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0013] The foregoing aspects and many of the attendant
`advantages of this invention will become more readily
`appreciated as the same becomes better understood by
`reference to the following detailed description, when taken
`in conjunction with the accompanying drawings, wherein:
`
`[0014] FIG. 1 is a schematic diagram illustrating the lack
`of cross connectivity between service providers under the
`present wireless message delivery infrastructure;
`
`[0015] FIG. 2A is a schematic diagram illustrating a
`system infrastructure for implementing a first method for
`rerouting a wireless message in accord with the present
`invention;
`
`[0016] FIG. 2B is a schematic diagram illustrating a
`system infrastructure for implementing a second method for
`rerouting a wireless message in accord with the present
`invcntion;
`
`[0017] FIG. 3A is a schematic diagram illustrating further
`details of the system infrastructure of FIG. 2A;
`
`[0018] FIG. 3B is a schematic diagram illustrating further
`details of the system infrastructure of FIG. 2B;
`
`[0019] FIG. 4A is a flowchart for illustrating the logic
`used by the present invention in performing the first method
`for rerouting a wireless message;
`
`[0020] FIG. 4B is a flowchart for illustrating the logic
`used by the present invention in performing the first method
`for rerouting a wireless message;
`
`[0021] FIG. 5 is a representation of an exemplary user
`interface for implementing a sign-up process with the mes-
`sage rerouting/reformatting service of the invention;
`
`[0022] FIG. 6 is an entity relationship diagram corre-
`sponding to an exemplary database schema for implement-
`ing the database aspects of the invention; and
`
`[0023] FIG. 7 is a schematic drawing of a computer
`system that may be implemented for various components in
`the system of the present invention.
`DETAILED DESCRIPTION
`
`[0024] The present invention provides a method and sys-
`tem that enables wireless device users to send messages
`from their devices to other wireless devices that use a
`
`different service provider than the sending device. In the
`following description, numerous specific details are pro-
`vided, to provide a thorough understanding of embodiments
`of the invention. One skilled in the relevant art will recog-
`nize, however, that the invention can be practiced without
`one or more of the specific details, or with other methods,
`components, etc. In other instances, well-known structures
`or operations are not shown or described in detail to avoid
`obscuring aspccts of various cmbodimcnts of thc invcntion.
`
`this specification to “onc
`[0025] Rcfcrcncc throughout
`embodiment” or “an embodiment” means that a particular
`feature, structure, or characteristic described in connection
`with the embodiment is included in at least one embodiment
`
`the appearances of the
`invention. Thus,
`of the present
`phrases “in one embodiment” or “in an embodiment” in
`various places throughout this specification are not neces—
`sarily all referring to the same embodiment. Furthermore,
`the particular features, structures, or characteristics may be
`combined in any suitable manner in one or more embodi-
`ments.
`
`[0026] An exemplary system 60 for implementing a first
`method for rerouting messages in accord with the present
`invention is shown in FIGS. 2A and 3A. As will be
`
`recognized by those skilled in the art, FIG. 2A depicts
`various conventional wireless infrastructure components,
`including all of the infrastructure components illustrated in
`FIG. 1 and discussed above, wherein like-numbered com-
`ponents perform substantially the same functions in both
`infrastructures. The infrastructure of FIG. 2A further
`
`includes a plurality of SMTP (simple mail transport proto—
`col) gateways corresponding to various service providers,
`including an AT&T Wireless SMTP gateway 62, a Verizon
`SMTP gateway 64, a Voicestream SMTP gateway 66, and a
`Sprint PCS gateway 68. It is noted that SMTP gateways 62,
`64, 66, and 68 are depicted twice in each of FIGS. 2A and
`3A to enable the routing of messages to be depicted more
`clearly. It will be understood, that these SMPT gateways
`may represent the same or separate facilities, depending on
`the locations of the sending and receiving wireless devices.
`In addition to the foregoing conventional wireless infrastruc-
`ture components, the system further includes a third party
`message rerouting/reformatting service 70 that provides
`various services for facilitating text message cross-compat-
`ibility between the various service providers.
`
`[0027] The primary components used by rerouting/refor-
`matting service 70 are depicted in FIG. 3A. Rerouting/
`reformatting service 70 is connected to SMTP gateways 62,
`64, 66, and 68 via a network 72. In general, the connection
`to network 72 will be a land-based connection, although it
`may be a wireless connection as well. Rerouting/reformat-
`ting service 70 is also linked in communication with SMSCs
`16, 28, 40, and 50 via either a land-based link or a wireless
`link.
`
`[0028] Rerouting/reformatting service 70 receives incom-
`ing e-mail messages 75 forwarded by SMTP gateways 62,
`
`13
`
`13
`
`

`

`US 2003/0104827 A1
`
`Jun. 5, 2003
`
`64, 66, and 68 at a POP3 (Post Office Protocol) server 76.
`Preferably, communication with POP3 server 76 will be
`enabled through one or more URLs that are used as access
`points to rerouting/reformatting service 70. POP3 server 76
`is connected in communication with an application server
`78, which in turn is connected in communication with a
`database server 80. As will be understood by those skilled in
`the art, each of POP3 server 76, application server 78, and
`database server 80 may run on one or more separate
`machines in a distributed multi-tier environment, or may be
`run on two machines, or even a single machine. For instance,
`it is common to use a single machine to perform e-mail
`server and application server functions.
`
`[0029] Preferably, database server 80 will comprise a
`relational database management system (RDBMS) database
`server, such as the SQL (structured query language) database
`servers provided by Oracle
`(Oracle
`8i), Microsoft
`(SQLserver), Informix, IBM (DB2), or Sybase. Database
`server 80 operates on data stored in a database 82 having an
`exemplary schema that includes a provider rules table 81, a
`user rules table 84, a rules definition table 85, user table 86,
`a devices table 88, a devices capability table 90, a phone
`number—to—service provider mapping (phone map) table 92,
`and a transaction table 94
`
`[0030] Application server 78 includes one or more soft-
`ware modules comprising a data extractor and message
`reformattor 96 that generates destination messages 98 based
`on corresponding e-mail messages 75 and data stored in
`database 82. Messages 98 are reformatted to meet
`the
`particular requirements of the service provider for a selected
`destination device, capabilities of the destination device, and
`any applicable rules corresponding to the initial sender user
`and/or the service provider. Messages 98 are then sent to a
`selected destination device via one or more service provider
`facilities depending on the capabilities of the destination
`device and other information stored in database 82, further
`details of which are discussed below.
`
`[0031] A flowchart corresponding to a method for rerout-
`ing messages that is enabled by the system infrastructure of
`FIGS. 2A and 3A is shown in FIG. 4A. The method begins
`in a block 100, wherein a user operating a sending wireless
`device 83 enters a text message and selects a unique iden-
`tifier corresponding to a destination device the user desires
`the message to be delivered to. The unique identifier may
`comprise a telephone number for the destination device, if
`the device is a wireless phone or pager, or may comprise
`some other unique identifier corresponding to other desti-
`nation devices previously registered by the user with rerout-
`ing/reformatting service 70, further details of which are
`discussed below.
`
`in a block 102, a Internet domain name
`[0032] Next,
`corresponding to one or more Internet domains registered by
`rerouting’reformatting service 70 is appended to the unique
`identifier so as to form an e-mail delivery address. For
`example, suppose the unique identifier is 425.555.1212 and
`the domain name is “ondevice.com.” The resulting e-mail
`address will then be “425.5551212@ondevice.com.”
`
`[0033] There are several ways in which the domain name
`may be appended to the unique identifier. Preferably, this
`will be performed at the user device, wherein the device,
`such as a cellular phone, will be programmed to append the
`domain name in response to a menu option or key sequence
`
`entered by the user. Adding a feature of this type to a cellular
`phone may be accomplished by adding circuitry to an
`existing cellular phone, including the functionality in a new
`cellular phone, providing the functionality via a downloaded
`upgrade, or through other means that will be known to those
`skilled in the wireless device arts.
`
`[0034] The text message is then sent as an e—mail message
`75 to an SMTP gateway corresponding to the service pro-
`vider of the user’s device in a block 104. In general, each
`service provider will operate one or more SMTP gateways,
`or may share a SMTP gateway with one or more other
`providers. For simplicity,
`the configuration depicted in
`FIGS. 2A and 3A show a single SMTP gateway for each
`wireless service provider.
`
`In a block 106 the e-mail message is routed from
`[0035]
`the SMTP gateway via network 72 to POP3 server 76 at
`rerouting/reformatting service 70 based on the URL for the
`e-mail message. In addition, the message may traverse one
`or more other SMPT servers (not shown) along its route to
`POP3 server 76. Once received by web server 76, the text
`content, a sending device identifier (ID), and destination
`device identifier (ID) are extracted in a block 108. Typically,
`if the sending device is a cellular or PCS phone, the sending
`device ID will comprise the phone number for the device.
`This phone number may be identified using an automatic
`number identification (ANI) system, or it may be automati-
`cally appended to the message text via functionality built in
`to the sending device and extracted by data extractor and
`message reformatter 96. Similarly, the destination device ID
`may comprise the portion of the URL prior to the “@domain
`name” (hereinafter referred to as the prefix), such as might
`be the case if the destination device was a wireless phone or
`pager
`
`In some instances, the user may desire to send the
`[0036]
`text message to a PDA device (e.g., palm pilot), a handheld
`computer, or a PC e-mail account rather than a wireless
`phone or pager. In these instances, the user will generally
`have registered one or more of these types of devices with
`rerouting/reformatting service 70, and device IDs for those
`devices will be stored in database 82. Accordingly,
`the
`selected device may be determined based on indicia in the
`prefix of the e-mail address in optional combination with the
`sending device phone number or other indicia contained in
`e—mail message 75 or the e—mail address.
`
`[0037] Once the sending and destination device IDs have
`been extracted,
`the user ID and capability information
`corresponding to the destination device are retrieved from
`database 82 in a block 110 based on identification of the
`
`sending device and the destination device ID. In addition, a
`wireless access point for the destination device is retrieved.
`The wireless access point is an end point that messages need
`to reach or be directed to so that the destination device can
`access those messages. The wireless access point for a
`cellular phone or page will typically comprise the phone
`number for those devices. The wireless access points for
`wireless PDA’s, pocket PCs and laptops will
`typically
`comprise an IP address or a URI. for a wireless Internet
`service provider for those devices.
`
`[0038] The service provider(s) for enabling a destination
`message to reach the destination device is/are then identified
`in a block 112 based on the wireless access point and/or the
`destination device capabilities determined above. For
`
`14
`
`14
`
`

`

`US 2003/0104827 A1
`
`Jun. 5, 2003
`
`instance, if the destination device is a cellular phone or
`pager, data contained in phone map table 92 and/or one or
`more remote database tables that contain phone number-to-
`service provider mapping information may be queried to
`retrieve the service provider for the destination. Based on the
`service provider(s), the capabilities of the destination device,
`and any preferences entered by the user, data extractor and
`message reformatter 96 will reformat e-mail message 75 in
`a block 114 to produce a destination message 98. In more
`detail, destination message 98 will be reformatted, as nec-
`essary, based on the capabilities of the destination device
`stored in the device capabilities table 90, preferences entered
`by the user stored in rule definitions table 85, user table 86,
`and/or device capabilities table 90, and rules for the service
`provider that preferably are stored in provider rules table 83
`and/or rule definition table 85 rules table 84. Generally,
`destination message 98 will comprise an SMS message, an
`e-mail message, or an instant message.
`
`[0039] Depending on the type of destination device and/or
`applicable rules, destination message 98 will generally be
`forwarded to an appropriate service provider facility and/or
`other service facility in a block 116, via either a land-based
`network 72 or a wireless network link. For instance, if the
`message is to be received as a text message by a wireless
`destination device such as a wireless phone 15 or a pager 87
`and the service provider is AT&T wireless, the message will
`be formatted to correspond with any applicable protocol
`required by the SMS messaging services provided by AT&T
`wireless, and forwarded to AT&T wireless SMSC 16, along
`with the phone number for the destination device, where-
`upon AT&T wireless SMSC 16 will send the message to the
`destination device via a wireless antenna 74.
`
`If the message is to be sent to a PDA 89, a pocket
`[0040]
`PC (not shown), or a wireless-enabled laptop 91, destination
`message 98 will generally be delivered to an appropriate
`SMTP gateway for the destination device’s carrier. If the
`destination device supports instant messaging chat session,
`destination message 98 may be routed through an instant
`messaging service center 67. In other instances, the message
`may be first routed through a service provider SMPT, and
`then routed through a service provider SMSC. In addition, if
`the destination device is a WAP (wireless access protocol)-
`enabled device,
`the destination message may be routed
`through a WAP gateway 97.
`
`In some instances, the user will desire to send the
`[0041]
`message to a general e-mail address that may be access by
`both wireless and land-based devices, such as a land-line
`computer 93. Accordingly, destination message 98 will be
`sent to a land-line SMPT 69 and a POP3 server 71 corre-
`sponding to the domain that services the e-mail address. For
`example, if the e-mail address is serviced by Earthlink,
`destination message 98 is sent to an SMPT operated by
`Earthlink (or operated by another for the purposes of sup-
`porting Earthlink e-mail accounts, and passed to