Computer network multicasting traffic monitoring and compensation

• US 8,060,598 B1
• Filed: 07/01/2002
• Issued: 11/15/2011
• Est. Priority Date: 07/01/2002
• Status: Active Grant

• Current Assignee: T-Mobile Innovations LLC (Deutsche Telekom AG)
• Original Assignee: Sprint Communications Company LP (Deutsche Telekom AG)
• Inventors: Cook, Fred S., Green, Douglas R.
• Primary Examiner(s): WASEL, MOHAMED A
• Application Number:
  US10/186,852
• Time in Patent Office: 3,424 Days
• Field of Search: 709223-229, 709/231, 709/232
• US Class Current: 709/224
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 45/16 Multipoint routing

Abstract

A method is provided for monitoring multicasting traffic in an internetwork between a multicasting source in a first domain and a multicasting destination in a second domain. The multicasting source offers connections to a predetermined multicast stream according to predetermined multicast group information. The multicasting destination sends a join message to a router within the internetwork in order to initiate routing of the predetermined multicast stream to the multicasting destination. A notification of the joining is sent from the router to a ledger application, the notification including identifying information of the multicasting destination and the multicasting source. The multicasting source transmitting datagrams of the predetermined multicast stream to the multicasting destination via the router. The ledger application receives and logs the notification as a transaction event. The transaction events are aggregated in response to the first domain of the multicasting source and in response to the second domain of the multicasting destination, thereby allowing reimbursement of costs between domains for transporting the multicasting traffic.

Claims

1. A method of monitoring multicasting traffic in a network between a multicasting source in a first domain and a multicasting destination in a second domain, wherein said multicasting source offers connections to a predetermined multicast stream according to predetermined multicast group information, said method comprising the steps of:

said multicasting destination sending a join message to a router within said network in order to initiate routing of said predetermined multicast stream to said multicasting destination;

sending a notification of said joining from said router to a ledger application, said notification including identifying information of said multicasting destination and said multicasting source;

said multicasting source transmitting datagrams of said predetermined multicast stream to said multicasting destination via said router;

said ledger application receiving and logging said notification as a transaction event; and

sorting transaction events according to said first domain of said multicasting source and according to said second domain of said multicasting destination, wherein said sorted transaction events identify a reimbursement of costs between domains for transporting said multicasting traffic.

2. The method of claim 1 further comprising the steps of:

said multicasting destination sending a leave message;

said router terminating forwarding of said datagrams to said multicasting destination;

said router sending a leave notification to said ledger application; and

said ledger application receiving and logging said leave notification;

wherein said transaction event is updated in response to a duration of time between said join message and said leave message.

3. The method of claim 1 further comprising the steps of:

said router detecting a termination of interest in said predetermined multicast stream by said multicasting destination;

said router terminating forwarding of said datagrams to said multicasting destination;

said router sending a termination notification to said ledger application; and

said ledger application receiving and logging said termination notification;

wherein said transaction event is updated in response to a duration of time between said join message and said termination notification.

4. The method of claim 1 further comprising the step of:

authenticating said multicasting source in response to said join message, wherein said notification of said joining and said transmission of datagrams to said multicasting destination occur only after successful authentication.

5. The method of claim 1 wherein said network is a private network for a business enterprise having a plurality of subdivisions, said method further comprising the step of:

charging said aggregated transaction events against respective ones of said subdivisions.

6. The method of claim 1 further comprising the steps of:

collecting payment from said first domain according to said aggregated transaction events; and

disbursing payment to said second domain according to said aggregated transaction events.

7. The method of claim 6 wherein said transmission of datagrams includes transport over a backbone network operated by a backbone provider, wherein said ledger application runs in said backbone network, and wherein said collecting and disbursement steps are performed by said backbone provider.

8. A ledger application for executing on a host within a computer network to monitor multicasting traffic in an internetwork between a multicasting source in a first domain and a multicasting destination in a second domain, wherein said multicasting source offers connections to a predetermined multicast stream according to predetermined multicast group information, said ledger application comprising:

means for receiving a notification from a router of a joining of a multicasting destination with said predetermined multicast stream, said notification including identifying information of said multicasting destination and said multicasting source;

means for logging said notification as a transaction event; and

means for sorting transaction events according to said first domain of said multicasting source and according to said second domain of said multicasting destination, wherein the sorted transaction events identify a reimbursement of costs between domains for transporting said multicasting traffic.

9. The ledger application of claim 8 further comprising:

means for receiving a leave notification from said router when said multicasting destination terminates reception of said predetermined multicast stream;

means for logging said leave notification; and

means for updating said transaction event in response to a duration of time between said join notification and said leave notification.

10. A method of operating a multicast-enabled router in an internetwork, said method comprising the steps of:

receiving an enroll message from a destination client requesting receipt of a predetermined multicast content stream from a source server connected to the internetwork;

determining a user identification corresponding to said destination client;

determining a source identification corresponding to said source server;

creating at least a portion of a multicast stream path between said source server and said destination client to include the multicast-enabled router;

sending notification to a ledger application of a transaction event defined by said enroll message, said user identification, and said source identification;

receiving a leave message from the destination client when the predetermined multicast content stream is no longer desired by the destination client; and

sending notification to said ledger application to update said transaction event according to said leave message, whereby a duration between notification of the enroll message and notification of said leave message identifies a cost reimbursement for transporting said multicasting content stream.

11. The method of claim 10 wherein said predetermined content stream is sent as multicast datagrams from said source server and wherein said enroll message is comprised of a join message sent from said destination client to said multicast-enabled router in a multicast group management protocol.

12. The method of claim 10 wherein said predetermined content stream is comprised of licensed content and wherein said enroll message is comprised of a license acknowledgement message sent from said destination client to said source server.