Open transaction central billing system
View Patent ↗Systems and methods comprise an end-user device, including one or more processors configured to execute a payment component, the payment component configured to transmit, by the end-user device to a transaction server, an indication of a user desire to use a data service, the data service being outside a current service plan of the end-user device or available at a lower cost within a different service plan; receive a billing request from a transaction server in response to the indication of the user desire, the billing request including a service plan offer associated with the data service; and transmit a response to the billing request; wherein the end-user device is in secure network communication with the transaction server via a first network.
1. A system, comprising:
an end-user device, including one or more processors configured to execute a payment component, the payment component configured to
transmit, by the end-user device to a transaction server, an indication of a user desire to use a data service, the data service being outside a current service plan of the end-user device or available at a lower cost within a different service plan;
receive a billing request from a transaction server in response to the indication of the user desire, the billing request including a service plan offer associated with the data service; and
transmit a response to the billing request;
wherein the end-user device is in secure network communication with the transaction server via a first network.
2. The system recited in claim 1 , wherein the payment component includes a billing agent of a service processor.
3. The system recited in claim 1 , wherein the payment component includes a billing agent, wherein the billing agent performs one or more of the following: authenticate a request for a central billing transaction session, communicate a transaction authorization request to a user or device ordering function, receive a user or device ordering function response, and report a user or device ordering function authorization of an approved transaction.
4. The system recited in claim 1 , wherein the one or more processors is further configured to:
execute a browser application for communicating with the transaction server, wherein the transaction server is accessible via a website for electronic commerce based transactions, and device information for the end-user device is embedded in a header of a network request sent from the end-user device to the transaction server, and wherein the device information indicates that a central billing option is available to a compatible third party transaction server.
5. The system recited in claim 1 , wherein the one or more processors is further configured to:
execute a browser application for communicating with the transaction server, wherein the transaction server is accessible via a website for electronic commerce based transactions, and a token for the end-user device is embedded in a header of a network request sent from the end-user device to the transaction server to indicate that the end-user device is configured with a payment component, and wherein the device information indicates a central billing option is available to a compatible third party transaction server.
6. The system recited in claim 1 , wherein the one or more processors is further configured to:
execute a browser application for communicating with the transaction server, wherein the transaction server is accessible via a website for electronic commerce based transactions, and a token for the end-user device is embedded in a header of a network request sent from a hypertext transfer protocol (HTTP), wireless application protocol (WAP), or portal browser of the end-user device to the transaction server to indicate that the end-user device is configured with a payment component, and wherein the device information indicates a central billing option is available to a compatible third party transaction server.
7. The system recited in claim 1 , further comprising:
a billing server, wherein the billing server confirms an electronic commerce based transaction between the end-user device and the transaction server.
8. The system recited in claim 1 , wherein the one or more processors is further configured to:
send an embedded token to the transaction server that indicates that the payment component is located on the end-user device.
9. The system recited in claim 1 , wherein the one or more processors is further configured to:
send a billing event to a billing server.
10. The system recited in claim 1 , wherein the one or more processors is further configured to:
send a billing event to the transaction server.
11. The system recited in claim 1 , wherein the one or more processors is further configured to:
acknowledge a request for a transaction billing session.
12. The system recited in claim 1 , wherein the one or more processors is further configured to:
acknowledge a request for a transaction billing session; and
provide a set of credentials.
13. The system recited in claim 1 , wherein the one or more processors is further configured to:
authenticate the transaction server.
14. The system recited in claim 1 , wherein the one or more processors is further configured to:
send an address for a billing assistance server to the transaction server.
15. The system recited in claim 1 , wherein the transaction server is further configured to:
communicate a user or device ordering transaction authorization request to a billing server; and
receive a billing server transaction authorization if approved.
16. The system recited in claim 1 , wherein the one or more processors is further configured to:
receive a record of a completed transaction.
17. The system recited in claim 1 , wherein the one or more processors is further configured to:
transmit a record of a completed transaction.
18. A method, comprising:
transmitting, by an end-user device to a transaction server, an indication of a user desire to use a data service, the data service being outside a current service plan of the end-user device or available at a lower cost within a different service plan;
authenticating a transaction request for a transaction session, the transaction request including a new service plan offer from the transaction server, wherein the end-user device is in communication with the transaction server via a first network;
communicating a transaction-authorization request to a user or device ordering function, the transaction-authorization request based on the transaction request from the transaction server;
receiving authorization of an approved transaction from the user or the device ordering function in response to the transaction-authorization request; and
reporting the authorization of the approved transaction to the transaction server.
19. The method recited in claim 18 , further comprising:
executing a browser application on the processor of the end-user device for communicating with a transaction server, wherein the transaction server is accessible via a website for electronic commerce based transactions, and device information for the end-user device is embedded in a header of a network request sent from the end-user device to the transaction server, and wherein the device information indicates a central billing option is available to a compatible third party transaction server.
20. The method recited in claim 18 , further comprising:
executing a browser application on the processor of the end-user device for communicating with a transaction server, wherein the transaction server is accessible via a website for electronic commerce based transactions, and a token for the end-user device is embedded in a header of a network request sent from an HTTP, WAP, or portal browser of the end-user device to the transaction server to indicate that the end-user device is configured with a payment component, and wherein the device information indicates a central billing option is available to a compatible third party transaction server.
21. The method recited in claim 18 , further comprising:
sending an embedded token from the end-user device to the transaction server that indicates that the payment component is located on the end-user device.
22. The method recited in claim 18 , further comprising:
sending a billing event from the end-user device to a billing server.
23. The method recited in claim 18 , further comprising:
sending a billing event from the end-user device to the transaction server.
24. The method recited in claim 18 , further comprising:
acknowledging a request for a transaction billing session.
25. The method recited in claim 18 , further comprising:
acknowledging a request for a transaction billing session; and
providing a set of credentials.
26. The method recited in claim 18 , further comprising:
authenticating the transaction server.
27. The method recited in 18 , further comprising:
sending an address for a billing assistance server to the transaction server.
28. The method recited in 18 , further comprising:
receiving a record of a completed transaction.
29. The method recited in 18 , further comprising:
transmitting a record of a completed transaction.
30. A computer program product, the computer program product being embodied in a computer readable storage medium and comprising computer instructions for:
transmitting, by an end-user device to a transaction server, an indication of a user desire to use a data service, the data service being outside a current service plan of the end-user device or available at a lower cost within a different service plan;
authenticating a transaction request for a transaction session, the transaction request including a new service plan offer from the transaction server, wherein the end-user device is in communication with the transaction server via a first network;
communicating a transaction-authorization request to a user or device ordering function, the transaction-authorization request based on the transaction request from the transaction server;
receiving authorization of an approved transaction from the user or the device ordering function in response to the transaction-authorization request; and
reporting the authorization of the approved transaction to the transaction server.