FI106152B - A method of billing for services and products purchased through a computer network - Google Patents

Description

106152

A method of billing for services and products purchased through a computer network

The invention relates to a method according to the preamble of claim 1.

In trade with information networks such as the Internet, billing is done according to prior art, for example through credit card companies. In this case, 10 customers have reported their credit card number to the payee via the Internet. Alternative payment methods include cash on delivery, downloadable electronic money, or special billing based on Internet server logs, for example. The rechargeable electronic money acts as a means of payment so that the customer as if opens an account in the payee's system and deposits the desired amount in that account. The price of ordered products, such as service products, is deducted from the customer's account balance. Special invoicing based on log files 20, in turn, operates by sending a separate invoice to the subscriber for the products they have ordered. In this billing method, the subscriber is usually billed after the product has been delivered, and generally requires a pre-existing billing agreement between the payer and the payee.

25: ·. ·. However, prior art payment methods include certain problems. The billing method based on credit card number reporting includes the risk number for the customer. getting to outsiders. Due to these abuses, this risk is now well known and efforts have been made to solve the problem by developing encryption methods for data transmission. In addition to the potential for abuse, credit card billing also has the potential to: * ·. a large proportion of potential consumers, particularly in the product groups targeted at young people 35, are excluded from trading; due to the lack of a credit card. Billing very cheap products through credit card companies is neither 'economical nor sensible.

2 106152

The use of downloadable electronic money or billing based on log files also involves tricky restrictions. The rechargeable electronic money requires a deposit corresponding to the customer's consumption. However, not all consumers 5 are ready to commit to product suppliers, and depositing can be difficult and uncomfortable. Billing based on downloadable electronic money also does not allow impulse buys from new suppliers. Billing based on log files 10 is not yet suitable for impulse purchases in new customer relationships. In addition, this method of billing requires pre-existing contracts and mutual trust between the parties to the transaction. In billing based on log files, therefore, cash flow is done through a separate billing routine 15 and is therefore not an economical way to charge small amounts.

The object of the invention is to eliminate the drawbacks of the above-described technology and to provide a completely new method of invoicing for services and products purchased from a data network.

. The invention is based on the fact that, when using the Internet through a telephone operator, the billing of services and products purchased from the Internet is also arranged in connection with the billing of the telephone operator. According to the invention, the connection from the caller through the telecommunication network is established through the intelligent network (SSP exchange), whereby the SCP database has the ability to influence the billing of the call.

The invention is also based on the fact that the A-30 number identity, i.e. the calling subscriber identity and the user name known to the Internet, transmitted by the telecommunications network are linked when the connection ”·. Internet dialing is formed. In this case, the Internet *. ·: · Billing for the use of a service or ordering a product •; can be accomplished by forwarding the invoiced amount to SCP on the basis of an A number identity corresponding to 35 Internet user names.

I I

• t • · • 4 · · 3 106152

According to the invention, pulse-based billing can be implemented, for example, with a Send Charging Information (SCI) message from Core-INAP, on the basis of which the SSP exchange sends the correct billing bounce to the subscriber's pulse counter. The so-called 5 ticket-based billing, in turn, can be implemented, for example, with a Core-INAP FCI (Furnish Charging Information) message, whereby the SCP database instructs the SSP exchange to establish a telephone connection to e.g. The FCI message generating the billing label is sent with 10 of these instructions.

More specifically, the billing method according to the invention is characterized by what is stated in the characterizing part of claim 1.

15

The invention provides considerable advantages. With the method of the invention, it is economical to perform the invoicing of small amounts. The method does not require a separate contract or deposit, so the method also allows for impulse buys. Also, the method of the invention does not require a credit card number or password, which may be susceptible to fraud. All in all, the method is well-suited for both time-based billing of services and the number of items'! 25 for one-time billing.

The invention will now be described with reference to Examples *. · 'And with reference to the accompanying drawing.

