Search Images Maps Play YouTube News Gmail Drive More »
Sign in
Screen reader users: click this link for accessible mode. Accessible mode has the same essential features but works better with your reader.

Patents

  1. Advanced Patent Search
Publication numberUS20130144789 A1
Publication typeApplication
Application numberUS 13/753,189
Publication date6 Jun 2013
Filing date29 Jan 2013
Priority date12 Jun 2007
Also published asEP2168393A2, US7933799, US8195547, US20080313044, US20100174595, US20110173053, WO2008152118A2, WO2008152118A3
Publication number13753189, 753189, US 2013/0144789 A1, US 2013/144789 A1, US 20130144789 A1, US 20130144789A1, US 2013144789 A1, US 2013144789A1, US-A1-20130144789, US-A1-2013144789, US2013/0144789A1, US2013/144789A1, US20130144789 A1, US20130144789A1, US2013144789 A1, US2013144789A1
InventorsJanne Aaltonen, Sami Saru
Original AssigneeApple Inc.
Export CitationBiBTeX, EndNote, RefMan
External Links: USPTO, USPTO Assignment, Espacenet
Method and system for managing credits via a mobile device
US 20130144789 A1
Abstract
System and method for delivering upon request credits having monetary value to a mobile device using a communications network. An account of available credit for the user of the mobile device is maintained and authorization to issue credit is generated when a request for credit for the mobile device is received and there is available credit in the account associated with the mobile device equal to or greater than the requested credit. Credit may be offset, or sponsored, by one or more token providers and issued to the user, upon authorization, to enable the user to use the mobile device to purchase items, e.g., at a point of sale terminal.
Images(3)
Previous page
Next page
Claims(33)
We claim:
1. A method comprising:
transmitting, from a mobile computing device, a credit request requesting that a sponsor authorize issuance of a credit having monetary value to the mobile computing device; and
receiving, at the mobile computing device, from an issuing server, the credit having monetary value, wherein the credit having monetary value is issued to the mobile computing device upon the sponsor authorizing the credit request and the user of the mobile computing device is notified upon receiving the credit.
2. The method of claim 1, wherein the credit having monetary value is debited from an account associated with the user of the mobile computing device.
3. The method of claim 1, wherein the credit having monetary value is debited from an account associated with the sponsor.
4. The method of claim 1, wherein the sponsor authorizes the credit having monetary value by transmitting an authorization message to the issuing server.
5. The method of claim 4, wherein the credit request is transmitted to a mobile computing device of the sponsor.
6. The method of claim 4, wherein the credit request is transmitted to the issuing server and the issuing server transmits a second credit request to a mobile computing device of the sponsor, wherein the credit request identifies the sponsor.
7. The method of claim 1, wherein the credit request includes data indicating a requested monetary amount.
8. The method of claim 7, wherein the credit request includes data identifying an on sale item, wherein the requested monetary amount is based on a purchase price of the on sale item.
9. The method of claim 8, further comprising:
entering a code associated with the on sale item, the code indicating the purchase price of the on sale item.
10. The method of claim 8, wherein entering the code comprises scanning the code.
11. The method of claim 1, further comprising:
transmitting, to a point of sale system, data indicative of the credit having monetary value to purchase an on sale item.
12. A mobile computing device, comprising:
a processor; and
a memory containing instructions that, when executed, cause the processor to:
transmit a credit request requesting that a sponsor authorize issuance of a credit having monetary value to the mobile computing device; and
receive, from an issuing server, the credit having monetary value, wherein the credit having monetary value is issued to the mobile computing device upon the sponsor authorizing the credit request and the user of the mobile computing device is notified upon receiving the credit.
13. The mobile computing device of claim 12, wherein the credit having monetary value is debited from an account associated with the user of the mobile computing device.
14. The mobile computing device of claim 12, wherein the credit having monetary value is debited from an account associated with the sponsor.
15. The mobile computing device of claim 12, wherein the sponsor authorizes the credit having monetary value by transmitting an authorization message to the issuing server.
16. The mobile computing device of claim 15, wherein the credit request is transmitted to a mobile computing device of the sponsor.
17. The mobile computing device of claim 15, wherein the credit request is transmitted to the issuing server and the issuing server transmits a second credit request to a mobile computing device of the sponsor, wherein the credit request identifies the sponsor.
18. The mobile computing device of claim 12, wherein the credit request includes data indicating a requested monetary amount.
19. The mobile computing device of claim 18, wherein the credit request includes data identifying an on sale item, wherein the requested monetary amount is based on a purchase price of the on sale item.
20. The mobile computing device of claim 19, wherein the instructions further cause the processor to:
enter a code associated with the on sale item, the code indicating the purchase price of the on sale item.
21. The mobile computing device of claim 19, wherein entering the code comprises scanning the code.
22. The mobile computing device of claim 12, wherein the instructions further cause the processor to:
transmit, to a point of sale system, data indicative of the credit having monetary value to purchase an on sale item.
23. A non-transitory computer-readable medium containing instructions that, when executed by a mobile computing device, cause the mobile computing device to:
transmit, a credit request requesting that a sponsor authorize issuance of a credit having monetary value to the mobile computing device; and
receiving, from an issuing server, the credit having monetary value, wherein the credit having monetary value is issued to the mobile computing device upon the sponsor authorizing the credit request and the user of the mobile computing device is notified upon receiving the credit.
24. The non-transitory computer-readable medium of claim 23, wherein the credit having monetary value is debited from an account associated with the user of the mobile computing device.
25. The non-transitory computer-readable medium of claim 23, wherein the credit having monetary value is debited from an account associated with the sponsor.
26. The non-transitory computer-readable medium of claim 23, wherein the sponsor authorizes the credit having monetary value by transmitting an authorization message to the issuing server.
27. The non-transitory computer-readable medium of claim 26, wherein the credit request is transmitted to a mobile computing device of the sponsor.
28. The non-transitory computer-readable medium of claim 26, wherein the credit request is transmitted to the issuing server and the issuing server transmits a second credit request to a mobile computing device of the sponsor, wherein the credit request identifies the sponsor.
29. The non-transitory computer-readable medium of claim 23, wherein the credit request includes data indicating a requested monetary amount.
30. The non-transitory computer-readable medium of claim 29, wherein the credit request includes data identifying an on sale item, wherein the requested monetary amount is based on a purchase price of the on sale item.
31. The non-transitory computer-readable medium of claim 30, wherein the instructions further cause the mobile computing device to:
enter a code associated with the on sale item, the code indicating the purchase price of the on sale item.
32. The non-transitory computer-readable medium of claim 30, wherein entering the code comprises scanning the code.
33. The non-transitory computer-readable medium of claim 23, wherein the instructions further cause the mobile computing device to:
transmit, to a point of sale system, data indicative of the credit having monetary value to purchase an on sale item.
Description
    FIELD OF THE INVENTION
  • [0001]
    The present invention relates generally to methods and systems for payment of goods and services, and the issuance of credits toward the payment of goods and services, via a mobile device.
  • BACKGROUND OF THE INVENTION
  • [0002]
    Usage of cellular or mobile telephones is very popular and common. In a typical arrangement for use of a mobile telephone, a user subscribes to a mobile telephone service offered by a mobile telephone operator or carrier and enters into a pre-paid or post-paid plan with the mobile telephone operator. A pre-paid subscription plan is usually an arrangement where the user pays in advance for the telephone services to be used over a future period of time. A post-paid subscription plan is usually an arrangement where the user pays for the telephone services after using the services.
  • [0003]
    The services available using the mobile telephone may be voice services (i.e., making and receiving telephone calls), messaging services such as Short Message Service (SMS), Multimedia Message Service (MMS), data services such as Internet browsing or Wireless Application Protocol (WAP) browsing, video calls, downloading content, streaming content, purchasing applications such as games or other software, using location, guidance or navigation services, finding information, and communicating with a group of people and others.
  • [0004]
    Mobile telephones can also be used as a payment method in point of sales transactions. One example of such usage involves use of the near field communication (NFC) capabilities of a mobile telephone to use it as credit card in the point of sales transaction.
  • [0005]
    On the other hand, instead of being used to pay for goods and services, a mobile telephone can receive coupons for discounts which may be used in a point of sales transactions conducted using the mobile telephone or otherwise, and free samples which may be received using the mobile telephone or otherwise. In this regard, reference is made to International Publication No. WO 2007/060451.
  • SUMMARY OF THE INVENTION
  • [0006]
    The present invention is directed at least in part to a method and system for providing credits, vouchers or coupons representative of monetary value to users of mobile devices such as mobile telephones, as set forth in the appended claims. The users of the mobile telephones are able to use the monetary value of the credits to purchase goods and/or services at e.g. point of sale terminals and the like.
  • BRIEF DESCRIPTION OF THE DRAWINGS
  • [0007]
    The invention, together with further objects and advantages thereof, may best be understood by reference to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals identify like elements, and wherein:
  • [0008]
    FIG. 1 is a schematic of an exemplifying architecture of a first embodiment of a credit delivery system in accordance with the invention.
  • [0009]
    FIG. 2 is a schematic of an exemplifying architecture of a second embodiment of a credit delivery system in accordance with the invention.
  • [0010]
    FIG. 3 is a schematic of an exemplifying architecture of a third embodiment of a credit delivery system in accordance with the invention.
  • DETAILED DESCRIPTION OF THE INVENTION
  • [0011]
    Referring to the accompanying drawings wherein the same reference numerals refer to the same or similar elements, FIG. 1 shows an architecture of an embodiment of a mobile payment system in accordance with the invention which is designated generally as 10.
  • [0012]
    System 10 may be implemented to provide credits having monetary value to mobile devices 12 (only one of which is shown in FIG. 1) and thus can be considered to be independent of the mobile devices 12, i.e., not include the mobile devices. On the other hand, the invention also encompasses a system for enabling users of mobile devices 12 to receive credits having monetary value which would be inclusive of the mobile devices. In the latter case, the users may be required to view advertisements in exchange for the credits.
  • [0013]
    The mobile devices 12 may be any form of mobile terminal such as a mobile telephone, a multimedia computer, a personal digital assistant (PDA), a laptop computer or a personal computer.
  • [0014]
    Mobile devices 12 are arranged to use a communications network 14 to communicate with other elements of the system 10 described below. Communications network 14 can utilize any cellular network technologies which include, but are not limited to, GSM, WCDMA, CDMA, GPRS. In addition to traditional cellular networks, local area networks such as Wireless Local area networks (WLAN), BlueTooth (BT) and other technologies such as WiMax, Broadcasting over DVB-H, ISDB-T, DMB or broadcasting over cellular can be used. The communications network 14 can also be a generic Internet access network using any data transport methods. Moreover, the communications network 14 may be any cellular, broadcast, wide area, local area or Internet network. Communications network 14 can also be a combination of different communications networks such as a Wireless Local Area Network (WLAN) and a Wideband Code Division Multiplex (WCDMA) network.
  • [0015]
    Subscribers to the mobile telephone operator using the mobile devices 12 can use the same communications network or another communications network as the communications network 14 being used to receive credits, i.e., a hybrid network is possible.
  • [0016]
    In a preferred embodiment, the communications network 14 is a cellular network and the mobile device 12 is a mobile telephone.
  • [0017]
    System 10 also includes a billing system 16 operatively coupled to the communications network 14 or specific parts thereof, and may be arranged to maintain an account of available money for each mobile device. Further, billing system 16 may be arranged to monitor and/or meter usage of the communications network 14 by each mobile device 14 and monitor and/or meter usage and payments of or for the advertisements being delivered to each mobile device 12. The billing system 16 may be a real-time billing system or a close-to-real-time billing system. The billing system 16 or other suitable means associated with the system 10 can thus arrange for payment from users of the mobile devices 12 based on their usage of the communications network 14. Payment may be pre-paid, i.e. the user has paid for the service before using the communications network and the billing system monitors and reduces the paid amount in the user's account based on usage. Alternatively payment may be post-paid and a billing system monitors usage of the communications network and the user pays for the services after usage. Usage of the communications network 14 may entail voice services, messaging services (Short Message Service, Multimedia Message Service, Instant Message Service, Electronic mail services), video telephony services, push-to-talk services, data services such as Internet or Wireless Application Protocol (WAP) browsing services, content usage (television, radio, video) services, download services, premium SMS (pSMS) service, among others.
  • [0018]
    In one embodiment of the invention, billing system 16 meters usage of the services by each user and compares the metered usage with a free or subsidized balance allocated to each user. In this manner, although invoices are not sent to the users, the metered usage is compared with business rules associated with the users and the cost for providing the free or subsidized services to the users is invoiced directly or indirectly from advertisers. Other techniques to provide subsidized or free telephone services to the users are also envisioned. For subsidized telephone services, the users may be responsible for a portion of their usage and thus they would be interested in eliminating unnecessary use of such telephone services.
  • [0019]
    System 10 also includes a wallet service server 18 which in one embodiment, is a computer system running the wallet service, described below. Wallet service server 18 communications with the mobile devices 12 via the communications network 14, and is operatively coupled to the billing system 16.
  • [0020]
    In conjunction with the system 10, there may be one or more provisioning systems in the form of token providers 20 which provide tokens which can be used to offset some of the mobile service such as voice or messaging, or a token provider can be an advertiser which, in exchange for offsetting a portion of the mobile service being provided to users of the mobile devices 12, sends advertisements via communications network 14 to the users' mobile devices (additional details of this feature are described below). A token provider 20 may also be a party which wants to offset some specific payments to users of mobile devices 12. Each token provider 20 is provided with access via a computer program operating system 10 to the billing system 14 and the wallet service server 18. Billing system 14 would manage the payments from each token provider for whatever credits or services their tokens are designated to offset, or sponsor.
  • [0021]
    Regardless of the nature of the sponsorship provided by token provider(s) 20, each token provider 20 will cause credits or services, or possibly other items of value, to be provided to the users' mobile devices 12. As such, it should be understood that system 10 may be implemented to provide the credits or services arising from sponsorship by token provider(s) 20 to mobile devices 12 and thus can be considered to be independent of the token provider(s) 20, i.e., not include the token provider(s) 20 or the mobile devices 12. On the other hand, the invention also encompasses a system for enabling token providers to offset delivery of credits or services, or possibly other items of values, to users of mobile devices 12 to receive credits or services, and this system would be inclusive of the token provider(s) 20 and mobile devices 12.
  • [0022]
    Issuer 22 is a party which can issue vouchers, coupons or mobile credits for the mobile devices 12. The issuer 22 can issue the credits using any of the techniques disclosed in International Publication No. WO 2007/060451, incorporated in its entirety by reference herein. In one such technique, issuer 22 issues a code which is delivered to the mobile device 12, e.g., via the wallet service server 18 and possibly also via the billing system 16. This code, in practice, works as a coupon which can be used in or by a point of sales (POS) terminal 24. The code is used in or by the POS terminal 24 to verify the amount of credit associated with the code. Thus, the POS terminal 24 sends the code to issuer 22 so that issuer 22 can verify and provide a verification message to the POS terminal 24. When a positive verification message is received by the POS terminal 24, the user of the mobile device 12 is granted the value of the issued coupon for consideration by the POS terminal 24.
  • [0023]
    The token provider(s) 20 is operatively connected to the issuer 22 to enable each token provider 20 to authorize issuance of credits to the users' mobile devices 12. The issuer 22 is also operatively coupled to the billing system 16 to coordinate payment for the credits, i.e., allocate payments for the credits to the different token providers 20. The issuer 22 is also operatively coupled to the wallet service server 18 to provide the credits to the mobile devices 12.
  • [0024]
    There are several ways to use system 10 to enable a user of a mobile device 12 to receive and use an electronically provided credit, which is being considered equivalent to a voucher or coupon. In one embodiment, a user of the mobile device 12 sends a request for a credit having monetary value (message S1 in FIG. 1). The request can be short message service (SMS) message sent over communications network 14 or a Multimedia Message Service (MMS) message. The request can also be a premium SMS message with a specific monetary value sent to a specific number. Further, the request can be, for example, a Web or Wireless Application Protocol (WAP) session between the wallet service server 18 and the mobile device 12. In addition, the request can be generated by a special application running in the mobile device 12. This special application can be, for example, Java, Symbian or, an application running in Subscriber Identity Module. (SIM application). Other forms of requests, and applications for generating such requests are also envisioned.
  • [0025]
    The message S1 indicating a request for a credit having monetary value is analyzed by the wallet service server 18. The wallet service server 18 communicates with billing system 16, message S2, to determine whether the user of the mobile device 12 which generated the request message S1 has a credit in their account maintained by the billing system 16. The credit in each account can be so called pre-paid credit, i.e., existing and available money, or it can be post-paid credit. For pre-paid credit, the requested amount of money is deducted from the amount in the pre-paid account. For post-paid credit, the requested amount of money will be invoiced later.
  • [0026]
    In the embodiment described above, the wallet service server 18 communicates with the billing system 16 to ascertain whether the user requesting credit has available credit in their account (pre-paid credit) or the ability to draw on a line of credit (post-paid credit). In an alternative embodiment, the wallet service server 18 communicates with the issuer 22, or even possibly with a third party such as a bank or credit card company (not shown in FIG. 1) to ascertain whether the issuer 22 or third party has an account with pre-paid or post-paid credit for the user of the mobile device 12 requesting credit.
  • [0027]
    Regardless of which technique is used to ascertain the availability of credit to the user of the mobile device 12 requesting credit, when there is sufficient credit, i.e., in the account maintained by the billing system 16 or by the third party such as a bank or credit card company, this causes a process of generating and delivering a code to be used to confirm the transaction. The code is typically generated by the issuer 22, as in prior art techniques. In one embodiment of the invention, the code corresponds to the monetary value of the requested credit or the monetary value of the premium SMS sent from the mobile terminal 12 to the wallet service server 18. The monetary value can be less then, equal to or more than the requested amount of credit depending on possible transaction fees and also on the existence and nature of possible token providers 20 of the credit request.
  • [0028]
    Once generated, the code to be used in the POS terminal 24 is delivered to the mobile device 12 by message S3.
  • [0029]
    Once the message S3 is received by the mobile device 12, a computer program in the mobile device 12 can enable the user of the mobile device 12 to obtain money or items, tangible or intangible, having monetary value using the POS terminal 24. In one embodiment, message S3 is readable by the user, e.g. by displaying the message to the user as a text message, and the user may use the code by entering the code at the POS terminal using numeric keys at the POS terminal. The POS terminal 24 validates the code from the user 12, for example, using prior art techniques.
  • [0030]
    In some embodiments of the invention, the token provider 20 may be another subscriber to the mobile telephone operator, such as a friend or a parent of the user of the mobile device 12. Thus, in the embodiment shown in FIG. 2, a user of mobile device 12 sends a message to a token provider 20, e.g., his mother, to ask her to give him some money (message S11) in order to, for example, buy an ice cream from a shop. Alternatively, the user of mobile device 12 may ask token provider 20 to give him an authorization/credit to buy a certain item via message S11. The item sought to be purchased may be identified in message S11 using different means like an ISBN number of a book or as a web link to a web site having information about the item (e.g., a link to a book in the Amazon.com web store), a key word, a bar code, or a bar code number.
  • [0031]
    Upon receipt of message S11, e.g., by a mobile device of the token provider 20, a computer program in the mobile device of the token provider 20 would be arranged to enable the user thereof to connect with wallet service server 18 to grant credit having a certain monetary value or credit for the item for the user of the mobile device 12 (message S12). This may take the form of an authorization to allow a certain amount of credit from an account maintained by the billing system 16 to be used by the user of mobile device 12.
  • [0032]
    Identification of an item may be implemented such that the user of the mobile device 12 contacts token provider 20 by sending, for example, a MMS message identifying an item sought to be purchased and disclosing or otherwise providing a bar code of the item (message S11). This bar code information may be then delivered to the wallet service server 18, via message S12, by including a picture received in the message S11 or as a SMS message containing a bar code number.
  • [0033]
    The connection between a token provider 20 and the wallet service server 18 may be implemented in several ways, including as a SMS, MMS, using Web/WAP interface, or using a software application installed in the token provider's mobile device (an application in the mobile device will then manage the connection between the mobile device and the wallet service server 18, e.g., using SMS or a data connection). The wallet service server 18 may then communicate with billing system 16 (as in FIG. 1) to ascertain the availability of credit, as explained above.
  • [0034]
    After the availability of credit to the user of mobile device 12 requesting such credit is checked and confirmed, the wallet service server 18 notifies the user of mobile device 12 about the available credit (message S13), and the user can then proceed with a purchase as explained above with reference to FIG. 1.
  • [0035]
    As shown in FIG. 3, an embodiment of the present invention also contemplates only indirect communications between the user of the mobile device 12 and a token provider 20. In this embodiment, the user of the mobile device communicates with the wallet service server 18 to request credit (message S21) and the wallet service server 18 forwards as such or as a modified request to a token provider identified in the message S21 by the user of the mobile device 12. In some embodiments, it is conceivable that the user does not know for certain whether there will be a token provider willing to partly or even fully cover the requested credit. Wallet service server 18 then communicates with a token provider 20 advising the token provider of the user's request for credit and requesting a response as to whether the token provider 20 is willing to provide some or all of the requested credit (message S22). If token provider 20 agrees to provide credit, a message S23 is sent by token provider 20 to the wallet service server 18 which proceeds to issue credit to the user and notify the user of the available credit (message S24), and possibly also notify the user of the identity of the token provider or sponsors of the credit. Alternatively the credit can be used to top-up the amount of credit in the user's account in the billing system 16. The available credit can be used by the user of the mobile device in the manner described above.
  • [0036]
    The process by which the wallet service server 18 identifies whether or not the token provider can provide some or all of the requested credit can involve the sending of a series of messages, in the form of a negotiation, or dialogue, between the wallet service server 18 and the token provider 20. For example, the token provider 20 may respond, in message S23, with a message indicating an amount that the token provider 20 is willing to provide. The wallet service server 18 can compare this amount with the amount of requested credit; if it is less than the amount of requested credit, the wallet service server 18 can check the balance associated with the mobile device in the billing system 16, add this to the amount of credit the token provider 20 has indicated it is willing to provide, and if there is a shortfall in the amount of available credit (i.e. a combination of that in the billing system 16 and the amount of credit agreed to be provided by the token provider 20), the wallet service server 18 could transmit a further request message (i.e. a repeat of message S21) to the token provider 20 or another token provider. The amount of credit requested in the further request message will be less than that specified in the initial S21 message, but more than that offered by the token provider in message S23. It will be appreciated that this process can continue, iteratively, until the token provider 20 has agreed to provide an amount that, together with the available credit in the billing system 16, equals the requested credit. If the token provider 20 is unable to provide an amount of credit that would cover the shortfall, the wallet service system 18 can coordinate similar requests between a plurality of different token providers 20 such that the requested credit is provided by a combination of different token providers 20 (and/or including the billing system 16).
  • [0037]
    In one embodiment, a token provider 20 may be an entity or individual that wants to advertise products or services to customers participating in a mobile marketing arrangement, or an advertisement management system that is operated by, for example, an advertising delivery company. In exchange for providing credit to a user, the user would be required to be exposed to one or more advertisements.
  • [0038]
    A token provider can thus refer to a brand owner, a service provider, an advertisement agent, a merchant or any other party that wants to provide advertisements to consumers. Advertisements can be commercial, such as a product or service promotion, or non-commercial, such as a general information service notification. A token provider may also be a company in the business of delivering advertisements from several advertisers, i.e., it is the intermediary between advertisers and the operators of advertisement distribution channels. Such a token provider would create an advertisement management system, which could be over an Internet interface, and includes tools for each advertiser to define rules of their advertisement campaign, i.e., to enable them to tailor the advertisement campaign to their specific desires. This may include reserving, programming and/or booking an advertising campaign via an Internet interface. Parameters which are determined include, but are not limited to, the time period or periods when to send advertisements, the duration of the advertising campaign, the target group or groups, demographics of the target group(s), the format or type of advertisement, the target price level or cost per advertisement or for the advertising campaign in its entirety, the sociological background of the target audience, demographics of the target group(s) including, for example, age, sex and income level(s), target telephone type, etc. In addition to determining the rules, each advertiser typically provides one or more actual advertisements in the form of data, text, pictures, video, audio, html-documents, links, television content, videos, HTML, xHTML, WAP pages, web pages, etc., or any digital content compatible for reception and display by the users' mobile devices 12.
  • [0039]
    The server including or interfacing with the billing system 16, wallet service server 18 and issuer 22 may also include a database containing information such as profiles of the users of the mobile devices 12. Alternatively, the wallet service server 18 includes such a database. In this manner, each token provider could be provided with data about each user requesting credit (in the message from the wallet service server 18 to the token provider 20), determine which user or users they want to receive their advertisements as per their advertising campaign, and authorize credit only for the user or users. An advertisement-supported system for providing credit to users of mobile devices is therefore provided. In the arrangement in which the database is associated with the wallet service server 18, the database could further include data identifying mobile devices and token providers registered in respect thereof. The wallet service server 18 could then perform an initial filtering of credit requests by querying the database in order to identify which, if any, of the available token providers the mobile device has registered with. In this way the wallet service server 18 would only send user data to token providers with which the user associated with the requesting mobile device has registered. In a further arrangement the wallet service server 18 is arranged to send the credit request to token providers with whom the user has registered, but without any user data. This arrangement is particularly useful in environments where the user data is maintained by a given token provider upon registration of the user and where data protection requires that the user data is not distributed beyond the token provider.
  • [0040]
    Several computer programs resident on computer-readable media may be used in the invention. One computer program is resident in a server which controls or functions as the billing system 16, wallet service server 18 and issuer 22, and interfaces with the mobile device 12 via the communications network 14 and with the token provider 20, e.g., also via a communications network. This computer program enables users of mobile devices to request and receive credit, possibly from one or more token providers. In this regard, the designation of elements as a billing system 16, wallet service server 18 and issuer 22 are for ease of explanation of the invention and it is envisioned that all of these elements can be combined in a single electronic component.
  • [0041]
    In the context of this document, computer-readable medium could be any means that can contain, store, communicate, propagate or transmit a program for use by or in connection with the method, system, apparatus or device. The computer-readable medium can be, but is not limited to (not an exhaustive list), electronic, magnetic, optical, electromagnetic, infrared, or semi-conductor propagation medium. The medium can also be (not an exhaustive list) an electrical connection having one or more wires, a portable computer diskette, a random access memory (RAM), a read-only memory (ROM), an erasable, programmable, read-only memory (EPROM or Flash memory), an optical fiber, and a portable compact disk read-only memory (CDROM). The medium can also be paper or other suitable medium upon which a program is printed, as the program can be electronically captured, via for example, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. Also, a computer program or data may be transferred to another computer-readable medium by any suitable process such as by scanning the computer-readable medium.
  • [0042]
    One embodiment of a computer program in accordance with the invention which delivers upon request credits having monetary value to a mobile device using a communications network is arranged to maintain an account of available credit for the user of the mobile device (a function of the billing system 16), receive a request for credit from the mobile device 12, ascertain whether there is available credit in the account associated with the mobile device equal to or greater than the requested credit (a function of the wallet service server 18), generate an authorization to issue credit when there is available credit in the account (a function of the wallet service server 18), issue credit in response to the authorization (a function of the issuer 22), and notify the user of the mobile device via the communications network of the issuance of credit (a function of the wallet service server 18).
  • [0043]
    The same or a different computer program can maintain and manage both pre-paid credit accounts which have an available balance and post-paid credit accounts which require later payment. The computer program manages the pre-paid account such that the account is reduced by each amount of authorized credit.
  • [0044]
    The same or a different computer program can also enable one or more token providers to provide available credit into the account of each user of a mobile device, and also manage payments from each token provider for credits they have provided.
  • [0045]
    The same or a different computer program can also issue a code indicative of the issuance of a specific amount of credit and coordinate delivery of the code to the mobile device. As noted above, the code can be used by a point of sale terminal in order to verify the amount of credit associated with the code.
  • [0046]
    The foregoing enables innovative and focused mobile marketing and advertising. Indeed, the popularity of mobile telephones has enabled their use, along with related infrastructure, as a media for providing mobile marketing, i.e., advertisements to the users of the telephones.
  • [0047]
    This is important because such a concept is considered by advertisers as the next new channel to directly reach consumers since it utilizes core assets and characteristics of the mobile media, namely, it is personal in that it is directed solely to individual consumers, it is “always on” and can reach the consumers whenever they access their communications devices, it is mobile and naturally forms groups of people who communicate actively with each other. These characteristics combined with social networks—based approaches of the Internet could form a very powerful base to execute marketing strategies.
  • [0048]
    In general, mobile marketing and advertising can be divided into the following four categories: mobile marketing, mobile advertising, mobile direct marketing and mobile customer relation management (CRM). The present invention in any of its forms discussed above is applicable to all categories.
  • [0049]
    Mobile marketing is commonly considered as the systematic planning, implementing and control of a mix of business activities intended to bring together buyers and sellers for the mutually advantageous exchange or transfer of products or services where the primary point of contact with the consumer is via their mobile device.
  • [0050]
    Mobile advertising is commonly considered as the paid, public, non-personal announcement of a persuasive message by an identified token provider as well as the non-personal presentation or promotion by a firm of its products to its existing customers and potential customers where such communication is delivered to a mobile telephone or other mobile device. Examples of mobile advertising include: Wireless Application Protocol (WAP) Banner ads, mobile search advertising, mobile video bumpers, and interstitial ads in or on device portals.
  • [0051]
    Mobile direct marketing is commonly considered a sales and promotion technique in which promotional materials are delivered individually to potential customers via the potential customer's mobile telephone or other mobile device. Examples of mobile direct marketing include the sending of Short Message Service (SMS), Multimedia Message Service (MMS) or Wireless Application Protocol (WAP) push messages, Bluetooth messaging and other marketing to mobile telephones or other mobile devices.
  • [0052]
    Mobile customer relation management is commonly considered as a combination of all the foregoing in a manner that establishes a long-term, engaging relationship between the customer and the marketing or promoting company.
  • [0053]
    At present, mobile marketing and advertising is mostly based on push campaigns to opt-in a consumer mobile number in a database, or pull campaigns that acquire mobile telephone numbers from consumers. The most typical example of the pull campaign is the “text-to-win” campaign where, e.g., a soft drink bottle contains a short code to be sent via text message to a certain telephone number. In return, the consumer receives a notification if they have won with the selected marketing message, or a series of messages is broadcast to their mobile telephone. Other popular methods of direct advertisement are achieved using text and video messaging.
  • [0054]
    Having described exemplary embodiments of the invention with reference to the accompanying drawings, it will be appreciated that the present invention is not limited to those embodiments, and that various changes and modifications can be effected therein by one of ordinary skill in the art without departing from the scope or spirit of the invention as defined by the appended claims. For example, while it is described that a mobile phone user will initiate a request for issuance of credits, it is foreseen that the initiation of requests can come from an advertiser or sponsor, wherein after receiving the request the system checks to determine if enough credits are present in a user's account to issue credits to the particular user.
