Call authorization and billing message routing capability

This application is related to an application of Yigang Cai, Qing Hong He, Min Liu, John B. Reid, Ashish Trevidi, Yile Enoch Wang, and Jay Z. Zhao entitled “Pre-Biller Capability In Enhanced Charging Collection Function (CCF) Applications”, which application is assigned to the assignee of the present application and is being filed concurrently herewith.

This invention relates to methods and apparatus for routing telecommunications authorization, billing, and charging inquiries and responses in a telecommunications network.

After many years of experience in postpaid charging of telecommunications calls, telecommunications service providers and their customers are becoming increasingly interested in real time charging which offers cost control and immediate balance update.

In response to these demands, the new generation of telecommunications systems such as those specified by 3GPP (3rd Generation Partnership Project) and 3GPP2 (3rd Generation Partnership Project 2) have introduced new and highly flexible billing arrangements. These billing arrangements are described in a standards document as Diameter billing arrangements.

In accordance with these Diameter billing arrangements, call authorization and billing services are provided by a group of Diameter servers, which store a customer profile and maintain billing records and account data for their served customers. These servers are accessed (optionally via a Diameter agent), and respond to billing inquiries from calls originated in a network by providing information to the Diameter client process controlling the billing aspects of a call. Because of a need to have a high degree of flexibility in the assignment of identifications of customers and because of the very large volume of billing inquiries and responses, it is necessary to provide a large number of Diameter servers in a network and to provide essentially complete flexibility in the assignment of subscribers to individual Diameter servers.

In accordance with one Diameter billing arrangement, the Diameter client comprises a database for storing the identity of the Diameter Server for serving each subscriber of the network. This arrangement creates problems for keeping all Diameter client databases up to date and in synchronism, and requires a large database in each Diameter client. For both of these reasons, if the number of subscribers served by a Diameter system is large, this arrangement is undesirable.

Accordingly, a problem of the prior art is that there is no efficient system for determining the identity of the Diameter server of a particular customer without incurring a penalty in call setup time of a telecommunications call.

The above problem is alleviated and an advance is made over the teachings of the prior art in accordance with this invention wherein a billing agent for routing billing inquiry messages to the appropriate Diameter server further contains a database for determining the identity of the billing server given only the identity of the subscriber making a call for which a billing inquiry message has been received. Advantageously, such a billing agent which may serve a plurality of billing clients, and can directly process and forward messages without requiring that the messages contain the identity of the Diameter server serving the customer who has originated a call for which a billing inquiry message has been received. The identity of the Diameter server is returned with a billing request response message, so that the billing agent need not determine the identity of the Diameter server in subsequent billing inquiry billing or action messages.

Advantageously, compared with storing a database for identifying the Diameter server for serving each subscriber in each Diameter client, the database is maintained only in the Diameter agent, thus sharply reducing the multiple copies of this database in the many Diameter clients of a network.

FIG. 1 is a block diagram of the prior art Diameter system configuration;

FIG. 2 is a block diagram illustrating the Diameter system configuration in accordance with Applicants' invention; and

FIG. 3 is a flow diagram illustrating Diameter message exchanges in accordance with Applicants' invention.

FIG. 1 is a block diagram illustrating the operation of an authorization, charging and billing system, the Diameter system in accordance with the prior art. Billing and charging functions are initiated from a Diameter client, a software process including data storage for generating Diameter billing request messages and receiving Diameter responses. These responses can influence the action of a telecommunications switch (not shown) associated with the Diameter client, to request establishment of calls and to request disconnect of calls. When the Diameter client 11 receives an initial message representing an originating telecommunications call, the Diameter client queries a subscriber database 12 to determine which of a plurality of Diameter servers 21 , . . . , 23 ; . . . ; 25 , . . . , 27 can serve the subscriber originating the telecommunications call. When the Diameter client receives the identification of the Diameter server from the database 12 , the Diameter client sends a message including the identity of the Diameter server for the subscriber and call to an intermediate Diameter agent 15 which includes a message switch 17 for transmitting the request message to the proper Diameter server. This may be one of the Diameter servers 21 , . . . , 23 directly connected to the Diameter agent or the message may be directed to another intermediate Diameter agent 19 for transmission to one of the Diameter servers 25 , . . . , 27 . The important point to remember is that the Diameter client receives the identification of the Diameter server for this call from the local subscriber database 12 . The Diameter server comprises a database 22 for storing subscriber profiles and billing and account data.

