Method and system for network and intra-portal link (IPL) sharing in distributed relay control protocol (DRCP)

• US 10,116,498 B2
• Filed: 09/14/2016
• Issued: 10/30/2018
• Est. Priority Date: 04/23/2013
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Saltsidis, Panagiotis
• Primary Examiner(s): Liu, Siming
• Application Number:
  US15/265,292
• Publication Number:
  US 20170063726A1
• Time in Patent Office: 776 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 2012/5652 Cell construction, e.g. including header, packetisation, depacketisation, assembly, reassembly
• CPC Class Codes: H04L 2212/00 Encapsulation of packets
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0659 by isolating or reconfiguring faulty entities
• CPC Class Codes: H04L 41/0668 by dynamic selection of recovery network elements, e.g. replacement by the most appropriate element after failure
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0813 characterised by the conditions triggering a change of settings
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/082 the condition being updates or upgrades of network functionality
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element
• CPC Class Codes: H04L 41/342 between virtual entities, e.g. orchestrators, SDN or NFV entities
• CPC Class Codes: H04L 41/344 Out-of-band transfers
• CPC Class Codes: H04L 43/065 related to network devices
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/46 : Cluster building
• CPC Class Codes: H04L 49/253 : using establishment or release of connections between ports
• CPC Class Codes: H04L 49/354 : for supporting virtual local area networks [VLAN]
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 69/03 : Protocol definition or specification protocol conformance testing H04L1/244
• CPC Class Codes: H04L 69/324 : in the data link layer [OSI layer 2], e.g. HDLC
• CPC Class Codes: Y02D 30/50 : in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

A method supporting network and intra-portal link (IPL) sharing in a link aggregation group at a network device is disclosed. The method starts with transmitting frames on the IPL at the network device, where the physical link or aggregation link of the link aggregation group is dedicated to the IPL. The network device determines that the network device is configured with a network and IPL sharing method that is consistent with the neighbor network device, the network and IPL sharing method including sharing by at least one of time, tag, and encapsulation, where the network and IPL sharing method indicates sharing of the physical link or link aggregation between frames for the IPL and frames for another IPL or a network link of the link aggregation group. Then the network device transmits the frames between the network device and the neighbor network device using the network and IPL sharing method.

Claims

1. A method supporting network and intra-portal link (IPL) sharing in a link aggregation group at a network device, wherein the network device and a neighbor network device are included in a portal of the link aggregation group, wherein the network device is coupled to the neighbor network device via an intra-portal port (IPP) using an IPL that is a logical point-to-point link between the network device and the neighbor network device, the method comprising:

receiving a first type/length/value (TLV) message transmitted from the neighbor network device;

determining that the network device is configured with a network and IPL sharing method consistent with that of the neighbor network device, wherein the determining includes;

comparing a recorded neighbor network and IPL sharing method received from the first TLV message with a home network and IPL sharing method of the network device; and

transmitting frames between the network device and the neighbor network device using the network and IPL sharing method.

2. The method of claim 1, wherein the network and IPL sharing method including at least one of:

network and IPL sharing by time,

network and IPL sharing by tag, and

network and IPL sharing by encapsulation.

3. The method of claim 1, wherein the first TLV message is included in a distributed relay control protocol data unit (DRCPDU).

4. The method of claim 1, wherein the first TLV message includes a first field indicating a type of the first TLV message being for network and IPL sharing method, a second field indicating a network and IPL sharing method, wherein a value of one in the second field indicates network and IPL sharing by time is used, and wherein a value of two in the second field indicates network and IPL sharing by tag is used.

5. The method of claim 1, wherein the determining that the network device is configured with a network and IPL sharing method that is consistent with the neighbor network device further includes:

comparing a recorded neighbor network and IPL sharing encapsulation received from the neighbor network device with a home network and IPL sharing encapsulation of the network device.