The drawing schematically illustrates one embodiment of the method of the invention.

• * • · • ·

One such system environment is illustrated in the drawing; wherein the method of the invention can be used.

In this figure, measures related to the use of one of the methods of the invention are also associated with this environment.

; The actions are described as arrows in the · ·. ·. · Not between system components. The figure shows a telephone interface 4 106152 through which a user of a paid service connects to a telephone network. Other components of the system include the SSP exchange 21 of the telecommunications network, the Internet dialing set 22, the SCP database 23 and the inspection database 24, and the Internet 25.

5

Using the billing method involves the following steps: 1) The telephone user calls from the subscription 20 (for example, by modem or ISDN modem) to the number 22 of the internet dialing set 10, whereupon the call is first connected to the SSP exchange 21 closest to the subscription 20.

2) Retrieving billing and switching information for basic call billing from SCP database 23. The basic billing can be 15 typically e.g. 15 rpm + ppm and its target number is the actual number of the internet dialing series 22.

3) The call is connected to an internet dialing set 22, whereupon the user enters his / her ID and password 20 which allows him / her to connect to the Internet connection service.

•% i 9 • «.

'. 4) When the user connects to the connection service, the »I» is updated; information in the inspection database 24 that the said »· •; 25 callers or 20 subscribers have contacted I · ···! user ID. The interface 20 is identified by its A-state • • i * · serial number.

9 »•» • · 9 5) The user navigates the Internet 25 and subscribes to the 30 products they have found or uses a paid service.

; ·. 6) Data is transferred to the inspection database 24 that certain services or * t \ have been used by the user in question. ordered certain products. On the basis of the information received in step 4, database 24 associates the user IDs with the correct A subscriber number.

t) f * 99 t f 106152 7) Database 24 transfers information from order to SCP database 23 for billing of interface 20.

8) If billing is done on a ticket basis, the SCP database 5 23 commands to establish a telephone connection to, e.g. FCI message (Furnish Charging Information).

10) Based on this FCI message, the SSP Center 21 makes a ticket 26 to charge for that subscription.

9) In the case of pulse-based billing, the SCP database 23 sends a Send 15 Charging Information (SCI) message to the SSP 23.

11) Based on this SCI message, the SSP exchange 21 sends a pulse burst of service or product price to the subscriber interface 20.

20

When the call is disconnected, the connection between the user ID and the A subscriber number in the verification database 24 can be deactivated.

If desired, the database 24 can also store data for 25 different user accounts or subscriptions 20 for paid service: ·. restrictions on the use of bones. When migrating to database 24. information 6 that a particular user ID or subscription 20 wants to use certain services or order certain products is checked if this is possible. If user information 30 is found in database 24 (A-number identity and user ID correspondence) and the user has not exceeded e.g.

: '·· For each billing period or subscription limit per subscription, the database informs 24 service providers that: a fee may be charged, and at the same time transmits to SCP 23 35 information for billing the caller. . in principle, be either user-specific, telephone-specific or a combination of these.

6 106152

If the user information is not found in the database 24 (A-number identity and username do not match) or the user, for example, for each billing period, the usage limit is exceeded, the database 24 informs the service provider-5 that charging is not possible. The same can be done if the user is so called. blacklisted for unpaid invoices. In these denial-of-charge cases, no information is sent to SCP 23 for billing purposes 7.

10

The service or product pulse-based billing is done by a Core-INAP SCI (Send Charging Information) message 9. The SCP 23 may send one or more kappa-15s to the SSP 21 during such a freely dialed call 9. SCI messages 9 allow the sending of individual counting pulse or MPM messages 11, but also the exchange of the rate case. It is also possible to construct a system in which the SCI message 9 can be used to control the so-called. accounting information or CHG messages.

20

Within one SCI message 9, 1 to 15 pulses may be determined to be charged. The SSP exchange 21 then sends a corresponding counting pulse message (MPM) message 11 in the direction of the A-subscriber 20 containing the aforementioned number of pulses.

