# US 2019/0173782 A1 · Multiple rstp domain separation

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0173782 A1
- Document ID: US20190173782A1
- Status: Published application
- Kind: A1
- Application number: 15/830,520
- Filed: 2017-12-04
- Published: 2019-06-06
- Earliest claimed: 2017-12-04
- Assignees: iS5 Communications Inc.
- Applicants: Is5 Communications Inc.
- Inventors: Tamer Soliman; Yuri Luskind; Kostya Belezko; Boris Tseitin
- Web page: https://patentgrep.com/patent/US20190173782A1

## CPC

- H04L 12/4645: {Details on frame tagging (routing of packets H04L45/00; support for virtual LAN H04L49/354)}
- H04L 12/42: Loop networks
- H04L 12/4625: {Single bridge functionality, e.g. connection of two networks over a single bridge}
- H04L 12/4637: {Interconnected ring systems}
- H04L 45/48: Routing tree calculation
- H04L 2012/421: {Interconnected ring systems}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

The present invention relates to electronic systems for use in high demand or mission critical environments, including power stations, sub-stations, roadside transportation, rail, and industrial applications. The present invention provides a) increased resilience of mission critical communications infrastructure b) ability to maintain multiple independent RSTP domains over HSR ring d) method of using a hidden VLAN as an RSTP domain ID c) a method of creating multiple redundant protocols domains over HSR ring.

## Claims

### Claim 1

A system for domain separation in a control plane of an L2 network having a plurality of network instances, the system comprising:
(a) a first ring network 101;
(b) a second network 103 having the plurality of network instances, each instance of the second network 103 connected to the first ring network 101 through a plurality of network devices 102 and generating at least one second network control frame 200 and each network device keeping the control plane of the first ring network 101 and the second network 102 separate while integrating the data plane of the first and second networks;
(c) each network device 102 receiving the at least one second network control frame 200 from each instance associated with the network device and assigning each of the at least one second network control frame 200 a second network domain ID and a control frame domain ID thereto by each network device 102, and releasing the second network control frame 200 with the control frame domain ID as a marked second network control frame 201 to be carried on the first ring network 101; and
wherein, when each network device 102 receives the marked second network control frame 201 from the first ring network 101 and where the control frame domain ID of the marked second network control frame 201 matches the control frame domain ID of the specific instance of the second network 103, the network device 102 releases the second network control frame 200 to the instance of the second network 103 associated with that control frame domain ID after removing the control frame domain ID from the marked second network control frame 201.

### Claim 2 (depends on 1)

The system of claim 1 wherein the plurality of network instances are distributed over one or more control domains of the second network 103.

### Claim 3 (depends on 2)

The system of claim 2 wherein at least two instances of the plurality of the network instances of the second network 103 belong to the same control domain.

### Claim 4 (depends on 2)

The system of claim 2 wherein the second network domain ID further comprises a frame tag.

### Claim 5 (depends on 3)

The system of claim 3 wherein the frame tag is attached, embedded or associated with the second network domain ID.

### Claim 6 (depends on 4)

The system of claim 4 wherein the frame tag is in a virtual container.

### Claim 7 (depends on 3)

The system of claim 3 wherein the second network control frame is a BPDU.

### Claim 8 (depends on 3)

The system of claim 3 wherein the first ring network is configured as an HSR ring.

### Claim 9 (depends on 3)

The system of claim 3 wherein the second network is configured as an STP/RSTP domain.

### Claim 10 (depends on 3)

The system of claim 3 wherein the network device is a HSR-DS device.

### Claim 11 (depends on 5)

The method of claim 5 wherein the virtual container is comprised of a hidden VLAN for control traffic, without impacting network traffic.

### Claim 12

A method for domain separation in a control plane of a L2 network having a plurality of network instances, the method comprising:
(a) connecting a first ring network 101 to a second network 103 having the plurality of network instances, each instance of the second network 103 connected to the first ring network 101 through a plurality of network devices 102;
(b) generating at least one second network control frame 200 and each network device keeping the control plane of the first ring network 101 and the second network 102 separate while integrating the data plane of the first and second networks;
(c) receiving the at least one second network control frame 200 from each instance associated with the network device from each network device 102 assigning each of the at least one second network control frame 200 a second network domain ID and a control frame domain ID upon releasing the second network control frame 200 with the control frame domain ID as a marked second network control frame 201 to be carried on the first ring network 101; and
wherein, when each network device 102 receives the marked second network control frame 201 from the first ring network 101 and where the control frame domain ID of the marked second network control frame 201 matches the control frame domain ID of the specific instance of the second network 103, the network device 102 releases the second network control frame 200 to the specific instance of the second network 103 after removing the control frame domain ID from the marked second network control frame 201.

