FLEXIBLE RATING OF TELECOMMUNICATION CALLS

Abstract: During a telephone or other connection an exchange stores information about charges to be made for that connection. To provide flexible charging the exchange responds to a charge variation request signal (200) to transmit to a party by whom a proposed charge is to be borne a signal requiring acknowledgement (206, 208) and to modify (212, 214) a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received, so as to vary the charging arrangements, for example to invoke a higher rate of charge, or alternatively to change the party by whom charges are to be borne.

Description: Flexible rating of telecommunication calls The present invention relates to telecommunications services and apparatus, and more especially to arrangements for charging for telecommunications services. It is applicable both to telephony based services and to others such as broadband services. Telephone calls and other telecommunications links tend to be charged on a time of day/duration/distance basis where the fee levied is dependent upon the time of day the call is made, the duration of the call and the distance between the parties involved in the call. A number of telephony services are now available which make use of variations to this basic theme through a variety of means. These include called party charging, split called/calling party charging or premium rate charging (where an additional fee is charged on top of the basic "normal" call charge and credited to the called party). Use of these mechanisms has enabled the creation of a number of services both in the UK and elsewhere. However, the arrangements employed hitherto lack flexibility. For example, premium rate calls employ the same pence per minute rate throughout the duration of calls. This means that one can find operators of recorded information services artificially increasing the duration of a call (by giving the information out more slowly than is necessary) in order to recoup the charge they consider appropriate for a particular piece of information. This means that the service operator needs more equipment and lines and of course it is wasteful of his customers' time. According to the present invention there is provided a telecommunications exchange including - a store for storing information as to the cost of a connection - means for storing therein charge information - control means responsive, during a connection in progress, to receipt of a charge variation request signal from a connected party, to (a) transmit to a party by whom a proposed charge is to be borne a signal requiring acknowledgement (b) modify a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received. In another aspect the invention provides a telecommunications network including - a store for storing information as to the cost of a connection - means for storing therein charge information - control means responsive, during a connection in progress, to receipt of a charge variation request signal from a connected party, to (a) transmit to a party by whom a proposed charge is to be borne a signal requiring acknowledgement (b) modify a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received. In a further aspect, the invention provides a method of operating telecommunication network including the steps of: (a) making a connection between a first and a second party; (b) storing information as to the charge to be made for the connection; (c) receiving, during a connection in progress, a charge variation request signal from a connected party; and in response (d) transmitting to a party by whom a proposed charge is to be borne a signal requiring acknowledgement; and (e) modifying a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received. It will be seen that the invention allows the charging of a call to be varied as it progresses, but only with the permission of the party who will bear the charge. For example the called party might request the network operator to vary the charging applied to a received call, whilst it is in progress. Charge variation requests may be issued under a number of circumstances; for example i) to increase/decrease the charge of the call for the rest of the call duration or until subsequently modified, ii) to generate a "one-off" charge/credit against the caller or iii) temporarily increase/decrease the cost of the call for a specific period of time. This mechanism may also be applied in the reverse direction as a means whereby the caller may raise charges against the called party. In order that unscrupulous operators do not mis-use this mechanism, the invention makes provision for the party to whom the charges for the call are to be debited to be automatically alerted by the network prior to the charge variation being invoked. The "charged" party may then have the option to refuse the variation should they so desire. In this case the call will not automatically clear, rather the party requesting charge variation will be informed. The charged party may also hang-up at any point in the call, in which case they will automatically refuse any charge variance negotiation currently taking place. This feature (Charge Variation Request) may be invoked by a number of routes. One possibility, for a normal analogue line, would be for the initiator to invoke a register recall function followed by dialling a special code. Appropriate voice prompts would be played to the distant party during this time to advise them of what was going on and to request acceptance or rejection of the requested charge variation. This they could do by dialling a reply e.g. 1 for accept and 3 for reject. Having received the necessary information, the exchange originating the request would then advise the initiator of the result of the request via a recorded voice message and modify the charging information accordingly. This modification will generally require a signalling message to be transferred to the distant exchange in order that it can modify its charging rate. Some embodiments of the invention will now be described with reference to the accompanying drawings, in which: Figure 1 is a block diagram of a telecommunications network; and Figures 2 to 4 are flowcharts indicating the operation of preferred embodiments of the invention. Figure 1 shows a telephone network which has a large number of digital local exchanges only two of which 1 a, 1 b are shown. Each exchange is connected via concentrators (not shown) and local analogue lines 2 to subscriber terminations illustrated as telephones 3. Each local exchange is also connected via high-speed digital links 4 to two (but optionally one) of a relatively smaller number of digital main switching units (D SU) 5 which together form a trunk network with each DMSU 5 being connected to every other one. Figure 1 also shows the construction of the digital local exchange. Calls are routed by a cross-point switch 10 under stored-program control by a central processing unit (CPU) 1 1 . Telephone calls from a subscriber termination 3 to another such termination on the same local exchange are routed directly by the CPU 1 1 and switch 10 whilst other calls are routed to the DMSU 5 and thence via the trunk network to a destination termination. The CPU 1 1 is able to distinguish between local numbers and trunk numbers by means of a routing table store 1 2 containing stored information indicating which number prefixes are allocated to trunk calls and which to local. The DMSUs 5 may also be linked to other networks for providing additional services, for example a digital derived services network 6 for which provides routing of calls using a numbering system which, because it is unrelated to the topological location of the relevant lines, requires number translation. Such services may also carry differing charge rates, for example (in the UK) "free" (0800) calls (which are charged to the called party) and premium rate (0891 ) calls. Charging for calls is performed by the CPU 1 1 in the local exchange, though there is no reason why the local exchange could not be provided with a separate processing unit to perform this or other tasks ancillary to the main task of routing calls. In this description it is assumed that all charging is performed by the local exchange, though there is no reason why the higher order exchanges could not provide charging facilities, in lieu of the local exchange, for calls which they handle. The way this works is as follows. At the commencement of a call, the CPU 1 1 of the local exchange of the subscriber originating the call records destination information - either the fact that it is a local call, or the dialling code prefix of a non-local call. When the connection is made, the local exchange receives (internally, or from the local exchange of the called subscriber) a "call connected" signal indicating that the latter has answered, and the call commences. At this point a Call Detail Record is set up in an assigned storage area 13 of the CPU 1 1 , with the information set out below; except of course the stop time and duration. These are computed by the CPU at the end of the call and added to the detail record. The charge band information is obtained by reference to a store 14 containing information as to the charging rates according to destination, time of day, day of the week etc. The information contained in the Call Detail Record typically includes the following: Date of call Number of calling subscriber Number called Time of starting of call Time of ending of call Duration of call Charge band code. - although not all of this information is strictly necessary. Upon the termination of the call, the information in the Call Detail Record(s) is transferred to a billing data store 1 5 in the local exchange 1 . This information is transferred on a daily basis to a district data collection centre 7 and thence to a Billing centre 8 where the data may be further processed and bills distributed. If charging rates change at a certain time of day - perhaps calls are cheaper after 6pm - then this can be accommodated by the Billing Centre 8. If for example a call is in progress at 6pm and the relevant Call Detail Record contains an indication that shows that the call is to be charged in charge band a; the Billing Centre will contain stored charging tables giving the pence per minute rates for charge band a and calculate the correct charge accordingly. The charging process as so far described is entirely conventional. The variations now to be described have as their object permitting the changing of the charging arrangements during the course of a call. Possible facilities are: 1 . The charge is made to the called party instead of the calling party; 2. The charge rate is increased (or decreased) for the remainder of the call (or until a further such change is made); 3. A one-off charge is made in addition to the normal call charge. 4. The charge rate is changed for a fixed period of time or until the end of the call, whichever is earlier (this could be achieved by two requests as under (2) above, but has the advantage that the party bearing the charge knows in advance the cost that he is agreeing to); It is envisaged that each of these will be implemented by: (a) One party requesting the change; (b) The other party agreeing to the change; (c) The change being implemented. - though it may well be considered satisfactory for charge reductions to be implemented without the agreement of the party being charged. Similarly, if the person requesting a charge or charge increase is the party against whose account the charge in question is to be made, then the acknowledgement procedure may if desired be dispensed with. Figure 2 is a flowchart illustrating the processes that take place, in the case of a local call, in the CPU of the local exchange 1 a handling the call, in the event that a party A1 makes a call to party A2, and then requests that the cost of the call be charged to party A2. First, party A1 goes off-hook (100) and the exchange responds by setting up the call (102) and sends a ringing signal to party A2 (104). When party A2 goes off-hook (106), this is signalled to the exchange and the connection of the call is complete. The exchange a creates (108) a Call Detail Record in its store 13, with the numbers of party A1 and A2 recorded as the calling and called numbers respectively. Thus far, the process is conventional. The call proceeds (1 10). Suppose now that party A1 wishes the cost of call to be charged to party A2. Any desired form of signal may be employed; currently in the UK, existing services (such as three-way calling) available during the course of a call are set up using the recall signal (a single loop-disconnect signal) followed by a number of digits dialled using multifrequency tone dialling, and for this example the code R#1 5 is assumed. Thus party A1 dials R#15 (1 12). The local exchange CPU 1 1 responds by: (a) playing (1 14) a voice announcement to party A1 - for example using a recorded message unit 1 6 - e.g. "Your request for charge transfer is being processed"; (b) playing (1 1 6) a voice announcement to party A2 requesting permission to make the change, e.g. "The calling party has requested that you are charged for this call. The rate is 1 5p per minute. Please key ' 1 ' to accept or '2' to refuse.". If party A2 keys '2' to send a multifrequency signal back to the exchange, no further action is taken (other than perhaps announcing the refusal to party A1 ); if however he keys ' 1 ' this is recognised by the exchange which responds by: (a) creating (120) a new Call Detail Record identical to the previous one but with the called and calling numbers transposed (b) erasing (122) the original Call Detail Record. Alternatively, if the system is set up so that party A2 becomes responsible only for those call charges incurred after the changeover, then the original Record can be closed, inserting the current time as the finish time (and of course as the start time on the new Call Detail Record). (c) Assuming that the normal network configuration is 'calling party clear' - i.e. the call clears down immediately only when the calling party goes on hook so that the party paying for the call controls when it ends - then this may be reversed ( 1 24) to give control to party A2. (d) Playing (126) a further voice announcement to party A1 confirming that the change has occurred, e.g. "The other party is now paying for the call. " The call then proceeds normally ( 1 28), and assuming control reversal has taken place is terminated by party A2 going on-hook (130) whereupon the exchange clears the connection (132) and writes (134) the Call Detail Record(s) to the store in the usual way. Figure 3 shows the same process, but where the two parties A, B are connected to different local exchanges A, B. Steps equivalent to those in Figure 2 are given the same reference numerals. The process differs in that: Step 1 50: the charge reversal request is forwarded by exchange A to exchange B. Step 1 52: the accept signal is forwarded by exchange B to exchange A. Step 154, 156: exchange A responds to the acceptance by instructing exchange B to set up its own Call Detail Record for the call, naming party B as the calling party: this signal will contain the necessary number, charge band and timing details as exchange B will not previously have recorded such information. Exchange B then reacts by creating the Call Detail Record in its own store 1 3. (Alternatively, if the network is set up to permit an exchange to create charges for other exchanges, exchange A could set up the new record, as in the case of Figure 2). Figure 4 illustrates the implementation of facility 2, again assuming parties A, B, on different local exchanges. The call (originated by party A) is set up in the usual way (steps 100 to 1 10). Suppose party B is providing a recorded information service, and that party A is currently in the course of a dialogue with equipment at party B (for example by recorded announcements played at party B and spoken or keypad responses sent by party A and recognised by party B's equipment - the network being transparent as far as this dialogue is concerned). Suppose further that party A has requested a service (for example the latest stock market figures) for which party B makes a charge. Party B's equipment signals (200) a request for a higher rate call charge to be invoked by transmission of a "R#1 2" signal. It is assumed that the particular charging rate is inherent in this particular code, as also is the fact that the request originates from equipment at party B, other codes being allocated for use by a human operator requesting the same service and for different call rates. Thus exchange B responds by: Step 202: sending a coded (tone) acknowledgement signal to party B. Step 204: forwarding a charging rate increase request signal to exchange A. Exchange A responds to this signal by playing (206) to party A an announcement e.g. "The other party has requested a charging rate of 90 pence per minute. Please key ' 1 ' to accept or '2' to decline.". Assume that party A accepts by (208) keying ' 1 '. The corresponding tone signal is received by exchange A which responds by - 210: sending an accept signal to exchange B - 212: closing the current Call Detail Record by entering the current time and call duration - 214: opening a new Call Detail Record with the current time as the start time. Local exchange B, upon receipt of the accept signal from exchange A, transmits (216) to party B an "Accept" tone, so that party B's equipment can then proceed to play (218) the valuable recorded information. The call continues (220) at the new charge rate, and terminates normally, as previously described. Probably it will be appropriate to revert to the original charge rate after the information has been sent, so step 300 shows party B's equipment sending a signal "R#20", to be interpreted as "resume original rate". This is acknowledged (302) by exchange B and forwarded (304) to exchange A, which responds by: 306 - playing a recorded announcement to party A, e.g. "normal charging resumed". 308 - closing the current Call Detail Record 310 - opening a new Call Detail Record (copying the charging rate from the earliest record held for that call in the store 13). The call continues (312). Further charging rate charges may of course be invoked in the same way. Any convenient arrangements for crediting the party (party B in this example) making the additional charge may, be employed, as with existing 'premium rate' services where the called party receives a proportion of the call charge, for example the charge rate codes inserted into the Call Detail Record may be interpreted by the billing centre 8 as an instruction to credit the called party's account with the appropriate sum. Although not mentioned above, it is envisaged that a party being called upon to authorise a charge rate may decline to accept the change simply by terminating the call. The above description envisages the creation of two or more Call Detail Records for a single call. This has the advantage of compatibility with existing Call Detail Record formats. It may mean, though, that existing billing centre software will list on a bill the separate sections of a call as if they were separate calls: however this could be avoided by arranging for the billing centre 8 to recognise when a Call Detail Record for a given subscriber line (number) has a start time which is the same as the finish time of another such record - a condition which does not normally occur, since it will take at least a second to clear down a call and dial a new one. Upon such recognition the billing centre may process the two records together as desired. This recognition could be facilitated by including in the Call Detail Record a flag to be set by the CPU 1 1 to indicate "further CDR follows". Alternatively a single Call Detail Record could be used, with a variable length format so that it could accommodate multiple entries each with its own start and stop times and charge band indicator. In either case it is assumed that the remote billing centre 8 accommodates any variation in charging rate according to time of day; however it may be necessary to take such variations into account in generating the announcement at step 206 - either by switching between two or more alternative announcements under control of a local clock, or by quoting the different rates in the announcement itself. In the event that facility 3 is desired (a single charge), then the process would proceed as depicted in Figure 4 down to step 220 save that step 21 would be replaced by two steps. (a) Create a complete new Call Detail Record bearing the one-off charge (say, £3) - either as a record with zero call duration and fixed charge of £3 or, if this is more convenient to fit in with existing billing mechanisms, a record with a short call duration, for example of 1 second and a charging rate of £3 per second. (b) Create a new Call Detail Record for the continuation of the call. For facility 4 (new charge rate only for a specified period) the procedure would be as in Figure 4 down to step 220, but exchange A would be programmed to set a timer for the relevant period (different codes at step 200 being used for different periods), and respond on timeout by automatically performing steps 306- 310. The above description assumes that additional call charges are raised because of services (information) being supplied over the telephone (or other) connection in question. However it is not essential that this is so, for example the call may be associated with a related application such as a pay-per-view cable TV offering where a customer dials up the TV service using a telephony call. The above mechanism could be used to accept the charges for the selected film/programme from the TV service provider, causing the appropriate telephone bill to be debited, even though the actual service which is being paid for is not transmitted over the telephony connection. Other mechanisms may be applicable, such as use of the Analogue Display Screen Interface for communicating charge variation alerts, requests and acknowledgements. Similarly, other network access arrangements may be used for example ISDN basic/primary rate access, or similar, where the appropriate messages may be transmitted using common channel signalling between the terminal equipment and the network. Finally it is noted that certain steps referred to above may require appropriate message facilities in digital inter-exchange signalling and will require the allocation of new codes within any existing inter-exchange signalling protocol (e.g. C7).

