Multicasting method and apparatus

1. Field of the invention

This relates to a method and apparatus for providing audio and/or visual communication services, in real-time to a multiplicity of identifiable users on a communications network, such as the Internet. In a preferred embodiment, the invention monitors which users are receiving signals on which one of a plurality of channels and modifies the content of at least some signals in response thereto. A particular application is to provide services akin to multi-channel radio or television with commercial programming content adjusted in accordance with the identity of the individual user.

2. Background of the Invention

Systems such as the Internet typically are point-to-point (or unicast) systems in which a message is converted into a series of addressed packets which are routed from a source node through a plurality of routers to a destination node. In most communication protocols the packet includes a header which contains the addresses of the source and the destination nodes as well as a sequence number which specifies the packet's order in the message.

In general, these systems do not have the capability of broadcasting a message from a source node to all the other nodes in the network because such a capability is rarely of much use and could easily overload the network. However, there are situations where it is desirable for one node to communicate with some subset of all the nodes. For example, multi-party conferencing capability analogous to that found in the public telephone system and broadcasting to a limited number of nodes are of considerable interest to users of packet-switched networks. To satisfy such demands, packets destined for several recipients have been encapsulated in a unicast packet and forwarded from a source to a point in a network where the packets have been replicated and forwarded on to all desired recipients. This technique is known as IP Multicast Backbone or MBONE. More recently, routers have become available which can route the multicast addresses (class D addresses) provided for in communication protocols such as TCP/IP and UDP/IP. A multicast address is essentially an address for a group of host computers who have indicated their desire to participate in that group. Thus, a multicast packet can be routed from a source node through a plurality of multicast routers (or mrouters) to one or more devices receiving the multicast packets. From there the packet is distributed to all the host computers that are members of the multicast group.

These techniques have been used to provide on the Internet audio and video conferencing as well as radio-like broadcasting to groups of interested parties. See, for example, <nplcit id="ncit0001" npl-type="b"><text>K. Savetz et al. MBONE Multicasting Tomorrow's Internet (IDG Books Worldwide Inc., 1996</text></nplcit>).

Further details concerning technical aspects of multicasting may be found in the Internet documents Request for Comments (RFC) 1112 and 1458 which are reproduced at Appendices A and B of the Savetz book and <nplcit id="ncit0002" npl-type="s"><text>D.P. Brutaman et al., "MBONE provides Audio and Video Across the Internet," IEEE Computer, Vol. 27, No. 4, pp. 30 - 36 (April 1994</text></nplcit>). A further example may be found in <patcit id="pcit0001" dnum="WO9515658A"><text>WO95/15658</text></patcit> (Discovery Communications Inc.). <patcit id="pcit0002" dnum="WO9515658A"><text>WO95/15658</text></patcit> relates to a network manager that monitors and manages cable headend components and set top terminals in a television delivery system. Another example may be found in <patcit id="pcit0003" dnum="EP0617563A"><text>EP 0617563, 28th September 1994</text></patcit> (1994-09-28), in which a data processing system is described for providing on-demand video information on subscriber demand, for very large video data files. The system enables rapid response to the requests by network subscribers, independent of the number of video files offered for selection.

3. Summary of the Invention

The present invention relates to a method and system for metering real-time streaming media for commercial purposes according to the appended claims.

The present invention is scalable architecture for delivery of real-time information over a communications network. Embedded into the architecture is a control mechanism that provides for the management and administration of users who are to receive the real-time information.

In the preferred embodiment, the information being delivered is high-quality audio. However, it could also be video, graphics, text or any other type of information that can be transmitted over a digital network. This information is delivered in real-time to any number of widely distributed users. It is real-time in that for a given channel of information, approximately the same information is being sent at approximately the same time to everyone who is enabled to receive the information.

Preferably, there are multiple <i>channels</i> of information available simultaneously to be delivered to users, each channel consisting of an independent stream of information. A user chooses to tune in or tune out a particular channel, but does not choose the time at which the channel distributes its information. Advantageously, interactive (two-way) information can be incorporated into the system, multiple streams of information can be integrated for delivery to a user, and certain portions of the information being delivered can be tailored to the individual user.

4. Brief Description of the Drawing

These and other objects, features and advantages of our invention will be more readily apparent from the following Detailed Description of a Preferred Embodiment of our invention in which <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Fig. 1</figref> is a schematic diagram depicting an overview of the system of the present invention;</li><li><figref idref="f0002">Fig. 2</figref> is a schematic diagram depicting the network control center for the system of <figref idref="f0001">Fig. 1</figref>;</li><li><figref idref="f0003">Fig. 3</figref> is a schematic diagram depicting a unicast distribution structure;</li><li><figref idref="f0004">Fig. 4</figref> is a schematic diagram depicting a multicast distribution structure;</li><li><figref idref="f0005">Fig. 5</figref> is a schematic diagram depicting the connection between the media server and the user in the system of <figref idref="f0001">Fig. 1</figref>;</li><li><figref idref="f0006 f0007 f0008 f0009 f0010 f0011 f0012 f0013 f0014 f0015 f0016 f0017 f0018 f0019 f0020 f0021">Figs. 6-17</figref> are timing diagrams which depict various aspects of the operation of the system of <figref idref="f0001">Fig. 1</figref>; and</li><li><figref idref="f0022">Figs. 18</figref> and <figref idref="f0023">19</figref> depict the user interface for control of the system of <figref idref="f0001">Fig. 1</figref>.</li></ul>

Where the same reference numerals appear in multiple drawings, the numerals refer to the same or corresponding structure in such drawings.

5. Detailed Description of the preferred Embodiment

Referring to <figref idref="f0001">Fig. 1</figref>, the system of the present invention comprises a Network Control Center 10, a plurality of Primary Servers 20, Media Servers 30, Users 40 and Control Servers 50 and an Administration Server 60. The servers are interconnected by a communications network, which in the preferred embodiment is the global connected internetwork known as the <i>Internet</i>. The Network Control Center 10 is the source of the information being distributed. It receives audio feeds from satellite, over the <b>air</b> broadcast or in other ways and processes this information for delivery over the network on multiple channels of information. This processing consists of optionally recording the information for future broadcast and dynamically inserting paid commercial advertisements.

For each channel of information, there is a Primary Server 20 that receives the stream of information from the Network control Center 10 and compresses the information stream to allow for more efficient transmission. The Primary Servers 20 are directly connected to the network.

The Primary Servers forward information via the network to a number of Media Servers 30. There may be a large number of Media Servers and in fact there may be many levels of Media Servers. For example, a Media Server which receives a stream of information from a Primary Server may forward that stream via the network to another Media Server which then forwards it to a User 40. This multilevel hierarchical structure is described in more detail below.

