Charging in telecommunications network

• US 20040152444A1
• Filed: 11/25/2003
• Published: 08/05/2004
• Est. Priority Date: 05/28/2001
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Lialiamou, Helen, Ilama, Vesa
• Granted Patent: US 7,889,662 B2
• Time in Patent Office: Days
• US Class Current: 455/406
• CPC Class Codes: H04L 12/1403 Architecture for metering, charging or billing
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04M 15/00 Arrangements for metering, time-control or time indication ; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP
• CPC Class Codes: H04M 15/31 Distributed metering or calculation of charges
• CPC Class Codes: H04M 15/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/43 Billing software details
• CPC Class Codes: H04M 15/56 for VoIP communications
• CPC Class Codes: H04M 15/63 based on the content carried by the session initiation protocol [SIP] messages
• CPC Class Codes: H04M 15/7655 shared by technologies
• CPC Class Codes: H04M 15/77 involving multiple accounts per user
• CPC Class Codes: H04M 15/772 per service, e.g. prepay or post-pay
• CPC Class Codes: H04M 15/80 Rating or billing plans; Tariff determination aspects
• CPC Class Codes: H04M 15/8292 Charging for signaling or unsuccessful connection
• CPC Class Codes: H04M 2215/0152 General billing plans, rate plans, e.g. charge rates, numbering plans, rate centers, customer accounts
• CPC Class Codes: H04M 2215/0164 Billing record, e.g. Call Data Record [CDR], Toll Ticket[TT], Automatic Message Accounting [AMA], Call Line Identifier [CLI], details, i.e. parameters, identifiers, structure
• CPC Class Codes: H04M 2215/202 VoIP; Packet switched telephony
• CPC Class Codes: H04M 2215/2026 Wireless network, e.g. GSM, PCS, TACS
• CPC Class Codes: H04M 2215/204 UMTS; GPRS
• CPC Class Codes: H04M 2215/22 Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/32 : Involving wireless systems
• CPC Class Codes: H04M 2215/725 : Shared by technologies, e.g. one account for different access technologies
• CPC Class Codes: H04M 2215/7254 : Multiple accounts per user
• CPC Class Codes: H04M 2215/7263 : per service, e.g. prepay and post-pay
• CPC Class Codes: H04M 2215/96 : Distributed calculation of charges, e.g. in different nodes like for mobiles between HLR and VLR, or between the terminal and the billing function
• CPC Class Codes: H04W 24/00 : Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 24/10 : Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 4/24 : Accounting or billing

Abstract

A method and a system for collecting session-specific event data in a tele-communications network where sessions are connected through a number of network entities which generate event data and have mutual signaling con-nections. The objective of the invention is to provide a solution whereby event detail records relating to one session but generated by a number of different network entities are sent in a centralized manner in real-time to a given collecting network entity. Thus, the event data combination is optimized and the unnecessary transmission of event detail records from one collecting network entity to another is avoided.

Claims

1. A method for collecting session-specific event data in a network where user connections during a session are connected through a number of network entities generating event data and having a mutual signaling connection,

characterized by the steps of

storing in each of the network entities generating event data a set of addresses for the network entities collecting event data,

during connection set-up

choosing one address of a collecting network entity from the set in each of the event data generating a network entity,

and during the connection

sending event data which is being generated during the connection to the network entity chosen.

2. A method according to claim 1, characterized in that the address of the collecting entity is globally unique.

3. A method according to claim 1, characterized in that during the connection set-up a predetermined network entity receives a session/connection establishment request, selects the said address from the set, and indicates it to the other network entities generating event data by inserting the address in the signaling messages which it sends during the connection set-up.

4. A method according to claim 3, characterized in that a globally unique identifier pertaining to the said session is inserted in the said message.

5. A method according to claim 3 or 4, characterized by

receiving a signaling message including the said address,

comparing the said address with a primary address of the set, and if the addresses compared are equal,

sending the message to the next network entity, whereby said receiving and comparing steps are performed in the network entity which generates event data.

6. A method according to claim 3 or 4, characterized by

receiving a signaling message including the said address,

comparing the said address with a primary address in the set, and if the addresses compared fail to correspond to each other,

replacing the received address with the primary address selected from the set and sending the message to the next network entity, whereby said receiving and comparing steps are performed in the network entity which generates event data.

7. A method according to claim 1, characterized in that the network entity is a network element.

8. A method according to claim 1, characterized in that the network entity is a user terminal.

9. A method according to claim 1, characterized in that the content of the set is identical at least in the network entities within the same domain.

10. A method according to claim 1, characterized in that the content of the set is identical at least in the network entities within the same network.

11. A method according to claim 1, characterized in that the stored set of addresses of the network entities generating the event data is in the form of a table.

12. A method according to claim 1, characterized in that the event data includes charging data.

13. A communication system comprising at least the routing network entities and the network entities generating the event data and the network entities collecting the event data,

characterIzed in that each of the event data generating network entities includes

a set of addresses for the network entities collecting event data,

selecting means for choosing from the set one address of a collecting network entity,

signaling means for signaling selected addresses between network entities generating event data,

sending means for sending event data generated during a session to the address chosen by the selection means.