WO2001060045A2

WO2001060045A2 - Flexible call billing method

Info

Publication number: WO2001060045A2
Application number: PCT/DE2001/000526
Authority: WO
Inventors: Markus HÖHFELD; Mady Jansen
Original assignee: Siemens Aktiengesellschaft
Priority date: 2000-02-10
Filing date: 2001-02-12
Publication date: 2001-08-16
Also published as: WO2001060045A3

Abstract

The invention relates to a method for parallelly billing prepaid customers involving the following steps: 1) both accounts of the subscriber are maintained in a database (SCP); 2) during call set-up, the selection logic is run through which, according to the specific feature, determines the account to be used; 3) money for a first time slice and for the warning period is reserved on the selected account; 3a) the money is reserved firstly on the selected account. If there is not a sufficient amount of money in the selected account in order to guarantee the call billing of the time slice, the missing remainder is reserved on the other account in the case of overrun (3/4). At the end of the time slice, the actual accrued connection costs are compiled. If the call is terminated by the subscriber during the time slice, or if no additional amount of money can no longer be reserved (forced release), the accumulated costs are debited from the account; 5) otherwise the call is continually billed time slice by time slice; 6) once the call has been terminated, the costs accumulated in the buffer memories are debited from the accounts, and; 7) reserved amounts of money that have not been used are returned so that the money is available for other calls.

Description

description

Procedure for flexible billing

Field of the Invention

Prepaid systems are increasingly being used to charge for telephone calls. The fees incurred on ^¬ line be deducted from the account. During the conversation, the account balance is checked online and the conversation is carried out by

System exits after playing a warning tone if the account runs empty. Prepaid systems are "intelligent example of the additional technology networks * m telephone networks reali ^¬ Siert.

State of the art

The following procedures exist, but each of them solve some of the technical problems:

• Prepaid with one account per user.

• Limited implementation of a prepaid procedure with 2 accounts. No parallel calls can be made with this procedure. Call forwarding must therefore also be activated, ie this service is not available to the user, which means a significant restriction. Furthermore, the account selection cannot be changed during the call, but the selection is made only once when the call is set up by ¹ . This contradicts the usual tariff rate; ι b, m who ublιcher _Λ eιse cer is required (and implemented) to switch to the current tariff in the case of time-dependent billing.

• In addition, the use of 2 prepaid accounts is only now becoming increasingly interesting due to the introduction of CAMEL in mobile communications. Because CAMEL enables roammg of prepaid participants and thus implies the payment of incoming calls abroad (MTC leg). This results in new application options and operator requirements for innovative charging concepts.

The object of the invention is to provide a flexible billing concept.

The object of the invention is also to provide billing concepts for prepaid billing with 2 and more prepaid accounts. 0

Presentation of the invention

The invention consists in a computer-aided method5 with which the problems of online charging are applied to several

Accounts will be drawn. The method can be applied to an IN system. It can be used in combination with other IN-based methods. C The procedure solves the technical problems by the following steps:

1. Both (all) accounts of the subscriber are managed in a database, in an IN, for example, based on the IN terminology in the SCP (Service Control Point). 5 2. When the call is set up, the selection logic is run through, which, depending on the particular specification, determines the indications 1 (account 1), 2 (account 2) 3 (account 2 with overflow to 1) and 4 (account 1 with overflow to 2). 3. Money is reserved in the selected account for a first time slice and the warning period. This reservation ensures that parallel calls do not "telephone the same money". 3a The reservation is initially made on the selected one

Account (account 1 for 1/3, account 2 for 2/3). If there is not enough money to pay the

To guarantee time slice, in the event of overflow (3/4), the missing remainder on the other account reserved. Possibly. not enough money can be reserved to charge the entire time slice. Then at least the remaining balance of the selected account and overflow is reserved. 4. The call is connected, for a maximum of the duration guaranteed by the reservation.