Patent Citations
Cited PatentFiling datePublication dateApplicantTitle
US7478065 *23 Dec 199913 Jan 2009Swisscom Mobile AgPayment transaction method and payment transaction system
US7533047 *3 May 200512 May 2009International Business Machines CorporationMethod and system for securing card payment transactions using a mobile communication device
US20020091569 *1 Aug 200111 Jul 2002Keiko KitauraElectronic coupon system
US20060173772 *2 Feb 20053 Aug 2006Hayes John BSystems and methods for automated processing, handling, and facilitating a trade credit transaction
US20070011099 *10 Jul 200611 Jan 2007Conrad SheehanSECURE ELECTRONIC TRANSACTIONS BETWEEN A MOBILE DEVICE AND OTHER MOBILE, FIXED, or VIRTUAL DEVICES
US20070022058 *18 Jul 200625 Jan 2007Fujitsu LimitedWireless computer wallet for physical point of sale (POS) transactions
US20070094113 *21 Oct 200526 Apr 2007Eduardo ChapetaTransactional mobile system
US20080059375 *6 Sep 20076 Mar 2008Basil Munir AbifakerPayment Card Terminal for Mobile Phones
US20090157546 *11 Feb 200818 Jun 2009G-Xchange, Inc.Person to person virtual cash transfer transaction using mobile phones
US20100299256 *4 Aug 201025 Nov 2010Yahoo! Inc.Systems and methods for implementing person-to-person money exchange
Referenced by
Citing PatentFiling datePublication dateApplicantTitle
US857090825 Apr 201329 Oct 2013Headwater Partners I LlcAutomated device provisioning and activation
US85837812 Mar 200912 Nov 2013Headwater Partners I LlcSimplified service network architecture
US858811013 Sep 201219 Nov 2013Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US858954125 May 201119 Nov 2013Headwater Partners I LlcDevice-assisted services for protecting network capacity
US860691124 Jan 201210 Dec 2013Headwater Partners I LlcFlow tagging for service policy implementation
US86261159 Sep 20117 Jan 2014Headwater Partners I LlcWireless network service interfaces
US86301922 Mar 200914 Jan 2014Headwater Partners I LlcVerifiable and accurate service usage monitoring for intermediate networking devices
US863061115 Nov 201214 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US863061719 Oct 201214 Jan 2014Headwater Partners I LlcDevice group partitions and settlement platform
US863063018 Dec 201214 Jan 2014Headwater Partners I LlcEnhanced roaming services and converged carrier networks with device assisted services and a proxy
US863110215 Nov 201214 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US86348052 Aug 201221 Jan 2014Headwater Partners I LlcDevice assisted CDR creation aggregation, mediation and billing
US863482112 Nov 201221 Jan 2014Headwater Partners I LlcDevice assisted services install
US863533525 May 201121 Jan 2014Headwater Partners I LlcSystem and method for wireless network offloading
US863567828 Mar 201321 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US863981115 Jan 201328 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US864019815 Jan 201328 Jan 2014Headwater Partners I LlcAutomated device provisioning and activation
US866636413 Sep 20124 Mar 2014Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US86675714 Dec 20124 Mar 2014Headwater Partners I LlcAutomated device provisioning and activation
US86755072 Mar 200918 Mar 2014Headwater Partners I LlcService profile management with user preference, adaptive policy, network neutrality and user privacy for intermediate networking devices
US868809913 Sep 20121 Apr 2014Headwater Partners I LlcOpen development system for access service providers
US869507319 Apr 20138 Apr 2014Headwater Partners I LlcAutomated device provisioning and activation
US871363012 Apr 201229 Apr 2014Headwater Partners I LlcVerifiable service policy implementation for intermediate networking devices
US872455419 Mar 201313 May 2014Headwater Partners I LlcOpen transaction central billing system
US872512328 Sep 201113 May 2014Headwater Partners I LlcCommunications device with secure data path processing agents
US873795722 Apr 201327 May 2014Headwater Partners I LlcAutomated device provisioning and activation
US87451914 Oct 20113 Jun 2014Headwater Partners I LlcSystem and method for providing user notifications
US874522012 Jul 20133 Jun 2014Headwater Partners I LlcSystem and method for providing user notifications
US878866120 Jan 201422 Jul 2014Headwater Partners I LlcDevice assisted CDR creation, aggregation, mediation and billing
US87937581 Dec 201129 Jul 2014Headwater Partners I LlcSecurity, fraud detection, and fraud mitigation in device-assisted services systems
US879790816 May 20135 Aug 2014Headwater Partners I LlcAutomated device provisioning and activation
US87994512 Mar 20095 Aug 2014Headwater Partners I LlcVerifiable service policy implementation for intermediate networking devices
US883277720 Sep 20119 Sep 2014Headwater Partners I LlcAdapting network policies based on device service processor configuration
US88393872 Mar 200916 Sep 2014Headwater Partners I LlcRoaming services network and overlay networks
US88393882 Mar 200916 Sep 2014Headwater Partners I LlcAutomated device provisioning and activation
US886845517 Aug 201221 Oct 2014Headwater Partners I LlcAdaptive ambient services
US88861629 Jan 201411 Nov 2014Headwater Partners I LlcRestricting end-user device communications over a wireless access network associated with a cost
US88930091 Dec 201118 Nov 2014Headwater Partners I LlcEnd user device that secures an association of application to service policy with an application certificate check
US889774320 Dec 201125 Nov 2014Headwater Partners I LlcVerifiable device assisted service usage billing with integrated accounting, mediation accounting, and multi-account
US88977442 Oct 201225 Nov 2014Headwater Partners I LlcDevice assisted ambient services
US889807913 Sep 201225 Nov 2014Headwater Partners I LlcNetwork based ambient services
US889829321 Sep 201125 Nov 2014Headwater Partners I LlcService offer set publishing to device agent with on-device service selection
US89034522 Oct 20122 Dec 2014Headwater Partners I LlcDevice assisted ambient services
US892446928 Sep 201130 Dec 2014Headwater Partners I LlcEnterprise access control and accounting allocation for access networks
US892454328 Sep 201130 Dec 2014Headwater Partners I LlcService design center for device assisted services
US892454920 Aug 201230 Dec 2014Headwater Partners I LlcNetwork based ambient services
US894802518 Apr 20143 Feb 2015Headwater Partners I LlcRemotely configurable device agent for packet routing
US90140267 Feb 201221 Apr 2015Headwater Partners I LlcNetwork based service profile management with user preference, adaptive policy, network neutrality, and user privacy
US90260793 Jan 20145 May 2015Headwater Partners I LlcWireless network service interfaces
US903712728 Apr 201419 May 2015Headwater Partners I LlcDevice agent for remote user configuration of wireless network access
US909431123 Jul 201428 Jul 2015Headwater Partners I, LlcTechniques for attribution of mobile device data traffic to initiating end-user application
US9111272 *25 Mar 201018 Aug 2015Bizmodeline Co., Ltd.Mobile payments
US913770131 Mar 201515 Sep 2015Headwater Partners I LlcWireless end-user device with differentiated network access for background and foreground device applications
US91377392 Mar 200915 Sep 2015Headwater Partners I LlcNetwork based service policy implementation with network neutrality and user privacy
US91439761 Apr 201522 Sep 2015Headwater Partners I LlcWireless end-user device with differentiated network access and access status for background and foreground device applications
US91544282 Apr 20156 Oct 2015Headwater Partners I LlcWireless end-user device with differentiated network access selectively applied to different applications
US91548266 Apr 20126 Oct 2015Headwater Partners Ii LlcDistributing content and service launch objects to mobile devices
US917310425 Mar 201527 Oct 2015Headwater Partners I LlcMobile device with device agents to detect a disallowed access to a requested mobile data service and guide a multi-carrier selection and activation sequence
US917930819 Apr 20123 Nov 2015Headwater Partners I LlcNetwork tools for analysis, design, testing, and production of services
US917931519 Mar 20153 Nov 2015Headwater Partners I LlcMobile device with data service monitoring, categorization, and display for different applications and networks
US917931623 Mar 20153 Nov 2015Headwater Partners I LlcMobile device with user controls and policy agent to control application access to device location data
US917935930 Mar 20153 Nov 2015Headwater Partners I LlcWireless end-user device with differentiated network access status for different device applications
US91980429 Jan 201324 Nov 2015Headwater Partners I LlcSecurity techniques for device assisted services
US919807410 Apr 201524 Nov 2015Headwater Partners I LlcWireless end-user device with differential traffic control policy list and applying foreground classification to roaming wireless data service
US919807515 Apr 201524 Nov 2015Headwater Partners I LlcWireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US919807616 Apr 201524 Nov 2015Headwater Partners I LlcWireless end-user device with power-control-state-based wireless network access policy for background applications
US919811724 Mar 201524 Nov 2015Headwater Partners I LlcNetwork system with common secure wireless message service serving multiple applications on multiple wireless devices
US920428218 Dec 20121 Dec 2015Headwater Partners I LlcEnhanced roaming services and converged carrier networks with device assisted services and a proxy
US92043743 Apr 20151 Dec 2015Headwater Partners I LlcMulticarrier over-the-air cellular network activation server
US921515926 Mar 201515 Dec 2015Headwater Partners I LlcData usage monitoring for media data services used by applications
US921561313 Apr 201515 Dec 2015Headwater Partners I LlcWireless end-user device with differential traffic control policy list having limited user control
US922002728 Aug 201522 Dec 2015Headwater Partners I LlcWireless end-user device with policy-based controls for WWAN network usage and modem state changes requested by specific applications
US92257979 Apr 201529 Dec 2015Headwater Partners I LlcSystem for providing an adaptive wireless ambient service to a mobile device
US923240324 Mar 20155 Jan 2016Headwater Partners I LlcMobile device with common secure wireless message service serving multiple applications
US923583120 Jul 201212 Jan 2016Gofigure Payments, LlcMobile payment systems and methods
US924745018 Dec 201226 Jan 2016Headwater Partners I LlcQuality of service for device assisted services
US925366310 Dec 20132 Feb 2016Headwater Partners I LlcControlling mobile device communications on a roaming network based on device state
US925873517 Apr 20159 Feb 2016Headwater Partners I LlcDevice-assisted services for protecting network capacity
US92705595 Dec 201323 Feb 2016Headwater Partners I LlcService policy implementation for an end-user device having a control application or a proxy agent for routing an application traffic flow
US927118416 Apr 201523 Feb 2016Headwater Partners I LlcWireless end-user device with per-application data limit and traffic control policy list limiting background application traffic
US927743316 Apr 20151 Mar 2016Headwater Partners I LlcWireless end-user device with policy-based aggregation of network activity requested by applications
US927744510 Apr 20151 Mar 2016Headwater Partners I LlcWireless end-user device with differential traffic control policy list and applying foreground classification to wireless data service
US931991313 Apr 201519 Apr 2016Headwater Partners I LlcWireless end-user device with secure network-provided differential traffic control policy list
US93511935 Dec 201324 May 2016Headwater Partners I LlcIntermediate networking devices
US93861217 Apr 20155 Jul 2016Headwater Partners I LlcMethod for providing an adaptive wireless ambient service to a mobile device
US938616530 May 20145 Jul 2016Headwater Partners I LlcSystem and method for providing user notifications
US939246214 Nov 201412 Jul 2016Headwater Partners I LlcMobile end-user device with agent limiting wireless data communication for specified background applications based on a stored policy
US949119924 Jul 20148 Nov 2016Headwater Partners I LlcSecurity, fraud detection, and fraud mitigation in device-assisted services systems
US949156422 Jul 20168 Nov 2016Headwater Partners I LlcMobile device and method with secure network messaging for authorized components
US952157817 Apr 201513 Dec 2016Headwater Partners I LlcWireless end-user device with application program interface to allow applications to access application-specific aspects of a wireless network access policy
US953216122 Dec 201527 Dec 2016Headwater Partners I LlcWireless device with application data flow tagging and network stack-implemented network access policy
US953226115 Jan 201427 Dec 2016Headwater Partners I LlcSystem and method for wireless network offloading
US95443972 Feb 201510 Jan 2017Headwater Partners I LlcProxy server for providing an adaptive wireless ambient service to a mobile device
US955788923 Jan 201331 Jan 2017Headwater Partners I LlcService plan design, user interfaces, application programming interfaces, and device management
US956554325 Sep 20137 Feb 2017Headwater Partners I LlcDevice group partitions and settlement platform
US956570719 Dec 20147 Feb 2017Headwater Partners I LlcWireless end-user device with wireless data attribution to multiple personas
US957201924 Nov 201414 Feb 2017Headwater Partners LLCService selection set published to device agent with on-device service selection
US957818212 May 201421 Feb 2017Headwater Partners I LlcMobile device and service management
US959147429 Aug 20147 Mar 2017Headwater Partners I LlcAdapting network policies based on device service processor configuration
US960945910 Dec 201428 Mar 2017Headwater Research LlcNetwork tools for analysis, design, testing, and production of services
US960954415 Nov 201328 Mar 2017Headwater Research LlcDevice-assisted services for protecting network capacity
US961519215 Jul 20164 Apr 2017Headwater Research LlcMessage link server with plural message delivery triggers
US964195717 Aug 20162 May 2017Headwater Research LlcAutomated device provisioning and activation
US96479183 Aug 20169 May 2017Headwater Research LlcMobile device and method attributing media services network usage to requesting application
US967473126 Jul 20166 Jun 2017Headwater Research LlcWireless device applying different background data traffic policies to different device applications
US970577123 Jul 201411 Jul 2017Headwater Partners I LlcAttribution of mobile device data traffic to end-user application based on socket flows
US970606114 Nov 201411 Jul 2017Headwater Partners I LlcService design center for device assisted services
US974989815 Apr 201529 Aug 2017Headwater Research LlcWireless end-user device with differential traffic control policy list applicable to one of several wireless modems
US974989915 Apr 201529 Aug 2017Headwater Research LlcWireless end-user device with network traffic API to indicate unavailability of roaming wireless connection to background applications
US97558426 Apr 20125 Sep 2017Headwater Research LlcManaging service user discovery and service launch object placement on a device
US20100193699 *4 Feb 20105 Aug 2010Fujifilm CorporationRadiography network system and radiographic image capturing system control method
US20110238569 *25 Mar 201029 Sep 2011Bizmodeline Co., Ltd.Mobile payments
US20130229951 *19 Apr 20135 Sep 2013Headwater Partners I LlcAutomated device provisioning and activation
US20140006276 *28 Jun 20122 Jan 2014Bank Of America CorporationMobile wallet account number differentiation
US20140365363 *9 Jun 201411 Dec 2014Prairie Cloudware, IncSecure integrative vault of consumer payment instruments for use in payment processing system and method