US6377997B1 - Dynamic assignment of multicast network addresses - Google Patents

Dynamic assignment of multicast network addresses Download PDF

Info

Publication number
US6377997B1
US6377997B1 US09480904 US48090400A US6377997B1 US 6377997 B1 US6377997 B1 US 6377997B1 US 09480904 US09480904 US 09480904 US 48090400 A US48090400 A US 48090400A US 6377997 B1 US6377997 B1 US 6377997B1
Authority
US
Grant status
Grant
Patent type
Prior art keywords
announcement
data stream
data
source node
further
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related
Application number
US09480904
Inventor
Peter C. Hayden
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hewlett-Packard Development Co LP
Original Assignee
Hewlett-Packard Development Co LP
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Grant date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12254Address allocation for local use, e.g. on Local Area Networks [LAN] or on Universal Serial Bus [USB] networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/16Arrangements for providing special services to substations contains provisionally no documents
    • H04L12/18Arrangements for providing special services to substations contains provisionally no documents for broadcast or conference, e.g. multicast
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12264Address allocation involving the solving of address allocation conflicts; involving testing of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12283Address allocation involving aspects of pools of addresses, e.g. assignment of different pools of addresses to different Dynamic Host Configuration Protocol [DHCP] servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12207Address allocation
    • H04L29/12292Address allocation for group-, multicast- and broadcast-communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L29/00Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents
    • H04L29/12Arrangements, apparatus, circuits or systems, not covered by a single one of groups H04L1/00 - H04L27/00 contains provisionally no documents characterised by the data terminal contains provisionally no documents
    • H04L29/12009Arrangements for addressing and naming in data networks
    • H04L29/12792Details
    • H04L29/12801Details about the structures and formats of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2038Address allocation for local use, e.g. on local area networks [LAN] or on universal serial bus [USB] networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2046Address allocation involving the solving of address allocation conflicts or involving testing of addresses
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2061Address allocation involving aspects of pools of addresses, e.g. assignment of different pools of addresses to different dynamic host configuration protocol [DHCP] servers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/20Address allocation
    • H04L61/2069Address allocation for group-, multicast- and broadcast-communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements or network protocols for addressing or naming
    • H04L61/60Details
    • H04L61/6004Structures or formats of addresses

Abstract

Multicast addresses on a computer network are dynamically assigned to a temporary node task. In particular, a server dynamically assigns a multicast address to a data stream in response to a request for the data stream from a client. The server assigns the multicast address in cooperation with other servers from a pool of network-allocated but unassigned multicast addresses. Once the data stream is terminated, the assigned multicast address is deassigned and returned to the pool of unassigned multicast addresses for possible reuse by the nodes.

Description

RELATED APPLICATION

This application is a continuation of U.S. application Ser. No. 07/981,274, filed Nov. 25, 1992, now U.S. Pat. No. 6,018,771, the entire teachings of which are incorporated herein by reference in the entirety.

BACKGROUND OF THE INVENTION

In computer networks, it is often desirable for one node to transmit data over a network so the data can be received by all other nodes connected to the network. To accomplish the transmitting, a pool of multicast (group) addresses may be allocated to each network by a network standards body, such as the Institute of Electrical and Electronic Engineers (IEEE) or the American National Standards Institute (ANSI). Any node on the network can read data being transmitted on a multicast address. The standards body guarantees that allocated multicast addresses do not overlap between networks.

Traditionally, multicast addresses were assigned from the pool one at a time, each multicast address serving a specific purpose or function. For example, there are specific multicast addresses assigned for Ethernet end-station “hello” messages, LAT service announcements, and Fiber Distributed Data Interface (FDDI) status reporting frames. Each assigned multicast address serves one explicit function. To prevent a node that is receiving one data stream from being inundated by other data streams, a unique multicast address is required for each unique data stream.

A problem with the traditional assignment method is that each multicast address on a network is assigned for a single specific purpose or function. As the number of specific functions on the network increases, more multicast addresses from the network's allocated pool are assigned to meet the need. Once the network's pool of allocated multicast addresses is depleted, the network must be allocated an additional pool of multicast addresses. This in turn depletes more addresses from the finite set of addresses that are available to be allocated to the various networks.

While many multicast addresses may be allocated to a network and assigned by the network for specific functions, only a relatively few multicast addresses may be in use on the network at any one time. Indeed, many multicast addresses may be used infrequently because the associated functions are in low demand. Networks are thus expanding their pool of multicast addresses while not using all multicast addresses already allocated to the networks.

SUMMARY OF THE INVENTION

There are effectively an infinite number of arbitrary individual data streams available for transmitting over a network. For example, in a computer network accessing video programs, there may be one data stream for each movie, television program, and video image available to the public. Therefore, it is impractical to assign a unique multicast address for every possible data stream. A mechanism to assign a unique multicast address from a finite set of addresses for the duration of the data stream is an ideal solution. The preferred approach is completely distributed and lacks a central agent for assigning the multicast addresses. Therefore, this approach is reliable as nodes join and leave a local area network (LAN).

In addition, it is highly desirable not to force interested nodes on the network to receive unwanted data streams. At the same time, for those nodes that do want to receive a data stream, it is desirable that only the data stream in which the node is interested be received.

The invention provides a general mechanism in which a node on a network can dynamically assign a single multicast address from a network-wide pool of unassigned multicast addresses, and subsequently use that assigned address for the node's own purposes. When the assigned address is no longer needed, it is returned to the pool. This dynamic assignment permits networks to use fewer multicast addresses then would be required if they were assigned in a more traditional basis where a unique address is assigned for each possible function.

The invention pertains to a computer network having a transmitter node for transmitting a particular data stream to at least one receiver node. A node's classification as a transmitter or receiver may vary based on the data stream being transmitted or the network protocol. A data stream is transmitted to a dynamically assigned multicast address by first selecting a candidate multicast address that is not being used by any node on the network. An announcement is transmitted at a dedicated announcement multicast address to notify potential receiver nodes and other transmitter nodes that the candidate multicast address has been assigned. Finally, the transmitter node transmits the data stream at the candidate multicast address.

Prior to transmission of a service data stream, available services may be identified on the announcement multicast address. Nodes may forward commands to the transmitter node to initialize transmission on candidate addresses. Transmitter nodes may also automatically transmit a particular data stream without receiving a command for that data stream. Thereafter, the services are identified on the announcement address with their candidate addresses so that any node may receive the transmitted data streams.