The topology of the Internet dictates the ideal placement of Media Servers, the fan-out of each Media Server and the number of levels of Media Servers between the Primary Server and Users. For example, the Media Servers which feed from a Primary Server might be placed at a major points of presence (POPs) of each of the large Internet service providers. These Media Servers might also be placed near clouds which serve as high bandwidth exchange points between the major carriers. Similarly, Media Servers which feed to Users might be placed on or close to networks which have a large number of subscribers to minimize the distance and number of data streams being transmitted.

Control Servers 50 are responsible for keeping track of which Users are listening to which channels and for directing the Media Servers to start and stop streams of information to those Users. The Control Servers are also responsible for handling other interactions among the various components of the system as will be described in more detail below. Each Control Server is responsible for managing a <i>cluster</i> of Media Servers; and each Media Server is managed by a single Control Server at any given time. As a result, the control Servers are distributed throughout the Internet, preferably located close to the Media Servers.

The Administration Server 60 is responsible for registering new Users, authenticating Users who want to log onto the system, and maintaining audit logs for how many Users are listening to which channels and at which times. Maintaining audit logs and gathering statistics are features critical to monitoring the delivery of paid commercial messages as well as for other purposes. For example, for purposes of assessing copyright royalties, the audit logs can record the number of listeners for each musical or video selection that is distributed by the system. Another application is to determine the percentage of listeners who are interested in listening to a particular musical selection by determining how many listen to the entire selection and how many turn it off.

The system of the present invention can be considered a distribution architecture integrated with a control architecture. The distribution architecture handles scalable real-time delivery of information to any number of Users on a packet switched network, such as the Internet. The control architecture represents a second scalable system integrated with the distribution architecture for managing and administering the delivery of that information.

The remainder of this description is divided into three sections. In the next section the distribution architecture will be described in more detail. Following that, the control architecture will be described. In the third section the User interface will be illustrated.

I. Distribution Architecture

The distribution architecture provides for the delivery of real-time information to any number of Users distributed throughout a network. As will be described in detail below, the distribution architecture is scalable to allow for efficient delivery of multiple simultaneous information channels in real-time to a large number of Users.

In the preferred embodiment, the information which is being distributed consists of high-quality audio in addition to other information. It should be appreciated that the basic architecture and other general principles set forth herein would also apply to the delivery of video, graphics, text or any other type of information that can be delivered over a digital network. In addition, it should be appreciated that an information stream can consist of audio with supplemental information such as text and graphic images and commands to control software running on the User's computer.

The source of information in the preferred embodiment is the Network Control Center 10, depicted in the schematic diagram of <figref idref="f0002">Fig. 2</figref>. Control Centers of this type of design are available from Broadcast Electronics, Inc. and are similar to what would be found in a conventional radio station serving multiple frequencies.

Referring to <figref idref="f0002">Fig. 2</figref>, the incoming signal can be received in a variety of ways such as from a satellite, over-the-air broadcast, cable or hard disk. It is then processed by Receiver/Decoder 110, which decodes the signal and provides an incoming audio stream. Routing Switcher 120 is responsible for routing the incoming audio feed from the Receiver to either Delay Recording Workstation 140 or to one of the Playback/Control Workstations 130. Real-time insertion of paid commercial advertising takes place at the Playback/Control Workstations and the resulting integrated audio stream is delivered to the Primary Servers. The Delay Recording Workstation is responsible for recording an incoming broadcast so that it can be played back at a later time.

Supervisory Workstation 150 is responsible for managing and controlling the Playback/Control Workstations, Delay Recording Workstations and other computers as may be connected to the local area network within the Network Control Center. Production Workstation 160 and AudioVAULT-NFS Server 170 are used to manipulate audio samples, such as commercial messages for use by the Playback/Control Workstations. The audio being delivered can consist of syndicated TV or radio programs, such as would be received over satellite or cable and delivered as described above. These can be delivered live and/or played back at a later time. It is also possible for the delivery of information, such as music, to take place from information that is all stored locally such as on a hard disk. A new play list and its associated music data can then be downloaded periodically to update the channel. Additionally, it is possible to deliver commercial-free programming, for example public service announcements or label-specific music.

In the preferred embodiment the Primary Servers are responsible for compressing the audio stream using an advanced perceptual technique developed and licensed by AT&amp;T Corp. and Lucent Technologies, Inc. This highly sophisticated algorithm is used to maximize the benefit of the bandwidth available. Advantageously, two bitrates are available, a first rate of approximately 2 OKbps and a second rate of approximately 56Kbps. Using the perceptual technique, the quality of the first rate is similar to FM monaural (with a sampling rate of approximately 22,000 16-bit samples per second) and the second rate is close to CD quality stereo (with a sampling rate of approximately 32,000 16-bit samples in stereo each second). The signals at the two different bitrates comprise two different audio channels and thus require two different compression processes.

The computational requirements of compressing an audio stream in real time using techniques such as the advanced perceptual technique are approximately 100% of a Pentium-Pro 200Mhz computer and the computational requirements of decompressing an audio stream in real time are approximately 30% of a Pentium 75Mhz computer. Future improvements and/or changes to the algorithm could significantly change these requirements. For the present, a dedicated computer is required within the Primary Server to compress the audio stream. The decompression process takes place on end Users' computers and preferably would use only a portion of the computers' computational requirements, allowing the computers to be used for other tasks while they are processing the audio stream.

It is important to appreciate that the compression and decompression techniques employed by the present invention are not critical to the overall operation of the system and the advantages obtained therefrom could be obtained with other compression methodologies. Advantageously, the identity of the compression technique used can be encoded into the audio stream in the packet header. This makes it possible to identify to the receiver the nature of the decompression algorithm to use; and thereby make it possible for the computer within the Primary Server to select an optimum compression algorithm depending on the nature of the audio stream to be compressed.

The remainder of the distribution architecture comprises the multilevel hierarchy of data transmission originating at the Primary Server 20 and terminating at the Users 40 as shown in <figref idref="f0003">Figure 3</figref>. In the preferred embodiment, the network is the global connected Internet. It can also include private networks which are connected to the Internet and it could be implemented on any packet switched network, cable-modem-based or satellite-based cable system. It is possible that certain links within the overall system, for example, the link between the Primary Server and the first level of Media Servers, are private data links which carry only data associated with this system. This could also be true of other data transmission paths in the distribution architecture. The User receiving the information preferably can be anyone who has access to the Internet with sufficient bandwidth to receive the resulting audio data.

It should be appreciated that the distribution architecture of the present invention provides for scalability. Using such a structure, any number of Users, and as widely distributed as necessary, can be accommodated. In the preferred embodiment, the fan-out at each level of Media Server (given the state of technology today) is on the order of ten, but the same structure could be applied with other fan-outs. The location and fan-out of the Media Servers is chosen to minimize overall network bandwidth consumed.

The flow of information from Primary Server 20 through network to User 40 is based on the delivery of a continuous sequence of individual pieces of information, or packets. Thus the distribution architecture implements a form of multicast packet delivery to a group. The group in this case is the set of all users who are listening to a given channel at a given time. Group membership is dynamic, Users can start and stop listening to a channel at any time.