· 25 The pulses are stored in the counter of the A-subscriber 20 and form the basis for charging in this way.

* «·«

The following is an example of pulse billing. If the cost of the pulse is 48.8p and the service user 30 is charged FIM 30 (= 61 pulse, 48.8p per pulse), the SCP 23 will send pulses to the SSP 21 in SCI messages 9 as follows: 1. SCI- message: 15 pulses 3 5 2. SCI message: 15 pulses 3. SCI message: 15 pulses 4. SCI message: 15 pulses 5. SCI message: 1 pulse 106152 7

Similarly, the SSP exchange 21 transmits in the direction of the A-subscriber 20 the respective counting messages 11: 1. MPM message: 15 pulses 5. 2. MPM message: 15 pulses 3. MPM message: 15 pulses 4. MPM message: 15 pulses 5. MPM message: 1 pulse 10 Another possibility to implement the service charge is to change the tariff already generated by the SSP 21 to the A-subscriber 20 by SCI message 9. This is done by first transmitting a new tide rate case (Level_to_Use) by SCI message from 9 SCPs to 23 SSPs 21 and immediately by exchanging 15 new SCI messages by 9 old rate case (Level_to_Use).

For example, when charging a service user of FIM 30 (= 61 beats, 48.8p / beats), the SCP 23 may first send the SSP 21 a SCI-20 message 9 in which the rate case orders to send a 61 beats pulse in the direction of A subscriber 20. Immediately thereafter, SCP 23. . sends a new SCI message 9 to the SSP 21 specifying the original rate case as the rate case.

It is also possible to construct a system in which, via the SCI message 9, it is possible to request the SSP exchange 21 to send in the direction of the subscriber A- '·· also so-called. calculation information, or CHG words. The service is then charged by sending an SCI message 9 from the SCP 23 to the SSP 21 defining the contents of the CHG message to be transmitted from the SSP 21 to the A-20. In this case, the one-time service-related fee can be set in a very flexible manner in the CHG message. For example, the rate can be between 1 penny and 100,000 FIM.

35 Alternatively, billing may also be effected on a ticket: ·: ·. ' jaisesti. When ticket or service-based charging is used for a service or product, 21 ICA messages (InitiateCallAttempt) are sent from the SCP 23 to the SSP and at the same time the ticket is dominant. 106152 FCI Message 8. Since the ICA operation is only used here to enable transmission of the FCI message 8, the "call" generated by the ICA operation does not actually connect outside of the SSP exchange 21 but establishes a short link within the SSP exchange 5 21 between the two virtual interfaces. The "calling" virtual interface A is provided in the callingPartyNumber field of the ICA message and the "corresponding" virtual interface B in the destinationRoutin-gAddress field.

10 The actual debit information is transmitted in the fCIChar-geBase section of the FCI message 8, as well as in the optional filledNumber, creditCardNumber and accountNumber fields. The fCIChargeBase part of the FCI message 8 reports the rate either as a level-toUse or a cHGBased. For example, the lengths of other fields in the free format 15 are: chargedNumber = 14 octets, 28 characters, creditCardNumber = 8 octets, 16 characters, accountNumber = 12 octets, 24 characters.

20 In this case, the A-subscriber identity of the subscriber paying for the service or product may be expressed, for example, by accountNumber -? field. The billing (price,! '·' Number of copies, currency, etc.) and billing information for a service or product can be divided into both fCIChargeBase and chargedNumber -: ·. fields. It is also possible that the creditCardNumber field-

* «I

this is used as an extension of the chargedNumber field if its 28 'characters are not sufficient for billing and billing purposes.

The billing label created in the SSP exchange 21 is transferred to the billing system of the teleoperator, whereby, based on the fields of the said billing label, the correct A-subscriber 20 is billed for the service or product he uses. There are also 35 money transfers to the service provider and different. . clearing between teleoperators can be accomplished by means of a computation chain, 26.

