Apparatus and method for telecommunications services

• US 6,954,631 B2
• Filed: 02/13/2003
• Issued: 10/11/2005
• Est. Priority Date: 02/13/2003
• 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: Thiebot, Christophe
• Primary Examiner(s): TIEU, BINH KIEN
• Application Number:
  US10/366,072
• Publication Number:
  US 20040162054A1
• Time in Patent Office: 971 Days
• Field of Search: 455/406, 455/408, 455/414.1, 455/418, 455/422.1, 455/424, 455/560, 379/114.2, 379/114.28, 379/114.03
• US Class Current: 455/406
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Abstract

One embodiment disclosed relates to a modular apparatus for telecommunications services. The apparatus includes at least a network interface, a service logic program, and a plug-in module. The network interface exchanges signals with a telephony network, and the service logic program communicates control events with the telephony network by way of the network interface. The plug-in module is configured to exchange in real-time (i) a first type of messages with a charging server and (ii) a second type of messages with the service logic program.

Claims

1. A modular apparatus for telecommunications services, the apparatus comprising:

(a) a network interface for exchanging signals with a telephony network;

(b) a service logic program configured to communicate control events with the telephony network by way of the network interface; and

(c) a plug-in module configured to exchange in real-time (i) a first type of messages with a charging server under a specific billing protocol which is particular to the charging server and (ii) a second type of messages with the service logic program under a message-based interface (MBI) call authorization protocol which is independent of the specific billing protocol.

2. The apparatus of claim 1, wherein the service logic program comprises a prepaid service logic program, and the charging server comprises a prepaid charging server.

3. The apparatus of claim 1, further comprising:

(d) a fault tolerant controller coupled to the service logic program and to the plug-in module.

4. The apparatus of claim 1, wherein the plug-in module comprises a protocol stack for encoding and decoding communications with the service logic program and comprises core layers for communications with the charging server.

5. The apparatus of claim 4, wherein the plug-in module further comprises a management stack for communications with an OAM (operations, administration, and management) service that sends events to the service logic program.

6. A high-availability apparatus for telecommunications services, the apparatus comprising:

(a) a first network interface for exchanging signals with a telephony network;

(b) a first service logic program configured to communicate control events with the telephony network by way of the first network interface;

(c) a first plug-in module configured to exchange in real-time (i) a first type of messages with a charging server and (ii) a second type of messages with the first service logic program;

(d) a first fault tolerant controller coupled to the first service logic program and to the first plug-in module;

(e) a second network interface for exchanging signals with the telephony network;

(f) a second service logic program configured to communicate control events with the telephony network by way of the second network interface;

(g) a second plug-in module configured to exchange in real-time (i) the first type of messages with the charging server and (ii) the second type of messages with the second service logic program; and

(h) a second fault tolerant controller coupled to the second service logic program and the second plug-in module,

wherein a first service execution platform comprises the first network interface, the first service logic program, the first plug-in module, and the first fault tolerant controller,

wherein a second service execution platform comprises the second network interface, the second service logic program, the second plug-in module, and the second fault tolerant controller, and

wherein the first and second fault tolerant controllers are in communication such that the first and second service execution platforms may be individually activated to provide redundancy.

7. A method for telecommunications services, the method comprising:

exchanging signals between a service logic program and a telephony network;

exchanging in real-time a first type of messages between a module and a charging server under a specific billing Protocol that is particular to the charging server; and

exchanging in real-time a second type of messages between the module and the service logic program under a message-based interface (MBI) call authorization protocol that is independent of the specific billing protocol.

8. The method of claim 7, wherein the service logic program comprises a prepaid service logic program, and the charging server comprises a prepaid charging server.

9. The method of claim 7, further comprising:

sending an MBI authorize message from the service logic program to the module in response to the service logic program receiving a start of call event from the telephony network;

returning an MBI authorize confirm message from the module to the service logic program and upon the module receiving affirmative authorization from the charging server; and

returning an MBI authorize reject message from the module to the service logic program upon the module receiving a negative authorization response from the charging server.

10. The method of claim 7, further comprising:

sending an MBI announcement message from the module to the service logic program upon receipt of a play a message command from the charging server; and

returning an MBI announcement confirm message from the service logic program once the announcement is relayed to the telephony network.

11. The method of claim 7, further comprising:

sending an MBI re-authorize message from the service logic program to the module; and

returning an MBI authorize confirm message from the module to the service logic program upon the module successfully completing credit reservation with the charging server.

12. The method of claim 7, further comprising:

sending an MBI end message from the service logic program to the module upon receipt of an end of call event from the telephony network; and

returning an MBI end acknowledge message from the module to the service logic program after final debit communications between the module and the charging server.

13. The method of claim 7, further comprising:

sending an MBI startup message from the service logic program to the module upon service startup;

returning an MBI startup confirm message from the module to the service logic program upon a successful handshake between the module and the charging server; and

returning an MBI startup reject message from the module to the service logic program upon an unsuccessful handshake between the module and the charging server.

14. The method of claim 7, further comprising:

sending an MA query message from the from the service logic program to the module; and

returning an MA notify message from the module to the service logic program.

15. The method of claim 7, further comprising:

sending an MBI shutdown message from the service logic program to the module at service shutdown;

returning an MBI shutdown confirm message from the module to the service logic program upon a successful “

good-bye”

type exchange between the module and the charging server; and

returning an MBI shutdown reject message from the module to the service logic program upon an unsuccessful “

good-bye”

type exchange between the module and the charging server.

16. The method of claim 7, further comprising:

sending an MBI authorize reject message from the module to the service logic program upon receiving a call termination request from the charging server;

transmitting a release call event from service logic program to the telephony network; and

returning an MBE end message from the service logic program to the module.

17. The method of claim 7, further comprising:

sending en MBI end acknowledge message from the module to the service logic program after a final debit is processed with the charging server.

18. The method of claim 7, further comprising:

receiving a heart beat request by the module from the charging server; and

returning a heart beat response from the module to the charging server.

19. The method of claim 7, further comprising:

sending an MBI balance message from the service logic program to the module; and

returning an MBI balance confirm message from the module to the service logic program upon the module receiving an affirmative message from the charging server pertaining to account credit balance.

20. The method of claim 7, further comprising:

sending an MBI voucher message from the service logic program to the module; and

returning an MBI voucher confirm message from the module to the service logic program upon the module receiving an affirmative message from the charging server pertaining to account recharging.

21. A system for telecommunications services, the system comprising:

means for exchanging signals between a service logic program and a telephony network;

means for exchanging in real-time a first type of messages between a module and a charging server under a specific billing protocol that is particular to the charging server; and

means for exchanging in real-time a second type of messages between the module and the service logic program under a real-time call authorization protocol that is independent of the specific billing protocol.

22. A scalable apparatus for telecommunications services, the apparatus comprising:

a service logic program configured to communicate control events with a telephony network by way of a network interface; and

a plurality of plug-in modules configured to exchange in real-time (i) a first type of messages with a charging server under a specific billing protocol that is particular to the charging server and (ii) a second type of messages with the service logic program under a real-time call authorization protocol that is independent of the specific billing protocol,

wherein links to the charging server are creatable and deletable by way of activating and deactivating the plug-in modules such that bandwidth to the charging server is scalable.