EP1196899A1

EP1196899A1 - Method for billing a telephone subscription

Info

Publication number: EP1196899A1
Application number: EP00949515A
Authority: EP
Inventors: Lauri Isotalo
Original assignee: Elisa Communications Oyj
Current assignee: Elisa Communications Oyj
Priority date: 1999-07-20
Filing date: 2000-07-19
Publication date: 2002-04-17
Also published as: AU6284700A; WO2001009848A1; FI991627A; FI116021B

Abstract

The invention relates to a method for receiving and processing the invoicing information for an order placed through a telephone connection, in which a second telephone subscriber orders products or services from a first telephone subscriber. The invention also relates to a method for processing the invoicing information (8) of an order placed through a telephone connection and attaching it to a telephone bill. In the invention, the call is identified by means of an identifier (7), on the basis of which the first telephone subscriber can itemize the invoicing information (8) describing a product or service supplied and/or matters relating to them. The invoicing information (8) can be sent, if necessary, to a second operator, over an operator interface.

Description

METHOD FOR BILLING A TELEPHONE SUBSCRIPTION

The present invention relates to a method, according to the preamble to Claim 1, for receiving and processing invoicing information for an order placed through a telephone connection.

The invention also relates to a method, according to the preamble to Claim 10, for processing the invoicing information for an order placed through at telephone connection and attaching it to a telephone bill.

Invoicing solutions according to the state of the art are based on a method, in which a customer calls either a normal number in a telephone network or a special service number, which may be either free or subject to a surcharge. When a customer calls a normal number in a telephone network or a free number, the call is connected to the provider of the products or services. Next, the customer places an order either on the basis of product information received beforehand, for instance, from a catalogue, or on the basis of the telephone conversation. Payment for the product or service can take place, for example, by postal or other C.O.D. delivery, by bank giro, or by using a credit card.

If a customer calls a special telephone number subject to a surcharge, the price of the product or service is charged according to the charge rate of the relevant service number. The price may be one-off (price/call) or minute-based (price/minute). The service or product is paid for through a telephone bill, in which the price usually forms part of the total in the row for the service number area code in question, along with the price for any other calls made to this service number area code. In known services offered by phone and invoiced through a telephone network, the calling-party is generally the buyer. If the buyer is in a network other than that of the operator sending the service pulses, an inter-operator meter-pulse-clearing procedure will also be required, in which the operator receiving the meter-pulses credits the operating sending the pulses with a value, from which the operator receiving the pulses deducts a billing fee. The operator sending the meter-pulses correspondingly credits part of the money thus obtained to the service provider and retains the rest itself. The operator receiving the pulses in turn charges the value of the pulses to the calling connection.

In the case of a normal telephone-network number or a free service number, the provider of the product or service invoices the customer after the event, using the conventional invoicing methods in telephone sales. In such cases, postal C.O.D. delivery or a separate invoice delivered to the buyer's home are expensive ways of invoicing, especially for cheap services or products. On the other hand, customer are suspicious of giving their credit card numbers to pay for products or services, because they fear misappropriation. Payment by bank giro is not very suitable for charging for a service or product, as the details of the account and reference numbers must be given by word of mouth during the call, while, in addition, the provider has insufficient certainty of payment being made. Payment in cash on delivery of the product is quite simple in cases like pizza orders, but is open to misuses, such as baseless orders and malicious calls, while the person delivering the order must always have change.

In the case of a service number subject to a surcharge, customers pay the price of a service or product on a one-off basis (price/call) or a minute basis (price/minute) in their telephone bills. In this case, it is practically impossible to charge for services or products in such a way that their final sum would correspond to the number of meter- pulses sent during the call or a charge-class appropriate to the length of the call. Because it must be possible to change service and product prices flexibly, and it must also be possible to add arbitrary combinations of different products and services to the shopping basket, such a conventional invoicing method based on meter-pulses would require a vast number of special cases, to be able to invoice all the variations of purchases. The applications in general use to not permit payment for several products or services during a single call.

