Method, network and node for levying a tariff against an originator of a data transfer in a telecommunication network

• US 20030125013A1
• Filed: 12/28/2001
• Published: 07/03/2003
• Est. Priority Date: 12/28/2001
• Status: Abandoned Application

• Current Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Kaczmarska, Margaret, Chiu, Mable, Mizell, Jerry L.
• Application Number:
  US10/035,661
• Publication Number:
  US 20030125013A1
• Time in Patent Office: Days
• US Class Current: 455/408
• CPC Class Codes: H04L 12/14 Charging , metering or billing arrangements for data wireline or wireless communications
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/126 the source of the received data
• 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/41 Billing record details, i.e. parameters, identifiers, structure of call data record [CDR]
• CPC Class Codes: H04M 15/70 Administration or customization aspects; Counter-checking correct charges
• CPC Class Codes: H04M 15/73 Validating charges
• 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/22 Bandwidth or usage-sensitve billing
• CPC Class Codes: H04M 2215/32 Involving wireless systems
• CPC Class Codes: H04M 2215/70 Administration aspects, modify settings or limits or counter-check correct charges
• CPC Class Codes: H04M 2215/7072 Validate charges
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 4/24 Accounting or billing

Abstract

A mobile telecommunications network operable to provide data services to a mobile device serviced thereby comprising a first service node, a base station subsystem operable to transmit data to the first service node and receive data from the first service node, the first service node operable to receive a first packet, read a first service marking included therein, perform a first increment to a counter in a first traffic volume container dedicated to a service associated with the first service marking is provided. A node of the network for performing billing procedures on call detail records is also provided. A method of levying a tariff for data delivered from an originator to a terminal device in a telecommunication network comprising reading an identifier in a packet, determining a correspondence with the identifier and the originator of the data, and levying the tariff against the originator is provided.

Claims

1. A method of performing traffic volume accounting in a mobile telecommunication system, the method comprising the steps of:

reading a service marking included in a first packet received by a first node of the telecommunication system; and

performing a first increment to a counter in a first traffic volume container of a call detail record, the first increment indicative of a volume of data in the first packet, the first traffic volume container dedicated to a service associated with the service marking.

2. The method according to claim 1, further comprising opening the first traffic volume container upon determining that no open traffic volume containers in the call detail record are associated with the service associated with the service marking.

3. The method according to claim 1, wherein reading a service marking included in a first packet received by a first node further comprises reading a differentiated service codepoint in the first packet by the first node.

4. The method according to claim 3, wherein reading the differentiated service code point in the first packet further comprises reading the differentiated service codepoint in a transport layer header encapsulated in the first packet.

5. The method according to claim 1, further comprising writing the service marking by the first node of the network into the first packet prior to reading the service marking.

6. The method according to claim 1, further comprising writing the service marking by a second node of the network into the first packet prior to reading the service marking by the first node.

7. The method according to claim 1, further comprising:

receiving a second packet by the first node;

reading a service marking included in the second packet received by the first node;

determining that the service marking included in the second packet corresponds with the service marking read from the first packet; and

performing a second increment to the counter in the first traffic volume container, the second increment indicative of the volume of data in the second packet.

8. The method according to claim 1, further comprising:

reading at least a portion of an embedded tag in the first packet; and

authenticating an originator of the first packet based on contents of the embedded tag, the first traffic volume container dedicated to a context established between a mobile device and the originator.

9. The method according to claim 1, wherein authenticating an originator of the first packet is performed by public key infrastructure.

10. The method according to claim 9, wherein authenticating the originator of the first packet by public key infrastructure further comprises:

decrypting, by the first node, an encrypted hash generated by the originator from a uniform resource locator of a source file and a private key assigned to the originator uniform resource locator, the first packet comprising at least a portion of the source file;

calculating, by the first node, a second hash from the uniform resource locator and a public key assigned to the originator;

comparing the decrypted hash and the calculated hash; and

determining the decrypted hash and the calculated hash are identical.

11. A mobile telecommunications network operable to provide data services to a mobile device serviced thereby, the mobile telecommunications network comprising:

a first service node including an interface to a data network;

a base station subsystem operable to transmit data to the first service node and receive data from the first service node; and

at least one base transceiver station operable to provide radio frequency links to the mobile device, the first service node operable to receive a first packet and read a first service marking included in the first packet, the first service node operable to perform a first increment to a counter in a first traffic volume container of a call detail record maintained in the first service node, the first increment indicative of a volume of data in the first packet, the first traffic volume container dedicated to a service associated with the first service marking.