Multicasting can be implemented in a variety of ways, any or all of which can be used in the present invention. In the preferred embodiment, the Media Servers receive unicast packet streams and they then duplicate these streams into more unicast streams to other Media Servers which are in the membership group for that stream. The lowest level Media Servers use hardware broadcast, multicast and/or unicast to reach all Users served by that Media Server.

If the Media Server is directly connected to the same physical network as the User, hardware broadcast or multicast can be used to transmit the packet stream to all Users listening at that time on that network. In this case the Media Servers can translate the incoming packets into broadcast or multicast packets for transmission on the local network. Only a single packet is transmitted at-a-time on the local network and any computer directly connected to the local network can receive that packet. Hardware multicast is built into most networks and it is lower in overall overhead than hardware broadcast since computers not interested in a transmission do not have to process the packets. In the case that a Media Server is serving a User who is not on the same physical network, a unicast transmission is used to reach that User, which requires a separate packet transmission for each user so connected. In the preferred embodiment, the assignment of Users to Media Servers is done using control transactions among the User 40, Control Servers 50, and Administration Server 60. This system will be described more fully in the following section.

Multicasting can also be implemented within the Internet at the IP level using IP class D addresses and the IGMP group control protocol. <figref idref="f0004">Fig. 4</figref> illustrates how the multilevel hierarchical distribution architecture would operate using IP multicast delivery. Under this system, a packet is transmitted with a multicast address for a destination and each router maintains group membership lists for each interface that it is connected to and will forward packets across the Internet to other routers such that all Users within the global group eventually receive a copy of the packet. Unless and until all routers within the Internet understand multicasting in this way, it is necessary to supplement it with IP tunneling in which multicast packets are encapsulated in unicast packets and routed by unicast routers to a multicast routers. The present invention can and will be able to take advantage of IP multicasting as it becomes widely available. Each channel of information would be given its own class D address and the Media Server would then simply transmit packets using the appropriate IP destination address. In this case no Media Servers would be used as this function would be accomplished by the routers in use to store and forward other IP packets.

Thus it can be appreciated that the implementation of the multicast delivery structure can be implemented using a combination of IP unicast, IP multicast and hardware multicast or any other system which provides for distributed delivery of information to a specific group of destinations. It is expected that special relationships with Internet providers will be established so that delivery of the audio steams can take place with a guaranteed bandwidth and in the most efficient way possible.

In the preferred embodiment, packets of information for distribution use the UDP protocol under IP rather than the TCP protocol. TCP provides for reliable stream delivery but at the cost of retransmission and delays. For real-time information, it is usually more appropriate to use UDP since the information is time critical and low latency is more important that reliability. Since TCP is a point-to-point protocol, it is incompatible with IP multicasting. However, TCP could be used on the IP unicast links between Media Servers which are expected to have very low packet loss. In order to handle out of order, lost, duplicate and corrupted packets, the UDP packets are serialized.

In the preferred embodiment the size of the audio packets being transmitted is variable and can change on a packet by packet basis. It is expected that when using compression schemes that have a fixed bit rate, such as ADPCM, all packets for that stream would be the same size. Alternatively when using a variable bit rate compression algorithm, it is expected that packet size would vary so as to establish approximately the same amount of time for each sample. For example, if each packet corresponds to a 20 millisecond segment of speech, this could correspond to 100 bytes during one time period and 200 bytes during another. Additionally, the Media Server may choose to dynamically vary the packet size to accommodate changes in network conditions.

Since the resulting playback of audio information is sensitive to packet loss and network congestion, software running on the various computers which make up this system monitor the ongoing situation and adapt to it in the best possible way. This may involve using different Media Servers and/or lowering the data rate to the User. For example, similar to analog dynamic signal quality negotiation present in many analog radio receivers, the User software may request a lower bitrate until the situation is improved. Also, note that the audio information being delivered to the User is preferably interleaved so that a contiguous segment of the audiostream is distributed for transmission over several packets. As a result, the loss of one packet is spread out over multiple audio samples and causes minimal degradation in audio. Advantageously, a small degree of redundancy may be incorporated within the audio stream to further guard against packet loss.

Preferably, there are two bitrate options available to the User for audio delivery. These are approximately 20Kbps for standard audio and approximately 56Kbps for high quality audio. Thus, a 28.8Kbps modem connection over an analog phone line is sufficient to listen to standard audio broadcasts. To listen to high quality audio, an ISDN connection to the Internet is required, or some other connection with greater than 56Kbps bandwidth. It should be appreciated that higher bandwidths are currently becoming available to end Users. In particular the use of cable modems and residential fiber networks are enhancing the bandwidths available to Users and thus making broadcasts of higher bitrates more practical.

In addition to the content of the audio channel being delivered, it is also possible to deliver out of band of side-bar information such as graphics, images and text. This side-bar information is synchronized with the audio channel. This may only involve small increases in bandwidth requirements, such as 1-2Kbps. For example a music program could deliver images of an album cover, the text of song lyrics, or URLs for use by a Web browser. The User can preferably choose to have the side-bar information show up automatically or be hidden. It is also possible to incorporate two-way interaction into the system, such that for example Users can participate in a global chat session during the audio broadcast. These and other details are explained in more detail below under the description of the User interface.

The delivery of paid commercial advertising information is an important aspect of the present invention. Advertising may be incorporated into the audio stream within the Network Control Center as described above. It may also be incorporated into the audio stream at the User level, or at some intermediate point in the distribution architecture. In addition, the side-bar information discussed above can also include advertising content. <figref idref="f0005">Fig. 5</figref> illustrates the provision to the User of two separate streams 32, 34 of packets, one of which may be used for advertising. In this case the insertion of the stream of commercial advertising into the non-commercial stream occurs on the User's computer. <figref idref="f0005">Fig. 5</figref> also illustrates packet stream 36 which identifies the User to the system. This enables the system to monitor which Users are listening to which channels and also allows the system to vary, for example, the advertising content delivered to a User.

One advantage of this alternative is to allow targeted commercial delivery based on the individual User. That is, an individual User would receive the main audio feed plus a particular advertising stream unique to his demographic group. Note that the advertising stream typically is lower in overall bitrate and generally does not require real-time delivery, thus lowering the overall load on the network. For example, the advertising stream could be delivered to the User in advance of the regular programming, stored in a buffer in the User's computer and inserted into the stream of regular programming upon receipt of a cueing signal embedded in the stream of regular programming. Thus, a substantial number of targeted groups, perhaps 10 or 100 or even more could be accommodated without an impractical increase in network load.

II. Control Architecture

The control architecture described in this section is responsible for managing and administering the Users who are receiving the information being delivered by the distribution architecture described in the previous section. The control architecture handles new User registration, User login, the starting and stopping of audio streams and the monitoring of ongoing transmissions. The control architecture is scalable just as is the distribution architecture so that any number of Users can be managed.