In addition, because conventional service-number charging does not permit a shopping basket to be 'emptied' or the purchase transaction to be cancelled in the middle of a call, without the customer already being sent pulses, the conventional method of invoicing leads to situations, in which customers often have to be credited manually for part or all of the cost of calling the service number in question. Present service-number charging does not allow flexible provider-controlled pricing of services and products. Customers cannot see individual purchase transactions, products, and their prices on their telephone bills, because service-number calls are generally bunched as a row giving the total for all calls made to the service-number area code. Correspondingly, it is also not possible for the service provider to see, after the event, an itemization of the services and products it has delivered to customers. This is a particular drawback in problem situations, in which the customer and service provider try to determine whether a product or service supplied corresponds to the order placed and the price charged. The state of the art also does not permit a called-party to be charged through their phone bill for a service provided by a calling-party.

From the point of view of a public telephone network, the sending of meter-pulses, which takes place typically one meter-pulse at a time in a single signalling message, places an unnecessary load on the signalling channels and systems of the telephone network, particularly when largish sums of money are being charged to a calling connection. Up to 15 individual meter-pulses can be packed in a single message, but this is generally avoided, as the possible disappearance of the metering message during its journey would cause a corresponding loss of cash to the operator.

US patent publication 5.872.833 discloses an arrangement permitting a credit card to be used in invoicing between two subscribers. During a call between two subscribers, an agent is formed, which can be activated by either subscriber, and which listens to the voice-frequency signals sent from the telephone connections, or to data sent on top of the voice connection. This allows the buying subscriber to enter the number of their credit card from the telephone connection to the payment system, and for the selling subscriber to enter itemized price and other transaction information to the payment system. The information can be read by the buyer, who can then reject the deal.

The arrangement according to US patent publication 5.872.833 has the drawback that buying requires the possession of a credit card. This arrangement also requires the entry of the credit card number and of verification data, relating to the card or its possessor, that can be used to reduce the danger of unauthorized use of the credit card number. The invention is intended to eliminate the defects of the state of the art disclosed above and for this purpose create an entirely new type of method of invoicing a commercial transaction made by means of a telephone.

The invention is based on a call-specific identifier being formed, for example, in an SCP (Service Control Point) of the telephone network and being sent to the subscriber providing a product or service, when a switched connection is formed over an information network or telephone network. The identifier allows the subscriber providing goods or a service to attach invoicing information to a ticket, the SCP transmitting the information to the billing systems both of the operator providing the calling connection and of the operator providing the called connection.

More specifically, the method, according to the invention, for receiving and processing invoicing information through a telephone connection is characterized by what is stated in the characterizing section of Claim 1.

The method, according to the invention, for processing invoicing information of an order placed through a telephone connection, and attaching the information to the telephone bill of the first telephone connection, is characterized by what is stated in the characterizing section of Claim 10.

The invention has the advantages of flexible and cost-effective invoicing of products sold by telephone and of an arrangement that also transfers information on the products and services selected by the customer to the billing system of the buyer's operator.

The invention allows the creation of a flexible invoicing system, in which prices charged for products or services can be freely selected, and need no longer be set on the basis of the length of call or the number of pulses to be sent. Thus, customers are no longer unnecessarily charged for services that they may not want, or products that they ultimately may not want to order.

The method according to the invention is both highly flexible and also cost-effective, as the information on a confirmed transaction, together with its itemization, is transferred to the billing systems of both the charging operator and the subscriber's operator, without meter-pulses being sent, thus eliminating pulse losses of any kind. A precise itemization of a purchase transaction can easily be added to a telephone bill, stating the date of purchase, the products and services purchased, the number of items, the unit prices, and the final totals. Additional information on the provider, the services, or the products can also be added to the bill itemizatio. The invention is not limited to applications within one country, but can also be used to transfer payment transactions and bill itemizations between several countries and operators, provided the calling-party identity can be transferred reliably between operators.

The method according to the invention permits contact between the buyer and seller of a sen-ice or product even after the payment transaction itself, if the service or product does not satisfy the buyer. Both buyer and seller retain itemized receipts of the payment transaction. Possible disputes are easier to settle using the information recorded on the receipt, such as the date and time of the call, the services selected, and their prices.