12. The mobile telecommunications network according to claim 11, wherein the first service node is operable to receive a second packet and read a second service marking included in the second packet, the first service node operable to determine the second service marking is different than the first service marking, the first service node operable to perform a second increment to a second traffic volume container of the call detail record, the second traffic volume container dedicated to a second service associated with the second service marking.

13. The mobile telecommunications network according to claim 11, wherein the first service node is operable to open the first traffic volume container upon determining no open traffic volume containers dedicated to a service associated with the first service marking exist in the call detail record.

14. The mobile telecommunication network according to claim 11, further comprising at least one service node intermediate the first service node and the base station subsystem.

15. The mobile telecommunication network according to claim 11, further comprising a third node intermediate the data network and the first service node.

16. The mobile telecommunication network according to claim 11, wherein the first node is operable to read at least a portion of an embedded tag in the first packet, the first node further operable to authenticate an originator of the first packet based on contents of the embedded tag, the first traffic volume container dedicated to a context established between the mobile device and the originator.

17. The mobile telecommunication network according to claim 16, wherein the fist node authenticates the originator by a public key infrastructure procedure.

18. The mobile telecommunication network according to claim 17, wherein the embedded tag includes an encrypted hash generated by the originator from a uniform resource locator that addresses a file and a private key assigned to the originator, the first packet comprising at least a portion of the file, the first node operable to read at least a portion of the embedded tag from the first packet and decrypt the hash from a public key assigned to the originator, the first node further operable to calculate a hash from the uniform resource locator and the public key assigned to the originator, authentication of the originator made upon determination that the decrypted hash and the calculated hash are identical.

19. A node of a network for performing billing procedures on call detail records, the node comprising:

a processing unit;

a memory unit operable to store a billing algorithm executable by the processing unit; and

an interface to a network medium operable to receive a call detail record thereon, the billing algorithm operable to generate a tariff dependent on contents of a traffic volume container included in the call detail record, the traffic volume container having an identifier of an originator of network traffic associated therewith and maintained in the call detail record, the tariff further dependent on the identifier.

20. The node according to claim 19, wherein the identifier is a uniform resource locator of the originator.

21. The node according to claim 19, wherein the tariff is levied against the originator.

22. The node according to claim 19, wherein the tariff is levied against a terminating device within the network.

23. The node according to claim 22, wherein the terminating device is a mobile terminal.

24. The node according to claim 19, wherein the call detail record include other traffic volume containers, the tariff dependent on the identifier being independent of the other traffic volume containers.

25. A method of levying a tariff for data delivered from an originator to a terminal device in a telecommunication network, comprising:

reading an identifier in a packet;

determining a correspondence with the identifier and the originator of the data; and

levying the tariff against the originator.

26. The method according to claim 25, wherein reading an identifier further comprises reading the identifier embedded within the packet.

27. The method according to claim 25, wherein reading an identifier further comprises reading an embedded tag in the packet, the tag including the identifier.

28. The method according to claim 27, wherein reading an embedded tag further comprises reading the embedded tag including a uniform resource locator associated with the originator.

29. The method according to claim 25, wherein determining a correspondence further comprises indexing a record of a database with the identifier, the correspondence made upon matching the identifier with an identifier in the record.

30. The method according to claim 25, further comprising accumulating a traffic volume count in a call detail record, the traffic volume count indicative of the data volume of the packet.

31. The method according to claim 30, wherein accumulating a traffic volume count further comprises:

opening a traffic volume container in a node of the network; and

incrementing a counter in the traffic volume container.

32. The method according to claim 30, wherein accumulating a traffic volume count further comprises incrementing a counter in an open traffic volume container in a node of the network.

33. The method according to claim 30, wherein accumulating a traffic volume count further comprises accumulating the traffic volume count dedicated to the data transmitted from the originator to the terminal device.

34. The method according to claim 33, wherein accumulating a traffic volume count further comprises accumulating the traffic volume count in the call detail record including a plurality of traffic volume counters, the traffic volume count maintained in a first traffic volume container of the plurality of traffic volume containers, the first traffic volume container dedicated to accumulating a traffic volume count of the data delivered to the terminal device from the originator.

35. The method according to claim 25, further comprising:

accumulating, in a call detail record, a first traffic volume count of the data delivered to the terminal device from the originator, the call detail record including other traffic volume counts;

associating the identifier with the traffic volume count;

transmitting the call detail record to an accounting node; and

parsing, by the accounting node, the traffic volume count from the call detail record, the tariff levied independent of the other traffic volume counts within the call detail record.