6. The method of claim 5, wherein the recorded neighbor network and IPL sharing encapsulation is received from a second TLV message transmitted from the neighbor network device, and wherein the second TLV message includes a field indicating a type of the second TLV message being network and IPL sharing encapsulation.

7. The method of claim 6, wherein the second TLV message includes a field containing a digest computed from a sequence of identifiers representing frames associated with gateway conversation identifiers for an encapsulation method.

8. The method of claim 6, wherein the second TLV message includes a field indicating a digest computed from a sequence of identifiers representing translated values of identifiers used for frames associated with gateway conversation identifiers when the neighbor'"'"'s network and IPL sharing method is sharing by tag.

9. The method of claim 1, further comprising:

determining that the network device no longer uses the network and IP sharing method consistent with that of the neighbor network device; and

transmitting frames on the IPL, wherein a physical link or link aggregation of the link aggregation group is dedicated to the IPL.

10. The method of claim 1, further comprising:

prior to receiving the first TLV message, transmitting frames on the IPL over a dedicated physical link or link aggregation of the link aggregation group.

11. A network device supporting network and intra-portal link (IPL) sharing in a link aggregation group, wherein the network device and a neighbor network device are included in a portal of the link aggregation group, wherein the network device is coupled to the neighbor network device via an intra-portal port (IPP) using an IPL that is a logical point-to-point link between the network device and the neighbor network device, the network device comprising:

ports coupled to one or more physical or aggregation links of the link aggregation group; and

a processor coupled to the ports, executing a distributed resilient network interconnect (DRNI) function, the DRNI function being operative to receive a first type/length/value (TLV) message transmitted from the neighbor network device, determine that the network device is configured with a network and IPL sharing method that is consistent with the neighbor network device, wherein the determination is to include to compare a recorded neighbor network and IPL sharing method received from the first TLV message with a home network and IPL sharing method of the network device, and further operative to cause transmission of frames between the network device and the neighbor network device using the network and IPL sharing method.

12. The network device of claim 11, wherein the network and IPL sharing method including at least one of:

network and IPL sharing by time,

network and IPL sharing by tag, and

network and IPL sharing by encapsulation.

13. The network device of claim 11, wherein the first TLV message is included in a distributed relay control protocol data unit (DRCPDU).

14. The network device of claim 11, wherein the first TLV message includes a first field indicating a type of the first TLV message being for network and IPL sharing method, a second field indicating a network and IPL sharing method, wherein a value of one in the second field indicates network and IPL sharing by time is used, and wherein a value of two in the second field indicates network and IPL sharing by tag is used.

15. The network device of claim 11, where the determination that the network device is configured with a network and IPL sharing method that is consistent with the neighbor network device is further to:

compare a recorded neighbor network and IPL sharing encapsulation received from the neighbor network device with a home network and IPL sharing encapsulation of the network device.

16. The network device of claim 15, wherein the recorded neighbor network and IPL sharing encapsulation is received from a second TLV message transmitted from the neighbor network device, and wherein the second TLV message includes a field indicating a type of the second TLV message being network and IPL sharing encapsulation.

17. The network device of claim 16, wherein the second TLV message includes a field containing a digest computed from a sequence of identifiers representing frames associated with gateway conversation identifiers for an encapsulation method.

18. The network device of claim 16, wherein the second TLV message includes a field indicating a digest computed from a sequence of identifiers representing translated values of identifiers used for frames associated with gateway conversation identifiers when the neighbor'"'"'s network and IPL sharing method is sharing by tag.

19. The network device of claim 11, the DRNI function being further operative to:

determine that the network device no longer uses the network and IP sharing method consistent with that of the neighbor network device, and

transmit frames on the IPL, wherein the physical link or link aggregation of the link aggregation group is dedicated to the IPL.

20. The network device of claim 11, the DRNI function being further operative to:

prior to receipt of the first TLV message, transmit frames on the IPL over a dedicated physical link or link aggregation of the link aggregation group.