Methods, systems and program products for efficient communications during data sharing event

• US 8,144,632 B1
• Filed: 09/25/2007
• Issued: 03/27/2012
• Est. Priority Date: 06/28/2006
• Status: Active Grant

• Current Assignee: Iocom UK Limited
• Original Assignee: inSORS Integrated Communications, Inc.
• Inventors: Chapweske, Adam M., Swanson, Jon N.
• Primary Examiner(s): Pezzlo, John
• Assistant Examiner(s): CAMPBELL, MATTHEW T
• Application Number:
  US11/903,915
• Time in Patent Office: 1,645 Days
• Field of Search: 370/260, 370/261, 370/236, 379/202.01, 709/204
• US Class Current: 370/261
• CPC Class Codes: H04L 12/1827 Network arrangements for conference optimisation or adaptation
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04M 3/567 Multimedia conference systems
• CPC Class Codes: H04N 7/15 Conference systems

Abstract

One example embodiment of the invention is a method for communicating streaming data between a plurality of users participating in a real-time communications event over a packet based data network, the method comprising the steps of: a source identifying a first sink corresponding to a request, the request including at least a method, one or more method parameters, and a time to live value; the source using a sink data repository to identify a first sink address corresponding to the first sink, the sink data repository comprising sink addresses for a plurality of different sinks; the source communicating the request to said first sink; and, the first sink returning an error message if the time to live has expired, and if the time to live has not expired the first sink processing the request through one or more steps of: acting as a resource by executing the method using the method parameters and communicating a response to the source; acting as a filter by forwarding the request to a second sink; and, redirecting the request back to the source for communicating to a second sink.

Claims

1. A method for communicating streaming data between a plurality of users participating in a real-time communications event over a packet based data network, the method comprising the steps of:

a source using a locator table that correlates a plurality of requests to a plurality of different sinks to identify a first sink corresponding to a request to join a video conference, said request including at least a method, one or more method parameters, and a time to live value;

said source using a sink data repository to identify a first sink address corresponding to said first sink, said sink data repository comprising sink addresses and associated latency values for a plurality of different sinks, wherein said identified first sink address is selected so that said latency value associated with said identified first sink address satisfies said time to live value;

said source communicating said request to said first sink;

said first sink returning an error message if said time to live has expired, and if said time to live has not expired said first sink processing said request through one or more steps of;

acting as a resource by executing said method using said method parameters and communicating a response to said source, wherein executing said method includes connecting said source with a plurality of other sources at a conference bridge, each of said sources communicating real time streaming video and audio data to one another over said bridge whereby said plurality of sources conduct a video conference;

acting as a filter by forwarding said request to a second sink; and

,

redirecting said request back to said source for communicating to a second sink;

said source transmitting a reserve request to one or more of said first sinks, said reserve request including a maximum amount of latency and a time frame; and

said one or more first sinks receiving said reserve request and returning a success response if said sink can provide a latency that satisfies said maximum latency value for said time frame, and otherwise returning a failure response.

2. A method as defined by claim 1 and wherein the step of said first sink processing said request includes one of the steps of:

said first sink reducing said time to live value if said time to live value is an amount of time, and if said time to live value is an elapsed time said first sink estimating downstream delay time between it and a node, said first sink reducing said time to live value by said downstream delay time, and said first sink forwarding said request to said node.

3. A method as defined by claim 1 wherein the step of said first sink processing said request includes:

said first sink using a second sink data repository to determine a sink address for a second sink, said second sink located on a different computer than said first sink, said first sink acting as a filter by forwarding said request to said second sink at said second sink address; and

wherein said second sink returns an error message to said source if said time to live has expired and processes said request if said time to live has not expired.

4. A method as defined by claim 1 wherein said request comprises a first request, and further including the step of said sink receiving a second request including a time to live value, and wherein said sink processes the one of said first and second requests having the smaller time to live value before the other of said first and second requests.

7. A method as defined by claim 1, wherein said packet based data network is synchronized and said time to live value is a clock time, and further wherein said time to live value has expired if said time to live value exceeds an actual clock time, otherwise said time to live value has not expired.

8. A method as defined by claim 3, wherein said request comprises a first request, and further including a step of said second sink receiving a second request having a time to live value, and wherein said second sink processes the one of said first and second requests having the smaller time to live value before the other of said first and second requests.

9. A method as defined by claim 1, wherein said first sink forwarding said request to a second sink further comprises:

said first sink determining a plurality of target second sinks to which said request could be forwarded;

said first sink estimating a latency of each of said plurality of target second sinks; and

said first sink forwarding said request to a one of the plurality of target second sinks having the smallest estimated latency.

