US6370142B1 - Method and apparatus for performing per-port IP multicast pruning - Google Patents
Method and apparatus for performing per-port IP multicast pruning Download PDFInfo
- Publication number
- US6370142B1 US6370142B1 US08/832,042 US83204297A US6370142B1 US 6370142 B1 US6370142 B1 US 6370142B1 US 83204297 A US83204297 A US 83204297A US 6370142 B1 US6370142 B1 US 6370142B1
- Authority
- US
- United States
- Prior art keywords
- multicast
- group
- stations
- switch
- membership
- 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 - Lifetime
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/54—Store-and-forward switching systems
- H04L12/56—Packet switching systems
- H04L12/5601—Transfer mode dependent, e.g. ATM
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/10—Packet switching elements characterised by the switching fabric construction
- H04L49/104—Asynchronous transfer mode [ATM] switching fabrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/25—Routing or path finding in a switch fabric
- H04L49/256—Routing or path finding in ATM switching fabrics
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/30—Peripheral units, e.g. input or output ports
- H04L49/3081—ATM peripheral units, e.g. policing, insertion or extraction
- H04L49/309—Header conversion, routing tables or routing tags
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04Q—SELECTING
- H04Q11/00—Selecting arrangements for multiplex systems
- H04Q11/04—Selecting arrangements for multiplex systems for time-division multiplexing
- H04Q11/0428—Integrated services digital network, i.e. systems for transmission of different types of digitised signals, e.g. speech, data, telecentral, television signals
- H04Q11/0478—Provisions for broadband connections
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/35—Switches specially adapted for specific applications
- H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
Definitions
- the invention relates generally to the field of switched networks and Internet Protocol (IP) multicast forwarding. More specifically, the invention relates to pruning IP multicast traffic within an IP subnet and the determination of IP multicast group memberships in a switched network.
- IP Internet Protocol
- Multicast is the transmission of information to a group of recipients (e.g., a multicast group) via a single transmission by the source.
- a protocol used to support membership registration for IP multicast traffic is Internet Group Management Protocol (IGMP).
- IGMP is used by end-stations in networks to communicate the addresses of IP multicast groups in which the end-stations would like to participate.
- routers Using this multicast group membership information from IGMP, routers carry out multicast pruning. Multicast packets are transmitted in such a way that only subnets with members (learned through IGMP) receive the appropriate multicast traffic. Further, multicast packets are forwarded in such a way that there is no “looping” of packets in the network. Loops are avoided within subnets by using a spanning tree algorithm and across subnets through the use of a multicast routing protocol. This prior method of multicast pruning performed by IGMP routers will be discussed further with reference to FIG. 2 .
- IGMP messages have an eight octet format including a type field and a group address field. IGMP messages are encapsulated in IP Datagrams using an IP protocol number of two. Three types of IGMP messages are exchanged between IP hosts and multicast routers: membership query messages, membership report messages, and leave group messages. As illustrated by FIG. 1A, membership query messages (represented with solid arrows) are used by multicast routers (e.g., router 110 ) to learn which IP multicast groups have members on a particular attached network. The membership query messages are forwarded to each connected interface by intermediate switches 120 . IP hosts 130 respond to membership query messages with membership reports (represented with dashed arrows) which identify a multicast group in which the reporting IP host is participating. IP hosts 130 can also send unsolicited membership reports when they wish to join a multicast group. Further, leave group messages (not shown) may be sent by IP hosts when they no longer wish to participate in a particular multicast group.
- membership query messages represented with solid arrows
- membership reports represented
- the IGMP protocol 145 runs on router 110 .
- the IGMP protocol periodically generates IGMP membership queries using a set of timers 150 .
- multicast routers Based upon the IGMP membership reports received from each attached network, multicast routers track IP multicast group membership represented on a given port by maintaining a multicast groups table 155 .
- Multicast routers maintain lists of multicast group memberships for each attached network and a timer for each group membership.
- the multicast group membership information is used to eliminate branches that do not lead to members of the multicast group to which the multicast packet is addressed.
- a multicast router may assume the role of an IGMP querier or a non-querier.
- a multicast router assumes it is the IGMP querier for each attached network. However, if a multicast router hears a query message from another router with a lower IP address, it will become a non-querier for that network.
- This querier election mechanism prevents more than one multicast router from being a querier for a given network. Further details about this protocol are available in Fenner, W., “Internet Group Management Protocol, Version 2,” INTERNET-DRAFT, Xerox PARC, May 20, 1996 and also in S. Deering, Request for Comments 1112, “Host Extensions for IP Multicasting,” August 1989.
- FIG. 2 illustrates the pruning of subnets for a multicast message in a routed network in which one or more end-stations reside on switched subnetworks.
- the routed network includes routers 201 through 205 , Layer 2 switches 250 through 254 , and endstations 231 through 244 .
- Routers 201 through 205 are multicast routers running IGMP or an equivalent group management protocol to discover the IP multicast group memberships of each attached network.
- Switches 250 through 254 represent switches employing current forwarding logic.
- Such a switch 120 is illustrated in FIG. 1 C.
- the switch 120 includes a forwarding engine 160 .
- the forwarding engine 160 has no forwarding rules (forwarding logic) for IP multicast traffic.
- the switch 120 when the switch 120 receives a packet with an IP multicast address, the address is mapped to a medium dependent broadcast address such as an Ethernet broadcast address and processed using the associated broadcast forwarding logic. Therefore, in the present example, since the forwarding engine 160 has no knowledge of which ports lead to end-stations participating in IP multicast groups, upon receiving an IP multicast packet, the forwarding engine 160 must forward the packet to each of its connected interfaces. This forwarding behavior is currently required to assure that all end-stations listening for the IP multicast group addressed by the packet will receive the packet.
- end-stations 231 through 244 are all members of either the white multicast group or the black multicast group represented with hollow or solid circles, respectively.
- the thick lines represent the network segments upon which the multicast message will be forwarded.
- the multicast message will be forwarded from router 203 to routers 202 and 205 .
- the multicast message will not be forwarded from router 203 to router 204 as no black multicast group members exist on this network segment. While this prior method of pruning is sufficient to eliminate multicast traffic on the network segment connecting router 203 and router 204 , it is limited to pruning at a network level.
- a disadvantage of this prior approach is switches 120 forward IP multicast packets to all of their ports regardless of the IP multicast groups represented on a given port. Therefore, non-multicast group members residing on a network segment with one or more IP multicast group members wind up having to process and filter packets to destination addresses in which they have no interest.
- this prior approach forces endstations 234 and 236 to process and filter IP multicast messages intended for end-stations 233 and 235 .
- end-stations 237 , 239 , 240 , 241 , and 242 are interrupted by IP multicast messages intended for end-station 238 . Having to process these undesired packets takes up valuable resources at the end-station. In addition, bandwidth on the link is wasted.
- IP multicast traffic such that multicast packets addressed to a particular multicast group address do not propagate into portions of a switched network in which no end-stations are listening for the particular multicast group address.
- a switch is coupled to one or more end-stations.
- IP Internet Protocol
- the switch forwards the packet only to those of the end-stations that are participating in the IP multicast group, thereby eliminating the exposure of multicast traffic to end-stations not participating in the IP multicast group.
- switches implementing per-port IP multicast pruning no longer burden non-multicast group members with packets in which they have no interest. In addition, bandwidth is conserved on the link to the end-station.
- IP multicast group membership can be solicited from end-stations residing on a given switched network in the absence of a multicast router.
- the switch first determines if another device is currently acting as a querier for the switched network. If no device is currently acting as the querier for the switched network, the switch originates a multicast group membership query and transmits the multicast group membership query onto one or more of its ports.
- the IP multicast group memberships in a switched network can be determined.
- a switch determines if another device is currently acting as a querier for the switched network. If no device is currently acting as a querier for the switched network, the switch sends a multicast group membership query on one or more of its ports.
- an end-station transmits a multicast group membership report to the switch.
- the multicast group membership report indicates the IP multicast group membership of the end-station.
- the switch records the IP multicast group membership of the end-station. In this manner, IP multicast pruning can be performed on a per-port basis within a switch even when no multicast routers are present on the network or when multicast is otherwise disabled.
- FIG. 1A illustrates how a multicast router determines multicast group membership.
- FIG. 1B is a block diagram of the multicast router of FIG. 1 A.
- FIG. 1C is a block diagram of the switches of FIG. 1 A.
- FIG. 2 illustrates a prior approach to the pruning of subnets for a multicast message in a routed network in which one or more end-stations reside on switched subnetworks.
- FIG. 3 illustrates switch forwarding logic according to one embodiment of the present invention.
- FIG. 4 illustrates the significance of employing per-port pruning when forwarding a multicast message in switched subnetworks according to one embodiment of the present invention.
- FIG. 5 is a flow diagram illustrating a method of performing per-port multicast pruning in a switched network according to one embodiment of the present invention.
- FIG. 6 is a flow diagram illustrating a method of forwarding multicast packets according to one embodiment of the present invention.
- FIG. 7 is a flow diagram illustrating a method of proxying IGMP membership reports according to one embodiment of the present invention.
- FIG. 8 is a flow diagram illustrating a method of pseudo-IGMP membership query generation according to one embodiment of the present invention.
- FIG. 9 illustrates a switching device according to an embodiment of the invention.
- FIG. 10 illustrates an entry in a master destination tag table according to an embodiment of the invention.
- FIG. 11 illustrates how information for constructing locally stored tables is derived from the destination mask field in the master destination tag table.
- the present invention includes various steps, which will be described below.
- the steps can be embodied in machine-executable instructions, which can be used to cause a general-purpose or special-purpose processor programmed with the instructions to perform the steps.
- the steps of the present invention might be performed by specific hardware components that contain hardwired logic for performing the steps, or by any combination of programmed computer components and custom hardware components.
- the present invention is not limited to any particular protocol for discovering IP multicast groups.
- the method and apparatus of the present invention are not limited to networks employing IGMP to discover IP multicast group membership. Rather, the disclosed method and apparatus is useful in connection with any group management protocol that discovers IP multicast group membership by way of a query-response mechanism.
- the current level of pruning provided by multicast routers is insufficient to prevent end-stations in switched networks from having to process and filter many packets to destination addresses in which they have no interest.
- pruning is only carried out to the subnet level, rather than to the end-station level.
- switches utilize the host reporting mechanism for group management protocols such as IGMP to learn IP multicast group membership for each of their ports. Once this group membership information is known, the forwarding of multicast messages can be limited to only those ports having a member of the multicast group being addressed. In this manner, multicast traffic destined for a particular group will be excluded from network segments that include no members of the multicast group.
- group management protocols such as IGMP
- FIG. 4 is useful for illustrating the significance of employing per-port pruning in a switched network.
- the network includes multicast routers 201 through 205 and end-stations 231 through 244 .
- switches 250 through 254 have been replaced by Layer 2 switches 450 through 454 which are capable of per-port IP multicast pruning.
- switches implementing per-port IP multicast pruning no longer burden non-multicast group members with packets in which they have no interest. For example, since switch 450 maintains a local mapping of IP multicast groups to ports, multicast packets addressed to the black multicast group are no longer transmitted to end-stations 234 and 236 .
- multicast packets addressed to the black multicast group are no longer forwarded to end-stations 237 and 239 by switch 453 and switch 454 no longer forwards black multicast group messages to end-stations 240 , 241 , and 242 .
- One advantage, therefore, of providing per-port pruning in a switch is the preservation of valuable end-station processing. For example, end-station processing is not consumed filtering “wrong addresses.” In addition, link bandwidth is not needlessly wasted transmitting multicast packets that will simply be dropped by the end-station at the other end of the link
- FIG. 5 is a flow diagram illustrating a method of performing per-port IP multicast pruning in a switched network according to one embodiment of the present invention.
- the host portion of IGMP in order to avoid duplicate membership reports, causes an end-station to suppress its IGMP membership report if it hears another IGMP membership report for an IP multicast group in which it is participating.
- Each end-station waits for a random time interval before responding to an IGMP membership query. If while waiting, an end-station sees an IGMP membership report from another end-station for the same IP multicast group, then the endstation will not generate an IGMP membership report.
- step 535 to be sure that each end-station generates an IGMP membership report for each IP multicast group in which it is interested, the switch needs to create the illusion that the end-station is the only system on the subnet interested in participating in that IP multicast group.
- an IGMP membership query is received by the switch.
- the IGMP membership query might have been originated by a querying multicast router or, according to another aspect of the present invention the IGMP membership query might have been originated by another switch. The latter possibility will become apparent after the discussion of pseudo-IGMP query generation.
- multicast group membership information is solicited from end-stations by forwarding the IGMP membership query to each end-station on the subnet.
- IGMP membership reports are received from end-stations that are participating in multicast groups.
- the switch suppresses forwarding the IGMP membership reports to other end-stations on the same subnet. In this manner, it appears to the host portion of IGMP running on each end-station that it is the only system reporting for the multicast groups in which it is participating. Since no end-station will hear reports corresponding to the multicast groups in which it is participating, each end-station that is participating in a multicast group is forced to respond to the IGMP membership query with an IGMP membership report.
- IGMP membership report forwarding by the switch will be discussed further below with respect to proxying of IGMP membership reports.
- multicast group destination lists are modified based upon the IGMP membership reports received in step 530 .
- the switch After an IGMP membership report is received, the switch records the IP multicast group membership of the end-station and the port on the switch to which the end-station is attached. The creation and subsequent maintenance of multicast group destination lists is discussed further below.
- a multicast message is received by the switch.
- the switch forwards the multicast message to a set of ports that includes only those end-stations that are participating in the multicast group addressed by the message. For example, the message can be forwarded based upon an appropriate multicast group destination list.
- a destination list can be thought of conceptually as a list of ports to which packets directed to the destination list are to be forwarded.
- Destination lists can be stored as entries in a data structure such as a table (e.g., a two dimensional array) or other suitable data structure such as a sorted linked list, or a search tree.
- destination lists are maintained for forwarding membership reports for a particular virtual local area network (VLAN), for VLAN forwarding, and for forwarding IP multicast packets to each IP multicast group represented in a particular VLAN.
- VLAN virtual local area network
- one or more of the destination lists can span VLANs. While one approach to the creation and maintenance of each of these destination lists will now briefly be discussed, it will be recognized that numerous other ways are possible.
- the report destination list includes the ports having either a querier or a non-querier router. Discovery of querier and non-querier routers can be performed manually or automatically. Manual discovery occurs as a result of a user or network administrator specifying ports containing routers such as non-querier routers during switch configuration, for example. The switch can, then access the manually entered information to update the report destination list. Automatic discovery occurs as a result of the switch detecting router queries by snooping or listening to multicast traffic. The report destination list is created upon VLAN creation. As group membership queries are received from routers, the receiving port is added to the report destination list.
- the Other_Querier_Present timer is the length of time which must pass before a determination can be made by IGMP as to whether or not a querier device such as a multicast router is present.
- a single timer can be maintained for the report destination list. When a single timer is used, rather than removing a particular port, all ports are removed from the report destination list. Importantly, however, manually configured ports should not be timed-out.
- the VLAN destination list contain all ports that are members of a particular VLAN.
- a forwarding table is maintained per VLAN which includes a multicast group destination list for each IP multicast group within the particular VLAN supporting multicasting.
- the forwarding table can be indexed by a function of the multicast group address using a hash function, for example.
- each multicast group destination list should contain all ports having members of the particular IP multicast group and all router ports. However, as will be discussed further below, in certain situations routers need not be members of every IP multicast group.
- the tables storing the destination lists can be indexed by “Destination tags” also referred to as “Dtags” and can be centrally located or distributed throughout the switch.
- Dtags can be centrally located or distributed throughout the switch.
- the forwarding table can be separated into two levels, a first level for mapping IP multicast group addresses to group multicast Dtags, and a second level for mapping the Dtags to ports.
- the forwarding table can be maintained by the switch in a manner similar to the GA-to-Dtag table, discussed below. Destination tags are discussed in detail below with reference to FIGS. 9 through 11.
- multicast group destination lists are created upon user configuration or dynamically based upon receipt of IGMP membership reports and queries. Thereafter, the switch updates the multicast group destination lists based upon IGMP membership reports and port expiration timers.
- a port report expiration timer is maintained for each multicast group destination list member. When a report is received, the receiving port is added to the appropriate multicast group destination list if it is not already a current member and the corresponding port report timer should be reset. If the port report timer expires, the port is removed from the multicast group destination list.
- any port may contain one or more IP multicast groups, thus any port may be in multiple multicast group destination lists.
- FIG. 3 is a logical view of the switch forwarding logic according to one embodiment of the present invention.
- Switch 310 can be a switching device such as the Bay Networks Centillion 100 switch.
- Switch 310 includes a plurality of ports including 355 , 360 , 370 , and 380 .
- the switch 310 also can accommodate one or more virtual local area networks (VLANs) such as VLAN 1 325 and VLAN N 350 .
- the switch also includes a master control process (MCP) also referred to as a “switch manager” 320 .
- MCP master control process
- the switch manager 320 maintains the destination lists and other tables used for forwarding.
- IP multicast group 1 it is assumed one or more members of IP multicast group 1 are on port 355 . Also, one or more members of IP multicast group 2 are assumed to be coupled to port 380 . Further, multicast routers are coupled to ports 360 and 370 . To assure all members of a particular IP multicast group receive packets addressed to the group, all multicast routers are made members of each IP multicast group. In this manner, a group member across a given router will receive each communication directed to its IP multicast group.
- multicast routers need not be made members of each IP multicast group in an environment in which multicast routers advertise their IP group memberships. It should be appreciated, in this situation, that a given multicast router need not be made a member of every IP multicast group, but rather its membership can be limited to the IP multicast groups which are advertised as being across the router.
- Bubble 335 depicts the VLAN query forwarding.
- IGMP membership queries are received by the switch, they are forwarded onto the VLAN destination list which contains each port participating in a particular VLAN.
- ports 355 through 380 are all participating in VLAN 1 325 .
- the multicast group 1 data forwarding bubble 330 represents the switch's forwarding engine forwarding a multicast packet to the multicast destination list maintained for group 1 .
- IP multicast packets forwarded onto the multicast destination list maintained for group 1 will be forwarded to ports 355 , 360 , and 370 . Since no members of multicast group 1 are coupled to port 380 , no multicast packets addressed to group 1 will be forwarded to port 380 .
- the multicast group 2 data forwarding bubble 345 illustrates the result of the switch's forwarding engine forwarding a multicast packet to the multicast destination list maintained for group 2 .
- IP multicast packets forwarded onto the multicast destination list maintained for group 2 will be forwarded to ports 360 , 370 and 380 .
- No members of multicast group 2 are coupled to port 355 , therefore, no multicast packets addressed to group 2 will be forwarded to port 355 .
- Bubble 340 depicts the report forwarding logic. Reports are only forwarded to ports coupled to multicast routers (including querying and non-querying routers) or other querying devices such as a switch generating pseudo-IGMP queries. As discussed above, this behavior is what forces each multicast group participant to respond with a report. As will be discussed further with reference to proxying of IGMP membership reports, in one embodiment, all reports are processed by the switch manager 320 prior to being forwarded.
- this embodiment illustrates that multicast destination lists can be maintained independently of VLANs. Specifically, separate VLANs need not be created for each IP multicast group. Rather, the multicast destination lists may be subsets of destinations within one or more VLANs. In this manner, the network administrator need not be exposed to the administrative complexity of managing additional VLANs. Further advantages will be apparent to those of ordinary skill in the art.
- forwarding logic described herein may be implemented in hardware, software or a combination thereof.
- software can maintain the tables required by the forwarding logic as described above by listening to membership reports and learning the group memberships of the switch's ports.
- FIG. 6 is a flow diagram illustrating a method of forwarding multicast packets according to one embodiment of the present invention.
- a packet is received by the switch at step 605 .
- the forwarding engine of the switch evaluates the destination address of the packet and the protocol identified in the packet. If the destination address is a multicast group address and if the protocol is IGMP, then the flow continues to step 620 . Otherwise, if the destination address is not a multicast group address or if the protocol is not IGMP, then the flow branches to step 615 .
- the packet is forwarded using normal forwarding rules.
- the forwarding engine determines the multicast group. If the multicast group is the all-systems multicast group (i.e., 224.0.0.1), then the flow follows the “yes” path to step 625 . Otherwise, if the multicast group is not the all-systems multicast group, then the flow continues with step 630 .
- step 625 it has previously been determined by step 620 that the packet is addressed to the all-systems multicast group, thus, the packet is forwarded to the ports in the VLAN destination list and to the switch manager 320 .
- the forwarding engine determines if the type field of the IGMP message indicates the messages is an IGMP membership report. If the packet type is report, then the flow branches to step 635 . However, if the packet type is other than report, the flow continues with step 640 .
- the IGMP membership report is forwarded to the switch manager 320 for report destination list processing.
- the switch manager 320 may simply forward the report onto the report destination list thereby forwarding the report to all ports having either a querier or a non-querier device.
- the switch manager 320 may be functioning as a proxy and suppress the forwarding of some reports as will be discussed further below.
- the forwarding engine determines if the group address in the IGMP message is a known IP multicast group.
- the group address is known, for example, if it can be found in the forwarding table, meaning at least one end-station has subscribed to the IP multicast group. In this example, if the group address is found in the forwarding table, then the flow continues with step 645 .
- the multicast packet is forwarded onto the appropriate group multicast destination list by retrieving the group multicast destination list or corresponding Dtag from the forwarding table, for example.
- step 650 the multicast packet is forwarded to all ports coupled to multicast routers using the report destination list. This behavior ensures IP multicast group members on other networks will be receive packets addressed to their IP multicast group.
- FIG. 7 is a flow diagram illustrating a method of proxying IGMP membership reports according to one embodiment of the present invention.
- the switch discovers which ports are coupled to multicast routers. This switch can detect multicast routers automatically or the ports on which multicast routers can be manually entered by an operator or a network administrator. The switch can automatically detect querier multicast routers by listening for IGMP membership queries, for example. However, non-querier multicast routers need to be manually entered if they are to receive IGMP membership reports. Otherwise, the port to which the non-querier was coupled would time-out when no IGMP membership queries were received.
- step 720 the ports discovered in step 710 are added to the report destination list.
- an IGMP membership report is received by the switch.
- the IGMP membership report might be in response to an earlier IGMP membership query sent by a querier device or it might be unsolicited.
- the switch forwards IGMP membership reports to the switch manager 320 .
- the switch manager 320 determines if the IGMP membership report is the first received for the multicast group being reported since the last IGMP membership query was received.
- the switch manager 320 can accomplish this, for example, by maintaining a “first-report” flag per multicast group on the switch or by other means such as maintaining a counter. Assuming a flag mechanism is used, when an IGMP membership query is received the flag can be set to a state indicating the first report for the group has not been sent.
- the flag should be set to a state indicating the first report has been sent. It may be also be useful to include a timer to toggle the flag should a membership query become lost. Regardless of the mechanism employed, if the IGMP membership report is the first received for the multicast group being reported, then processing continues with step 750 . Otherwise, processing continues at step 760 .
- the IGMP membership report is forwarded to each port in the report destination list. This proxying process can be repeated beginning with step 730 .
- step 760 since an IGMP membership report for this multicast group has already been forwarded to the ports coupled to multicast routers, the IGMP membership report can be ignored (e.g., discarded or dropped). The process can be repeated starting with step 730 . Note that the switch manager 320 will continue to discard IGMP membership reports for a previously reported multicast group until the next IGMP membership query is received by the switch.
- neighboring multicast routers can update their local tables that track IP multicast groups by processing only a single IGMP membership report per IP multicast group on the attached network.
- the multicast routers are protected from having to process large numbers of IGMP membership reports that might otherwise have a detrimental effect on their performance.
- a switch can periodically query each of its ports and forward one membership report per IP multicast group represented. After discovering which ports are coupled to multicast routers, the switch can independently query its ports rather than waiting for further membership queries.
- the prior pruning approach discussed with respect to FIGS. 1A through 2 is limited to networks including routers that support multicast routing. That is, one or more multicast routers must be present and additionally multicast routing must be enabled. When no multicast routers are present on the network or when multicast is otherwise disabled, it is desirable to continue to provide the ability to perform IP multicast pruning on a per-port basis within a switch. Therefore, it would be advantageous for a switch to detect the absence of a querier device and initiate IGMP membership queries of its own. The rest of the switches on the network can then use the IGMP membership reports triggered by the “pseudo-IGMP queries” to build local maps of IP multicast groups to ports as described above. These maps can then be used to control forwarding of multicast traffic within a subnet.
- FIG. 8 is a flow diagram illustrating a method of pseudo-IGMP membership query generation according to one embodiment of the present invention. This is accomplished by each switch performing the following steps.
- Steps 810 through 830 represent a state in which the switch is a non-querier. In this state, the switch waits until it determines that no querier device is present on the network. Upon determining that no querier device is present, however, the switch enters a second state and begins originating IGMP membership queries of its own.
- the switch sets the other querier present timer.
- the other querier present timer is the length of time required to make a determination as to whether or not a querier device is present.
- each switch adds a random value to the other querier present timer. If an IGMP membership query is received (step 820 ) prior to the expiration of the other querier present timer (step 830 ), then processing continues with step 810 , where the timer will be reset.
- step 830 if the other querier present timer has expired and no IGMP membership queries have been received, then processing continues with step 840 . However, while the timer remains active, processing loops back to step 820 .
- Steps 840 through 870 represent a state in which the switch has assumed the role of a querier device. In this state, the switch will periodically transmit IGMP membership queries on each of its ports until the switch hears an IGMP membership query.
- the switch sends IGMP membership queries over each port.
- the switch sets a membership query transmit timer.
- This timer represents the amount of time which must pass before a port is removed from the group destination lists. Essentially, if the timer expires and no IGMP membership reports have been received on a given port, it is assumed no multicast group members are on that port.
- step 860 if an IGMP membership query has been received then the switch resumes the non-querier state and processing continues with step 810 . However, if no IGMP membership queries have been received processing continues as step 870 .
- step 870 if the membership query transmit timer has expired, then it is time to send IGMP membership queries again and processing continues to step 840 . Otherwise, while the timer is active, processing loops back to step 860 until either an IGMP membership query is detected or the timer expires.
- Switching device 310 includes a common backplane 902 to which multiple switching interface cards may be connected. While in the illustrated embodiment the common backplane 902 is an ATM cell switching backplane, the present invention is not limited to any particular type of backplane. In any event, the switching interface cards do not themselves have to be ATM interface cards. Any type of network interface card may used as long as circuitry is provided for converting data from the format supported by the interface cards to the format supported by the common backplane 902 . Further, any number and combination of interface cards may be present, including token ring, ATM, FDDI and serial WAN interface cards. In the illustrated embodiment, two token ring interface cards 910 and 912 and one ATM interface card 914 are connected to the common backplane 902 in switching device 310 .
- backplane 902 is an ATM backplane
- all data moving over the backplane 902 is in the form of ATM cells.
- All packet data received by non-ATM interface cards, such as token ring interface cards 910 and 912 must be segmented into cells when entering the backplane 902 and re-assembled into packets when leaving the backplane 902 for packet transmission.
- token ring interface cards 910 and 912 include circuitry for performing segmentation and reassembly. Specifically, cards 910 and 912 respectively include packet buffers 926 and 944 connected to their respective ports. Both incoming and outgoing packets are temporarily stored these packet buffers.
- a Segmentation And Reassembly circuit encapsulates the data from the packet into ATM cells, which are then stored in a cell buffer.
- SAR Segmentation And Reassembly circuit
- Packet-based cards such as token ring interface cards 910 and 912 must extract the appropriate information from the cells, which are stored in the cell buffer, and encapsulate the data in a packet constructed in the packet buffer.
- Cards 910 and 912 respectively include SARs 924 and 948 which are respectively connected between packet buffers 926 and 944 and cell buffers 982 and 984 .
- Cell buffers 982 and 184 are respectively coupled to backplane 902 through backplane interfaces 986 and 950 .
- processing is performed on cards 910 and 912 by processors 916 and 936 respectively.
- Processors 916 and 936 are respectively coupled to memory 918 and 938 .
- ATM card 914 includes control units 972 and 974 coupled between its ports and a cell buffer 960 .
- a VTT 980 is coupled between control unit 972 and control unit 974 .
- the cell buffer 960 is coupled to the ATM backplane 902 through an interface 962 .
- Switching device 310 includes a master control process (MCP) 320 for controlling the flow of information within switching device 310 .
- MCP master control process
- the data transfers that occur between interface cards within switching device 310 included three general types of traffic.
- Data that is sent between packet switching interfaces e.g. data sent from token ring interface card 910 to token ring interface card 912
- LAN-to-LAN traffic Data that is sent between a packet switching interface and a cell switching interface (e.g. data sent from token ring interface card 910 and ATM interface card 914 ) is referred to as LAN-to/from-ATM traffic.
- Data that is sent between two cell switching interfaces is referred to as ATM-to-ATM traffic.
- MCP 320 includes a controller 906 and a memory 908 .
- Memory 908 stores a plurality of tables, including a master destination tag (“Dtag”) table that shall be described hereafter.
- Controller 906 generally represents control circuitry used to construct and maintain the tables within memory 908 , and to control the flow of data within device 310 based on those tables. Controller 906 may be implemented with hard wired circuitry, or by causing a processor to execute instructions. The present invention is not limited to a particular implementation of controller 906 .
- MCP 320 is illustrated separate from cards 910 , 912 and 914 for the purposes of explanation. However, MCP 320 may actually reside on one of the interface cards, or be distributed among the various interface cards.
- MCP 320 uses Dtags to control the distribution of data within and between each of the cards in device 310 , and between ports on each of the cards.
- Data flow management primarily involves the routing of cells over the backplane 902 and between ports, and the control of segmentation and re-assembly of packets to and from cells. Controls are provided for the stripping and adding of appropriate encapsulation headers during both segmentation and re-assembly to provide standardized formatting of packet data over cell based networks.
- Dtags are twelve bit values. By convention, the four high order bits for Dtags used for point-to-point forwarding are zero. The second four bits in a point-to-point Dtag specify the destination card and the low order four bits specify the destination port on the specified destination card.
- the Dtags for point-to-point forwarding are pre-allocated upon the initialization of switch device 310 . This convention is arbitrary. In some embodiments it may simplify recognition of the direct single port Dtags.
- multicast operations For operations in which data is sent to multiple ports (multicast operations), at least one of the first four bits is non-zero.
- These multicast Dtags and their associated table entries are allocated after initialization as needed to represent the virtual architecture of the switching device 310 .
- special Dtags are also allocated for transmitting messages to MCP 320 .
- a Dtag is used as an index to tables that provide the necessary information to allow the various components within the switch device 310 to deal with the forwarding and management of packet/cell data flows.
- MCP 320 maintains a master Dtag table within the memory 908 .
- each entry within the master Dtag table has the form illustrated by entry 1000 in FIG. 10 .
- each Dtag entry includes a destination mask 1010 , a priority value 1014 , a destination VPI/VCI value 1016 , a source strip/insert control field 1018 , and a destination strip/insert control field 1020 .
- Each port on each card within device 310 is represented by one bit within destination mask 1010 .
- the bit that corresponds to a port is set if the port is a destination port for data associated with the Dtag entry.
- all ports on a given interface card correspond to contiguous bits within the destination mask 1010 . Consequently, it may be quickly determined whether data associated with a particular Dtag entry should be sent to a particular card by performing an OR operation on the bits within destination mask 1010 that correspond to the ports on the card.
- Priority value 1014 indicates the priority level to be used when transmitting data to the destination ports designated in the Dtag entry.
- the destination VPI/VCI value 1016 is used for ATM cells that are sourced on an ATM card or sent from an ATM card. Since the destination for a packet received by a LAN card may be an ATM port on an ATM card, there must be a place to carry the destination VPI/VCI value.
- the destination VPI/VCI value 1016 stores the information necessary for this case.
- the source strip/insert control field 1018 includes control data used to construct the appropriate cell headers during the segmentation process.
- the destination strip/insert control information 1020 includes control data used to construct the appropriate packet headers during the reassembly process.
- Controller 906 creates a unique Dtag entry in the master Dtag table contained in memory 908 for each destination or combination of destinations. Each entry in Dtag table has a unique index. The indexes to the entries in the master Dtag table are referred to as Dtags. These same Dtags are also used to index other tables that shall be described hereafter. As shall be explained hereafter, Dtags and the tables indexed thereby are the primary mechanisms for routing data within device 310 .
- token ring card 910 includes four ports 928 , 930 , 932 and 934
- token ring card 912 includes four ports 952 , 954 , 956 and 958
- ATM card 914 includes four ports 964 , 966 , 968 and 970 .
- Data received by any of the interface cards within device 310 may be destined for any one of the ports on any one of the interface cards. Consequently, the master Dtag table preferably contains one entry for each of the ports on each of the interface cards. The destination mask 1010 in the Dtag entry that corresponds to a given port would have the bit that corresponds to the port set.
- data received at one port may be destined for more than one other port.
- packets may arrive at port 928 that are to be transmitted out through ports 930 , 952 and 954 .
- a Dtag entry is constructed for each desired unique set of destination ports.
- Dtag entries are not constructed for every possible unique set of destination ports, since the number of possible combinations may be extremely high. Rather, Dtag entries are constructed for every unique set of destination ports for which there is a reason to send data to the ports as a set (e.g. the set of ports that belong to a virtual token ring).
- a Dtag entry would be constructed in which the bits of the destination mask 1010 that correspond to ports 930 , 952 and 954 would be set.
- the data When data is received by an interface card within device 310 , the data will contain some indication as to where the data is to be sent.
- the type of destination information will vary based on the type of message that contains the data and type of network from which the data was received. For example, a packet received at port 928 of token ring interface card 910 may designate a destination with a MAC address. In contrast, cells received at port 964 may designate a destination with a VCI value.
- the present invention uses the destination designations to determine the appropriate Dtag for a particular block of data, and routes all data within device 310 based on the Dtag.
- controller 906 constructs and maintains tables within memory 908 in addition to the master Dtag table.
- the tables used to determine the Dtag appropriate for incoming data include a VCI-to-Dtag table that establishes a correspondence between VCI values and Dtags, a LTR-to-Dtag table that establishes a correspondence between virtual token rings and Dtags, and a GA-to-Dtag table that establishes a correspondence between group addresses and Dtags.
- each entry in the VCI-to-Dtag table may include a reassembly ID value and a quality of service value.
- the LTR-to-Dtag table may include a ring number. The present invention is not limited to any particular set of tables or fields.
- controller 906 controls all routing within device 310 based on the tables described above.
- the interface card transmits the destination designation for the data over backplane 902 to controller 906 .
- Controller 906 uses the destination designation as in index to a table to determine the appropriate Dtag for received data. For example, if the destination designation indicated a particular VCI value, then the VCI value would be used as an index to the VCI-to-Dtag table to determine the appropriate Dtag.
- the Dtag is used as an index to the master Dtag table to determine the appropriate Dtag entry.
- the data contained in the Dtag entry is used to determine the cards and ports to which the data must be sent over backplane 902 .
- Cells containing data that indicates the cards and ports to which the data must be sent is communicated over backplane 902 to the interface card which received the data.
- the interface card then begins transferring the data to the appropriate interface cards over backplane 902 .
- the preferred embodiment distributes the information contained in the tables stored in memory 908 to the various interface cards.
- controller 906 transmits information over backplane 902 to the various interface cards to cause the cards to build their own internal tables.
- the tables contained in each card include tables for determining the Dtags for all data that the card may receive from external sources, and tables indexed by the Dtags for determining the cards and ports to which the data must be sent.
- the tables used to determine the Dtags for data received from outside sources may include locally stored versions of the VCI-to-Dtag table, LTR-to-Dtag table and/or GA-to-Dtag table described above.
- Tables indexed by the Dtags for determining the cards and ports to which the data must be sent may include a locally stored version of all or a portion of the master Dtag table.
- information from the master Dtag table is used to create two locally stored tables. This embodiment is illustrated in FIG. 9 .
- cards 910 , 912 and 914 respectively include Local Port Mask tables (LPMs) 920 , 940 and 976 and Card Mask Tables (CMTs) 922 , 942 , and 978 .
- LPMs 920 , 940 and 976 are tables, indexed by Dtags, which indicate which of the local ports on the card are destination ports for a given Dtag. For example, assume that the Dtag “DTAG 1 ” is the index for an entry in the master Dtag table whose destination mask 1010 designates ports 928 , 952 and 954 as destination ports. LPM 920 would have a corresponding entry, indexed by DTAG 1 , that designates that port 928 is a destination port.
- CMTs 922 , 942 and 978 are tables, indexed by Dtags, which indicate which of the other interface cards within device 310 should be sent data that is associated with a given Dtag.
- CMT 922 would have an entry, indexed by DTAG 1 , that designates interface card 912 as a destination card.
- Interface card 912 is a destination card for data associated with DTAG 1 because ports 952 and 954 , which are destination ports for DTAG 1 , reside on interface card 912 .
- LPM 940 in interface card 912 would contain an entry, indexed by DTAG 1 , which designates ports 952 and 954 as destination ports.
- CMT 942 in interface card 912 would contain an entry, indexed by DTAG 1 , which designates interface card 910 as card to which data associated with DTAG 1 must be sent.
- the entry in LPM 976 indexed by DTAG 1 would not designate any local ports as destination ports.
- the entry in CMT 978 indexed by DTAG 1 would designate both interface cards 910 and 912 as cards to which data associated with DTAG 1 must be sent.
- a LPM entry for a given Dtag may be easily constructed from the Dtag entry in the master Dtag table for the Dtag. Specifically, for each interface card, the LPM entry for a Dtag includes those bits within the destination mask 1010 field that correspond to the ports on the interface card.
- the destination mask 1010 of an exemplary Dtag entry is illustrated.
- the bits in destination mask 1010 correspond to ports 928 , 930 , 932 , 934 , 952 , 954 , 956 , 958 , 964 , 966 , 968 and 970 respectively.
- the bits indicated by 1102 correspond to the ports on card 910 . Consequently, for card 910 , the LPM entry for the Dtag in question includes the bits indicated by 1102 .
- a CMT entry for a given Dtag may also be easily constructed from the entry in the master Dtag table that corresponds to the Dtag.
- each CMT entry includes one bit for each interface card within device 310 other than the interface card on which the particular CMT is stored. The bit that corresponds to a given interface card is set if any one of the bits in the destination mask 1010 that correspond to the ports on the given interface is set.
- the bits indicated by 1104 correspond to ports on card 912
- the bits indicated by 1106 correspond to ports on card 914
- the CMT entry in card 910 for the Dtag in question includes one bit for each card other than card 910 that is present in device 310 .
- the bit that corresponds to a card is set in the CMT entry if any bits that correspond to the ports on the card are set in the destination mask.
- at least one of the bits 1104 that correspond to ports on card 912 is set, so the bit corresponding to card 912 in the CMT entry is set. None of the bits 1106 that correspond to ports on card 914 are set, so the bit corresponding to card 914 in the CMT entry is not set.
- the tables described above are stored locally on the various interface cards so that intra-card and inter-card routing control functions may be performed locally within the cards rather than through the intervention of the MCP 320 .
- the destination address of the data IEEE MAC address for token ring interface cards, VPI/VCI for ATM cards
- the correspondence between the various types of destination addresses and Dtags are stored in tables maintained locally within each interface card. Consequently, the Dtag for a particular block of received data may be determined by the receiving interface card without any additional communication with MCP 320 .
- the interface card determines where the data must be sent. Specifically, circuitry on the interface card, such as processor 916 , uses the Dtag as an index to the locally stored LPM to determine whether the data is to be sent out on a local port, and as an index to the locally stored CMT to determine whether the data is to be sent over backplane 902 to one or more other interface cards.
- the interface card sends the data to the specified local ports. If the CMT entry corresponding to the Dtag indicates that the data is sent to one or more other cards in device 310 , then the data is placed on backplane 902 . In the preferred embodiment, the card mask from the CMT entry is placed on the backplane 902 prior to placing the data on the backplane. Each card in device 310 reads the card mask to determine whether it should read the subsequent data.
- the data was received by a LAN card, then the data must be packaged into cells prior to placing the data on backplane 902 .
- This process typically requires stripping some information from the packets and adding additional information to encapsulate the data into ATM cells.
- This operation is performed by the SAR unit within the LAN card based on control information stored in one or more locally maintained tables. The entries for such tables are constructed based on the source strip/insert control field 1018 in the master Dtag table.
- control information must still be placed in the cells to designate the Dtag associated with the cells prior to placing the cells onto the backplane 902 .
- the operation of sending out on one or more ports of a LAN card a packet that arrived on a port of the same LAN card is performed without converting the packet to ATM cells. Consequently, packets that are only between ports on the same LAN card do not have to be segmented, re-assembled, or transferred over backplane 902 . This significantly reduces the traffic over backplane 902 while increasing the efficiency of local port-to-port packet transfers.
- Cells containing data that is to be transferred from the receiving interface card to one or more other interface cards is placed on the backplane 902 by the interface card that received the data from an external source.
- the header for the cells contains data indicating the Dtag associated with the cells.
- Each interface card inspects the card mask placed on the backplane to determine whether the interface card is a destination interface card for the cell that will follow the card mask.
- Each card indicated as a destination card by the card mask reads the cell off of backplane 902 and stores the cell in a cell buffer.
- the Dtag associated with a cell is determined by the cell header information. Once the Dtag has been determined, the Dtag is used as an index to the local LPM table to determine on which local ports the data is to be sent. Once the local ports have been determined, the data is sent to external devices through the specified local ports.
- the data to be sent out on local ports may be sent as cells, so no conversion is necessary.
- the data from the cells must be re-assembled into packets.
- the re-assembly process typically includes stripping some information from the cells, and adding information to create a packet.
- the information to strip and/or add for any given re-assembly operation is determined with reference to one or more locally stored tables. Such tables include the information from the destination strip/insert control 1020 field of the master Dtag table.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims (11)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/832,042 US6370142B1 (en) | 1995-07-12 | 1997-04-02 | Method and apparatus for performing per-port IP multicast pruning |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/501,483 US5732080A (en) | 1995-07-12 | 1995-07-12 | Method and apparatus for controlling data flow within a switching device |
US08/832,042 US6370142B1 (en) | 1995-07-12 | 1997-04-02 | Method and apparatus for performing per-port IP multicast pruning |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/501,483 Continuation-In-Part US5732080A (en) | 1995-07-12 | 1995-07-12 | Method and apparatus for controlling data flow within a switching device |
Publications (1)
Publication Number | Publication Date |
---|---|
US6370142B1 true US6370142B1 (en) | 2002-04-09 |
Family
ID=46276166
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/832,042 Expired - Lifetime US6370142B1 (en) | 1995-07-12 | 1997-04-02 | Method and apparatus for performing per-port IP multicast pruning |
Country Status (1)
Country | Link |
---|---|
US (1) | US6370142B1 (en) |
Cited By (100)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020001310A1 (en) * | 2000-06-29 | 2002-01-03 | Khanh Mai | Virtual multicasting |
US20020048275A1 (en) * | 1997-12-16 | 2002-04-25 | Antonio Atwater | Method and apparatus for receiving full-motion digital video multi-casts, interactive data and interactive voice via a DSL circuit |
US20020085557A1 (en) * | 2000-12-29 | 2002-07-04 | Jensen Claus P. | Determining the presence of IP multicast routers |
US20020120769A1 (en) * | 2000-12-21 | 2002-08-29 | Ammitzboell Benny Loenstrup | Multicast traffic control protocol pruning in a layer 2 switch |
US20020122390A1 (en) * | 2001-03-02 | 2002-09-05 | Jeremy Garff | Method and apparatus for classifying querying nodes |
US20020141401A1 (en) * | 1999-07-01 | 2002-10-03 | Mark Albert | Distributing packets among multiple tiers of network appliances |
US20020196802A1 (en) * | 1998-02-26 | 2002-12-26 | Joshua Sakov | Data forwarding method and apparatus |
US6515969B1 (en) * | 1999-03-01 | 2003-02-04 | Cisco Technology, Inc. | Virtual local area network membership registration protocol for multiple spanning tree network environments |
US20030041171A1 (en) * | 1998-06-17 | 2003-02-27 | Naofumi Kobayashi | Communication control unit and communication control method applied for multicast-supporting LAN |
US6529882B1 (en) * | 1999-11-03 | 2003-03-04 | Electronics And Telecommunications Research Institute | Method for managing group membership in internet multicast applications |
US20030043804A1 (en) * | 2001-08-30 | 2003-03-06 | Surender Kumar | Use of IP-multicast technology for 2-party calls in mobile communication networks |
US6557111B1 (en) * | 1999-11-29 | 2003-04-29 | Xerox Corporation | Multicast-enhanced update propagation in a weakly-consistant, replicated data storage system |
US20030123453A1 (en) * | 2001-12-10 | 2003-07-03 | Alcatel | Method and apparatus of directing multicast traffic in an Ethernet MAN |
US20030140084A1 (en) * | 1999-04-15 | 2003-07-24 | D'angelo Leo A. | System controlling use of a communication channel |
US6614787B1 (en) * | 1999-03-30 | 2003-09-02 | 3Com Corporation | System and method for efficiently handling multicast packets by aggregating VLAN context |
US6633765B1 (en) * | 2000-08-28 | 2003-10-14 | Qualcomm, Incorporated | Method and apparatus for performing coverage control for multicast services in a wireless network |
US6636499B1 (en) * | 1999-12-02 | 2003-10-21 | Cisco Technology, Inc. | Apparatus and method for cluster network device discovery |
US6661789B1 (en) * | 1999-09-10 | 2003-12-09 | Alcatel | Dynamic burstification based on fully/partially shared multicast entities |
US20040015583A1 (en) * | 2000-11-30 | 2004-01-22 | Barrett Mark A | Network management apparatus |
US6697349B2 (en) * | 2001-08-30 | 2004-02-24 | Motorola, Inc. | System and methods for distributed connection and mobility processing in a multicast IP network incorporating multi-cell location areas |
US6711163B1 (en) * | 1999-03-05 | 2004-03-23 | Alcatel | Data communication system with distributed multicasting |
US20040071131A1 (en) * | 2002-10-15 | 2004-04-15 | Cisco Technology, Inc. | Port policy management for calls in a centralized call control packet network |
US20040071137A1 (en) * | 2002-08-06 | 2004-04-15 | Qiang He | Method for forwarding multicast message in network communication |
US20040076162A1 (en) * | 2002-10-16 | 2004-04-22 | Jong-Kuk Lee | Method for providing IP multicast service using virtual LAN |
US6757294B1 (en) * | 2000-03-13 | 2004-06-29 | International Business Machines Corporation | System and method for amicable small group multicast in a packet-switched network |
US6785275B1 (en) | 2000-03-13 | 2004-08-31 | International Business Machines Corporation | Method and system for creating small group multicast over an existing unicast packet network |
US20040174826A1 (en) * | 2002-12-26 | 2004-09-09 | George Popovich | Method and apparatus for minimizing dense mode multicast flooding between a local area network switch and a router |
US20040190514A1 (en) * | 2003-03-27 | 2004-09-30 | Motohiro Uchiyama | Communication method and receiving terminal in multicast communication network |
US6804236B1 (en) * | 1998-10-07 | 2004-10-12 | Cisco Technology, Inc. | Efficient network multicast switching apparatus and methods |
US6829248B1 (en) * | 1999-03-08 | 2004-12-07 | Conexant Systems, Inc. | Integrated switching segmentation and reassembly (SAR) device |
US6836462B1 (en) | 2000-08-30 | 2004-12-28 | Cisco Technology, Inc. | Distributed, rule based packet redirection |
US6847638B1 (en) * | 2000-10-16 | 2005-01-25 | Cisco Technology, Inc. | Multicast system for forwarding desired multicast packets in a computer network |
US20050025160A1 (en) * | 2000-11-22 | 2005-02-03 | Cisco Technology, Inc. | System and method for grouping multiple VLANs into a single 802.11 IP multicast domain |
US6856621B1 (en) * | 1999-10-11 | 2005-02-15 | Stonesoft Oy | Method of transmission of data in cluster environment |
US6873618B1 (en) * | 1999-03-16 | 2005-03-29 | Nortel Networks Limited | Multipoint network routing protocol |
US20050216601A1 (en) * | 2002-08-16 | 2005-09-29 | Yost William H | Download optimization in the presence of multicast data |
US20050220104A1 (en) * | 2003-03-31 | 2005-10-06 | Fujitsu Limited | Communication system and communication apparatus |
US20050243751A1 (en) * | 2004-04-28 | 2005-11-03 | Samsung Electronics Co., Ltd. | Time slot reservation method for multicast data in wireless network |
US6963572B1 (en) | 1999-10-22 | 2005-11-08 | Alcatel Canada Inc. | Method and apparatus for segmentation and reassembly of data packets in a communication switch |
US6990103B1 (en) * | 1999-07-13 | 2006-01-24 | Alcatel Canada Inc. | Method and apparatus for providing distributed communication routing |
US20060039375A1 (en) * | 2002-07-31 | 2006-02-23 | Thomas Bahls | Method, communication system and communication device for trainsmitting broadcasting information via a communication network |
US7013157B1 (en) * | 2002-06-03 | 2006-03-14 | Cisco Technology, Inc. | Method for multicast delivery with designated acknowledgment |
US7016351B1 (en) * | 2000-02-29 | 2006-03-21 | Cisco Technology, Inc. | Small group multicast in a computer network |
US7068661B1 (en) * | 1999-07-13 | 2006-06-27 | Alcatel Canada Inc. | Method and apparatus for providing control information in a system using distributed communication routing |
US20060164984A1 (en) * | 2004-11-14 | 2006-07-27 | Cisco Technology, Inc. | Limiting unauthorized sources in a multicast distribution tree |
US20060221968A1 (en) * | 2005-03-31 | 2006-10-05 | Ashu Razdan | System and method for distributing VoIP data packets in group communications among wireless telecommunication devices |
US20060239254A1 (en) * | 1998-12-08 | 2006-10-26 | Nomadix, Inc. | Systems and Methods for Providing Dynamic Network Authorization, Authentication and Accounting |
US20070030817A1 (en) * | 2005-08-08 | 2007-02-08 | Senthil Arunachalam | Constraining multicast traffic between a layer 2 network device and a router |
WO2007019785A1 (en) * | 2005-08-19 | 2007-02-22 | Zte Corporation | A multicast supported virtual local area network switching system and a method thereof |
US7197556B1 (en) * | 1999-10-22 | 2007-03-27 | Nomadix, Inc. | Location-based identification for use in a communications network |
US20070104170A1 (en) * | 2000-12-28 | 2007-05-10 | Cisco Technology, Inc. | Support mobile device in asymmetric link environment |
US7222188B1 (en) * | 1995-12-08 | 2007-05-22 | Nortel Networks Limited | Method and apparatus for forwarding traffic between locally attached networks using level 3 addressing information |
US7310335B1 (en) * | 2000-09-06 | 2007-12-18 | Nokia Networks | Multicast routing in ad-hoc networks |
US7346053B1 (en) * | 2002-05-07 | 2008-03-18 | Cisco Technology, Inc. | Methods and apparatus for supporting IP multicast for a mobile router |
US7356578B1 (en) * | 2003-05-28 | 2008-04-08 | Landesk Software Limited | System for constructing a network spanning tree using communication metrics discovered by multicast alias domains |
US20080123644A1 (en) * | 2006-11-28 | 2008-05-29 | Alcatel | Method and apparatus for improved IGMP group membership messaging |
US20080253373A1 (en) * | 2005-09-13 | 2008-10-16 | Ist International Inc. | System and Method for Supporting Flexible Overlays and Mobility in Ip Communication and Computer Networks |
US7447202B1 (en) * | 2003-03-03 | 2008-11-04 | Cisco Technology, Inc. | Method and system for optimized reliable non-member group communication through write-only membership |
CN100444574C (en) * | 2002-12-31 | 2008-12-17 | 阿尔卡特公司 | Multicast optimization in a VLAN tagged network |
US7468977B1 (en) * | 1995-07-12 | 2008-12-23 | Nortel Networks Limited | LAN/ATM switch having local packet switching and an ATM core fabric |
US20090016244A1 (en) * | 2002-09-20 | 2009-01-15 | Vishal Sharma | System and method for network layer protocol routing in a peer model integrated optical network |
US7580391B1 (en) | 2000-12-20 | 2009-08-25 | Cisco Technology, Inc. | Dynamic network allocation for mobile router |
US7633926B1 (en) * | 2003-02-06 | 2009-12-15 | Cisco Technology, Inc. | Extending multicast applications available on data networks to cell-based wireless networks |
US20090310609A1 (en) * | 2007-06-26 | 2009-12-17 | Alvaro Fernandez Gutierrez | Method and device for managing multicast groups |
US20100014519A1 (en) * | 2007-10-15 | 2010-01-21 | Media Patents, S.L. | Methods for managing multicast traffic between sources sending data and hosts requesting data and network equipment used to implement the methods |
US20100046516A1 (en) * | 2007-06-26 | 2010-02-25 | Media Patents, S.L. | Methods and Devices for Managing Multicast Traffic |
US7707300B1 (en) | 2001-04-13 | 2010-04-27 | Cisco Technology, Inc. | Methods and apparatus for transmitting information in a network |
US7716363B1 (en) * | 2004-02-10 | 2010-05-11 | Cisco Technology, Inc. | Method and apparatus of providing zero configuration single source multicasting reporting |
US20100183008A1 (en) * | 2007-10-15 | 2010-07-22 | Fernandez Gutierrez Alvaro | Method for managing multicast traffic in a data network and network equipment using said method |
US20100254383A1 (en) * | 2007-10-30 | 2010-10-07 | Media Patents, S.L. | Method for managing multicast traffic between equipment in a multicast data network |
US20110010441A1 (en) * | 2008-03-05 | 2011-01-13 | Media Patents, S.L. | Equipment in a data network and methods for monitoring, configuring and/or managing the equipment |
US7877483B1 (en) * | 2002-10-28 | 2011-01-25 | Cisco Technology, Inc. | Virtual local area network pruning protocol |
US20110058551A1 (en) * | 2008-02-01 | 2011-03-10 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
US20110058548A1 (en) * | 2008-02-01 | 2011-03-10 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
US7924837B1 (en) * | 2000-07-31 | 2011-04-12 | Avaya Communication Israel Ltd. | IP multicast in VLAN environment |
US20110149960A1 (en) * | 2009-12-17 | 2011-06-23 | Media Patents, S.L. | Method and apparatus for filtering multicast packets |
US20110222486A1 (en) * | 2010-03-10 | 2011-09-15 | Cisco Technology, Inc. | Downlink OFDMA for Service Sets with Mixed Client Types |
US8156246B2 (en) | 1998-12-08 | 2012-04-10 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US20120113986A1 (en) * | 2010-11-09 | 2012-05-10 | Cisco Technology, Inc. | System and method for managing acknowledgement messages in a very large computer network |
US20120120950A1 (en) * | 2010-11-15 | 2012-05-17 | Mentze Duane Edward | Convergence of multicast traffic in response to a topology change |
US8189584B2 (en) | 2009-07-27 | 2012-05-29 | Media Patents, S. L. | Multicast traffic management in a network interface |
US8208418B1 (en) * | 2009-01-16 | 2012-06-26 | Extreme Networks, Inc. | Methods, systems, and computer readable media for conserving multicast port list resources in an internet protocol (IP) packet forwarding device |
US8295300B1 (en) * | 2007-10-31 | 2012-10-23 | World Wide Packets, Inc. | Preventing forwarding of multicast packets |
US20130182706A1 (en) * | 2012-01-18 | 2013-07-18 | International Business Machines Corporation | Requesting multicast membership information in a distributed switch in response to a miss event |
US8503630B2 (en) | 2012-01-09 | 2013-08-06 | EC Data Systems, Inc. | Scalable and flexible internet fax architecture |
US8588381B2 (en) | 2012-02-27 | 2013-11-19 | EC Data Systems, Inc. | Scalable and flexible Internet fax architecture for processing outbound fax messages |
US8613053B2 (en) | 1998-12-08 | 2013-12-17 | Nomadix, Inc. | System and method for authorizing a portable communication device |
US20140126561A1 (en) * | 2012-11-07 | 2014-05-08 | Cisco Technology, Inc. | Work group bridge nomadic roaming |
US8830997B1 (en) * | 2005-06-22 | 2014-09-09 | Marvell International Ltd. | Preventing denial-of-service attacks employing broadcast packets |
US20140258319A1 (en) * | 2003-08-20 | 2014-09-11 | Apple Inc. | Method and apparatus for accelerating the expiration of resource records in a local cache |
US8856419B2 (en) | 2010-07-19 | 2014-10-07 | International Business Machines Corporation | Register access in distributed virtual bridge environment |
US8891535B2 (en) | 2012-01-18 | 2014-11-18 | International Business Machines Corporation | Managing a global forwarding table in a distributed switch |
US8964742B1 (en) * | 2010-07-28 | 2015-02-24 | Marvell Israel (M.I.S.L) Ltd. | Linked list profiling and updating |
US9008091B1 (en) | 2010-11-19 | 2015-04-14 | Extreme Networks, Inc. | Methods, systems, and computer readable media for improved multicast scaling through policy based redirection |
US20150188767A1 (en) * | 2013-12-27 | 2015-07-02 | Futurewei Technologies, Inc. | Traffic Behavior Driven Dynamic Zoning for Distributed Traffic Engineering in SDN |
US20160094353A1 (en) * | 2014-09-30 | 2016-03-31 | Vmware, Inc. | Technique to submit multicast membership state in absence of querier |
US9397917B2 (en) | 2014-01-10 | 2016-07-19 | Huawei Technologies Co., Ltd. | System and method for zoning in software defined networks |
US9471612B2 (en) | 2012-06-29 | 2016-10-18 | International Business Machines Corporation | Data processing method, data query method in a database, and corresponding device |
US10277778B2 (en) | 2014-06-24 | 2019-04-30 | Ec Data Systems Inc. | Audit logging for a secure, scalable and flexible internet fax architecture |
US10581744B2 (en) | 2016-12-02 | 2020-03-03 | Cisco Technology, Inc. | Group-based pruning in a software defined networking environment |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5331637A (en) | 1993-07-30 | 1994-07-19 | Bell Communications Research, Inc. | Multicast routing using core based trees |
US5355375A (en) | 1993-03-18 | 1994-10-11 | Network Systems Corporation | Hub controller for providing deterministic access to CSMA local area network |
US5361256A (en) * | 1992-11-27 | 1994-11-01 | International Business Machines Corporation | Inter-domain multicast routing |
WO1995001023A1 (en) | 1993-06-17 | 1995-01-05 | Ascom Timeplex Trading Ag | Hub for segmented virtual local area network |
US5396493A (en) | 1992-08-31 | 1995-03-07 | Kabushiki Kaisha Toshiba | Local area network bridge apparatus with dedicated packet filtering mechanism |
US5400326A (en) * | 1993-12-22 | 1995-03-21 | International Business Machines Corporation | Network bridge |
US5428615A (en) | 1991-01-25 | 1995-06-27 | Digital Equipment Corp. | Many to few group address translation through a network bridge |
US5448565A (en) | 1992-11-12 | 1995-09-05 | International Business Machines Corp. | Multiport LAN bridge |
US5481540A (en) | 1990-08-24 | 1996-01-02 | At&T Corp. | FDDI bridge frame learning and filtering apparatus and method |
US5517494A (en) * | 1994-09-30 | 1996-05-14 | Apple Computer, Inc. | Method and system of multicast routing for groups with a single transmitter |
US5608726A (en) | 1995-04-25 | 1997-03-04 | Cabletron Systems, Inc. | Network bridge with multicast forwarding table |
US5664091A (en) | 1995-08-31 | 1997-09-02 | Ncr Corporation | Method and system for a voiding unnecessary retransmissions using a selective rejection data link protocol |
US5737334A (en) * | 1995-07-12 | 1998-04-07 | Bay Networks, Inc. | Pipeline architecture for an ATM switch backplane bus |
US5781549A (en) * | 1996-02-23 | 1998-07-14 | Allied Telesyn International Corp. | Method and apparatus for switching data packets in a data network |
US5818838A (en) * | 1995-10-12 | 1998-10-06 | 3Com Corporation | Method and apparatus for transparent intermediate system based filtering on a LAN of multicast packets |
US5852606A (en) * | 1995-07-12 | 1998-12-22 | Bay Networks, Inc. | Method and apparatus for transmitting cells across an ATM switch bus |
US5968126A (en) * | 1997-04-02 | 1999-10-19 | Switchsoft Systems, Inc. | User-based binding of network stations to broadcast domains |
US6023563A (en) * | 1996-08-20 | 2000-02-08 | Shani; Ron | Networking switch having the network presence of a bridge |
US6075776A (en) * | 1996-06-07 | 2000-06-13 | Nippon Telegraph And Telephone Corporation | VLAN control system and method |
US6111876A (en) * | 1996-03-12 | 2000-08-29 | Nortel Networks Limited | VLAN frame format |
-
1997
- 1997-04-02 US US08/832,042 patent/US6370142B1/en not_active Expired - Lifetime
Patent Citations (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5481540A (en) | 1990-08-24 | 1996-01-02 | At&T Corp. | FDDI bridge frame learning and filtering apparatus and method |
US5428615A (en) | 1991-01-25 | 1995-06-27 | Digital Equipment Corp. | Many to few group address translation through a network bridge |
US5396493A (en) | 1992-08-31 | 1995-03-07 | Kabushiki Kaisha Toshiba | Local area network bridge apparatus with dedicated packet filtering mechanism |
US5448565A (en) | 1992-11-12 | 1995-09-05 | International Business Machines Corp. | Multiport LAN bridge |
US5361256A (en) * | 1992-11-27 | 1994-11-01 | International Business Machines Corporation | Inter-domain multicast routing |
US5355375A (en) | 1993-03-18 | 1994-10-11 | Network Systems Corporation | Hub controller for providing deterministic access to CSMA local area network |
WO1995001023A1 (en) | 1993-06-17 | 1995-01-05 | Ascom Timeplex Trading Ag | Hub for segmented virtual local area network |
US5331637A (en) | 1993-07-30 | 1994-07-19 | Bell Communications Research, Inc. | Multicast routing using core based trees |
US5400326A (en) * | 1993-12-22 | 1995-03-21 | International Business Machines Corporation | Network bridge |
US5517494A (en) * | 1994-09-30 | 1996-05-14 | Apple Computer, Inc. | Method and system of multicast routing for groups with a single transmitter |
US5608726A (en) | 1995-04-25 | 1997-03-04 | Cabletron Systems, Inc. | Network bridge with multicast forwarding table |
US5898686A (en) * | 1995-04-25 | 1999-04-27 | Cabletron Systems, Inc. | Network bridge with multicast forwarding table |
US5737334A (en) * | 1995-07-12 | 1998-04-07 | Bay Networks, Inc. | Pipeline architecture for an ATM switch backplane bus |
US5852606A (en) * | 1995-07-12 | 1998-12-22 | Bay Networks, Inc. | Method and apparatus for transmitting cells across an ATM switch bus |
US5664091A (en) | 1995-08-31 | 1997-09-02 | Ncr Corporation | Method and system for a voiding unnecessary retransmissions using a selective rejection data link protocol |
US5818838A (en) * | 1995-10-12 | 1998-10-06 | 3Com Corporation | Method and apparatus for transparent intermediate system based filtering on a LAN of multicast packets |
US5781549A (en) * | 1996-02-23 | 1998-07-14 | Allied Telesyn International Corp. | Method and apparatus for switching data packets in a data network |
US6111876A (en) * | 1996-03-12 | 2000-08-29 | Nortel Networks Limited | VLAN frame format |
US6075776A (en) * | 1996-06-07 | 2000-06-13 | Nippon Telegraph And Telephone Corporation | VLAN control system and method |
US6023563A (en) * | 1996-08-20 | 2000-02-08 | Shani; Ron | Networking switch having the network presence of a bridge |
US5968126A (en) * | 1997-04-02 | 1999-10-19 | Switchsoft Systems, Inc. | User-based binding of network stations to broadcast domains |
Non-Patent Citations (15)
Title |
---|
"Deploying IP Multicast Applications on Switched-Based Networks", A White Paper, Agile Networks, Inc., 1996, pp. 1-12. |
"Foundry Products", downloaded from Website http://www.foundrynet.com/. |
"Higher Level Protocols Used With IP Multicast", An IP Multicast Initiative White Paper, Stardust Technologies, Inc., 1995-1997. |
"Host Extensions For IP Multicasting", S. Deering, Network Working Group, pp. 1-16. |
"How IP Multicast Works" An IP Multicast Initiative White Paper, Stardust Technologies, Inc., 1995-1997, pp. 1-12. |
"Internet Group Management Protocol, Version 2", W. Fenner, Internet-Draft, Internet Engineering Task Force Inter-Domain Multicast Routing Working Group, pp. 1-22. |
"Introduction to IP Multicast Routing", An IP Multicast Initiative White Paper, Stardust Technologies, Inc., 1995-1997, pp. 1-15. |
"IP Multicast Backgrounder" An IP Multicast Initiative White Paper, Stardust Technologies, Inc., 1995-1997, pp. 1-9. |
"Layer-3 Virtual LANs: The Only VLAN Implementataion To Deliver On the Full Promise Of Switched Internetworking", A White Paper, Agile Networks, 1996, pp. 1-13. |
Cisco Systems, Inc., "IP Multicast Streamlines Delivery Of Multicast Applications", Packet(TM) Magazine Arhcive, First Quarter 1995, downloaded from Web Site http://www.cisco.com/warp/public/674/4.html, 6 pages. |
Cisco Systems, Inc., "IP Multicast Streamlines Delivery Of Multicast Applications", Packet™ Magazine Arhcive, First Quarter 1995, downloaded from Web Site http://www.cisco.com/warp/public/674/4.html, 6 pages. |
D. R. Cheriton, S. E. Deering, "Host Groups: A Multicast Extension For Datagram Internetworks", Ninth Data Communications Symposium, Sep. 1985, pp. 172-179. |
Katz, D., "A Proposed Standard for the Transmission of IP Datagrams over FDDI Networks", RFC 1188, Oct. 1990. |
Pustateri, T., "IP Multicast over Token-Ring Local Area Networks", RFC-1469, Jun. 1993. |
Stephen E. Deering, "Multicast Routing In Internetworks And Extended LANs", ACM Symposium On Communications Architectures And Protocols, ACM Sigcomm, Aug. 1998, pp. 55-64. |
Cited By (208)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7468977B1 (en) * | 1995-07-12 | 2008-12-23 | Nortel Networks Limited | LAN/ATM switch having local packet switching and an ATM core fabric |
US7222188B1 (en) * | 1995-12-08 | 2007-05-22 | Nortel Networks Limited | Method and apparatus for forwarding traffic between locally attached networks using level 3 addressing information |
US20020048275A1 (en) * | 1997-12-16 | 2002-04-25 | Antonio Atwater | Method and apparatus for receiving full-motion digital video multi-casts, interactive data and interactive voice via a DSL circuit |
US7840981B2 (en) * | 1997-12-16 | 2010-11-23 | Nokia Siemens Networks Gmbh & Co. Kg | Method and apparatus for receiving full-motion digital video multi-casts, interactive data and interactive voice via a DSL circuit |
US20020196802A1 (en) * | 1998-02-26 | 2002-12-26 | Joshua Sakov | Data forwarding method and apparatus |
US7411916B2 (en) * | 1998-02-26 | 2008-08-12 | Nortel Networks Limited | Data forwarding method and apparatus |
US8516139B2 (en) | 1998-06-17 | 2013-08-20 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting LAN |
US20090135821A1 (en) * | 1998-06-17 | 2009-05-28 | Fujitsu Limited | Communication control unit and communication control method applied for multi-cast-supporting lan |
US20030041171A1 (en) * | 1998-06-17 | 2003-02-27 | Naofumi Kobayashi | Communication control unit and communication control method applied for multicast-supporting LAN |
US7487251B2 (en) * | 1998-06-17 | 2009-02-03 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting LAN |
US9088505B2 (en) | 1998-06-17 | 2015-07-21 | Fujitsu Limited | Communication control unit and communication control method applied for multi-cast-supporting LAN |
US8429283B2 (en) | 1998-06-17 | 2013-04-23 | Fujitsu Limited | Communication control unit and communication control method applied for multi-cast supporting LAN |
US8370512B2 (en) * | 1998-06-17 | 2013-02-05 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting LAN |
US8521894B2 (en) | 1998-06-17 | 2013-08-27 | Fujitsu Limited | Communication control unit and communication control method applied for multi-cast-supporting LAN |
US20100254384A1 (en) * | 1998-06-17 | 2010-10-07 | Fujitsu Limited | Communication control unit and communication control method applied for multi-cast supporting lan |
US20080165773A1 (en) * | 1998-06-17 | 2008-07-10 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting lan |
US20080165772A1 (en) * | 1998-06-17 | 2008-07-10 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting lan |
US20080159284A1 (en) * | 1998-06-17 | 2008-07-03 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting lan |
US8364834B2 (en) | 1998-06-17 | 2013-01-29 | Fujitsu Limited | Communication control unit and communication control method applied for multicast-supporting LAN |
US6804236B1 (en) * | 1998-10-07 | 2004-10-12 | Cisco Technology, Inc. | Efficient network multicast switching apparatus and methods |
US8156246B2 (en) | 1998-12-08 | 2012-04-10 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8364806B2 (en) | 1998-12-08 | 2013-01-29 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US9160672B2 (en) | 1998-12-08 | 2015-10-13 | Nomadix, Inc. | Systems and methods for controlling user perceived connection speed |
US10341243B2 (en) | 1998-12-08 | 2019-07-02 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US7689716B2 (en) | 1998-12-08 | 2010-03-30 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization, authentication and accounting |
US8266269B2 (en) | 1998-12-08 | 2012-09-11 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US9548935B2 (en) | 1998-12-08 | 2017-01-17 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8788690B2 (en) | 1998-12-08 | 2014-07-22 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8725899B2 (en) | 1998-12-08 | 2014-05-13 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8244886B2 (en) | 1998-12-08 | 2012-08-14 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8606917B2 (en) | 1998-12-08 | 2013-12-10 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8266266B2 (en) | 1998-12-08 | 2012-09-11 | Nomadix, Inc. | Systems and methods for providing dynamic network authorization, authentication and accounting |
US8613053B2 (en) | 1998-12-08 | 2013-12-17 | Nomadix, Inc. | System and method for authorizing a portable communication device |
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 |
US8370477B2 (en) | 1998-12-08 | 2013-02-05 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US8725888B2 (en) | 1998-12-08 | 2014-05-13 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US10110436B2 (en) | 1998-12-08 | 2018-10-23 | Nomadix, Inc. | Systems and methods for providing content and services on a network system |
US20060239254A1 (en) * | 1998-12-08 | 2006-10-26 | Nomadix, Inc. | Systems and Methods for Providing Dynamic Network Authorization, Authentication and Accounting |
US7286491B1 (en) | 1999-03-01 | 2007-10-23 | Cisco Technology, Inc. | Virtual local area network membership registration protocol for multiple spanning tree network environments |
US6515969B1 (en) * | 1999-03-01 | 2003-02-04 | Cisco Technology, Inc. | Virtual local area network membership registration protocol for multiple spanning tree network environments |
US6711163B1 (en) * | 1999-03-05 | 2004-03-23 | Alcatel | Data communication system with distributed multicasting |
US6829248B1 (en) * | 1999-03-08 | 2004-12-07 | Conexant Systems, Inc. | Integrated switching segmentation and reassembly (SAR) device |
US6873618B1 (en) * | 1999-03-16 | 2005-03-29 | Nortel Networks Limited | Multipoint network routing protocol |
US6614787B1 (en) * | 1999-03-30 | 2003-09-02 | 3Com Corporation | System and method for efficiently handling multicast packets by aggregating VLAN context |
US9059955B2 (en) | 1999-04-15 | 2015-06-16 | Advanced Messaging Technologies, Inc. | System controlling use of a communication channel |
US6717938B1 (en) * | 1999-04-15 | 2004-04-06 | J2 Global Communications, Inc. | System controlling use of a communication channel |
US20030140084A1 (en) * | 1999-04-15 | 2003-07-24 | D'angelo Leo A. | System controlling use of a communication channel |
US8238380B2 (en) | 1999-04-15 | 2012-08-07 | J2 Global Communications, Inc. | System controlling use of a communication channel |
US20060098692A1 (en) * | 1999-04-15 | 2006-05-11 | D Angelo Leo A | System controlling use of a communication channel |
US6999478B2 (en) | 1999-04-15 | 2006-02-14 | J2 Global Communications, Inc. | System controlling use of a communication channel |
US20020141401A1 (en) * | 1999-07-01 | 2002-10-03 | Mark Albert | Distributing packets among multiple tiers of network appliances |
US6891839B2 (en) | 1999-07-01 | 2005-05-10 | Cisco Technology, Inc. | Distributing packets among multiple tiers of network appliances |
US20060268877A1 (en) * | 1999-07-13 | 2006-11-30 | Gollamudi Ramana V | Method and apparatus for providing distributed communication routing |
US6990103B1 (en) * | 1999-07-13 | 2006-01-24 | Alcatel Canada Inc. | Method and apparatus for providing distributed communication routing |
US7920563B2 (en) | 1999-07-13 | 2011-04-05 | Alcatel Lucent | Method and apparatus for providing distributed communication routing |
US7068661B1 (en) * | 1999-07-13 | 2006-06-27 | Alcatel Canada Inc. | Method and apparatus for providing control information in a system using distributed communication routing |
US6661789B1 (en) * | 1999-09-10 | 2003-12-09 | Alcatel | Dynamic burstification based on fully/partially shared multicast entities |
US6856621B1 (en) * | 1999-10-11 | 2005-02-15 | Stonesoft Oy | Method of transmission of data in cluster environment |
US6963572B1 (en) | 1999-10-22 | 2005-11-08 | Alcatel Canada Inc. | Method and apparatus for segmentation and reassembly of data packets in a communication switch |
US20060050738A1 (en) * | 1999-10-22 | 2006-03-09 | David Carr | Method and apparatus for segmentation and reassembly of data packets in a communication switch |
US7197556B1 (en) * | 1999-10-22 | 2007-03-27 | Nomadix, Inc. | Location-based identification for use in a communications network |
US7463650B2 (en) | 1999-10-22 | 2008-12-09 | Alcatel Lucent Canada Inc. | Method and apparatus for segmentation and reassembly of data packets in a communication switch |
US6529882B1 (en) * | 1999-11-03 | 2003-03-04 | Electronics And Telecommunications Research Institute | Method for managing group membership in internet multicast applications |
US6557111B1 (en) * | 1999-11-29 | 2003-04-29 | Xerox Corporation | Multicast-enhanced update propagation in a weakly-consistant, replicated data storage system |
US6636499B1 (en) * | 1999-12-02 | 2003-10-21 | Cisco Technology, Inc. | Apparatus and method for cluster network device discovery |
US7978718B2 (en) | 2000-02-29 | 2011-07-12 | Cisco Technology, Inc. | Small group multicast in a computer network |
US20060203819A1 (en) * | 2000-02-29 | 2006-09-14 | Dino Farinacci | Small group multicast in a computer network |
US7016351B1 (en) * | 2000-02-29 | 2006-03-21 | Cisco Technology, Inc. | Small group multicast in a computer network |
US7720019B1 (en) | 2000-02-29 | 2010-05-18 | Cisco Technology, Inc. | Small group multicast in a computer network |
US6757294B1 (en) * | 2000-03-13 | 2004-06-29 | International Business Machines Corporation | System and method for amicable small group multicast in a packet-switched network |
US6785275B1 (en) | 2000-03-13 | 2004-08-31 | International Business Machines Corporation | Method and system for creating small group multicast over an existing unicast packet network |
US20020001310A1 (en) * | 2000-06-29 | 2002-01-03 | Khanh Mai | Virtual multicasting |
US7924837B1 (en) * | 2000-07-31 | 2011-04-12 | Avaya Communication Israel Ltd. | IP multicast in VLAN environment |
US6633765B1 (en) * | 2000-08-28 | 2003-10-14 | Qualcomm, Incorporated | Method and apparatus for performing coverage control for multicast services in a wireless network |
US6836462B1 (en) | 2000-08-30 | 2004-12-28 | Cisco Technology, Inc. | Distributed, rule based packet redirection |
US7443796B1 (en) | 2000-08-30 | 2008-10-28 | Cisco Technology, Inc. | Distributed, rule based packet redirection |
US7310335B1 (en) * | 2000-09-06 | 2007-12-18 | Nokia Networks | Multicast routing in ad-hoc networks |
US6847638B1 (en) * | 2000-10-16 | 2005-01-25 | Cisco Technology, Inc. | Multicast system for forwarding desired multicast packets in a computer network |
US7385977B2 (en) | 2000-10-16 | 2008-06-10 | Cisco Technology, Inc. | Multicast system for forwarding desired multicast packets in a computer network |
US20050157741A1 (en) * | 2000-10-16 | 2005-07-21 | Ishan Wu | Multicast system for forwarding desired multicast packets in a computer network |
US7301946B2 (en) * | 2000-11-22 | 2007-11-27 | Cisco Technology, Inc. | System and method for grouping multiple VLANs into a single 802.11 IP multicast domain |
US20070286108A1 (en) * | 2000-11-22 | 2007-12-13 | Robert Meier | System and method for grouping multiple vlans into a single 802.11 ip multicast domain |
US20050025160A1 (en) * | 2000-11-22 | 2005-02-03 | Cisco Technology, Inc. | System and method for grouping multiple VLANs into a single 802.11 IP multicast domain |
US7944925B2 (en) * | 2000-11-22 | 2011-05-17 | Cisco Technology, Inc. | System and method for grouping multiple VLANs into a single 802.11 IP multicast domain |
US20040015583A1 (en) * | 2000-11-30 | 2004-01-22 | Barrett Mark A | Network management apparatus |
US7580391B1 (en) | 2000-12-20 | 2009-08-25 | Cisco Technology, Inc. | Dynamic network allocation for mobile router |
US7746874B1 (en) | 2000-12-20 | 2010-06-29 | Cisco Technology, Inc. | Dynamic network allocation for mobile router |
US20020120769A1 (en) * | 2000-12-21 | 2002-08-29 | Ammitzboell Benny Loenstrup | Multicast traffic control protocol pruning in a layer 2 switch |
US20070104170A1 (en) * | 2000-12-28 | 2007-05-10 | Cisco Technology, Inc. | Support mobile device in asymmetric link environment |
US7295551B1 (en) | 2000-12-28 | 2007-11-13 | Cisco Technology, Inc. | Support mobile device in asymmetric link environment |
US7630352B2 (en) | 2000-12-28 | 2009-12-08 | Cisco Technology, Inc. | Support mobile device in asymmetric link environment |
US6967932B2 (en) * | 2000-12-29 | 2005-11-22 | Intel Corporation | Determining the presence of IP multicast routers |
US20020085557A1 (en) * | 2000-12-29 | 2002-07-04 | Jensen Claus P. | Determining the presence of IP multicast routers |
US20060062159A1 (en) * | 2000-12-29 | 2006-03-23 | Intel Corporation, A Delaware Corporation | Determining the presence of IP multicast routers |
US7660268B2 (en) * | 2000-12-29 | 2010-02-09 | Intel Corporation | Determining the presence of IP multicast routers |
US20020122390A1 (en) * | 2001-03-02 | 2002-09-05 | Jeremy Garff | Method and apparatus for classifying querying nodes |
US7707300B1 (en) | 2001-04-13 | 2010-04-27 | Cisco Technology, Inc. | Methods and apparatus for transmitting information in a network |
US7103011B2 (en) * | 2001-08-30 | 2006-09-05 | Motorola, Inc. | Use of IP-multicast technology for 2-party calls in mobile communication networks |
US20030043804A1 (en) * | 2001-08-30 | 2003-03-06 | Surender Kumar | Use of IP-multicast technology for 2-party calls in mobile communication networks |
US6697349B2 (en) * | 2001-08-30 | 2004-02-24 | Motorola, Inc. | System and methods for distributed connection and mobility processing in a multicast IP network incorporating multi-cell location areas |
US20030123453A1 (en) * | 2001-12-10 | 2003-07-03 | Alcatel | Method and apparatus of directing multicast traffic in an Ethernet MAN |
US8054835B2 (en) * | 2001-12-10 | 2011-11-08 | Alcatel Lucent | Method and apparatus of directing multicast traffic in an Ethernet MAN |
US7346053B1 (en) * | 2002-05-07 | 2008-03-18 | Cisco Technology, Inc. | Methods and apparatus for supporting IP multicast for a mobile router |
US7013157B1 (en) * | 2002-06-03 | 2006-03-14 | Cisco Technology, Inc. | Method for multicast delivery with designated acknowledgment |
US20060039375A1 (en) * | 2002-07-31 | 2006-02-23 | Thomas Bahls | Method, communication system and communication device for trainsmitting broadcasting information via a communication network |
US7590116B2 (en) * | 2002-08-06 | 2009-09-15 | Huawei Technologies Co., Ltd. | Method for forwarding multicast message in network communication |
US20040071137A1 (en) * | 2002-08-06 | 2004-04-15 | Qiang He | Method for forwarding multicast message in network communication |
US8931085B2 (en) * | 2002-08-16 | 2015-01-06 | Thomson Licensing | Download optimization in the presence of multicast data |
US20050216601A1 (en) * | 2002-08-16 | 2005-09-29 | Yost William H | Download optimization in the presence of multicast data |
US20090016244A1 (en) * | 2002-09-20 | 2009-01-15 | Vishal Sharma | System and method for network layer protocol routing in a peer model integrated optical network |
US20040071131A1 (en) * | 2002-10-15 | 2004-04-15 | Cisco Technology, Inc. | Port policy management for calls in a centralized call control packet network |
US7372849B2 (en) * | 2002-10-15 | 2008-05-13 | Cisco Technology, Inc. | Port policy management for calls in a centralized call control packet network |
US20040076162A1 (en) * | 2002-10-16 | 2004-04-22 | Jong-Kuk Lee | Method for providing IP multicast service using virtual LAN |
US7391767B2 (en) * | 2002-10-16 | 2008-06-24 | Electronics And Telecommunications Research Institute | Method for providing IP multicast service using virtual LAN |
US7877483B1 (en) * | 2002-10-28 | 2011-01-25 | Cisco Technology, Inc. | Virtual local area network pruning protocol |
US20040174826A1 (en) * | 2002-12-26 | 2004-09-09 | George Popovich | Method and apparatus for minimizing dense mode multicast flooding between a local area network switch and a router |
CN100444574C (en) * | 2002-12-31 | 2008-12-17 | 阿尔卡特公司 | Multicast optimization in a VLAN tagged network |
US7633926B1 (en) * | 2003-02-06 | 2009-12-15 | Cisco Technology, Inc. | Extending multicast applications available on data networks to cell-based wireless networks |
US7447202B1 (en) * | 2003-03-03 | 2008-11-04 | Cisco Technology, Inc. | Method and system for optimized reliable non-member group communication through write-only membership |
US7639683B2 (en) * | 2003-03-27 | 2009-12-29 | Fujitsu Limited | Multicast communication method using layer 2 and 3 switches |
US20040190514A1 (en) * | 2003-03-27 | 2004-09-30 | Motohiro Uchiyama | Communication method and receiving terminal in multicast communication network |
US20050220104A1 (en) * | 2003-03-31 | 2005-10-06 | Fujitsu Limited | Communication system and communication apparatus |
US8135010B2 (en) * | 2003-03-31 | 2012-03-13 | Fujitsu Limited | System and apparatus thereof for Ethernet PON communication |
US7356578B1 (en) * | 2003-05-28 | 2008-04-08 | Landesk Software Limited | System for constructing a network spanning tree using communication metrics discovered by multicast alias domains |
US9619517B2 (en) * | 2003-08-20 | 2017-04-11 | Apple Inc. | Method and apparatus for accelerating the expiration of resource records in a local cache |
US20140258319A1 (en) * | 2003-08-20 | 2014-09-11 | Apple Inc. | Method and apparatus for accelerating the expiration of resource records in a local cache |
AU2004310308B2 (en) * | 2003-11-05 | 2010-01-21 | Cisco Technology, Inc. | System and method for grouping multiple VLANS into a single 802.11 IP multicast domain |
US7716363B1 (en) * | 2004-02-10 | 2010-05-11 | Cisco Technology, Inc. | Method and apparatus of providing zero configuration single source multicasting reporting |
US20050243751A1 (en) * | 2004-04-28 | 2005-11-03 | Samsung Electronics Co., Ltd. | Time slot reservation method for multicast data in wireless network |
US7940765B2 (en) * | 2004-11-14 | 2011-05-10 | Cisco Technology, Inc. | Limiting unauthorized sources in a multicast distribution tree |
US20060164984A1 (en) * | 2004-11-14 | 2006-07-27 | Cisco Technology, Inc. | Limiting unauthorized sources in a multicast distribution tree |
US20060221968A1 (en) * | 2005-03-31 | 2006-10-05 | Ashu Razdan | System and method for distributing VoIP data packets in group communications among wireless telecommunication devices |
US7724743B2 (en) | 2005-03-31 | 2010-05-25 | Qualcomm Incorporated | System and method for distributing VoIP data packets in group communications amoung wireless telecommunication devices |
US20100195578A1 (en) * | 2005-03-31 | 2010-08-05 | Qualcomm Incorporated | System and method for distributing voip data packets in group communications among wireless telecommunication devices |
US8830997B1 (en) * | 2005-06-22 | 2014-09-09 | Marvell International Ltd. | Preventing denial-of-service attacks employing broadcast packets |
US20070030817A1 (en) * | 2005-08-08 | 2007-02-08 | Senthil Arunachalam | Constraining multicast traffic between a layer 2 network device and a router |
US8040884B2 (en) * | 2005-08-08 | 2011-10-18 | Cisco Technology, Inc. | Constraining multicast traffic between a layer 2 network device and a router |
WO2007019785A1 (en) * | 2005-08-19 | 2007-02-22 | Zte Corporation | A multicast supported virtual local area network switching system and a method thereof |
US8189582B2 (en) | 2005-08-19 | 2012-05-29 | Zte Corporation | Multicast supported virtual local area network switching system and method thereof |
US20080219260A1 (en) * | 2005-08-19 | 2008-09-11 | Zte Corporation | Multicast Supported Virtual Local Area Network Switching System and Method Thereof |
US20080253373A1 (en) * | 2005-09-13 | 2008-10-16 | Ist International Inc. | System and Method for Supporting Flexible Overlays and Mobility in Ip Communication and Computer Networks |
US7672325B2 (en) * | 2006-11-28 | 2010-03-02 | Alcatel Lucent | Method and apparatus for improved IGMP group membership messaging |
US20080123644A1 (en) * | 2006-11-28 | 2008-05-29 | Alcatel | Method and apparatus for improved IGMP group membership messaging |
US8086716B2 (en) | 2007-06-26 | 2011-12-27 | Media Patents, S.L. | Methods and devices for managing multicast groups |
US20090310609A1 (en) * | 2007-06-26 | 2009-12-17 | Alvaro Fernandez Gutierrez | Method and device for managing multicast groups |
US8094602B2 (en) | 2007-06-26 | 2012-01-10 | Media Patents, S.L. | Methods and apparatus for managing multicast groups |
US20100046516A1 (en) * | 2007-06-26 | 2010-02-25 | Media Patents, S.L. | Methods and Devices for Managing Multicast Traffic |
US20100054247A1 (en) * | 2007-06-26 | 2010-03-04 | Media Patents, S.L. | Method and device for managing multicast groups |
US20100054248A1 (en) * | 2007-06-26 | 2010-03-04 | Media Patents, S.L. | Method and device for managing multicast groups |
US7921198B2 (en) | 2007-06-26 | 2011-04-05 | Media Patents, S.L. | Method and device for managing multicast groups |
US7908354B2 (en) | 2007-06-26 | 2011-03-15 | Media Patents, S.L. | Method and device for managing multicast groups |
US20100054249A1 (en) * | 2007-06-26 | 2010-03-04 | Media Patents, S.L. | Method and device for managing multicast groups |
US8422499B2 (en) | 2007-10-15 | 2013-04-16 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic |
US20100014519A1 (en) * | 2007-10-15 | 2010-01-21 | Media Patents, S.L. | Methods for managing multicast traffic between sources sending data and hosts requesting data and network equipment used to implement the methods |
US20100183008A1 (en) * | 2007-10-15 | 2010-07-22 | Fernandez Gutierrez Alvaro | Method for managing multicast traffic in a data network and network equipment using said method |
US20100172353A1 (en) * | 2007-10-15 | 2010-07-08 | Media Patents, S.L. | Methods for managing multicast traffic between sources sending data and hosts requesting data and network equipment used to implement the methods |
US20100172352A1 (en) * | 2007-10-15 | 2010-07-08 | Media Patents, S.L. | Methods for managing multicast traffic between sources sending data and hosts requesting data and network equipment used to implement the methods |
US8184630B2 (en) | 2007-10-15 | 2012-05-22 | Media Patents, S.L. | Method for managing multicast traffic in a data network and network equipment using said method |
US20100172351A1 (en) * | 2007-10-15 | 2010-07-08 | Media Patents, S.L. | Methods for managing multicast traffic between sources sending data and hosts requesting data and network equipment used to implement the methods |
US8064449B2 (en) | 2007-10-15 | 2011-11-22 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic |
US8582572B2 (en) | 2007-10-15 | 2013-11-12 | Media Paents, S.L. | Methods and apparatus for managing multicast traffic |
US8571028B2 (en) | 2007-10-15 | 2013-10-29 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic |
US20100254383A1 (en) * | 2007-10-30 | 2010-10-07 | Media Patents, S.L. | Method for managing multicast traffic between equipment in a multicast data network |
US8644310B2 (en) | 2007-10-30 | 2014-02-04 | Media Patents, S.L. | Method for managing multicast traffic between equipment in a multicast data network |
US8295300B1 (en) * | 2007-10-31 | 2012-10-23 | World Wide Packets, Inc. | Preventing forwarding of multicast packets |
US9031068B2 (en) | 2008-02-01 | 2015-05-12 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
US8565140B2 (en) | 2008-02-01 | 2013-10-22 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
US20110058548A1 (en) * | 2008-02-01 | 2011-03-10 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
US20110058551A1 (en) * | 2008-02-01 | 2011-03-10 | Media Patents, S.L. | Methods and apparatus for managing multicast traffic through a switch |
US20110010441A1 (en) * | 2008-03-05 | 2011-01-13 | Media Patents, S.L. | Equipment in a data network and methods for monitoring, configuring and/or managing the equipment |
US8340095B2 (en) | 2008-03-05 | 2012-12-25 | Media Patents, S.L. | Equipment in a data network and methods for monitoring, configuring and/or managing the equipment |
US8208418B1 (en) * | 2009-01-16 | 2012-06-26 | Extreme Networks, Inc. | Methods, systems, and computer readable media for conserving multicast port list resources in an internet protocol (IP) packet forwarding device |
US8189584B2 (en) | 2009-07-27 | 2012-05-29 | Media Patents, S. L. | Multicast traffic management in a network interface |
US20110149960A1 (en) * | 2009-12-17 | 2011-06-23 | Media Patents, S.L. | Method and apparatus for filtering multicast packets |
US8559323B2 (en) | 2010-03-10 | 2013-10-15 | Cisco Technology, Inc. | Downlink OFDMA for service sets with mixed client types |
US10433313B2 (en) | 2010-03-10 | 2019-10-01 | Cisco Technology, Inc. | Downlink OFDMA for service sets with mixed client types |
US20110222486A1 (en) * | 2010-03-10 | 2011-09-15 | Cisco Technology, Inc. | Downlink OFDMA for Service Sets with Mixed Client Types |
US9363048B2 (en) | 2010-03-10 | 2016-06-07 | Cisco Technology, Inc. | Downlink OFDMA for service sets with mixed client types |
US8856419B2 (en) | 2010-07-19 | 2014-10-07 | International Business Machines Corporation | Register access in distributed virtual bridge environment |
US8964742B1 (en) * | 2010-07-28 | 2015-02-24 | Marvell Israel (M.I.S.L) Ltd. | Linked list profiling and updating |
US8520676B2 (en) * | 2010-11-09 | 2013-08-27 | Cisco Technology, Inc. | System and method for managing acknowledgement messages in a very large computer network |
US20120113986A1 (en) * | 2010-11-09 | 2012-05-10 | Cisco Technology, Inc. | System and method for managing acknowledgement messages in a very large computer network |
US8654769B2 (en) * | 2010-11-15 | 2014-02-18 | Hewlett-Packard Development Company, L.P. | Convergence of multicast traffic in response to a topology change |
US20120120950A1 (en) * | 2010-11-15 | 2012-05-17 | Mentze Duane Edward | Convergence of multicast traffic in response to a topology change |
US9008091B1 (en) | 2010-11-19 | 2015-04-14 | Extreme Networks, Inc. | Methods, systems, and computer readable media for improved multicast scaling through policy based redirection |
US8503630B2 (en) | 2012-01-09 | 2013-08-06 | EC Data Systems, Inc. | Scalable and flexible internet fax architecture |
US9042532B2 (en) | 2012-01-09 | 2015-05-26 | Advanced Messaging Technologies, Inc. | Scalable and flexible internet fax architecture |
US8861400B2 (en) * | 2012-01-18 | 2014-10-14 | International Business Machines Corporation | Requesting multicast membership information in a distributed switch in response to a miss event |
US20130182706A1 (en) * | 2012-01-18 | 2013-07-18 | International Business Machines Corporation | Requesting multicast membership information in a distributed switch in response to a miss event |
DE102013200031B4 (en) | 2012-01-18 | 2018-10-18 | International Business Machines Corporation | Manage a global routing table in a distributed switch |
US8891535B2 (en) | 2012-01-18 | 2014-11-18 | International Business Machines Corporation | Managing a global forwarding table in a distributed switch |
US9225851B2 (en) | 2012-02-27 | 2015-12-29 | Advanced Messaging Technologies Inc. | Scalable and flexible internet fax architecture for processing outbound fax messages |
US8588381B2 (en) | 2012-02-27 | 2013-11-19 | EC Data Systems, Inc. | Scalable and flexible Internet fax architecture for processing outbound fax messages |
US9471612B2 (en) | 2012-06-29 | 2016-10-18 | International Business Machines Corporation | Data processing method, data query method in a database, and corresponding device |
DE102013210914B4 (en) | 2012-06-29 | 2018-06-21 | International Business Machines Corporation | Data processing method, data retrieval method in database and corresponding unit |
US20140126561A1 (en) * | 2012-11-07 | 2014-05-08 | Cisco Technology, Inc. | Work group bridge nomadic roaming |
US9491001B2 (en) * | 2012-11-07 | 2016-11-08 | Cisco Technology, Inc. | Work group bridge nomadic roaming |
CN105900393A (en) * | 2013-12-27 | 2016-08-24 | 华为技术有限公司 | Traffic behavior driven dynamic zoning for distributed traffic engineering in SDN |
US9432257B2 (en) * | 2013-12-27 | 2016-08-30 | Huawei Technologies Co., Ltd. | Traffic behavior driven dynamic zoning for distributed traffic engineering in SDN |
US20150188767A1 (en) * | 2013-12-27 | 2015-07-02 | Futurewei Technologies, Inc. | Traffic Behavior Driven Dynamic Zoning for Distributed Traffic Engineering in SDN |
US9397917B2 (en) | 2014-01-10 | 2016-07-19 | Huawei Technologies Co., Ltd. | System and method for zoning in software defined networks |
US10277778B2 (en) | 2014-06-24 | 2019-04-30 | Ec Data Systems Inc. | Audit logging for a secure, scalable and flexible internet fax architecture |
US10477069B2 (en) | 2014-06-24 | 2019-11-12 | Ec Data Systems Inc. | Audit logging for a secure, scalable and flexible internet fax architecture |
US10477070B2 (en) | 2014-06-24 | 2019-11-12 | Ec Data Systems Inc. | Audit logging for a secure, scalable and flexible Internet fax architecture |
US10674040B2 (en) | 2014-06-24 | 2020-06-02 | EC Data Systems, Inc. | Audit logging for a secure, scalable and flexible internet fax architecture |
US9479348B2 (en) * | 2014-09-30 | 2016-10-25 | Vmware, Inc. | Technique to submit multicast membership state in absence of querier |
US20160094353A1 (en) * | 2014-09-30 | 2016-03-31 | Vmware, Inc. | Technique to submit multicast membership state in absence of querier |
US10581744B2 (en) | 2016-12-02 | 2020-03-03 | Cisco Technology, Inc. | Group-based pruning in a software defined networking environment |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6370142B1 (en) | Method and apparatus for performing per-port IP multicast pruning | |
US6785274B2 (en) | Efficient network multicast switching apparatus and methods | |
US6639901B1 (en) | Apparatus for and method for supporting 802.1Q VLAN tagging with independent VLAN learning in LAN emulation networks | |
US6553028B1 (en) | Method and apparatus for multicast switching using a centralized switching engine | |
EP0903028B1 (en) | Connection aggregation in switched communications networks | |
US7924837B1 (en) | IP multicast in VLAN environment | |
US6430621B1 (en) | System using different tag protocol identifiers to distinguish between multiple virtual local area networks | |
US6483832B1 (en) | IP multicast over routed ATM network using lane | |
AU697935B2 (en) | Method for establishing restricted broadcast groups in a switched network | |
US6839348B2 (en) | System and method for distributing multicasts in virtual local area networks | |
EP1597875B1 (en) | Method and device for protocol-independent realization of ip multicast | |
US6563830B1 (en) | Multicast registration of all multicast flows in an asynchronous transfer mode based emulated LAN | |
US6041057A (en) | Self-configuring ATM network | |
US6757286B1 (en) | Self-configuring communication network | |
US9407533B2 (en) | Multicast in a trill network | |
US8364834B2 (en) | Communication control unit and communication control method applied for multicast-supporting LAN | |
US7693158B1 (en) | Methods and systems for selectively processing virtual local area network (VLAN) traffic from different networks while allowing flexible VLAN identifier assignment | |
US6532233B1 (en) | Multicast communication method and apparatus | |
US20020124107A1 (en) | Vlan advertisement protocol (VAP) | |
US7697552B2 (en) | MAC address scalability in interconnected rings | |
CA2289070A1 (en) | Multicast switching | |
US6289017B1 (en) | Method of providing redundancy and load sharing among multiple LECs in an asynchronous mode network | |
US6643289B1 (en) | Method of MPOA status change notification | |
US7006444B1 (en) | Self-configuring communication network | |
US6493345B1 (en) | Single sender private multicast server for use with LAN emulation in asynchronous transfer mode networks |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: BAY NETWORKS, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PITCHER, DEREK;SESHADRI, KISHORE K.;SIMONE, DANIEL A.;REEL/FRAME:008507/0038;SIGNING DATES FROM 19970401 TO 19970402 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS NA INC., CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:BAY NETWORKS, INC.;REEL/FRAME:010461/0283 Effective date: 19990430 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS CORPORATION, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS NA INC.;REEL/FRAME:010547/0891 Effective date: 19991229 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS LIMITED, CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706 Effective date: 20000830 Owner name: NORTEL NETWORKS LIMITED,CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706 Effective date: 20000830 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK N.A., AS COLLATERAL AGENT, NEW Free format text: SECURITY AGREEMENT;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:017198/0151 Effective date: 20060214 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS LIMITED, CANADA Free format text: RELEASE OF PATENT SECURITY AGREEMENT;ASSIGNOR:JPMORGAN CHASE BANK N.A., AS COLLATERAL AGENT;REEL/FRAME:017914/0962 Effective date: 20060705 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
AS | Assignment |
Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT,NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023892/0500 Effective date: 20100129 Owner name: CITIBANK, N.A., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023892/0500 Effective date: 20100129 |
|
AS | Assignment |
Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023905/0001 Effective date: 20100129 Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT,NEW YO Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023905/0001 Effective date: 20100129 Owner name: CITICORP USA, INC., AS ADMINISTRATIVE AGENT, NEW Y Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC.;REEL/FRAME:023905/0001 Effective date: 20100129 |
|
AS | Assignment |
Owner name: AVAYA INC.,NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:023998/0878 Effective date: 20091218 Owner name: AVAYA INC., NEW JERSEY Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:023998/0878 Effective date: 20091218 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS LIMITED,ONTARIO Free format text: RELEASE OF SECURITY INTERESTS;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:024045/0401 Effective date: 20051024 |
|
AS | Assignment |
Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLATERAL AGENT, THE, PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535 Effective date: 20110211 Owner name: BANK OF NEW YORK MELLON TRUST, NA, AS NOTES COLLAT Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA INC., A DELAWARE CORPORATION;REEL/FRAME:025863/0535 Effective date: 20110211 |
|
AS | Assignment |
Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, PENNSYLVANIA Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639 Effective date: 20130307 Owner name: BANK OF NEW YORK MELLON TRUST COMPANY, N.A., THE, Free format text: SECURITY AGREEMENT;ASSIGNOR:AVAYA, INC.;REEL/FRAME:030083/0639 Effective date: 20130307 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 025863/0535;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST, NA;REEL/FRAME:044892/0001 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 023892/0500;ASSIGNOR:CITIBANK, N.A.;REEL/FRAME:044891/0564 Effective date: 20171128 Owner name: AVAYA INC., CALIFORNIA Free format text: BANKRUPTCY COURT ORDER RELEASING ALL LIENS INCLUDING THE SECURITY INTEREST RECORDED AT REEL/FRAME 030083/0639;ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A.;REEL/FRAME:045012/0666 Effective date: 20171128 |
|
AS | Assignment |
Owner name: AVAYA, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:045045/0564 Effective date: 20171215 Owner name: SIERRA HOLDINGS CORP., NEW JERSEY Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CITICORP USA, INC.;REEL/FRAME:045045/0564 Effective date: 20171215 |