IEC 61850 GOOSE (Generic Object Oriented Substation Event) is a publisher-subscriber communication model that replaces traditional copper wiring for binary signals like trip commands and interlocking. It transmits a dataset of status values across the local Ethernet network using multicast messaging, allowing a single intelligent electronic device (IED) to send a message simultaneously to multiple receiving IEDs within a strict 4-millisecond latency window.
Glossary
IEC 61850 GOOSE

What is IEC 61850 GOOSE?
A high-speed, peer-to-peer communication protocol defined by the IEC 61850 standard for exchanging protection and control signals between intelligent electronic devices in a substation.
Reliability is enforced through a retransmission mechanism that repeats messages with increasing intervals, ensuring delivery without requiring a TCP acknowledgment. Each GOOSE message carries a VLAN tag for traffic prioritization and a time-to-live parameter, enabling switches to filter stale data during network congestion. This protocol is foundational for substation automation intelligence and modern adaptive protection schemes.
Key Features of GOOSE Messaging
The Generic Object Oriented Substation Event (GOOSE) protocol is a high-speed, peer-to-peer communication mechanism designed to replace traditional copper wiring for protection and control signals within a substation.
Publisher-Subscriber Architecture
GOOSE operates on a publisher-subscriber model, eliminating the need for a master controller. An Intelligent Electronic Device (IED) publishes a GOOSE message onto the local network, and multiple subscribing IEDs simultaneously receive and process the data. This peer-to-peer mechanism is fundamentally different from client-server SCADA polling and enables true distributed protection logic.
Ultra-High Speed Retransmission
To guarantee delivery over non-deterministic Ethernet, GOOSE uses an aggressive retransmission mechanism. Upon a state change event, the message is sent at exponentially increasing intervals (e.g., 1 ms, 2 ms, 4 ms, 8 ms) before settling into a steady-state heartbeat. This ensures that even if a packet is lost during a network burst, the critical trip or block signal is received within the required 4 ms transfer time for fast protection applications.
VLAN Tagging and Priority
GOOSE frames are tagged with IEEE 802.1Q VLAN headers and IEEE 802.1p priority bits. By assigning a high priority (typically 4 or higher) and a dedicated Virtual LAN, GOOSE traffic bypasses standard TCP/IP stack queues. This logical segregation ensures that protection signals are not delayed by lower-priority engineering access or video traffic on the same physical network infrastructure.
Dataset and State Numbering
Each GOOSE message contains a Dataset—a pre-configured collection of data attributes (e.g., circuit breaker status, protection pickup, recloser block). The message includes a state number (StNum) that increments only when a data value changes, and a sequence number (SqNum) that increments with every retransmission. Subscribers use these numbers to detect missing packets, out-of-sequence frames, and configuration mismatches instantly.
Virtual Wiring Replacement
GOOSE effectively replaces hundreds of copper control cables with a single fiber optic or copper Ethernet link. Traditional hardwired signals—such as breaker failure initiate, lockout trips, and busbar protection interlocking—are mapped to logical data objects. This reduces material costs, eliminates ground potential rise risks, and allows protection schemes to be modified via software configuration rather than physical rewiring.
Quality and Test Mode Flags
Every GOOSE message carries a quality attribute for each data value, indicating validity, overflow, or failure states. Additionally, a test mode (Sim) bit allows IEDs to distinguish between live operational traffic and simulated signals during commissioning. Subscribers can be configured to ignore test messages, enabling safe, on-site testing of protection logic without tripping in-service breakers.
GOOSE vs. Sampled Values vs. MMS
Comparison of the three primary IEC 61850 communication protocols used for substation automation, highlighting their distinct purposes, performance characteristics, and data models.
| Feature | GOOSE | Sampled Values | MMS |
|---|---|---|---|
Primary Purpose | Protection & control signaling | Streaming digitized analog measurements | Client-server monitoring & control |
Communication Model | Publisher-subscriber (multicast) | Publisher-subscriber (multicast) | Client-server (TCP/IP) |
OSI Layer | Layer 2 (Ethernet) | Layer 2 (Ethernet) | Layer 7 (Application) |
Transmission Type | Event-driven (spontaneous) | Continuous streaming | Request-response |
Typical Latency | < 3 ms | < 1 ms | 10-100 ms |
Data Content | Binary status, trip commands | Current & voltage waveforms | Metering, settings, reports |
VLAN Tagging | |||
Retransmission Mechanism | Exponential backoff | None (loss tolerated) | TCP retransmission |
Frequently Asked Questions
Clear, technically precise answers to the most common questions about Generic Object Oriented Substation Events (GOOSE), the high-speed peer-to-peer communication mechanism defined by the IEC 61850 standard for substation automation.
IEC 61850 GOOSE (Generic Object Oriented Substation Event) is a publisher-subscriber communication model defined by the IEC 61850 standard for transmitting high-speed, time-critical protection and control signals between Intelligent Electronic Devices (IEDs) within a substation. Unlike traditional client-server protocols, GOOSE messages are multicast directly onto the local Ethernet network at Layer 2 (Data Link Layer) using a reserved multicast MAC address range, bypassing the TCP/IP stack entirely to achieve transmission times under 3 milliseconds. A GOOSE publisher sends a structured dataset containing binary status points (e.g., breaker position, trip signals) and analog values (e.g., current magnitude) in a single Ethernet frame. To guarantee delivery without acknowledgment mechanisms, the message is retransmitted at exponentially increasing intervals—starting as fast as every 1 millisecond and slowing to a steady-state heartbeat of several seconds. Each message carries a StNum (state number) that increments on a data change event and a SqNum (sequence number) that resets to zero with each new state, allowing subscribers to detect missed messages or out-of-sequence frames immediately. This mechanism replaces hundreds of hardwired copper control cables with a single fiber or copper Ethernet link, dramatically reducing installation cost, weight, and commissioning time while enabling flexible, software-defined protection logic.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding GOOSE requires familiarity with the broader IEC 61850 standard and the substation automation environment in which it operates. These related concepts define the data models, communication stacks, and engineering processes that enable high-speed peer-to-peer signaling.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us