> For the complete documentation index, see [llms.txt](https://www.opal-rt.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/iec-61850-8-1-goose.md).

# IEC 61850-8-1 GOOSE

## Introduction to IEC 61850‑8‑1 GOOSE

IEC 61850‑8‑1 GOOSE (Generic Object Oriented Substation Event) is the standard mechanism for high‑speed, peer‑to‑peer event communication in digital substations. It enables protection relays, breakers, and automation IEDs to exchange real‑time status changes, such as trips, interlocking signals, or blocking conditions, with deterministic low latency. GOOSE messages are mapped directly onto Layer‑2 multicast Ethernet frames, allowing fast delivery without TCP/IP overhead. They are used extensively in protection schemes, substation automation, and any application requiring millisecond‑grade event transfer.

## Protocol characteristics

* **Publisher/Subscriber Architecture**\
  GOOSE uses a decentralized **publisher/subscriber** model, where an IED publishes event datasets onto a multicast Ethernet MAC address, and any subscribing IED on the VLAN can receive them. There is no master device: communication is peer‑to‑peer and event‑driven.
* **Event‑Driven State Changes**\
  Instead of periodic polling, GOOSE frames are sent immediately when a dataset value changes (e.g., breaker open/close, protection trip). A fast retransmission scheme repeats messages at decreasing intervals to ensure deterministic delivery.
* **Data Model**\
  Payloads consist of IEC 61850 datasets that contain Boolean status signals, analog values, timestamps, and quality bits. These correspond to Logical Nodes and Data Attributes defined in the 61850 object model.
* **Control Block & Dataset Configuration**\
  Each GOOSE message is defined by a **GOOSE Control Block (GCB)**, which specifies the dataset contents, MAC address, VLAN priority, retransmission timing, and state number. Engineering tools configure these via the SCL file (ICD/CID/SCD).
* **Transport Mechanism**\
  GOOSE is transmitted using **Layer‑2 multicast Ethernet frames**, typically with VLAN tagging (802.1Q), Priority tagging (802.1p), and MAC address: 01‑0C‑CD‑01‑00‑XX (GOOSE range). Because GOOSE bypasses TCP/IP, it achieves very low latency and deterministic performance.
* **Reliability & Latency Considerations**\
  GOOSE achieves reliability through deterministic retransmission intervals, sequence numbers, state numbers and mandatory VLAN & priority configuration. It is designed for **sub‑4 ms end‑to‑end latency**, suitable for protection and interlocking signals.
* **Security Model (Protocol‑agnostic)**\
  IEC 61850‑8‑1 does not natively provide encryption, authentication, or integrity protection. Deployments rely on network segmentation, dedicated protection VLANs, port security, GOOSE‑specific intrusion detection and optional IEC 62351‑6 profile. Security is implemented outside the GOOSE protocol.

## How the protocol works

* **Dataset & Control Block configuration**\
  Engineering tools generate SCL files that define, which data attributes belong in the GOOSE dataset, VLAN ID and priority, multicast MAC address, minimum/maximum retransmission intervals and GOOSE Control Block parameters. IEDs load these during initialization to determine how and where to publish GOOSE messages.
* **Event publication**\
  When a monitored signal changes (e.g., protection trip asserted), the publisher updates the dataset, increments the state number, sends a burst of GOOSE frames at very short intervals (e.g., 1–3 ms) and gradually increases the interval over time if the state does not change. Subscribers detect these changes immediately.
* **Reception & subscription**\
  Subscribing IEDs join the VLAN carrying the multicast address, monitor the GOOSE stream, verify sequence/state numbers and update internal logic in real‑time based on the dataset. Reception is connectionless: any device on the VLAN can subscribe.
* **Application processing**\
  GOOSE events feed interlocking logic, breaker control schemes, protection element coordination, load shedding sequences and distributed automation logic. The logic is evaluated on every new GOOSE frame.

## Example applications

* **Protection Schemes (Inter‑IED)**\
  GOOSE enables fast exchange of protection trips, blocking signals, breaker positions, and element statuses for busbar protection, transformer differential protection, breaker failure schemes and line protection permissive/blocking logic.
* **Interlocking & Supervisory Logic**\
  Highly coordinated operations such as preventing incorrect breaker operations, ensuring safe switching sequences and validating bay/feeder statuses across multiple IEDs are implemented using GOOSE messaging.
* **Fast Load Shedding & Remedial Control**\
  GOOSE supports millisecond‑scale triggers for under‑frequency shedding, remedial action schemes, distributed automation responses and rapid contingency mitigation.
* **Process Bus Communication**\
  In digital substations, GOOSE is used to exchange equipment status, alarms and interprocess automation signals between bay‑level and process‑level IEDs.
* **Testing & Simulation**\
  GOOSE streams can be published or replayed using test‑set tools to validate protection logic, perform scheme verification, or reproduce event scenarios.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.opal-rt.com/docs/rt-lab/configure-ios/communication-protocol-ios/iec-61850-8-1-goose.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