This section describes the control protocol, which consists of the format and sequence of control messages that are exchanged among Users, Control Servers, Media Servers, Primary Servers and the Administration Server. These messages are in the form of objects, which have specific data formats. objects are exchanged preferably using the TCP protocol although other options are possible. Below we describe the sequence of objects passed among the various computers and detail the internal structure of each object.

The major objects used in the present embodiment of the invention are set forth in Table 1. For each object, Table 1 provides a brief description of its function, identification of the names of the fields in the object, their types and a brief description of their function. <tables id="tabl0001" num="0001"><table frame="topbot"><title><i>TABLE 1</i></title><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Channel Activation Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Contains information used for channel activation</i>/<i>deactivation. It is sent to Media and Primary Servers to tell them to carry or stop carrying a specific channel. Media Servers get the channel from another server in the system hierarchy and Primary Servers get and encode the feed from the actual input source.</i></b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b>Field Name</b></entry><entry><b>Field Type</b></entry><entry><b>Remarks</b></entry></row><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Moniker</i></entry><entry>Moniker Object</entry><entry>unique channel identifier</entry></row><row rowsep="0"><entry /><entry>Activate</entry><entry>Int</entry><entry>action flag (activate/deactivate)</entry></row><row rowsep="0"><entry /><entry><i>CompressType</i></entry><entry>Int</entry><entry>type of compression to use</entry></row><row><entry /><entry><i>Host</i></entry><entry>Host Object</entry><entry>host carrying the channel</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Channel Guide Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Contains analytical and descriptive information for an item requested that is uniquely identified by a moniker. It is usually the reply to a Channel Guide Request object.</i></b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b>Field Name</b></entry><entry><b>Field Type</b></entry><entry><b>Remarks</b></entry></row><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Type</i></entry><entry>int</entry><entry>type of content</entry></row><row><entry /><entry><i>Result</i></entry><entry /><entry>the content data itself</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Channel Guide Request Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Conveys a request for analytical and descriptive information about an item uniquely identified by the contained moniker. The reply is in the form of a Channel Guide object.</i></b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b>Field Name</b></entry><entry><b>Field Type</b></entry><entry><b>Remarks</b></entry></row><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry>inherited from base class</entry></row><row rowsep="0"><entry /><entry><i>Type</i></entry><entry>Int</entry><entry>type of content</entry></row><row><entry /><entry><i>Moniker</i></entry><entry>Moniker Object</entry><entry>unique identifier</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Host Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i> Encapsulates the attributes of a networked computer related to the operation or services it offers or requests.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>HostName</i></entry><entry>String</entry><entry>computer name and domain</entry></row><row rowsep="0"><entry /><entry><i>PortNumber</i></entry><entry>Int</entry><entry>port number for service</entry></row><row><entry /><entry><i>DisplayName</i></entry><entry>String</entry><entry>descriptive computer name</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Login Information Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Encapsulates the name and password by which a User is known to the system.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top">Field Name</entry><entry valign="top">Field Type</entry><entry valign="top">Remarks</entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Login</i></entry><entry>String</entry><entry>User's system login name</entry></row><row><entry /><entry><i>Password</i></entry><entry>String</entry><entry>User's system password (possibly encrypted)</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Media Control Interface (MCI) Request Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Encapsulates a multimedia control command, such as play and stop, and any extra information that may be necessary to perform the requested service.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Command</i></entry><entry>Int</entry><entry>multimedia command</entry></row><row><entry /><entry><i>String</i></entry><entry>String</entry><entry>command-specific extra info</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Moniker Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>A moniker encapsulates the name of an object or process with the intelligence necessary to work with that name. In other words, it provides naming and binding services. The Moniker Object is used in the system for unique identification of various components, parts or features, such as a channel, a directory, or a computer list.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b><i>Token</i></b></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><b><i>ID</i></b></entry><entry>String</entry><entry>unique string identifier</entry></row><row><entry /><entry><b><i>DisplayName</i></b></entry><entry>String</entry><entry>User-readable name</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Ping Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Ping is the name given to the "Are-You-Alive?" operation useful in determining if a specific computer is up and running. This object is used in the system when a server has to be queried for its operation status. It can also provide timing information for statistical purposes and quality of service evaluations.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Yield Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Date</i></entry><entry>Date</entry><entry>system date</entry></row><row><entry /><entry><i>Time</i></entry><entry>Time</entry><entry>system time</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Protocol List Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Encapsulates a general purpose collection object.</i></b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b>Field Name</b></entry><entry><b>Field Type</b></entry><entry><b>Remarks</b></entry></row><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row><entry /><entry><i>Type</i></entry><entry>Int</entry><entry>type of object list</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Result Message Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Acts as the acknowledgment for a requested service successfully carried that out or reports errors that occur in the system during a client</i>/<i>server transaction.</i></b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b>Field Name</b></entry><entry><b>Field Type</b></entry><entry><b>Remarks</b></entry></row><row rowsep="0"><entry /><entry><b><i>Token</i></b></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><b><i>Code</i></b></entry><entry>Int</entry><entry>result code</entry></row><row><entry /><entry><b><i>Message</i></b></entry><entry>String</entry><entry>message corresponding to code</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Security Token Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Contains the authorization key for a transaction. The key must be validated before any service is performed.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row><entry /><entry><i>ID</i></entry><entry><b>String</b></entry><entry>authorization key/transaction ID.</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Server Activation Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Contains information used in the server activation</i>/<i>deactivation process. Used for announcement as well as command purposes (e.g., a server can notify the administration database that is now activated or a server can be instructed to manage someone else).</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><b><i>Token</i></b></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><b><i>Active</i></b></entry><entry>Int</entry><entry>action flag (activate/deactivate)</entry></row><row rowsep="0"><entry /><entry><b><i>Manage</i></b></entry><entry>Int</entry><entry>control flag (manage/associate)</entry></row><row rowsep="0"><entry /><entry><b><i>Type</i></b></entry><entry>Int</entry><entry>server type</entry></row><row><entry /><entry><b><i>Host</i></b></entry><entry>Host Object</entry><entry>host to be controlled</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Server List Request Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Encapsulates a request for a list of available server resources for an identified service (e.g., a request for a list of Control Servers for a specified channel).</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top">Remarks</entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Type</i></entry><entry>Int</entry><entry>type of service</entry></row><row rowsep="0"><entry /><entry><i>Moniker</i></entry><entry>Moniker Object</entry><entry>content/channel unique identifier</entry></row><row><entry /><entry><i>Host</i></entry><entry>Host Object</entry><entry>local host information</entry></row><row><entry /><entry /><entry /><entry /></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Statistics Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Contains system-related information that can be used by load-balancing algorithms and for statistical purposes.</i></b></entry></row><row><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Load</i></entry><entry>Int</entry><entry>load on the system</entry></row><row rowsep="0"><entry /><entry><i>Threads</i></entry><entry>Int</entry><entry>number of threads running</entry></row><row rowsep="0"><entry /><entry><i>Users</i></entry><entry>Int</entry><entry>number of Users being</entry></row><row rowsep="0"><entry /><entry><i>Uptime</i></entry><entry>Int</entry><entry>serviced</entry></row><row rowsep="0"><entry /><entry><i>NumberManaged</i></entry><entry>Int</entry><entry>amount of time running</entry></row><row rowsep="0"><entry /><entry><i>NumberAssociated</i></entry><entry>Int</entry><entry>number of managed servers</entry></row><row><entry /><entry /><entry /><entry>number of associated servers</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Statistics Request Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Encapsulates</i> a <i>request for system-related information that can be used by load-balancing algorithms and statistical purposes.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Load</i></entry><entry>Int</entry><entry>request flag (on/off)</entry></row><row rowsep="0"><entry /><entry><i>Threads</i></entry><entry>Int</entry><entry>request flag (on/off)</entry></row><row rowsep="0"><entry /><entry><i>Users</i></entry><entry>Int</entry><entry>request flag (on/off)</entry></row><row rowsep="0"><entry /><entry><i>Uptime</i></entry><entry>Int</entry><entry>request flag (on/off)</entry></row><row rowsep="0"><entry /><entry><i>NumberManaged</i></entry><entry>Int</entry><entry>request flag (on/off)</entry></row><row><entry /><entry><i>NumberAssociated</i></entry><entry>Int</entry><entry>request flag (on/off)</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>User Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>Users and Servers use this object to register themselves with the administration database. They provide the information for subsequent logins (name, password) and other system-related info. The end-Users provide personal</i>, <i>demographic, and system-related information.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top">Field Name</entry><entry valign="top">Field Type</entry><entry valign="top">Remarks</entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Login</i></entry><entry>Login Information Object</entry><entry>login information(name, password)</entry></row><row rowsep="0"><entry /><entry><i>FirstName</i></entry><entry>String</entry><entry>User's first name</entry></row><row rowsep="0"><entry /><entry><i>LastName</i></entry><entry>String</entry><entry>User's last name</entry></row><row rowsep="0"><entry /><entry><i>Title</i></entry><entry>String</entry><entry>User's job title</entry></row><row rowsep="0"><entry /><entry><i>Company</i></entry><entry>String</entry><entry>User's employer</entry></row><row rowsep="0"><entry /><entry><i>Address1</i></entry><entry>String</entry><entry>User's home street address</entry></row><row rowsep="0"><entry /><entry><i>Address2</i></entry><entry>String</entry><entry>User's address extra</entry></row><row rowsep="0"><entry /><entry><i>City</i></entry><entry>String</entry><entry>city, village</entry></row><row rowsep="0"><entry /><entry><i>State</i></entry><entry>String</entry><entry>state, province or foreign country</entry></row><row rowsep="0"><entry /><entry><i>ZipCode</i></entry><entry>String</entry><entry>zip or postal code</entry></row><row rowsep="0"><entry /><entry><i>Age</i></entry><entry>String</entry><entry>User's age</entry></row><row rowsep="0"><entry /><entry><i>Gender</i></entry><entry>String</entry><entry>User's gender</entry></row><row rowsep="0"><entry /><entry><i>PhoneNumber</i></entry><entry>String</entry><entry>telephone number</entry></row><row rowsep="0"><entry /><entry><i>FaxNumber</i></entry><entry>String</entry><entry>fax number</entry></row><row rowsep="0"><entry /><entry><i>Email</i></entry><entry>String</entry><entry>email address</entry></row><row rowsep="0"><entry /><entry><i>Demographics</i></entry><entry>Dictionary</entry><entry>market-targeting extra User info</entry></row><row><entry /><entry><i>SystemInfo</i></entry><entry>Dictionary</entry><entry>system-related information</entry></row></tbody></tgroup><tgroup cols="4" colsep="0"><colspec colnum="1" colname="col1" colwidth="10mm" /><colspec colnum="2" colname="col2" colwidth="55mm" /><colspec colnum="3" colname="col3" colwidth="47mm" /><colspec colnum="4" colname="col4" colwidth="55mm" /><thead><row rowsep="0"><entry namest="col1" nameend="col4" align="left" valign="top"><b><i>Version Object</i></b></entry></row><row><entry valign="top" /><entry namest="col2" nameend="col4" align="left" valign="top"><b><i>All components of the system use this object to retort their versioning information to the party they transact with in order to use a protocol they both understand. They are also given the chance to update themselves if a newer version exists.</i></b></entry></row><row rowsep="0"><entry valign="top" /><entry valign="top"><b>Field Name</b></entry><entry valign="top"><b>Field Type</b></entry><entry valign="top"><b>Remarks</b></entry></row></thead><tbody><row rowsep="0"><entry /><entry><i>Token</i></entry><entry>Security Token Object</entry><entry /></row><row rowsep="0"><entry /><entry><i>Major</i></entry><entry>Int</entry><entry>major protocol version number</entry></row><row rowsep="0"><entry /><entry><i>Minor</i></entry><entry>Int</entry><entry>minor protocol version number</entry></row><row rowsep="0"><entry /><entry><i>Type</i></entry><entry>Int</entry><entry>sender type</entry></row><row><entry /><entry><i>Client</i></entry><entry>Version</entry><entry>client version information</entry></row></tbody></tgroup></table></tables>

