IEC 61850 GOOSE Messaging is a publisher-subscriber communication mechanism defined in the IEC 61850 standard for substation automation. It replaces traditional copper wiring for binary signals—such as trip commands, breaker status, and interlocking—with multicast Ethernet frames transmitted directly between Intelligent Electronic Devices (IEDs) on the station bus. Each GOOSE message carries a structured dataset of status values and quality attributes, published repeatedly with increasing intervals to ensure delivery without requiring acknowledgment from subscribers.
Glossary
IEC 61850 GOOSE Messaging

What is IEC 61850 GOOSE Messaging?
IEC 61850 GOOSE Messaging is a high-speed, peer-to-peer communication protocol defined by the IEC 61850 standard that enables protection relays and bay controllers to exchange status and control signals across a substation local area network.
The protocol achieves deterministic transfer times under 4 milliseconds by mapping directly to the Ethernet data link layer, bypassing TCP/IP overhead. A retransmission mechanism begins with a minimum interval of 1 millisecond after a state change, then exponentially backs off to a steady-state heartbeat. Each frame includes a stNum (state number) and sqNum (sequence number) to allow subscribers to detect missed messages and maintain a fail-safe default state if communication is lost, ensuring protection-grade reliability.
Key Characteristics of GOOSE Messaging
Generic Object Oriented Substation Events (GOOSE) is a publisher-subscriber communication model that replaces traditional copper wiring with high-speed, multicast Ethernet frames for protection and control applications.
Publisher-Subscriber Architecture
GOOSE operates on a publisher-subscriber model, fundamentally different from client-server SCADA protocols. A single Intelligent Electronic Device (IED) publishes a dataset—such as a trip signal or breaker status—onto the substation LAN. Multiple subscribing IEDs simultaneously receive and process this data. This eliminates the need for point-to-point copper wiring between every relay and bay controller, drastically reducing design complexity and commissioning time. The multicast addressing ensures that critical state changes reach all logical nodes subscribed to the specific GOOSE control block within the required transfer time.
High-Speed Retransmission Mechanism
To guarantee delivery without TCP overhead, GOOSE employs a rapid retransmission strategy directly over Ethernet Layer 2. Upon a state change event, the IED publishes the GOOSE message immediately, then retransmits it at exponentially increasing intervals:
- T1 (First Retransmission): Typically 2-4 ms after the initial event.
- T2, T3... Tn: Intervals double until reaching a steady-state heartbeat period (e.g., 5-10 seconds). This mechanism ensures that even if the initial frame is lost due to a network microburst, subsequent frames arrive within the stringent 3 ms transfer time required for tripping applications, matching the performance of hardwired schemes.
VLAN Tagging and Priority
GOOSE frames are tagged with IEEE 802.1Q VLAN headers to enforce traffic segregation and quality of service on the substation bus. Key parameters include:
- Priority Code Point (PCP): Set to 4 or higher to ensure GOOSE traffic is placed in the highest priority egress queue on substation switches, ahead of SCADA or file transfer traffic.
- VLAN ID (VID): Isolates protection traffic into a dedicated virtual network, preventing broadcast storms from non-critical devices from impacting relay-to-relay communication. This strict prioritization is essential for meeting the deterministic latency requirements of IEC 61850-5 performance classes during fault conditions when network congestion peaks.
Dataset and State Numbering
Each GOOSE message carries a structured dataset—a predefined collection of data attributes like circuit breaker position, protection start, and quality bits. Integrity is maintained through strict numbering:
- StNum (State Number): Increments each time a data attribute within the dataset changes value. A subscriber detects a state change by comparing the received StNum to the last stored value.
- SqNum (Sequence Number): Increments with every retransmission of the same state, resetting to 1 when StNum changes. This allows subscribers to detect missing retransmission frames.
- TimeAllowedtoLive: A holdover timer that informs the subscriber how long to wait for the next expected retransmission before declaring a communication loss.
Virtual Wiring and Substation Configuration Language
The logical connections between publishing and subscribing IEDs are defined using the Substation Configuration Language (SCL) in XML format. The System Configuration Description (SCD) file binds GOOSE publishers to subscribers, replacing physical wiring diagrams with software-defined signal mapping. This enables:
- Late Binding: Protection engineers can modify trip logic and interlocking schemes without pulling new cables.
- Automated Testing: GOOSE subscriptions can be simulated and tested using software tools before commissioning.
- Full Traceability: Every signal path is documented in the SCD file, eliminating the ambiguity of undocumented field wiring modifications.
GOOSE vs. Sampled Values
While both are IEC 61850 Layer 2 protocols, they serve distinct purposes:
- GOOSE: Transmits binary status and analog setpoints (e.g., trip, close, interlock) on an event-driven basis. Data is published only when a change occurs, with a background heartbeat.
- Sampled Values (SV): Streams raw digitized current and voltage waveforms from merging units at high rates (80 samples/cycle for protection, 256 for metering). SV is a continuous, high-bandwidth stream. A modern process bus architecture uses SV to digitize the instrument transformer outputs and GOOSE to transmit the resulting trip commands, fully eliminating copper from the switchyard to the relay room.
Frequently Asked Questions
Clear, technically precise answers to the most common questions about Generic Object Oriented Substation Event messaging, its mechanism, and its role in modern protection schemes.
IEC 61850 GOOSE (Generic Object Oriented Substation Event) is a high-speed, peer-to-peer communication protocol that replaces traditional copper wiring for exchanging binary status and analog values between Intelligent Electronic Devices (IEDs) within a substation. Instead of a master-slave polling architecture, GOOSE uses a publisher-subscriber model over the substation Local Area Network (LAN). When a protection relay detects a state change—such as a breaker opening or a trip initiation—it multicasts a GOOSE message containing a dataset of attributes directly onto the network. To ensure delivery, the message is retransmitted with exponentially increasing intervals (e.g., 1 ms, 2 ms, 4 ms, up to a heartbeat of 1 second) until the state stabilizes. This mechanism guarantees delivery within a strict 3-4 millisecond transfer time for critical protection applications like teleprotection and breaker failure initiation, meeting the stringent performance requirements of IEC 61850-5 class P2/P3.
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
IEC 61850 GOOSE messaging operates within a broader ecosystem of protection schemes, intelligent devices, and automation standards. The following concepts are essential for understanding how high-speed peer-to-peer communication enables modern substation automation and fault management.

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