• At the end of the time slice, the connection costs actually incurred (these can differ from the reservations) are collected in 4 intermediate stores ZI, Z2, Z3, Z4

• If the call is ended by the subscriber during the time slice or no more money can be reserved (forced release), the accrued costs will be debited from the account (point 6). 5. Otherwise the call will continue to be made on a slice basis. For every time slice

• the selection logic is run through again.

• Money is reserved in the selected account.

• Are the connection costs actually incurred m accumulated in the buffer stores

• It is checked whether the subscriber has ended the call or the call must be ended by the system (forced release) (point 6)

6. Only after the call has ended are the costs incurred in the intermediate stores deducted from the accounts.

7. Unused reservations are returned so that the money is available for other calls.

In the method according to the invention, it is important to carry out the charging only after the end of the call in order to ensure the consistency between tickets and online charging. It is therefore important to accumulate the accumulated costs in four buffers and not to distribute them directly to the accounts in the time slice. This procedure correctly reserves reservations for parallel calls that are released and deposits during a (long) call. By clearly separating the selection logic, different variants of the process can be generated quickly and flexibly.

The combination of 2 (or more) prepaid accounts and charging for parallel calls is new. The possibility of re-evaluating the selection criterion during the call is also new. The combination of the methods is technically complex (given the design options for IN-based services) and leads to the technical solution using 4 buffers.

The invention therefore consists in a method which extends prepaid services by flexible, innovative charging concepts and which is characterized by the following properties

1. The billing is done online with a review of the

Account balance when establishing a connection, monitoring the connection and playing a warning tone before the system-mediated connection end due to insufficient funds in the account.

2. Two different user accounts can be used for billing.

3. The selection of the account on which the payment is to be made is implemented by an independent selection logic.

Examples are time-dependent selection (weekend talk go to account 2), target-dependent selection (connections to friends go to account 2), ....

4. An overflow mechanism can also be activated in the selection logic. If the selected account does not have sufficient cover, the other account is automatically called.

5. The selection criteria can change during the conversation, e.g. with time-dependent selection. 6. Several simultaneous calls can be made.

Simultaneous calls arise, for example, when the call is forwarded, when an outgoing call and the forwarded incoming one Reputation must be charged. They also arise due to the fact that one can dial in to any account from any telephone to charge the following call online to his own account. 7. The procedure can be combined with all others

(Known) extensions for prepaid services, such as B. origin-dependent billing (mobile local call, home zone), Screenmg-Mechamsmen, ....

This procedure makes it technically possible to set up a bonus account. Depending on the turnover, the user receives a bonus, which, however, can only be called by phone at limited times. This procedure can also be used to implement a MTC bonus that is of interest to mobile communications: for every incoming call, the mobile subscriber receives a bonus that is primarily used to cover the costs of incoming calls in the case of Roammg. (If a mobile phone prepaid subscriber is abroad, costs for the share of the connection from the HPLMN to the VPLMN apply to him).

This procedure makes it possible to maintain separate accounts for incoming and outgoing calls for prepaid subscribers in order to increase the transparency of the costs incurred or to enable user-defined cost controlling for incoming and / or outgoing calls ,

Many other approaches to using 2 accounts and any combination are possible.

Description of the preferred embodiments

The figures show as follows: Figure 1 "Call account confirmation period * Figure 2" SubFSL ("Flexible Service Logic"; account determination Figure 3a, 3b "Tanfermittung") Figure 4 "Is there an MLC call?"

Figure 5 ^w tariff model "

Figure 6a, 6b "Reserve the first amount of money

FIG. 7 "Calculating the available amount of money" FIG. 8 "Checking for insufficient amount of money ^*

FIG. 9 "Checking the available amount of money"

Figure 10 "Release the reserved amount of money ^*

Figure 11 "Call setup messages for the second account *

Figure 12 "Checking the available time" Figure 13 "Checking the time for the second account *

Figure 14 "Charge notice ^*

FIG. 15a, b “connection charged online”

