Communication methods and systems

• US 8,219,449 B2
• Filed: 11/13/2008
• Issued: 07/10/2012
• Est. Priority Date: 11/15/2007
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett-Packard Development Company, L.P. (HP Inc.)
• Inventors: Bertin, Olivier, Desiderio, Didier
• Primary Examiner(s): Champagne, Luna
• Application Number:
  US12/270,342
• Publication Number:
  US 20090132397A1
• Time in Patent Office: 1,335 Days
• Field of Search: None
• US Class Current: 705/16
• CPC Class Codes: G06Q 20/20 Point-of-sale [POS] network systems
• 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/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion

Abstract

A system arranged to receive an authorization request from an application server using a first communication protocol; identify a charging server associated with the authorization request from a plurality of charging servers, each charging server associated with a respective charging server communication protocol; and communicate with the identified charging server using the respective charging server communication protocol.

Claims

1. A system comprising:

a charging gateway comprising a generic interface to an applications server such that the applications server communicates with the charging gateway using a common protocol independent of a charging server being communicated with, including executable instructions to;

receive directly from a user agent, through the applications server, an authorization request;

identify a charging server associated with the authorization request from a plurality of charging servers implementing a plurality of charging server communication protocols based upon information contained in the authorization request, each of the plurality of charging servers associated with a respective one of the plurality of charging server communication protocols;

select an associated one of a plurality of modules included in the charging gateway based on the identified charging server;

translate, by the associated module selected, communications between the common protocol and the respective charging server communication protocol; and

communicate, using the respective charging server communication protocol, to obtain request information from the identified charging server.

2. A system as claimed in claim 1, wherein the executable instructions are configured such that a charging server is identified implicitly by communications received to the charging gateway from the applications server being for only one particular module.

3. A system as claimed in claim 2, wherein the executable instructions are configured such that the associated one of a plurality of modules is selected in the charging gateway by the applications server.

4. A system as claimed in claim 2, wherein each of the plurality of modules comprises a Java bean.

5. A system as claimed in claim 4, wherein the authorization request is provided in Remote Method Invocation.

6. A system comprising:

a charging gateway comprising a generic interface to an applications server such that the applications server communicates with the charging gateway using a common protocol independent of a charging server being communicated with, including executable instructions to;

receive directly from a user agent, through the applications server, a service request;

identify a particular charging server, from a plurality of charging servers implementing a plurality of charging server communication protocols, associated with at least one of the user agent and a user using the user agent, wherein the charging server is identified based upon information contained in the service request;

receive an authorization request at the charging gateway such that the charging gateway communicates with the identified charging server using a respective one of the plurality of charging server communication protocols associated with the identified charging server;

select a module associated with the identified particular charging server from modules included in the charging gateway; and

translate, by the associated module selected, communications between the common protocol and the respective charging server communication protocol,

wherein the respective charging server communication protocol is selected based upon information contained in the service request.

7. A system as claimed in claim 6, arranged to provide the authorization request to the associated module selected such that the associated module selected communicates with the identified charging server using the respective charging server communication protocol associated with the identified charging server.

8. A system as claimed in claim 7, wherein the modules comprise Java beans.

9. A system as claimed in claim 8, wherein the service request is provided in Remote Method Invocation.

10. A system as claimed in claim 6, arranged to receive an authorization response from the charging gateway.

11. A system as claimed in claim 10, arranged to selectively provide content or a service identified in the user request based on the authorization response.

12. A communication method comprising:

receiving, at a charging gateway, directly from a user agent, through an applications server, an authorization request;

identifying, by the charging gateway, a charging server associated with the authorization request from a plurality of charging servers implementing a plurality of charging server communication protocols based upon information contained in the authorization request, each charging server associated with a respective one of the plurality of charging server communication protocols;

selecting a module from among a plurality of modules included in the charging gateway based on the identified charging server;

translating, by the selected module, communications between a common protocol used between the applications server and the charging gateway and the respective charging server communication protocol; and

communicating, by the charging gateway, with the identified charging server using the respective charging server communication protocol, to obtain request information from the identified charging server.

13. A method as claimed in claim 12, wherein identifying the charging server comprises identifying the module associated with the identified respective charging server.

14. A method as claimed in claim 13, wherein communicating with the identified charging server comprises the identified module communicating with the identified charging server using the respective charging server communication protocol.

15. A method as claimed in claim 12, wherein the plurality of modules comprise a plurality of Java beans.

16. A system as claimed in claim 15, wherein the authorization request is provided in Remote Method Invocation.

17. A communication method comprising:

receiving, at a charging gateway, directly from a user agent, through an applications server, a service request;

identifying, by the charging gateway, a charging server, from a plurality of charging servers implementing a plurality of charging server communication protocols, associated with at least one of the user agent and a user using the user agent, wherein the charging server is identified based upon information contained in the service request;

receiving an authorization request at the charging gateway;

selecting a module from among a plurality of modules included in the charging gateway based on the identified charging server;

translating, by the selected module, communications between a common protocol used between the applications server and the charging gateway and a respective one of the charging server communication protocols associated with the identified charging server; and

communicating, by the charging gateway, with the identified charging server using the respective charging server communication protocol associated with the identified charging server.

18. A method as claimed in claim 17, wherein charging server is identified implicitly by communications received to the charging gateway from the applications server being for only one module.

19. A method as claimed in claim 18, wherein the modules comprise Java beans.

20. A method as claimed in claim 19, wherein the service request is provided in Remote Method Invocation.

21. A method as claimed in claim 17, further comprising receiving an authorization response from the charging gateway.

22. A method as claimed in claim 21, further comprising selectively providing content or a service identified in the service request based on the authorization response.

23. A non-transitory computer-readable medium having computer-readable instructions stored thereon that, if executed by one or more processors cause the one or more processors to:

receive, at a charging gateway, directly from a user agent, through an applications server, an authorization request;

identify, by the charging gateway, a charging server associated with the authorization request from a plurality of charging servers implementing a plurality of charging server communication protocols based upon information contained in the authorization request, each charging server associated with a respective one of the plurality of charging server communication protocols used to communicate between the charging gateway and the identified charging server;

select a module from among a plurality of modules included in the charging gateway based on the identified charging server;

translate, by the selected module, communications between a common protocol used between the applications server and the charging gateway and the respective charging server communication protocol associated with the identified charging server; and

communicate, using the respective charging server communication protocol associated with the identified charging server, to obtain request information from the identified charging server.

24. The non-transitory computer-readable medium as claimed in claim 23, wherein the computer-readable instructions to identify the charging server includes executable instructions to identify a module associated with the identified charging server.

25. The non-transitory computer-readable medium as claimed in claim 23, wherein the computer-readable instructions to communicate, by the identified module, with the identified charging server using the respective charging server communication protocol associated with the identified charging server.