### Claim 13 (depends on 12)

The method of claim 12 wherein the plurality of network instances are distributed over one or more control domains of the second network 103.

### Claim 14 (depends on 13)

The method of claim 13 wherein at least two instances of the plurality of the network instances of the second network 103 belong to the same control domain.

### Claim 15 (depends on 13)

The method of claim 13 wherein the second network domain ID further comprises a frame tag.

### Claim 16 (depends on 14)

The method of claim 14 wherein the frame tag is attached, embedded or associated with the second network domain ID.

### Claim 17 (depends on 14)

The method of claim 14 wherein the frame tag is in a virtual container.

### Claim 18 (depends on 14)

The method of claim 14 wherein the second network control frame is a BPDU.

### Claim 19 (depends on 14)

The method of claim 14 wherein the first ring network is configured as an HSR ring.

### Claim 20 (depends on 14)

The method of claim 14 wherein the second network is configured as an STP/RSTP domain.

### Claim 21 (depends on 14)

The method of claim 14 wherein each network device is configured as an HSR-DS device.

### Claim 22 (depends on 16)

The method of claim 16 wherein the virtual container is comprised of a hidden VLAN for control traffic, without impacting network traffic.

### Claim 23

A network device for domain separation in a control plane of an L2 network having a plurality of network instances, the device connecting a first network 101 to a second network 103, the second network having the plurality of network instances and comprising:
(a) a first port 150 for receiving at least one second network control frame 200 from each instance associated with the network device and having an Domain Separation logic function for assigning a control frame domain ID to each of the at least one second network control frame 200 prior to releasing through port 120 to port 110;
(b) a second port 110 for receiving a second network control frame with a control frame domain ID attached thereto 201;
(c) a third port 120 for receiving:
(i) from the second port 110, the at least one marked second network control frame having a control frame domain ID 201 and comparing the control frame domain ID with the control domain ID of the specific instance of the second network 103 to determine whether the control frame domain ID of the specific instance of the second network 103 matches the control frame ID of the at least one marked second network control frame and where the marked second network control frame 201 match, releasing the second network control frame without the control frame domain ID as an unmarked second network control frame 200 to be carried on the second network 103; and
(ii) from port 150, at least one second network control frame 200 from each instance associated with the network device and assigning a control frame domain ID to each of the at least one second network control frame 200 prior to releasing through port 120 to port 110 as per the Domain Separation Logic Function; and
(d) a forth port 160 acting as a virtual switch port.

### Claim 24 (depends on 23)

The device of claim 23 wherein the first network 101 is a HSR ring and port 120 is an interlink port.

### Claim 25 (depends on 24)

The device of claim 24 wherein the second network is a STP/RSTP domain.

### Claim 26 (depends on 23)

The device of claim 23 wherein at least two of the plurality of network instances of the second network 103 belong to the same control domain.

### Claim 27 (depends on 23)

The device of claim 23 wherein the second network domain ID further comprises a frame tag.

### Claim 28 (depends on 27)

The device of claim 27 wherein the frame tag is attached, embedded or associated with the second network domain ID.

### Claim 29 (depends on 27)

The device of claim 27 wherein the frame tag is in a virtual container.

### Claim 30 (depends on 23)

The device of claim 23 wherein the second network control frame is a BPDU.

### Claim 31 (depends on 30)

The device of claim 30 wherein the tag is embedded in the BPDU frame.

### Claim 32 (depends on 27)

The device of claim 27 wherein the BPDU tag is placed in the BPDU in a virtual container.

### Claim 33 (depends on 32)

The device of claim 32 wherein the virtual container is comprised of a hidden VLAN used on the HSR-DS devices for the purpose of domain separation without impacting network traffic.