In an arrangement according to the invention, the called party can invoice the calling party or vice versa. In the payment arrangement according to the invention, the telephone subscriber need not to possess a credit card.

In the following, the invention is examined with the aid of embodiments according to the accompanying drawings.

The first embodiment, according to Figure 1. shows an operational diagram of a case in which the called party invoices the calling party, over an operator interface.

The second embodiment, according to Figure 2, shows an operational diagram of a case in which the calling party invoices the called party, over an operator interface.

The third embodiment, according to Figure 3. shows an operational diagram of a case in which the called party invoices the calling party, in the network of the same operator.

The fourth embodiment, according to Figure 4, shows an operational diagram of a case in which the calling party invoices the called party, in the network of the same operator.

All the embodiments according to the Figures use the following numbered elements:

In the systems used in the embodiments, there is a first operator 1 1 providing, in all the examples of embodiments, a connection to the called party, i.e. the subscriber receiving the call. In embodiments 3 and 4. first operator 1 1 also provides a connection to the calling party, I e the subscriber making the call In the systems used m the embodiments, there is a first SSP centre 4 (Service Switching Point) controlled by the first operator 11, which handles intelligent telephone network services and the related control database, the first SCP 1 (Service Control Point) The first invoicing information

8 in embodiment 1, the second invoicing information 42 in embodiment 2. the third invoicing information 43 in embodiment 3. and the fourth invoicing information 44 in embodiment 4 each contain information defined by the invoicing subscπber for a product or service ordered from this subscriber The invoicing information contains information freely definable by the selling subscriber, relating, for instance, to the product or service ordered, the service provider, the service or purchase transaction, terms of delivery, product warranty, or terms of return The systems used in the embodiments incorporate an invoicing system 12, which produces, from the invoicing information, an entry for the telephone bill and/or credits the service provider's account, or a separate invoice or credit to the service provider's account

In addition to the above, a few additional elements are used m the first and second embodiments according to Figures 1 and 2

There is a second operator 13 providing a calling connection in embodiments 1 and 2 An operator-cleaπng server 14 handles the transmission of invoicing information between the operators A call ticket for the call event can be formed in the SSP centre

16. controlled by the second operator 13, under the control of the second SCP 2 controlled by the second operator 13 This can be used to produce, using a second billing system 18 controlled by the second operator 13. an entr in the telephone bill for the subscπber connection, or to credit the service producer's account

Certain elements, which are not used in the other embodiments, are used m the first embodiment according to Fi ure 1

The first calling connection 3 is connected to a public or private telephone network or mobile telephone network. The first called connection 5 is also connected to a public or pπvate telephone network or mobile telephone network and is in the network of a different operator to that of the first calling connection The first called terminal device 6 connected to the first called connection 5 can be, for example, an IVR device, a switchboard, a series-telephone system, or an individual telephone apparatus, which may also be a mobile station. A first identifier 7 identifies a specific telephone connection between the first calling connection 3 and the first called connection 5. In addition, there is a second subscriber-billing server 15, which maintains subscriber data and handles the transmission of billing information to billing system 18. The first call ticket 9 and the fifth call ticket 19 contain invoicing information in a specified form.

Certain elements, which are not used in the other embodiments, are used in the second embodiment according to Figure 2:

The second calling connection 26 is connected to a public or private telephone network or mobile telephone network. The second called connection 27 is also connected to a public or private telephone network or mobile telephone network and is in the network of a different operator to that of the second calling connection 26. The terminal device 20 of the second calling party is a terminal device, near second calling connection 26, which can form an information network connection and communicate with first SCP 1 through the network. There is also a second service-provider billing-server 24 controlled by the second operator 13, which maintains service provider data and handles the transmission of invoicing information to second billing system 18. The second call ticket 22 and the sixth call ticket 25 contain invoicing information in a specified form.

Elements, which are not used in the other embodiments, are used in the third embodiment according to Figure 3:

The third calling connection 28 and the third called connection 29 are connections of a public or private telephone network or mobile station network, which are in the network of the same operator. The terminal device 30 of the third called party can communicate with first SCP 1. The third call ticket 32 contains invoicing information in a specified form and the third identifier identifies a specific telephone connection between third calling connection 28 and third called connection 29.

Elements, which are not used in the other embodiments, are used in the fourth embodiment according to Figure 4: The fourth calling connection 33 and the fourth called connection 36 are connections of a public or private telephone network or mobile telephone network, which are in the network of the same operator. The terminal device 34 of the fourth calling party can be, for example, an IVR device, switchboard, series-telephone system, or individual telephone apparatus, able to communicate with first SCP 1. The fourth call ticket 38 contains invoicing information in a specified form and the fourth identifier 37 identifies a specific telephone connection between fourth calling connection 33 and fourth called connection 36.

Elements are used in the first, third, and fourth embodiments, according to Figures 1. 3. and 4. which are not used in the second embodiment according to Figure 2:

The first service-provider billing-server controlled by the first operator 11 , is a system by means of which first operator 11 maintains service-provider information and handles the transmission of invoicing information to the first billing system 12.

Elements are used in the second, third, and fourth embodiments according to Figures 2. 3. and 4. which are not used in the first embodiment according to Figure 1:

The first subscriber billing-server 23 controlled by first operator 11 is a system, by means of which the first operator 1 1 maintains subscriber information and hanldes the transmission of invoicing information to the first billing system 12.

Embodiment 1) the called party invoices the calling party over an operator interface.

This method involves the following operations (101 - 103) to form and identify a telephone connection:

101) A number, dialled from the first calling connection 3, to either a service number or an ordinary number in a public telephone network, is received.

102) The call is routed to the first SSP centre 4. In this case, the call also travels over an operator interface.

103) The first SSP centre 4 triggers the dialled number and requests the first SCP 1 for instructions relating to the routing of the call. First SCP 1 activates the logic relating to the service or telephone number in question. First SCP 1 detects from the logic that the terminal device 6 of the first called party is connected to the called connection 5 In connection with the relevant service, terminal device 6 of the first called party requires a first identifier 7 identifying the call. First SCP 1 generates \\ ith first identifier 7 in a suitable manner and attaches it to the relevant incoming call.

After this, first SCP 1 can deliver first identifier 7 to the terminal network device 6 of the first called party, either separately typically over information networks (stage 104) or duπng call formation (stage 105) Next, first SCP 1 receives, from the called party, the first invoicing information 8 identified with the first identifier ^" (stage 106):

104) The first identifier ⁷ is supplied by means of. e.g., the Internet or a separate data communications connection, from first SCP 1 to the network terminal device 6 of the first called party.

105) The first identifier 7 is supplied when the call is connected to the first called connection 5. Thus, the first identifier 7 can be supplied, e.g., as part of the called number, in, or as part of, the calling-party field, or in, or as part of. some other signalling field (e.g.. REDI and OCA fields).

106) Once me call has been connected, a situation arises once or more, in which the called party wishes to invoice calling connection 3 First SCP 1 then receives the first invoicing information 8. identified with first identifier ^". from the network terminal device of the first called party, for example, by means of a surplus ISDN connection Besides simply the amount of money to be paid, first invoicing information 8 contains additional information on the product purchased, for forwarding ultimately to the telephone bill of first calling connection 3, or to an invoice for the supplied product or service to be sent to the possessor of the calling connection, as an appendix to the telephone bill.

First SCP 1 can send first invoicing information 8 to first billing system 12 in at least two ways, 107 and/or 108. After this, the service provider's account is credited 109: 107) The first invoicing information 8 is forwarded (107a) to first service-provider billing-server 10 and from there to first billing system 12 (107b).

108) The first invoicing information 8 is forwarded to first SSP centre 4 (108a), in which a first call ticket 9 is made from the first invoicing information 8 (108b) and the information in the first ticket 9 is sent to first billing system 12 (108c).