Unlike traditional protocols based on state computers, the control protocol of the present invention is a light-weight, stateless protocol comprising simple sequences of objects. It is <i>light-weight</i> in that in most sequences only two objects are involved in the transaction and after a sequence is completed the connection can be reused. It is also <i>stateless</i> in that the server maintains no information about the client. Every transaction is handled independently of the previous ones. States exist in the lower levels, for example within the TCP layer, to express logical states of a network connection but they are not actually part of the control protocol.

In the preferred embodiment, the software running on the Control Servers, Media Servers and Primary Servers is programmed for Windows NT and UNIX environment using the OLE environment. In addition, COM interfaces are used between components. The Rogue Wave system is used to transfer objects between the applications running on the various computers. The software running on the User computer is preferably programmed for a Windows 32-bit environment, so it will run on a Windows 95 or Windows NT computer. Alternatively, Macintosh and UNIX environments can be accommodated by other User software.

The basic process of a control transaction consists of a <i>version sequence</i> followed by one or more <i>protocol sequences.</i> The version sequence starts after the computer initiating the transaction, the client, has established a connection with the computer completing the transaction, the <i>server.</i> The client sends a Version object (defined in Table 1) and in response the server then sends back its own Version object. This version sequence is used so that both client and server are aware of the version numbers of the software they are using. If a version number is older than expected, either client or server can choose to conform to the previous version or abort the transaction, depending on its needs and capabilities. If a version number is newer than expected, in most cases the current transaction can be completed since the software systems are designed to be fully backward compatible with previous versions. Additionally, in the case that the server of the transaction is the Administration Server, the client receives information about what the latest version number is and thus the client can be informed that a software update is needed. The process of handling automatic updating of User software is described more fully below.