The transmitter nodes also monitor the dedicated multicast address to identify conflicts between the selected candidate address and addresses announced by other nodes and to resolve the conflicts by selecting new candidate addresses.

In particular, a preferred system for transmitting video data streams over a computer network is described. The system comprises video sources, each video source having access to at least one video program. On the computer network are client nodes and server nodes. A user on a client node may have an interest in various video programs. The server nodes are in communication with the video sources and respond to commands received from the client nodes. Specifically, the server nodes select particular video programs from the video sources, either automatically or in response to client node commands for the particular video program. There are a plurality of multicast addresses allocated to the computer network. One such multicast address is used cooperatively by the server nodes to announce information regarding available video programs to all client nodes. The remaining pool of multicast addresses is used by the server nodes to transmit video programs to any and all interested client nodes. The server nodes cooperatively manage the dynamic assignment of multicast addresses so that multicast addresses are exclusively assigned to a single video program while that video program is being transmitted. After the video program transmission terminates, the assigned multicast address is deassigned and returned to the pool of unassigned multicast addresses for possible reassignment.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing and other objects, features and advantages of the invention will be apparent from the following more particular description of preferred embodiments of the drawings in which like reference characters refer to the same parts throughout the different views.

FIG. 1 is a schematic block diagram of computer network adapted for transmitting video data streams.

FIG. 2 is a block diagram of the multicast addresses A1-AN available on network 10 of FIG. 1.

FIG. 3 is a schematic block diagram of the announcement address A1of FIG. 2.

FIG. 4 is a schematic block diagram of a transmission address An of FIG. 2.

FIGS. 5A and 5B are a flow chart showing the steps performed by a client node 30 of FIG. 1.

FIG. 6 is a flow chart showing the steps performed by a server node 20 of FIG. 1.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a schematic block diagram of a typical computer network adapted for accessing video data streams. The network comprises a network structure 10, server nodes 20 a-x, and client nodes 30 a-m. The network structure 10 may be any applicable network configuration, such as a star-wired or a bus topology. Server nodes 20 a-x perform tasks for the network. The server nodes 20 a-x are connected to the network structure 10 by respective cabling 12 a-x. Likewise, the client nodes 30 a-m are connected to the network structure 10 by respective cabling 13 a-m. The client nodes 30 a-m are operated by users accessing the network. The network may be compatible with any network protocol supporting multicast addresses, including Ethernet, IEEE 802.3, and FDDI (ANSI X3T9.5). Although a preferred embodiment is described in terms of video data streams, the invention applies to computer networks for transmitting any data streams between nodes.

The network 10 is allocated at least one block of N multicast addresses A1-An according to the particular network protocol. One of the allocated multicast address A1 is an announcement address. Each server 20 a-x periodically transmits announcement messages on the announcement address A1. The selection of the announcement interval is a trade-off between announcing frequently so that clients 30 a-m can rapidly access data and avoiding an unnecessary load on the network 10 and the servers 20 a-x. In a preferred embodiment of the invention, the announcement interval is on the order of a few seconds. The remaining allocated multicast addresses A2-An are considered to be in either a pool of unassigned multicast addresses 12 or a table of assigned multicast addresses 14. These remaining multicast addresses A2-An are cooperatively assigned by the servers 20 a-x and readable by all servers 20 a-x and all clients 30 a-m on the network 10.

In a preferred embodiment, the cooperation between the servers is entirely distributed. Instead of using a central database, each server node 20 a-x on the network 10 maintains a view of the multicast addresses A1-An. The server nodes 20 a-x maintain respective views 24 a-x, the views are maintained in the respective node's local address space. Assignment information is shared between the nodes on the network 10. Changes in the assignment status of the multicast addresses are tracked by the server nodes 20 a-x. From the announcement address A1, the client nodes 30 a-m may track the data streams being transmitted on the assigned multicast addresses. On a steady-state network 10, all server views 24 a-x are synchronized to be identical.

In a preferred embodiment of the invention, the server nodes 20 a-x service video data for the client nodes 30 a-m. Connected to the server nodes 20 a-x may be such devices as tuners 21 and video players 23. Tuners 21 may collect TV video signals from local broadcasts or satellites. Video players 23 may be video cassette players or CD ROMs connected to a video library 25. For simplicity and clarity of description, each server node 20 is shown connected to one video device. A server node 20 may have access to more than one video device, and each video device may in turn be of a separate type.

The server nodes 20 a-x typically compress video signals into video data streams for transmission over the network structure 10. Client nodes 30 a-m receive the video data streams. The client nodes 30 a-m may then manipulate the video data streams, decompress the video data streams into video signals for display or recording, or otherwise process the video data streams.

Server nodes 20 a-x transmit the video data streams over the network 10 by using multicast addresses. FIG. 2 shows the address assignments for the N multicast addresses allocated to the network. Address A1 is the announcement address. A single announcement address A1 on the network is used by all servers 20 a-x to supply video program information to all clients 30 a-m. Addresses A2-An are assignable transmission addresses. The servers 20 a-x use the assignable transmission addresses A2-An to transmit the video data streams to the clients 30 a-m.

FIG. 3 shows the relevant fields of the data packets 16 available at the announcement address A1. Each announcement packet 16 contains fields for the server name A1a, the network address of the server A1b, the description of data streams being transmitted by the server A1c, the multicast address where the video data is being transmitted A1d, and a list of data streams available from the server A1e. The description of a data stream is unique for that data stream, regardless of the network on which the data stream is available. The use of unique descriptions promotes conflict resolution as networks are linked together. In addition to the identified fields, the announcement packet 16 may have additional fields. FIG. 3 does not limit the number nor the size of fields available in the announcement packet 16. For example, the announcement packet 16 may supply a database address where the client 30 can randomly access pertinent information, such as an index of available video programs cross-referenced to servers capable of providing the video program and servers currently transmitting the video program over the network.

FIG. 4 shows the relevant fields of a data packet 18 available at a transmission address An. The transmission packet 18 contains a header field Anh for identifying such information as the sending server and the data stream and a field Anb containing a frame of the data stream. FIG. 4 does not limit the number of fields available in the transmission packet 18 nor the size of the fields.

FIGS. 5A and 5B provide a flow chart of the processing performed by the client nodes 30 a-m. Client processing begins at step 300 of FIG. 5A. As shown at step 305, the client 30 monitors the announcement address A1. By monitoring the announcement packets 16 at announcement address A1, the client 30 can generate a list of all video programs being transmitted by each server 20 and all available video programs that the servers 20 a-x are capable of transmitting. At step 310, the client 30 selects a video data stream in which a user is interested. To continue, the client 30 must determine whether the selected video data stream is already being transmitted by a server 20, as shown at step 315.

