Methods, systems and program products for a distributed communications configuration

• US 8,023,437 B1
• Filed: 06/28/2006
• Issued: 09/20/2011
• 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): Banks Harold; Marsha D
• Assistant Examiner(s): CAMPBELL, MATTHEW T
• Application Number:
  US11/477,169
• Time in Patent Office: 1,910 Days
• Field of Search: 370/260, 370/261, 370/270, 370/229, 370/392, 379/202.01, 709/203, 711/163
• US Class Current: 370/261
• CPC Class Codes: H04L 12/1813 for computer conferences, e.g. chat rooms instant messaging H04L51/04; protocols for multimedia communication H04L65/1101; arrangements for multi-party communication H04L65/403; telephonic conference arrangements H04M3/56; television conference systems H04N7/15

Abstract

One example embodiment of the invention is directed to a method for communicating streaming data between a plurality of users participating in a real-time communications event over a packet based data network. One example method comprises steps of a source identifying a first sink corresponding to a request, the request including at least a method and method parameters, the source using a sink data repository to determine a first sink address corresponding to the first sink, and the source communicating the request to the first sink at the first sink address. Additional steps include a resource executing the method using the parameters and the resource communicating a response to the source following execution of the method.

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 first of the plurality of users using a locator table that resolves request aliases to identify a first sink useful to process a first request, a second of the plurality of users using said locator table to identify said first sink useful to process a second request, a third of the plurality of users using said locator table to identify said first sink useful to process a third request, each of said first, second and third requests including at least a method and one or more method parameters;

said first, second and third users using one or more sink tables that are different from the locator table to determine an address corresponding to said first sink and communicating said first, second and third requests to said first sink;

said first sink performing the steps of;

using a forwarding data depository to identify a second sink useful to execute said first request and forwarding said first request to said second sink;

using a redirect data depository to redirect said second request by communicating a redirect address obtained from said redirect data depository to said second user;

executing said third request by executing said method using said one or more method parameters from said third request and communicating a response to said third user;

whereby each of said users utilizes said first sink to communicate real time audio or video data to one another over the network while participating in the real time communications event, and

wherein said first sink executes a communicated request when said first sink is capable of executing said communicated request, forwards said communicated request when said first sink is not capable of executing said communicated request and information regarding said communicated request is stored in said forwarding table, and uses said redirect data depository when said first sink is not capable of executing said communicated request and information regarding said communicated request is not stored in said forwarding table.

2. A method as defined by claim 1 wherein said first request comprises an alias URL, and wherein said locator table resolves said alias URL to an actual resource URL, and wherein said one or more sink tables correlate said actual resource URL to a memory address.

3. A method as defined by claim 1 wherein said first request comprises an alias URL, and wherein said locator table resolves said alias URL to a plurality of different actual resource URL'"'"'s, and wherein the first of the plurality of users communicates said first request to a second of said plurality of different resource URL'"'"'s following an error response after communicating the resource to a first of said plurality of resource URL'"'"'s.

4. A method as defined by claim 1, wherein:

said third request comprises instructions to record at least one video data stream being communicated during the real-time communications event and includes parameters identifying the at least one data stream, and wherein executing said method of said third request causes said first sink to operate as a recorder and to record the at least one data stream identified by the parameters.

5. A method for communicating streaming data between a plurality of users participating in a video conference over a packet based data network, the method comprising the steps of:

a first of the plurality of users using a locator data depository that resolves request aliases to identify a first sink useful to process a first request, a second of the plurality of users using said locator data depository to identify said first sink useful to process a second request, a third of the plurality of users using said locator data depository to identify said first sink useful to process a third request, each of said first, second and third requests including at least a method and one or more method parameters;

said first, second and third users using one or more sink tables that are different from the locator data depository to determine an address corresponding to said first sink and communicating said first, second and third requests to said first sink;

said first sink performing the steps of;

acting as a filter to forward said first communicated request by recognizing only a portion of a request identifier as corresponding to an entry in a forwarding table that it maintains and using that entry to determine a second sink to communicate said first request to and forwarding said first communicated request to said second sink;

using a redirect data depository that it maintains to determine a redirect address for said second communicated request and communicating said redirect address to said second user communicating said second request;

acting as a resource by executing said third communicated request by executing said method using said one or more method parameters from said third request and communicating a response to said third user communicating said third request;

a fourth of the plurality of users using a second locator data depository to resolve an alias resource corresponding to a fourth request, said second locator data depository identifying at least a third and a fourth sink either of which are useful to process said fourth request, the fourth user communicating said fourth request to said fourth sink following receiving an error message after communicating said fourth request to said third sink;

wherein said first, second, third and fourth sinks partially define a distributed configuration of sinks spread across the network that are used by the first, second, third and fourth users to communicate streaming audio and video data to one another during the videoconference; and

wherein said first sink acts as a resource when said first sink is capable of executing said communicated request, acts as a filter when said first sink is not capable of executing said communicated request and information regarding said communicated request is stored in said forwarding table, and uses said redirect data depository when said first sink is not capable of executing said communicated request and information regarding said communicated request is not stored in said forwarding table.

6. A method as defined by claim 5 wherein said communicated request includes a uniform resource locator.

7. A method as defined by claim 5 wherein the method further includes the steps of:

said first of the plurality of users using said locator table to determine another sink corresponding to another request, said another request including at least a second method and second method parameters;

said first of the plurality of users using said sink table to determine a sink address corresponding to said another sink;

said first of the plurality of users communicating said another request to said another sink; and

,

said another sink acting as a second resource executing said second method and communicating a response to said first of the plurality of users.

8. A method as defined by claim 5 wherein said sink table correlates results from said locator data depository to an IP address for a sink.

9. A method as defined by claim 5 and further comprising said first of the plurality of users communicating a plurality of additional requests to a plurality of additional sinks over the data network, each of said additional sinks maintaining a locally stored individual sink data depository, a locally stored individual forwarding data depository, and a locally stored individual redirect data depository, said plurality of sinks thereby defining a distributed configuration for communicating real time communications data that avoids reliance on any centralized data depositories for forwarding or redirect data;

and,

each of said plurality of additional sinks configured to forward, execute and redirect requests depending on the request.

10. A method as defined by claim 5, wherein said plurality of users is a first plurality of users, said request is communicated between said first of the plurality of users and said first sink using a first protocol that is not Session Initiation Protocol (SIP), and wherein said first sink is a gateway providing an interface facilitating communication between said first plurality of users communicating said request using said first protocol and a second plurality of users communicating requests using a second protocol different from said first protocol, said second protocol being SIP.