109) Later, the charge information of the first service-provider billing-server 10 or the information in first call ticket 9 made by first SSP centre 4, or both, are utilized when first billing system 12 credits the service provider's account. Thus, valuable additional information can be attached to the credit to the service provider's account, which can later facilitate, for instance, discussions between the customer and the service provider in problem situations.

Operations 110 - 113 are carried out to invoice the calling-party. These operations can be carried out before operations 107 - 109, partly or completely simultaneously with operations 107 - 109, or after operations 107 - 109:

110) First SCP 1 also transmits the first invoicing information 8 to the other operator

13 (110a). This typically takes place through a dedicated operator-clearing server 14, to permit clearing of charges between the operators. If the operators do not have a common operator-clearing server 14. the said server can be divided into several parts, in which each operator has its own server for clearing of charges. This also permits 'double-entry book-keeping' of all payment transactions to be maintained.

Notification of a payment transaction can be sent from operator-clearing server 14 either to a second SCP 2 controlled by the other operator (110b), to a subscriber- billing server (110c),or in applicable parts to both.

I l l) If necessary, second SCP 2 can forward the first invoicing information 8 or part of it to a second subscriber-billing server 15 (I l ia), and command a second SSP centre 16 to make a call record of the first invoicing information 8 (111b). after which a fifth call ticket 19 is made from the record for further processing and billing. 112) Second billing system 18 receives the first invoicing information 8, either from second subscriber-billing server 15 (112a), or from fifth call ticket 19 from second SSP centre (112b).

113) From the information it receives, second billing system 18 produces a bill for the calling-party. The bill may include, besides the services and products billed, various additional information, on, for instance, the product, the service provider, the service or product transaction itself, the terms of delivery, the product warranty, or the possible terms of return.

Embodiment 2) the calling party invoices the called party over an operator interface

This method involves the following operations to form a call connection, identify it, and receive identified invoicing information from the calling party (201 - 206):

201) A call request to a called-party number is received from a second calling connection 26.

202) The call is routed to first SSP centre 4. In this case, the call also travels over an operator interface.

203) First SSP centre 4 triggers the dialled number and requests first SCP 1 for call- routing instructions. First SCP 1 activates the logic relating to the relevant service or telephone number. First SCP 1 notes from the logic that the second calling party's network terminal device 20, connected to the second calling connection 26, requires a second identifier 21 to identify a call event in the relevant service. First SCP 1 generates this identifier in a suitable manner and attaches it to the incoming call in question.

204) Second identifier 21 is sent over information networks to the second calling party's network terminal device 20 connected to second calling connection 26.

The device can be, for example, a PC running a www-based user-interface and connected to an information network, and/or a WAP-technology mobile station.

205) The call is connected to second called connection 27. 206) If, at a suitable stage, it is wished to make a call-billing order from the calling connection, First SCP 1 receives second invoicing information 42 from network terminal device 20 of the second calling party and, at the same time, second identifier 21 through the information network or, for example, a surplus ISDN connection. Besides the amount to be paid, second invoicing information 42 includes additional information to be forwarded ultimately to the customer's telephone bill, or to a product or service invoice to be sent to the customer as an appendix to the telephone bill.

The first SCP 1 can send second invoicing information 42 to first billing system 12 in at least two ways (207 and/or 208). After this, a bill is produced for the called party (209):

207) The second invoicing information 42 is transmitted from the first operator to first subscriber billing-server 23 (207a) and from there to first billing system 12 (207b).

208) The information is transmitted to first SSP centre 4 controlled by the first operator 11 (208a), in which a second call ticket 22 is made from second invoicing information 42, the information contained in second call ticket 22 being sent to first billing system 12 (208b).

209) From this information, first billing system 12 produces a bill for the called party. Besides the services and products being invoiced, the bill may include additional information, relating, for example, to the product, the service provider, the service or product transaction itself, the terms of delivery, the product warranty, and possible terms of return.

Operations 210 - 213 of the method are carried out to credit the calling party as the service provider. These operations can be carried out before operations 207 - 209, in part or wholly simultaneously with operations 207 - 209, or after operations 207 - 209:

