US20150280929A1 - Scalable ip-services enabled multicast forwarding with efficient resource utilization - Google Patents
Scalable ip-services enabled multicast forwarding with efficient resource utilization Download PDFInfo
- Publication number
- US20150280929A1 US20150280929A1 US14/714,270 US201514714270A US2015280929A1 US 20150280929 A1 US20150280929 A1 US 20150280929A1 US 201514714270 A US201514714270 A US 201514714270A US 2015280929 A1 US2015280929 A1 US 2015280929A1
- Authority
- US
- United States
- Prior art keywords
- oif
- multicast
- blocks
- block
- session
- 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.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/02—Details
- H04L12/16—Arrangements for providing special services to substations
- H04L12/18—Arrangements for providing special services to substations for broadcast or conference, e.g. multicast
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/16—Multipoint routing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/58—Association of routers
- H04L45/586—Association of routers of virtual routers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/60—Router architectures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/60—Network streaming of media packets
- H04L65/61—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio
- H04L65/611—Network streaming of media packets for supporting one-way streaming services, e.g. Internet radio for multicast or broadcast
Definitions
- Various embodiments of the present invention are generally related to the field of telecommunications and more particularly, but not by way of limitation, to network switches and systems and methods for multicast internet protocol (IP) forwarding.
- IP internet protocol
- IP flow refers to a stream of packets that enter and exit the same set of interfaces.
- the packets of a particular IP flow have the same values in the IP packet header for the following six attributes of the IP packet header: (1) Source IP Address, (2) Source L4 Port, (3) Type of Service (TOS), (4) Destination IP Address, (5) Destination L4 Port, and (6) Protocol.
- the network switch modules including the processors residing in the modules, can be partitioned into virtual routers (VRs), that is, software running on the processors that emulates the functioning of an individual physical hardware router.
- VRs virtual routers
- a first subscriber may desire high definition television (HDTV) service over a network.
- a second subscriber may desire mobile telephone service over the network.
- the first subscriber may occasionally desire video-on-demand (VOD).
- VOD video-on-demand
- the second subscriber may need to switch between voice communication and high-speed digital data communication.
- a “unicast” communication typically refers to a communication from a single source device to a single destination device over a network.
- a “multicast” communication typically refers to a communication to a group of destination devices from one or more source devices.
- Multicast packet forwarding raises additional complexity because of the many destination devices. Many existing router devices will be unable to provide the desired scalability to accommodate such additional destination devices. This is particularly true when each individual data flow may require “per-flow” services for the multicast traffic. Allocating resources efficiently for a large number of multicast data flows is a challenging problem.
- multicast broadcasting of content presents additional complexity because individual users may join or leave a particular multicast group at will and often. Such “channel surfing” creates an additional burden for keeping track of the participants of a multicast group so that the content can be routed appropriately.
- a network switch module includes a memory and multiple processors partitioned among multiple virtual routers (VRs). Each VR maintains a data structure containing therein information regarding the active multicast IP sessions, including a first value (e.g., a pointer) for each of the active multicast IP sessions, at least one chain of one or more blocks of second values (e.g., pointers) and one or more transmit control blocks (TCBs). Each first value is indicative of a chain of one or more blocks of second values.
- a first value e.g., a pointer
- TDBs transmit control blocks
- Each second value is indicative of an outbound interface (OIF) of the network device participating in the active multicast IP session defined by the first value and identifies a number of times packets associated with the active multicast IP session are to be replicated.
- the TCBs have stored therein control information to process or route packets.
- Each second value is indicative of a TCB.
- Each TCB identifies an OIF of the network device through which packets are to be transmitted.
- FIG. 1 is a block diagram of one example of an operating environment for the present system and methods.
- FIG. 2 is a block diagram of one example of a Virtual Router (VR) in accordance with an embodiment of the present invention.
- VR Virtual Router
- FIG. 3 is a block diagram of one example of a Packet Forwarding Engine (PFE) and a main memory of a VR in accordance with embodiments of the present invention.
- PFE Packet Forwarding Engine
- FIG. 4 is a flow chart illustrating a multicast internet protocol (IP) packet forwarding method in accordance with an embodiment of the present invention.
- IP internet protocol
- FIG. 5 is a block diagram of an OIF module and multicast TCB module for a set of multicast sessions in accordance with an embodiment of the present invention.
- FIG. 6 is a flow chart illustrating a process that is invoked in accordance with an embodiment of the present invention if multicast packet forwarding is invoked in FIG. 4 .
- FIG. 7 is a flow chart illustrating packet retrieval and replication in accordance with an embodiment of the present invention.
- FIG. 8 is a flow chart illustrating processing by an egress module in accordance with an embodiment of the present invention.
- FIG. 9 is a flow chart illustrating more detail of acts included in the multicast forwarding in accordance with an embodiment of the present invention.
- IP internet protocol
- references to “one embodiment” or “an embodiment” mean that the feature being referred to is included in at least one embodiment of the invention.
- separate references to “one embodiment” in this description do not necessarily refer to the same embodiment; however, neither are such embodiments mutually exclusive, unless so stated and except as will be readily apparent to those of ordinary skill in the art.
- the present invention can include any variety of combinations and/or integrations of the embodiments described herein.
- the phrase “exemplary embodiment” means that the embodiment being referred to serves as an example or illustration.
- block diagrams illustrate exemplary embodiments of the invention.
- flow diagrams illustrate operations of the exemplary embodiments of the invention. The operations of the flow diagrams will be described with reference to the exemplary embodiments shown in the block diagrams. However, it should be understood that the operations of the flow diagrams could be performed by embodiments of the invention other than those discussed with reference to the block diagrams, and embodiments discussed with references to the block diagrams could perform operations different than those discussed with reference to the flow diagrams. Moreover, it should be understood that although the flow diagrams may depict serial operations, certain embodiments could perform certain of those operations in parallel.
- FIG. 1 is a block diagram of one example of an operating environment for the present system and methods.
- a system 100 typically includes personal computers (PCs) 102 that are respectively connected to modems 106 .
- the modems 106 are typically respectively connected to a digital subscriber line access module (DSLAM) 116 .
- DSLAM 116 multiplexes signals from the modems 106 onto the Internet Protocol (IP) network 118 .
- IP network 118 is typically connected to a router box 114 that includes virtual routers (VRs) 128 .
- the router box 114 is typically connected to the Internet 112 .
- the router box 114 is also typically connected to a dynamic host configuration protocol (DHCP) server 120 , a web portal 122 , a RADIUS server 124 , and a control server 126 .
- DHCP dynamic host configuration protocol
- the router 114 includes three VRs 128 , other examples call for any number of VRs 128 .
- one or more of the VRs 128 can establish subscriber connections, such as to users of the PCs 102 .
- the VRs 128 can use the DHCP server 120 for assigning IP network addresses to the PCs 102 .
- the VRs 128 can use the RADIUS server 124 to authenticate subscribers. After authenticating subscribers, the VRs 128 can configure subscriber connections according to service profiles, which refer to subscriber-specific services that individual subscribers receive during connections.
- the VRs 128 can receive service profiles information from the control server 126 or the RADIUS server 224 .
- FIG. 1 illustrates an example in which the users accessing the Internet 112 via PCs, this is merely an illustrative example.
- the individual users may access the Internet 112 or other computer or communications network wirelessly, such as by using a 3rd Generation (3G) or other mobile phone or other handheld or portable device, or by using a laptop or other portable computing device with Wireless Fidelity (WiFi) (e.g., using IEEE 802.11b wireless networking) capability or the like.
- 3G 3rd Generation
- WiFi Wireless Fidelity
- the individual users may access the Internet 112 or other communications or computer network using an Ethernet connection, a Very High bit rate Digital Subscriber Line (VHDSL) connection, a Fiber To The Premises (FTTP) connection, or a cable TV line or like connection, or the like.
- VHDSL Very High bit rate Digital Subscriber Line
- FTP Fiber To The Premises
- the present systems and methods are not limited to any particular devices or techniques for accessing the Internet 112 , such as through the router box 114 .
- the exemplary system 100 typically provides network services to thousands of subscribers. Each subscriber can receive a particular set of services upon establishing a connection with the system 100 .
- FIG. 2 is a block diagram of one example of a VR 128 .
- the VR 128 includes a packet forwarding engine (PFE) 206 , and one or more virtual interfaces (VIs) 208 from a source or to a destination.
- a VI over which multicast packets are forwarded is sometimes referred to as an Outbound Interface (OIF).
- OIF Outbound Interface
- Different services can be applied to multicast packet forwarding traffic as well as unicast packet forwarding traffic. Which services are applied to a particular packet are determined, in one example, by an inbound policy or an outbound policy associated with a particular VI 208 .
- the packet header (e.g., one or more of the above-described six packet header attributes defining an IP flow) is examined (e.g., such as by comparing such attribute(s) to one or more matching criteria in an access control list (ACL)) to determine whether any services should be applied to the packet and, if so, which services should be applied.
- ACL access control list
- FIG. 3 is a block diagram of one example of a Packet Forwarding Engine (PFE) 300 and a main memory 302 of a VR 128 .
- PFE 300 includes an ingress module 304 , an egress module 306 , a PFE memory 308 , a Direct Memory Access (DMA) engine 310 , a packet input interface 312 , a packet output interface 314 , and a main memory interface 316 .
- the ingress module 304 includes an ingress rate limit module 318 , an ingress statistics module 320 , a flow classification module 322 , and a multicast forwarding module 324 .
- the PFE memory 308 includes a Flow Control Block (FCB) 326 , a multicast block 328 , an Outbound InterFace (OIF) module 330 , a default Transmit Control Block (TCB) 332 , a multicast TCB module 334 , a metering block 336 , and a statistics block 338 .
- the egress module 306 includes a TCB processing module 340 , a header transform module 342 , an egress rate limit module 344 , and an egress statistics module 346 .
- FIG. 4 is a flow chart of one example of a multicast internet protocol (IP) packet forwarding method such as can be performed, for example, by using the PFE 300 and main memory 302 of FIG. 3 .
- IP internet protocol
- a packet is received at the packet input interface 312 on a particular virtual interface (VI) of a particular VR in the router box 114 .
- VIP virtual interface
- the ingress rate limit module 318 performs a rate limiting function to control a packet ingress data rate through the ingress module 304 .
- the ingress statistics module 320 computes packet ingress statistics, such as packet count, byte count, etc. Such ingress statistics may be important for managing subscriber service levels, among other things.
- the flow classification module 322 is used to classify the data flow, for example, as a unicast flow or a multicast flow.
- the flow classification module 322 typically uses a predefined portion of the packet header to classify the data flow, and to identify the particular FCB associated with the flow. For example, the “destination address” portion of the packet header is used to identify the packet as a multicast packet.
- the data flow classification uses the source IP address and the destination IP address portions of the packet header to classify the data flow.
- a second mode sometimes referred to as an “adaptive-optimized mode”
- additional portions of the packet header are used to further classify the data flow in accordance with the appropriate services.
- the flow classification at 406 uses the information extracted from the packet header to look up a corresponding FCB entry in FCB 326 . If the data flow is a multicast data flow then, in one example, the corresponding FCB entry will have a “multicast” flag set, and a “forwarding action” field of the FCB entry will indicate that hardware forwarding of packets is to be used for the multicast data flow.
- the classification indicates a multicast data flow, then, at 410 , multicast packet forwarding is invoked. Otherwise, at 412 , unicast packet forwarding is invoked.
- Each FCB entry in FCB 326 includes information identifying a particular multicast session.
- Each multicast session is defined by a ⁇ Source, Group ⁇ pair, which is sometimes referred to as an ⁇ S, G ⁇ pair.
- the Source field of the ⁇ S, G ⁇ pair defines the source of the multicast transmission. In one example, this is a single multicast transmission source. In another example, there are multiple (e.g., redundant) transmission sources for the same multicast transmission.
- the Group field of the ⁇ S, G ⁇ pair defines a group corresponding to the multicast session. In one example, the group can be conceptualized as a “channel” of content. There may be one recipient or a very large number of recipients of the content.
- Such recipients of the multicast content can join or leave the Group at will, such as by issuing the appropriate Internet Group Management Protocol (IGMP) request or using one or more other protocols.
- IGMP Internet Group Management Protocol
- each multicast session can have multiple IP flows associated with that particular multicast session, there can be multiple FCBs associated with the same ⁇ S, G ⁇ , where each FCB corresponds to one of these IP flows, and the ⁇ S, G ⁇ defines the particular multicast session. This may be true, for example, in the adaptive-optimized mode case, where because of the different services levels needed, there are different IP flows associated with the same multicast session.
- FIG. 5 is a block diagram of one example of an OIF module 330 and multicast TCB module 334 for a set of multicast sessions defined by respective ⁇ S, G ⁇ pairs ⁇ S, G ⁇ 1 through ⁇ S, G ⁇ n .
- the ⁇ S, G ⁇ pair 500 of a particular multicast session includes a first pointer 501 that points to a dynamically allocated set of OIF Blocks 502 .
- the particular number of OIF Blocks 502 depends on how many OIFs are then participating in that multicast session. For a particular multicast session, each OIF block 502 points to a subsequent OIF block 502 (with the exception of the last OIF block 502 in this conceptual “chain” of OIF blocks).
- Each OIF block includes a reasonably small number of slots 503 for storing corresponding second pointers 504 to a TCB 506 for a particular OIF.
- the example of FIG. 5 illustrates eight slots 503 per OIF block 502 , each slot for storing a corresponding second pointer 504 to a TCB 506 .
- Another example includes six second pointer slots 503 per OIF block 502 .
- Each second pointer 504 points to a particular TCB 506 for a particular OIF, which may service one or more users participating in the corresponding multicast session.
- Each OIF block 502 typically has the same number of second pointer slots 503 as every other OIF block 502 , however, the number of OIF blocks 502 can vary between different ⁇ S, G ⁇ pairs, or even for the same ⁇ S, G ⁇ pair, such as at different points in time when different numbers of OIFs are part of that particular multicast session. More particularly, as OIFs are added or removed from a multicast session (such as may happen when users join or leave the multicast session) corresponding second pointers 504 are added or removed, respectively. If needed, additional OIF blocks 502 are added or removed, such as to accommodate the addition or removal of the second pointers 504 .
- each multicast session includes OIF blocks 502 that are chained together by third pointers 505 from one OIF block 502 to another OIF block 502 (except for the last OIF block 502 in the chain).
- the OIF list can be updated by simply updating a single OIF block 502 , during which time the other OIF blocks 502 in that chain are still available and usable for performing multicast forwarding.
- each multicast session (defined by a particular ⁇ S, G ⁇ pair) points to its own chain of OIF blocks 502
- different multicast sessions point to the same (shared) chain of OIF blocks 502 .
- This will likely be the less typical case, for example, in which these two or more different multicast sessions each have the same OIFs participating in that multicast session.
- This can be conceptualized as two or more different channels that are being “watched” by the same OIFs.
- the pointers from each such multicast session can point to the same (shared) chain of OIF blocks 502 , if desired.
- separate chains of OIF blocks 502 can be maintained for each multicast session, for example, if such a simplified implementation is desired.
- Each second pointer 504 points to a particular TCB 506 , which typically includes information relevant to processing or routing packets to the particular OIF that is associated with that second pointer 504 , or to services associated with the particular OIF that is associated with that second pointer 504 . For example, if the packet header matches particular services in the ACL, attributes in the TCB are adjusted accordingly to obtain such services.
- Each second pointer 504 corresponds to a particular outbound interface (OIF) through which multicast packets are being forwarded, such as from the packet output interface 314 of the VR out over the network.
- OFIF outbound interface
- second pointers 504 from different multicast sessions can point to the same (shared) TCB 506 for that OIF.
- the second pointer PTR 2 ( 2 , 4 ) from the second multicast session points to the shared TCB( 1 ) as the second pointer PTR 2 ( n , 5 ) from the nth multicast session.
- second pointers 504 from different multicast sessions may share the same TCB 506 .
- a particular TCB 506 typically includes, among other things, OIF information 508 , header transformation information 510 , metering information 512 , and statistics information 514 .
- the OIF information 508 includes, for example, information identifying which OIF will be used by the packet output interface 314 to output the packets from the VR.
- the header transformation information 510 includes, for example, Media Access Control (MAC) address generation information and protocol independent multicast (PIM) encapsulation information for that particular OIF.
- the metering information 512 includes, for example, egress rate limiting or other like information for that particular OIF.
- the statistics information 514 includes egress statistics collection information for that particular OIF.
- the schema depicted in FIG. 5 provides numerous advantages. As discussed above, scalability from one to very many users is a desirable property. The ability to update the multicast forwarding schema as many users join or leave different multicast sessions (which sometimes results in adding or removing OIFs) is another desirable property. For example, when a user joins or leaves a multicast session under circumstances that require adding or removing an OIF to that multicast session, the OIF list can be updated by simply updating a single OIF block 502 , during which time the other OIF blocks 502 in that chain are still available and usable for performing multicast forwarding.
- each OIF block 502 is typically apportioned into a small number of second pointer slots 503 .
- Each OIF block 502 is typically independently addressable and updatable when updating that OIF block to add or remove a particular OIF's second pointer 504 .
- both OIF blocks 502 and TCBs 506 are capable of being dynamically allocated as needed. Together with the sharing of TCBs 506 or even of OIF chains, as discussed above, the schema illustrated in FIG. 5 typically offers one or more of the advantages of scalability, updatability, efficiency in memory usage, and high throughput performance with reduced interruptions.
- FIG. 6 is a flow chart of one example of a process that is invoked if multicast packet forwarding is invoked at 410 of FIG. 4 .
- a multicast forwarding operation is initiated, such as by calling executable or interpretable instructions of the multicast forwarding module 324 .
- information in the packet header is mapped to an FCB entry in FCB module 326 .
- Each FCB entry in the FCB module 326 identifies an IP flow or a group of IP flows for an ⁇ S, G ⁇ pair 500 corresponding to a particular multicast session.
- a first pointer 501 is extracted to the first OIF block 502 in the chain of one or more OIF blocks 502 corresponding to that multicast session.
- next second pointer 504 in the current OIF block 502 is retrieved.
- the retrieved second pointer 504 to a TCB 506 is used to build a portion of a control block that will be sent to the DMA engine 310 .
- process flow returns to 606 . Otherwise, process flow proceeds to 606 and the control block that was constructed for the completed OIF block 502 is sent to the DMA engine 310 . In this manner, one control block corresponding to each OIF block 502 is sent to the DMA engine 310 after that control block is constructed from the corresponding OIF block 502 .
- process flow returns to 606 . Otherwise, at 610 , if no other OIF blocks 501 exist in the chain, then process flow proceeds to 614 to process (or wait for) the next received packet (e.g., at 400 of FIG. 4 ).
- FIG. 7 is a flow chart of one example of packet retrieval and replication.
- the DMA engine 310 receives a control block (such as from 608 in FIG. 6 ).
- the next entry in the received control block is retrieved.
- the stored packet is retrieved from a packet buffer in the main memory 302 by DMA engine 310 .
- the retrieved packet is sent to the egress module 306 for egress transmission, along with the corresponding control block entry, which provides information to the egress module 306 about how that particular packet is to be processed for the particular recipient user corresponding to the control block entry, which, in turn, corresponded to a particular second pointer 504 , as discussed above.
- process flow returns to 702 to retrieve the next entry in the control block. Otherwise, process flow returns to 700 to receive (or wait for) another control block.
- a packet is held in the packet buffer in the main memory 302 so that it can be replicated.
- the replicated packets are sent to the egress module 306 for further processing (particular to the user that is to receive that replicated packet) and transmission that OIF.
- FIG. 8 is a flow chart of one example of processing by the egress module 306 .
- a replicated packet is received from the DMA engine 310 .
- the replicated packet is processed according to the TCB 506 corresponding to the particular OIF's second pointer 504 . As discussed above, such information is encapsulated into the control block that was submitted to the DMA engine 310 , and communicated to the egress module 306 along with the replicated packet.
- header transformation occurs. In one example, this includes MAC address generation or encapsulation appropriate for the designated OIF over which the replicated packet will be transmitted.
- egress rate limiting, if any is applied.
- egress statistics, if any, are computed.
- the replicated packet is transmitted out over the computer network on the designated OIF.
- FIG. 9 is a flow chart of one example of more detail of acts included in the multicast forwarding, such as at 602 of FIG. 6 or elsewhere, as appropriate. Among other things, the flow chart of FIG. 9 illustrates one example of how TCBs 506 are created and, where possible, shared.
- the system determines whether a received packet represents a new IP flow. This can be determined by looking at the above-described attributes in the packet header that identify a particular IP flow. If the packet corresponds to a previously identified multicast IP flow, then process flow proceeds to 606 , and a previously defined FCB entry and a previously defined TCB 506 are used for further multicast forwarding processing. If a new flow is detected at 900 , there will be no matching FCB entry in FCB 326 . Therefore, for a new flow detected at 900 , a new FCB entry will be created in FCB 326 , as discussed below.
- a new flow is detected at 900 , then, at 902 , is its determined whether the new flow is a strict optimized mode or, instead, is in an adaptive optimized mode that provides one or more services for that particular flow. This determination is typically made using a configurable attribute.
- an OIF list (e.g., a chain of OIF blocks, as illustrated in FIG. 5 ) is built for the ⁇ S, G ⁇ entry corresponding to the newly identified multicast flow. Because no flow-specific services are required, this OIF list includes second pointers 504 to a default TCB corresponding to each OIF in that multicast session. This default TCB does not include any per-flow of ACL-based service-specific attributes. Instead this default TCB typically depends only on attributes and services that are applicable to all flows associated with the particular VI serving as the OIF. Each OIF participating in the multicast session will have a corresponding second pointer 504 to its corresponding default TCB.
- the OIF module 330 of the PFE 300 is updated with each OIF block 502 in the chain of OIF blocks that make up the OIF list of that particular multicast flow.
- the OIF module 330 of the PFE 300 is typically updated with such OIF blocks 502 on a block-by-block basis.
- the FCB 326 of the PFE 300 is updated to include, for example, a pointer to the OIF list for the newly identified multicast flow. Then, process flow proceeds to 606 of FIG. 6 (or elsewhere, if appropriate).
- the adaptive optimized mode instead of the strict optimized mode, then, at 910 it is determined whether any ingress services are needed. In one example, this includes checking for such ingress services on the VI 208 at which the packet is received.
- a TCB 506 is created to control the providing of any such ingress services, (otherwise process flow proceeds to 916 ).
- a second pointer 504 is created to point to this newly created TCB 506 .
- This newly created TCB 506 for the ingress services includes an OIF field 508 that specifies a null OIF (the PFE 300 does not actually forward any packets out any such null OIF).
- next OIF entry that is, a second pointer 504
- process flow proceeds to 906 .
- next OIF entry that is, a second pointer 504
- process flow proceeds to 906 .
- a second pointer 504 is created to point to the new TCB 506 or the default TCB 332 , as appropriate, and the OIF list for that multicast session is updated accordingly.
- some TCBs 506 may be shared by multiple second pointers 504 .
- the default TCB 332 is likely shared by multiple second pointers 504 .
- Other TCBs 506 may correspond to individual second pointers 504 .
Abstract
Methods, apparatus and data structures are provided for managing multicast IP flows. According to one embodiment, a network switch module includes a memory and multiple processors partitioned among multiple virtual routers (VRs). Each VR maintains a data structure containing therein information regarding the multicast sessions, including a first value for each of the multicast sessions, at least one chain of one or more blocks of second values and one or more transmit control blocks (TCBs). Each first value is indicative of a chain of one or more blocks of second values. Each second value corresponds to an outbound interface (OIF) participating in the multicast session and identifies a number of times packets associated with the multicast session are to be replicated. The TCBs have stored therein control information to process or route packets. Each second value is indicative of a TCB that identifies an OIF of the network device through which packets are to be transmitted.
Description
- This application is a continuation of U.S. patent application Ser. No. 14/616,521, filed Feb. 6, 2015, which is a continuation of U.S. patent application Ser. No. 13/756,071, filed Jan. 31, 2013, now U.S. Pat. No. 8,953,513, which is a continuation of U.S. patent application Ser. No. 13/015,880, filed Jan. 31, 2011, now U.S. Pat. No. 8,369,258, which is a continuation of U.S. patent application Ser. No. 12/328,858, filed Feb. 12, 2009, now U.S. Pat. No. 8,213,347, which is a divisional of U.S. patent application Ser. No. 10/949,943 filed Sep. 24, 2004, now U.S. Pat. No. 7,499,419, all of which are hereby incorporated by reference in their entirety for all purposes.
- Contained herein is material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction of the patent disclosure by any person as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights to the copyright whatsoever. Copyright© 2004-2015, Fortinet, Inc.
- 1. Field
- Various embodiments of the present invention are generally related to the field of telecommunications and more particularly, but not by way of limitation, to network switches and systems and methods for multicast internet protocol (IP) forwarding.
- 2. Description of the Related Art
- The use of computer or communications networks, including Local Area Networks (LANs), Wide-Area Networks (WANs), and the Internet continues to grow at ever increasing rates. Each day, more and more computer systems or communications devices are becoming interconnected in such wired or wireless networks, which typically communicate data in packets. This has created a need for high performance network switches, such as for use by network service providers. Many such switches comprise multiple modules, with many data flows between the modules themselves and between the interfaces to external networks. A data flow is sometimes called an “IP flow,” which refers to a stream of packets that enter and exit the same set of interfaces. The packets of a particular IP flow have the same values in the IP packet header for the following six attributes of the IP packet header: (1) Source IP Address, (2) Source L4 Port, (3) Type of Service (TOS), (4) Destination IP Address, (5) Destination L4 Port, and (6) Protocol.
- In some cases, the network switch modules, including the processors residing in the modules, can be partitioned into virtual routers (VRs), that is, software running on the processors that emulates the functioning of an individual physical hardware router. As a result of the combination of hundreds of thousands of data flows for the virtual routers in these network switches, there is a need for efficiently processing packet data flows, and for controlling the resources consumed within the network switch.
- As broadband network access becomes more available, individual subscribers of network service providers have more available options for different services and service levels. Even the same subscriber may have different service needs at different times. As an illustrative example, a first subscriber may desire high definition television (HDTV) service over a network. A second subscriber may desire mobile telephone service over the network. The first subscriber may occasionally desire video-on-demand (VOD). The second subscriber may need to switch between voice communication and high-speed digital data communication.
- A “unicast” communication typically refers to a communication from a single source device to a single destination device over a network. By contrast, a “multicast” communication typically refers to a communication to a group of destination devices from one or more source devices. Multicast packet forwarding raises additional complexity because of the many destination devices. Many existing router devices will be unable to provide the desired scalability to accommodate such additional destination devices. This is particularly true when each individual data flow may require “per-flow” services for the multicast traffic. Allocating resources efficiently for a large number of multicast data flows is a challenging problem. Moreover, multicast broadcasting of content presents additional complexity because individual users may join or leave a particular multicast group at will and often. Such “channel surfing” creates an additional burden for keeping track of the participants of a multicast group so that the content can be routed appropriately.
- Methods, apparatus and data structures for managing multicast Internet Protocol (IP) flows are described. According to one embodiment, a network switch module includes a memory and multiple processors partitioned among multiple virtual routers (VRs). Each VR maintains a data structure containing therein information regarding the active multicast IP sessions, including a first value (e.g., a pointer) for each of the active multicast IP sessions, at least one chain of one or more blocks of second values (e.g., pointers) and one or more transmit control blocks (TCBs). Each first value is indicative of a chain of one or more blocks of second values. Each second value is indicative of an outbound interface (OIF) of the network device participating in the active multicast IP session defined by the first value and identifies a number of times packets associated with the active multicast IP session are to be replicated. The TCBs have stored therein control information to process or route packets. Each second value is indicative of a TCB. Each TCB identifies an OIF of the network device through which packets are to be transmitted.
- Other features of embodiments of the present invention will be apparent from the accompanying drawings and from the detailed description that follows.
- Embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which like reference numerals refer to similar elements and in which:
-
FIG. 1 is a block diagram of one example of an operating environment for the present system and methods. -
FIG. 2 is a block diagram of one example of a Virtual Router (VR) in accordance with an embodiment of the present invention. -
FIG. 3 is a block diagram of one example of a Packet Forwarding Engine (PFE) and a main memory of a VR in accordance with embodiments of the present invention. -
FIG. 4 is a flow chart illustrating a multicast internet protocol (IP) packet forwarding method in accordance with an embodiment of the present invention. -
FIG. 5 is a block diagram of an OIF module and multicast TCB module for a set of multicast sessions in accordance with an embodiment of the present invention. -
FIG. 6 is a flow chart illustrating a process that is invoked in accordance with an embodiment of the present invention if multicast packet forwarding is invoked inFIG. 4 . -
FIG. 7 is a flow chart illustrating packet retrieval and replication in accordance with an embodiment of the present invention. -
FIG. 8 is a flow chart illustrating processing by an egress module in accordance with an embodiment of the present invention. -
FIG. 9 is a flow chart illustrating more detail of acts included in the multicast forwarding in accordance with an embodiment of the present invention. - Methods, apparatus and data structures for multicast internet protocol (IP) forwarding are described herein. In the following description, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Note that in this description, references to “one embodiment” or “an embodiment” mean that the feature being referred to is included in at least one embodiment of the invention. Further, separate references to “one embodiment” in this description do not necessarily refer to the same embodiment; however, neither are such embodiments mutually exclusive, unless so stated and except as will be readily apparent to those of ordinary skill in the art. Thus, the present invention can include any variety of combinations and/or integrations of the embodiments described herein. Moreover, in this description, the phrase “exemplary embodiment” means that the embodiment being referred to serves as an example or illustration.
- Herein, block diagrams illustrate exemplary embodiments of the invention. Also herein, flow diagrams illustrate operations of the exemplary embodiments of the invention. The operations of the flow diagrams will be described with reference to the exemplary embodiments shown in the block diagrams. However, it should be understood that the operations of the flow diagrams could be performed by embodiments of the invention other than those discussed with reference to the block diagrams, and embodiments discussed with references to the block diagrams could perform operations different than those discussed with reference to the flow diagrams. Moreover, it should be understood that although the flow diagrams may depict serial operations, certain embodiments could perform certain of those operations in parallel.
- The following detailed description includes references to the accompanying drawings, which form a part of the detailed description. The drawings show, by way of illustration, specific embodiments in which the invention may be practiced. These embodiments, which are also referred to herein as “examples,” are described in enough detail to enable those skilled in the art to practice the invention. The embodiments may be combined, other embodiments may be utilized, or structural, logical and electrical changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
- In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one. In this document, the term “or” is used to refer to a nonexclusive or, unless otherwise indicated. Furthermore, all publications, patents, and patent documents referred to in this document are incorporated by reference herein in their entirety, as though individually incorporated by reference. In the event of inconsistent usages between this document and those documents so incorporated by reference, the usage in the incorporated reference(s) should be considered supplementary to that of this document; for irreconcilable inconsistencies, the usage in this document controls.
- Some portions of the following detailed description are presented in terms of algorithms and symbolic representations of operations on data bits within a computer memory. These algorithmic descriptions and representations are the ways used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm includes a self-consistent sequence of steps leading to a desired result. The steps are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like. It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless specifically stated otherwise as apparent from the following discussions, terms such as “processing” or “computing” or “calculating” or “determining” or “displaying” or the like, refer to the action and processes of a computer system, or similar computing device, that manipulates and transforms data represented as physical (e.g., electronic) quantities within the computer system's registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices.
-
FIG. 1 is a block diagram of one example of an operating environment for the present system and methods. In the example ofFIG. 1 , asystem 100 typically includes personal computers (PCs) 102 that are respectively connected to modems 106. Themodems 106 are typically respectively connected to a digital subscriber line access module (DSLAM) 116. TheDSLAM 116 multiplexes signals from themodems 106 onto the Internet Protocol (IP)network 118. TheIP network 118 is typically connected to arouter box 114 that includes virtual routers (VRs) 128. Therouter box 114 is typically connected to theInternet 112. Therouter box 114 is also typically connected to a dynamic host configuration protocol (DHCP)server 120, aweb portal 122, aRADIUS server 124, and acontrol server 126. - Although, in this example, the
router 114 includes threeVRs 128, other examples call for any number ofVRs 128. In one example, one or more of theVRs 128 can establish subscriber connections, such as to users of thePCs 102. When establishing such connections, theVRs 128 can use theDHCP server 120 for assigning IP network addresses to thePCs 102. The VRs 128 can use theRADIUS server 124 to authenticate subscribers. After authenticating subscribers, theVRs 128 can configure subscriber connections according to service profiles, which refer to subscriber-specific services that individual subscribers receive during connections. In one example, theVRs 128 can receive service profiles information from thecontrol server 126 or the RADIUS server 224. - After the
VRs 128 establish subscriber connections, they typically provide access to theweb portal 122, where users can select new services. Additionally, after establishing subscriber connections, theVRs 128 typically process and forward packets over theIP network 118 and theInternet 112. AlthoughFIG. 1 illustrates an example in which the users accessing theInternet 112 via PCs, this is merely an illustrative example. In other examples, the individual users may access theInternet 112 or other computer or communications network wirelessly, such as by using a 3rd Generation (3G) or other mobile phone or other handheld or portable device, or by using a laptop or other portable computing device with Wireless Fidelity (WiFi) (e.g., using IEEE 802.11b wireless networking) capability or the like. In still other examples, the individual users may access theInternet 112 or other communications or computer network using an Ethernet connection, a Very High bit rate Digital Subscriber Line (VHDSL) connection, a Fiber To The Premises (FTTP) connection, or a cable TV line or like connection, or the like. Thus, the present systems and methods are not limited to any particular devices or techniques for accessing theInternet 112, such as through therouter box 114. Theexemplary system 100 typically provides network services to thousands of subscribers. Each subscriber can receive a particular set of services upon establishing a connection with thesystem 100. -
FIG. 2 is a block diagram of one example of aVR 128. In this example, theVR 128 includes a packet forwarding engine (PFE) 206, and one or more virtual interfaces (VIs) 208 from a source or to a destination. A VI over which multicast packets are forwarded is sometimes referred to as an Outbound Interface (OIF). Different services can be applied to multicast packet forwarding traffic as well as unicast packet forwarding traffic. Which services are applied to a particular packet are determined, in one example, by an inbound policy or an outbound policy associated with aparticular VI 208. In one example, the packet header (e.g., one or more of the above-described six packet header attributes defining an IP flow) is examined (e.g., such as by comparing such attribute(s) to one or more matching criteria in an access control list (ACL)) to determine whether any services should be applied to the packet and, if so, which services should be applied. -
FIG. 3 is a block diagram of one example of a Packet Forwarding Engine (PFE) 300 and a main memory 302 of aVR 128. In this example,PFE 300 includes aningress module 304, anegress module 306, aPFE memory 308, a Direct Memory Access (DMA)engine 310, apacket input interface 312, apacket output interface 314, and amain memory interface 316. In this example, theingress module 304 includes an ingressrate limit module 318, aningress statistics module 320, aflow classification module 322, and a multicast forwarding module 324. In this example, thePFE memory 308 includes a Flow Control Block (FCB) 326, amulticast block 328, an Outbound InterFace (OIF)module 330, a default Transmit Control Block (TCB) 332, amulticast TCB module 334, ametering block 336, and astatistics block 338. In this example, theegress module 306 includes aTCB processing module 340, aheader transform module 342, an egressrate limit module 344, and anegress statistics module 346. -
FIG. 4 is a flow chart of one example of a multicast internet protocol (IP) packet forwarding method such as can be performed, for example, by using thePFE 300 and main memory 302 ofFIG. 3 . At 400, a packet is received at thepacket input interface 312 on a particular virtual interface (VI) of a particular VR in therouter box 114. When a packet is received at 400, it is not known whether the packet is part of a multicast data flow or a unicast data flow. At 402, in one example, the ingressrate limit module 318 performs a rate limiting function to control a packet ingress data rate through theingress module 304. At 404, in one example, theingress statistics module 320 computes packet ingress statistics, such as packet count, byte count, etc. Such ingress statistics may be important for managing subscriber service levels, among other things. - At 406, in one example, the
flow classification module 322 is used to classify the data flow, for example, as a unicast flow or a multicast flow. Theflow classification module 322 typically uses a predefined portion of the packet header to classify the data flow, and to identify the particular FCB associated with the flow. For example, the “destination address” portion of the packet header is used to identify the packet as a multicast packet. In one example, in a first mode (sometimes referred to as a “strict-optimized mode”), the data flow classification uses the source IP address and the destination IP address portions of the packet header to classify the data flow. In a second mode (sometimes referred to as an “adaptive-optimized mode”), in which subscriber-specific services are needed, additional portions of the packet header are used to further classify the data flow in accordance with the appropriate services. - In one example, the flow classification at 406 uses the information extracted from the packet header to look up a corresponding FCB entry in
FCB 326. If the data flow is a multicast data flow then, in one example, the corresponding FCB entry will have a “multicast” flag set, and a “forwarding action” field of the FCB entry will indicate that hardware forwarding of packets is to be used for the multicast data flow. At 408, if the classification indicates a multicast data flow, then, at 410, multicast packet forwarding is invoked. Otherwise, at 412, unicast packet forwarding is invoked. - Each FCB entry in
FCB 326 includes information identifying a particular multicast session. Each multicast session is defined by a {Source, Group} pair, which is sometimes referred to as an {S, G} pair. The Source field of the {S, G} pair defines the source of the multicast transmission. In one example, this is a single multicast transmission source. In another example, there are multiple (e.g., redundant) transmission sources for the same multicast transmission. The Group field of the {S, G} pair defines a group corresponding to the multicast session. In one example, the group can be conceptualized as a “channel” of content. There may be one recipient or a very large number of recipients of the content. Such recipients of the multicast content can join or leave the Group at will, such as by issuing the appropriate Internet Group Management Protocol (IGMP) request or using one or more other protocols. Thus, scalability and the ability to easily update the Group are desirable qualities of the present multicast forwarding systems and methods. - Since each multicast session can have multiple IP flows associated with that particular multicast session, there can be multiple FCBs associated with the same {S, G}, where each FCB corresponds to one of these IP flows, and the {S, G} defines the particular multicast session. This may be true, for example, in the adaptive-optimized mode case, where because of the different services levels needed, there are different IP flows associated with the same multicast session.
-
FIG. 5 is a block diagram of one example of anOIF module 330 andmulticast TCB module 334 for a set of multicast sessions defined by respective {S, G} pairs {S, G}1 through {S, G}n. The {S, G} pair 500 of a particular multicast session includes afirst pointer 501 that points to a dynamically allocated set ofOIF Blocks 502. The particular number ofOIF Blocks 502 depends on how many OIFs are then participating in that multicast session. For a particular multicast session, each OIF block 502 points to a subsequent OIF block 502 (with the exception of thelast OIF block 502 in this conceptual “chain” of OIF blocks). - Each OIF block includes a reasonably small number of
slots 503 for storing correspondingsecond pointers 504 to aTCB 506 for a particular OIF. The example ofFIG. 5 illustrates eightslots 503 perOIF block 502, each slot for storing a correspondingsecond pointer 504 to aTCB 506. Another example includes sixsecond pointer slots 503 perOIF block 502. Eachsecond pointer 504 points to aparticular TCB 506 for a particular OIF, which may service one or more users participating in the corresponding multicast session. Each OIF block 502 typically has the same number ofsecond pointer slots 503 as every other OIF block 502, however, the number of OIF blocks 502 can vary between different {S, G} pairs, or even for the same {S, G} pair, such as at different points in time when different numbers of OIFs are part of that particular multicast session. More particularly, as OIFs are added or removed from a multicast session (such as may happen when users join or leave the multicast session) correspondingsecond pointers 504 are added or removed, respectively. If needed, additional OIF blocks 502 are added or removed, such as to accommodate the addition or removal of thesecond pointers 504. Using the present systems and methods, dynamically adding or removing such OIF blocks 502 as needed is easy because, among other things, each multicast session includes OIF blocks 502 that are chained together bythird pointers 505 from oneOIF block 502 to another OIF block 502 (except for thelast OIF block 502 in the chain). When a user joins or leaves a multicast session under circumstances that require adding or removing an OIF to that multicast session, the OIF list can be updated by simply updating asingle OIF block 502, during which time the other OIF blocks 502 in that chain are still available and usable for performing multicast forwarding. AlthoughFIG. 5 illustrates a typical example in which each multicast session (defined by a particular {S, G} pair) points to its own chain of OIF blocks 502, it is possible that, in one example implementation, different multicast sessions point to the same (shared) chain of OIF blocks 502. This will likely be the less typical case, for example, in which these two or more different multicast sessions each have the same OIFs participating in that multicast session. This can be conceptualized as two or more different channels that are being “watched” by the same OIFs. When this occurs, the pointers from each such multicast session can point to the same (shared) chain of OIF blocks 502, if desired. Alternatively, separate chains of OIF blocks 502 can be maintained for each multicast session, for example, if such a simplified implementation is desired. - Each
second pointer 504 points to aparticular TCB 506, which typically includes information relevant to processing or routing packets to the particular OIF that is associated with thatsecond pointer 504, or to services associated with the particular OIF that is associated with thatsecond pointer 504. For example, if the packet header matches particular services in the ACL, attributes in the TCB are adjusted accordingly to obtain such services. Eachsecond pointer 504 corresponds to a particular outbound interface (OIF) through which multicast packets are being forwarded, such as from thepacket output interface 314 of the VR out over the network. - Because more than one multicast session can use the same OIF of the VR,
second pointers 504 from different multicast sessions can point to the same (shared)TCB 506 for that OIF. In the illustrative example ofFIG. 5 , the second pointer PTR2(2,4) from the second multicast session points to the shared TCB(1) as the second pointer PTR2(n,5) from the nth multicast session. Thus,second pointers 504 from different multicast sessions may share thesame TCB 506. - Similarly, because multiple IP flows can use the same OIF, there can be
multiple TCBs 506 for the same OIF, such as for multiple IP flows on the same OIF, where such multiple flows use different services and, therefore, have differentcorresponding TCBs 506. - In
FIG. 5 , for example, aparticular TCB 506 typically includes, among other things,OIF information 508,header transformation information 510,metering information 512, andstatistics information 514. TheOIF information 508 includes, for example, information identifying which OIF will be used by thepacket output interface 314 to output the packets from the VR. Theheader transformation information 510 includes, for example, Media Access Control (MAC) address generation information and protocol independent multicast (PIM) encapsulation information for that particular OIF. Themetering information 512 includes, for example, egress rate limiting or other like information for that particular OIF. Thestatistics information 514 includes egress statistics collection information for that particular OIF. - The schema depicted in
FIG. 5 provides numerous advantages. As discussed above, scalability from one to very many users is a desirable property. The ability to update the multicast forwarding schema as many users join or leave different multicast sessions (which sometimes results in adding or removing OIFs) is another desirable property. For example, when a user joins or leaves a multicast session under circumstances that require adding or removing an OIF to that multicast session, the OIF list can be updated by simply updating asingle OIF block 502, during which time the other OIF blocks 502 in that chain are still available and usable for performing multicast forwarding. - The schema depicted in
FIG. 5 allows many users to be managed very efficiently because of, among other things, its use offirst pointers 501 from {S, G} pairs to shared or independent chains of OIF blocks 502, and per-OIFsecond pointers 504 to shared orindependent TCBs 506. Moreover, each OIF block 502 is typically apportioned into a small number ofsecond pointer slots 503. Each OIF block 502 is typically independently addressable and updatable when updating that OIF block to add or remove a particular OIF'ssecond pointer 504. As an illustrative example, if the OIF corresponding to second pointer PTR2(1,3) in OIF Block (1,1) was removed from the multicast session of {S, G}1 (for example, because all of the one or more users of that OIF left that multicast session), then the second pointer PTR2(1, 3) in that OIF Block (1, 1) is removed, opening onesecond pointer slot 503 in OIF Block (1, 1) that could later be filled by another second pointer for another OIF being added (e.g., to service one or more users joining that multicast session). - While such updating of a
particular OIF block 502 is occurring, other OIF blocks 502 in the same or a different chain of OIF blocks 502 are still usable to carry out multicast forwarding to the users represented by thesecond pointers 504 in those other OIF blocks 502. This improves the ability to multicast content, without interruption, to a large number of recipient users on different OIFs of a particular multicast session, even as othersecond pointers 504 are added or removed, such as to accommodate other recipient users of that multicast session that are joining or leaving that multicast session. In one example, both OIF blocks 502 andTCBs 506 are capable of being dynamically allocated as needed. Together with the sharing ofTCBs 506 or even of OIF chains, as discussed above, the schema illustrated inFIG. 5 typically offers one or more of the advantages of scalability, updatability, efficiency in memory usage, and high throughput performance with reduced interruptions. -
FIG. 6 is a flow chart of one example of a process that is invoked if multicast packet forwarding is invoked at 410 ofFIG. 4 . At 600, a multicast forwarding operation is initiated, such as by calling executable or interpretable instructions of the multicast forwarding module 324. At 602, information in the packet header is mapped to an FCB entry inFCB module 326. Each FCB entry in theFCB module 326 identifies an IP flow or a group of IP flows for an {S, G} pair 500 corresponding to a particular multicast session. At 604, from that FCB entry, afirst pointer 501 is extracted to thefirst OIF block 502 in the chain of one or more OIF blocks 502 corresponding to that multicast session. - At 606 the next
second pointer 504 in thecurrent OIF block 502 is retrieved. At 606, the retrievedsecond pointer 504 to aTCB 506 is used to build a portion of a control block that will be sent to theDMA engine 310. At 606, if othersecond pointers 504 exist in thecurrent OIF block 502, then process flow returns to 606. Otherwise, process flow proceeds to 606 and the control block that was constructed for the completedOIF block 502 is sent to theDMA engine 310. In this manner, one control block corresponding to each OIF block 502 is sent to theDMA engine 310 after that control block is constructed from the correspondingOIF block 502. At 610, if other OIF blocks 502 exist in that chain, then the next OIF block 502 is retrieved and made the current OIF block, a new control block is initiated, and process flow returns to 606. Otherwise, at 610, if no other OIF blocks 501 exist in the chain, then process flow proceeds to 614 to process (or wait for) the next received packet (e.g., at 400 ofFIG. 4 ). -
FIG. 7 is a flow chart of one example of packet retrieval and replication. At 700, theDMA engine 310 receives a control block (such as from 608 inFIG. 6 ). At 702, the next entry in the received control block is retrieved. At 704, the stored packet is retrieved from a packet buffer in the main memory 302 byDMA engine 310. At 706, the retrieved packet is sent to theegress module 306 for egress transmission, along with the corresponding control block entry, which provides information to theegress module 306 about how that particular packet is to be processed for the particular recipient user corresponding to the control block entry, which, in turn, corresponded to a particularsecond pointer 504, as discussed above. At 708, if there are more entries in the control block, then process flow returns to 702 to retrieve the next entry in the control block. Otherwise, process flow returns to 700 to receive (or wait for) another control block. In the manner illustrated inFIG. 7 , a packet is held in the packet buffer in the main memory 302 so that it can be replicated. The replicated packets are sent to theegress module 306 for further processing (particular to the user that is to receive that replicated packet) and transmission that OIF. -
FIG. 8 is a flow chart of one example of processing by theegress module 306. At 800, a replicated packet is received from theDMA engine 310. At 802, the replicated packet is processed according to theTCB 506 corresponding to the particular OIF'ssecond pointer 504. As discussed above, such information is encapsulated into the control block that was submitted to theDMA engine 310, and communicated to theegress module 306 along with the replicated packet. At 804, header transformation occurs. In one example, this includes MAC address generation or encapsulation appropriate for the designated OIF over which the replicated packet will be transmitted. At 806, egress rate limiting, if any, is applied. At 808, egress statistics, if any, are computed. At 810, the replicated packet is transmitted out over the computer network on the designated OIF. -
FIG. 9 is a flow chart of one example of more detail of acts included in the multicast forwarding, such as at 602 ofFIG. 6 or elsewhere, as appropriate. Among other things, the flow chart ofFIG. 9 illustrates one example of howTCBs 506 are created and, where possible, shared. - At 900, the system determines whether a received packet represents a new IP flow. This can be determined by looking at the above-described attributes in the packet header that identify a particular IP flow. If the packet corresponds to a previously identified multicast IP flow, then process flow proceeds to 606, and a previously defined FCB entry and a previously defined
TCB 506 are used for further multicast forwarding processing. If a new flow is detected at 900, there will be no matching FCB entry inFCB 326. Therefore, for a new flow detected at 900, a new FCB entry will be created inFCB 326, as discussed below. - If a new flow is detected at 900, then, at 902, is its determined whether the new flow is a strict optimized mode or, instead, is in an adaptive optimized mode that provides one or more services for that particular flow. This determination is typically made using a configurable attribute.
- At 902, if in the strict optimized mode, then, at 904, an OIF list (e.g., a chain of OIF blocks, as illustrated in
FIG. 5 ) is built for the {S, G} entry corresponding to the newly identified multicast flow. Because no flow-specific services are required, this OIF list includessecond pointers 504 to a default TCB corresponding to each OIF in that multicast session. This default TCB does not include any per-flow of ACL-based service-specific attributes. Instead this default TCB typically depends only on attributes and services that are applicable to all flows associated with the particular VI serving as the OIF. Each OIF participating in the multicast session will have a correspondingsecond pointer 504 to its corresponding default TCB. Then, at 906, theOIF module 330 of thePFE 300 is updated with each OIF block 502 in the chain of OIF blocks that make up the OIF list of that particular multicast flow. TheOIF module 330 of thePFE 300 is typically updated with such OIF blocks 502 on a block-by-block basis. Then, at 908, theFCB 326 of thePFE 300 is updated to include, for example, a pointer to the OIF list for the newly identified multicast flow. Then, process flow proceeds to 606 ofFIG. 6 (or elsewhere, if appropriate). - At 902, if in the adaptive optimized mode instead of the strict optimized mode, then, at 910 it is determined whether any ingress services are needed. In one example, this includes checking for such ingress services on the
VI 208 at which the packet is received. At 910, if one or more such ingress services are needed, then, at 912, aTCB 506 is created to control the providing of any such ingress services, (otherwise process flow proceeds to 916). Then, at 914, asecond pointer 504 is created to point to this newly createdTCB 506. This newly createdTCB 506 for the ingress services includes anOIF field 508 that specifies a null OIF (thePFE 300 does not actually forward any packets out any such null OIF). - At 916, it is determined whether there is a next OIF entry (that is, a second pointer 504) in the OIF list for the new multicast flow. If there is no such next OIF entry (e.g., upon specification of an invalid {S, G} entry or a null OIF), then process flow proceeds to 906. Otherwise, at 918, it is determined whether any outbound services are needed on the next OIF entry in the
OIF module 330. If so, then, at 920, anew TCB 506 is created for that OIF entry to control the providing of any such outbound services, otherwise, at 922, theVI default TCB 332 is used for that OIF entry. Then, at 924, asecond pointer 504 is created to point to thenew TCB 506 or thedefault TCB 332, as appropriate, and the OIF list for that multicast session is updated accordingly. Then, at 926, it is determined if there is a next OIF entry in the OIF list for the multicast session. If so, process flow returns to 918, otherwise process flow proceeds to 906. - Using the above process described with respect to
FIG. 9 , someTCBs 506 may be shared by multiplesecond pointers 504. For example, thedefault TCB 332 is likely shared by multiplesecond pointers 504.Other TCBs 506 may correspond to individualsecond pointers 504. - Although the above examples have been discussed with respect to a router box providing virtual routers (e.g., VRs 128), the present systems and methods are not so limited. For example, certain aspects of the present systems and methods are also applicable to alternative systems using hardware routers instead of the virtual routers.
- It is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-described embodiments (and/or aspects thereof) may be used in combination with each other. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, device, article, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.
Claims (15)
1. A network switch module comprising:
a memory partitioned among a plurality of virtual routers (VRs);
a plurality of processors partitioned among the plurality of VRs; and
wherein each VR of the plurality of VRs maintains a data structure in the memory, the data structure including information relating to a set of multicast sessions being handled by the VR and including:
a plurality of pairs of a source field and a group field ({S, G} pairs) stored in the memory, in which each pair of the plurality of {S, G} pairs defines a multicast session of the set of multicast sessions and wherein the source field defines a source of a multicast transmission and the group field defines a group corresponding to the multicast session;
a first pointer associated with each of the plurality of {S, G} pairs that points to a dynamically allocated set of OIF blocks, wherein a number of outbound interface (OIF) blocks in the set of OIF blocks is dependent upon how many of a plurality of OIFs of the VR are currently participating in the multicast session and the number of OIF blocks in the set of OIF blocks defines how many times packets associated with the multicast session are to be replicated;
a set of slots associated with each OIF block of the set of OIF blocks, each slot of the set of slots configured to store a second pointer to a transmit control block (TCB) which services one or more users participating in the multicast session and which represents a data structure configured to store control information relevant to processing or routing packets, including information regarding an OIF of the plurality of OIFs through which the packets are to be transmitted;
a third pointer associated with each OIF block of the set of OIF blocks to chain together the set of OIF blocks, wherein only one OIF block of the set of OIF blocks is updated responsive to users joining or leaving the multicast session.
2. The network switch module of claim 1 , wherein each OIF block of the set of OIF blocks is independently accessible without affecting processing of other OIF blocks of the set of OIF blocks.
3. The network switch module of claim 1 , wherein the TCB includes control information for processing replicated packets.
4. The network switch module of claim 3 , wherein the control information includes one or more of header transformation control information, metering control information and statistics control information.
5. The network switch module of claim 3 , wherein the second pointer associated with a first OIF block of the set of OIF blocks of a first {S, G} pair of the plurality of {S, G} pairs is permitted to point to and thus share a first TCB with another OIF block of the set of OIF blocks of the first {S, G} pair or with a second OIF block of the set of OIF blocks of a second (S, G} pair of the plurality of {S, G} pairs.
6. A method of managing multicast Internet Protocol (IP) sessions, the method comprising:
identifying, by a router, active multicast IP sessions; and
maintaining, by the router, a data structure within a memory of the router containing therein information regarding the active multicast IP sessions;
wherein the data structure includes:
a plurality of pairs of a source field and a group field ({S, G} pairs), in which each pair of the plurality of {S, G} pairs defines a multicast IP session of the active multicast IP sessions, wherein the source field defines a source of a multicast transmission of the multicast IP session and the group field defines a group corresponding to the multicast IP session;
a first pointer associated with each of the plurality of {S, G} pairs that points to a dynamically allocated set of outbound interface (OIF) blocks, wherein a number OIF blocks in the dynamically allocated set of OIF blocks is dependent upon a number of OIFs of the router that are participating in the IP multicast session and the number of OIF blocks in the dynamically allocated set of OIF blocks defines a number of times packets of the IP multicast session are to be replicated;
a set of slots for each OIF block of the set of dynamically allocated OIF blocks, each slot of the set of slots having stored therein a second pointer to a transmit control block (TCB) data structure which services one or more users participating in the IP multicast session and which has stored therein control information to process or route packets of the IP multicast session, including information regarding an OIF of the router through which the packets are to be transmitted;
a third pointer associated with each OIF block of the set of dynamically allocated OIF blocks that links together the set of dynamically allocated OIF blocks and updates only one of OIF block of the OIF blocks responsive to users joining or leaving the IP multicast session.
7. The method of claim 6 , wherein each OIF block of the set of OIF blocks is independently accessible without affecting processing of other OIF blocks of the set of OIF blocks.
8. The method of claim 6 , wherein the TCB includes control information for processing replicated packets.
9. The method of claim 8 , wherein the control information includes one or more of header transformation control information, metering control information and statistics control information.
10. The method of claim 6 , wherein the second pointer associated with a first OIF block of the set of OIF blocks of a first {S, G} pair of the plurality of {S, G} pairs is permitted to point to and thus share a first TCB with another OIF block of the set of OIF blocks of the first {S, G} pair or with a second OIF block of the set of OIF blocks of a second (S, G} pair of the plurality of {S, G} pairs.
11. A method of managing multicast Internet Protocol (IP) sessions, the method comprising:
identifying, by a network device, active multicast IP sessions; and
maintaining, by the network device, a data structure within a memory of the network device containing therein information regarding the active multicast IP sessions;
wherein the data structure includes:
a plurality of pairs of a source field and a group field ({S, G} pairs), in which each pair of the plurality of {S, G} pairs defines a multicast IP session of the active multicast IP sessions, wherein the source field defines a source of a multicast transmission of the multicast IP session and the group field defines a group corresponding to the multicast IP session;
a first value associated with each of the plurality of {S, G} pairs that is indicative of a dynamically allocated set of outbound interface (OIF) blocks, wherein a number OIF blocks in the dynamically allocated set of OIF blocks is dependent upon a number of OIFs of the network device that are participating in the IP multicast session and the number of OIF blocks in the dynamically allocated set of OIF blocks defines a number of times packets of the IP multicast session are to be replicated;
a set of slots for each OIF block of the set of dynamically allocated OIF blocks, each slot of the set of slots having stored therein a second value indicative of a transmit control block (TCB) data structure which services one or more users participating in the IP multicast session and which has stored therein control information to process or route packets of the IP multicast session, including information regarding an OIF of the network device through which the packets are to be transmitted;
a third value associated with each OIF block of the set of dynamically allocated OIF blocks that links together the set of dynamically allocated OIF blocks and update only one OIF block of the OIF blocks responsive to users joining or leaving the IP multicast session.
12. The method of claim 11 , wherein each OIF block of the set of OIF blocks is independently accessible without affecting processing of other OIF blocks of the set of OIF blocks.
13. The method of claim 11 , wherein the TCB includes control information for processing replicated packets.
14. The method of claim 13 , wherein the control information includes one or more of header transformation control information, metering control information and statistics control information.
15. The method of claim 11 , wherein the second value associated with a first OIF block of the set of OIF blocks of a first {S, G} pair of the plurality of {S, G} pairs comprises a pointer and is permitted to point to and thus share a first TCB with another OIF block of the set of OIF blocks of the first {S, G} pair or with a second OIF block of the set of OIF blocks of a second (S, G} pair of the plurality of {S, G} pairs.
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/714,270 US9166805B1 (en) | 2004-09-24 | 2015-05-16 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/866,898 US9319303B2 (en) | 2004-09-24 | 2015-09-26 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US15/097,016 US10038567B2 (en) | 2004-09-24 | 2016-04-12 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
Applications Claiming Priority (6)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/949,943 US7499419B2 (en) | 2004-09-24 | 2004-09-24 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US12/328,858 US8213347B2 (en) | 2004-09-24 | 2009-02-12 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US13/015,880 US8369258B2 (en) | 2004-09-24 | 2011-01-28 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US13/756,071 US8953513B2 (en) | 2004-09-24 | 2013-01-31 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/616,521 US9167016B2 (en) | 2004-09-24 | 2015-02-06 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/714,270 US9166805B1 (en) | 2004-09-24 | 2015-05-16 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/616,521 Continuation US9167016B2 (en) | 2004-09-24 | 2015-02-06 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/866,898 Continuation US9319303B2 (en) | 2004-09-24 | 2015-09-26 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/866,989 Continuation US10303354B2 (en) | 2004-09-24 | 2015-09-27 | Devices and methods for navigating between user interfaces |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150280929A1 true US20150280929A1 (en) | 2015-10-01 |
US9166805B1 US9166805B1 (en) | 2015-10-20 |
Family
ID=38040735
Family Applications (9)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/949,943 Active 2025-04-19 US7499419B2 (en) | 2004-09-24 | 2004-09-24 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US12/328,858 Active 2025-07-02 US8213347B2 (en) | 2004-09-24 | 2009-02-12 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US12/467,304 Expired - Fee Related US7881244B2 (en) | 2004-09-24 | 2009-05-17 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US13/015,880 Active 2025-03-31 US8369258B2 (en) | 2004-09-24 | 2011-01-28 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US13/756,071 Expired - Fee Related US8953513B2 (en) | 2004-09-24 | 2013-01-31 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/616,521 Active 2024-11-24 US9167016B2 (en) | 2004-09-24 | 2015-02-06 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/714,270 Active US9166805B1 (en) | 2004-09-24 | 2015-05-16 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/866,898 Active US9319303B2 (en) | 2004-09-24 | 2015-09-26 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US15/097,016 Active 2025-01-18 US10038567B2 (en) | 2004-09-24 | 2016-04-12 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
Family Applications Before (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/949,943 Active 2025-04-19 US7499419B2 (en) | 2004-09-24 | 2004-09-24 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US12/328,858 Active 2025-07-02 US8213347B2 (en) | 2004-09-24 | 2009-02-12 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US12/467,304 Expired - Fee Related US7881244B2 (en) | 2004-09-24 | 2009-05-17 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US13/015,880 Active 2025-03-31 US8369258B2 (en) | 2004-09-24 | 2011-01-28 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US13/756,071 Expired - Fee Related US8953513B2 (en) | 2004-09-24 | 2013-01-31 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US14/616,521 Active 2024-11-24 US9167016B2 (en) | 2004-09-24 | 2015-02-06 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/866,898 Active US9319303B2 (en) | 2004-09-24 | 2015-09-26 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US15/097,016 Active 2025-01-18 US10038567B2 (en) | 2004-09-24 | 2016-04-12 | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
Country Status (1)
Country | Link |
---|---|
US (9) | US7499419B2 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107277810A (en) * | 2016-04-06 | 2017-10-20 | 阿瓦亚公司 | The mandate of smart phone antifraud and checking for secure interactive |
US10038567B2 (en) | 2004-09-24 | 2018-07-31 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
CN109981305A (en) * | 2019-03-19 | 2019-07-05 | 全链通有限公司 | Group communication method, equipment and computer readable storage medium |
US10742652B2 (en) | 2016-11-17 | 2020-08-11 | Avaya Inc. | Mobile caller authentication for contact centers |
Families Citing this family (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7111072B1 (en) * | 2000-09-13 | 2006-09-19 | Cosine Communications, Inc. | Packet routing system and method |
US7487232B1 (en) * | 2000-09-13 | 2009-02-03 | Fortinet, Inc. | Switch management system and method |
US7574495B1 (en) * | 2000-09-13 | 2009-08-11 | Fortinet, Inc. | System and method for managing interworking communications protocols |
US8250357B2 (en) | 2000-09-13 | 2012-08-21 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US7389358B1 (en) * | 2000-09-13 | 2008-06-17 | Fortinet, Inc. | Distributed virtual system to support managed, network-based services |
US7272643B1 (en) * | 2000-09-13 | 2007-09-18 | Fortinet, Inc. | System and method for managing and provisioning virtual routers |
US7181547B1 (en) | 2001-06-28 | 2007-02-20 | Fortinet, Inc. | Identifying nodes in a ring network |
US7161904B2 (en) * | 2002-06-04 | 2007-01-09 | Fortinet, Inc. | System and method for hierarchical metering in a virtual router based network switch |
US7177311B1 (en) | 2002-06-04 | 2007-02-13 | Fortinet, Inc. | System and method for routing traffic through a virtual router-based network switch |
US7116665B2 (en) * | 2002-06-04 | 2006-10-03 | Fortinet, Inc. | Methods and systems for a distributed provider edge |
US7203192B2 (en) | 2002-06-04 | 2007-04-10 | Fortinet, Inc. | Network packet steering |
US7376125B1 (en) | 2002-06-04 | 2008-05-20 | Fortinet, Inc. | Service processing switch |
US7096383B2 (en) * | 2002-08-29 | 2006-08-22 | Cosine Communications, Inc. | System and method for virtual router failover in a network routing system |
US7266120B2 (en) | 2002-11-18 | 2007-09-04 | Fortinet, Inc. | System and method for hardware accelerated packet multicast in a virtual routing system |
US7720095B2 (en) * | 2003-08-27 | 2010-05-18 | Fortinet, Inc. | Heterogeneous media packet bridging |
US7698456B2 (en) * | 2003-09-29 | 2010-04-13 | Cisco Technology, Inc. | Methods and apparatus to support routing of information |
US7808904B2 (en) | 2004-11-18 | 2010-10-05 | Fortinet, Inc. | Method and apparatus for managing subscriber profiles |
US20070115979A1 (en) * | 2004-11-18 | 2007-05-24 | Fortinet, Inc. | Method and apparatus for managing subscriber profiles |
US8089964B2 (en) | 2005-04-05 | 2012-01-03 | Cisco Technology, Inc. | Transporting multicast over MPLS backbone using virtual interfaces to perform reverse-path forwarding checks |
US20070097970A1 (en) * | 2005-11-01 | 2007-05-03 | Georgios Margaritis | Packet retransmitter |
US8934486B2 (en) * | 2006-03-16 | 2015-01-13 | Cisco Technology, Inc. | System and method for implementing multicast over a label-switched core network |
US7852826B2 (en) * | 2006-09-29 | 2010-12-14 | Intel Corporation | Techniques to communication MAP information elements in a wireless network |
US8392593B1 (en) * | 2007-01-26 | 2013-03-05 | Juniper Networks, Inc. | Multiple control channels for multicast replication in a network |
US8064446B2 (en) | 2007-08-24 | 2011-11-22 | At&T Intellectual Property I, L.P. | Multicast with adaptive dual-state |
CN100583997C (en) * | 2007-10-19 | 2010-01-20 | 深圳华为通信技术有限公司 | Service starting method, device and system of network television, and network television terminal |
US8739269B2 (en) * | 2008-08-07 | 2014-05-27 | At&T Intellectual Property I, L.P. | Method and apparatus for providing security in an intranet network |
US8713627B2 (en) * | 2008-08-14 | 2014-04-29 | Juniper Networks, Inc. | Scalable security services for multicast in a router having integrated zone-based firewall |
US8307422B2 (en) | 2008-08-14 | 2012-11-06 | Juniper Networks, Inc. | Routing device having integrated MPLS-aware firewall |
US8958310B2 (en) * | 2010-01-28 | 2015-02-17 | Hewlett-Packard Development Company, L.P. | Investigating quality of service disruptions in multicast forwarding trees |
US8995439B2 (en) | 2010-05-13 | 2015-03-31 | Comcast Cable Communications, Llc | Control of multicast content distribution |
CN102006244A (en) * | 2010-12-31 | 2011-04-06 | 重庆新媒农信科技有限公司 | Server and method for forwarding data requests |
WO2014177194A1 (en) * | 2013-04-30 | 2014-11-06 | Telefonaktiebolaget L M Ericsson (Publ) | Multicast group reuse in cellular network multicast transport |
US9604202B2 (en) | 2014-05-08 | 2017-03-28 | Eastman Chemical Company | Furan-2,5-dicarboxylic acid purge process |
US10229230B2 (en) * | 2015-01-06 | 2019-03-12 | International Business Machines Corporation | Simulating a large network load |
US9749221B2 (en) | 2015-06-08 | 2017-08-29 | International Business Machines Corporation | Multi-destination packet handling at overlay virtual network tunneling endpoints |
US10733144B2 (en) * | 2016-07-13 | 2020-08-04 | Netapp, Inc. | Persistent indexing and free space management for flat directory |
US10476879B2 (en) * | 2017-07-26 | 2019-11-12 | International Business Machines Corporation | Blockchain authentication via hard/soft token verification |
CN107888415B (en) * | 2017-11-03 | 2020-11-13 | 北京佳讯飞鸿电气股份有限公司 | Network management system data maintenance method |
KR102262962B1 (en) | 2018-02-14 | 2021-06-10 | 삼성전자주식회사 | A method and an electronic device providing a function or a content relating to an application |
CN110213304B (en) * | 2018-02-28 | 2021-11-30 | 成都高新信息技术研究院 | Block chain network interconnection method and system |
Family Cites Families (279)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4667287A (en) * | 1982-10-28 | 1987-05-19 | Tandem Computers Incorporated | Multiprocessor multisystem communications network |
US4590468A (en) | 1983-03-10 | 1986-05-20 | Western Digital Corporation | Token access controller protocol and architecture |
US4667323A (en) * | 1985-09-03 | 1987-05-19 | Allen-Bradley Company, Inc. | Industrialized token passing network |
US4726018A (en) * | 1986-08-25 | 1988-02-16 | International Business Machines Corporation | Method of providing priority access to a transmission communication ring |
US6453406B1 (en) * | 1990-10-17 | 2002-09-17 | Compaq Computer Corporation | Multiprocessor system with fiber optic bus interconnect for interprocessor communications |
AU1061892A (en) * | 1991-02-06 | 1992-08-13 | Fmc Corporation | Access to transmit on a message priority basis |
US5742760A (en) | 1992-05-12 | 1998-04-21 | Compaq Computer Corporation | Network packet switch using shared memory for repeating and bridging packets at media rate |
US5490252A (en) * | 1992-09-30 | 1996-02-06 | Bay Networks Group, Inc. | System having central processor for transmitting generic packets to another processor to be altered and transmitting altered packets back to central processor for routing |
US5371852A (en) | 1992-10-14 | 1994-12-06 | International Business Machines Corporation | Method and apparatus for making a cluster of computers appear as a single host on a network |
US6018771A (en) | 1992-11-25 | 2000-01-25 | Digital Equipment Corporation | Dynamic assignment of multicast network addresses |
US5955089A (en) * | 1993-04-20 | 1999-09-21 | Uab Research Foundation | Strain selection of pneumococcal surface proteins |
US5568525A (en) * | 1993-08-19 | 1996-10-22 | International Business Machines Corporation | System and method for connection of multiple protocol terminals |
US5581705A (en) * | 1993-12-13 | 1996-12-03 | Cray Research, Inc. | Messaging facility with hardware tail pointer and software implemented head pointer message queue for distributed memory massively parallel processing system |
KR100258137B1 (en) | 1993-12-30 | 2000-06-01 | 윤종용 | Improved Allocation Method and Apparatus for Virtual Path and Virtual Channel Recognizer in Asynchronous Transmission System |
US5745778A (en) * | 1994-01-26 | 1998-04-28 | Data General Corporation | Apparatus and method for improved CPU affinity in a multiprocessor system |
US5473599A (en) | 1994-04-22 | 1995-12-05 | Cisco Systems, Incorporated | Standby router protocol |
JPH07302236A (en) * | 1994-05-06 | 1995-11-14 | Hitachi Ltd | Information processing system, method therefor and service providing method in the information processing system |
US5491691A (en) | 1994-08-16 | 1996-02-13 | Motorola, Inc. | Method and apparatus for pacing asynchronous transfer mode (ATM) data cell transmission |
JP3307508B2 (en) * | 1994-09-01 | 2002-07-24 | 富士通株式会社 | Communication network configuration detection method |
US5812819A (en) | 1995-06-05 | 1998-09-22 | Shiva Corporation | Remote access apparatus and method which allow dynamic internet protocol (IP) address management |
US5987521A (en) | 1995-07-10 | 1999-11-16 | International Business Machines Corporation | Management of path routing in packet communications networks |
US6405262B1 (en) | 1995-07-14 | 2002-06-11 | Microsoft Corporation | Efficient inter-process object and interface pinging |
US6212556B1 (en) * | 1995-11-13 | 2001-04-03 | Webxchange, Inc. | Configurable value-added network (VAN) switching |
US5684800A (en) * | 1995-11-15 | 1997-11-04 | Cabletron Systems, Inc. | Method for establishing restricted broadcast groups in a switched network |
US5699347A (en) | 1995-11-17 | 1997-12-16 | Bay Networks, Inc. | Method and apparatus for routing packets in networks having connection-oriented subnetworks |
US6058307A (en) * | 1995-11-30 | 2000-05-02 | Amsc Subsidiary Corporation | Priority and preemption service system for satellite related communication using central controller |
EP0781068A1 (en) | 1995-12-20 | 1997-06-25 | International Business Machines Corporation | Method and system for adaptive bandwidth allocation in a high speed data network |
WO1997026735A1 (en) * | 1996-01-16 | 1997-07-24 | Raptor Systems, Inc. | Key management for network communication |
US6542502B1 (en) * | 1996-01-26 | 2003-04-01 | International Business Machines Corporation | Multicasting using a wormhole routing switching element |
US5892924A (en) * | 1996-01-31 | 1999-04-06 | Ipsilon Networks, Inc. | Method and apparatus for dynamically shifting between routing and switching packets in a transmission network |
CA2243359A1 (en) * | 1996-01-31 | 1997-08-07 | Ipsilon Networks, Inc. | Improved method and apparatus for dynamically shifting between routing and switching packets in a transmission network |
US5841973A (en) * | 1996-03-13 | 1998-11-24 | Cray Research, Inc. | Messaging in distributed memory multiprocessing system having shell circuitry for atomic control of message storage queue's tail pointer structure in local memory |
JPH09275400A (en) * | 1996-04-04 | 1997-10-21 | Hitachi Ltd | Atm exchange system |
US6085238A (en) | 1996-04-23 | 2000-07-04 | Matsushita Electric Works, Ltd. | Virtual LAN system |
US5881236A (en) | 1996-04-26 | 1999-03-09 | Hewlett-Packard Company | System for installation of software on a remote computer system over a network using checksums and password protection |
US6220768B1 (en) * | 1996-06-28 | 2001-04-24 | Sun Microsystems, Inc. | Network asset survey tool for gathering data about node equipment |
JPH1079740A (en) * | 1996-09-03 | 1998-03-24 | Hitachi Ltd | Router device using atm switch |
US6802068B1 (en) * | 1996-10-16 | 2004-10-05 | International Business Machines Corporation | Addressless internetworking |
US7145898B1 (en) | 1996-11-18 | 2006-12-05 | Mci Communications Corporation | System, method and article of manufacture for selecting a gateway of a hybrid communication system architecture |
US6169793B1 (en) * | 1996-12-24 | 2001-01-02 | Evolving Systems, Inc. | Systems and methods for providing order and service mediation for telecommunications systems |
US6098110A (en) * | 1996-12-30 | 2000-08-01 | Compaq Computer Corporation | Network switch with a multiple bus structure and a bridge interface for transferring network data between different buses |
US6260073B1 (en) * | 1996-12-30 | 2001-07-10 | Compaq Computer Corporation | Network switch including a switch manager for periodically polling the network ports to determine their status and controlling the flow of data between ports |
JP2842530B2 (en) | 1997-01-08 | 1999-01-06 | 日本電気株式会社 | ATM VLAN client-server system |
US6226296B1 (en) | 1997-01-16 | 2001-05-01 | Physical Optics Corporation | Metropolitan area network switching system and method of operation thereof |
US5964847A (en) * | 1997-03-10 | 1999-10-12 | International Business Machines Corporation | Mobile client computer interacting with docking device |
US6032193A (en) | 1997-03-20 | 2000-02-29 | Niobrara Research And Development Corporation | Computer system having virtual circuit address altered by local computer to switch to different physical data link to increase data transmission bandwidth |
US5875290A (en) * | 1997-03-27 | 1999-02-23 | International Business Machines Corporation | Method and program product for synchronizing operator initiated commands with a failover process in a distributed processing system |
CA2202572C (en) * | 1997-04-14 | 2004-02-10 | Ka Lun Eddie Law | A scaleable web server and method of efficiently managing multiple servers |
JP3575225B2 (en) | 1997-05-19 | 2004-10-13 | 株式会社日立製作所 | Packet switch, packet switching network, and packet switching method |
US6137777A (en) | 1997-05-27 | 2000-10-24 | Ukiah Software, Inc. | Control tool for bandwidth management |
US6260072B1 (en) * | 1997-06-12 | 2001-07-10 | Lucent Technologies Inc | Method and apparatus for adaptive routing in packet networks |
US6173399B1 (en) * | 1997-06-12 | 2001-01-09 | Vpnet Technologies, Inc. | Apparatus for implementing virtual private networks |
US6108699A (en) | 1997-06-27 | 2000-08-22 | Sun Microsystems, Inc. | System and method for modifying membership in a clustered distributed computer system and updating system configuration |
US7162738B2 (en) | 1998-11-03 | 2007-01-09 | Tumbleweed Communications Corp. | E-mail firewall with stored key encryption/decryption |
US7117358B2 (en) | 1997-07-24 | 2006-10-03 | Tumbleweed Communications Corp. | Method and system for filtering communication |
US20050081059A1 (en) * | 1997-07-24 | 2005-04-14 | Bandini Jean-Christophe Denis | Method and system for e-mail filtering |
US6069895A (en) * | 1997-08-29 | 2000-05-30 | Nortel Networks Corporation | Distributed route server |
US6256295B1 (en) * | 1997-09-25 | 2001-07-03 | Nortel Networks Limited | Method and apparatus for determining multiple minimally-overlapping paths between nodes in a network |
US6574661B1 (en) | 1997-09-26 | 2003-06-03 | Mci Communications Corporation | Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client |
US6381644B2 (en) * | 1997-09-26 | 2002-04-30 | Mci Worldcom, Inc. | Integrated proxy interface for web based telecommunications network management |
US6134315A (en) * | 1997-09-30 | 2000-10-17 | Genesys Telecommunications Laboratories, Inc. | Metadata-based network routing |
US6014669A (en) | 1997-10-01 | 2000-01-11 | Sun Microsystems, Inc. | Highly-available distributed cluster configuration database |
US6198751B1 (en) * | 1997-11-19 | 2001-03-06 | Cabletron Systems, Inc. | Multi-protocol packet translator |
US6339782B1 (en) * | 1997-11-21 | 2002-01-15 | International Business Machines Corporation | Persistence mechanism and method for objects |
US6266695B1 (en) * | 1997-12-23 | 2001-07-24 | Alcatel Usa Sourcing, L.P. | Telecommunications switch management system |
US6339595B1 (en) * | 1997-12-23 | 2002-01-15 | Cisco Technology, Inc. | Peer-model support for virtual private networks with potentially overlapping addresses |
KR100269146B1 (en) * | 1997-12-29 | 2000-10-16 | 윤종용 | Gateway device in atm-based access network |
US6047330A (en) * | 1998-01-20 | 2000-04-04 | Netscape Communications Corporation | Virtual router discovery system |
US6081508A (en) | 1998-02-25 | 2000-06-27 | Indus River Networks, Inc. | Remote computer communication |
US6175867B1 (en) * | 1998-03-23 | 2001-01-16 | Mci World Com, Inc. | System and method for managing networks addressed via common network addresses |
US6459682B1 (en) * | 1998-04-07 | 2002-10-01 | International Business Machines Corporation | Architecture for supporting service level agreements in an IP network |
US6343083B1 (en) | 1998-04-09 | 2002-01-29 | Alcatel Usa Sourcing, L.P. | Method and apparatus for supporting a connectionless communication protocol over an ATM network |
US6278708B1 (en) | 1998-04-10 | 2001-08-21 | Cisco Technology, Inc. | Frame relay access device with user-configurable virtual circuit bundling |
US6249519B1 (en) | 1998-04-16 | 2001-06-19 | Mantra Communications | Flow based circuit steering in ATM networks |
US6639897B1 (en) * | 1998-04-22 | 2003-10-28 | Nippon Telegraph And Telephone Corporation | Communication network of linked nodes for selecting the shortest available route |
US6269452B1 (en) | 1998-04-27 | 2001-07-31 | Cisco Technology, Inc. | System and method for fault recovery for a two line bi-directional ring network |
US6434619B1 (en) * | 1998-04-29 | 2002-08-13 | Alcatel Canada Inc. | Internet-enabled service management system and method |
US6317748B1 (en) * | 1998-05-08 | 2001-11-13 | Microsoft Corporation | Management information to object mapping and correlator |
WO1999066675A1 (en) * | 1998-06-19 | 1999-12-23 | Unisphere Solutions, Inc. | A quality of service facility in a device for performing ip forwarding and atm switching |
US6625650B2 (en) * | 1998-06-27 | 2003-09-23 | Intel Corporation | System for multi-layer broadband provisioning in computer networks |
US6269099B1 (en) * | 1998-07-01 | 2001-07-31 | 3Com Corporation | Protocol and method for peer network device discovery |
US6640248B1 (en) | 1998-07-10 | 2003-10-28 | Malibu Networks, Inc. | Application-aware, quality of service (QoS) sensitive, media access control (MAC) layer |
US6680922B1 (en) | 1998-07-10 | 2004-01-20 | Malibu Networks, Inc. | Method for the recognition and operation of virtual private networks (VPNs) over a wireless point to multi-point (PtMP) transmission system |
US6226788B1 (en) * | 1998-07-22 | 2001-05-01 | Cisco Technology, Inc. | Extensible network management system |
US6769124B1 (en) | 1998-07-22 | 2004-07-27 | Cisco Technology, Inc. | Persistent storage of information objects |
US6286038B1 (en) * | 1998-08-03 | 2001-09-04 | Nortel Networks Limited | Method and apparatus for remotely configuring a network device |
US6697360B1 (en) * | 1998-09-02 | 2004-02-24 | Cisco Technology, Inc. | Method and apparatus for auto-configuring layer three intermediate computer network devices |
US6438612B1 (en) | 1998-09-11 | 2002-08-20 | Ssh Communications Security, Ltd. | Method and arrangement for secure tunneling of data between virtual routers |
EP1116132A2 (en) * | 1998-09-22 | 2001-07-18 | Science Applications International Corporation | User-defined dynamic collaborative environments |
US6338092B1 (en) * | 1998-09-24 | 2002-01-08 | International Business Machines Corporation | Method, system and computer program for replicating data in a distributed computed environment |
US6920146B1 (en) * | 1998-10-05 | 2005-07-19 | Packet Engines Incorporated | Switching device with multistage queuing scheme |
US6397253B1 (en) | 1998-10-06 | 2002-05-28 | Bull Hn Information Systems Inc. | Method and system for providing high performance Web browser and server communications |
US6856676B1 (en) * | 1998-10-15 | 2005-02-15 | Alcatel | System and method of controlling and managing voice and data services in a telecommunications network |
US6493349B1 (en) | 1998-11-13 | 2002-12-10 | Nortel Networks Limited | Extended internet protocol virtual private network architectures |
US6324583B1 (en) * | 1998-11-17 | 2001-11-27 | International Business Machines Corp. | Method and apparatus for enabling communication between dissimilar protocol stacks |
US6608816B1 (en) | 1998-11-18 | 2003-08-19 | Nortel Networks Limited | Method and apparatus for providing differentiated services using a multi-level queuing mechanism |
US6614781B1 (en) * | 1998-11-20 | 2003-09-02 | Level 3 Communications, Inc. | Voice over data telecommunications network architecture |
US6466976B1 (en) * | 1998-12-03 | 2002-10-15 | Nortel Networks Limited | System and method for providing desired service policies to subscribers accessing the internet |
EP1142227A2 (en) | 1998-12-23 | 2001-10-10 | Nokia Wireless Routers, Inc. | A unified routing scheme for ad-hoc internetworking |
US6609153B1 (en) | 1998-12-24 | 2003-08-19 | Redback Networks Inc. | Domain isolation through virtual network machines |
US6134226A (en) * | 1998-12-31 | 2000-10-17 | Motorola, Inc. | Method and system for allocating a system resource to subscribers of a wireless communications system |
US6654787B1 (en) | 1998-12-31 | 2003-11-25 | Brightmail, Incorporated | Method and apparatus for filtering e-mail |
US6487666B1 (en) | 1999-01-15 | 2002-11-26 | Cisco Technology, Inc. | Intrusion detection signature analysis using regular expressions and logical operators |
US6449650B1 (en) * | 1999-02-01 | 2002-09-10 | Redback Networks Inc. | Methods and apparatus for deploying quality of service policies on a data communication network |
EP1153496B1 (en) | 1999-02-19 | 2011-01-19 | Nokia Siemens Networks Oy | Network arrangement for communication |
US7116679B1 (en) * | 1999-02-23 | 2006-10-03 | Alcatel | Multi-service network switch with a generic forwarding interface |
EP1171976A2 (en) | 1999-02-23 | 2002-01-16 | Alcatel Internetworking, Inc. | Multi-service network switch |
US6674756B1 (en) | 1999-02-23 | 2004-01-06 | Alcatel | Multi-service network switch with multiple virtual routers |
US6850531B1 (en) | 1999-02-23 | 2005-02-01 | Alcatel | Multi-service network switch |
US6192051B1 (en) * | 1999-02-26 | 2001-02-20 | Redstone Communications, Inc. | Network router search engine using compressed tree forwarding table |
US6246682B1 (en) * | 1999-03-05 | 2001-06-12 | Transwitch Corp. | Method and apparatus for managing multiple ATM cell queues |
JP3465620B2 (en) | 1999-03-17 | 2003-11-10 | 日本電気株式会社 | Virtual private network construction system |
US6658013B1 (en) * | 1999-03-23 | 2003-12-02 | Nortel Networks Limited | Method and apparatus for ensuring survivability of inter-ring traffic |
US7000014B2 (en) | 1999-04-02 | 2006-02-14 | Nortel Networks Limited | Monitoring a virtual private network |
US6839348B2 (en) | 1999-04-30 | 2005-01-04 | Cisco Technology, Inc. | System and method for distributing multicasts in virtual local area networks |
US6542515B1 (en) | 1999-05-19 | 2003-04-01 | Sun Microsystems, Inc. | Profile service |
US6807181B1 (en) | 1999-05-19 | 2004-10-19 | Sun Microsystems, Inc. | Context based control data |
US6542466B1 (en) | 1999-05-20 | 2003-04-01 | Motorola, Inc. | Communication network method and apparatus |
JP4110671B2 (en) | 1999-05-27 | 2008-07-02 | 株式会社日立製作所 | Data transfer device |
WO2000076152A1 (en) | 1999-06-03 | 2000-12-14 | Fujitsu Network Communications, Inc. | Method and system for transmitting traffic in a virtual tunnel of a transmission line |
JP3792940B2 (en) | 1999-06-10 | 2006-07-05 | 富士通株式会社 | Packet multicast delivery system |
US6694437B1 (en) | 1999-06-22 | 2004-02-17 | Institute For Information Technology | System and method for on-demand access concentrator for virtual private networks |
US6697359B1 (en) | 1999-07-02 | 2004-02-24 | Ancor Communications, Inc. | High performance switch fabric element and switch systems |
US7058716B1 (en) * | 1999-07-02 | 2006-06-06 | Covad Communications Group, Inc. | Automatic configuration and provisioning of virtual circuits for initial installation of high bandwidth connections |
US6938097B1 (en) | 1999-07-02 | 2005-08-30 | Sonicwall, Inc. | System for early packet steering and FIFO-based management with priority buffer support |
US6914907B1 (en) | 1999-08-05 | 2005-07-05 | Alcatel Canada Inc. | Method and apparatus for providing multi-cast transmissions using a distributed router |
US6597956B1 (en) * | 1999-08-23 | 2003-07-22 | Terraspring, Inc. | Method and apparatus for controlling an extensible computing system |
US6868082B1 (en) | 1999-08-30 | 2005-03-15 | International Business Machines Corporation | Network processor interface for building scalable switching systems |
US6532088B1 (en) * | 1999-09-10 | 2003-03-11 | Alcatel | System and method for packet level distributed routing in fiber optic rings |
EP1085711B1 (en) | 1999-09-20 | 2013-06-05 | Christian Prof. Dr. Tschudin | Method and apparatus for processing and forwarding data packets |
US6738371B1 (en) | 1999-09-28 | 2004-05-18 | Ericsson Inc. | Ingress data queue management in a packet data router |
US6597699B1 (en) | 1999-09-28 | 2003-07-22 | Telefonaktiebolaget Lm Ericsson (Publ) | Quality of service management in a packet data router system having multiple virtual router instances |
US6785691B1 (en) * | 1999-10-13 | 2004-08-31 | Avaya Technology Corp. | Object oriented processing system and data sharing environment for applications therein |
US6556544B1 (en) * | 1999-10-22 | 2003-04-29 | Nortel Networks Limited | Method and system for provisioning network resources for dynamic multicast groups |
US7046665B1 (en) | 1999-10-26 | 2006-05-16 | Extreme Networks, Inc. | Provisional IP-aware virtual paths over networks |
US7376827B1 (en) | 1999-11-05 | 2008-05-20 | Cisco Technology, Inc. | Directory-enabled network elements |
US6629128B1 (en) * | 1999-11-30 | 2003-09-30 | Recursion Software, Inc. | System and method for distributed processing in a computer network |
US7117530B1 (en) | 1999-12-07 | 2006-10-03 | Watchguard Technologies, Inc. | Tunnel designation system for virtual private networks |
US6775267B1 (en) * | 1999-12-30 | 2004-08-10 | At&T Corp | Method for billing IP broadband subscribers |
US6775284B1 (en) | 2000-01-07 | 2004-08-10 | International Business Machines Corporation | Method and system for frame and protocol classification |
JP2001202371A (en) | 2000-01-19 | 2001-07-27 | Sony Corp | Data communication system and receiver to be used therefor |
CN1426639A (en) | 2000-02-23 | 2003-06-25 | 金伯利R·皮科克 | Methods and apparatus for controlling internet protocol traffic in WAN and LAN |
US6496935B1 (en) | 2000-03-02 | 2002-12-17 | Check Point Software Technologies Ltd | System, device and method for rapid packet filtering and processing |
AU2001243597A1 (en) * | 2000-03-03 | 2001-09-17 | Radiant Logic, Inc. | System and method for providing access to databases via directories and other hierarchical structures and interfaces |
JP3765971B2 (en) * | 2000-03-06 | 2006-04-12 | 富士通株式会社 | Ring configuration method and its node device |
US20020019875A1 (en) * | 2000-03-20 | 2002-02-14 | Garrett John W. | Service selection in a shared access network |
US6980526B2 (en) * | 2000-03-24 | 2005-12-27 | Margalla Communications, Inc. | Multiple subscriber videoconferencing system |
US6631519B1 (en) * | 2000-03-30 | 2003-10-07 | Microsoft Corporation | Automated schema and interface generation |
US7096495B1 (en) * | 2000-03-31 | 2006-08-22 | Intel Corporation | Network session management |
US6954429B2 (en) | 2000-04-05 | 2005-10-11 | Dyband Corporation | Bandwidth control system |
US7028333B2 (en) | 2000-04-12 | 2006-04-11 | Corente, Inc. | Methods and systems for partners in virtual networks |
US7181766B2 (en) | 2000-04-12 | 2007-02-20 | Corente, Inc. | Methods and system for providing network services using at least one processor interfacing a base network |
US7215637B1 (en) * | 2000-04-17 | 2007-05-08 | Juniper Networks, Inc. | Systems and methods for processing packets |
US6701449B1 (en) * | 2000-04-20 | 2004-03-02 | Ciprico, Inc. | Method and apparatus for monitoring and analyzing network appliance status information |
US7062642B1 (en) | 2000-05-20 | 2006-06-13 | Ciena Corporation | Policy based provisioning of network device resources |
US20010048661A1 (en) | 2000-05-24 | 2001-12-06 | David Clear | Method and apparatus for multi-protocol redundant router protocol support |
US6732314B1 (en) | 2000-05-26 | 2004-05-04 | 3Com Corporation | Method and apparatus for L2TP forward error correction |
US6414595B1 (en) | 2000-06-16 | 2002-07-02 | Ciena Corporation | Method and system for processing alarm objects in a communications network |
FI20001574A (en) | 2000-06-30 | 2001-12-31 | Nokia Corp | Resource allocation and service forwarding over a wireless network |
US6728897B1 (en) * | 2000-07-25 | 2004-04-27 | Network Appliance, Inc. | Negotiating takeover in high availability cluster |
US6816462B1 (en) * | 2000-08-02 | 2004-11-09 | International Business Machines Corporation | System and method to determine connectivity of a VPN secure tunnel |
US6668282B1 (en) * | 2000-08-02 | 2003-12-23 | International Business Machines Corporation | System and method to monitor and determine if an active IPSec tunnel has become disabled |
US6424657B1 (en) | 2000-08-10 | 2002-07-23 | Verizon Communications Inc. | Traffic queueing for remote terminal DSLAMs |
US7216179B2 (en) | 2000-08-16 | 2007-05-08 | Semandex Networks Inc. | High-performance addressing and routing of data packets with semantically descriptive labels in a computer network |
US6883170B1 (en) | 2000-08-30 | 2005-04-19 | Aspect Communication Corporation | Method and system to maintain a hierarchy of instantiated application objects and to enable recovery from an applications failure |
US7149216B1 (en) * | 2000-09-05 | 2006-12-12 | Cisco Technology, Inc. | M-trie based packet processing |
US7263106B2 (en) | 2000-09-13 | 2007-08-28 | Fortinet, Inc. | System and protocol for frame relay service over the internet |
US7389358B1 (en) | 2000-09-13 | 2008-06-17 | Fortinet, Inc. | Distributed virtual system to support managed, network-based services |
US7174372B1 (en) | 2000-09-13 | 2007-02-06 | Fortinet, Inc. | System and method for managing router metadata |
US7487232B1 (en) | 2000-09-13 | 2009-02-03 | Fortinet, Inc. | Switch management system and method |
US7574495B1 (en) | 2000-09-13 | 2009-08-11 | Fortinet, Inc. | System and method for managing interworking communications protocols |
US7272643B1 (en) | 2000-09-13 | 2007-09-18 | Fortinet, Inc. | System and method for managing and provisioning virtual routers |
US8250357B2 (en) | 2000-09-13 | 2012-08-21 | Fortinet, Inc. | Tunnel interface for securing traffic over a network |
US7444398B1 (en) | 2000-09-13 | 2008-10-28 | Fortinet, Inc. | System and method for delivering security services |
US7111072B1 (en) | 2000-09-13 | 2006-09-19 | Cosine Communications, Inc. | Packet routing system and method |
US6822958B1 (en) * | 2000-09-25 | 2004-11-23 | Integrated Device Technology, Inc. | Implementation of multicast in an ATM switch |
US7293255B2 (en) | 2000-09-25 | 2007-11-06 | Sun Microsystems, Inc. | Apparatus and method for automated creation of resource types |
US20020066034A1 (en) | 2000-10-24 | 2002-05-30 | Schlossberg Barry J. | Distributed network security deception system |
US6665495B1 (en) | 2000-10-27 | 2003-12-16 | Yotta Networks, Inc. | Non-blocking, scalable optical router architecture and method for routing optical traffic |
US7313614B2 (en) | 2000-11-02 | 2007-12-25 | Sun Microsystems, Inc. | Switching system |
US7089293B2 (en) * | 2000-11-02 | 2006-08-08 | Sun Microsystems, Inc. | Switching system method for discovering and accessing SCSI devices in response to query |
US6985956B2 (en) * | 2000-11-02 | 2006-01-10 | Sun Microsystems, Inc. | Switching system |
KR100703499B1 (en) | 2000-12-09 | 2007-04-03 | 삼성전자주식회사 | Database structure for implementing traffic engineering function in multi protocol label switching system and constructing method thereof |
US20020075901A1 (en) | 2000-12-19 | 2002-06-20 | Bruce Perlmutter | Bandwidth management for tunneling servers |
US7131140B1 (en) | 2000-12-29 | 2006-10-31 | Cisco Technology, Inc. | Method for protecting a firewall load balancer from a denial of service attack |
US7155518B2 (en) | 2001-01-08 | 2006-12-26 | Interactive People Unplugged Ab | Extranet workgroup formation across multiple mobile virtual private networks |
US7054291B2 (en) | 2001-01-22 | 2006-05-30 | Telefonaktiebolaget Lm Ericsson (Publ) | Method of and system for mobile station abbreviated point-to-point protocol negotiation |
US7073200B2 (en) | 2001-01-24 | 2006-07-04 | Intel Corporation | Method of providing secure content-based user experience enhancement within a content protection architecture |
US7039720B2 (en) | 2001-01-25 | 2006-05-02 | Marconi Intellectual Property (Ringfence) , Inc. | Dense virtual router packet switching |
US7010715B2 (en) | 2001-01-25 | 2006-03-07 | Marconi Intellectual Property (Ringfence), Inc. | Redundant control architecture for a network device |
US7242665B2 (en) * | 2001-01-25 | 2007-07-10 | Ericsson Ab | Network device virtual interface |
US7159031B1 (en) | 2001-01-26 | 2007-01-02 | Fortinet, Inc. | Remote customer management of virtual routers allocated to the customer |
WO2002065290A1 (en) * | 2001-02-13 | 2002-08-22 | Candera, Inc. | Failover processing in a storage system |
US7225259B2 (en) * | 2001-02-21 | 2007-05-29 | Nokia Inc. | Service tunnel over a connectionless network |
US7042843B2 (en) * | 2001-03-02 | 2006-05-09 | Broadcom Corporation | Algorithm for time based queuing in network traffic engineering |
JP4481518B2 (en) | 2001-03-19 | 2010-06-16 | 株式会社日立製作所 | Information relay apparatus and transfer method |
US7269157B2 (en) | 2001-04-10 | 2007-09-11 | Internap Network Services Corporation | System and method to assure network service levels with intelligent routing |
JP3945297B2 (en) | 2001-04-24 | 2007-07-18 | 株式会社日立製作所 | System and management system |
US7325249B2 (en) | 2001-04-30 | 2008-01-29 | Aol Llc | Identifying unwanted electronic messages |
US7913261B2 (en) | 2001-05-02 | 2011-03-22 | nCipher Corporation, Ltd. | Application-specific information-processing method, system, and apparatus |
US6944168B2 (en) | 2001-05-04 | 2005-09-13 | Slt Logic Llc | System and method for providing transformation of multi-protocol packets in a data stream |
US7042848B2 (en) * | 2001-05-04 | 2006-05-09 | Slt Logic Llc | System and method for hierarchical policing of flows and subflows of a data stream |
US6922774B2 (en) * | 2001-05-14 | 2005-07-26 | The United States Of America As Represented By The National Security Agency | Device for and method of secure computing using virtual machines |
US7002965B1 (en) | 2001-05-21 | 2006-02-21 | Cisco Technology, Inc. | Method and apparatus for using ternary and binary content-addressable memory stages to classify packets |
US6952397B2 (en) | 2001-06-07 | 2005-10-04 | Corrigent Systems Ltd. | Communication in a bidirectional ring network with single-direction receiving |
US7020143B2 (en) | 2001-06-18 | 2006-03-28 | Ericsson Inc. | System for and method of differentiated queuing in a routing system |
ES2298178T3 (en) | 2001-06-21 | 2008-05-16 | T + T Oleochemie Gmbh | PROCEDURE FOR THE ENZYME DISOCIATION OF OILS AND FATS. |
US7181547B1 (en) | 2001-06-28 | 2007-02-20 | Fortinet, Inc. | Identifying nodes in a ring network |
US6940864B2 (en) | 2001-07-16 | 2005-09-06 | International Business Machines Corporation | Network access traffic sorter |
US7054311B2 (en) * | 2001-07-27 | 2006-05-30 | 4198638 Canada Inc. | Methods and apparatus for storage and processing of routing information |
US7369555B2 (en) | 2001-07-31 | 2008-05-06 | Telefonaktiebolaget Lm Ericsson (Publ) | Channel resource allocation arrangement and method |
US20030055920A1 (en) | 2001-09-17 | 2003-03-20 | Deepak Kakadia | Method and apparatus for automatic quality of service configuration based on traffic flow and other network parameters |
US7830787B1 (en) | 2001-09-25 | 2010-11-09 | Cisco Technology, Inc. | Flooding control for multicast distribution tunnel |
US7342917B2 (en) | 2001-10-02 | 2008-03-11 | Comverse, Inc. | Multimedia personalized call management (MPCM) |
US7316029B1 (en) * | 2001-10-25 | 2008-01-01 | Sprint Communications Company L.P. | Network security services architecture |
JP2003134160A (en) | 2001-10-25 | 2003-05-09 | Matsushita Electric Ind Co Ltd | Band guarantee system, repeater and network management server |
DE60109177T2 (en) | 2001-10-30 | 2005-07-28 | Alcatel | Forward IP packets for routing protocols |
US7320142B1 (en) | 2001-11-09 | 2008-01-15 | Cisco Technology, Inc. | Method and system for configurable network intrusion detection |
US6798773B2 (en) | 2001-11-13 | 2004-09-28 | Nokia, Inc. | Physically scoped multicast in multi-access networks |
CA2361971A1 (en) | 2001-11-14 | 2003-05-14 | Michael Gazier | A system and method for increasing the speed of activating dsl service |
US7484003B2 (en) | 2001-11-17 | 2009-01-27 | Redback Networks Inc. | Method and apparatus for multiple contexts and layer 3 virtual private networks |
US7379465B2 (en) | 2001-12-07 | 2008-05-27 | Nortel Networks Limited | Tunneling scheme optimized for use in virtual private networks |
US20030115308A1 (en) | 2001-12-19 | 2003-06-19 | Michael Best | Network management system architecture |
CA2365681A1 (en) | 2001-12-19 | 2003-06-19 | Alcatel Canada Inc. | System and method for managing information for elements in a communication network |
EP1331766A1 (en) | 2001-12-20 | 2003-07-30 | Alcatel | A telecommunications system employing virtual service network architecture |
US8688853B2 (en) * | 2001-12-21 | 2014-04-01 | Agere Systems Llc | Method and apparatus for maintaining multicast lists in a data network |
JP2003197897A (en) * | 2001-12-28 | 2003-07-11 | Fuji Film Microdevices Co Ltd | Semiconductor photoelectric transducer |
US6982987B2 (en) | 2002-01-10 | 2006-01-03 | Harris Corporation | Wireless communication network including data prioritization and packet reception error determination features and related methods |
US7246245B2 (en) | 2002-01-10 | 2007-07-17 | Broadcom Corporation | System on a chip for network storage devices |
US7801155B2 (en) | 2002-03-01 | 2010-09-21 | Verizon Business Global Llc | Resource allocation in virtual routers |
US20030174650A1 (en) | 2002-03-15 | 2003-09-18 | Broadcom Corporation | Weighted fair queuing (WFQ) shaper |
US20030185221A1 (en) | 2002-03-29 | 2003-10-02 | Alan Deikman | Network controller with shadowing of software routing tables to hardware routing tables |
US7197553B2 (en) | 2002-04-19 | 2007-03-27 | Nortel Networks Limited | Network system having a virtual-service-module |
US7082477B1 (en) * | 2002-04-30 | 2006-07-25 | Cisco Technology, Inc. | Virtual application of features to electronic messages |
US7221945B2 (en) * | 2002-05-03 | 2007-05-22 | Leapstone Systems, Inc. | System and method for establishing and controlling access to network resources |
US20030212735A1 (en) | 2002-05-13 | 2003-11-13 | Nvidia Corporation | Method and apparatus for providing an integrated network of processors |
US7376125B1 (en) | 2002-06-04 | 2008-05-20 | Fortinet, Inc. | Service processing switch |
US7203192B2 (en) | 2002-06-04 | 2007-04-10 | Fortinet, Inc. | Network packet steering |
US7161904B2 (en) * | 2002-06-04 | 2007-01-09 | Fortinet, Inc. | System and method for hierarchical metering in a virtual router based network switch |
US7187676B2 (en) | 2002-06-04 | 2007-03-06 | Sun Microsystems, Inc. | Apparatus and method for steering a communication to an open stream |
US7340535B1 (en) | 2002-06-04 | 2008-03-04 | Fortinet, Inc. | System and method for controlling routing in a virtual router system |
US7177311B1 (en) | 2002-06-04 | 2007-02-13 | Fortinet, Inc. | System and method for routing traffic through a virtual router-based network switch |
US7116665B2 (en) | 2002-06-04 | 2006-10-03 | Fortinet, Inc. | Methods and systems for a distributed provider edge |
US6625169B1 (en) | 2002-06-14 | 2003-09-23 | Telesys Technologies, Inc. | Integrated communication systems for exchanging data and information between networks |
US20040006601A1 (en) | 2002-07-01 | 2004-01-08 | Bernstein David B. | Method and system for optimized persistent messaging |
US20040019651A1 (en) | 2002-07-29 | 2004-01-29 | Andaker Kristian L. M. | Categorizing electronic messages based on collaborative feedback |
US7339929B2 (en) * | 2002-08-23 | 2008-03-04 | Corrigent Systems Ltd. | Virtual private LAN service using a multicast protocol |
US20040042416A1 (en) | 2002-08-27 | 2004-03-04 | Ngo Chuong Ngoc | Virtual Local Area Network auto-discovery methods |
US7096383B2 (en) | 2002-08-29 | 2006-08-22 | Cosine Communications, Inc. | System and method for virtual router failover in a network routing system |
US6959194B2 (en) | 2002-09-04 | 2005-10-25 | Cmg International B.V. | SMS-messaging |
US20040078772A1 (en) | 2002-10-16 | 2004-04-22 | Cosine Communications, Inc. | Dynamic route exchange |
AU2003301482A1 (en) | 2002-10-16 | 2004-05-04 | Rocksteady Networks, Inc. | System and method for dynamic bandwidth provisioning |
US7266120B2 (en) | 2002-11-18 | 2007-09-04 | Fortinet, Inc. | System and method for hardware accelerated packet multicast in a virtual routing system |
US7324489B1 (en) | 2003-02-18 | 2008-01-29 | Cisco Technology, Inc. | Managing network service access |
US7519057B2 (en) | 2003-02-18 | 2009-04-14 | Broadcom Corporation | System and method for communicating using a multiserver platform |
US7499398B2 (en) | 2003-04-16 | 2009-03-03 | International Business Machines Corporation | Method and system for oversubscribing bandwidth in a communications network |
US7831667B2 (en) * | 2003-05-15 | 2010-11-09 | Symantec Corporation | Method and apparatus for filtering email spam using email noise reduction |
US7386010B2 (en) | 2003-06-13 | 2008-06-10 | Corrigent Systems Ltd | Multiprotocol media conversion |
US7532640B2 (en) * | 2003-07-02 | 2009-05-12 | Caterpillar Inc. | Systems and methods for performing protocol conversions in a machine |
US7720095B2 (en) | 2003-08-27 | 2010-05-18 | Fortinet, Inc. | Heterogeneous media packet bridging |
US7839843B2 (en) * | 2003-09-18 | 2010-11-23 | Cisco Technology, Inc. | Distributed forwarding in virtual network devices |
US7698456B2 (en) | 2003-09-29 | 2010-04-13 | Cisco Technology, Inc. | Methods and apparatus to support routing of information |
US7586911B2 (en) * | 2003-10-17 | 2009-09-08 | Rmi Corporation | Method and apparatus for packet transmit queue control |
US20050113114A1 (en) * | 2003-11-26 | 2005-05-26 | Nokia Corporation | Method and apparatus to provide efficient routing of packets for a network initiated data session |
US20050147095A1 (en) * | 2003-12-30 | 2005-07-07 | Intel Corporation | IP multicast packet burst absorption and multithreaded replication architecture |
US7620041B2 (en) | 2004-04-15 | 2009-11-17 | Alcatel-Lucent Usa Inc. | Authentication mechanisms for call control message integrity and origin verification |
US7787863B2 (en) | 2004-05-24 | 2010-08-31 | Computer Associates Think, Inc. | System and method for automatically configuring a mobile device |
US7499419B2 (en) * | 2004-09-24 | 2009-03-03 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
US7916691B2 (en) | 2004-10-05 | 2011-03-29 | Telefonaktiebolaget L M Ericsson (Publ) | Arrangement and method relating to service provisioning control |
US20070115979A1 (en) | 2004-11-18 | 2007-05-24 | Fortinet, Inc. | Method and apparatus for managing subscriber profiles |
US7808904B2 (en) | 2004-11-18 | 2010-10-05 | Fortinet, Inc. | Method and apparatus for managing subscriber profiles |
US7831834B2 (en) * | 2005-03-14 | 2010-11-09 | Yahoo! Inc | Associating a postmark with a message to indicate trust |
US7293355B2 (en) | 2005-04-21 | 2007-11-13 | Endicott Interconnect Technologies, Inc. | Apparatus and method for making circuitized substrates in a continuous manner |
US7668920B2 (en) | 2006-03-01 | 2010-02-23 | Fortinet, Inc. | Electronic message and data tracking system |
US7545740B2 (en) | 2006-04-07 | 2009-06-09 | Corrigent Systems Ltd. | Two-way link aggregation |
US8077611B2 (en) | 2006-07-27 | 2011-12-13 | Cisco Technology, Inc. | Multilevel coupled policer |
US20080049760A1 (en) | 2006-08-24 | 2008-02-28 | Gilles Bergeron | Oversubscription in broadband network |
US20080112318A1 (en) | 2006-11-13 | 2008-05-15 | Rejean Groleau | Traffic shaping and scheduling in a network |
US9059940B2 (en) * | 2010-08-04 | 2015-06-16 | Alcatel Lucent | System and method for transport control protocol in a multi-chassis domain |
-
2004
- 2004-09-24 US US10/949,943 patent/US7499419B2/en active Active
-
2009
- 2009-02-12 US US12/328,858 patent/US8213347B2/en active Active
- 2009-05-17 US US12/467,304 patent/US7881244B2/en not_active Expired - Fee Related
-
2011
- 2011-01-28 US US13/015,880 patent/US8369258B2/en active Active
-
2013
- 2013-01-31 US US13/756,071 patent/US8953513B2/en not_active Expired - Fee Related
-
2015
- 2015-02-06 US US14/616,521 patent/US9167016B2/en active Active
- 2015-05-16 US US14/714,270 patent/US9166805B1/en active Active
- 2015-09-26 US US14/866,898 patent/US9319303B2/en active Active
-
2016
- 2016-04-12 US US15/097,016 patent/US10038567B2/en active Active
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10038567B2 (en) | 2004-09-24 | 2018-07-31 | Fortinet, Inc. | Scalable IP-services enabled multicast forwarding with efficient resource utilization |
CN107277810A (en) * | 2016-04-06 | 2017-10-20 | 阿瓦亚公司 | The mandate of smart phone antifraud and checking for secure interactive |
US10742652B2 (en) | 2016-11-17 | 2020-08-11 | Avaya Inc. | Mobile caller authentication for contact centers |
CN109981305A (en) * | 2019-03-19 | 2019-07-05 | 全链通有限公司 | Group communication method, equipment and computer readable storage medium |
Also Published As
Publication number | Publication date |
---|---|
US8953513B2 (en) | 2015-02-10 |
US20160226670A1 (en) | 2016-08-04 |
US9319303B2 (en) | 2016-04-19 |
US20150156234A1 (en) | 2015-06-04 |
US20110122872A1 (en) | 2011-05-26 |
US20090225754A1 (en) | 2009-09-10 |
US20130156033A1 (en) | 2013-06-20 |
US7881244B2 (en) | 2011-02-01 |
US20160020994A1 (en) | 2016-01-21 |
US9167016B2 (en) | 2015-10-20 |
US20100142527A1 (en) | 2010-06-10 |
US7499419B2 (en) | 2009-03-03 |
US20070110062A1 (en) | 2007-05-17 |
US8213347B2 (en) | 2012-07-03 |
US9166805B1 (en) | 2015-10-20 |
US8369258B2 (en) | 2013-02-05 |
US10038567B2 (en) | 2018-07-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10038567B2 (en) | Scalable IP-services enabled multicast forwarding with efficient resource utilization | |
US7877508B1 (en) | Method and system for intelligently forwarding multicast packets | |
US9338096B2 (en) | Multicast tree packing for multi-party video conferencing under SDN environment | |
US6570875B1 (en) | Automatic filtering and creation of virtual LANs among a plurality of switch ports | |
US8780899B2 (en) | Method and system for improving traffic distribution across a communication network | |
WO2021207922A1 (en) | Packet transmission method, device, and system | |
EP3179687B1 (en) | Network flow information statistics method and apparatus | |
JP2006005437A (en) | Traffic distributed control unit | |
US10567180B2 (en) | Method for multicast packet transmission in software defined networks | |
US20230379244A1 (en) | Ultra reliable segment routing | |
US6795441B1 (en) | Hierarchy tree-based quality of service classification for packet processing | |
WO2023116580A1 (en) | Path switching method and apparatus, network device, and network system | |
US8305918B2 (en) | Method of configuring the quality-of-service profile of a given stream at an access node of a packet communications network | |
EP4325800A1 (en) | Packet forwarding method and apparatus | |
US7339953B2 (en) | Surplus redistribution for quality of service classification for packet processing | |
CN114175583B (en) | System resource management in self-healing networks | |
EP2260612B1 (en) | Bandwidth signalling | |
US7602716B1 (en) | Load sharing on DOCSIS | |
US20120011235A1 (en) | Systems and Methods for Implementing Multiple ISIS Routing Instances on a Network Element | |
Hashim et al. | An approach to enhance aggregated source specific multicast scheme |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |