Open transaction central billing system

• US 20100191613A1
• Filed: 03/02/2009
• Published: 07/29/2010
• Est. Priority Date: 01/28/2009
• Status: Active Grant

• Current Assignee: ItsOn, Inc.
• Original Assignee: Greg Raleigh
• Inventors: Raleigh, Gregory G.
• Granted Patent: US 8,229,812 B2
• Time in Patent Office: Days
• US Class Current: 705/26.1
• CPC Class Codes: G06F 15/177 Initialisation or configuration control processor initialisation G06F9/4405
• CPC Class Codes: G06Q 10/06315 Needs-based resource requirements planning or analysis
• CPC Class Codes: G06Q 10/06375 Prediction of business process outcome or impact based on a proposed change
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• CPC Class Codes: G06Q 20/32 using wireless devices
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 30/0207 Discounts or incentives, e.g. coupons or rebates
• CPC Class Codes: G06Q 30/0241 Advertisements
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/0284 Time or distance, e.g. usage of parking meters or taximeters
• CPC Class Codes: G06Q 30/04 Billing or invoicing
• CPC Class Codes: G06Q 30/0601 Electronic shopping [e-shopping]
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/12 Accounting
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 12/1407 Policy-and-charging control [PCC] architecture
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0876 Aspects of the degree of configuration automation
• CPC Class Codes: H04L 41/0893 Assignment of logical groups to network elements
• CPC Class Codes: H04L 41/0894 : Policy-based network configuration management
• CPC Class Codes: H04L 41/5003 : Managing SLA; Interaction between SLA and QoS
• CPC Class Codes: H04L 41/5025 : by proactively reacting to service quality change, e.g. by reconfiguration after service quality degradation or upgrade
• CPC Class Codes: H04L 41/5054 : Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 47/20 : Traffic policing
• CPC Class Codes: H04L 47/2408 : for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 51/046 : Interoperability with other network applications or services
• CPC Class Codes: H04L 63/0236 : Filtering by address, protocol, port number or service, e.g. IP-address or URL
• CPC Class Codes: H04L 63/04 : for providing a confidential data exchange among entities communicating through data packet networks
• CPC Class Codes: H04L 63/0428 : wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/08 : for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0853 : using an additional device, e.g. smartcard, SIM or a different communication terminal cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234
• CPC Class Codes: H04L 63/0892 : by using authentication-authorization-accounting [AAA] servers or protocols
• CPC Class Codes: H04L 63/10 : for controlling access to devices or network resources
• CPC Class Codes: H04L 63/20 : for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 67/145 : avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 67/306 : User profiles
• CPC Class Codes: H04L 67/34 : involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/51 : Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/55 : Push-based network services
• CPC Class Codes: H04L 67/564 : Enhancement of application control based on intercepted application data
• CPC Class Codes: H04L 67/63 : Routing a service request depending on the request content or context
• CPC Class Codes: H04L 9/32 : including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04M 15/00 : Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/49 : Connection to several service providers
• CPC Class Codes: H04M 15/58 : based on statistics of usage or network monitoring
• CPC Class Codes: H04M 15/61 : based on the service used
• CPC Class Codes: H04M 15/66 : Policy and charging system
• CPC Class Codes: H04M 15/80 : Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8055 : Selecting cheaper transport technology for a given service
• CPC Class Codes: H04M 15/88 : Provision for limiting connection, or expenditure
• CPC Class Codes: H04M 2215/0188 : Network monitoring; statistics on usage on called/calling number
• CPC Class Codes: H04W 12/00 : Security arrangements; Authentication; Protecting privacy or anonymity
• CPC Class Codes: H04W 12/02 : Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/037 : of the control plane, e.g. signalling traffic
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/08 : Access security
• CPC Class Codes: H04W 12/37 : Managing security policies for mobile devices or for controlling mobile applications
• CPC Class Codes: H04W 24/08 : Testing, supervising or monitoring using real traffic
• CPC Class Codes: H04W 28/02 : Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0215 : based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0268 : using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 28/12 : using signalling between network elements
• CPC Class Codes: H04W 4/02 : Services making use of location information
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/18 : Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 4/20 : Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/24 : Accounting or billing
• CPC Class Codes: H04W 4/50 : Service provisioning or reconfiguring
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 8/02 : Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
• CPC Class Codes: H04W 8/18 : Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 8/20 : Transfer of user or subscriber data
• CPC Class Codes: H04W 84/04 : Large scale networks; Deep hierarchical networks
• CPC Class Codes: H04W 84/042 : Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: Y02P 90/80 : Management or planning

Abstract

Various embodiments are disclosed for a services policy communication system and method. In some embodiments, an open transaction central billing system includes a communications device, in which the communications device is configured to execute a payment component to accept a billing request from a transaction server; and a transaction server, in which the transaction server is programmed with a set of credentials, and the communications device is in network communication with the transaction server.

Claims

1. A system, comprising:

a communications device, wherein the communications device is configured to execute a payment component to accept a billing request from a transaction server; and

a transaction server, wherein the transaction server is programmed with a set of credentials, and wherein the communications device is in 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 communications device 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 communications device is embedded in a header of a network request sent from the communications 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 communications device 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 communications device is embedded in a header of a network request sent from the communications device to the transaction server to indicate that the communications 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 communications device 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 communications device is embedded in a header of a network request sent from an HTTP, WAP, or portal browser of the communications device to the transaction server to indicate that the communications 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 communications device and the transaction server.

8. The system recited in claim 1, wherein the communications device is further configured to:

send an embedded token to the transaction server that indicates that the payment component is located on the communications device.

9. The system recited in claim 1, wherein the communications device is further configured to:

send a billing event to a billing server.

10. The system recited in claim 1, wherein the communications device is further configured to:

send a billing event to the transaction server.

11. The system recited in claim 1, wherein the communications device is further configured to:

acknowledge a request for a transaction billing session.

12. The system recited in claim 1, wherein the communications device 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 communications device is further configured to:

authenticate the transaction server.

14. The system recited in claim 1, wherein the communications device 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 communications device is further configured to:

receive a record of a completed transaction.

17. The system recited in claim 1, wherein the communications device is further configured to:

transmit a record of a completed transaction.

18. A method, comprising:

authenticating a request for a central billing transaction session using a processor of a communications device, wherein the communications device is in communication with a transaction server via a first network;

communicating a transaction authorization request to a user or device ordering function;

receiving a user or device ordering function response; and

reporting a user or device ordering function authorization of an approved transaction.

19. The method recited in claim 18, further comprising:

executing a browser application on the processor of the communications 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 communications device is embedded in a header of a network request sent from the communications 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 communications 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 communications device is embedded in a header of a network request sent from an HTTP, WAP, or portal browser of the communications device to the transaction server to indicate that the communications 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 communications device to the transaction server that indicates that the payment component is located on the communications device.

22. The method recited in claim 18, further comprising:

sending a billing event from the communications device to a billing server.

23. The method recited in claim 18, further comprising:

sending a billing event from the communications 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:

authenticating a request for a central billing transaction session, wherein the communications device is in communication with a transaction server via a first network;

communicating a transaction authorization request to a user or device ordering function;

receiving a user or device ordering function response; and

reporting a user or device ordering function authorization of an approved transaction.