After the version sequence, one or more protocol sequences occur in which other objects are exchanged between client and server. When a particular protocol sequence is completed, another independent protocol sequence can be serviced. The protocol sequences that are part of the control architecture of the present invention are summarized in Table 2 and described below in conjunction with <figref idref="f0006 f0021">Figures 6-17</figref>. <tables id="tabl0002" num="0002"><table frame="all"><title><b>TABLE 2</b></title><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="53mm" /><colspec colnum="2" colname="col2" colwidth="29mm" colsep="0" /><colspec colnum="3" colname="col3" colwidth="26mm" /><colspec colnum="4" colname="col4" colwidth="59mm" /><thead><row><entry namest="col1" nameend="col4" align="center" valign="top"><b>Summary of Protocol Sequences</b></entry></row><row><entry valign="top">Control Sequence</entry><entry valign="top">Client</entry><entry valign="top">Server</entry><entry valign="top">Main Objects Exchanged</entry></row></thead><tbody><row rowsep="0"><entry morerows="2" rowsep="1">User Registration and Login (see <figref idref="f0006">Fig. 6</figref>)</entry><entry>User</entry><entry>Administration</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry /><entry>User Object</entry></row><row><entry /><entry /><entry>Channel Guide Object</entry></row><row rowsep="0"><entry morerows="2" rowsep="1">User Login (see <figref idref="f0007">Fig. 7</figref>)</entry><entry>User</entry><entry>Administration</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry /><entry>Login Information Object</entry></row><row><entry /><entry /><entry>Channel Guide Object</entry></row><row rowsep="0"><entry morerows="7" rowsep="1">Channel Play (see <figref idref="f0008">Figs 8a</figref>, <figref idref="f0009">8B</figref>, <figref idref="f0010">8C</figref>)</entry><entry>User</entry><entry>Administration</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry /><entry>Server List Object</entry></row><row rowsep="0"><entry /><entry>Control</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry /><entry>Server List Object</entry></row><row rowsep="0"><entry /><entry>Media</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry /><entry>MCI Objects -</entry></row><row rowsep="0"><entry /><entry /><entry>OPEN /PLAY/STOP/CLOSE</entry></row><row><entry /><entry /><entry>Ping Objects (TCP connection stays open)</entry></row><row rowsep="0"><entry morerows="1" rowsep="1">Token Validation (see <figref idref="f0011">Figs. 9A</figref>, <figref idref="f0012">9B</figref>)</entry><entry morerows="1" rowsep="1">Control or Media or Primary</entry><entry morerows="1" rowsep="1">Administration or Control</entry><entry>Version Object</entry></row><row><entry>Security Token Object</entry></row><row rowsep="0"><entry morerows="2" rowsep="1">Server Registration and Login (see <figref idref="f0013">Fig. 10</figref>)</entry><entry morerows="2" rowsep="1">Media or Control</entry><entry>Administration</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry>User Object</entry></row><row><entry /><entry>Server Activation Object</entry></row><row rowsep="0"><entry morerows="2" rowsep="1">Server Login (see <figref idref="f0014">Fig. 11</figref>)</entry><entry morerows="1">Media or Control</entry><entry>Administration</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry>Login Object</entry></row><row><entry /><entry /><entry>Server Activation Object</entry></row><row rowsep="0"><entry morerows="1" rowsep="1">Control Server Activation (see <figref idref="f0015">Fig. 12</figref>)</entry><entry>Administration</entry><entry>Control</entry><entry>Version Object</entry></row><row><entry /><entry /><entry>Server Activation Object</entry></row></tbody></tgroup><tgroup cols="4"><colspec colnum="1" colname="col1" colwidth="53mm" /><colspec colnum="2" colname="col2" colwidth="29mm" colsep="0" /><colspec colnum="3" colname="col3" colwidth="26mm" /><colspec colnum="4" colname="col4" colwidth="59mm" /><thead><row><entry valign="top">Control Sequence</entry><entry valign="top">Client</entry><entry valign="top">server</entry><entry valign="top">Main Objects Exchanged</entry></row></thead><tbody><row rowsep="0"><entry morerows="2" rowsep="1">Media Server Activation (see <figref idref="f0016">Fig. 13</figref>)</entry><entry>Control</entry><entry>Media</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry /><entry>Server Activation Object</entry></row><row><entry /><entry /><entry>Ping Objects (TCP connection stays open)</entry></row><row rowsep="0"><entry morerows="1" rowsep="1">Control Channel Activation (see <figref idref="f0017">Fig. 14</figref>)</entry><entry>Administration</entry><entry>Control</entry><entry>Version Object</entry></row><row><entry /><entry /><entry>Channel Activation Object</entry></row><row rowsep="0"><entry morerows="1" rowsep="1">Media Channel Activation (see <figref idref="f0018">Fig. 15</figref>)</entry><entry>Control</entry><entry>Media</entry><entry>(open TCP connection)</entry></row><row><entry /><entry /><entry>Channel Activation Objects</entry></row><row rowsep="0"><entry morerows="3" rowsep="1">Distribution Activation (see <figref idref="f0019 f0020">Fig. 16</figref>)</entry><entry>Media</entry><entry morerows="3" rowsep="1">Media or Primary</entry><entry>Version Object</entry></row><row rowsep="0"><entry /><entry>MCI Objects</entry></row><row rowsep="0"><entry /><entry>OPEN/PLAY/STOP/CLOSE</entry></row><row><entry /><entry>Ping Objects (TCP connection stays open)</entry></row><row rowsep="0"><entry morerows="1" rowsep="1">Statistics Request (see <figref idref="f0021">Fig. 17</figref>)</entry><entry>Administration</entry><entry morerows="1" rowsep="1">Control or Media</entry><entry>Version Object</entry></row><row><entry /><entry>Statistics Object</entry></row></tbody></tgroup></table></tables>

The User registration and login sequences are the processes by which a new User registers with the system, logs in and retrieves programming information. The channel play sequence takes place when a User asks to listen to a particular channel. The token validation sequence is used to verify that a computer requesting a service is authorized to do so. The Server registration, login and activation sequences are used by Control and Media Servers when they become active. The Control Server and Media Server activation sequences are used to manage the Control and Media Servers. The control channel, media channel and distribution activation sequences are used to cause a channel to be distributed to a Media Server. Finally, the statistics request is used for administrative purposes.

<figref idref="f0006">Fig. 6</figref> illustrates the User registration and login sequence in more detail. This sequence takes place after the User has installed the User software on his/her computer. It is expected that the User will download the software from the Internet and then invoke it which in the preferred embodiment will use the Windows Wizard interface. This will guide the User through the installation process including filling out the registration form, which we will describe more fully in the next section. After the User has selected a name and password and selected the option to register, the User computer opens a TCP connection to the Administration Server. Advantageously, the full domain name of the Administration Server is embedded into the User software, although it could be discovered in other ways. The User and Administration Server then exchange version objects with the Administration Server as described above. If the version numbers meet expectations, the User sends a User Object to the Administration Server. The format of the User Object is shown in Table 1. Once the Administration Server receives the User Object, it verifies that the information is filled in properly and that the selected User name is unique. If the User Object is invalid for any reason, the Administration Server returns a Result Message Object with a code indicating the reason. The format of the Result Message Object is shown in Table 1. If the User information is valid, the Administration Server updates the global database of User names and passwords and then generates a security token for that User. This security token is then returned to the User in a Result Message Object.

Upon receiving the Result Message Object, the User saves the security token for future use. This token is an identifier that allows the User to request services from the Administration Server and other computers within the overall system. The security token is not saved permanently or registered on the User computer. Normally, the User software then immediately sends a Channel Guide Request Object to the Administration Server and a Channel Guide Object is returned. The format of these objects is also shown in Table 1. Note that in principle, this is a separate transaction and could take place in a separate TCP connection to the Administration Server. In particular, once the User has registered and logged in, he/she can request the Channel Guide Object again since it may have been updated since the previous request. At this point the TCP connection to the Administration server is closed.

The process of User registration only needs to take place once for each User. However anyone can re-register at any time, even after the software has been installed. In particular, it is expected that if multiple persons use a computer, each person will register and obtain his/her own User name and password. If the registration process is not completed successfully, the User software saves the registration information and ask the User if they would like to try again the next time the software is invoked.

Since the security token is not permanently saved by the User software, it is lost when the User software is closed, and the security token must again be retrieved from the Administration Server the next time the User wants to use the system. This process is the purpose of the login sequence illustrated in <figref idref="f0007">Fig. 7</figref>. This sequence is used if a User has already registered and needs only to retrieve a valid Security token. In this case the sequence consists of the User's sending a Login Information object to the Administration Server. The Administration Server then queries the User database to validate the login name and password. If the login name and password are correct, then a security token is returned to the User. Normally the receipt of the security token will immediately be followed by a channel information request sequence, just as in the registration sequence described previously.

The control sequence that takes place when a User initiates a channel play operation is illustrated in <figref idref="f0008">Figs. 8A</figref>, <figref idref="f0009">8B</figref> and <figref idref="f0010">8C</figref>. First the User software requests a Control Server List from the Administration Server. Note that the Server List Request object, illustrated in Table 1 contains a channel identifier. The Administration Server generates a sorted list of Control Servers based on overall system load and the location of the User on the network and returns this list to the User using a Protocol List Object. Once the control Server List is returned to the User, the Administration Server is no longer needed and the TCP connection is closed.

The User software then searches the list of Control Servers and opens a TCP connection to the first host listed. If that host computer does not respond, then the next Control Server on the list is tested and so forth in succession. Upon obtaining a response from a Control Server, the User software uses a Server List Request Object to requests a Media Server List from the Control Server. If the Control Server is too busy to service the User, it returns a Result Message Object so indicating and the User software tries the next Control Server on the list. However, in the likely scenario that the Control Server is able to handle the User's request, a sorted list of Media Servers is generated and returned to the User computer using a Protocol List Object. The TCP connection to the control Server is then closed by the User software.

At this point the User software initiates a TCP connection to the first Media Server on the list provided by the Control Server. As in the previous case, it attempts to connect to the first host on the list and if unsuccessful tries the next hosts in succession. Once the Version objects are exchanged, the User software sends an MCI Request Object to the Media Server. An MCI Request Object can be used for four basic commands: OPEN, PLAY, STOP and CLOSE. The User software must first send an OPEN command for the desired channel. If the returned Result Message Object indicates success, the User software then sends a PLAY command.

When the Media Server receives a valid PLAY command, it initiates the delivery of audio information to the User as described in the previous section. Note that this could be in the form of broadcast, Multicast or unicast packets to a specific UDP port. The TCP connection through which the MCI Request Objects were sent stays open during the audio play operation. In addition, Ping Objects are sent to the User on a periodic basis to verify that the computer is still working and active. When the User software receives a Ping Object, it simply returns it. The Media Server uses the ping Objects to measure round trip time and also to determine when a User's computer has terminated abnormally. In that case the audio stream is terminated.

In the case of normal termination of the audio stream, the User makes an explicit selection to stop and this causes a STOP command to be sent to the Media Server in an MCI Request Object. The Media Server then terminates the audio stream to that User. When the User closes the application software or selects another channel to play, the User software will send a CLOSE command to the Media Server in an MCI Request Object and the TCP connection is closed.

The initiation of the audio stream by the Media Server causes a log entry to be generated and sent to the Administration Server. This information is important so that the Administration Server can update its database to indicate which Users are listening to which channels. The security token is used to identify the User initiating the audio stream. Additionally, when the audio stream is terminated to any User, another log message is generated and sent to the Administration server.

<figref idref="f0011">Fig. 9A</figref> illustrates the process by which security tokens are validated. The Administration Server is the only server that can validate a security token. Thus, when a User requests services from a Control Server or from a Media Server, that server must go back to the Administration Server with a token validation sequence. However, Control Servers and Media Servers are allowed to cache validations of security tokens so that they do not have to validate tokens repeatedly once they have validated it the first time. In the case where a Media Server receives a request, the token will be validated with the Control Server that is managing that Media Server. <figref idref="f0012">Fig. 9B</figref> identifies the various token validation scenarios.

<figref idref="f0013">Fig. 10</figref> illustrates the process by which a new Server is registered. This process is similar to new User registration. It is expected, however, that the server installation will be through a Web interface rather than a Wizard. The Administration Server, upon receiving a User Object from a Media Server or Control Server validates the User name and password and generate a security token just as in the case of User registration. Normally the Server then immediately sends back a Server Activation Object indicating that it is ready to be used as a system resource. Once this process has been completed, the TCP connection to the Administration Server is closed.

If a Media Server or Control Server that has sent a Server Activation Object to the Administration Server becomes inactive, it will send another Server Activation Object indicating this condition. In the case of a Media Server, this object is sent to the managing Control Server. In the case of a Control Server, this object sent to the Administration Server. As in the case of User registration, Media Server and Control Server registration needs only take place once per computer. However, if the computer is restarted, the server must login and again retrieve a security token. This is the server login and activation sequence shown in <figref idref="f0014">Figure 11</figref>.

Once a Control Server has indicated to the Administration Server that it is ready, the Administration Server can activate that Control Server by sending the Control Server a Server Activation Object as illustrated in <figref idref="f0015">Fig. 12</figref>. This is a separate transaction and is used to tell the Control Server which Media Servers it is supposed to manage. Recall that a control Server and a number of Media Servers form a <i>cluster</i> of Media Servers. The single control Server that manages that cluster must be given a list of host computers corresponding to the Media Servers in that cluster.