210) The first SCP 1 transmits information on the payment event also to the second operator 13 (210a). To permit inter-operator clearing of charges, this typically takes place through a dedicated operator-clearing server 14. If the operators do not have a common operator-clearing server 14, the said server can be divided into several parts, in which each operator has their own server for clearing of charges. The term 'double-entry book-keeping' can then be used for all payment transactions. Data on second invoicing information 42 can be sent from operator-clearing server 14 either to a second SCP 2 controlled by second operator 13 (210b), to second service-provider billing server 24 (210c), or, in applicable parts, to both of these.

211) If necessary, second SCP 2 can forward information on the payment transaction, or part of it, to second service-provider billing-server 24 (211a), and/or command second SSP centre 16 to make a call record of second invoicing information 42 (21 lb), after which a sixth call ticket 25 is made from the record, for further processing and billing.

212) Second billing system 18 controlled by second operator 13 receives the information for billing either from second service-provider billing-server 24 (212a) or from second SSP centre 16 from sixth call ticket 25 (212b).

213) Later, the information forming the basis of billing or sixth call ticket 25 made by the second SSP centre 16 is utilized by second billing system 18 to credit the service-provider. This allows additional information valuable to the service provider to be attached to the service-provider credit, which can later facilitate discussions between customer and service provider in problem situations.

Embodiment 3) the called party invoices the calling party in the network of the same operator.

This method involves the following operations (301 - 303) to form a call connection:

301) Number dialling from a third calling connection 28. directed to either a service number or to an ordinary number in a public telephone network, is received.

302) The call is routed to first SSP centre 4.

303) The first SSP centre 4 triggers the dialled number and requests first SCP 1 for call-routing instructions. The first SCP 1 activates the logic for the relevant service or telephone number. The first SCP 1 notes from the logic that the third called-party ^*s network terminal device 30, connected to the third called connection 29, requires a third identifier 31 identifying the call event in connection with the service. The first SCP 1 generates this third identifier 31 in a suitable manner and attaches it to the relevant incoming call.

Next, first SCP 1 can send third identifier 31 to the network terminal device 30 of the third called party, either separately, typically over information networks (stage 304), or during call formation (stage 305). Next, first SCP 1 receives the third invoicing information 43 identified with the third identifier 31 from the called party (stage 306).

304) The third identifier 31 is sent, for instance, over the Internet or a separate data communications connection, from first SCP 1 to network terminal device 30 of the third called party.

305) Third identifier 31 is sent when connecting the call to the third called connection 29. In this case, third identifier 31 can be delivered, for example, as part of the called-party number, in, or as part of. the calling-party number field, or in, or as part of, some other signalling field (e.g., the REDI and OCA fields).

306) Once the call is connected, a situation arises once or more, in which the called- party wishes to invoice third calling connection 28. The first SCP 1 then receives third invoicing information 43. identified with the third identifier 31. sent from the third called party's network terminal device 30, for example, over a surplus ISDN connection. Besides simply the amount of money to be paid, third invoicing information 43 contains additional information on the product purchased, to be forwarded ultimately to the telephone bill of the possessor of the calling connection, or to a product or service invoice to be delivered to the possessor of the calling connection, as an appendix of the telephone bill.

The first SCP 1 can send the third invoicing information 43 to the operator's billing system in at least two ways, 307 and/or 308. Next, third invoicing information 43 is utilized to invoice the calling party and credit called party 309 as the service provider. 307) The information of the payment transaction is sent to the first service-provider billing-server 10 and/or to the first subscriber-billing server 23 (307a) and from there to the first billing system 12 (307b).

308) The information is transmitted to first SSP centre 4 (308a), in which a third call ticket 32 is made from the payment transaction information (308b) and third call ticket 32 is sent to the first billing system 12 (308c).

309) Later, the payment data of the first service-provider billing-server 10, or third call ticket 32 made by first SSP centre 4, or both are utilized to credit the service-provider by the first billing system 12. Thus, additional information. valuable to the sen-ice provider, can be attached to the service-provider credit, and can later facilitate discussions between customer and service provider in problem situations. On the basis of this information, first billing system 12 produces a bill for the calling party. Besides services and products, the bill can contain various information on. for instance, the product, the serv ice provider, the actual service or purchase transaction, the terms of delivery, the product warranty, and possible terms of return.