Claims: C Δ1MS 1 . A telecommunications exchange including - a store for storing information as to the cost of a connection - means for storing therein charge information - control means responsive, during a connection in progress, to receipt of a charge variation request signal from a connected party, to (a) transmit to a party by whom a proposed charge is to be borne a signal requiring acknowledgement (b) modify a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received. 2. A telecommunications network including - a store for storing information as to the cost of a connection - means for storing therein charge information - control means responsive, during a connection in progress, to receipt of a charge variation request signal from a connected party, to (a) transmit to a party by whom a proposed charge is to be borne a signal requiring acknowledgement (b) modify a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received. 3. A telecommunications exchange or network according to claim 1 or claim 2, in which the control means is operable to send, upon receipt of the acknowledgement, a confirmation signal to the requesting party. 4. A telecommunications exchange or network according to any one of the preceding claims, including voice announcement means and in which the signal requiring acknowledgement and/or the confirmation signal is a voice signal representing a spoken message. 5. A telecommunications exchange or network according to any one of the preceding claims in which the control means is responsive to an assigned request signal for a charge reversal (a) so to modify the store contents that charges to the party currently being charged shall be cancelled, or shall cease; and (b) so to modify the store contents that another party shall bear respectively the charges, or the further charges, for the connection. 6. A telecommunications exchange or network according to any one of the preceding claims in which the control means is responsive to an assigned request signal for a charge reversal (a) so to modify the store contents that charges to the party currently being charged shall be cancelled, or shall cease (b) to transmit to another exchange participating in the connection a request that that other exchange generate charge information. 7. A telecommunications exchange or network according to any one of the preceding claims in which the control means is operable in response to an assigned request signal for charge rate modification so to modify the store contents that the charging rate for continuation of the call shall be different from that obtaining prior to the receipt of that request signal. 8. A telecommunications exchange or network according to claim 8 in which the control means is operable in response to an assigned request signal for temporary charge rate modification so to modify the store contents that the charging rate for continuation of the call shall for a specified period or for the remainder of the call if shorter be different from that obtaining prior to the receipt of that request signal. 9. A telecommunications exchange or network according to any one of the preceding claims in which the control means is operable in response to an assigned request signal for a single charge so to modify the store contents that an additional charge shall be made. 10. A method of operating a telecommunication network including the steps of: (a) making a connection between a first and a second party; (b) storing information as to the charge to be made for the connection; (c) receiving, during a connection in progress, a charge variation request signal from a connected party; and in response (d) transmitting to a party by whom a proposed charge is to be borne a signal requiring acknowledgement; and (e) modifying a respective portion of the store contents relating to said connection in progress only if such an acknowledgement is received.

Inventors: ANDERSON JOHN ROLAND, SWALE RICHARD PAUL, ANDERSON, JOHN, ROLAND, SWALE, RICHARD, PAUL
Applicants: ANDERSON JOHN ROLAND, BRITISH TELECOMM, SWALE RICHARD PAUL, ANDERSON, JOHN, ROLAND, BRITISH TELECOMMUNICATIONS PUBLIC LIMITED COMPANY, SWALE, RICHARD, PAUL
Application year: 1995
Main classification: H04M15
IPC codes: H04M15