FIG. 2 is a block diagram illustrating the operation of the Diameter system in accordance with Applicants' invention. A change within the Diameter client is noted by having a different designation number ( 211 ) for this client. In accordance with Applicants' invention, the Diameter client sends an initial message which does not contain the identity of the Diameter server for this call to an enhanced Diameter agent 215 . The enhanced Diameter agent still includes a message router 217 but in addition contains a database 219 to identify the Diameter server for a subscriber given the subscriber identification received in the original Diameter request message. The Diameter agent database 219 contains the required information, and the message, including this information is sent to the selected Diameter server, one of the group 241 , . . . , 243 . For subsequent Diameter messages, the identity of the Diameter server serving this call is included in the message so that the database 219 need not be repeatedly accessed for this call. Each Diameter server comprises a subscriber profile database such as database 242 .

The connection between the Diameter client and the Diameter agent and between the Diameter agent and the Diameter server is shown as a direct connection but it can also be a connection established through a data network such as the Internet.

In the Diameter system, messages include a header comprising a command code to identify the purpose of the message, an Attribute/Value pair (AVP) to identify a subscriber, and, if known, a Destination-Host indicator to identify the Diameter server. An original message from the Diameter client would not contain the Destination-Host attribute value pair; the Diameter agent uses the database of the Diameter agent to determine this value from the value of the subscriber number, and routes the message to the Diameter server identified by the Destination-Host indicator.

The response to the original billing request message includes an authorization to establish the call, or a denial of that authorization. Subsequent exchanges between the Diameter client and Diameter server include further authorization or denial indicators.

FIG. 3 is a flow diagram illustrating the operation of Applicants' invention. The Diameter client generates billing request data when a call originates (action block 301 ). The Diameter client sends a Diameter request message which does not include the Diameter server identification to the Diameter agent (action block 303 ). The Diameter agent determines the identity of the Diameter server serving the caller (action block 305 ). The Diameter agent sends the Diameter request message now including the Diameter server identity to the Diameter server (action block 307 ). The Diameter server responds to the Diameter client with a message providing the billing request response data and the Diameter server identity (action block 309 ).

For subsequent messages between the Diameter client and the Diameter server, the Diameter server identity is included in the Destination-Host AVP (action block 311 ); this identity was reported to the Diameter client in action block 309 .

The arrangement described in accordance with Applicants' invention is especially useful for calls requiring real time billing such as calls billed against a prepaid account. However, the arrangement can also be used for billing calls which do not require real time billing in which case the Diameter server performs the conventional postpaid billing function.

While the above preferred embodiment is for 3rd generation telecommunications systems it can also be retrofitted to earlier telecommunications systems; in that case the Diameter server would be a process in a control processor of a switching system.

In accordance with Applicants' invention, the Diameter agent can be further enhanced by a translator 221 to translate between messages of the Diameter system in a first dialect and messages of, for example, the Radius system, in a second dialect. With this arrangement, the Diameter agent and the Diameter servers can also serve subscribers served by the prior art Radius billing and charging system. The Diameter agent 215 receives messages from and to Radius client 251 , and translates these messages into Diameter messages using translator 221 . Thus, a system in accordance with Applicants' invention can also handle legacy equipment using, for example, the Radius system, and not arranged to query a Diameter server.

In this description, it is assumed that the identity of the Diameter server, received in an initial response message, is retained by the Diameter client. This arrangement has the disadvantage that if the identity of the Diameter server changes during a call, the message will be incorrectly routed. It appears that this condition is unlikely, but to protect against it, in an alternate embodiment, the Diameter client does not specify the identity of the Diameter server in subsequent messages to the Diameter agent. If the Diameter agent database includes a cache memory, then subsequent requests to identify the Diameter server can be handled expeditiously.

The above description is of one preferred embodiment of Applicants' invention. Other embodiments will be apparent to those of ordinary skill in the art without departing from the scope of the invention. The invention is limited only by the attached claims.