Distributed real-time communications system

• US 6,009,457 A
• Filed: 04/22/1996
• Issued: 12/28/1999
• Est. Priority Date: 04/01/1996
• Status: Expired due to Fees

• Current Assignee: Avid Technology Incorporated
• Original Assignee: Rocket Networks, Incorporated (Avid Technology Incorporated)
• Inventors: Moller, Matthew Donaldson
• Primary Examiner(s): Rinehart, Mark H.
• Application Number:
  US08/636,219
• Time in Patent Office: 1,345 Days
• Field of Search: 345/302, 395/200.33, 395/200.35, 395/200.61, 395/200.78, 395/551, 84/645, 84/602, 84/609, 84/610, 84/634, 709/203, 709/205, 709/231, 709/248, 713/400
• US Class Current: 709/203
• CPC Class Codes: G10H 1/0058 Transmission between separate instruments or between individual components of a musical system G10H1/0083 takes precedence
• CPC Class Codes: G10H 2240/175 for jam sessions or musical collaboration through a network, e.g. for composition, ensemble playing or repeating; Compensation of network or internet delays therefor
• CPC Class Codes: G10H 2240/311 MIDI transmission G10H2240/056 takes precedence
• CPC Class Codes: H04L 12/1822 Conducting the conference, e.g. admission, detection, selection or grouping of participants, correlating users to one or more conference sessions, prioritising transmission
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A method and apparatus is provided which enables users to communicate in a perceived real time environment. In one embodiment a number of musical parts are contributed one each from a number of client terminals. Each terminal generates and sends to a server a short sequence or sequence of sequences, for example a few bars of music. The server echoes the sequences out to each of the other clients'"'"' terminals where they are synchronised to a local clock and repeated a plurality of times, with the generated sequence being repeated at the sending client a similar number of times. The local synchronisacion overcomes the problems of propagation delay between clients and server and the repetition of sequences allows a continuous stream of data to be output at each client.

A solo, or non-repetitive line may be added by commencing sending the solo line to the server before the remaining lines. The solo line is buffered at each of the clients and then synchronized to the local clock. The non-solo lines arrive at the solo client after the solo data stream has commenced. However, as they are repetitive they are synchronised by the local clock to the next sequence repeat.

Claims

1. A method for synchronising data from a plurality of sources over a client-server network comprising the steps of:

sending a first start command from the server to a first client to start a local clock at said first client;

sending a continuous stream of data from said first client to said server;

sending a further start command from the server to a plurality of further clients to start a local clock in each of said further clients, said further start command being delayed with respect to said first start command;

sending a sequence of data from each of said plurality of further clients to said server;

sending said continuous data stream from said server to each of said plurality of further clients;

re-synchronising said received continuous data stream at each of said plurality of further clients;

sending the data sequences from said server to each of said plurality of further clients and to said first client;

wherein said step of sending either includes or excludes sending a given data sequence back to a respective further client from which it was sent;

re-synchronising the received data sequences at each of said clients to the local clock; and

repeating the received and locally generated data sequences at each of said clients a plurality of times.

2. A method according to claim 1, wherein one or more of said sequences of data comprises a sequence of sequences of data.

3. A method according to claim 1, wherein each data sequence is representative of a musical instrumental part.

4. A method according to claim 3, wherein one or more of said data sequences is generated by a Musical Instrument Digital Interface (MIDI) device.

5. A method according to claim 4, comprising playing back the received data sequences on said MIDI device.

6. A method according to claim 1, wherein the sequence of data sent by each client co the server comprises data about a sequence of one or more musical notes and includes the relative timing of the note, and other parameters describing the note.

7. A method according to claim 1, wherein the length of each data sequence is variable.

8. A method according to claim 1, wherein the length of the data sequence produced by each client is the same.

9. A method according to claim 1, wherein one or more clients generate a data sequence having a length different to that of said first data sequence.

10. A method according to claim 2, wherein the length of each sequence of said sequence of sequences is the same.

11. A method according to claim 2, wherein the sequences comprising said sequence of sequences have different lengths.

12. A method according to claim 9, wherein the length of each longer sequence is an integral multiple of the length of the shortest sequence.

13. A method according to claim 1, comprising, for each local clock:

setting a beat length; and

on each beat;

a) retrieving a data stream from the server;

b) examining the data stream for data to be played back;

c) outputting the playback data; and

d) repeating steps a) to c) for any remaining data streams.

14. A method according to claim 13, wherein each local clock includes a counter, comprising the step of incrementing the counter every beat.

15. A method according to claim 14, wherein the data sequence sent to each client includes sequence length data, comprising the step of dividing the cumulative count of said counter by the sequence length and determining the present sequence beat from the remainder.

16. Apparatus for synchronizing data from a plurality of sources over a client-server network comprising:

means for sending a first start command from the server to a first client to start a local clock at said first client;

means for sending a continuous stream of data from said first client to said server;

means for sending a further start command from the server to a plurality of further clients to start a local clock in each of said further clients, said further start command being delayed with respect to said first start command;

means for sending a sequence of data from each of said plurality of further clients to said server;

means for sending said continuous data stream from said server the each of said plurality of further clients;

means for re-synchronising said received continuous data stream at each of said plurality of further clients;

means for sending the data sequences from said server to each of said plurality of further clients and to said first client;

means for re-synchronising the received data sequences at each of said clients to the local clock; and

means for repeating the received data sequences at each of said clients a plurality of times.

17. Apparatus according to claim 16, wherein one or more of said sequences of data comprises a sequence of sequences of data.

18. Apparatus according to claim 16, wherein each data sequence is representative of a musical instrumental part.

19. Apparatus according to claim 18, wherein said generating means comprises a Musical Instrument Digital Interface (MIDI) device.

20. Apparatus according to claim 19, comprising means for playing back the received data sequences on said MIDI device.

21. Apparatus according to claim 18, wherein the sequence of data sent by each client to the server comprises data about a sequence of one or more musical noses and includes the relative timing of the note, and other parameters describing the note.

22. Apparatus according to claim 16, wherein the length of each data sequence is variable.

23. Apparatus according to claim 16, wherein the length of the data sequence produced by each client is the same.

24. Apparatus according to claim 16, wherein one or more clients generate a data sequence having a length different to that of said first data sequence.

25. Apparatus according to claim 17, wherein the length of each sequence of said sequence of sequences is the same.

26. Apparatus according to claim 17, wherein the sequences comprising said sequence of sequences have different lengths.

27. Apparatus according to claim 24, wherein the length of each longer sequence is an integral multiple of the length of the shortest sequence.

28. Apparatus according to claim 16, comprising, for each local clock:

means for setting a beat length;

means for retrieving a data stream from the server on each beat;

means for examining on each beat the data stream for data to be played back; and

means for outputting the playback data on each beat.

29. Apparatus according to claim 28, wherein each local clock includes a counter, the apparatus further comprising means for incrementing the counter every beat.

30. Apparatus according to claim 29, wherein the data sequence sent to each client includes sequence length data, the apparatus further comprising means for dividing the cumulative count of said counter by the sequence length and determining the present sequence beat from the remainder.