Source: https://patents.google.com/patent/US9553798B2/en
Timestamp: 2018-07-19 00:37:35
Document Index: 333764695

Matched Legal Cases: ['Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 14', 'art 11']

US9553798B2 - Method and system of updating conversation allocation in link aggregation - Google Patents
Method and system of updating conversation allocation in link aggregation Download PDF
US9553798B2
US9553798B2 US14135556 US201314135556A US9553798B2 US 9553798 B2 US9553798 B2 US 9553798B2 US 14135556 US14135556 US 14135556 US 201314135556 A US201314135556 A US 201314135556A US 9553798 B2 US9553798 B2 US 9553798B2
US14135556
US20140314095A1 (en )
This application claims priority to U.S. Provisional Patent Application No. 61/815,203, entitled “A Method and System of Updating Conversation Allocation in Link Aggregation,” U.S. Provisional Patent Application No. 61/815,200, entitled “A Method and System of Implementing Conversation-Sensitive Collection for A Link Aggregation Group,” filed on Apr. 23, 2013, and U.S. Provisional Patent Application No. 61/865,125, entitled “A Method and System of Updating Conversation Allocation in Link Aggregation,” filed on Aug. 12, 2013 respectively, which are incorporated by reference herein in their entirety.
This application is also related to co-pending U.S. Provisional Patent Application No. 61/815,204, entitled “A Method and System of Implementing Distributed Resilient Network Interconnect for a Link Aggregation Group,” filed on Apr. 23, 2013, co-pending U.S. Provisional Patent Application No. 61/839,022, entitled “A Method and System of Implementing Intra-Portal Link of Distributed Resilient Network Interconnect for a Link Aggregation Group,” filed on Jun. 25, 2013, co-pending U.S. Provisional Patent Application No. 61/865,126, entitled “A Method and System of Implementing Distributed Resilient Network Interconnect for a Link Aggregation Group,” filed on Aug. 12, 2013, co-pending U.S. Provisional Patent Application No. 61/900,284, entitled “A Method and System of Supporting Operator Commands in Link Aggregation Group,” filed on Nov. 5, 2013, and co-pending U.S. Provisional Patent Application No. 61/902,518, entitled “A Method and System of Implementing Distributed Resilient Network Interconnect for a Link Aggregation Group,” filed on Nov. 11, 2013, which are incorporated by reference herein in their entirety.
This application is also related to U.S. patent application Ser. No. 14/134,966, entitled “A Method and System of Implementing Conversation-Sensitive Collection for a Link Aggregation Group,” filed on Dec. 19, 2013, and U.S. Provisional Patent Application 61/918,610, entitled “A Method and System of Implementing Distributed Resilient Network Interconnect for a Link Aggregation Group,” filed on Dec. 19, 2013, which are incorporated by reference herein in their entirety.
As illustrated in FIG. 1A, link aggregation is a network configuration and process used to aggregate multiple links between a pair of nodes 120, 122 in the network to enable transmission of user data on each of the links participating in a Link Aggregation Group (LAG) 101 (see, e.g., Institute of Electrical and Electronics Engineers (IEEE) standard 802.1AX). Aggregating multiple network connections in this fashion can increase throughput beyond what a single connection can sustain, and/or can be used to provide resiliency in case of a failure of one of the links The “Distributed Resilient Network Interconnect” (DRNI) 102 (see Clause 8 of IEEE 802.1AX-REV/D1.0) specifies extensions to link aggregation in order to be able to use link aggregation on a network interface even between more than two nodes, for example between four nodes K, L, M and O as illustrated in FIG. 1B.
FIGS. 12A-C illustrate conversation mask-1 to mask-3 TLVs for an aggregation port according to one embodiment of the invention.
Internal Sublayer Service (ISS): An augmented version of the MAC service, defined in IEEE Std 802.1AC—2012.
Network devices are commonly separated into a control plane and a data plane (sometimes referred to as a forwarding plane or a media plane). In the case that the network device is a router (or is implementing routing functionality), the control plane typically determines how data (e.g., packets) is to be routed (e.g., the next hop for the data and the outgoing port for that data), and the data plane is in charge of forwarding that data. For example, the control plane typically includes one or more routing protocols (e.g., an exterior gateway protocol such as Border Gateway Protocol (BGP) (RFC 4271), Interior Gateway Protocol(s) (IGP) (e.g., Open Shortest Path First (OSPF) (RFC 2328 and 5340), Intermediate System to Intermediate System (IS-IS) (RFC 1142), Routing Information Protocol (RIP) (version 1 RFC 1058, version 2 RFC 2453, and next generation RFC 2080)), Label Distribution Protocol (LDP) (RFC 5036), Resource Reservation Protocol (RSVP) (RFC 2205, 2210, 2211, 2212, as well as RSVP-Traffic Engineering (TE): Extensions to RSVP for LSP Tunnels RFC 3209, Generalized Multi-Protocol Label Switching (GMPLS) Signaling RSVP-TE RFC 3473, RFC 3936, 4495, and 4558)) that communicate with other network devices to exchange routes and select those routes based on one or more routing metrics. In addition, the control plane also typically include ISO layer 2 control protocols such as Rapid Spanning Tree Protocol (RSTP), Multiple Spanning Tree Protocol (MSTP), and SPB (Shortest Path Bridging), which have been standardized by various standard bodies (e.g., SPB has been defined in IEEE Std 802.1aq—2012).
Network devices can also support native L2 network technologies and device types including VLAN bridged networks supported by C-VLAN bridges, provider bridges, provider backbone bridges, provider backbone bridges—traffic engineering (TE) (as defined in IEEE std 802.1ad—2005, IEEE std 802.1ah—2008, IEEE std 802.1aq/D2.1, IEEE std 802.1Q—2011) and similar technologies and network device types. The above listing of network device types and supported technologies is provided by way of example and not limitation. One skilled in the art would understand that other technologies, standards and device types can be included as network devices as used herein.
FIG. 2 is a diagram of one embodiment of Link Aggregation Sublayer 200. Aggregator client 202 communicates with a set of aggregation ports 292, 294, 296 through aggregator 250. In one embodiment, aggregator 250 presents a standard IEEE Std 802.1Q Internal Sublayer Service (ISS) interface to aggregator client 202. Aggregator 250 binds to one or more aggregation ports including aggregation Ports 292, 294, 296. Aggregator 250 distributes frame transmissions from aggregator client 202 to aggregation Ports 292, 294, 296, and to collect received frames from aggregation Ports 292, 294, 296 and pass them to aggregator client 202 transparently.
FIG. 12C illustrates conversation mask-3 TLV for an aggregation port according to one embodiment of the invention. Conversation mask-3 TLV 1220 also contains three fields, a TLV type 1222, conversation mask-3 length 1224, and port operation conversation mask-3 1226. These fields serve similar functions to the corresponding fields of Conversation mask-1 TLV 1210 respectively. In one example embodiment, the length of conversation mask-3 is 130 octets and the total length of the three combined port conversation masks is 512 octets. The first two conversation masks have included 384 octets (i.e., 192 octets each) for the port operation conversation mask, leaving only 130 octets needed for the third port conversation mask—to equal the size of the port conversation mask described herein above with reference to FIGS. 4A-C. Thus, one skilled in the art would understand that this alternate embodiment with three conversation mask TLVs can be used in place of a single TLV, further the TLV could be divided into any number of separate TLVs according to the same principles discussed here. Similarly, where embodiments are discussed herein with reference to utilizing a single conversation mask TLV, it would be understood that alternate embodiments with multiple conversation mask TLVs are also contemplated.
Once it is determined that the operational parameters (however, some of the parameters could be considered administrative parameters) of the network device and partner network device for the same link aggregation group are compatible and both declare long LACPDUs (may also be referred to as Version 2 LACPDUs), processing received conversation-sensitive information by long LACPDUs is possible. Each long LACPDU is over 128 octets in length. As discussed herein above, an enhanced LACPDU is needed to update conversation allocation information as a traditional LACPDU may support only up to 1024 conversations. Long LACPDUs are one embodiment of enhanced LACPDUs and other embodiments of enhanced LACPDUs are feasible in supporting the invention disclosed. Enhanced LACPDUs, in a general form, may carry control information needed to exchange conversation allocation information on links of link aggregation groups between a local network device and a partner network device. Some embodiments may not use long LACPDU, for example, when an implementation of LACP supports only no more than 1024 conversations. In other embodiment, long LACPDU is used. As each LACPDU is longer than 128 octets and it is able to support more conversations than traditional LACPDUs of 128 octets. For example, a long LACPDU may transmit a conversation mask TLV illustrated in FIG. 4A, which may indicate conversation allocation state of up to 4096 conversations. Long LACPDUs take more network resources to process and transmit, and it may not be efficient to allow their transmission at all time. Thus block 608 may set a timer to provide a time window for the network device to transmit long LACPDUs. Once the timer expires, the network device no longer transmits long LACPDUs and the process ends without updating conversation allocation. With the setting of timer for the long LACPDUs, the network device determines that operations through enhanced LACPDUs (long LACPDUs are utilized in this embodiment of the invention) are possible as described in block 303 of FIG. 3. Similar to block 305 of FIG. 3, process 600 flows to blocks 608-622 and update conversation state of an aggregation port.
FIG. 11 is a diagram of one embodiment of a network device implementing conversation-sensitive collection for the Link Aggregation Group in a network. The network device may process conversations wherein each conversation is for a service or an application in the network. The network device 1180 can implement a link aggregation sublayer 1170 as described herein above in regard to FIG. 2 and supports the link aggregation functions described herein above. The network device 1180 can include a network processor 1100, a set of ports 1140, a storage device 1150 and similar network device components. The components of the network device are provided by way of example and not limitation. The network device 1180 can implement the aggregation functions and the link aggregation sublayer 1170 using any number or type of processors and with any configuration. In other embodiments, the aggregation functions and link aggregation sublayer and related components are distributed over a set of network processors, a set of line cards and their constituent general purpose and application specific processor or similar implemented in a network device architecture.
Some terms have been changed between the present document and the priority documents for sake of clarity. However, all changes in terms have been with regard to equivalent terminology. A ‘data flow’ as used herein and the priority documents is understood to refer to an ordered sequence of frames, which is also equivalent to a ‘conversation.’ Reference has been made to a link aggregation group ‘level,’ which introduces a dichotomy between the ‘link level’ and the link aggregation group ‘level’ and stating that a conversation identifier identifies a conversation at a link aggregation group level is equivalent to indicating that the conversation identifier identifies the conversation at a given link aggregation group. Where ‘each frame’ of a set of frames received at a network device was recited, a particular ‘received frame’ is within this set of frames.
1. A method implemented by a network device for updating conversation allocation over links of a link aggregation group, wherein the network device is communicatively coupled with aggregation ports through the links of the link aggregation group, the method comprising:
verifying that an implementation of a conversation-sensitive link aggregation control protocol (LACP) is operational, wherein the conversation-sensitive LACP coordinates conversation-sensitive frame collection and distribution of the network device and a partner network device, and wherein the partner network device is a remote network device of the link aggregation group communicatively coupled with the network device;
determining that operations through enhanced link aggregation control protocol data units (LACPDUs) are possible, wherein the determination is based at least partially on a compatibility check between a first set of operational parameters of the network device and a second set of operational parameters of the partner network device; and
updating a first conversation allocation state of an aggregation port of the link aggregation group based on a determination that the first conversation allocation state is incorrect, wherein the first conversation allocation state indicates a first list of conversations transmitting through the aggregation port, and wherein updating the first conversation allocation state of the aggregation port of the link aggregation group includes:
receiving one or more enhanced LACPDUs from the partner network device indicating a partner conversation allocation state different from the first conversation allocation state; and
updating the first conversation allocation state through an updating function.
2. The method of claim 1, wherein verifying that the implementation of a conversation-sensitive LACP is operational comprises:
an identifier of an algorithm used to assign frames to port conversation identifiers at the partner network device;
a conversation identifier digest from the partner network device; and
a conversation service mapping digest from the partner network device.
3. The method of claim 1, wherein the compatibility check between the first set of operational parameters of the network device and the second set of operational parameters of the partner network device includes:
4. The method of claim 1, wherein the enhanced LACPDUs are long LACPDUs, and wherein each long LACPDU is over 128 octets in length.
5. The method of claim 1, wherein the first conversation allocation state of the aggregation port is represented by a conversation mask of the aggregation port.
6. The method of claim 5, wherein the conversation mask of the aggregation port is represented by one or more conversation mask Type/Length/Values (TLVs).
7. The method of claim 6, wherein a conversation mask TLV includes:
8. The method of claim 7, wherein the conversation mask state field contains one bit indicating whether a first conversation mask of the aggregation port of the network device and a second conversation mask of a matching aggregation port of the partner network device are consistent, wherein a collection conversation mask and a distribution conversation mask indicate lists of conversations collected in a collection function and distributed in a distribution function respectively.
9. The method of claim 7, wherein the port operation conversation mask field indicates the conversation allocation state of the aggregation port.
10. The method of claim 1, wherein the determination that the first conversation allocation state is incorrect is based on at least one of:
a determination that the first conversation allocation state of the aggregation port of the link aggregation group at the network device is different from a second conversation allocation state of the aggregation port received from the partner network device, wherein the second conversation allocation state indicates a second list of conversations received through the link aggregation group; and
a detection of a change of operational state or management configuration of the aggregation group at the network device, wherein the operational state is associated with each port of the aggregation group at the network device.
setting a timeout timer after the determination that the operations through the enhanced LACPDUs are possible, wherein the operations through the enhanced LACPDUs are inhabited after a timeout period.
12. The method of claim 1, wherein each conversation is for a service or an application in a network.
13. A network device configured to be communicatively coupled with aggregation ports through links of a link aggregation group, the network device comprising:
a network processor including:
an aggregation controller configured to verify that an implementation of a conversation-sensitive link aggregation control protocol (LACP) is operational, wherein the conversation-sensitive LACP coordinates conversation-sensitive frame collection and distribution of the network device and a partner network device, and wherein the partner network device is a remote network device of the link aggregation group communicatively coupled with the network device;
the aggregation controller further configured to determine operations through enhanced link aggregation control protocol data units (LACPDUs) are possible, wherein the determination is based on a compatibility check between a first set of operational parameters of the network device and a second set of operational parameters of the partner network device; and
the aggregation controller further configured to update a first conversation allocation state of an aggregation port of the link aggregation group based on a determination that the first conversation allocation state is incorrect, wherein the first conversation allocation state indicates a first list of conversations transmitting through the aggregation port, and wherein the update of the first conversation allocation state of the aggregation port of the link aggregation group includes: receipt of one or more enhanced LACPUDs from the partner network device indicating a partner conversation allocation state different from the first conversation allocation state, and update of the first conversation allocation state through an updating function.
a storage device configured to store conversation allocation states of the list of conversations transmitting through the aggregation port.
15. The network device of claim 13, wherein the network processor further including:
a link aggregation sublayer including:
a control parser and multiplexer configured to process LACPDUs and the frames from and transmit to aggregation ports of the link aggregation group;
a client interface configured to receive conversation-sensitive frames from and transmit toward the partner network device;
a frame distributor configured to distribute frames from the partner network devices toward the aggregation ports; and
a frame collector configured to collect frames from the aggregation ports toward the partner network device; and
an aggregator client configured to interact with the link aggregation sublayer to process frames.
16. The network device of claim 13, wherein the aggregation controller verifies that the implementation of a conversation-sensitive LACP is operational by:
17. The network device of claim 13, wherein the aggregation controller performs the compatibility check between the first set of operational parameters of the network device and the second set of operational parameters of the partner network device by:
18. The network device of claim 13, wherein the enhanced LACPDUs are long LACPDUs, wherein each long LACPDU is over 128 octets in length.
19. The network device of claim 13, wherein the first conversation allocation state of the aggregation port is represented by a conversation mask of the aggregation port.
20. The network device of claim 19, wherein the conversation mask of the aggregation port is represented by one or more conversation mask Type/Length/Values (TLVs).
21. The network device of claim 20, wherein a conversation mask TLV includes:
22. The network device of claim 21, wherein the conversation mask state field contains one bit indicating whether a first conversation mask of the aggregation port of the network device and a second conversation mask of a matching aggregation port of the partner network device are consistent, wherein a collection conversation mask and a distribution conversation mask indicate lists of conversations collected in a collection function and distributed in a distribution function of the aggregation port respectively.
23. The network device of claim 22, wherein the port operation conversation mask field indicates the conversation allocation state of the aggregation port.
24. The network device of claim 13, wherein the determination that the first conversation allocation state is incorrect is based on at least one of:
25. The network device of claim 13, wherein the link aggregation controller sets a timeout timer after the determination that the operations through enhanced LACPDUs are possible, wherein the operations through enhanced LACPDUs are inhabited after a timeout period.
26. The network device of claim 13, wherein each conversation is for a service or an application in a network.
27. A non-transitory computer-readable storage medium having instruction stored therein, which when executed by a processor, causes the processor to perform operations implemented by a network device for updating conversation allocation over links of a link aggregation group, wherein the network device is configured to be communicatively coupled with aggregation ports through the links of the link aggregation group, the operations comprising:
US14135556 2013-04-23 2013-12-19 Method and system of updating conversation allocation in link aggregation Active 2034-05-10 US9553798B2 (en)
US201361815200 true 2013-04-23 2013-04-23
US201361815203 true 2013-04-23 2013-04-23
US201361865125 true 2013-08-12 2013-08-12
US14135556 US9553798B2 (en) 2013-04-23 2013-12-19 Method and system of updating conversation allocation in link aggregation
EP20140714418 EP2989764A1 (en) 2013-04-23 2014-03-07 A method and system of updating conversation allocation in link aggregation
PCT/SE2014/050282 WO2014175804A1 (en) 2013-04-23 2014-03-07 A method and system of updating conversation allocation in link aggregation
CN 201480023171 CN105122749B (en) 2013-04-23 2014-03-07 Update session link assignment polymerization method and system
RU2015149846A RU2015149846A (en) 2013-04-23 2014-03-07 The method and system upgrade release dialogues aggregating links
US15402427 US20170142003A1 (en) 2013-04-23 2017-01-10 Method and system of updating conversation allocation in link aggregation
US15402427 Continuation US20170142003A1 (en) 2013-04-23 2017-01-10 Method and system of updating conversation allocation in link aggregation
US20140314095A1 true US20140314095A1 (en) 2014-10-23
US9553798B2 true US9553798B2 (en) 2017-01-24
ID=51728970
US14135556 Active 2034-05-10 US9553798B2 (en) 2013-04-23 2013-12-19 Method and system of updating conversation allocation in link aggregation
US15402427 Pending US20170142003A1 (en) 2013-04-23 2017-01-10 Method and system of updating conversation allocation in link aggregation
US (2) US9553798B2 (en)
EP (2) EP2989765A1 (en)
CN (2) CN105122748B (en)
RU (1) RU2015149846A (en)
WO (2) WO2014175805A1 (en)
US20160254960A1 (en) * 2015-02-26 2016-09-01 Cisco Technology, Inc. Automatic Discovery and Provisioning of Multi-Chassis Etherchannel Peers
US20060227711A1 (en) 2005-04-12 2006-10-12 Fujitsu Limited Purge mechanism in link aggregation group management
US20070150614A1 (en) 2005-12-23 2007-06-28 Nortel Networks Limited Method and apparatus for implementing filter rules in a network element
US20090073873A1 (en) 2007-09-17 2009-03-19 Integrated Device Technology, Inc. Multiple path switch and switching algorithms
US20090135838A1 (en) 2007-11-26 2009-05-28 Alcatel Lucent System and method for supporting link aggregation and other layer-2 protocols primarily over unidirectional links
US20090225752A1 (en) 2008-03-05 2009-09-10 Fujitsu Limited Apparatus and method for transferring frames through aggregated communication links
US20110075559A1 (en) 2009-09-30 2011-03-31 Fujitsu Limited Communication apparatus and frame transmission method
US20110200046A1 (en) 2010-02-17 2011-08-18 Toshiaki Kojima Communication apparatus, communication method, and computer program
WO2012065336A1 (en) 2010-11-15 2012-05-24 中兴通讯股份有限公司 Device-level redundancy protection method and system based on link aggregation control protocol
US20120233492A1 (en) 2011-03-10 2012-09-13 Cisco Technology, Inc. Transmitting network information using link or port aggregation protocols
US20120236859A1 (en) 2011-03-15 2012-09-20 Force10 Networks, Inc. Method & apparatus for configuring a link aggregation group on a stacked switch
WO2012142910A1 (en) 2011-04-21 2012-10-26 中兴通讯股份有限公司 Method and system for implementing elastic network interface and interconnection
US8422485B2 (en) 2005-11-07 2013-04-16 Samsung Electronics Co., Ltd Method and system for providing multimedia portal contents in communication system
US20130301427A1 (en) * 2012-05-08 2013-11-14 Cisco Technology, Inc. Grace state and pacing in link aggregation
US20140025736A1 (en) 2012-07-23 2014-01-23 Cisco Technology, Inc. System and method for cluster link aggregation control in a network environment
US20140226457A1 (en) 2013-02-13 2014-08-14 Canning Hsueh Enhanced retry method
US20140281669A1 (en) 2013-03-15 2014-09-18 International Business Machines Corporation OpenFlow Controller Master-slave Initialization Protocol
US20140314097A1 (en) 2013-04-23 2014-10-23 Telefonaktiebolaget L M Ericsson (Publ) Method and system for network and intra-portal link (ipl) sharing in distributed relay control protocol (drcp)
US20150124837A1 (en) 2013-11-05 2015-05-07 Telefonaktiebolaget L M Ericsson (Publ) Method and system of supporting operator commands in link aggregation group
US20150271088A1 (en) 2012-10-19 2015-09-24 Zte Corporation Method, device and system for bidirectional flow on same path in aggregation group
US20160065407A1 (en) * 2014-08-29 2016-03-03 Telefonaktiebolaget L M Ericsson (Publ) Method and system for supporting distributed relay control protocol (drcp) operations upon misconfiguration
CN100477601C (en) * 2005-04-12 2009-04-08 富士通株式会社 Characteristic identifying message for link aggregation marker protocol
CN101674208B (en) * 2009-10-28 2012-01-04 杭州华三通信技术有限公司 LACP MAD detection method and device thereof
US20150023351A1 (en) 2006-06-05 2015-01-22 Tellabs Operations, Inc. Method and apparatus for performing link aggregation
EP2701342A1 (en) 2011-04-21 2014-02-26 ZTE Corporation Method and system for implementing elastic network interface and interconnection
US20140112191A1 (en) 2012-03-02 2014-04-24 Telefonaktiebolagel L M Ericsson (publ) Technique for Ensuring Congruency in Link Aggregation
US20140317250A1 (en) 2013-04-23 2014-10-23 Telefonaktiebolaget L M Ericsson (Publ) Method and system for synchronizing with neighbor in a distributed resilient network interconnect (drni) link aggregation group
US20140313938A1 (en) 2013-04-23 2014-10-23 Telefonaktiebolaget L M Ericsson (Publ) Packet data unit (pdu) structure for supporting distributed relay control protocol (drcp)
US20140313939A1 (en) 2013-04-23 2014-10-23 Telefonaktiebolaget L M Ericsson (Publ) Method and system for synchronizing with neighbor in a distributed resilient network interconnect (drni) link aggregation group
"Draft Standard for Local and Metropolitan Area Networks-Link Aggregation; IEEE P802.1AX-Rev/D1.0", IEEE Draft, 802-1AX-REV-D1-0, Feb. 1, 2013, pp. 1-190, vol. 802.1, No. d1-0, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Draft Standard for Local and Metropolitan Area Networks-Link Aggregation; IEEE P802.1AX-REV/D3.1", IEEE Draft, 802-1AX-REV-D3-1, Dec. 20, 2013, pp. 1-138, vol. 802.1, No. d3-1, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Draft Standard for Local and Metropolitan Area Networks-Link Aggregation; IEEE P802.1AX-REV/D3.1", IEEE Draft, 802-1AX-REV-D3-1, Dec. 20, 2013, pp. 139-317, vol. 802.1, No. d3-1, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"IEEE Standard for Local and metropolitan area networks-Link Aggregation; IEEE Std 802.1AX-2008", IEEE Standard, Nov. 3, 2008, 162 pages, The Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation Control Protocol (LACP) (802.3ad) for Gigabit Interfaces", Cisco IOS Release 12.2(31)SB2, Mar. 1, 2007, pp. 1-18.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 1-25, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 129-148, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 149-170, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 171-199, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 26-47, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 48-68, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D0.5, Jan. 13, 2013, pp. 69-128, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D1.0, Feb. 1, 2013, 190 pages.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 1-25, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 129-148, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 149-170, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 171-199, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 26-47, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 48-68, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D0.5, Jan. 13, 2013, pp. 69-128, Institute of Electrical and Electronics Engineers, Inc., New York, NY, USA.
"Link Aggregation", Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D1.0, Feb. 1, 2013, 190 pages.
"Series G: Transmission Systems and Media, Digital Systems and Networks", Digital networks-Optical transport networks, Series Y: Global Information Infrastructure, Internet Protocol Aspects and Next-Generation Networks, ITU-T, G.870/Y.1352, Oct. 2012, 30 pages.
Ao, Ting, "Thinking on conversation-sensitive frame collection", IEEE Draft, AXREV-TINGA-LACP-Extension-1112-VO, Nov. 11, 2012, pp. 1-14, vol. 802.1, No. VO, IEEE-SA, Piscataway, NJ, USA.
Communication Pursuant to Article 94(3) EPC for Application No. 14 724 800.9, mailed Apr. 22, 2016, 7 pages.
Final Office Action, U.S. Appl. No. 14/167,155, mailed Jul. 22, 2016, 53 pages.
Final Office Action, U.S. Appl. No. 14/257,769, dated Apr. 26, 2016, 22 pages.
Final Office Action, U.S. Appl. No. 14/257,871, mailed Aug. 16, 2016, 42 pages.
Finn, "Diagrams to support ballots comments on 802.1AX-REV; axrev-nfinn-DRNI-diagrams-0312-v01", IEEE Draft, AXREV-NFINN-DRNI-Diagrams-0312-V01, Mar. 12, 2012, pp. 1-3, vol. 802.1, No. v01, IEEE-A, Piscataway, NJ, USA.
Haddock, "Rough Outline for a Intra-Portal Protocol Version 03", IEEE Draft; AXREV-Haddock-Rough-Intra-Portal-Protocol-0912-V03, Sep. 12, 2012, 12 pages, vol. 802.1, No. v03, IEEE-SA, Piscataway, NJ, USA.
IEEE 802.11, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications," Standard, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Mar. 29, 2012, 2793 pages.
IEEE 802.1AC-2012, "Media Access Control (MAC) Service Definition," Standard for Local and metropolitan area networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Sep. 14, 2012, 43 pages.
IEEE 802.1ad-2005, "Virtual Bridged Local Area Networks, Amendment 4: Provider Bridges," Standard for Local and metropolitan area networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), May 26, 2006, 74 pages.
IEEE 802.1ah-2008, "Virtual Bridged Local Area Networks, Amendment 7: Provider Backbone Bridges," Standard for Local and Metropolitan Area Networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Aug. 14, 2008, 121 pages.
IEEE 802.1Q-2011, "Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks," Institute of Electrical and Electronics Engineers, Inc. (IEEE), Aug. 31, 2011, 1365 pages.
IEEE 802.3-2012, "IEEE Standard for Internet," Section One, 634 pages; Section Two, 780 pages; Section Three, 358 pages; Section Four, 732 pages; Section Five, 844 pages; Section Six, 400 pages; Institute of Electrical and Electronics Engineers, Inc.; Dec. 28, 2012.
IEEE P802.1aq/D2.1, "Virtual Bridged Local Area Networks, Amendment 9: Shortest Path Bridging," Draft Standard for Local and Metropolitan Area Networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Aug. 21, 2009, 208 pages.
IEEE P802.1AX-REV/D0.3, "Link Aggregation," Draft Standard for Local and Metropolitan Area Networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Sep. 9, 2012, 183 pages.
IEEE P802.1AX-REV/D3.0, "Link Aggregation," Draft Standard for Local and Metropolitan Area Networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Sep. 24, 2013, 312 pages.
IEEE P802.1AX-REV-D4.3, "Link Aggregation," Draft Standard for Local and Metropolitan Area Networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Jul. 21, 2014, 320 pages.
IEEE P802.1AX-REV-D4.4b, "Link Aggregation," Draft Standard for Local and Metropolitan Area Networks, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Aug. 31, 2014, 329 pages.
IEEE P802.1Q-REV/D1.0, "Media Access Control (MAC) Bridges and Virtual Bridged Local Area Networks," Draft Standard, Institute of Electrical and Electronics Engineers, Inc. (IEEE), Apr. 23, 2013, 1791 pages.
International Preliminary Report on Patentability (Chapter I), Application No. PCT/SE2014/050177, mailed May 19, 2016, 9 pages.
International Preliminary Report on Patentability for Application No. PCT/SE2014/050282, mailed Jul. 27, 2015, 23 pages.
International Preliminary Report on Patentability, Application No. PCT/IB2014/060913, dated Aug. 4, 2015, 50 pages.
International Preliminary Report on Patentability, Application No. PCT/IB2014/060914, dated Aug. 4, 2015, 64 pages.
International Preliminary Report on Patentability, Application No. PCT/IB2014/060915, dated Jul. 30, 2015, 66 pages.
International Preliminary Report on Patentability, Application No. PCT/IB2014/060916, dated Aug. 4, 2015, 64 pages.
International Preliminary Report on Patentability, Application No. PCT/IB2014/060917, dated Aug. 4, 2015, 70 pages.
International Preliminary Report on Patentability, Application No. PCT/SE2014/050283, dated Jul. 1, 2015, 8 pages.
International Preliminary Report on Patentablility, Application No. PCT/IB2014/060912, dated Aug. 7, 2015, 64 pages.
International Search Report and Written Opinion, Application No. PCT/IB2014/060912, dated Aug. 28, 2014, 13 pages.
International Search Report and Written Opinion, Application No. PCT/IB2014/060913, dated Aug. 27, 2014, 14 pages.
International Search Report and Written Opinion, Application No. PCT/IB2014/060914, dated Aug. 27, 2014, 14 pages.
International Search Report and Written Opinion, Application No. PCT/IB2014/060915, dated Jul. 30, 2014, 13 pages.
International Search Report and Written Opinion, Application No. PCT/IB2014/060916, dated Jul. 31, 2014, 14 pages.
International Search Report and Written Opinion, Application No. PCT/IB2014/060917, dated Jul. 22, 2014, 14 pages.
International Search Report and Written Opinion, Application No. PCT/SE2014/050282, dated Jul. 29, 2014, 11 pages.
International Search Report, Application No. PCT/SE2014/050177, dated Jul. 14, 2014, 4 pages.
International Search Report, Application No. PCT/SE2014/050283, dated Jul. 21, 2014, 3 pages.
Link Aggregation, Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV(TM)/D3.1, Dec. 20, 2013, 317 pages.
Link Aggregation, Draft Standard for Local and Metropolitan Area Networks, IEEE P802.1AX-REV™/D3.1, Dec. 20, 2013, 317 pages.
Nigel Bragg; "Split Brain Detection 1; axbq-bragg-split-brain-detection-0912-v00", IEEE Draft, vol. 802.1, No. v00, Sep. 6, 2012, pp. 1-8.
Non-Final Office Action, U.S. Appl. No. 14/134,966, dated Jun. 17, 2015, 17 pages.
Non-Final Office Action, U.S. Appl. No. 14/134,966, dated Nov. 25, 2015, 18 pages.
Non-Final Office Action, U.S. Appl. No. 14/167,155, dated Dec. 4, 2015, 39 pages.
Non-Final Office Action, U.S. Appl. No. 14/257,252, dated Feb. 2, 2016, 41 pages.
Non-Final Office Action, U.S. Appl. No. 14/257,360, dated Jan. 13, 2016, 59 pages.
Non-Final Office Action, U.S. Appl. No. 14/257,637, dated Mar. 21, 2016, 44 pages.
Non-Final Office Action, U.S. Appl. No. 14/257,769, dated Dec. 8, 2015, 28 pages.
Non-Final Office Action, U.S. Appl. No. 14/257,859, dated Dec. 7, 2015, 61 pages.
Non-Final Office Action, U.S. Appl. No. 14/257,871, dated Mar. 16, 2016, 47 pages.
Notice of Allowance, U.S. Appl. No. 14/134,966, dated Jun. 17, 2016, 19 pages.
Notice of Allowance, U.S. Appl. No. 14/257,859, dated Jul. 11, 2016, 34 pages.
RFC 1058: Hedrick, "Routing Information Protocol," Network Working Group, Request for Comments, Jun. 1988, 33 pages.
RFC 1142: Oran, "OSI IS-IS Intra-domain Routing Protocol," Network Working Group, Request for Comments, Feb. 1990, 157 pages.
RFC 1180: Socolofsky, et al., "A TCP/IP Tutorial," Network Working Group, Request for Comments, Jan. 1991, 28 pages.
RFC 1321: Rivest, "The MD5 Message-Digest Algorithm," Network Working Group, Request for Comments, Apr. 1992, 20 pages.
RFC 2080: Malkin, et al., "RIPng for IPv6," Network Working Group, Request for Comments, Jan. 1997, 19 pages.
RFC 2205: Braden, et al., "Resource ReSerVation Protocol (RSVP)-Version 1 Functional Specification," Network Working Group, Request for Comments, Sep. 1997, 112 pages.
RFC 2210: Wroclawski, "The Use of RSVP with IETF Integrated Services," Network Working Group, Request for Comments, Sep. 1997, 33 pages.
RFC 2211: Wroclawski, "Specification of the Controlled-Load Network Element Service," Network Working Group, Request for Comments, Sep. 1997, 33 pages.
RFC 2212: Shenker, et al., "Specification of Guaranteed Quality of Service," Network Working Group, Request for Comments, Sep. 1997, 20 pages.
RFC 2328: Moy, "OSPF Version 2," Network Working Group, Request for Comments, The Internet Society, Apr. 1998, 244 pages.
RFC 2453: Malkin, "RIP Version 2," Network Working Group, Request for Comments, The Internet Society, Nov. 1998, 39 pages.
RFC 2460: Deering, et al., "Internet Protocol, Version 6 (IPv6) Specification," Network Working Group, Request for Comments, The Internet Society, Dec. 1998, 39 pages.
RFC 2474: Nichols, et al., "Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers," Network Working Group, Request for Comments, The Internet Society, Dec. 1998, 20 pages.
RFC 2475: Blake, et al., "An Architecture for Differentiated Services," Network Working Group, Request for Comments, The Internet Society, Dec. 1998, 36 pages.
RFC 2597: Heinanen, et al., "Assured Forwarding PHB Group," Network Working Group, Request for Comments, The Internet Society, Jun. 1999, 11 pages.
RFC 2675: Borman, et al., "IPv6 Jumbograms," Network Working Group, Request for Comments, The Internet Society, Aug. 1999, 9 pages.
RFC 2983: Black, "Differentiated Services and Tunnels," Network Working Group, Request for Comments, The Internet Society, Oct. 2000, 14 pages.
RFC 3086: Nichols, et al., "Definition of Differentiated Services Per Domain Behaviors and Rules for their Specification," Network Working Group, Request for Comments, The Internet Society, Apr. 2001, 24 pages.
RFC 3140: Black, et al., "Per Hop Behavior Identification Codes," Network Working Group, Request for Comments, The Internet Society, Jun. 2001, 8 pages.
RFC 3209: Awduche, et al., "RSVP-TE: Extensions to RSVP for LSP Tunnels," Network Working Group, Request for Comments, The Internet Society, Dec. 2001, 61 Pages.
RFC 3246: Davie, et al., "An Expedited Forwarding PHB (Per-Hop Behavior)," Network Working Group, Request for Comments, The Internet Society, Mar. 2002, 16 pages.
RFC 3247: Charny, et al., "Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior)," Network Working Group, Request for Comments, The Internet Society, Mar. 2002, 24 pages.
RFC 3260: Grossman, "New Terminology and Clarifications for Diffserv," Network Working Group, Request for Comments, The Internet Society, Apr. 2002, 10 pages.
RFC 3289: Baker, et al., "Management Information Base for the Differentiated Services Architecture," Network Working Group, Request for Comments, The Internet Society, May 2002, 116 pages.
RFC 3290: Bernet, et al., "An Informal Management Model for Diffserv Routers," Network Working Group, Request for Comments, The Internet Society, May 2002, 56 pages.
RFC 3317: Chan, et al., "Differentiated Services Quality of Service Policy Information Base," Network Working Group, Request for Comments, The Internet Society, Mar. 2003, 96 pages.
RFC 3473: Berger, "Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions," Network Working Group, Request for Comments, The Internet Society, Jan. 2003, 42 pages.
RFC 3936: Kompella, et al., "Procedures for Modifying the Resource reSerVation Protocol (RSVP)," Network Working Group, Request for Comments, The Internet Society, Oct. 2004, 7 pages.
RFC 4113: Fenner, et al., "Management Information Base for the User Datagram Protocol (UDP)," Network Working Group, Request for Comments, The Internet Society, Jun. 2005, 19 pages.
RFC 4271: Rekhter, et al., "A Border Gateway Protocol 4 (BGP-4)," Network Working Group, Request for Comments, The Internet Society, Jan. 2006, 104 pages.
RFC 4301: Kent, et al., "Security Architecture for the Internet Protocol," Network Working Group, Request for Comments, The Internet Society, Dec. 2005, 101 pages.
RFC 4309: Housley, et al., "Using Advanced Encryption Standard (AES) CCM Mode with IPsec Encapsulating Security Payload (ESP)," Network Working Group, Request for Comments, The Internet Society, Dec. 2005, 13 pages.
RFC 4495: Polk, et al., "A Resource Reservation Protocol (RSVP) Extension for the Reduction of Bandwidth of a Reservation Flow," Network Working Group, Request for Comments, The Internet Society, May 2006, 21 pages.
RFC 4558: Ali, et al., "Node-ID Based Resource Reservation Protocol (RSVP) Hello: A Clarification Statement," Network Working Group, Request for Comments, The Internet Society, Jun. 2006, 7 pages.
RFC 4594: Babiarz, et al., "Configuration Guidelines for DiffServ Service Classes," Network Working Group, Request for Comments, The Internet Society, Aug. 2006, 57 pages.
RFC 4761: Kompella, et al., "Virtual Private LAN Service (VPLS) Using BGP for Auto-Discovery and Signaling," Network Working Group, Request for Comments, The IETF Trust, Jan. 2007, 28 pages.
RFC 4762: Lasserre, et al., "Virtual Private LAN Service (VPLS) Using Label Distribution Protocol (LDP) Signaling," Network Working Group, Request for Comments, The IETF Trust, Jan. 2007, 31 pages.
RFC 5036: Andersson, et al., "LDP Specification," Network Working Group, Request for Comments, The IETF Trust, Oct. 2007, 135 pages.
RFC 5340: Coltun, et al., "OSPF for IPv6," Network Working Group, Request for Comments, The IETF Trust, Jul. 2008, 94 pages.
RFC 5405: Eggert, et al., "Unicast UDP Usage Guidelines for Application Designers," Network Working Group, Request for Comments, IETF Trust and the persons identified as the document authors, Nov. 2008, 27 pages.
RFC 5865: Baker, et al., "A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic," Internet Engineering Task Force (IETF), Request for Comments, IETF Trust and the persons identified as the document authors, May 2010, 14 pages.
RFC 793: "Transmission Control Protocol, DARPA Internet Program Protocol Specification," Network Working Group, Request for Comments, Sep. 1981, 91 pages.
RFC: 768: Postel, "User Datagram Protocol," Network Working Group, Request for Comments, Aug. 28, 1980, 3 pages.
Saltsidis, Panagiotis, "802.1AX-REV-Link Aggregation Revision", Jul. 13, 2013, 17 pages, Joint IEEE-SA and ITU Workshop on Ethernet, Geneva, Switzerland.
Written Opinion of the Interational Preliminary Examining Authority, Application No. PCT/IB2014/060915, dated Apr. 8, 2015, 8 pages.
Written Opinion of the International Preliminary Examining Authority, Application No. PCT/IB2014/060912, dated Mar. 30, 2015, 8 pages.
Written Opinion of the International Preliminary Examining Authority, Application No. PCT/IB2014/060913, dated Apr. 2, 2015, 10 pages.
Written Opinion of the International Preliminary Examining Authority, Application No. PCT/IB2014/060916, dated Apr. 1, 2015, 8 pages.
Written Opinion of the International Preliminary Examining Authority, Application No. PCT/SE2014/050282, dated May 6, 2015, 5 pages.
Written Opinion of the International Preliminary Examining Authority, Application No. PCT/SE2014/050283, dated Jul. 21, 2014, 7 pages.
Written Opinion of the International Preliminary Examining Authroity, Application No. PCT/IB2014/060914, dated Mar. 30, 2015, 10 pages.
Written Opinion of the International Preliminary Examining Authroity, Application No. PCT/IB2014/060917, dated Apr. 8, 2015, 11 pages.
Written Opinion, Application No. PCT/SE2014/050177, dated Jul. 14, 2014, 8 pages.
Written Opinion, Application No. PCT/SE2014/050283, dated Jul. 21, 2014, 6 pages.
Yuehua, Wei, "Establish/Maintain a Portal and Distributed Relay," IEEE 802 plenary, San Antonio, Nov. 2012, 9 pages.
RU2015149846A (en) 2017-05-26 application
RU2639692C2 (en) grant
CN105122749A (en) 2015-12-02 application
WO2014175804A1 (en) 2014-10-30 application
US20140314095A1 (en) 2014-10-23 application
CN105122748A (en) 2015-12-02 application
WO2014175805A1 (en) 2014-10-30 application
EP2989765A1 (en) 2016-03-02 application
CN105122748B (en) 2018-06-01 grant
EP2989764A1 (en) 2016-03-02 application
US20170142003A1 (en) 2017-05-18 application
CN105122749B (en) 2018-06-01 grant
US20060203820A1 (en) 2006-09-14 Method and system for communicating and isolating packetized data through a plurality of last-mile carriers to form a multi-node intranet
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SALTSIDIS, PANAGIOTIS;FARKAS, JANOS;GEROE, BALAZS PETER;REEL/FRAME:032586/0866