If the selected video data stream is not currently being transmitted, the client 30 must cause a server 20 to transmit the video data stream. At step 320, the client 30 sends a request over the network to an appropriate server 20 having access to the desired video data stream. The request instructs the server 20 to transmit over the network the video data stream from its video source. The client 30 then waits for an announcement from the server 20, shown at 325. The announcement for the video data stream will contain the transmission address An for the video data stream in the transmission address field A1d.

After reviewing the request sent by a client at 320, the server 20 determines a transmission address An from available addresses as discussed below and announces that transmission address An in the transmission address field A1d at announcement address A1. The server 20 then transmits a video data stream comprising frames of data at the transmission address An. To read the data stream, a client 30 reads continuous data packets 18 at the transmission address An.

Turning to step 330 of FIG. 5B, the client 30 reads data from a transmission packet 18. In the header Anh of each transmission packet 18 is information indicating the identity of the server 20 sending the video data and a description of the video data. As shown at step 335, if the client 30 does not read an expected header from the transmission address, then the client 30 may have lost the video data stream. In the case of a lost data stream, the client 30 waits for a new announcement at step 325. As discussed below, the transmission address An for the video data stream may be changed by the server 20 because of conflicts between servers over the transmission address An.

In an alternative embodiment of the invention, the client 30 monitors the announcement address A1 for any new announcements related to video programs in which the users are interested. Upon detecting a change in the transmission address An, the client 30 switches to a new transmission address An, to read the video data stream.

If the client 30 reads a proper transmission packet 18, then the client 30 processes the data frame Anb at step 340. Processing the data frame Anb may involve manipulating the data or decompressing the data to create a video image.

The steps of reading and processing transmission packets 18 continues until the client 30 is finished with the video data stream. Periodically, the client 30 sends a keep-alive message to the server 20. For example, the client 30 sends a keep-alive message at rate T/2, where T is the server timeout period (described below). The keep-alive message informs the server 20 that the client 30 is still reading the video data stream. As long as a client 30 is reading the data, the server 20 will continue to transmit the video data stream on the transmission address An. The step of sending the periodic keep-alive message is shown at step 350. A client 30 that does not send periodic keep-alive messages may read the video data steam, but that client 30 risks having the data stream terminate without notice. When the client 30 finishes reading the video data stream, processing ends and the routine returns at step 355.

In an alternative embodiment of the invention, the client 30 sends a message to a server 20 whenever the client 30 starts to read a data stream from a transmission address An assigned to that server 20. The client 30 then sends a message to the transmitting server 20 when it stops reading from the transmission address An. The server 20 continues to transmit the data stream at the transmission address An until the count of clients 30 a-m reading the transmission address An becomes zero. Unfortunately, the server 20 is not guaranteed to receive either the start or stop message. If a start message is not received by the server 20, then the server 20 may terminate a transmission while a client 30 is reading the data stream. If a stop message is not received by the server 20, then the server 20 may continue to transmit a data stream indefinitely. Consequently, this alternative embodiment is less desirable than the keep-alive embodiment.

In an alternative embodiment of the invention, a client 30 may generate the list of video programs by scanning the multicast addresses A2-An and sampling transmission packets 18. Active transmissions can be identified by the existence of a transmission packet 18 at a multicast address An. By reading the header Anh of the transmission packet 18, the client 30 can determine the contents of the transmission on that transmission address. From the header Anh of the transmission packet 18, the client 30 can generate a list of video programs on assigned multicast addresses without accessing an announcement address A1.

Similarly, the announcement address may only provide clients 30 a-m with assigned multicast addresses A1d without a description of the data stream A1c. In that case, the client 30 can generate a list of assigned multicast addresses. By using the list of assigned multicast addresses, instead of the larger set of allocated multicast addresses A2-An, the client 30 can reduce the scanning time.

FIG. 6 is a flow chart of the server 20 processing steps. At network initialization, all non-dedicated multicast addresses A2-An are unassigned and are in the pool of unassigned multicast addresses 12. The processing is initiated by a client request for a video data stream that is not being transmitted over the network 10. Alternatively, the server 20 may automatically transmit particular video data streams independent of client requests. For example, a server 20 may transmit the particular video data stream during the duration of that data stream's availability (e.g. news broadcasts, network programming, etc.). After the video data stream is selected, the server 20 must select a multicast address for transmitting the particular video data stream.

Upon entry at step 200, the server 20 selects a candidate transmission address An from the pool of unassigned multicast addresses 12, as shown in step 210. In a preferred embodiment of the invention, the server 20 selects addresses from the pool of unassigned multicast addresses 12 in a random fashion. In an alternative embodiment of the invention, the server 20 sequentially selects the next available address from the pool of unassigned multicast addresses 12. Once a candidate transmission address An is selected, the server 20 must notify the client 30 and other servers 20 a-x of the selection.

The server 20 notifies the clients 30 a-m and the other servers 20 a-x by sending an announcement message at step 220. The announcement is sent over the announcement address A1 as shown in FIG. 3. To facilitate rapid recognition by the clients 30 a-m and other servers 20 a-x, the announcement message is queued to the announcement address A1 immediately. In a preferred embodiment of the invention, two announcement messages are sent in succession at step 220. Preferably, the announcement message is sent twice during the currently active announcement interval. After the announcement messages have been queued to the announcement address A1, the server 20 is ready to transmit the video data stream.

The server 20 transmits the video data stream at step 230. The video data stream is transmitted at the transmission address An. In a preferred embodiment, there is only one video data stream being transmitted at a transmission address An during steady state. However, it is possible that multiple servers 20 a-x may simultaneously select an identical candidate transmission address An from the pool of unassigned multicast addresses 12. In that case, there would be a conflict over a selected transmission address An. Until the conflict is resolved, there may be multiple servers 20 a-x transmitting on a single transmission address An. Because clients 30 a-m read only data frames carrying requested information, the system can tolerate short-term conflicts over a multicast address. However, to promote network efficiency, conflicts over a multicast address are resolved so that only one data stream is transmitted per multicast address.

The servers 20 a-x are responsible for resolving conflicts over transmission addresses. Each server 20 monitors the announcement address A1 as shown at step 240. By monitoring the announcement address A1, each server 20 maintains a local table of assigned multicast addresses 14 in a local view 24. Alternatively, the table may be cooperatively maintained in a shared database. In particular, the server 20 recognizes conflicts between itself and other servers 20 a-x over a transmission address An.

Once a conflict is detected, as shown at step 250, the servers 20 a-x resolve the conflict. In a preferred embodiment of the invention, a priority system is used to resolve the conflict as shown at step 260. In a preferred embodiment of the invention, a server's priority is based on the server's network address. In particular, a server 20 having a numerically higher-valued network address has priority over a server 20 having a numerically lower-valued network address. The server 20 with the highest numeric network address will keep the selected transmission address An.

Alternatively, numerically lower-valued network addresses could provide priority over numerically higher-valued network addresses. All other servers 20 that conflict with the priority server 20, will select another candidate transmission address An, from the pool of unassigned multicast addresses 12 and continue at step 210.

If no conflict is detected or if the server 20 has the highest priority, the selected candidate transmission address An becomes assigned to the server 20. The processing then returns to the calling routine at 270.

Typically, the assignment and transmitting continue until there are no clients 30 a-m signaling an interested in the data stream to the server 20. In a preferred embodiment, the server 20 terminates the transmission and deassigns the multicast address when no keep-alive messages are received within a time-out period, T. A reasonable time-out period is ten minutes (T=10 min). In an alternative embodiment of the invention, the server 20 terminates the transmission and deassigns the multicast address when the count of clients 30 a-m reading the data stream becomes zero. If the data stream is being automatically transmitted, then the server 20 may automatically terminate the transmission, such as at the end of a transmission duration.

Equivalents

Those skilled in the art will know, or be able to ascertain using no more than routine experimentation many equivalents to specific embodiments to the invention described herein.

These and all other equivalents are intended to be encompassed by the following claims.

Claims (54)

What is claimed is:
1. A communication protocol for transmitting a data stream between nodes on a computer network having a plurality of multicast addresses, the protocol comprising:
a multicast address designated as an announcement address for a source node; and
a packet of announcement data transmitted from the source node on the announcement address, the announcement data including an indication of a multicast address for a data stream supplied by the source node.
2. The protocol of claim 1 wherein the announcement data further includes a description of the data stream.
3. The protocol of claim 1 wherein the announcement data further includes an indication of the source node supplying the data stream.
4. The protocol of claim 1 wherein the announcement data further includes an indication of additional data streams available from the source node.
5. The protocol of claim 1 wherein the announcement data is periodically transmitted based on an announcement interval.
6. The protocol of claim 5 wherein the announcement data is further transmitted during an announcement interval in response to an assignment of a multicast address to a data stream.
7. The protocol of claim 1 further comprising a request from a receiving node to the source node for transmission of the data stream.
8. The protocol of claim 1 further comprising a keep-alive message from a receiving node to the source node.
9. The protocol of claim 1 further comprising a start message from a receiving node to indicate that the receiving node is reading the data stream.
10. The protocol of claim 9 further comprising a stop message from the receiving node to the source node indicating that the receiving node stopped reading the data stream.
11. A method for transmitting a data stream between nodes on a computer network having a plurality of multicast addresses, the method comprising:
designating an announcement address for a source node as a multicast address; and
transmitting a packet of announcement data from the source node on the announcement address, wherein the announcement data includes an indication of a multicast address for a data stream supplied by the source node.
12. The method of claim 11 wherein the announcement data further includes a description of the data stream.
13. The method of claim 11 wherein the announcement data further includes an indication of the source node supplying the data stream.
14. The method of claim 11 wherein the announcement data further includes an indication of additional data streams available from the source node.
15. The method of claim 11 further comprises periodically transmitting the announcement data based on an announcement interval.
16. The method of claim 15 further comprises further transmitting the announcement data during an announcement interval in response to an assignment of a multicast address to a data stream.
17. The method of claim 11 further comprising, from a receiving node to the source node, requesting transmission of the data stream.
18. The method of claim 11 further comprising transmitting a keep-alive message from a receiving node to the source node.
19. The method of claim 11 farther comprising transmitting a start message from a receiving node to indicate that the receiving node is reading the data stream.
20. The method of claim 19 further comprising transmitting a stop message from the receiving node to the source node to indicate that the receiving node stopped reading the data stream.
21. A communication protocol for transmitting a data stream between nodes on a computer network having a plurality of multicast addresses, the protocol comprising:
a multicast address designated as an announcement address for a source node; and
a packet of announcement data transmitted from the source node on the announcement address at least periodically, the announcement data including an indication of a multicast address for a data stream supplied by the source node and a description of the data stream.
22. The protocol of claim 21 wherein the announcement data further includes an indication of the source node supplying the data stream.
23. The protocol of claim 21 wherein the announcement data further includes an indication of additional data streams available from the source node.
24. The protocol of claim 21 wherein the announcement data is periodically transmitted based on an announcement interval.
25. The protocol of claim 24 wherein the announcement data is further transmitted during an announcement interval in response to an assignment of a multicast address to a data stream.
26. The protocol of claim 21 further comprising a request from a receiving node to the source node for transmission of the data stream.
27. The protocol of claim 21 further comprising a keep-alive message from a receiving node to the source node.
28. The protocol of claim 21 further comprising a start message from a receiving node to indicate that the receiving node is reading the data stream.
29. The protocol of claim 28 further comprising a stop message from the receiving node to the source node indicating that the receiving node stopped reading the data stream.
30. A method for transmitting a data stream between nodes on a computer network having a plurality of multicast addresses, the method comprising:
designating an announcement address for a source node as a multicast address; and
transmitting a packet of announcement data from the source node on the announcement address at least periodically, wherein the announcement data includes an indication of a multicast address for a data stream supplied by the source node and a description of the data stream.
31. The method of claim 30 wherein the announcement data further includes an indication of the source node supplying the data stream.
32. The method of claim 30 wherein the announcement data further includes an indication of additional data streams available from the source node.
33. The method of claim 30 further comprises periodically transmitting the announcement data based on an announcement interval.
34. The method of claim 33 further comprises further transmitting the announcement data during an announcement interval in response to an assignment of a multicast address to a data stream.
35. The method of claim 30 further comprising, from a receiving node to the source node, requesting transmission of the data stream.
36. The method of claim 30 further comprising transmitting a keep-alive message from a receiving node to the source node.
37. The method of claim 30 further comprising transmitting a start message from a receiving node to indicate that the receiving node is reading the data stream.
38. The method of claim 37 further comprising transmitting a stop message from the receiving node to the source node to indicate that the receiving node stopped reading the data stream.
39. A communication protocol for transmitting a data stream between nodes on a computer network having a plurality of multicast addresses, the protocol comprising:
a multicast address designated as an announcement address for a source node; and
a packet of announcement data transmitted from the source node on the announcement address, the announcement data including an indication of a multicast address for a data stream supplied by the source node, a description of the data stream, an indication of the source node supplying the data stream, and an indication of additional data streams available from the source node.
40. The protocol of claim 39 wherein the announcement data is periodically transmitted based on an announcement interval.
41. The protocol of claim 40 wherein the announcement data is further transmitted during an announcement interval in response to an assignment of a multicast address to a data stream.
42. The protocol of claim 39 further comprising a request from a receiving node to the source node for transmission of the data stream.
43. The protocol of claim 39 further comprising a keep-alive message from a receiving node to the source node.
44. The protocol of claim 39 further comprising a start message from a receiving node to indicate that the receiving node is reading the data stream.
45. The protocol of claim 44 further comprising a stop message from the receiving node to the source node indicating that the receiving node stopped reading the data stream.
46. The protocol of claim 39 wherein the announcement data includes a reference to a database.
47. A method for transmitting a data stream between nodes on a computer network having a plurality of multicast addresses, the method comprising:
designating an announcement address for a source node as a multicast address; and
transmitting a packet of announcement data from the source node on the announcement address, wherein the announcement data includes an indication of a multicast address for a data stream supplied by the source node, a description of the data stream, an indication of a server node supplying the data stream, and an indication of additional data streams available from the source node.
48. The method of claim 47 further comprises periodically transmitting the announcement data based on an announcement interval.
49. The method of claim 48 further comprises further transmitting the announcement data during an announcement interval in response to an assignment of a multicast address to a data stream.
50. The method of claim 47 further comprising, from a receiving node to the source node, requesting transmission of the data stream.
51. The method of claim 47 further comprising transmitting a keep-alive message from a receiving node to the source node.
52. The method of claim 47 further comprising transmitting a start message from a receiving node to indicate that the receiving node is reading the data stream.
53. The method of claim 52 further comprising transmitting a stop message from the receiving node to the source node to indicate that the receiving node stopped reading the data stream.
54. The method of claim 47 wherein the announcement data includes a reference to a database.
US09480904 1992-11-25 2000-01-11 Dynamic assignment of multicast network addresses Expired - Fee Related US6377997B1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US07981274 US6018771A (en) 1992-11-25 1992-11-25 Dynamic assignment of multicast network addresses
US09480904 US6377997B1 (en) 1992-11-25 2000-01-11 Dynamic assignment of multicast network addresses

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US09480904 US6377997B1 (en) 1992-11-25 2000-01-11 Dynamic assignment of multicast network addresses
US10128029 US7010597B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses
US10128007 US6665727B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US07981274 Continuation US6018771A (en) 1992-11-25 1992-11-25 Dynamic assignment of multicast network addresses

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US10128029 Division US7010597B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses
US10128007 Division US6665727B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses

Publications (1)

Publication Number Publication Date
US6377997B1 true US6377997B1 (en) 2002-04-23

Family

ID=25528257

Family Applications (4)

Application Number Title Priority Date Filing Date
US07981274 Expired - Lifetime US6018771A (en) 1992-11-25 1992-11-25 Dynamic assignment of multicast network addresses
US09480904 Expired - Fee Related US6377997B1 (en) 1992-11-25 2000-01-11 Dynamic assignment of multicast network addresses
US10128007 Expired - Fee Related US6665727B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses
US10128029 Expired - Fee Related US7010597B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US07981274 Expired - Lifetime US6018771A (en) 1992-11-25 1992-11-25 Dynamic assignment of multicast network addresses

Family Applications After (2)

Application Number Title Priority Date Filing Date
US10128007 Expired - Fee Related US6665727B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses
US10128029 Expired - Fee Related US7010597B2 (en) 1992-11-25 2002-04-22 Dynamic assignment of multicast network addresses

Country Status (1)

Country Link
US (4) US6018771A (en)

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2000066044A1 (en) 1999-05-05 2000-11-09 Michelson Gary K Nested interbody spinal fusion implants
US20020116520A1 (en) * 1992-11-25 2002-08-22 Compaq Information Technologies Group L.P. Dynamic assignment of multicast network addresses
US20030154307A1 (en) * 2002-01-31 2003-08-14 3Com Corporation Method and apparatus for aggregate network address routes
US20040148421A1 (en) * 2003-01-23 2004-07-29 International Business Machines Corporation Systems and methods for the distribution of bulk data using multicast routing
US6798782B1 (en) 1999-12-10 2004-09-28 Sun Microsystems, Inc. Truly anonymous communications using supernets, with the provision of topology hiding
US6870842B1 (en) * 1999-12-10 2005-03-22 Sun Microsystems, Inc. Using multicasting to provide ethernet-like communication behavior to selected peers on a network
US6938169B1 (en) 1999-12-10 2005-08-30 Sun Microsystems, Inc. Channel-specific file system views in a private network using a public-network infrastructure
US6970941B1 (en) 1999-12-10 2005-11-29 Sun Microsystems, Inc. System and method for separating addresses from the delivery scheme in a virtual private network
US6977929B1 (en) 1999-12-10 2005-12-20 Sun Microsystems, Inc. Method and system for facilitating relocation of devices on a network
US20060262795A1 (en) * 2003-11-25 2006-11-23 Cisco Technology, Inc. Reliable multicast communication
US7336790B1 (en) 1999-12-10 2008-02-26 Sun Microsystems Inc. Decoupling access control from key management in a network
US7765581B1 (en) 1999-12-10 2010-07-27 Oracle America, Inc. System and method for enabling scalable security in a virtual private network