Figure 16 "Calculation of the amount of money required *

Figure 17a, b "Reserved amount of money for the time slice" Figure 18a, b "Restore the account"

Figure 19 "Process of Call and Account Handling"

Numerous other requirements regarding Performance optimization and implementation constraints greatly increase the complexity of the algorithm, but are mainly based on implementation technology.

In the following phase, the prepaid service is supplemented by the CAMEL requirements and the method described in this invention is also used for MTC handling.

The invention is described below by an exemplary embodiment.

In this example, the call and user account handling for the MOC (Mobile Ongmating Call) is shown in particular.

Call and user account handling procedure (Figure 19) 7

This section describes top-level call and user account handling.

The following actions must be carried out:

1. The number called is first checked for "prohibited numbers" (see section Handling prohibited numbers). These are connections that cannot be billed online because no tariff model can be used or because the service subscriber is excluded from certain connections

2. Then on "toll free numbers" (see. Section Ge ^¬ Buhre free numbers), ie compounds which toll-free in a list numbers are managed is checked. For this

Numbers, the online billing of the PrePaidService is switched off, since the call is paid for by the other party (e.g. by a company that provides free telephone calls). However, there can also be free connections that are not managed in the list of free numbers. This connection is billed online, with the zero charge as it is managed by a set of e-parameters.

3. The expiry date of the card is monitored (see Absr-nmtt monitoring the validity period).

4. Since there is no basic fee, participants must implement a minimum number of fee units. This means that participants who have to reach a minimum turnover by reloading vouchers will be warned when their expiry date will soon be reached.

5. If the normalized CdPA (Called Party) is a number that must be mapped to another connection, the translation of a called subscriber number for service connections takes place. 6. Determine the "Friends and Family" (FnF) feature

7. Determine the account, must a second account be used? (Determme Account)

8. Determine the tariff model and the fee units that are used for a time slice. (Determme Tariff Mo ^¬ del)

9. Elapsed Gebuhreneinheiten earlier calls are released ^¬ em first new section of Gebuhreneinheiten is reserved, and all benotigten payer values are m CID's copied. (Reserve first money)

10. Calculates the available amount of money. These values are used for later threshold value comparisons. (Compute Available Money)