j 9 106152

Although the preceding examples have spoken about the Internet, the invention can also be applied to commerce through other computer networks. The invention may also be applied in such a way that the telephone interface 20 is a mobile telephone subscription or 5, for example, a business switchboard. Thus, one preferred embodiment of the invention may be shopping on a mobile phone which itself includes a computer.

«· •« «« »ψ 1 · w ·

Claims (8)

10 106152 A method of billing orders placed by a buyer using a data network (25) over a telephone network (20, 21, 22, 23) through a data network (25), the method of identifying a telephone interface (20) used by the buyer; billing information for billing system for billing the telephone interface (20), characterized by identifying the user ID of the buyer information network (25), storing identification information of the telephone subscription (20), contains a billable user name, 25 ·· ". - verifying from the audit database (24) whether the most billable user name is connected to a telephone interface (20), - verifying whether the bill is accepted tu request, and if the billing request is accepted: - Target the user account billing request to the buyer's telephone interface (20), «% 35 # f ·; ' - sending the billing information to the SCP database (23), * · «t I (r - sending the billing information from the SCP database (23) to the SSP exchange (21) that transmits the call t (* 11 106152) and sending the billing information to the billing system (20) for invoicing 5 Method according to claim 1, characterized in that, when sending billing information from the SCP database (23) to the SSP exchange switching center (21) and further from the SSP exchange (21) to the billing system - the SSP database (23) is transmitted to the SSP (21) ICA message and FCI message, 15. generates a billing label in the SSP center (21) based on the FCI message, and - transfers the billing label to the billing system. 20 A method according to claim 1, characterized in that, when sending billing information from the SCP database (23) to the SSP switching center (21) and: forwarding from the SSP exchange (21) to the billing system 25 "."! from the database (23) to the SSP exchange (21):; * at least one SCI message containing instructions for at least • · · ·; ·: to charge one pulse, • «· · · · 30. generated by the SSP exchange (21). calculating a counting pulse message based on each SCI message and sending each counting pulse message * to the pulse counter of the telephone interface (20) 35 * 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 l2 106152 A method according to claim 1, characterized in that, when transmitting billing information from the SCP database (23) to the SSP exchange switching center (21) and further from the SSP exchange (21) to the billing system 5 - from the SCP database (23). An SCI message containing a new tide rate case to be defined for the telephone interface (20) to the SSP exchange (21), and 10. immediately thereafter transmitting an SCI message from the SCP database (23) to the SSP exchange (21) ordering the return of the telephone interface (20) previous tax case. 15 A method according to claim 1, characterized in that, when sending billing information from the SCP database (23) to the SSP exchange switching center (21) and further from the SSP exchange (21) to the billing system 20, SSP data is transmitted from the SCP database (23). for the exchange (21), a SCI message, - generating, at the SSP exchange (21), a CHG message, * i · II *, based on the SCI message 25a; - sending a CHG message from the SSP exchange (21) to the telephone billing • • 1 ”··· subscription (20) and transmitting the billing information from the billing central to the billing system. * · E • · · • 1 · · · f i · • · · The method of claim 1, characterized in that, if the billing request is not accepted, the sender of the billing request is notified of the rejection. 106152 13 7. A method according to claim 1, characterized in that: - the verification database (24) uses a database containing information on the access restriction set for the telephone interface (20), and - in addition to checking the billable user ID and the connection to the telephone interface (20) acceptance. A method according to claim 1, characterized in that 15 - a verification database (24) uses a database containing information on the access restriction set for the user ID and 20. in addition to verifying the connection between the billable user ID and the telephone interface (20). • · · »··» »• · t ♦ •« · «•« «• ·« 111 * • · · • · · I · f I 4 • 4 4 • 1 ·. • · «• ·« · • I 1 I · 14 106152