# US 2012/0250508 A1 · Method and System for Protection Group Switching

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

- Number: US 2012/0250508 A1
- Document ID: US20120250508A1
- Status: Published application
- Kind: A1
- Application number: 13/076,097
- Filed: 2011-03-30
- Published: 2012-10-04
- Earliest claimed: 2011-03-30
- Assignees: Fujitsu Network Communications, Inc.
- Inventors: Stephen J. Brolin
- Web page: https://patentgrep.com/patent/US20120250508A1

## CPC

- H04L 47/41: by acting on aggregated flows or links
- H04L 47/22: Traffic shaping
- H04L 47/32: by discarding or delaying data units, e.g. packets or frames
- Y02D 30/50: in wire-line communication networks, e.g. low power modes or reduced link rate
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

According to one embodiment, a method may include receiving a plurality of flows, the plurality of flows comprising a working group of flows received via a working path and a protection group of flows received via a protection path, marking each flow in the working group with a first class marker, marking each flow in the protection group with a second class marker, determining whether each of the working group and the protection group is an active group or an inactive group, determining whether each of the plurality of flows is in the active group or in the inactive group based on whether each of the plurality of flows is marked with the first class marker or the second class marker, dropping each flow in the inactive group, and passing each flow in the active group.

## Claims

### Claim 1

A method comprising:
receiving a plurality of flows, the plurality of flows comprising a working group of flows received via a working path and a protection group of flows received via a protection path;
marking each flow in the working group with a first class marker;
marking each flow in the protection group with a second class marker;
determining whether each of the working group and the protection group is an active group or an inactive group;
determining whether each of the plurality of flows is in the active group or in the inactive group based on whether each of the plurality of flows is marked with the first class marker or the second class marker;
dropping each flow in the inactive group; and
passing each flow in the active group.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
designating the protection group as the active group if a fault is detected on the working path; and
designating the working group as the active group if no fault is detected on the working path.

### Claim 3 (depends on 1)

The method of claim 1, wherein dropping each flow in the inactive group comprises discarding received frames of each flow in the inactive group.

### Claim 4 (depends on 1)

The method of claim 1, wherein passing each flow in the active group comprises communicating received frames of each flow in the active group to a traffic manager.

### Claim 5 (depends on 1)

The method of claim 1, wherein marking a flow comprises setting at least one bit in a metatag attached to a frame in the flow.

### Claim 6 (depends on 5)

The method of claim 5, wherein the metatag is a layer-three metatag.

### Claim 7 (depends on 5)

The method of claim 5, wherein:
marking a first flow in the working group with a first class marker comprises setting at least one bit in a first metatag attached to a first frame in the first flow to a first value; and
marking a second flow in the protection group with a second class marker comprises setting at least one bit in a second metatag attached to a second frame in the second flow to a second value.

### Claim 8

A switching element comprising:
an ingress marker module configured to:
receive a plurality of flows via a plurality of ports, the plurality of flows comprising a working group of flows received via a working path and a protection group of flows received via a protection path;
mark each flow in the working group with a first class marker; and
mark each flow in the protection group with a second class marker; and
an ingress logic engine configured to:
determine whether each of the working group and the protection group is an active group or an inactive group;
determine whether each of the plurality of flows is in the active group or in the inactive group based on whether each of the plurality of flows is marked with the first class marker or the second class marker;
drop each flow in the inactive group; and
pass each flow in the active group.

### Claim 9 (depends on 8)

The system of claim 8, wherein the switching element is further configured to:
designate the protection group as the active group if a fault is detected on the working path; and
designate the working group as the active group if no fault is detected on the working path.

### Claim 10 (depends on 8)

The system of claim 8, wherein the switching element is further configured to discard received frames of the each flow in the inactive group.

### Claim 11 (depends on 8)

The system of claim 8, wherein the switching element is further configured to communicate received frames of each flow in the active group to a traffic manager.

### Claim 12 (depends on 9)

The system of claim 9, wherein marking a flow comprises setting at least one bit in a metatag attached to a frame in the flow.

### Claim 13 (depends on 12)

The system of claim 12, wherein the metatag is a layer-three metatag otherwise unused in layer-two communication as defined by an Open Systems Interconnection (OSI) model.

### Claim 14 (depends on 12)

The system of claim 12, wherein:
marking a first flow in the working group with a first class marker comprises setting at least one bit in a first metatag attached to a first frame in the first flow to a first value; and
marking a second flow in the protection group with a second class marker comprises setting at least one bit in a second metatag attached to a second frame in the second flow to a second value.

### Claim 15

Logic embodied in non-transitory computer readable memory and operable, when executed, to:
receive a plurality of flows, the plurality of flows comprising a working group of flows received via a working path and a protection group of flows received via a protection path;
mark each flow in the working group with a first class marker;
mark each flow in the protection group with a second class marker;
determine whether each of the working group and the protection group is an active group or an inactive group;
determine whether each of the plurality of flows is in the active group or in the inactive group based on whether each of the plurality of flows is marked with the first class marker or the second class marker;
drop each flow in the inactive group; and
pass each flow in the active group.

### Claim 16 (depends on 15)

The logic of claim 15, wherein the logic is further operable, when executed, to:
designate the protection group as the active group if a fault is detected on the working path; and
designate the working group as the active group if no fault is detected on the working path.

### Claim 17 (depends on 15)

The logic of claim 15, wherein the logic is further operable, when executed, to discard received frames of the each flow in the inactive group.

### Claim 18 (depends on 15)

The logic of claim 15, wherein the logic is further operable, when executed, communicate received frames of each flow in the active group to a traffic manager.

### Claim 19 (depends on 15)

The logic of claim 15, wherein marking a flow comprises setting at least one bit in a metatag attached to a frame in the flow.

### Claim 20 (depends on 19)

The logic of claim 19, wherein the metatag is a layer-three metatag otherwise unused in layer-two communication as defined by an Open Systems Interconnection (OSI) model.

### Claim 21 (depends on 19)

The logic of claim 19, wherein:
marking a first flow in the working group with a first class marker comprises setting at least one bit in a first metatag attached to a first frame in the first flow to a first value; and
marking a second flow in the protection group with a second class marker comprises setting at least one bit in a second metatag attached to a second frame in the second flow to a second value.

### Claim 22

A method comprising:
receiving a plurality of flows grouped into a plurality of working groups and a plurality of corresponding protection groups;
marking each flow with a group-identifying class marker;
assigning an active or inactive status to each group, wherein each protection group has an opposite status as compared to its corresponding working group;
identifying each flow as active or inactive based on the class marker of each flow and the active or inactive status of each group;
dropping each inactive flow; and
passing each active flow.