Embodiment 4) the calling party invoices the called party in the network of the same operator.

This method involves the following operations to form and identify a call connection and to receive identified invoicing information from the calling party (401 - 406):

401) A call request, sent from the fourth calling connection 33 to a called-party number, is received.

402) The call is routed to first SSP centre 4.

403) The first SSP centre 4 triggers the dialled number and requests first SCP 1 for call-routing instructions. The first SCP 1 activates the logic for the relevant service or telephone number. The first SCP notes from the logic that the fourth called party's network terminal device 34 requires a call-event identifier 35 in connection with the service in question. The first SCP 1 generates this identifier 35 in a suitable manner and attaches it to the relevant incoming call. 404) Identifier 35 is sent over information networks to the calling party's network terminal device 34 connected to fourth calling connection 33. This can be, for instance, a PC, connected to an information network, running a www-based user-interface, and/or a WAP-technology mobile station. It can also be an IVR device, switchboard, series-telephone system, or individual telephone apparatus connected to fourth calling connection 33.

405) The call is connected to the fourth called connection 36.

406) Once the call has been connected, a situation arises, once or more times, in which the calling party wishes to invoice called connection 36. The first SCP 1 then receives, over an information network or surplus ISDN connection, the fourth invoicing information 44 identified with the fourth identifier 37 from the fourth calling-party's network terminal device 34. Besides simply the amount of money to be paid, invoicing information 44 includes addition information on the purchased product, to be forwarded ultimately to the telephone bill of the possessor of the called connection or to a product or service invoice to be sent to the possessor of the called connection, as an appendix to the telephone bill.

The first SCP can send information on the payment transaction to first billing system 12. in at least two ways, 407 and/or 408.

407) The fourth invoicing information 44 is transmitted to first service-provider billing-server 10 and/ or first subscriber-billing server 23 (407a) and from there to first billing system 12 (407b).

408) The information is sent to first SSP centre 4 (408a), in which a fourth call ticket 38 is made from the payment-transaction information (408b), the fourth call ticket 38 being sent to first billing system 12 (408c).

409) Later, the payment information of the first service-provider billing-server 10, or fourth call ticket 38 made by first SSP centre 4, or both are utilized by first billing system 12 to credit the service provider. Thus, it is possible to attach to the service-provider credit additional valuable information for the service provider, which can later facilitate, for example, discussions between customer and service provider in problem situations. On the basis of this information, the first billing system 12 produces a bill for the called-party subscriber. The bill may contain, besides the services and products being invoiced, various additional information relating to, for example, the product, the service provider, the actual service or purchase event, the terms of delivery, the product warranty, and terms of possible return.

The invention can also be applied so that a suitable telephone network element, for example first SCP 1. takes care of attaching identifier 7 to invoicing information 44 received from the selling subscriber, during the call, in which case, first identifier 7 need not be sent to the selling subscriber.

In this application, the term calling-party subscriber refers to the subscriber from whose connection the telephone network receives a request to form a dialled connection to at least one specific connection.

In this application, the term called-party subscriber refers to the subscriber whose connection responds to the calling-party's request to form a connection.

The reference in the Claims to a first telephone connection can be to a calling or called- party connection.

The reference in the Claims to a second telephone connection can be to a calling or called-party connection.

Claims

Claims:

A method for receiving and processing invoicing information on an order placed through a telephone connection, in which method

- invoicing information (8) sent by a first telephone connection (5) is received (106),

- the invoicing information (8) is forwarded (112) to a billing system, to bill a second telephone connection,

characterized in that

- the telephone connection is given an identifier (7),

- the identification data of the first (5) and the second telephone connection (3) and the invoicing information (8) are combined, with the aid of the identifier (7).

2. A method according to Claim 1, characterized in that the invoicing information (8) includes information on the prices/s of the ordered product or service, or of the ordered products or services and/or other information defined by the first subscriber, relating to the ordered product or service, or to the ordered products or services, for instance, a verbal description of the ordered product or service, or products or services, the number of pieces of the products ordered, and their unit prices.