Families Citing this family (74)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6160843A (en) * 1996-03-29 2000-12-12 Cisco Technology, Inc. Communication server apparatus providing XDSL services and method
US7266686B1 (en) 1996-05-09 2007-09-04 Two-Way Media Llc Multicasting method and apparatus
US6728784B1 (en) * 1996-08-21 2004-04-27 Netspeak Corporation Collaborative multimedia architecture for packet-switched data networks
ES2290986T3 (en) 1997-03-12 2008-02-16 Nomadix, Inc. Nomada transmitter or router.
US6446108B1 (en) * 1997-07-18 2002-09-03 Lucent Technologies Inc. Method for wide area network service location
US6718387B1 (en) * 1997-12-10 2004-04-06 Sun Microsystems, Inc. Reallocating address spaces of a plurality of servers using a load balancing policy and a multicast channel
CA2239133C (en) * 1998-05-28 2007-08-28 Newbridge Networks Corporation Multicast methodology and apparatus for backpressure - based switching fabric
US6092120A (en) * 1998-06-26 2000-07-18 Sun Microsystems, Inc. Method and apparatus for timely delivery of a byte code and serialized objects stream
JP3786328B2 (en) * 1998-07-27 2006-06-14 株式会社日立製作所 Server and a communication control method
US8713641B1 (en) 1998-12-08 2014-04-29 Nomadix, Inc. Systems and methods for authorizing, authenticating and accounting users having transparent computer access to a network using a gateway device
US7194554B1 (en) 1998-12-08 2007-03-20 Nomadix, Inc. Systems and methods for providing dynamic network authorization authentication and accounting
US8266266B2 (en) 1998-12-08 2012-09-11 Nomadix, Inc. Systems and methods for providing dynamic network authorization, authentication and accounting
US6381029B1 (en) * 1998-12-23 2002-04-30 Etrauma, Llc Systems and methods for remote viewing of patient images
JP3644009B2 (en) * 1999-02-19 2005-04-27 富士通株式会社 Multicast session management device
US6707796B1 (en) * 1999-05-07 2004-03-16 Nortel Networks Limited System device and method for reducing forwarding states in a communication system
WO2000076158A1 (en) 1999-06-08 2000-12-14 The Trustees Of Columbia University In The City Of New York Network telephony appliance and system for inter/intranet telephony
US7296091B1 (en) * 1999-06-18 2007-11-13 The Trustees Of Columbia University In The City Of New York System and method for receiving over a network a broadcast from a broadcast source
WO2001031885A3 (en) 1999-10-22 2002-01-17 Nomadix Inc Gateway device having an xml interface and associated method
US6880090B1 (en) * 2000-04-17 2005-04-12 Charles Byron Alexander Shawcross Method and system for protection of internet sites against denial of service attacks through use of an IP multicast address hopping technique
EP1314305A4 (en) 2000-08-11 2005-02-02 Univ Columbia System and method for unified messaging in inter/intranet telephony
US8250357B2 (en) 2000-09-13 2012-08-21 Fortinet, Inc. Tunnel interface for securing traffic over a network
US6970920B2 (en) * 2001-04-11 2005-11-29 International Business Machines Corporation Methods, systems and computer program products for communicating with unconfigured network devices on remote networks
US7328336B2 (en) * 2001-06-26 2008-02-05 Ncipher Corporation Ltd System and method for small-area system data processing
US20020198972A1 (en) * 2001-06-26 2002-12-26 International Business Machines Corporation Pre-boot multicast address management protocol for a computer network
US7181547B1 (en) 2001-06-28 2007-02-20 Fortinet, Inc. Identifying nodes in a ring network
US7830787B1 (en) * 2001-09-25 2010-11-09 Cisco Technology, Inc. Flooding control for multicast distribution tunnel
US7389359B2 (en) 2001-10-19 2008-06-17 Foundry Networks, Inc. Method and system for intelligently forwarding multicast packets
JP3869417B2 (en) * 2001-10-29 2007-01-17 ノキア コーポレイション Method of providing a multicast service and / or broadcast service to the user terminal
US7647422B2 (en) * 2001-11-06 2010-01-12 Enterasys Networks, Inc. VPN failure recovery
EP1488333B1 (en) 2002-03-01 2010-10-06 Enterasys Networks, Inc. Location aware data network
JP3622733B2 (en) 2002-03-07 2005-02-23 ブラザー工業株式会社 Address setting device, program
US7370093B2 (en) * 2002-03-07 2008-05-06 Brother Kogyo Kabushiki Kaisha Electronic apparatus and system capable of assigning appropriate address
US7428586B2 (en) * 2002-03-12 2008-09-23 Intel Corporation System and method for discovering undiscovered nodes using a registry bit in a point-to-multipoint network
US7230926B2 (en) * 2002-03-12 2007-06-12 Intel Corporation Isolation technique for networks
US20030195964A1 (en) * 2002-04-10 2003-10-16 Mane Pravin D. Managing multicast sessions
US7478139B2 (en) * 2002-04-29 2009-01-13 International Business Machines Corporation Shared resource support for internet protocol
US7376125B1 (en) 2002-06-04 2008-05-20 Fortinet, Inc. Service processing switch
US8060598B1 (en) 2002-07-01 2011-11-15 Sprint Communications Company L.P. Computer network multicasting traffic monitoring and compensation
US7266120B2 (en) * 2002-11-18 2007-09-04 Fortinet, Inc. System and method for hardware accelerated packet multicast in a virtual routing system
US7586874B2 (en) * 2003-01-06 2009-09-08 Interdigital Technology Corporation Wireless communication method and apparatus for providing multimedia broadcast services
US7720095B2 (en) 2003-08-27 2010-05-18 Fortinet, Inc. Heterogeneous media packet bridging
US7925778B1 (en) 2004-02-13 2011-04-12 Cisco Technology, Inc. Method and apparatus for providing multicast messages across a data communication network
US20050195756A1 (en) * 2004-02-26 2005-09-08 Frattura David E. Status announcement system and method
US7580403B2 (en) * 2004-02-26 2009-08-25 Enterasys Networks, Inc. Status transmission system and method
WO2005091901A3 (en) * 2004-03-10 2006-02-02 Enterasys Networks Inc Dynamic network detection system and method
US7945945B2 (en) * 2004-08-06 2011-05-17 Enterasys Networks, Inc. System and method for address block enhanced dynamic network policy management
KR20050099899A (en) * 2004-04-12 2005-10-17 엘지전자 주식회사 Allocation method for internet protocol multicast based universal plug and play network
US7720983B2 (en) * 2004-05-03 2010-05-18 Microsoft Corporation Fast startup for streaming media
US9532069B2 (en) 2004-07-30 2016-12-27 Euclid Discoveries, Llc Video compression repository and model reuse
US8902971B2 (en) * 2004-07-30 2014-12-02 Euclid Discoveries, Llc Video compression repository and model reuse
US9743078B2 (en) 2004-07-30 2017-08-22 Euclid Discoveries, Llc Standards-compliant model-based video encoding and decoding
US9578345B2 (en) 2005-03-31 2017-02-21 Euclid Discoveries, Llc Model-based video encoding and decoding
US7499419B2 (en) 2004-09-24 2009-03-03 Fortinet, Inc. Scalable IP-services enabled multicast forwarding with efficient resource utilization
US7347628B2 (en) 2004-11-08 2008-03-25 Enterasys Networks, Inc. Optical interface identification system
FR2878397A1 (en) * 2004-11-25 2006-05-26 Thomson Licensing Sa Apparatus and distribution method on a local diffuse network services
US7818401B2 (en) * 2004-12-23 2010-10-19 General Instrument Corporation Method and apparatus for providing decentralized load distribution
US8086232B2 (en) * 2005-06-28 2011-12-27 Enterasys Networks, Inc. Time synchronized wireless method and operations
US8451762B2 (en) * 2006-06-27 2013-05-28 Thomson Licensing Method and apparatus for reliably delivering multicast data
CN100490425C (en) * 2006-07-17 2009-05-20 杭州华三通信技术有限公司 Multicast network deploying method and multicast network
CA2676219C (en) * 2007-01-23 2017-10-24 Euclid Discoveries, Llc Computer method and apparatus for processing image data
US8295204B2 (en) * 2008-02-22 2012-10-23 Fujitsu Limited Method and system for dynamic assignment of network addresses in a communications network
US20090307758A1 (en) * 2008-06-05 2009-12-10 Motorola, Inc. Method and apparatus to facilitate using a multicast stream to provide on-demand streaming content
JP5567021B2 (en) 2008-10-07 2014-08-06 ユークリッド・ディスカバリーズ・エルエルシーEuclid Discoveries,Llc Video compression which are based on features
KR101700349B1 (en) * 2010-01-04 2017-01-26 삼성전자 주식회사 Display apparatus and streaming tranforting method of the same
JP5636995B2 (en) * 2011-02-07 2014-12-10 セイコーエプソン株式会社 Network communication apparatus, method, and program
JP5643425B2 (en) * 2011-04-27 2014-12-17 日本電信電話株式会社 Wireless communication system and a base station apparatus
US9031378B2 (en) * 2012-04-03 2015-05-12 Via Technologies, Inc. Method of managing multiple wireless video traffic and electronic device thereof
JP5863085B2 (en) * 2012-09-21 2016-02-16 コーニンクレッカ フィリップス エヌ ヴェKoninklijke Philips N.V. Method and apparatus for dynamic address allocation
US9613633B2 (en) 2012-10-30 2017-04-04 Nuance Communications, Inc. Speech enhancement
US9467369B2 (en) * 2013-08-02 2016-10-11 Time Warner Cable Enterprises Llc Packetized content delivery apparatus and methods
CA2942336A1 (en) 2014-03-10 2015-09-17 Euclid Discoveries, Llc Continuous block tracking for temporal prediction in video encoding
US9237177B2 (en) * 2014-03-28 2016-01-12 Gosub 60, Inc. Systems and methods for media streaming and presentation in an application environment
US10070155B2 (en) 2014-11-10 2018-09-04 Time Warner Cable Enterprises Llc Packetized content delivery apparatus and methods
US9743151B2 (en) 2015-06-24 2017-08-22 Time Warner Cable Enterprises Llc Multicast video program switching architecture

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5079767A (en) 1988-09-27 1992-01-07 Digital Equipment Corporation Method of multicast message distribution
US5276442A (en) 1991-02-22 1994-01-04 Ericsson Ge Mobile Communications Inc. Dynamic address allocation within RF trunking multisite switch
US6018771A (en) * 1992-11-25 2000-01-25 Digital Equipment Corporation Dynamic assignment of multicast network addresses

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4590467A (en) * 1983-10-13 1986-05-20 Rockwell International Corporation Local area network interface controller
JPS62239641A (en) * 1986-04-11 1987-10-20 Hitachi Ltd Multiple address communication system
US5842224A (en) * 1989-06-16 1998-11-24 Fenner; Peter R. Method and apparatus for source filtering data packets between networks of differing media
US5058109A (en) * 1989-06-28 1991-10-15 Digital Equipment Corporation Exclusionary network adapter apparatus and related method
US5150464A (en) * 1990-06-06 1992-09-22 Apple Computer, Inc. Local area network device startup process
US5297143A (en) * 1990-12-03 1994-03-22 Echelon Systems, Corp. Network communication protocol including a reliable multicasting technique
US5321693A (en) * 1991-01-25 1994-06-14 Digital Equipment Corporation Multicast address in a local area network where the local area network has inadequate multicast addressing capability
US5956335A (en) * 1991-01-25 1999-09-21 Cabletron Systems, Inc. Many to few group address translation through a network bridge
US5280481A (en) * 1991-09-20 1994-01-18 Extension Technology Corp. Local area network transmission emulator
US5287346A (en) * 1991-10-16 1994-02-15 Carnegie Mellon University Packet switch
US5309433A (en) * 1992-06-18 1994-05-03 International Business Machines Corp. Methods and apparatus for routing packets in packet transmission networks
US5425028A (en) * 1992-07-16 1995-06-13 International Business Machines Corporation Protocol selection and address resolution for programs running in heterogeneous networks
US5434872A (en) * 1992-07-28 1995-07-18 3Com Corporation Apparatus for automatic initiation of data transmission
US5835723A (en) * 1995-12-28 1998-11-10 Intel Corporation Dynamic assignment of multicast addresses
US7023813B2 (en) * 2002-12-31 2006-04-04 Motorola, Inc. Methods for managing a pool of multicast addresses and allocating addresses in a communications system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5079767A (en) 1988-09-27 1992-01-07 Digital Equipment Corporation Method of multicast message distribution
US5276442A (en) 1991-02-22 1994-01-04 Ericsson Ge Mobile Communications Inc. Dynamic address allocation within RF trunking multisite switch
US6018771A (en) * 1992-11-25 2000-01-25 Digital Equipment Corporation Dynamic assignment of multicast network addresses

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
FDDI Station Management (SMJ), Preliminary Draft Proposed American National Standard, ANSI Std. X3T9 (1992):117-126.
IEEE Standards for Local Area Networks: Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications, IEEE Std. 802.3 (1985):23-32.