5. A real time communications system for conducting a real-time communications sharing event between a plurality of users over a synchronized packet based data network, the system comprising a plurality of computers linked to one another for communication with one another, and further comprising:

a plurality of sources linked to the network configured to communicate requests, each of said requests including at least a method and a time to live value, one each of said sources corresponding to one each of the users;

a plurality of first nodes distributed across a plurality of the computers, each of said first nodes configured to receive requests, to execute said method contained in said request and to communicate a response following execution of said method if said time to live value has not expired, and configured to communicate an error message if said time to live value has expired, at least one of said first nodes receiving a request and executing said request;

a plurality of second nodes distributed across a plurality of the computers, said second nodes configured to receive requests and to forward said requests to said first nodes if said time to live value has not expired and to return an error message if said time to live value has expired;

wherein said plurality of first nodes and second nodes collectively are configured as a distributed configuration for conducting a real time communications sharing event on the network whereby each of the plurality of users may communicate real time streaming data to each of the other users,

wherein each of said plurality of sources is configured to communicate a reserve request, specifying a maximum amount of latency and a time frame, and each of said first and second nodes is configured to return a success response if the node can guarantee a latency below the specified amount of latency during the specified time frame, otherwise the node returns a failure response, and

wherein said time to live value is a clock time, said time to live value has expired if an actual clock time exceeds said time to live value clock time, otherwise said time to live value has not expired.

6. A real time communications system as defined by claim 5 and further comprising:

a plurality of sink data depositories, each of said sink data depositories including address data for a plurality of said first and second nodes, each of said sources, said first nodes and said second nodes having access to at least one of said plurality of sink data depositories;

a plurality of forwarding data depositories, each of said forwarding data depositories including a address data for a plurality of said first and second nodes correlated to said requests, at least each of said second nodes having access to at least one of said plurality of forwarding data depositories;

a plurality of redirect data depositories, each of said redirect data depositories including address data for a plurality of said first and second nodes correlated to said requests, at least a portion of said first and second nodes having access to at least one of said redirect data depositories; and

,

wherein at least a portion of said first and second nodes are configured to function as both first and second nodes, and wherein at least a portion of said first nodes are redundant with one another whereby a particular request may be executed by any of said redundant first nodes, and wherein one of said second nodes when forwarding said particular request selects the one of said redundant first nodes that will result in the least delay.

10. A real time communications system as defined by claim 5, wherein one of said first nodes receives a first request having a first time to live value and a second request having a second time to live value, and wherein said one of said first nodes executes the one of said first and second requests having a time to live value nearer to said actual time before executing the other of said first and second requests.

11. A real time communications system as defined by claim 5, wherein each of said plurality of second nodes identifies a plurality of target first nodes to which a received request could be forwarded, estimates a latency for each of said plurality of target first nodes, and forwards said request to a one of the plurality of target first nodes having the smallest estimated latency.

12. A real time communications system as defined by claim 6, wherein each said sink data depository further includes an estimated latency value associated with said address data for each of said sources, said first nodes and said second nodes, and wherein a destination address for each said requested is selected such that said latency value associated with said destination address satisfies said time to live value of said request.

13. A method for communicating streaming data between a plurality of users participating in a real-time communications event over a packet based data network, the method comprising the steps of:

a source identifying a first sink corresponding to a first request using a locator table that correlates a plurality of first requests to a plurality of different sinks, said first request including at least a method, one or more method parameters, and a time to live value;

said source using a sink data repository to identify a first sink address corresponding to said first sink, said sink data repository comprising sink addresses and associated latency values for a plurality of different sinks, wherein said identified first sink address is selected so that said latency value associated with said identified first sink address satisfies said time to live value;

said source communicating said first request to said first sink; and

,

said first sink returning an error message if said time to live has expired, and if said time to live has not expired said first sink processing said first request through one or more steps of;

acting as a resource by executing said method using said method parameters and communicating a response to said source;

acting as a filter by determining a plurality of target second sinks to which said first request could be forwarded, estimating a latency of each of said plurality of target second sinks, and forwarding said first request to a one of the plurality of target second sinks having the smallest estimated latency by using a second sink data repository to determine a sink address for the second sink having the smallest latency; and

redirecting said first request back to said source for communicating to a second sink,

wherein when said source transmits a reserve request including a maximum amount latency value and a time frame to one or more of said different sinks, said one or more first sinks return a success response if said sink can provide a latency lower than said maximum latency value for said time frame, and otherwise returning a failure response,

wherein said first request comprises a request to join a video conference, and wherein the step of processing said first request comprises connection of said source with a plurality of other sources at a conference bridge, each of said sources communicating real time streaming video and audio data to one another over said bridge whereby said plurality of sources conduct a video conference.