The process by which a Control Server activates the Media Servers that it manages is illustrated in <figref idref="f0016">Fig. 13</figref>. The Control Server sends a Server Activation Object to the Media server indicating that it is responsible for channel management. This TCP connection between the control Server and the Media Server stays open during the time that both servers are active. The Control Server periodically sends Ping Objects to the Media Server across this open TCP connection to verify that the Media Server is still running.

<figref idref="f0017">Fig. 14</figref> illustrates the process by which a given channel is activated by the Administration Server. The Administration Server opens a connection to a Control Server that its wishes to have carry a given channel and provide a Channel Activation Object. This object indicates to the Control Server which Media or Primary Server the Control Server should direct its Media Servers to get the feed from. At this point the Control Server is said to be carrying that channel and it will be a valid host on a list of Control Servers requested by a Channel Play sequence.

<figref idref="f0018">Fig. 15</figref> illustrates what happens when a Control Server needs to provide a channel. First it sends a Channel Activation Object to one of the Media Servers that it manages across the open TCP connection described previously. This object indicates to the Media Server that it should start receiving the channel identified and from where it should receive it.

In <figref idref="f0019">Figs. 16A</figref> and <figref idref="f0020">16B</figref> depict how the Media Server requests distribution of an audio channel from another Media Server or from a Primary Server. This sequence is much the same as that in which a User requests the distribution of audio information from a Media Server. Note that a Media Server receives a single incoming stream for each channel that it is carrying and will then redistributes this stream to all Users or other Media Servers that request it.

Finally, <figref idref="f0021">Fig. 17</figref> illustrates the statistics request sequence. This sequence is used by the Administration Server to gather information from the Media Servers and Control Servers in order to manage the overall system. It can use this information to detect failures and to balance load as the dynamic conditions change. As indicated above, it can also use this information to monitor which Users are listening to which channel or whether Users stop listening to a channel at any time, such as during the play of a particular song. It can also use this information to control the advertising content that is downloaded to a particular User in advance of receipt of regular audio programming and/or monitor the delivery of advertising to the Users.

The control architecture described in this section is scalable to handle any number of Users. Note that the User registration process only happens once for each subscriber and the login process only happens once per session. These interactions, which require the Administration Server are expected to constitute a very small percentage of the overall system bandwidth. If the Administration Server were to become a bottleneck, however, it would be possible to duplicate it and to have the database it maintains distributed and automatically updated to guarantee consistency.

The Control Servers are distributed throughout the network and can handle the lower level interactions with the Users and the Media Servers. A single Control Server can handle preferably on the order of ten Media Servers up to several hundred Users. The bitrate among the Users, the Control Servers and the Media Servers is expected to be small in comparison to the audio transmission bitrate. The Ping Objects normally only involve the User and the nearest Media Server. They are also low in overhead since they are small and only get transmitted infrequently.

III. User Interface

The User interface is provided by the client application running on an individual computer and its associated graphical interface. In the preferred embodiment the User interface is available for 32-bit Windows (95 and NT), Macintosh and UNIX platforms. Preferably anyone on the Internet can freely download a copy of the client software and install it in their computer.

<figref idref="f0022">Figure 18</figref> illustrates the main User screen in the preferred embodiment. The screen is composed of three sections: channel guide (upper left frame), program guide (upper right frame), and multimedia frame (lower half of screen). The channel guide lists, as a tree hierarchy, the channels that are available from the system. The User selects a channel from the list of those displayed on the channel guide. The program guide provides information pertaining to the channel selected. This information can be a detailed schedule of the programming that has played or will be playing on the channel selected. Additionally, other relevant information will be displayed in this frame, for example, a notice regarding an upcoming special event on another channel. The multimedia frame provides an integrated web browser that displays information via a series of tabbed sections.

The information contained in the channel guide, program guide, and the tabs of the multimedia frame is dynamically transmitted to the client. For example, if a new channel begins operation, the client application can immediately display it as being available. Furthermore, the tabs displayed can be specifically relevant depending on what song is playing. For example, tabs displaying the album cover, information on the artist, song lyrics, tour dates can be displayed. Additionally, as shown in the example in <figref idref="f0022">figure 18</figref>, a tab can be available allowing the User to place an order for the CD or allowing the User to participate in a chat session related to the channel.

<figref idref="f0023">Figure 19</figref> illustrates the key pull-down menus available in the main User screen in the preferred embodiment. Table 3 provides a description of each of the functions available through the pull down menus, as shown in <figref idref="f0023">figure 19</figref>.

As will be apparent to those skilled in the art, numerous modifications may be made within the scope of the invention. <tables id="tabl0003" num="0003"><table frame="all"><title><b>Table 3</b></title><tgroup cols="3"><colspec colnum="1" colname="col1" colwidth="25mm" /><colspec colnum="2" colname="col2" colwidth="32mm" /><colspec colnum="3" colname="col3" colwidth="109mm" /><thead><row><entry namest="col1" nameend="col3" align="center" valign="top"><b>Pull-Down Menu Functions</b></entry></row><row><entry valign="top"><b>Menu Choice</b></entry><entry valign="top"><b>Menu Sub-Choice</b></entry><entry valign="top"><b>Description</b></entry></row></thead><tbody><row><entry><b>File</b></entry><entry>Login</entry><entry>Allows the User to login to the system.</entry></row><row><entry /><entry>Logout</entry><entry>Allows the User to logout from the system.</entry></row><row><entry /><entry>Register Close</entry><entry>Brings up a dialog so that the User can register with the system for the first time. Minimizes the screen.</entry></row><row><entry><b>Edit</b></entry><entry>Copy</entry><entry>Allows the User to copy the selection on to the clipboard.</entry></row><row><entry /><entry>Properties</entry><entry>Allows the User to set various properties.</entry></row><row><entry><b>Audio</b></entry><entry>Play</entry><entry>Begins playing the selected channel.</entry></row><row><entry /><entry>Stop</entry><entry>Stops playing the selected channel.</entry></row><row><entry /><entry>Mute</entry><entry>Stops the playing of audio</entry></row><row><entry><b>View</b></entry><entry>Tool Bar</entry><entry>Display or hide the tool bar (providing access to pull-down menu functions).</entry></row><row><entry /><entry>Status Bar</entry><entry>or hide the status bar normally situated at bottom of the screen.</entry></row><row><entry /><entry>Web Bar</entry><entry>Display or hide the tool bar section that provides access to the web browser functions.</entry></row><row><entry><b>Help</b></entry><entry>Help Topics</entry><entry>Brings up a list of available online help topics.</entry></row><row><entry /><entry>About...</entry><entry>Displays summary infirmation regarding this application, such as version number, copyright information, and so on.</entry></row></tbody></tgroup></table></tables>