Call conversion process for a business system for a global telecommunications network

• US 6,134,307 A
• Filed: 09/21/1998
• Issued: 10/17/2000
• Est. Priority Date: 09/21/1998
• Status: Expired due to Term

• Current Assignee: Iridium Satellite Llc (Iridium Communications, Incorporated)
• Original Assignee: Iridium IP, LLC
• Inventors: Cleary, John Gardner, Brouckman, Randall W., Hakl, Shawn Paul, Curran, Cheryl Marie
• Primary Examiner(s): Kuntz, Curtis A.
• Assistant Examiner(s): Barnie, Rexford N
• Application Number:
  US09/157,656
• Time in Patent Office: 757 Days
• Field of Search: 379/13, 379/115, 379/116, 379/119, 379/120, 379/220, 379/222, 379/229, 379/230, 379/121, 455/405, 455/406, 455/455, 455/456, 455/450, 455/432, 455/433, 455/436, 455/408
• US Class Current: 379/115.03
• 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/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/49 Connection to several service providers
• CPC Class Codes: H04M 15/50 for cross-charging network operators
• CPC Class Codes: H04M 15/53 using mediation
• CPC Class Codes: H04M 2215/0172 Mediation, i.e. device or program to reformat CDRS from one or more switches in order to adapt to one or more billing programs formats
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/46 Connection to several service providers
• CPC Class Codes: H04M 2215/52 Interconnection, inter-exchange, reseller billing, billing agreements between different operators, e.g. billing identifier added on the CDR in order to cross charge the other operator, inter-operator accounting, reconciliation, bill directly resellers customers
• CPC Class Codes: H04M 2215/96 Distributed calculation of charges, e.g. in different nodes like for mobiles between HLR and VLR, or between the terminal and the billing function

Abstract

The present invention provides a method for converting call events. The method includes receiving a plurality of call events from a plurality of sources in a global telecommunications network; converting the plurality of call events a plurality of call event records, the call event records having different destinations; sending a first portion of the plurality of call event records to a first destination; and sending a second portion of the plurality of call event records to a second destination. The method of the present invention allows for different types of billing information to be sent to different entities around the world in a global telecommunications network. It ensures that the correct information is eventually routed to the correct entity, so that proper billing can be performed.

Claims

1. A method for converting call events, comprising the steps of:

(a) receiving a plurality of call events from a plurality of sources in a global telecommunications network;

(b) converting the plurality of call events into a plurality of call event records, the call event records having different destinations wherein the types of call event records comprise valid records, original call detail records, invalid records, and event records, wherein the valid records, the invalid records, and the original call detail records are sent to the first destination, wherein the event records are sent to the second destination;

(c) sending a first portion of the plurality of call event records to a first destination; and

(d) sending a second portion of the plurality of call event records to a second destination, wherein a plurality of final destinations for the event records comprise;

sending a first portion of the event records to a home gateway,

sending a second portion of the event records to a plurality of gateways involved in handling a portion of a call,

sending a third portion of the event records to a settlements repository, and sending a fourth portion of the event records to a plurality of gateways involved with handling of a call and settling with a roaming partner.

2. The method of claim 1, wherein the first destination is a plurality of repositories comprising a usage repository, an error repository, and an original call detail record directory.

3. The method of claim 1, wherein the second destination is a plurality of subsequent processes, the subsequent processes comprising a settlements process and a distribution process.

4. The method of claim 1, wherein

valid records are sent to a usage repository,

invalid records are sent to an error repository, and

original call detail records are sent to an original call detail record directory.

5. A method for converting call events, comprising the steps of:

(a) receiving a plurality of call events from a plurality of sources in a global telecommunications network;

(b) converting the plurality of call events into a plurality of call event records, the call event records having different destinations wherein the types of call event records comprise valid records, original call detail records, invalid records, and event records, wherein the valid records, the invalid records, and the original call detail records are sent to the plurality of repositories, wherein the event records are sent to the plurality of subsequent processes;

(c) sending a first portion of the plurality of call event records to a plurality of repositories;

(d) sending a second portion of the plurality of call event records to a plurality of subsequent processes, wherein a plurality of final destinations for the event records comprise;

sending a first portion of the event records to a home gateway,

sending a second portion of the event records to a plurality of gateways involved in handling a portion of a call,

sending a third portion of the event records to a settlements repository, and

sending a fourth portion of the event records to a plurality of gateways involved with handling of a call and settling with a roaming partner.

6. The method of claim 5, wherein

valid records are sent to a usage repository,

invalid records are sent to an error repository, and

original call detail records are sent to an original call detail record directory.

7. A method for converting call events, comprising the steps of:

(a) receiving a plurality of call events from a plurality of sources in a global telecommunications network;

(b) converting the plurality of call events into a plurality of call event records, the call event records having different destinations, wherein the types of call event records comprise valid records, original call detail records, invalid records, and event records;

(c) grouping the plurality of call event records according to their final destinations;

(d) populating a plurality of repositories with valid records, the invalid records, and the original call detail records, wherein

valid records are sent to a usage repository,

invalid records are sent to an error repository, and

original call detail records are sent to an original call detail record directory; and

(e) releasing to a plurality of subsequent processes a second portion of the plurality of call event records, wherein a plurality of final destinations for the event records comprise

sending a first portion of the event records to a home gateway,

sending a second portion of the event records to a plurality of gateways involved in handling a portion of a call,

sending a third portion of the event records to a settlements repository, and

sending a fourth portion of the event records to a plurality of gateways involved with handling of a call and settling with a roaming partner.

8. A computer readable medium with computer instructions for converting call events, comprising instructions for:

(a) receiving a plurality of call events from a plurality of sources in a global telecommunications network;

(b) converting the plurality of call events into a plurality of call event records, the call event records having different destinations wherein the types of call event records comprise valid records, original call detail records, invalid records, and event records, wherein the valid records, the invalid records, and the original call detail records are sent to the first destination, wherein the vent records are sent to the second destination;

(c) sending a first portion of the plurality of call event records to a first destination; and

(d) sending a second portion of the plurality of call event records to a second destination, wherein a plurality of final destinations for the event records comprise;

sending a first portion of the event records to a home gateway,

sending a second portion of the event records to a plurality of gateways involved in handling a portion of a call,

sending a third portion of the event records to a settlements repository, and sending a fourth portion of the event records to a plurality of gateways involved with handling of a call and settling with a roaming partner.