Conference billing system with ID tagging

• US 5,844,973 A
• Filed: 06/29/1995
• Issued: 12/01/1998
• Est. Priority Date: 06/29/1995
• Status: Expired due to Term

• Current Assignee: Florescere Assets LLC (Intellectual Ventures LLC)
• Original Assignee: MCI Communications Corporation (Verizon Communications Inc.)
• Inventors: Venkatraman, Arunachalam, DeVries, Larry Ray, Gottlieb, Louis G.
• Primary Examiner(s): Shankar, Vijay
• Application Number:
  US08/496,619
• Time in Patent Office: 1,251 Days
• Field of Search: 379/112, 379/113, 379/114, 379/116, 379/118, 379/119, 379/127, 379/142, 379/201, 379/202, 379/204, 379/206
• US Class Current: 379/127.05
• 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/12 Discriminative metering , charging or billing
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/44 Augmented, consolidated or itemized billing statement or bill presentation
• CPC Class Codes: H04M 2203/5054 Meet-me conference, i.e. participants dial-in
• CPC Class Codes: H04M 2203/5063 Centrally initiated conference, i.e. conference server dials participants
• CPC Class Codes: H04M 3/56 Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15

Abstract

A conference billing system with ID tagging allocates charges for a conference based on a prior reservation. The billing system also supports different tariffs and pricing structures for individual call legs in the conference, such as audio, video, digital data, or mixed. In addition, the billing system prepares a consolidated bill for dial-in and dial-out calls based on a unique ID assigned to each conference. The bill contains the description of the conference with its individual call legs grouped together for easy identification and verification by the customer, even though the individual call legs of the conference may be serviced by different long distance switching offices.

Claims

1. In a telecommunications network, a system for processing billing information of a conference of calls carried on said telecommunications network, comprising:

reservation means for using information provided by a conference leader to generate a file referencing said conference, said file including an identifier for said conference;

switch means, in receipt of a dial-in call for said conference during call setup of said conference, for querying a database to retrieve routing information therefrom for routing said dial-in call, said dial-in call being tagged with said identifier;

a conference bridge for connecting said dial-in call to said conference in response to the routing thereof by said switch means, a call record that includes said identifier being generated by said switch means; and

processing means for using said identifier to create a billing record for said dial-in call, group said dial-in call with calls of said conference, and print an invoice to be provided to at least one party identified to be responsible for charges incurred for said conference.

2. The system of claim 1, wherein said switch means generates said call record after said dial-in call is completed, said identifier of said call record identifying said call as relating to said conference.

3. The system of claim 1, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said call being an audio call.

4. The system of claim 1, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said call being a video call.

5. The system of claim 1, wherein said processing means comprises a traffic processor and a billing processor, said traffic processor establishing a billing option for each call of said conference based on said information provided by said conference leader, said billing option designating said at least one party responsible for paying charges for said each call.

6. The system of claim 1, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said billing processor

(a) merges said conference file with said call record for each said calls of said conference and determines a charge for said each call;

(b) merges said conference file with a feature record for said each call and determines a charge for said each call;

(c) groups all calls pertaining to said conference; and

(d) prints said invoice for said conference.

7. The system of claim 1, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said billing processor

(a) generates sub-headings for said invoice; and

(b) sorts information in each customer'"'"'s record according to said sub-headings.

8. The system of claim 1, wherein said conference bridge is configured for routing dial-in calls to said conference by data in said file generated by said reservation system.

9. In a telecommunications network, a system for processing billing information of a conference of calls carried on said telecommunications network, comprising:

reservation means for using information provided by a conference leader to generate a file referencing said conference, said file including an identifier for said conference;

a conference bridge for receiving said identifier;

switch means, in receipt of a dial-out call from said conference, for retrieving from said conference bridge said identifier and tagging said dial-out call with said identifier during call setup, said switch means generating a call record that includes said identifier; and

processing means connected to said reservation means and said switch means for using said identifier to create a billing record for said dial-out call, group said dial-out call with calls of said conference, and print an invoice to be provided to at least one party identified to be responsible for charges incurred for said conference.

10. The system of claim 9, wherein said switch means generates said call record after said dial-out call is completed, said identifier of said call record identifying said call as relating to said conference.

11. The system of claim 9, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said call being an audio call.

12. The system of claim 9, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said call being a video call.

13. The system of claim 9, wherein said processing means comprises a traffic processor and a billing processor, said traffic processor establishing a billing option for each call of said conference based on said information provided by said conference leader, said billing option designating said at least one party responsible for paying charges for said each call.

14. The system of claim 9, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said billing processor

(a) merges said conference file with said call record for each said calls of said conference and determines a charge for said each call;

(b) merges said conference file with a feature record for said each call and determines a charge for said each call;

(c) groups all calls pertaining to said conference; and

(d) prints said invoice for said conference.

15. The system of claim 9, wherein said processing means comprises a traffic processor and a billing processor;

and

wherein said billing processor

(a) generates sub-headings for said invoice; and

(b) sorts information in each customer'"'"'s record according to said sub-headings.

16. The system of claim 9, wherein said conference bridge is configured for routing dial-out calls from said conference by data in said file generated by said reservation system.

17. A method of processing billing information for a conference of calls carried on a telecommunications network, comprising the steps of:

(a) generating a file relating to said conference based on information provided by a conference leader;

(b) assigning an identifier to each call of said conference during a call setup;

(c) creating a call record for said each call upon its completion;

(d) using said identifier for processing billing information for said conference including generating a billing record for said each call, grouping said each call with other calls of said conference, and printing an invoice to be provided to at least one party identified to be responsible for charges incurred for said conference.

18. The method of claim 17, wherein the generating of said billing record in said step d further comprises the steps of:

merging said conference file with the call record of said each call;

determining a charge for said each call of said conference;

merging said conference file with a feature record for said each call; and

determining a charge for said each call of said conference.

19. The method of claim 18, wherein said step d further comprises the steps of:

establishing a billing option for said each call of said conference based on said information provided by said conference leader; and

using said billing option to determine said at least one party responsible for paying charges for said each call.

20. The method of claim 18, wherein said step d further comprises the steps of:

generating sub-headings for said invoice; and

sorting information in said record for said each call according to said sub-headings.