as) United States
`a2) Patent Application Publication co) Pub. No.: US 2011/0082772 Al
`
` HIRSON (43) Pub. Date: Apr. 7, 2011
`
`
`US 20110082772A1
`
`(54) SYSTEMS AND METHODS FOR PURCHASES
`ON A MOBILE COMMUNICATION DEVICE
`
`(52) US. CM wee 705/27.1; 455/466; 715/760
`
`Inventor:
`(75)
`(73) Assignee:
`(21) Appl. No.:
`
`(8)HIRSON,San Francisco, CA
`(us) INC., San Francisco, CA
`12/617,435
`
`(22)
`
`Filed:
`
`Nov.12, 2009
`Related U.S. Application Data
`
`(60) Provisional application No. 61/247,876, filed on Oct.
`1, 2009.
`
`oo.
`.
`.
`Publication Classification
`
`ABSTRACT
`(57)
`Systems and methodsare provided tofacilitate online trans-
`actions via mobile communications. In one aspect, a system
`includes a plurality of converters to interface with a plurality
`of controllers in different formats for delivery of premium
`messages; and a common format processor coupled with the
`plurality of converters in a common format to send the pre-
`mium messages. In one embodiment, the common format
`processoris to receive a web request from a mobile phone, in
`response to a user selection within a mobile application
`executed separately from a browserapplication on the mobile
`phone, to providea web page in response to confirm a pre-
`defined purchase, to transmitat least one premium message to
`Int. Cl.
`(51)
`
`G06C 30/00 the mobile phoneusingafirst converter to obtain funds for the(2006.01)
`
`HO4W V2
`(2009.01)
`pre-defined purchase, and to communicate with the merchant
`GO6F 3/01
`(2006.01)
`to make the pre-defined purchase on behalf ofthe user.
`
`[] providing a loan/credit
`
`www.mobillcash.com
`
`File Edit View Help
`
`Please deposit
`
`$] 10.00
`
`181
`
`into my account @ mobile phone
`
`|1-456-123-7890
`
`by:
`
`charging my mobile phone
`
`185
`
`SAMSUNG 1009
`
`SAMSUNG 1009
`
`1
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 1 of 21
`
`US 2011/0082772 Al
`
`Aecount
`
`__
`
`User
`
`Terminal 114
`
`nee
`
`User
`
`Terminal 114
`
`Server
`413
`
` Data
`
`Telecommunications
`Network
`
`10s
`
`Server
`113
`
`e °
`
`Controller |. , ,|Controller
`
`415
`415
`
`Controller
`115
`
`Interchange
`104
`
`
`
`Wireless
`
`
`Telecommunications
`
`Network
`105
`
`
`Mobile
`Phone 117
`
`cee
`
`Mobile
`Phone 117
`
`FIG. 1
`
`Number 123
`
`Account
`4121
`
`Phone
`
`Data Storage
`Facility 107
`
`Schedule
`125
`
`2
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 2 of 21
`
`US 2011/0082772 Al
`
`Interchange 101
`
`Unified Data
`Interface 135
`
`115
`
`Common Format
`Processor 133
`
`Converter
`131
`
`Converter
`1341
`
`Converter
`134
`
`Controller
`115
`
`Controller
`115
`
`Controller
`
`3
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 3 of 21
`
`US 2011/0082772 Al
`
`142
`
`Billing
`Engine 157
`
`Decision
`Engine 154
`
`Mobile
`Message
`Generator
`153
`
`Regulations
`143
`
`Records 147
`
`Restrictions
`
`FIG. 3
`
`Common Format Processor 13
`
`Purchase
`Request
`
`177
`
`User
`
`Deposit|171
`Server
`Request
`Data Storage
`113
`Facility 107
`
`;yu Terminal 111
`
`
`onerse
`Sques
`
`179
`
`Confirmation
`
`173
`
`Interchange
`401
`
`Phone
`Number 123
`
`Account
`
`124
`
`
`175
`
`Mobile
`Phone 117
`
`Send Premium
`Messages
`
`FIG A
`
`4
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 4 of 21
`
`US 2011/0082772 A1
`
`www.mobillcash.com
`
`File Edit View Help
`
`Please deposit
`
`$] 10.00
`
`181
`
`183
`
`into my account @ mobile phone
`
`|1-456-123-7890
`
`by:
`
`ial
`
`185
`
`charging my mobile phone
`
`FIG. 5
`
`To confirm depositing $10.00
`into your account by
`charging on your phone bill,
`
`[-] providing a loan/credit
`please reply with “1",
`
`5
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 5 of 21
`
`US 2011/0082772 Al
`
`www.songs.com
`
`File Edit View Help
`
`[_] Credit Card
`
`Payment: $1.007~
`
`dal Mobile Account
`
`205
`
`www.mobillcash.com
`
`File Edit View Help
`
`
`
`
`
`www.songs.com requests a paymentof: $1.00+>208
`
`
`
`Please pay from my account @ mobile phone
`
`|1-456-123-7890
`
`183
`
`215
`
`
`
`FIG. 8
`
`6
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 6 of 21
`
`US 2011/0082772 Al
`
`FIG. ¢
`
`To confirm a payment of
`$1.00 to www.songs.com
`
`please reply with “1". Your paymentof $1.00 to
`www.songs.com is complete.
`
`7
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 7 of 21
`
`US 2011/0082772 Al
`
`Receive a request to deposit an amountinto an
`account associated with a mobile phone 301
`
`Transmit a message to the mobile phoneto
`confirm the request 303
`
`Receive a confirmation from the mobile phone
`for the request 305
`
`Calculate a numberof premium messagesto
`charge the mobile phone for the amount 307
`
`Transmit the numberof premium messagesto
`the mobile phone 309
`
`Receive a portion of the amount from the carrier
`of the mobile phone 311
`
`Credit the account associated with the mobile
`phone with the full amount 313
`
`FIG. 11
`
`8
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 8 of 21
`
`US 2011/0082772 Al
`
`Receive a request to pay an amount to a payee
`from an account associated with a mobile phone
`
`334
`
`Transmit a messageto the mobile phoneto
`confirm the request 333
`
`Receive a confirmation from the mobile phone
`for the request 335
`
`Charge the account a first fee for paying the
`amount 337
`
`Deduct a second fee from the amountin paying
`the payee 339
`
`Optionally charge the account a periodic fee to
`maintain the account 341
`
`FIG. 12
`
`9
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 9 of 21
`
`US 2011/0082772 Al
`
`www.mobillcash.com
`
`File Edit View Help
`
`www.games.com requests a paymentof: $10.002~293
`
`Please pay from my account @ mobile phone
`
`|1-456-123-7890
`
`;
`Options
`
`183
`
`208
`
`09
`Makethis paymentonly
`
`lm] Repeatthis payment|Monthly iV
`
`206
`
`207
`
`
`
`A] Collect funds for similar payments|Monthly V7]
`
`10
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 10 of 21
`
`US 2011/0082772 Al
`
`$10.00 to www.games.com
`
`FIG. 14
`
`Reply with:
`“4" to confirm; or
`“2' to schedule it as a
`monthly payment.
`
`www.games.com
`“3" to cancel the schedule.
`
`190
`
`$10.00 monthly to
`
`Reply with:
`“4" to pay for this month; or
`“2" to skip once; or
`
`11
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 11 of 21
`
`US 2011/0082772 Al
`
`Purchase
`
`Request
`
`277
`
`User
`Terminal 111
`
`
`Data Storage
`Facility 407
`
`Confirmation|271
`& Schedule
`Account
`121
`
`113
`
`
`
`279
`
`
`
`
`375
`
`Send Premium
`Messages
`
`
`
`FIG 16
`
`Schedule a transaction on a first date for a user
`at a phone number 431
`
`Determine a second date based onthe first date
`and an estimated time period to collect funds via
`a telecommunication carrier 433
`
`Transmit premium messagesto a mobile phone
`at the phone numberon the second date to
`collect funds for the transaction 435
`
`Confirmation
`
`Mobile
`Phone 117
`
`FIG. 17
`
`12
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 12 of 21
`
`US 2011/0082772 Al
`
`Receive a requestfora first transaction between a first
`party having a phone number and a second party 451
`
`Promptthe first party to schedule a second transaction
`based onthe first transaction 453
`
`Communicate with a mobile phone at the phone number to
`confirm the scheduling of the second transaction 455
`
`Estimate a time period between the transmitting of a
`premium message to the mobile phone and the receiving of
`funds collected by a telecommunication carrier of the
`
`mobile phone according to the premium message 457
`
`Determine a date to transmit premium messagesto the
`mobile phone based onthe estimated time period 459
`
`
`
`Transmit on the date one or more premium messagesto
`the mobile phonetocollect funds for the second
`transaction 461
`
`Perform the second transaction according to the schedule
`463
`
`FIG. 18
`
`13
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 13 of 21
`
`US 2011/0082772 A1
`
`www.games.com
`
`File Edit View Help
`
`Application
`211
`
`
`
`Top up your account via
`your phone number ?
`Yes | No
`
`www.games.com
`
`File Edit View Help
`
`14
`
`14
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 14 of 21
`
`US 2011/0082772 Al
`
`FIG. 21
`
`217
`
`190
`
`
`
`
`
`
`To top up your accountwith
`www.games.com, reply with:
`
`
`
` “4" to confirm; or
`
`“2' to also authorize future
`requests.
`
`
`
` Cancel
`OS EZ DOO
`
`
`LRQQ0DGQQQL
`
`OO
`CO
`OBRRQQQOQKP5
`
`
`O
`O
`O SESSOwe
`
`
`
`FIG. 22
`
`Your www.games.com points
`are running low. To top up,
`reply with:
`
`“4" to confirm; or
`“2" to top up when| need; or
`“3" to set up auto top up.
`1
`
`15
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 15 of 21
`
`US 2011/0082772 Al
`
`190
`
`To pay $0.75 to
`www.songs.com, reply with:
`
`www.games.com
`
`"4" to confirm and apply
`balance to your account with
`
`16
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 16 of 21
`
`US 2011/0082772 Al
`
`Purchase
`Request
`
`2
`
`EIEN
`
`Server
`i13a
`
`User
`Access
`|Terminal 111 ooo,
`
`27
`
`Confirmation
`
`Account
`124
`
`Charge
`Request
`
`279
`
`Interchange
`104
`101
`
`Data Storage
`Facility 107
`
`ConfirmationoP 273
`
`275
`
`Account
`Information 122
`
`{
`
`Authorization
`Phone
`
`Send
`Premium
`Messages
`
`126
`
`Number 123
`
`Mobile
`Phone 117
`
`FIG. 24
`
`FIG. 25
`
`Determine that the amount in an account of a user
`with a server is lower than a threshold 471
`
`Interact with the user to authorize topping up the
`account, without leaving the experience/
`environment currently provided by the server 473
`
`to collect funds to top up the account 475
`
`Transmit premium messages from an interchange
`to a mobile phone at the phone numberofthe user
`
`17
`
`17
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 17 of 21
`
`US 2011/0082772 Al
`
`Receive a requestto fund an accountusing funds
`associated with a phone number 481
`
`Communicate with a mobile phone at the phone
`number to confirm the request 483
`
`Obtain an authorization to skip mobile phone
`confirmation for subsequent requests to fund the
`
`accountvia the phone number485
`
`Add funds associated with the phone number to the
`account 487
`
`Determine the account needs additional funds 489
`
`While the user is in experience with the server,
`promptthe user to fund the account 491
`
`Add funds associated with the phone number to the
`account without mobile phone confirmation 493
`
`FIG. 26
`
`18
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 18 of 21
`
`US 2011/0082772 Al
`
`Top up your accountvia
`your phone number ?
`Yes | No
`
`Application 505
`
`Points Left
`
`513
`
`511
`
`19
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 19 of 21
`
`US 2011/0082772 Al
`
`FIG. 29 Yes, top up your account
`
`with GameX.
`
`20
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 20 of 21
`
`US 2011/0082772 Al
`
`Access
`
`oe
`:
`
`Premium
`Messages
`
`545
`
`
`
`
`
`
`Account
`124
`
`413b
`
`Purchase
`
`Facility 107
`
`vor
`
`547.4,
`
`5A
`
`Confirmation
`
`
`Interchange
`104
`
`
` Data Storage
`
`Information 122}|Number 123
`FIG. 31
`=
`—
`
`Receive a web requestin responseto a user selection in a
`mobile application executed separately from a browser
`application on the mobile phone 551
`
`Provide a web page to the browserapplication to confirm a
`pre-defined purchase 553
`
`purchase on behalf of the user 557
`
`Transmit at least one premium message to the mobile
`phone to obtain funds for the pre-defined purchase 555
`
`Communicate with the merchant to make the pre-defined
`
`FIG. 32
`
`21
`
`21
`
`

`

`Patent Application Publication
`
`Apr. 7, 2011 Sheet 21 of 21
`
`US 2011/0082772 Al
`
`Cache 404
`
`such as hard drive, flash 403
`
`Memory (e.g., ROM, Volatile
`RAM, Nonvolatile Memory,
`
`Microprocessor(s)
`
`memory) 408
`
`
`
`Inter-connect 402
`
`
`Display Controller
`& Display Device
`407
`
`/0
`Controller(s)
`406
`
`405
`
`lO Device(s)
`(e.g. mouse, or keyboard,
`or modem, or network
`interface, or printer, or
`scanner, or video camera)
`
`FIG. 33
`
`22
`
`22
`
`

`

`US 2011/0082772 Al
`
`Apr. 7, 2011
`
`SYSTEMS AND METHODS FOR PURCHASES
`ON A MOBILE COMMUNICATION DEVICE
`
`[0001] The present application claims the benefit of the
`filing date of Provisional U.S. Pat. App. Ser. No. 61/247,876,
`filed Oct. 1, 2009, the disclosure of which is incorporated
`herein by reference.
`
`FIELD OF THE TECHNOLOGY
`
`[0002] At least some embodimentsof the disclosure relate
`to mobile communications in general and, more particularly
`but not limited to, mobile communicationsto facilitate online
`transactions.
`
`BACKGROUND
`
`Short Message Service (SMS) is a communications
`[0003]
`protocol that allows the interchange of short text messages
`between mobile telephone devices. SMS messagesare typi-
`cally sent via a Short Message Service Center (SMSC)of a
`mobile carrier, which uses a store-and-forward mechanism to
`deliver the messages. When a mobile telephoneis not reach-
`able immediately for the delivery of the message, the SMSC
`stores the message forlaterretry.
`[0004]
`SMS messages can be sent via gateways. Some
`gateways function as aggregators. An aggregator typically
`does not have the capacity the deliver the messagesdirectly to
`the mobile phones. An aggregator typically interfaces with
`and relies upon the SMSC ofa mobile carrier to deliver SMS
`messages.
`
`Some gateways function as providers that are
`[0005]
`capable of sending text messages to mobile devicesdirectly,
`without going through the SMSCof other mobile operators.
`[0006] Text messaging between mobile telephonescan also
`be performed using other protocols, such as SkyMail and
`Short Mail in Japan.
`[0007]
`Some mobile carriers provide email gateway ser-
`vices to allow text messages to be sent to mobile phones via
`email. For example, a non-subscriber of the mobile carrier
`may send a message to an email address associated with a
`mobile phoneof a subscriber of the mobile carrier to have the
`message delivered to the mobile phone via text messaging.
`[0008] Emails can also be sent to mobile telephone devices
`via standard mail protocols, such as Simple Mail Transfer
`Protocol (SMTP) over Internet Protocol Suite (commonly
`TCP/IP, named from twoofthe protocols: the Transmission
`Control Protocol (TCP) and the Internet Protocol (IP)).
`[0009]
`Short messages may be used to provide premium
`services to mobile phones, such as newsalerts, ring tones, etc.
`The premium content providers may send the messagesto the
`SMSCof the mobile operator using a TCP/IP protocol, such
`as Short Message Peer-to-peer Protocol (SMPP) or Hypertext
`Transfer Protocol, for delivery to a mobile phone; and the
`mobile phoneis billed by the mobile operator for the cost of
`receiving the premium content.
`[0010]
`Premium services may also be delivered via text
`messages initiated from the mobile phone. For example, a
`televoting service provider may obtain a short code to receive
`text messages from mobile phones; and whenthe user sends
`a text message to the short code, the mobile carrier routes the
`
`message to the televoting service provider and charges the
`user a fee, a portion of which is collected for the televoting
`service provider.
`
`SUMMARY OF THE DESCRIPTION
`
`Systems and methods are provided to facilitate
`[0011]
`online transactions via mobile communications. Some
`embodiments are summarized in this section.
`[0012]
`In one aspect, a system includesa plurality of con-
`verters to interface with a plurality of controllers in different
`formats for delivery of premium messages; and a common
`format processor coupled withthe plurality of converters in a
`common format to send the premium messages. In one
`embodiment, the common format processor is to receive a
`web request from a mobile phone, in response to a user
`selection within a mobile application executed separately
`from a browser application on the mobile phone,to provide a
`web page in response to confirm a pre-defined purchase, to
`transmit at least one premium message to the mobile phone
`using a first converter to obtain funds for the pre-defined
`purchase, and to communicate with the merchant to make the
`pre-defined purchase on behalf of the user.
`[0013]
`In another aspect, a computer-implemented method
`includes: receiving in a computing device a web request from
`a mobile phoneofa user, in responseto the user selecting a
`user interface element within a mobile application executed
`separately from a browser application on the mobile phone,
`the user interface element being pre-associated with a mer-
`chant for a pre-defined purchase; in response to the web
`request, providing by the computing device a web page to the
`mobile phone to confirm the pre-defined purchase in the
`browserapplication executed on the mobile phoneofthe user;
`in response to the user confirming the pre-defined purchase
`via the web page presented in the browser application
`executed on the mobile phone,transmitting by the computing
`device at least one premium messageto the mobile phoneto
`obtain funds, accordingto at least one predeterminedprice of
`the at least one premium message, via a telecommunication
`carrier of the mobile phone; and communicating by the com-
`puting device with the merchant to make the pre-defined
`purchase using the funds on behalf of the user.
`[0014] The disclosure includes methods and apparatuses
`which perform these methods, including data processing sys-
`tems which perform these methods, and computer readable
`media containing instructions which when executed on data
`processing systems cause the systems to perform these meth-
`ods.
`
`[0015] Other features will be apparent from the accompa-
`nying drawings and from the detailed description whichfol-
`lows.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0016] The embodimentsareillustrated by way of example
`and not limitation in the figures of the accompanying draw-
`ings in which like references indicate similar elements.
`[0017]
`FIG. 1 shows a system to facilitate online transac-
`tions according to one embodiment.
`[0018]
`FIG. 2 shows an interchange to route messages
`according to one embodiment.
`[0019]
`FIG. 3 shows a messageprocessor according to one
`embodiment.
`
`FIG. 4 shows a methodto facilitate an online trans-
`[0020]
`action using an interchange according to one embodiment.
`
`23
`
`23
`
`

`

`US 2011/0082772 Al
`
`Apr. 7, 2011
`
`description. References to one or an embodiment in the
`FIG.5 illustrates a user interfaceto initiate a deposit
`[0021]
`transaction according to one embodiment.
`present disclosure are not necessarily references to the same
`[0022]
`FIG. 6 illustrates a user interface to confirm a
`embodiment; and, such references meanatleast one.
`deposit transaction according to one embodiment.
`[0048] Referencein this specification to “one embodiment”
`[0023]
`FIG.7 illustrates a user interface to initiate a pay-
`or “an embodiment” meansthata particular feature, structure,
`menttransaction according to one embodiment.
`or characteristic described in connection with the embodi-
`
`[0024] FIG.8illustrates a user interface to initiate a pay-
`mentis includedin at least one embodimentofthe disclosure.
`ment request according to one embodiment.
`The appearancesof the phrase “in one embodiment”in vari-
`[0025]
`FIG.9 illustrates a user interface to confirm a pay-
`ous placesin the specification are not necessarily all referring
`ment request according to one embodiment.
`to the same embodiment, nor are separate or alternative
`[0026]
`FIG. 10 illustrates a user interface to confirm the
`embodiments mutually exclusive of other embodiments.
`completion of a payment
`transaction according to one
`Moreover, various features are described which may be
`embodiment.
`exhibited by some embodiments andnotby others. Similarly,
`various requirements are described which may be require-
`ments for some embodiments but not other embodiments.
`
`[0027] FIG.11 shows a methodto facilitate a deposit trans-
`action according to one embodiment.
`[0028]
`FIG. 12 shows a methodto facilitate a payment
`transaction according to one embodiment.
`[0029]
`FIG. 13 showsa userinterface to schedule a future
`transaction during the web confirmation of a current transac-
`tion according to one embodiment.
`[0030]
`FIG. 14 showsa userinterface to schedule a future
`transaction during the mobile phone confirmation ofa current
`transaction according to one embodiment.
`[0031]
`FIG. 15 showsa userinterface to confirm a recurring
`transaction according to one embodiment.
`[0032]
`FIG. 16 showsa system to collect funds for sched-
`uled transactions according to one embodiment.
`[0033]
`FIG. 17 shows a methodto collect funds for sched-
`uled transactions according to one embodiment.
`[0034] FIG.18 shows a methodto perform scheduledtrans-
`actions according to one embodiment.
`[0035]
`FIGS. 19-20 illustrate a user interface to add funds
`to an account according to one embodiment.
`[0036]
`FIG. 21 illustrates a user interface on a mobile
`phone to obtain advance authorization to add funds to an
`account according to one embodiment.
`[0037]
`FIG. 22 illustrates a user interface on a mobile
`phoneto add funds to an account according to one embodi-
`ment.
`
`FIG. 23 illustrates a user interface on a mobile
`[0038]
`phoneto top up an account according to another embodiment.
`[0039]
`FIG. 24 illustrates a system to top up an account
`according to one embodiment.
`[0040]
`FIGS. 25-26 show methods to top up an account
`according to some embodiments.
`[0041]
`FIGS. 27-28 illustrate user interfaces to initiate a
`pre-determined purchase according to some embodiments.
`[0042]
`FIG. 29 illustrates a web page to confirm a pre-
`defined purchase according to one embodiment.
`[0043]
`FIG.30 illustrates a menu to launch separate appli-
`cations according to one embodiment.
`[0044]
`FIG. 31 illustrates a system to make a pre-defined
`purchase from a mobile phone according to one embodiment.
`[0045]
`FIG. 32 illustrates a method to make a pre-defined
`purchase according to one embodiment.
`[0046]
`FIG. 33 showsa data processing system, which can
`be used in various embodiments.
`
`DETAILED DESCRIPTION
`
`[0047] The following description and drawingsare illustra-
`tive and are not to be construed as limiting. Numerousspecific
`details are described to provide a thorough understanding.
`However, in certain instances, well known or conventional
`details are not described in order to avoid obscuring the
`
`24
`
`In one embodiment, an interchange is usedto inter-
`[0049]
`face with a plurality of different controllers of mobile com-
`munications, such as SMS messages. The interchange can be
`used to receive deposit requests and payment requests in an
`online environment. The interchange is configured to com-
`municate with the mobile phones through the different con-
`trollers to provide security and conveniencefor online trans-
`actions.
`
`FIG. 1 shows a system to facilitate online transac-
`[0050]
`tions according to one embodiment.In FIG.1, an interchange
`(101) is provided to interface with a plurality of different
`controllers (115) for communications with the mobile phones
`(117) over the wireless telecommunications network (105).
`[0051]
`In FIG. 1, a data storage facility (107) stores user
`accounts (121) and the corresponding phone numbers (123)
`ofthe mobile phones (117). The interchange (101) is coupled
`with the data storage facility (107) to confirm operations in
`the accounts (121) of the users via mobile communications
`with the mobile phones (117) at the corresponding phone
`numbers (123).
`[0052]
`In FIG.1, the interchange (101) may communicate
`with different controllers (115) of mobile communications
`via different networks (e.g., 105 and 103) and/or protocols.
`The interchange processes the requests in a common format
`and uses a set of converters for communications with the
`different controllers (115) respectively.
`[0053]
`For example, the controllers (115) maybe different
`aggregators, providers and/or SMSCsofdifferent mobile car-
`riers. Based on the phone numbers (123), the interchange
`(101) interfaces with the corresponding controllers (115) to
`communicate with the mobile phones (117) via text messag-
`ing to confirm the operations related to the corresponding
`accounts (121).
`[0054]
`In FIG.1, the user terminals (111) may use a unified
`interface to send requests to the interchange (101). For
`example, a web site of the interchange (101) may be used to
`receive deposit requests from the web browsers running in the
`user terminals (111). The deposit requests may be received
`directly from the user terminal (111), or via a third party
`whichinterfaces between the interchange (101) and the user
`terminal (111). For example, the third party may operate a
`web site to receive deposit requests from the user terminal
`(111) and provide the deposit requests to the interchange
`(101) via an application programminginterface (API) (e.g.,
`an API provided using a web service). The user terminals
`(111) are typically different from the mobile phones (117). In
`some embodiments, users may use the mobile phone (117)to
`access the web and submit the deposit request. Alternatively,
`
`24
`
`

`

`US 2011/0082772 Al
`
`Apr. 7, 2011
`
`the users may use the mobile phone (117) to submit the
`deposit requests via text messaging, email, instant messaging,
`etc.
`
`[0055] The use of the mobile phones(117) in the confirma-
`tion of the accounts (121) increases the security of the trans-
`action, since the mobile phones (117)are typically secured in
`the possession oftheusers.
`[0056]
`Further, in one embodiment, the interchange (101)
`mayuse the phonebills of the mobile phones (117) to collect
`funds for the accounts (121) that are associated with the
`mobile phones (117) for the convenience ofthe users (e.g.,
`those whodo not have a credit card or a bank account).
`[0057]
`In one embodiment, once the user accounts (121)
`are funded through the mobile phones (117), the users may
`use the user terminals (111) to access online servers (113) to
`make purchases. The users can use the accounts (121) to make
`the paymentfor the purchases, using the user terminals (111),
`withoutrevealing their financial information to the operators
`of the servers (113).
`[0058]
`In other embodiments, the interchange (101) may
`use other fund sourcesto deposit fundsinto the account(121).
`For example, the data storage facility (107) may further store
`information aboutotherfinancial accounts ofthe user, such as
`bank accounts, credit card accounts, PayPal accounts, etc.
`(not shown in FIG. 1). Such information aboutthe financial
`accountsofthe user can be associated with the phone number
`(123) in the data storage facility (107). In response to a
`deposit request from the user terminal (111), the interchange
`(101) mayidentify the phone number (123) to retrieve the
`information aboutat least one financial accountofthe user.
`
`Using the phone number (123) the interchange (101) may
`transmit a confirmation messageto the corresponding mobile
`phone (117). If the user replies to the confirmation message
`from the mobile phone (117), the interchange (101) may
`charge the financial account of the user (e.g., via automated
`clearing house (ACH))using the information aboutthe finan-
`cial account to deposit funds into the account (121) of the
`user. Alternatively, the user may provide the information
`aboutthe financial account(e.g., a bank account, a credit card
`number, a charge card number, etc.) from the mobile phone
`(117) together with the user’s reply to the confirmation mes-
`sage. Alternatively, the user may provide the information
`aboutthe financial account(e.g., a bank account, a credit card
`number, a charge card number, etc.) from the user terminal
`(111) together with the deposit request.
`[0059]
`In one embodiment, the fundsstored in the account
`(121) are in the unit of a currency (e.g., U.S. dollar, Euro,
`British pound, etc.) In some embodiments, the funds stored in
`the account (121) maybein the equivalent unit of a currency,
`such as points, stars, virtual currency/money,etc.
`[0060]
`In one embodiment, the mobile phones (117) are
`used by the corresponding users to make payments and/or
`manage funds, such as for making purchases in various web-
`sites hosted on the servers (113) of merchants and service
`providers and/or for transferring funds to or from an account
`(121) hosted on the data storage facility (107), or other
`accounts, such as telecommunication accounts of the mobile
`phones(117) with telecommunicationcarriers, phonebills of
`land-line telephoneservices, credit card accounts, debit card
`accounts, bank accounts, etc. The mobile phones (117) are
`used to confirm and/or approve the transactions associated
`with account (121) (or other accounts). The interchange (101)
`interfaces the mobile phones (117) and the servers (113) to
`
`confirm and/or approve transactions and to operate on the
`account (121) (and/or other accounts associated with the
`phone number(123)).
`[0061]
`For example, the user terminal (111) may provide
`the phone numbers (123) to the servers (113) to allow the
`servers (113) to charge the accounts (121) via the interchange
`(101). The interchange (101) sends a message to the mobile
`phone (117) via the phone number(123) to confirm the pay-
`ment. Once the paymentis confirmed via the corresponding
`mobile phone (117), the interchange (101) pays the server
`(113) using the funds from the corresponding the account
`(121) (and/or other accounts associated with the phone num-
`ber (123), such as bank accounts, credit card accounts, debit
`card accounts, mobile phone bills/accounts, land-line phone
`bill/accounts, etc.).
`[0062]
`Inone embodiment, the user terminal (111) may not
`even provide the phone number (123) to the server (113) to
`process the payment. The server (113) redirects a payment
`request to the interchange (101), which then prompts the user
`terminal (111) to provide the phone number(123) to the web
`site of the interchange (101).
`[0063]
`For example, the server (113) mayredirect the pay-
`ment request to the website of the interchange (101) with a
`reference indicating the purchase madevia the user terminal
`(111). The interchange (101) can use the reference to com-
`plete the paymentwith the server (113) for the purchase,after
`receiving the phone number (123) directly from the user
`terminal (111), or other information identifying the account
`(121), to confirm the paymentvia the mobile phone (117).
`[0064]
`In one embodiment, when the interchange (101)
`charges on the phone bill of the mobile phone (117) to fund
`the account (121), the mobile carrier of the mobile phone
`(117) may deduct a portion from the billed amount from the
`funds provided to the interchange (101). Thus, the inter-
`change (101) actually receives only a portion of the amount
`billed to the mobile phone (117). However, the interchange
`(101) may credit the full amountto the account (121) associ-
`ated with the mobile phone (117). The fees taken by the
`mobile carrier can be recovered through charging the user
`and/or the merchantfor the usage of the account (121).
`[0065]
`For example, the interchange (101) may charge the
`account (121) a fee for paying the server (113) to complete a
`purchase; and the interchange (101) may charge the server
`(113) a fee for transferring the funds to the server (113) (e.g.,
`by deducting a portion from the amountpaid by theuser to the
`operator of the server (113)). For example, the interchange
`(101) may charge a periodic fee (e.g., a monthly fee) to
`maintain the account (121). The interchange (101) may
`charge a fee when the fundsare initially deposited into the
`account (121) via the mobile phone (117), where the fee is
`smaller than the fee charged by the mobilecarrier.
`[0066]
`In one embodiment, the overall fees charged by the
`interchange (101) may be equalto or larger than the initial
`fees charged by the mobilecarrier to deposit the fundsinto the
`account (121), to avoid losing money. In some embodiment,
`the operations of the interchange (101) may be supported by
`advertisements; and the interchange (101) may chargeless
`than what the mobile carrier charges to deposit the fundsinto
`the account (121).
`[0067]
`For example, the interchange (101) may spread out
`the charges by the mobile carrier for depositing the funds into
`the account (121) on a per transaction basis or a per process
`basis, instead ofa lump sum atthe timethe user deposits funds
`into his account (121).
`
`25
`
`25
`
`

`

`US 2011/0082772 Al
`
`Apr. 7, 2011
`
`For example, the interchange (101) may charge the
`[0068]
`user account (121) a smaller fee than what the mobile carrier
`charges, when the fundsare initially deposited into the user
`account (121) via the mobile carrier. For instance, when a user
`deposits $10 to the account (121) via the mobile carrier, the
`mobile carrier may take $3 (30%), providing $7 to the inter-
`change (101). The interchange (101) may charge the user only
`$1, and thus credit the account (121) with $9; alternatively,
`the interchange (101) may credit the account (121) with the
`full $10, without deducting the amountthat is charged by the
`mobile carrier, at the time the funds are deposited.
`[0069] However, for the amount credited to the account
`(121), the interchange (101) is configured to pass to the mer-
`chants only $7 of the funds received from the mobilecarrier
`for the purchases madebythe user. The merchants may be the
`operators of the servers (113). The interchange (101) may
`charge the user and/or the merchantfees on a per transaction
`basis. For example, the user may be charged an amountfor a
`payment to the merchant; and the merchant may be charged
`another amount for the payment. Thus, the fees charged by
`the mobile carrier are actually deferred until the funds in the
`account are used; and the cost for the fees charged by the
`mobile c