3. Some method according to Claims 1-2, characterized in that a subscriber identifier, such as the telephone number, selected (101) in the second subscriber connection, is transmitted (102) to the service control point SCP (1) of the telephone network, which forms an identifier (7).

4. Some method according to Claim 3, characterized in that the telephone network's SSP centre (4) sends the SCP (1) a command to form an identifier (7), after having received (102) a certain subscriber identifier, such as a telephone number.

5. Some method according to Claims 1-4, characterized in that the identifier (7) of the telephone connection is transmitted (104) on the basis of the subscriber identifier to a selected first subscriber connection (5) as part of the called-party subscriber field, the calling-party subscriber field, or in some other signalling field, e.g., the REDI and/or OCA field.

6. A method according to Claims 1-5, characterized in that the identifier (7) is transmitted (204) to a network terminal device (20) connected to the first subscriber connection (5), by means of an information network, e.g., the Internet.

7. A method according to Claims 1-6, characterized in that the invoicing information (8) is sent (110a) to the server (14) taking care of inter-operator clearing of charges.

8. A method according to Claims 1-7, characterized in that the invoicing information (8) is received (106 - 108, 110-111) identified by an identifier (7).

9. A method according to Claims 1-8, characterized in that

- the billing system receives (107, 110) receives, from the direction of the first telephone connection, invoicing information (8) identified with the identifier (7) of the telephone connection, and containing the sum to be invoiced and a description of the product or service to be invoiced, and the identifying data of the first (5) and second (3) telephone connections

- on the basis of the invoicing information (8), a bill or item for a bill for the second subscriber connection (3) is produced (113), which contains the information contained in the invoicing information (8), such as a description of the product or service to be invoiced.

10. A method for processing the invoicing information of an order placed through a telephone connection and for attaching it to the telephone bill for the second telephone connection, characterized in that

- the billing system (12) receives (107 - 112), from the direction of the first telephone connection (5), invoicing information (8) identified with the identifier (7) of the telephone connection, and which contains the sum to be invoiced and a description of the product or service to be invoiced, and the identifying data of both the first (5) and the second (3) telephone connections, - on the basis of the invoicing information (8), a bill or item for a bill, which includes the information contained in the invoicing information (8), such as a description of the product or service to be invoiced, is produced (113) for the second subscriber connection (3) of the operator.

11. A method according to Claim 10, in which the bill or item for the bill is produced (112 - 113) with the aid of the operator's billing system (12 or 18) and/or the bill is targeted with the aid of customer data of the second telephone connection (3) available to the operator's billing system (12 or 18).

12. A method according to Claims 10-11, characterized in that, on the basis of the invoicing information (8), the operator's billing system (12 or 18) produces (109) a report for the first subscriber connection (5) on the product or service ordered from it and/or credits to it the payment for the ordered product or service.

13. A method according to one of Claims 10- 12, characterized in that the SSP centre (16) receives (11 lb), from the SCP (2), the invoicing information (8) and a command to make a call ticket (19) in a specified form from the invoicing information (8) and/or makes a call ticket (19) in a specified form from the invoicing information (8).

14. A method according to one of Claims 10- 13, characterized in that the invoicing information (8) is received (110b, 110c) from the server (14) taking care of the inter-operator clearing of charges.

15. A method according to one of Claims 10- 14, characterized in that the billing system (12) receives the invoicing information (8) from the subscriber-billing server (23) (207b), the service-provider billing-server (10) (107b), the SSP centre (4) (108c), or the server (14) taking care of the inter-operator clearing of charges.

16. A method according to one of Claims 10- 15, characterized in that

- invoicing information (8) sent by the first telephone connection (5) is received (106), - the invoicing information (8) is forwarded (112) to the billing system (12) for billing the second telephone connection (3),

- an identifier (7) is given (103) to the telephone connection,

- the identifying data of the first and second telephone connections and the invoicing information (8) are combined (206), with the aid of the identifier (7).