Systems and methods for billing for a network enabled application through a network platform regardless of whether the network enabled application is hosted by the platform

• US 8,606,247 B2
• Filed: 09/18/2007
• Issued: 12/10/2013
• Est. Priority Date: 03/20/2006
• Status: Active Grant

• Current Assignee: SMS AC Incorporated
• Original Assignee: SMS AC Incorporated
• Inventors: Pousti, Michael, Ballester, Andrew
• Primary Examiner(s): Brandt, Christopher M
• Application Number:
  US11/857,300
• Publication Number:
  US 20080194228A1
• Time in Patent Office: 2,275 Days
• Field of Search: 455/406, 455/412.1, 455/412.2, 455/414.1, 455/414.2, 455/414.3, 455/407, 455/408
• US Class Current: 455/414.3
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: H04M 15/68 Payment of value-added services
• CPC Class Codes: H04M 2215/0196 Payment of value-added services, mainly when their charges are added on the telephone bill, e.g. payment of non-telecom services, e-commerce, on-line banking

Abstract

A platform for supporting network enabled applications enables billing for microtransactions associated with the applications using the users wireless network carriers. The platform also enables access to billing for third party network enabled applications by wrapping the third party network enabled applications in code that allows the third party network enabled applications to be rendered to the user and the billing component.

Claims

1. A platform for supporting a network-enabled application, comprising:

a plurality of connections to a respective plurality of wireless network carriers, each of the wireless network carriers supporting a plurality of user devices;

at least one interface having access to the Internet; and

one or more servers, each of the one or more servers comprising at least one processor, wherein the one or more servers

receive a request from one of the plurality of user devices via one of the plurality of connections, the request including a product identifier associated with a third-party application and an owner identifier associated with a user of the user device,

identify a remote application server associated with the third-party application based on the product identifier,

send a request to the identified remote application server via the interface having access to the Internet,

receive content associated with the third-party application from the identified remote application server,

encode the received content associated with the third-party application,

send the encoded content to the user device,

generate a billing message comprising a billing amount which should be charged to the user of the user device for use of the third-party application, and

send the billing message to a billing system of a wireless network carrier supporting the user device.

2. The platform of claim 1, wherein the one or more servers:

detect a billing event generated by the third-party application, the billing event containing an identifier assigned to the user of the user device; and

determine whether the billing event is valid;

wherein the one or more servers generates the billing message and sends the billing message to the billing system if it is determined that the billing event is valid.

3. The platform of claim 1, wherein the one or more servers encode the received content by translating the received content from a format in which it was received into an appropriate format for the user device.

4. The platform of claim 3, wherein the format in which the received content was received is an HTML format, and wherein translating the received content comprises removing at least one of javascript, iframe, and script features.

5. The platform of claim 3, wherein the format in which the received content was received is an HTML format, and translating the received content comprises translating the received content from the HTML format to Flash format.

6. The platform of claim 3, wherein the format in which the received content was received is an HTML format, and translating the received content comprises translating the received content from the HTML format to a SilverLight format.

7. The platform of claim 1, further comprising an application wrapper, wherein the one or more servers determine whether the user is registered to receive the third-party application, and wherein, if it is determined that the user is not registered to receive the third-party application, the application wrapper presents a login page to the user of the user device.

8. The platform of claim 2, further comprising an intermediary billing system, the intermediary billing system configured to register one of the plurality of users by:

receiving a mobile phone number of the registering user;

assigning an identifier to the registering user; and

associating the mobile phone number of the registering user with the identifier assigned to the registering user;

wherein sending the billing message to a billing system of the wireless network carrier supporting the user device comprises sending, via the wireless network carrier, at least one text message to a mobile phone number associated with an identifier of the user of the user device.

9. The platform of claim 8, wherein the intermediary billing system receives a registration request from a third party provider, wherein the registration request comprises the identifier which is assigned to the registering user, the identifier which is assigned to the registering user generated by the third party provider.

10. The platform of claim 8, wherein the intermediary billing system receives a registration request from the registering user, and generates the identifier which is assigned to the registering user.

11. The platform of claim 9, wherein the intermediary billing system comprises a database, and wherein the intermediary billing system:

assigns the identifier to the registering user in the database; and

sends a unique verification code to the third party provider.

12. The platform of claim 11, wherein the intermediary billing system:

receives a verification code validation request containing a returned verification code from the third party provider;

determines whether the returned verification code is the same as the unique verification code sent to the third party provider;

if the returned verification code is not the same as the unique verification code sent to the third party provider, returns an error message to the third party provider; and

if the returned verification code is the same as the unique verification code sent to the third party provider, returns a validity confirmation message to the third party provider.

13. The platform of claim 2, wherein the third-party application is not hosted by the platform.

14. The platform of claim 2, further comprising at least one Application Programming Interface (API) configured to receive the billing event.

15. The platform of claim 1, wherein the one or more servers receive the content associated with the third-party application in a first format and encode the received content associated with the third-party application in a second format required for rendering the received content on the user device.

16. The platform of claim 15, wherein the one or more servers identify a type of user interface on the user device.

17. A platform of claim 16, wherein the second format is different when the user interface is a mobile user interface than when the user interface is not a mobile user interface.