Cited By (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7010597B2 (en) * 1992-11-25 2006-03-07 Hewlett-Packard Development Company, Lp. Dynamic assignment of multicast network addresses
US20020116520A1 (en) * 1992-11-25 2002-08-22 Compaq Information Technologies Group L.P. Dynamic assignment of multicast network addresses
WO2000066044A1 (en) 1999-05-05 2000-11-09 Michelson Gary K Nested interbody spinal fusion implants
US7685309B2 (en) 1999-12-10 2010-03-23 Sun Microsystems, Inc. System and method for separating addresses from the delivery scheme in a virtual private network
US6798782B1 (en) 1999-12-10 2004-09-28 Sun Microsystems, Inc. Truly anonymous communications using supernets, with the provision of topology hiding
US6870842B1 (en) * 1999-12-10 2005-03-22 Sun Microsystems, Inc. Using multicasting to provide ethernet-like communication behavior to selected peers on a network
US6938169B1 (en) 1999-12-10 2005-08-30 Sun Microsystems, Inc. Channel-specific file system views in a private network using a public-network infrastructure
US6970941B1 (en) 1999-12-10 2005-11-29 Sun Microsystems, Inc. System and method for separating addresses from the delivery scheme in a virtual private network
US6977929B1 (en) 1999-12-10 2005-12-20 Sun Microsystems, Inc. Method and system for facilitating relocation of devices on a network
US20060077977A1 (en) * 1999-12-10 2006-04-13 Sun Microsystems, Inc. System and method for separating addresses from the delivery scheme in a virtual private network
US7765581B1 (en) 1999-12-10 2010-07-27 Oracle America, Inc. System and method for enabling scalable security in a virtual private network
US7336790B1 (en) 1999-12-10 2008-02-26 Sun Microsystems Inc. Decoupling access control from key management in a network
US20030154307A1 (en) * 2002-01-31 2003-08-14 3Com Corporation Method and apparatus for aggregate network address routes
US7305489B2 (en) * 2002-01-31 2007-12-04 Utstarcom, Inc. Method and apparatus for aggregate network address routes
US20040148421A1 (en) * 2003-01-23 2004-07-29 International Business Machines Corporation Systems and methods for the distribution of bulk data using multicast routing
US7792984B2 (en) * 2003-01-23 2010-09-07 International Business Machines Corporation Systems and methods for the distribution of bulk data using multicast routing that mitigates network traffic on subnets
US20060262795A1 (en) * 2003-11-25 2006-11-23 Cisco Technology, Inc. Reliable multicast communication
US8346904B2 (en) * 2003-11-25 2013-01-01 Cisco Technology, Inc. Reliable multicast communication

Also Published As

Publication number Publication date Type
US6665727B2 (en) 2003-12-16 grant
US7010597B2 (en) 2006-03-07 grant
US20020116520A1 (en) 2002-08-22 application
US6018771A (en) 2000-01-25 grant
US20020116529A1 (en) 2002-08-22 application

Similar Documents

Publication Publication Date Title
US6119163A (en) Multicasting method and apparatus
US6654796B1 (en) System for managing cluster of network switches using IP address for commander switch and redirecting a managing request via forwarding an HTTP connection to an expansion switch
US5517488A (en) Method of load distribution for message processing in host system in local area network
US6310886B1 (en) Method and apparatus implementing a multimedia digital network
US5673393A (en) Managing bandwidth over a computer network having a management computer that allocates bandwidth to client computers upon request
US7133922B1 (en) Method and apparatus for streaming of data
US5548579A (en) System for effective allocation of network-wide bandwidth
US5410543A (en) Method for connecting a mobile computer to a computer network by using an address server
US5870554A (en) Server selection method where a client selects a server according to address, operating system and found frame for remote booting
US6496859B2 (en) System for network device location
US5886993A (en) System, device, and method for sharing contention mini-slots among multiple priority classes
US6134599A (en) System and method for organizing devices in a network into a tree using suitability values
US20030126277A1 (en) Apparatus and method for providing multimedia streaming service by using point-to-point connection
US6157622A (en) Communication apparatus and a method for controlling a communication apparatus
US5754799A (en) System and method for bus contention resolution
US5930473A (en) Video application server for mediating live video services
US7325073B2 (en) Peer to peer video on demand system selectively using client and server to forward the requested video program to another client
US6189034B1 (en) Method and apparatus for dynamic launching of a teleconferencing application upon receipt of a call
US20020062377A1 (en) Scalable directory, master and slave server based architecture for hosting application services
US5838912A (en) Distribution of digitally encoded presentations
US6151331A (en) System and method for providing a proxy FARP for legacy storage devices
US5862348A (en) Method and apparatus for connecting a client node to a server node based on load levels
US5878212A (en) System for updating mapping or virtual host names to layer-3 address when multimedia server changes its usage state to busy or not busy
US6571277B1 (en) Method and apparatus for scaling universal plug and play networks using atomic proxy replication
US20040064559A1 (en) Method and apparatus for dynamic assignment of network protocol addresses

Legal Events

Date Code Title Description
AS Assignment

Owner name: COMPAQ COMPUTER CORPORATION, TEXAS

Free format text: MERGER;ASSIGNOR:DIGITAL EQUIPMENT CORPORATION;REEL/FRAME:011776/0688

Effective date: 19991209

AS Assignment

Owner name: COMPAQ INFORMATION TECHNOLOGIES GROUP, L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COMPAQ COMPUTER CORPORATION;REEL/FRAME:012403/0293

Effective date: 20010620

CC Certificate of correction
AS Assignment

Owner name: COMPAQ INFORMATION TECHNOLOGIES GROUP, L.P., TEXAS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:DIGITAL EQUIPMENT CORPORATION;COMPAQ COMPUTER CORPORATION;REEL/FRAME:016334/0359;SIGNING DATES FROM 19991209 TO 20010620

Owner name: DIGITAL EQUIPMENT CORPORATION, MASSACHUSETTS

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:HAYDEN, PETER C.;REEL/FRAME:016334/0370

Effective date: 19921125

Owner name: HEWLETT-PACKARD DEVELOPMENT COMPANY, L.P., TEXAS

Free format text: CHANGE OF NAME;ASSIGNOR:COMPAQ INFORMATION TECHNOLOGIES GROUP L.P.;REEL/FRAME:016334/0385

Effective date: 20021001

FPAY Fee payment

Year of fee payment: 4

FPAY Fee payment

Year of fee payment: 8

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
FP Expired due to failure to pay maintenance fee

Effective date: 20140423