11. The credit of the PPS participant is checked. Depending on the credit, various promotions are drawn (e.g. if there is insufficient credit. (Insufflcient Credit)

12. The connection is established and the call is charged online. See the details below: (Connection and Chargmg)

Handling prohibited numbers

The network operator or service provider (provider) may sometimes avoid subscribers calling certain numbers. These are managed in a list of prohibited numbers, which is individual for each service provider. The network operator can add some prohibited numbers to the list of service providers. These cannot be deleted by the service provider. To facilitate the administration of prohibited numbers, exi ^¬ stare one black and two white lists to all numbers except for a few such as international long-distance calls (on which the international Ferngesprachcode preceded by), but JE is not this m the home PLMN (which the ^{international} long-distance call code is also prefixed, but followed by CC).

The list of prohibited numbers can be set and managed by the network operator using a Customer Service Control (CSC). The numbers must be saved in international format. They are valid for the subscribers of a service provider.

A first algorithm is used to find the most suitable black list number and the second white list of prohibited numbers. A second algorithm is used to find the exact number m of the first white list of prohibited numbers. The lists are determined and managed exclusively by the network operator. If the called party address (CdPA) is managed in the list of prohibited numbers, the subscriber is informed that a connection to the dialed number cannot be established. Otherwise, the main branch of the call and account handling is continued.

Free numbers

Some connections do not have to charge the caller. These can be obtained from a list free of charge

Numbers are managed for each service provider. The service provider can include some toll-free numbers in the service provider lists. For toll-free numbers, the onlme charging mechanism of the PPS is skipped. The numbers must be saved in international format. If the CdPA or CgPA (for MTC calls) is included in the list of toll-free numbers, the connection is established omitting the online billing mechanism. A call ticket is written. If the CdPA or CgPA is not listed as free of charge, the main branch of call and account handling is continued.

Monitoring the period of validity

The expiry date for the participant's accounts is checked here (only one expiry date for all accounts).

If the expiry date has passed, the call is terminated with a message and an error ticket if the validity is monitored and the ChargeFreeFlag is not set, i.e. if the top-up server is available.

An MTCLock flag is provided for the case where MOCs cannot be excluded after card expiration, i.e. the user can make calls for as long as he has credit. However, he cannot receive calls after the expiration date. The lock is made in the HLR, but the user receives the message "Expiry date reached, no MTC" after the following MOC if the flag MTCLock is set. The lock is automatically reset when the expiry date is postponed, for example after reloading ,

If the validity of the card has expired and the top-up server is not available, the call could be put through without an online charge. If the card has expired and the top-up server is available, a message is loaded and the call is terminated.

Notification of expiration date warning

If a subscriber makes a call and the expiry date is approaching, ie the date of the call is within the warning period before the expiry date and is not yet the expiry date exceeded, a message is imported before the connection is established. This is handled by the IP.

Translation of a called number for service connections

We check the CdPA number to see if it is a connection that is to be redirected to another number. This option enables service providers to offer additional services with known numbers from another network by simply routing the call back (re routmg).

Figure 1 Determine account

Each participant has two accounts (account 1 and account 2, with the contents cred.credit and crιdlιst [2] credit). It must be determined which account is to be debited. The account is determined using a service logic (Determme Account subFSL) (by setting "Account_2Flag" to 0 or 1) see Figure 2. If the account determination FSL is not found or is not active, a message (announcement) can be played and the call will be canceled.

Depending on which account the communication is carried out, the CID "account" is set to 1 (for account 1 ^, 2 (for account 2) or 3 (if both accounts communicate).

Figure 3 Determining the tariff model

There are several criteria for determining the charges for a particular call. These include the time and the zone (e.g. connection to the B participant) and some special criteria

CF ("Call Forwardmg"),

• FnF,

• FA ("Favorite Area"), 12

MLC ("Mobile Local Call"

CF, FnF and MLC can be combined, whereby in this example both CF and MLC are active at the same time. Since ^¬ is obtained by 6 possible combinations. If none is valid, the call is a normal MOC. A long model is used for each of these combinations. Each combination is assigned a tariff branch, this may be another desperation ^¬ supply, be the same branch or the same, but differently managed under ^¬ branching.

For example:

If the operator wants to provide a tariff model for MOC, one for CF and one for FnF, but none for CF and FnF, because in this case the call is to be billed according to the CF tariff model, you have to manage the following tariff models:

TarιffModell2 (for MOC), TariffModel04 (for CF), TaπffModel08 (for FnF). An IN number must be administered for each of these tariff models.

For example, TariffModel 12 (MOC) receives the IN number * lβl, TaπffModel04 (CF) receives the IN number * 162 and Ta ^¬ riffModel 08 (FnF) receives the IN number * 163. The IN numbers of the other tariff models must correspond to one of these three branches. Ie the IN number of Ta πffModel03 (the combination of CF and FnF) must be * 162 as with TarιffModel04 (CF).

Each tariff model consists of 5 sub-tariffs, which are called the tariff index and can be selected by the participant. The participant changes the tariff mdex in the DTMF menu.

13

Em call is em MLC when MLC are possible and CdPA is preset with ei ^¬ nem LAC Local Area Code, of the list of LAC corresponds to the LocA. If an MLC is detected, this is considered a tariff determination, see FIG. 4.

tariff model

The interface of each tariff model consists of the parameters:

Destination number (ie CdPA), the participant selected plan index and other parame ^¬ ter as FnF.

In addition, all parameters that are used to evaluate the tariff branch are provided as a CID.

If the managed tariff model cannot be found, a message is played and the call is terminated.

If we have a tariff model with a wide range of parameters (Figure 5), we usually have to manage sufficient time (NormGrantedTimelarge) to meet the most extensive parameter set. Since the variables of the equations are m different units of measurement, we have to consider a factor (out of 10). The factor is reduced in the formulas to the last bit portion. If no service logic floating point arithmetic can be used, the RoundedPricePerUnitDenumerator must be included for rounding the fee units RoundedPricePerUnit. Then exponents less than zero can be treated. The FnF marking, the tariff index and the time zone (CD TZ) can also be used for parameter selection. The current account, if it is the second account, also has an influence on the choice of parameters if it is empty or not empty. The target type (CID DT) is used as the last criterion.

As shown in Figure 20, this is realized as follows: If the TZEparmsFlag marking is not set, the time zones should not be used to define the parameters. Therefore TZ is set to 0. If the second account can be used (Account_2Flag set) and if it is not empty (CID Credιt_2Empty not set), the time zones are also not used. In this case TZ is set to 0. If Account_2Flag is set, but the second account is empty (CID Credιt_2Empty set), the marking NotFlatιfCredιt_2EmptyFlag decides what to do. If it is set, time zones must be used for the selection of the parameters, otherwise not.

The FnFEparmsFlag flag decides whether (if it is set) or not (if it is not set) special E parameters should be used for an FnF call. The tariff index shows which table is to be finally selected. The parameters from this table can now be used (y between 1 and 10 and x between 1 and 5).

Depending on the account used, an amount of money must be reserved on the first, the second or both accounts. For this

Reservation was developed in a new SIB Service Independent Building Block, Program Program, which reduces payer operations: the MngAccount SIB, see Figure 6. This SIB can read the account and the total amount of reserved shares, reserve a share, the expiry date of the reservations set, debits to the account, reserved Approve shares and count the number of calls to make a reservation on this account.

If the SIB cannot reserve the entire part, it reserves as much as possible and then ^issues the output "not sufficiently reserved" or "not reserved". In this case, the marking for a forced termination is set.

Figure 7 Calculation of the available amount of money

The available amount of money is calculated according to the CID account. For the current account, the available amount of money is set equal to "the balance on this account minus the total amount of reservations for this account". If the account is not currently used, the available amount of money will be set to zero. The total amount of money available is also calculated.

Figure 8 Insufficient credit

The procedure to check for a sufficient amount of money before making the connection is as follows:

If "FirstBitPortion" could be reserved, the call should be set up normally.

If FirstBitPortion is not sufficient, a check is carried out to determine whether the available sum "availableMoney" exceeds the threshold "callConnectThreshold". Otherwise the call is canceled.

It is checked whether "availableMoney" is sufficient to ensure a sufficiently long call duration, depending on the currently valid parameters. If the possible call duration is below the "callTimeThreshold", the call is not connected. All these Überprü be Ungen omitted if the charging ^¬ server is not available, ie when the "ChargeFreeFlag is set.

The specification of the call setup threshold values was carried out carefully, i.e. "normGrantedTime" should exceed "callTimeThreshold" and "callConnectThreshold" should be chosen with a view to a minimal set of parameters.

For example, "callConnectThreshold" cannot be used, i.e. managed as 0 to allow toll free connections to VMS m the first minute.

Figure 9 Checking the available amount of money

The call is terminated with a ticket if an insufficient amount of money could not be reserved. Reservations are released (release), Figure 10.

The "CallSetup" announcement does not have to be used.

Figure 11 call recordings on a second account

If "AvaιlableMoney_2" is below the "CallConnectThreshold_2" threshold and greater than or equal to "CallConnectThreshold_2mm", announcements (announceaccount2 and AA16) are played.

Figure 12 Checking allowable allowable time

The "Avaιlable_Granted_Tιme" is calculated (from parameters, unit fees and available money) and (on a time basis) compared with the "CallTimeThreshold" threshold. Calls are admitted if the available time is above the "CallTi eThreshold". If the available allotted time is below the "CallTimeThreshold", the free charge "ChargeFreeFlag" is checked. If it is set, the call is switched through free of charge. If it is not set, the call will not be connected. Instead, an announcement is played and the call is canceled.

The announcement can be a fixed message: "Not enough credit for this call".

Figure 13 call setup message on a second account

"Avaιlable_Granted_Tιme", which was calculated from the available sum "AvaιlableMoney_2", is below the threshold

"CallSetupThreshold_2" and above or equal to the threshold "CallSetupThreshold_2mm", two messages are played, but the call is not canceled. The participant will be informed of the amount of money in the second account (Announce Account). If the accounts communicate, message AA 6 will be played if AvaιlableMoney_l is above or equal to Tιme_l_Threshold_2, AA47 will not be played. The message dependent on AvaιlableMoney_l should not be played, it is managed as an empty message.

Figure 14 Charging reminder

First, the account 1 is checked to see whether it is above the charge warning threshold X. If this is not the case, a message (AA5a) is issued (it ^'may be empty if no message is to be issued). Then we check the credit on account_2 with regard to the recharge warning threshold Y. If the credit on account_2 is a high recharge threshold Y, no message is played. If this is the case, a check is carried out to determine whether the credit on account_l is zero, and a message reminds the user to top up the account and the credit to account 2 is announced. Is the credit on cred.credit not zero and credιt_2 is above the top-up threshold Z, reminds a message to top up the account and the credit from cred.credit is announced. After the messages, the call and account handling is continued.

Thus, the top-up games are played when creditl is low and credιt2 lies between "RechargeReminderY" and "Re-chargeRemmderZ" (where: RechargeRemmder Y> Re-chargeRemmderZ).

Figure 15 Connection and charging

The handling of calls made online is shown here.

Competing calls can be billed. Therefore, we reserve parts of the participant's credit and use them for the online fee. At the end of the call, the fees used are deducted from the reserved portion of the credit, depending on the account determined and the communication between the accounts of Account2 and / or the account of the subscriber. The reserved parts are released. This is done by a program module "mngaccount".

The call is put through to the dialed number or a forwarded number and the connection is established. This is a number without an SCM, which is sent in the INAP connection message.

The call is charged online. The INAP ApplyChargmg (AC) message is sent. After the first time, it is sent every time ACR_FINAL_ACTIVE is received. AC contains the call monitoring data for the SSP:

Allowed time,

• with the first AC or, if a tariff change occurs, the parameter set that is used to determine the fees, Warning tone ID,

• Time to play the warning sound before canceling the ANRU ^¬ fes,

• If the last bit section was used to calculate the allowed time, the parameter

"Forced Released" set to enable the call to be canceled.

After the start of the call, the last bit section of the active account was reserved. This last bit section is used to play a warning tone before the call is terminated due to insufficient funds.

In the event that a tariff changeover occurs during the first call monitoring interval, the changed call monitoring data and the switching time are recorded.

After each call monitoring interval or at the end of the call, ApplyChargmgReport (ACR) "final active * or ACR" final release "message is received. The ACR message contains the parameters:

• Sequence information ("final active" in order to receive a new allocated time, or "final release" to cancel the call),

• usedTime (and usedTimeAfterSwitch),

• Exit cause.

If a "final release ACR" is received, "Online Charged Connection" continues as shown in Fig. 15. The account is restored and the call is terminated.

If a "final active ACR" is received, the process continues as shown in the figure. "SumchargedMoney" (1,2 or 3) is increased by the amount of money used (depending on the active account) (sumcharged mcney = CID, which is the accumulated cost of this call). The part of the reserved portion, which remained unspent, is used as a rest for the next Reser vation ^¬ 'sα. before figure 1 6 for calculating the amount of money used).

A new section is reserved by the "MngAccount" module. Before e AC is sent, the service must calculate a new allowed time from "accountPortion".

If no sufficient amount of money is reserved, the

"forced parameter" set. The time allowed is equal to accountPortion plus the last bit section. The warning tone is not activated for fax or data calls. The next ACR is "final release".

If a new share could be reserved, the allotted time will be calculated according to the current tariff.

It must be ensured that exactly one basic fee of credit is deducted for a call. That is, if a tariff switch occurs during the first call monitoring interval and therefore two parameter sets are sent in the first AC message, the basic fee must be taken from the parameter set that is valid at the time when the anti-word message is received by the SSP , This applies both to the AoC functionality within the SSP and to the updating of the credit by the SCP.

If an error occurs in the connection between SSP and SCP, the router sends a "user abort". Now the service logic controls again, it can process the message, the call is canceled.

Figure 16 Calculation of the amount of money required After a message "final active AC", "usedMoney" (CID with the amount of money for a time slice of this call) is added to "sumchargedmoney". The difference between the time reserved for this AC and the time used for this AC is stored in "CID restl" and "rest2". For the next reservation we do not have to reserve this part of the credit (the rest) as it has not yet been used

Figure 17 Reservation of the next share

The next part is reserved for this call. The portion not used in the previous time slice is still reserved and therefore the reservation is reduced by this portion (rest). Depending on the success of the reservation, a "forced release" is set.

Figure 18 Restore the account

To restore the account, the call duration is then checked to ensure that it is greater than a certain predetermined threshold, the initial charge free time. If the call duration is greater than this threshold, the call is charged, otherwise it is not charged. " re-servedMoney "will be restored. The final charge will be added up m" sumchargedmdneyl, 2, 3 ".

"sumchargedMcney" will be deducted from the accounts and the reservations released. After the account is restored, a call ticket is written. Abbreviations

CAMEL Customized applications for mobile network enhanced logic CdPA Called Party Address

CF Call Forward g

CgPA Callmg Party Address

CID Credit

CSC Customer Service Control FnF, F&F Friends and Family (special tariff for selected

phones)

FA Favorite Area (Soerdarif for selected

Radio cells)

FCI Furnish Chargmg Information FSL Flexible Service Logic

IN Intelligent Network

IP Intelligent Peripheral

INAP Intelligent Network Application Part

LAC Local Area Code MLC Mobile Local Call

MOC Mobile Oming Call

MTC Mobile Termmating Call

PLMN Public Land Mobile Network

PPS PrePaid Service SCP Service Control Point

SSD Service Support Data

SSP Service Switchmg Pomg

Claims

claims

1. Procedure for billing connections

- where at least two fee accounts are used for billing, and

- a first account is selected when a call is set up, and

- a fee amount is reserved for this call on this selected account.

2. The method according to claim 1, characterized in that it is checked whether there is sufficient credit for the reservation on the selected account, and in the event of a negative test result, at least the remaining amount is reserved in a second account.

3. The method according to claim 1 or 2, characterized in that the reserved fee amount is sufficient for a fixed unit of time, and

- After the time unit has elapsed, the fee account to be used is selected again and an additional fee amount is reserved on this selected account.

4. The method according to any one of claims 1 to 3, characterized in that the connection costs actually incurred are collected and - deducted from the respective accounts only after the call has ended.

5. The method according to any one of the preceding claims, characterized in that - there is insufficient credit for a reservation, and the call is interrupted (forced release) and - the connection costs incurred are deducted from the respective accounts.

6. The method according to any one of the preceding claims, characterized in that simultaneous calls are made possible.

7. The method according to any one of the preceding claims, characterized in that the billing is carried out by means of a prepaid method.

8. The method according to any one of the preceding claims, characterized in that the connection costs incurred m are accumulated at least four buffers.

9. The method according to any one of the preceding claims, characterized in that it is realized by the technology of intelligent networks.

10. The method according to any one of the preceding claims, characterized in that it is used in a mobile radio network.